I'm running SuSE 6.3 on a Pentium II. I'm running it via loadlin since this is a work computer and windows is still the main OS :-( I have a ISA NE2000 Ethernet adapter. During installation I declared it as eth0 device, but everytime I boot I get the message that the device is busy and so my network connection doesn't work. Could someone tell me what is wrong ? Thanks ! Moritz -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Moritz Lennert wrote:
I'm running SuSE 6.3 on a Pentium II. I'm running it via loadlin since this is a work computer and windows is still the main OS :-(
I have a ISA NE2000 Ethernet adapter.
During installation I declared it as eth0 device, but everytime I boot I get the message that the device is busy and so my network connection doesn't work.
My theory is that since you're booting from loadlin, Windows has already initialised the network card. So when Linux goes to initialise it, it finds that the cards already up and running and figures that it's busy (which it is, since Windows is (was) still using it). Unfortunately I can't see how to fix this, other than starting Linux before Windows gets at the network card. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Moritz" == Moritz Lennert
writes:
> I have a ISA NE2000 Ethernet adapter. > During installation I declared it as eth0 device, but everytime > I boot I get the message that the device is busy and so my > network connection doesn't work. It sounds like an irq conflict. If your card is a PNP card, you could try the ISA PNP package. If not, then you will have to find an unused irq and then set the card manually. You should then specify the options in /etc/modules.conf. For example, mine is: options ne io=0x280 irq=11 You can find out which irq's have been occupied by typing cat /proc/interrupts at the command prompt and you can see what ioports have been occupied by typing cat /proc/ioports Charles -- ===================================================== One Net to rule them all, One Net to find them, One Net to bring them all, and with Linux bind them. ===================================================== -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
chris.reeves@iname.com
-
cpchan@myna.com
-
mlennert@club.worldonline.be