Problem with detecting ne2k-pci ethernet
Ben,
Before I describe my problem, let me state that I am not blaming
the graphical boot disk for this problem, though it may seem that way. At
this point, all I can do is describe my observations and let others
hypothesize....
I installed Slink about a month ago. Since then, whenever I booted
into it (my main work area is on a Redhat system installed on the same
machine), my Linksys ethernet card has been properly detected by the Slink
kernel. What is shown below is a snippet from my Redhat dmesg, but
something like that is what I used to see when booting into Slink.
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit
encapsulation enabled).
CSLIP: code copyright 1989 Regents of the University of California.
SLIP linefill/keepalive option.
ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker
http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html
ne2k-pci.c: PCI NE2000 clone 'Winbond 89C940' at I/O 0x1200, IRQ 10.
eth0: PCI NE2000 found at 0x1200, IRQ 10, 00:20:78:15:E3:9E.
Partition check:
Now the last time I successfully worked (according to my system
logs) on my Debian system was on Apr 5 18:45. Sometime after that I
downloaded and tried out the graphical boot floppy. After I failed at
that, I rebooted into Redhat and typed out my report of the test. The next
time I rebooted into Debian was on Apr 8 at 21:40. And from that time on,
the Debian kernel has steadfastly refused to acknowledge the presence of
my ethernet card.
If I manually insmod the 8390 and the ne2k-pci modules, the
ethernet support gets loaded correctly. But for the life of me, I cant
think of anything that changed that could cause this problem. My system
logs do not show anything untoward happening.
The only reason that I have to vaguely suspect the graphical boot
floppy was that I had asked it to mount (without reinitializing, of
course) the root Debian partition as root. Might it have changed anything?
I doubt it since the install subsequently failed, but then, things might
have changed without me being aware of it.
So my question are (1) How do I get my Debian kernel back to
normal and (2) Any idea on what caused this problem?
Regards,
Jor-el
Reply to: