I read at these links that I should be using the 3Com driver for my 3c905C-TX NIC: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html http://support.3com.com/infodeli/tools/nic/linuxdownloading.htm The driver, 3c90x is in available on my 6.3 system. locate 3c90x.o /lib/modules/2.2.13/net/3c90x.o So, I modified /etc/modules.conf like this: fgrep 3c /etc/modules.conf #alias eth0 3c59x alias eth0 3c90x and rebooted. But it still seems to use the old driver: lsmod | fgrep 3c 3c59x 19008 1 Where else could that module be loaded? I find this confusing. I have not built my own kernel. I do remember during the initial installation using Yast1 that I asked Yast to auto-detected my NIC, which it did. And now, looking at Yast->System admin->Integrate hardware into system->Configure networking device says: "3Com 3c90x/3c980 B/C series". Looks ok to me. I'm wondering first why changing modules.conf didn't work, and then if using the new 3com driver will clear up this /var/log/messages error: kernel: eth0: Transmit error, Tx status register 82. And also I see this in the boot log: <6>3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html <6>eth0: 3Com 3c905C Tornado at 0xd000, ***INVALID CHECKSUM 0027*** 00:50:da:d7:93:e9, IRQ 11 <6> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. <6> MII transceiver found at address 24, status 782d. <6> Enabling bus-master transmits and whole-frame receives. Also, anyone using two of these NICs in one computer? I noticed this (anonymous) person claiming that more than one card doesn't work: http://lhd.datapower.com/db/dispreport.cgi?DISP?875 Anyone know anything about that? Thanks, Bill Moseley mailto:moseley@hank.org -- 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/
Oh, fixed. I think.
I didn't know about the initrd system, and finally found and changed in
rc.config:
#INITRD_MODULES="3c59x"
INITRD_MODULES="3c90x"
And then I ran mk_initrd, but I'm not sure why got the message:
"no such kernel image: "//boot/vmlinuz.suse"
root@mardy:/etc > /sbin/mk_initrd
using "/dev/hda3" as root device (mounted on "/")
creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.2.13)
adding module "/lib/modules/2.2.13/net/3c90x.o"
no such kernel image: "//boot/vmlinuz.suse"
But it seems to work:
lsmod | fgrep 3c
3c90x 19628 1
And
fgrep 3c /var/log/boot.msg
<4>3Com 3c90x Version 1.0.0 1999
I read at these links that I should be using the 3Com driver for my 3c905C-TX NIC: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html http://support.3com.com/infodeli/tools/nic/linuxdownloading.htm
The driver, 3c90x is in available on my 6.3 system. locate 3c90x.o /lib/modules/2.2.13/net/3c90x.o
So, I modified /etc/modules.conf like this:
fgrep 3c /etc/modules.conf #alias eth0 3c59x alias eth0 3c90x
and rebooted. But it still seems to use the old driver:
lsmod | fgrep 3c 3c59x 19008 1
Where else could that module be loaded? I find this confusing.
I have not built my own kernel. I do remember during the initial installation using Yast1 that I asked Yast to auto-detected my NIC, which it did. And now, looking at Yast->System admin->Integrate hardware into system->Configure networking device says: "3Com 3c90x/3c980 B/C series". Looks ok to me.
I'm wondering first why changing modules.conf didn't work, and then if using the new 3com driver will clear up this /var/log/messages error:
kernel: eth0: Transmit error, Tx status register 82.
And also I see this in the boot log:
<6>3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
<6>eth0: 3Com 3c905C Tornado at 0xd000, ***INVALID CHECKSUM 0027*** 00:50:da:d7:93:e9, IRQ 11
<6> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. <6> MII transceiver found at address 24, status 782d. <6> Enabling bus-master transmits and whole-frame receives.
Also, anyone using two of these NICs in one computer? I noticed this (anonymous) person claiming that more than one card doesn't work:
http://lhd.datapower.com/db/dispreport.cgi?DISP?875
Anyone know anything about that?
Thanks,
Bill Moseley mailto:moseley@hank.org
-- 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/
Bill Moseley mailto:moseley@hank.org -- 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/
Bill Moseley wrote:
Oh, fixed. I think.
Good to hear.
I didn't know about the initrd system, and finally found and changed in rc.config:
#INITRD_MODULES="3c59x" INITRD_MODULES="3c90x"
And then I ran mk_initrd, but I'm not sure why got the message: "no such kernel image: "//boot/vmlinuz.suse"
root@mardy:/etc > /sbin/mk_initrd using "/dev/hda3" as root device (mounted on "/") creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.2.13) adding module "/lib/modules/2.2.13/net/3c90x.o" no such kernel image: "//boot/vmlinuz.suse"
But it seems to work:
lsmod | fgrep 3c 3c90x 19628 1
And
fgrep 3c /var/log/boot.msg <4>3Com 3c90x Version 1.0.0 1999
Looks good!
My only question now is what I need to do, if anything, to add a second 3c905c NIC into the system.
Well, since Linux only every looks for one network card when a module is loaded, you must tell it that there is, in fact, a second card. To do this enter the following at the LILO prompt (assuming the kernel image you're going to use is called 'linux', and that you know the IRQ and IO address for the card): linux ether=io,irq,eth1 If this works and both cards are detected, you can add this as an append line in /etc/lilo.conf, of the form: append="ether=io,irq,eth1"
At 11:53 PM 04/23/00 -0700, Bill Moseley wrote:
I read at these links that I should be using the 3Com driver for my 3c905C-TX NIC: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html http://support.3com.com/infodeli/tools/nic/linuxdownloading.htm
The driver, 3c90x is in available on my 6.3 system. locate 3c90x.o /lib/modules/2.2.13/net/3c90x.o
So, I modified /etc/modules.conf like this:
fgrep 3c /etc/modules.conf #alias eth0 3c59x alias eth0 3c90x
and rebooted. But it still seems to use the old driver:
lsmod | fgrep 3c 3c59x 19008 1
Where else could that module be loaded? I find this confusing.
I have not built my own kernel. I do remember during the initial installation using Yast1 that I asked Yast to auto-detected my NIC, which it did. And now, looking at Yast->System admin->Integrate hardware into system->Configure networking device says: "3Com 3c90x/3c980 B/C series". Looks ok to me.
I'm wondering first why changing modules.conf didn't work, and then if using the new 3com driver will clear up this /var/log/messages error:
kernel: eth0: Transmit error, Tx status register 82.
And also I see this in the boot log:
<6>3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
<6>eth0: 3Com 3c905C Tornado at 0xd000, ***INVALID CHECKSUM 0027*** 00:50:da:d7:93:e9, IRQ 11
<6> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. <6> MII transceiver found at address 24, status 782d. <6> Enabling bus-master transmits and whole-frame receives.
Also, anyone using two of these NICs in one computer? I noticed this (anonymous) person claiming that more than one card doesn't work:
http://lhd.datapower.com/db/dispreport.cgi?DISP?875
Anyone know anything about that?
Hope that helps, 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/
At 05:07 PM 04/24/00 +0100, Chris Reeves wrote:
My only question now is what I need to do, if anything, to add a second 3c905c NIC into the system.
Well, since Linux only every looks for one network card when a module is loaded, you must tell it that there is, in fact, a second card. To do this enter the following at the LILO prompt (assuming the kernel image you're going to use is called 'linux', and that you know the IRQ and IO address for the card): linux ether=io,irq,eth1
If this works and both cards are detected, you can add this as an append line in /etc/lilo.conf, of the form: append="ether=io,irq,eth1"
Hum, I guess I don't understand PCI cards. How will I even know the IRQ for the card? ftp://ftp.3com.com/pub/nic/linux/readme.txt says only to modify modules.conf, but I'm not sure that's even being used for my NIC. That page talks about how the driver assigning eth0, eth1 and so on by auto-detecting the card, and where they are in the PCI slots. Hardware! Thanks for the help, Bill Moseley mailto:moseley@hank.org -- 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 (2)
-
chris.reeves@iname.com
-
moseley@hank.org