From: Ashwin M. <ash...@ya...> - 2007-08-18 03:09:31
|
Martin Teufel wrote: > + modprobe ne > /lib/modules/2.4.34-grsec/kernel/drivers/net/ne.o: init_module: No such device or address > Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. 1. Check the IO and IRQ by using the utility floppy disk supplied (DOS bootable) at the time of purchase. 2. If possible, through the above utility enable auto selection of IRQ and IO. 3. Try loading the module with the correct parameters e.g. "modprobe ne io=0x300 irq=11" or load the module with autoprobe parameters check - http://tldp.org/HOWTO/Module-HOWTO/individual.html Hope it helps. with Regards, ASHWIN ____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC |
From: Ashwin M. <ash...@ya...> - 2007-08-23 04:23:56
|
Martin Teufel wrote: > Hello, > > I don't have a utitity floppy disk supplied with the system/NIC to boot from, but I checked out the IO and IRQ under Win98, and tried to give them Devil-Linux resp. the ne2k-pci as options, but nothing had changed. > Then I tried some random (high) IRQs like 7, 8, 9, 10, 11, 12 and after that (undo that) I tried to load the module with autoprobe parameters check. It changed nothing... > > [...] > > Btw.: Thanks for the URL: > http://tldp.org/HOWTO/Module-HOWTO/individual.html > It helped a bit and is a good summary. Just wanted to check if you loaded the module 8390 by the command "modprobe 8390" before trying to load the ne module. Maybe if you read the sections 15.4.15 and 15.4.16 it may help. First load the 8390 module and check if that loads at all. with Regards, ASHWIN ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 |
From: Martin T. <mar...@gm...> - 2007-08-23 07:40:57
|
Sorry, now I realized what you want to know. Of course I (or better: Devil-Linux / the ne2k-pci module) loaded all dependencies, including 8390 and crc32, but they are not used, just as the ne2k-pci module itself. It is loading it, no comments, no errors (as you can see below). ------------- root@Devil:~ # modprobe 8390 root@Devil:~ # root@Devil:~ # modprobe ne2k-pci root@Devil:~ # root@Devil:~ # modprobe -d 8390 ============================================= Module crc32 kname crc32 objkey crc32 names: crc32 mode: NORMAL Module matching crc32: /lib/modules/2.4.34-grsec/kernel/lib/crc32.o ============================================= ============================================= Module 8390 kname 8390 objkey 8390 names: 8390 mode: NORMAL Module matching 8390: /lib/modules/2.4.34-grsec/kernel/drivers/net/8390.o ============================================= root@Devil:~ # root@Devil:~ # modprobe -d ne2k-pci ============================================= Module crc32 kname crc32 objkey crc32 names: crc32 mode: NORMAL Module matching crc32: /lib/modules/2.4.34-grsec/kernel/lib/crc32.o ============================================= ============================================= Module 8390 kname 8390 objkey 8390 names: 8390 mode: NORMAL Module matching 8390: /lib/modules/2.4.34-grsec/kernel/drivers/net/8390.o ============================================= ============================================= Module ne2k-pci kname ne2k-pci objkey ne2k-pci names: ne2k-pci mode: NORMAL Module matching ne2k-pci: /lib/modules/2.4.34-grsec/kernel/drivers/net/ne2k-pci.o ============================================= root@Devil:~ # Listing all loaded modules: [...] ne2k-pci 4608 0 8390 6288 0 [ne2k-pci] crc32 2896 0 [8390] [...] ------------- Btw: Meanwhile I tried a third NIC (a RTL8029AS), and (what a wonder) it is exactly the same fault... -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger |
From: Ashwin M. <ash...@ya...> - 2007-08-23 08:07:51
|
Martin Teufel wrote: > Btw: Meanwhile I tried a third NIC (a RTL8029AS), and (what a wonder) it is exactly the same fault... What does "lspci" or "lspci -v" says ? Does it recognize the presence of the card ? with Regards, ASHWIN ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ |
From: Martin T. <mar...@gm...> - 2007-08-23 23:42:42
|
Of course it does! Every PCI-NIC I tried was recognized correctly. That's not the matter... ------------- lspci: [...] 00:08.0 SCSI storage controller: Adaptec AHA-7850 (rev 01) 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) 00:0a.0 VGA compatible controller: Cirrus Logic GD 5446 [...] lspci -v: [...] 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) Subsystem: Realtek Semiconductor Co., Ltd. RTL-8029(AS) Flags: medium devsel I/O ports at 1400 [size=32] Expansion ROM at <unassigned> [disabled] [size=32K] [...] setup -> NIC: Listing all known PCI Ethernet cards: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) (rev 0). -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser |
From: Ashwin M. <ash...@ya...> - 2007-08-24 17:55:21
|
Martin Teufel wrote: > Of course it does! > Every PCI-NIC I tried was recognized correctly. That's not the matter... > > Hope you know how to bring up the interface with an fixed IP address or use use dhcp to obtain an ip address for the interface eth0. You can also configure devil-linux with the IP parameters to do the job automatically too. However, I have strong feeling reading the manual i.e. "man ifconfig" will surely help. Further beyond this point continuing this thread would be technically an OT on this list. You can definitely check some NET Howto's or email me off the list. with Regards, ASHWIN ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC |
From: Martin T. <mar...@gm...> - 2007-08-27 01:40:18
|
Yes, I know how to bring up the interface with an fixed IP address etc... Finally I got the eth0 up, and want to post it here for possible future readers with the same problem: The reference to the manual of ifconfig wasn't so bad. Reading this made me try "ifconfig eth0 up". This gave me the error message "SIOCSIFFLAGS: Device or resource busy". I gave this message to google and came on [http://www.fedoraforum.org/forum/showthread.php?t=21264]. So I tried this, and eth0 came up on the next reboot. In other words: The setting in my (ugly) AMI-BIOS below PCI/PnP called "Plug and Play Aware O/S: no" made my eth0 busy and not working under Linux. I just turned it to "yes" and eth0 (my PCI-NIC) came up and running. [to run with Windows it has to be in "no" mode] Btw: The pppoe-start is still not working, but that's another problem and maybe should not be discussed here... Thanks to all who tried to help me. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer |
From: Martin T. <mar...@gm...> - 2007-08-23 03:42:05
|
Hello, I don't have a utitity floppy disk supplied with the system/NIC to boot from, but I checked out the IO and IRQ under Win98, and tried to give them Devil-Linux resp. the ne2k-pci as options, but nothing had changed. Then I tried some random (high) IRQs like 7, 8, 9, 10, 11, 12 and after that (undo that) I tried to load the module with autoprobe parameters check. It changed nothing... As I had no further ideas, I changed the NIC and built in a 3Com 3C905b-TX (PCI) (instead of the Compex RL2000A) and loaded (as I read to be the suitable driver) the 3c59x module. But: It's just the same! Module loaded, but not used... --------------- Listing all loaded modules: Module Size Used by Not tainted ppp_synctty 5544 0 (unused) ppp_async 6976 0 (unused) ppp_generic 23176 0 [ppp_synctty ppp_async] slhc 4736 0 [ppp_generic] p80211 18500 0 (unused) ipv6 175956 -1 3c509 10324 1 3c59x 27216 0 lvm-mod 60608 0 (autoclean) md 58400 0 (autoclean) libata 38648 0 (unused) loop 48688 0 eth0 Link encap:Ethernet HWaddr 00:50:04:65:55:4E BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Base address:0x1400 --------------- I just don't understand that... If it would be Windows (;-)), I would suppose that the NIC is disabled. And while I looked in some .config files to search for the cause of the fault, I found something strange (not directly in a file): modprobe --showconfig: [...] alias char-major-200 vxspec alias char-major-206 osst alias char-major-216 rfcomm alias dos msdos alias dummy0 dummy alias dummy1 dummy alias eth0 off alias iso9660 isofs alias md-personality-1 linear alias md-personality-2 raid0 alias md-personality-3 raid1 alias md-personality-4 raid5 alias md-personality-7 multipath [...] Why "alias eth0 off"?? Where does this come from? Could that be the fault? I'm confused... (and not a Linux-expert) Is there anybody who understands what is going on at my Devil-Linux? Btw.: Thanks for the URL: http://tldp.org/HOWTO/Module-HOWTO/individual.html It helped a bit and is a good summary. If it can be helpful, I could place my etc.tar.bz2 on a server, if someone is interested in looking through it. Thanks for any further suggestions. -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser |