Re: RH Fedora network interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Original Message ----- 
From: "Edward Dekkers" <edward@xxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, February 18, 2004 2:17 AM
Subject: Re: RH Fedora network interfaces


> Chris, I don't think it is so much an initialization at start-up that's
> failing, I'm thinking that on a warm boot as eth0 and 1 shut down,
> somehow the card is left in a jammed state. A warm boot does not remove
> power from the PCI bus (yes, even if they're on-board they're on the PCI
> bus). A cold boot does, hence in effect re-setting the card back to
> blank slate so to speak.
>
> I'm thinking the module for the card is not shutting the card back to
> blank slate mode on a warm boot.
>
> If you bring them down manually, then up again, what happens?
>
> Or more basic level, what about removing the module and re-installing it?
>
> Does Intel provide a Linux driver for that card?
>
> Those are the things I would look at.
>
> Regards,
> Ed.

I can bring up and down both interfaces after a cold boot and everything works
great.  But if I do a warm boot, the problem comes back to life - RH9 / Fedora
Core 1 will not see network ports.

I have downloaded the latest Intel drivers for this card, Pro/100 82559, and
when I 'make install' it goes okay but the last line says:

depmod: *** Unresolved symbols in
/lib/modules/2.4.22-1.2149.nptlsmp/kernel/drivers/net/e100.o

Is this a cause for concern?  (I am not physically in front of the server as I
write this so I didn't want to remotely reboot the sucker in case it doesn't
come back up and I have to drive to the datacenter again).

I did some digging on the error message above and in somewhat similar cases
(problems with getting network ports to work properly), I can also add that my
/etc/modules.conf has:

alias eth0 e100
alias eth1 e100

which appears to be correct.  The only other thing someone else had posted on a
vaguely related subject was that in his case some of the bootup scripts were
trying to access network ports ahead of 'ifconfig eth0 up' which was running
much later on in the bootup process.  Could this be a similar problem?  Where
can I look for the order this gets loaded in and where can I change it so that
'ifconfig eth0 up' runs later in the process?  (if that is a problem, that is)

Thanks,

Chris



-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux