Re: [expert] Re: 3c905B
>> > 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! 3C905B what? There are a number of these, and I don't really know the difference.The most recent ones I've bought personally are 3C905B/TX(something) and they work great. I've got a few old 3C905B(nothings) that are so hosed I can't get them work properly with Windows but they'll work with DOS. Don't know if there was ever a 3c905(nothing). After my bad experience with the old ones I swore off 3com until recently. To be honest, I think what got wrong with 3com in the windows world was that 3com bought Palm, which put them in competition with MS, so the drivers mysteriously got mangled. But I'm not one to speculate. (Oh! I just did.) Michael Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Re: 3c905B
On Wed, Nov 22, 2000 at 09:39:20AM +0100, mike veltman wrote: > On Sun, 19 Nov 2000, you wrote: > > > > 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! > > > > Funny because I have two of them in my system and never had a problem. > i get from computer fairs for 3-4 ukp, bnc/thickwire/other-type only problem one i had was white silk screened, all my others working are yellow silk screened, apart from having to boot a box with dos to run the config program srp Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Re: 3c905B
On Sun, 19 Nov 2000, you wrote: > > 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! > Funny because I have two of them in my system and never had a problem. Mike -- --- E-mail : [EMAIL PROTECTED] OS : Linux Country : The Netherlands Kernel : 2.2.17 on a PII/233/128MB Function : Technical Consultant Target : Next Project - Use any OS, If it does what it needs to do -- Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Re: 3c905B
Hello all, for what it's worth I am using a variety of 3com 3c905 (ISA as well as PCI) cards with great success under LM 7.0, 7.1 and 7.2. I did have to set the cards (some at least) to plug n play = off and also set them to the IRQ I wanted to use. I used the dos utility from 3com's web site to do this. Simply make a DOS or WIN 9xx bootable disk and copy the DOS portion of the utility to the disk. Boot the machine and run the utility to set up the card. reboot into linux and if auto-detect doesn't find the card, set it up using your favorite method. Hope this helps, -- Ken Thompson Electrocom Computer Services Payette, Idaho (208) 642-7101 (888) 642-7101 Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Re: 3c905B
http://support.3com.com/infodeli/inotes/techtran/ff0e_5ea.htm was just looking on the 3com web site and found this little tidbit. think you should research their website a little regarding the card, firmware, ... you may need to run a dos config utility on the card to get it to work. that is a shot in the dark, but i have to go out the door NOW so good hunting later tom Brent Timmer wrote: > > 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 > n
RE: [expert] Re: 3c905B
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 > > >
[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
[expert] Re: 3c905B
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, devic
