hi all, i have SuSE6.4 running on my machine, which is connected to my employer's network via an ethernet card (intel etherexpress pro 10+). most of the time, things are running fine. every now and then, however, the ethernet driver (eepro) gives the following message: eth0: XMT status: 0xffff80e0 (the actual number differs.) when this happens, i lose my connection. so far, the only way i've found to get it back again is to reboot. but that can be a problem, because i often have a network drive mounted (via samba), which (apparently) cannot be unmounted when the connection is down. result: i have to press the reset button, which is something i do not like doing, since i always tell my friends (most of whom think i'm nuts running linux anyway... :-) that you can usually recover nicely when something crashes, unlike some operating system we know... does anybody know what happens when the driver spits out this message? and does anybody know a way to get the connection back again without rebooting? i guess it would be enough if i could shut down eth0 manually and then start it again. any tips? TIA joost -- Joost Kremers, M.A. University of Nijmegen Department of Languages and Cultures of the Middle-East PO Box 9103 6500 HD Nijmegen tel: 024-3612996 fax: 024-3611972 __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Hi joost, have you tried: /sbin/init.d/networt restart ? or: cd /sbin/init.d/ ; route stop ; network restart ; route start I used to have an old, buggy BNC 10Mbit card, that would also stop working just out of the blue sky. I made a ping script, that executed either the first line (85%) or the second line (15%), when the link was down. if the first line works, the second one should go through as well, though... hope this helps. best regards, Alex P.S. Has anybody looked further into my question on "Promise ultra66" ? On Thu, 1 Mar 2001, Joost Kremers wrote:
hi all,
i have SuSE6.4 running on my machine, which is connected to my employer's network via an ethernet card (intel etherexpress pro 10+). most of the time, things are running fine. every now and then, however, the ethernet driver (eepro) gives the following message:
eth0: XMT status: 0xffff80e0
(the actual number differs.) when this happens, i lose my connection. so far, the only way i've found to get it back again is to reboot. but that can be a problem, because i often have a network drive mounted (via samba), which (apparently) cannot be unmounted when the connection is down. result: i have to press the reset button, which is something i do not like doing, since i always tell my friends (most of whom think i'm nuts running linux anyway... :-) that you can usually recover nicely when something crashes, unlike some operating system we know...
does anybody know what happens when the driver spits out this message? and does anybody know a way to get the connection back again without rebooting? i guess it would be enough if i could shut down eth0 manually and then start it again.
any tips? TIA
joost
-- Joost Kremers, M.A.
University of Nijmegen Department of Languages and Cultures of the Middle-East
PO Box 9103 6500 HD Nijmegen tel: 024-3612996 fax: 024-3611972
__________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
-- 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
On Thursday 01 March 2001 04:52, Joost Kremers wrote:
hi all,
i have SuSE6.4 running on my machine, which is connected to my employer's network via an ethernet card (intel etherexpress pro 10+). most of the time, things are running fine. every now and then, however, the ethernet driver (eepro) gives the following message:
eth0: XMT status: 0xffff80e0
(the actual number differs.) when this happens, i lose my connection. so far, the only way i've found to get it back again is to reboot. but that can be a problem, because i often have a network drive mounted (via samba), which (apparently) cannot be unmounted when the connection is down. result: i have to press the reset button, which is something i do not like doing, since i always tell my friends (most of whom think i'm nuts running linux anyway... :-) that you can usually recover nicely when something crashes, unlike some operating system we know...
does anybody know what happens when the driver spits out this message? and does anybody know a way to get the connection back again without rebooting? i guess it would be enough if i could shut down eth0 manually and then start it again.
any tips? TIA
joost
Joost, I don't know what the error message means, but I do know I have problems with SMB connections which are left hanging. If I shut down my NT box while I have a drive mounted on a linux box using mount -t smbfs ..., I cannot get the Linux box to get past releasing the SMB connection, and thus have to use the on/off control. This is a very longstanding issue with smbmount. I've never called it to the attention of the SaMBa folks, but you ask a VERY good question. Steve
participants (3)
-
Joost Kremers -
Robert Stragies -
Steven T. Hatton