this probably doesn't help people much, but I too have a 3c905b. It finds it as a boomerang(which it isn't), and it didn't work at all. I reinstalled linux (because of something else), and now miraculously it works fine. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Hoffman Sent: Saturday, November 18, 2000 8:14 PM To: Tom Berkley; [EMAIL PROTECTED] Subject: [expert] Re: 3c905B Tom, I did that card still is not seen. Also, change the /etc/modules.conf to both 3c59x and 3c90x same result. But I may have a clue for everyone... Starting scanning the Turbo linux dos and they had this pci config stuff. So I found Mandrakes stuff and made a little shell(pcistuff). If you look at the pci.lst file not all utilities report the card in the same manner perhaps if not being reported correctly it is not being initialized correctly. I also realize engineered message from different folks are not indicative of a problem. But then the question is what do the messages mean and where do we find the explanation of the messages? Run the shell on your system and send me the results so I may compare it to mine. Tom Berkley wrote: > Mandrake does not have problems with 3c905b cards. You want to just get > that one. Your installation has a problem with the card and the problem > is to find out what the problem is. Since the 3c905b does not have an > irq assigned and now that I know that the SMC is the other nic, remove > it and boot the system and see what happens. I think that you will find > the problem there. If you are using modules for the nic's, a line to the > /etc/modules.conf file > alias eth1 3c59x > There should also be a way to force the irq, I don't know the syntax, > but first check the nics for a conflict by removing the smc and > booting.\\ > > TB > > > Tom, > > > > The eth0 card is SMC-ultra hardware assigned IRQ 3 at io 280. So I am not nuts Mandrake has a problem with 3c905b cards! > > > > Tom Berkley wrote: > > > > > Well, so far I cannot find an IRQ assigned to either eth0 or eth1. That > > > is suspect and something to query the expert list about for starters. If > > > it were not for the eth0 also having no interrupt. Is the cable modem an > > > internal card type of device and if it is then its configuration is > > > probably conflicting with the eth0. I have no knowledge in that area and > > > cannot help there. > > > > > > Yeah, the more I look at the files you sent, the more I suspect either > > > the cable modem conflict or the 3Com just decided to pass on to the next > > > life. To verify the conflict, remove the modem install and see if it > > > works then. If not then contact 3Com for a swap. > > > > > > Tom Berkley > > > > > > Jeff Hoffman wrote: > > > > > > > > Tom, > > > > > > > > Thank you for some good input hard to find! > > > > > > > > I checked everything you said and it seems ok. Take a look at my > > > > configuration files I have attached.. > > > > > > > > Card comes UP when Linux starts however it just gets configured and never > > > > really comes UP. > > > > > > > > My eth0 is connected to my Cablemodem and is working fine. The 3com card is > > > > eth1and is connected to a 10/100 switch and I have good link lights. > > > > > > > > Tom Berkley wrote: > > > > > > > > > I take it that you have fired up linuxconf and gone to the network > > > > > section to configure the card. I looked at my config there and it uses > > > > > the 3c59x driver in mandrake 7.2... Its set to manual, there is a > > > > > primary name + domain (elbert.lunkhead), an ip address, the netmask is > > > > > 255.255.255.0, (if your netmask is not the same on all your machines, it > > > > > may not work) the net device is eth0, and the kernel module is 3c59x. I > > > > > do not us bind so I have all my machine names and ip addresses in > > > > > /etc/hosts and the /etc/resolv.conf has > > > > > > > > > > search my_isp_domainname > > > > > nameserver ipaddress > > > > > nameserver another ipaddress > > > > > nameserver yet another ipaddress > > > > > > > > > > and that's it. > > > > > > > > > > If that does not work when you restart the network, I would look in > > > > > /proc/interrupts and see what interrupt linux assigned to the nic. If > > > > > that is shared, then I would disable the hardware that it is shared with > > > > > (ie remove it or disable it in the bios if its usb). I would also remove > > > > > the nic and plug it back in just to make certain that its seated > > > > > properly in the slot. Don't laugh or sneer, I've seen hardware the > > > > > stopped working and started working again when this was done. > > > > > > > > > > While you're poking around in /proc look at the ioports and see what io > > > > > port is assigned to the nic. Do you have anything that is coming on line > > > > > later that has an ioport conflict. In laptops there can be conflicts > > > > > between pcmcia cards and the sound card that will lock a machine and you > > > > > have to power off to recover. I do not know of what would cause an > > > > > ioport conflict outside of this but there are some people around who may > > > > > know if you get this far. Poke around in /proc/net: cat out the dev file > > > > > and look at the eth0 status. > > > > > > > > > > How are you connected to the rest of your network? What are you plugging > > > > > into this nic? What mobo? Hub, switch, modem (dsl or cable), ??? > > > > > > > > > > I too have installed turbo linux. It did not like my hardware and made a > > > > > mess out of the partition that it was on, but redhat, mandrake, debian, > > > > > and win98se are very fond of my hardware. I don't know how to make your > > > > > hardware work, but I hope this gets you pointed in that direction. > > > > > > > > > > Tom Berkley > > > > > > > > > > Then I would look at the bios on the your motherboard and see if there > > > > > is an update. Next check with 3com and see if there is a firmware update > > > > > ( i've never seen a firmware update for an nic but this is the next step > > > > > on my list of things to check). > > > > > Jeff Hoffman wrote: > > > > > > > > > > > > Tom, > > > > > > > > > > > > OK I give up how do you make them work. > > > > > > > > > > > > The card is seen by harddrake and identified correcly. I have tried to > > > > > > use both the 3c59x and 3c90x drivers. Card configures just does not come > > > > > > "UP". > > > > > > > > > > > > So what am I missing? > > > > > > > > > > > > Turbo Linux on the same hardware will operate the card. > > > > > > > ------------------------------------------------------------------------ > > > > PCI devices found: > > > > Bus 0, device 0, function 0: > > > > Host bridge: Intel 82439TX (rev 1). > > > > Medium devsel. Master Capable. Latency=64. > > > > Bus 0, device 7, function 0: > > > > ISA bridge: Intel 82371AB PIIX4 ISA (rev 1). > > > > Medium devsel. Fast back-to-back capable. Master Capable. No bursts. > > > > Bus 0, device 7, function 1: > > > > IDE interface: Intel 82371AB PIIX4 IDE (rev 1). > > > > Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. > > > > I/O at 0xf000 [0xf001]. > > > > Bus 0, device 7, function 2: > > > > USB Controller: Intel 82371AB PIIX4 USB (rev 1). > > > > Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. > > > > I/O at 0x6400 [0x6401]. > > > > Bus 0, device 7, function 3: > > > > Bridge: Intel 82371AB PIIX4 ACPI (rev 1). > > > > Medium devsel. Fast back-to-back capable. > > > > Bus 0, device 16, function 0: > > > > VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1). > > > > Medium devsel. Master Capable. Latency=64. Min Gnt=4.Max Lat=255. > > > > Non-prefetchable 32 bit memory at 0xe0000000 [0xe0000000]. > > > > Bus 0, device 17, function 0: > > > > Ethernet controller: 3Com 3C905B 100bTX (rev 36). > > > > Medium devsel. Master Capable. Latency=64. Min Gnt=10.Max Lat=10. > > > > I/O at 0x6800 [0x6801]. > > > > Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000]. > > > > > > > ------------------------------------------------------------------------ > > > > Name: Dmesg.lst > > > > Dmesg.lst Type: application/x-unknown-content-type-lst_auto_file > > > > Encoding: base64 > > > > > > > > Name: Eth1up.lst > > > > Eth1up.lst Type: application/x-unknown-content-type-lst_auto_file > > > > Encoding: base64 > > > > > > > > Name: Ifconfig.lst > > > > Ifconfig.lst Type: application/x-unknown-content-type-lst_auto_file > > > > Encoding: base64 > > > > > > > ------------------------------------------------------------------------ > > > > CPU0 > > > > 0: 49923 XT-PIC timer > > > > 1: 631 XT-PIC keyboard > > > > 2: 0 XT-PIC cascade > > > > 3: 208 XT-PIC SMC Ultra > > > > 6: 55 XT-PIC floppy > > > > 8: 1 XT-PIC rtc > > > > 12: 19313 XT-PIC PS/2 Mouse > > > > 13: 1 XT-PIC fpu > > > > 14: 14437 XT-PIC ide0 > > > > 15: 20 XT-PIC ide1 > > > > NMI: 0 > > > > > > > ------------------------------------------------------------------------ > > > > 0000-001f : dma1 > > > > 0020-003f : pic1 > > > > 0040-005f : timer > > > > 0060-006f : keyboard > > > > 0070-007f : rtc > > > > 0080-008f : dma page reg > > > > 00a0-00bf : pic2 > > > > 00c0-00df : dma2 > > > > 00f0-00ff : fpu > > > > 0170-0177 : ide1 > > > > 01f0-01f7 : ide0 > > > > 0280-029f : SMC Ultra > > > > 0376-0376 : ide1 > > > > 0378-037f : parport0 > > > > 03c0-03df : vga+ > > > > 03f0-03f5 : floppy > > > > 03f6-03f6 : ide0 > > > > 03f7-03f7 : floppy DIR > > > > 0778-077a : parport0 > > > > 6800-687f : eth1 > > > > f000-f007 : ide0 > > > > f008-f00f : ide1 > > > > > > > ------------------------------------------------------------------------ > > > > Inter-| Receive | Transmit > > > > face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed > > > > lo: 3628 56 0 0 0 0 0 0 3628 56 0 0 0 0 0 0 > > > > eth0: 27244 267 0 0 0 0 0 210 6065 58 0 0 0 0 0 0 > > > > eth1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
