NIC trouble...quickly reaching the last straw with Suse
My Suse experience is now turning uglier. I'd had problems with sound in Suse 7.1 until very recently. I never did find out where the problem was...I just ended up doing a whole reinstallation. After that installation, the sound still had to be configured but after I configured it, I had the sound working for the first time in a LONG time. Let's hope it stays that way. Anyways, now I'm having NIC problems. I'm using two NICs for this two-system local LAN: Netgear FA310TX and a Japanese card that supposedly uses the VIA Rhine module. System 1 has the Netgear NIC and System 2 has the VIA card. Before I did the reinstall (on System 1) I was using two NICs on this system (one Netgear and one VIA-chipped). I could only use the Netgear in Linux because Windows 98 wouldn't configure this card. I relied on the VIA card for network use in Windows. This meant I had to swap the CAT5 cable everytime I went from one OS to another. System 2 uses only one NIC, the Netgear one. This system dualboots Windows 98 and Suse 7.1. This is the way System 1 is SUPPOSED to run, but I don't know why W98 doesn't like the Netgear NIC. I swear, it works in one OS but not the other. So, what I did was take out System 1's Netgear NIC and replace it with the VIA one. Before I reinstalled Suse 7.1 on System 1, I could network fine, but now that I'm using the VIA, I keep getting these messages in Suse's console window: Aug 1 17:03:32 500mhz kernel: PCI: Found IRQ 9 for device 00:0a.0 Aug 1 17:03:48 500mhz kernel: eth0: Transmit timed out, status 0000, PHY status 0000, resetting... Aug 1 17:04:20 500mhz last message repeated 8 times Aug 1 17:05:24 500mhz last message repeated 16 times Aug 1 17:06:28 500mhz last message repeated 16 times Aug 1 17:07:32 500mhz last message repeated 16 times Aug 1 17:08:33 500mhz last message repeated 13 times It's filling up my logs bigtime. The only way to get the logging to stop is to remove the via-rhine module from /etc/modules.conf. Here's what ifconfig says: root@500mhz:/home/ron > ifconfig eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::/10 Scope:Link inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:586 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xe800 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16080 Metric:1 RX packets:120 errors:0 dropped:0 overruns:0 frame:0 TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 So....let's see....Windows on System 1 doesn't like the Netgear NIC and Linux doesn't seem to like the VIA one, yet the Netgear works on this system's Linux and the VIA works on this system's Windows. Since this is the case, I'm doubting there's any problems with the CAT5 cables or the NICs themselves. This has to be a software problem or I'm seriously doing something wrong when configuring these NICs. The VIA in System 1 was working fine with Linux initially. I can ping theloopback and the host's IP fine. When I try to ping the other networked computer, I get this message: root@500mhz:/home/ron > ping 400mhz PING 400mhz.zama.com (192.168.2.20): 56 data bytes It then does nothing...like it's locked or waiting for the other system to reply. If I go to the other system and try the same thing, the exact same thing happens (both are running Suse 7.1). I'm at a loss here and after weeks of reading up and triple checking to make sure I've not forgotten anything, I'm again burned out with Suse. This is crazy. Sorry for the long post but I couldn't seek helpl without giving specifics... HELP! --- Ron Sinclair aka NipponDSM http://members.tripod.com/~WIGGLIT http://www.wigglit.com
Ron Sinclair wrote:
My Suse experience is now turning uglier. ....
I'm at a loss here and after weeks of reading up and triple checking to make sure I've not forgotten anything, I'm again burned out with Suse. This is crazy.
HELP!
I can understand your frustration, since I've been there myself. But I don't think it's quite fair to blame SuSE for a problem with a very particular configuration, particularly when you haven't been able to diagnose the problem yet. You seem already to have done some work with fault isolation, for instance by seeing what works in Windows as a way of ruling out hardware problems. What might be useful would be to find out if anyone else here has hardware similar to yours and if they've had the same problems. You're more likely to get a useful response if you put the question that way than if you post a long history (though sometimes the long history strikes a responsive chord somewhere). Paul
The NIC was working for a time and then it stopped for no apparent reason. I'd not tinkered with it since it was working (if it ain't broke, don't fix it). Been having alot of Suse problems lately, not just this one. Got pissed enough to where I wiped it off one of my systems and replaced it with Slack 7.0. I no longer have NIC problems and am learning how to administer a bare system. :o) The reason I included the history is because I can't stand when a poster doesn't include enough information for people to help. I'm not one for trading 20 emails on one problem. Also, working with NICs is much more elaborate than anything else on a computer system, even in Windows. I felt the information I provided was pertinent to this situation.
I can understand your frustration, since I've been there myself. But I don't think it's quite fair to blame SuSE for a problem with a very particular configuration, particularly when you haven't been able to diagnose the problem yet. You seem already to have done some work with fault isolation, for instance by seeing what works in Windows as a way of ruling out hardware problems. What might be useful would be to find out if anyone else here has hardware similar to yours and if they've had the same problems. You're more likely to get a useful response if you put the question that way than if you post a long history (though sometimes the long history strikes a responsive chord somewhere).
Paul
You forgot to tell us what nic your trying to get to work. I know that linksys cards are bears sometimes. 97% of the time i get linksys to work wth suse but sometimes its a bear an i have to workw with it for a while to get it work. tell us the nic brand please jack At 11:36 PM 8/7/2001 +0900, Ron Sinclair wrote:
The NIC was working for a time and then it stopped for no apparent reason. I'd not tinkered with it since it was working (if it ain't broke, don't fix it). Been having alot of Suse problems lately, not just this one. Got pissed enough to where I wiped it off one of my systems and replaced it with Slack 7.0. I no longer have NIC problems and am learning how to administer a bare system. :o)
The reason I included the history is because I can't stand when a poster doesn't include enough information for people to help. I'm not one for trading 20 emails on one problem. Also, working with NICs is much more elaborate than anything else on a computer system, even in Windows. I felt the information I provided was pertinent to this situation.
I can understand your frustration, since I've been there myself. But I don't think it's quite fair to blame SuSE for a problem with a very particular configuration, particularly when you haven't been able to diagnose the problem yet. You seem already to have done some work with fault isolation, for instance by seeing what works in Windows as a way of ruling out hardware problems. What might be useful would be to find out if anyone else here has hardware similar to yours and if they've had the same problems. You're more likely to get a useful response if you put the question that way than if you post a long history (though sometimes the long history strikes a responsive chord somewhere).
Paul
-- 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/faq and the archives at http://lists.suse.com
OK. It's a Laneed LS-10/100AL PCI. It's a japanese manufactured card. I tried to find as much info as possible online but almost all the sites were in japanese. I found one site that showed how it could be used with TurboLinux (big distro in Japan)...the site was in japanese but commandline instructions were in english (linux commands are universal...thank God!). I only got this card to work using TurboLinux and I HATE that distro with a passion! What may help is that on the chipset on the NIC, it says "VIA VT6102" Ron Sinclair http://members.tripod.com/~WIGGLIT http://members.fortunecity.com/wigglit http://wigglit.com
You forgot to tell us what nic your trying to get to work. I know that linksys cards are bears sometimes. 97% of the time i get linksys to work wth suse but sometimes its a bear an i have to workw with it for a while to get it work. tell us the nic brand please
jack
At 11:36 PM 8/7/2001 +0900, Ron Sinclair wrote:
The NIC was working for a time and then it stopped for no apparent reason. I'd not tinkered with it since it was working (if it ain't broke, don't fix it). Been having alot of Suse problems lately, not just this one. Got pissed enough to where I wiped it off one of my systems and replaced it with Slack 7.0. I no longer have NIC problems and am learning how to administer a bare system. :o)
The reason I included the history is because I can't stand when a poster doesn't include enough information for people to help. I'm not one for trading 20 emails on one problem. Also, working with NICs is much more elaborate than anything else on a computer system, even in Windows. I felt the information I provided was pertinent to this situation.
You may find this useful : http://www.scyld.com/network/ethercard.html. Also, it seems that this card uses same chipset as the DLink DFE-530TX (VIA Rhine) so you may find that a search on this card provides more English results. M On Tuesday 07 August 2001 3:10 pm, Ron Sinclair wrote:
OK. It's a Laneed LS-10/100AL PCI. It's a japanese manufactured card. I tried to find as much info as possible online but almost all the sites were in japanese. I found one site that showed how it could be used with TurboLinux (big distro in Japan)...the site was in japanese but commandline instructions were in english (linux commands are universal...thank God!). I only got this card to work using TurboLinux and I HATE that distro with a passion!
What may help is that on the chipset on the NIC, it says "VIA VT6102"
Ron Sinclair http://members.tripod.com/~WIGGLIT http://members.fortunecity.com/wigglit http://wigglit.com
You forgot to tell us what nic your trying to get to work. I know that linksys cards are bears sometimes. 97% of the time i get linksys to work wth suse but sometimes its a bear an i have to workw with it for a while
to
get it work. tell us the nic brand please
jack
At 11:36 PM 8/7/2001 +0900, Ron Sinclair wrote:
The NIC was working for a time and then it stopped for no apparent
reason.
I'd not tinkered with it since it was working (if it ain't broke, don't
fix
it). Been having alot of Suse problems lately, not just this one. Got pissed enough to where I wiped it off one of my systems and replaced it
with
Slack 7.0. I no longer have NIC problems and am learning how to
administer
a bare system. :o)
The reason I included the history is because I can't stand when a poster doesn't include enough information for people to help. I'm not one for trading 20 emails on one problem. Also, working with NICs is much more elaborate than anything else on a computer system, even in Windows. I
felt
the information I provided was pertinent to this situation.
Ron Sinclair wrote:
My Suse experience is now turning uglier.
I'd had problems with sound in Suse 7.1 until very recently. I never did find out where the problem was...I just ended up doing a whole reinstallation. After that installation, the sound still had to be configured but after I configured it, I had the sound working for the first time in a LONG time. Let's hope it stays that way.
Anyways, now I'm having NIC problems. I'm using two NICs for this two-system local LAN: Netgear FA310TX and a Japanese card that supposedly uses the VIA Rhine module. System 1 has the Netgear NIC and System 2 has the VIA card.
Before I did the reinstall (on System 1) I was using two NICs on this system (one Netgear and one VIA-chipped). I could only use the Netgear in Linux because Windows 98 wouldn't configure this card. I relied on the VIA card for network use in Windows. This meant I had to swap the CAT5 cable everytime I went from one OS to another.
System 2 uses only one NIC, the Netgear one. This system dualboots Windows 98 and Suse 7.1. This is the way System 1 is SUPPOSED to run, but I don't know why W98 doesn't like the Netgear NIC. I swear, it works in one OS but not the other.
So, what I did was take out System 1's Netgear NIC and replace it with the VIA one. Before I reinstalled Suse 7.1 on System 1, I could network fine, but now that I'm using the VIA, I keep getting these messages in Suse's console window:
Aug 1 17:03:32 500mhz kernel: PCI: Found IRQ 9 for device 00:0a.0 Aug 1 17:03:48 500mhz kernel: eth0: Transmit timed out, status 0000, PHY status 0000, resetting... Aug 1 17:04:20 500mhz last message repeated 8 times Aug 1 17:05:24 500mhz last message repeated 16 times Aug 1 17:06:28 500mhz last message repeated 16 times Aug 1 17:07:32 500mhz last message repeated 16 times Aug 1 17:08:33 500mhz last message repeated 13 times
It's filling up my logs bigtime. The only way to get the logging to stop is to remove the via-rhine module from /etc/modules.conf.
Here's what ifconfig says:
root@500mhz:/home/ron > ifconfig eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::/10 Scope:Link inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:586 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xe800
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16080 Metric:1 RX packets:120 errors:0 dropped:0 overruns:0 frame:0 TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
So....let's see....Windows on System 1 doesn't like the Netgear NIC and Linux doesn't seem to like the VIA one, yet the Netgear works on this system's Linux and the VIA works on this system's Windows. Since this is the case, I'm doubting there's any problems with the CAT5 cables or the NICs themselves. This has to be a software problem or I'm seriously doing something wrong when configuring these NICs.
The VIA in System 1 was working fine with Linux initially. I can ping theloopback and the host's IP fine. When I try to ping the other networked computer, I get this message:
root@500mhz:/home/ron > ping 400mhz PING 400mhz.zama.com (192.168.2.20): 56 data bytes
It then does nothing...like it's locked or waiting for the other system to reply.
If I go to the other system and try the same thing, the exact same thing happens (both are running Suse 7.1).
I'm at a loss here and after weeks of reading up and triple checking to make sure I've not forgotten anything, I'm again burned out with Suse. This is crazy.
Sorry for the long post but I couldn't seek helpl without giving specifics...
HELP!
--- Ron Sinclair aka NipponDSM http://members.tripod.com/~WIGGLIT http://www.wigglit.com
Last tiume I got errors like that, it was the cable. Cables are pretty cheap, try a new one. May or may not be the issue, but its one to get out the way. Matt
On Wednesday 01 August 2001 13:30, StarTux wrote:
Ron Sinclair wrote:
My Suse experience is now turning uglier.
I'd had problems with sound in Suse 7.1 until very recently. I never did find out where the problem was...I just ended up doing a whole reinstallation. After that installation, the sound still had to be configured but after I configured it, I had the sound working for the first time in a LONG time. Let's hope it stays that way.
Anyways, now I'm having NIC problems. I'm using two NICs for this two-system local LAN: Netgear FA310TX and a Japanese card that supposedly uses the VIA Rhine module. System 1 has the Netgear NIC and System 2 has the VIA card.
Before I did the reinstall (on System 1) I was using two NICs on this system (one Netgear and one VIA-chipped). I could only use the Netgear in Linux because Windows 98 wouldn't configure this card. I relied on the VIA card for network use in Windows. This meant I had to swap the CAT5 cable everytime I went from one OS to another.
System 2 uses only one NIC, the Netgear one. This system dualboots Windows 98 and Suse 7.1. This is the way System 1 is SUPPOSED to run, but I don't know why W98 doesn't like the Netgear NIC. I swear, it works in one OS but not the other.
So, what I did was take out System 1's Netgear NIC and replace it with the VIA one. Before I reinstalled Suse 7.1 on System 1, I could network fine, but now that I'm using the VIA, I keep getting these messages in Suse's console window:
Aug 1 17:03:32 500mhz kernel: PCI: Found IRQ 9 for device 00:0a.0 Aug 1 17:03:48 500mhz kernel: eth0: Transmit timed out, status 0000, PHY status 0000, resetting... Aug 1 17:04:20 500mhz last message repeated 8 times Aug 1 17:05:24 500mhz last message repeated 16 times Aug 1 17:06:28 500mhz last message repeated 16 times Aug 1 17:07:32 500mhz last message repeated 16 times Aug 1 17:08:33 500mhz last message repeated 13 times
It's filling up my logs bigtime. The only way to get the logging to stop is to remove the via-rhine module from /etc/modules.conf.
Here's what ifconfig says:
root@500mhz:/home/ron > ifconfig eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::/10 Scope:Link inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:586 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xe800
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16080 Metric:1 RX packets:120 errors:0 dropped:0 overruns:0 frame:0 TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
So....let's see....Windows on System 1 doesn't like the Netgear NIC and Linux doesn't seem to like the VIA one, yet the Netgear works on this system's Linux and the VIA works on this system's Windows. Since this is the case, I'm doubting there's any problems with the CAT5 cables or the NICs themselves. This has to be a software problem or I'm seriously doing something wrong when configuring these NICs.
The VIA in System 1 was working fine with Linux initially. I can ping theloopback and the host's IP fine. When I try to ping the other networked computer, I get this message:
root@500mhz:/home/ron > ping 400mhz PING 400mhz.zama.com (192.168.2.20): 56 data bytes
It then does nothing...like it's locked or waiting for the other system to reply.
If I go to the other system and try the same thing, the exact same thing happens (both are running Suse 7.1).
I'm at a loss here and after weeks of reading up and triple checking to make sure I've not forgotten anything, I'm again burned out with Suse. This is crazy.
Sorry for the long post but I couldn't seek helpl without giving specifics...
HELP!
--- Ron Sinclair aka NipponDSM http://members.tripod.com/~WIGGLIT http://www.wigglit.com
Last tiume I got errors like that, it was the cable. Cables are pretty cheap, try a new one. May or may not be the issue, but its one to get out the way.
Matt
I think it might be the cable also... Something is strange because I have about 4 machines with FA310TX's running both linux and windows (at various times). Never had a problem configuring that card on either Win or Linux. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 08/01/01 14:51 + +----------------------------------------------------------------------------+ "Never criticize someone until you have walked a mile in their shoes. That way, when you criticize them, you will be a mile away and have their shoes."
The cables weren't the problem as they work fine with Windows. That's the first thing I learned about running a network....check the cables FIRST as a possible culprit as there is a high chance that the NIC is unplugged, has an open, or is pinched or defective. Thanks though... Ron Sinclair http://members.tripod.com/~WIGGLIT http://members.fortunecity.com/wigglit http://wigglit.com
Last tiume I got errors like that, it was the cable. Cables are pretty cheap, try a new one. May or may not be the issue, but its one to get out the way.
Matt
participants (6)
-
Bruce Marshall -
Jack Malone -
Martin Webster -
Paul Abrahams -
Ron Sinclair -
StarTux