I’m having this most odd issue since I’ve upgraded to 11.0.
My network works fine in a fresh boot, but after some data has been transferred (had it drop on less than 10mb up to 300mb, and everything in between) it just drops dead, I can’t even ping my own router. I can only make it work with a reboot (/etc/init.d/network restart doesn’t cut it)
It’s most annoying when I try to run stuff like my cs1.6 server, ventrilo server, p2p programs or try to send large files over to other computers in the network
hwinfo identifies my sound card as Model: “Realtek RTL-8139/8139C/8139C+”
modprobe shows:
The real oddity is that it works flawlessly at first, I always hope “maybe this time it won’t drop” but it always does
I don’t really know what’s going on, I don’t know any reliable way of telling if the problem is on my laptop (Toshiba Satellite M70) or on my router (WBR-1310), so if anyone could give me some instructions on what to do to better identify the problem, I’d be grateful lol!
Are there interesting messages in dmesg when your connection drops? What happens to your link status?
sudo mii-tool eth0
I believe the M70 comes with a built-in intel wireless adapter. Is the wireless card associated to an access point? Maybe an access point using the same subnet?
Also to not pass the ‘obvious’ … have you checked or switched the utp cable and if maybe the switch(port) is having a problem?
I don’t think it’s something physically wrong with the cable, it works reliably when I boot the laptop on WinXP. I’m not really sure what you mean by switch(port), but the issue occurs on many applications using different ports, or changing the port on the same application.
as for dmesg, something interesting does come up:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0c 0005 c07f media 10.
eth0: Tx queue start entry 59802 dirty entry 59798.
eth0: Tx descriptor 0 is 0008a5ea.
eth0: Tx descriptor 1 is 0008a45f.
eth0: Tx descriptor 2 is 0008a5d6. (queue head)
eth0: Tx descriptor 3 is 0008a54a.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
and it repeats itself several times, with changing descriptors and queue heads (but I think that’s expected since many different packets timed out). The link is up, the same thing is shown with ethtool (don’t have mii-tool)
On to the wireless, iwconfig outputs:
ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:20662 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
So no access point, no conflict (at least that’s out of the list :))
Thanks for the responses!
ps. Oh and I also made a fresh* (imported my user from /etc/passwd) install of suse11, problem persists
This problem emerged after updating to 11.0, I tried to rollback to 10.3 but no success.
I thought about booting as a live CD and probe the problem using ssh to send files around the network (this ‘triggers’ the issue as good as having aMule up for a while, or a ventrilo server, etc. doing by ssh is faster).
Any thoughts of what should I look for if this succeeds?
have also openSUSE 11.0 installed and experience similar problems. After a while of inactivity on the net, the connection drops. I have read in an article on openSUSE about an internet connection timeout value, but it was not mentioned where this value is set. Maybe somebody knows it?
Disabling IPv6 did not help.
Need this laptop to be functional ASAP so I just ended up installing FreeBSD. So far seems to be working without problems.
I had the same problem with pre-installed ath0 drivers. Try to use madwifi drivers from the repo Index of /suse/11.1. After installing madwifi, don’t forget to select ath_pci in yast’s network setting. You can find more info here and here
