Re: eth1: Transmit timed out, status 0000, PHY status 0000 (fwd)
Hi Phil, I've forwarded it for you, however you likely didn't realize hat lkml is an "open" mailing list, ie: you don't need to be a subscriber to post. This is so that non-members can file bug reports, and send spam, etc.. ;o) Take care. -- Mike A. Harris - Linux advocate - Free Software advocate This message is copyright 2001, all rights reserved. Views expressed are my own, not necessarily shared by my employer. -- -- Forwarded message -- Date: Wed, 17 Jan 2001 10:46:54 +0100 From: Ph. Marek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Content-Type: text/plain; charset="us-ascii" Subject: Re: eth1: Transmit timed out, status , PHY status Hi Mike! I'm not on lkml but I follow the discussions from time to time and saw your mail. (as I'm not subscribed, please forward this to lkml) I've had the same problem using DLink 530 using 10baseT. DOS-diagnostic said "No connection". Even trying to say modprobe tulip options=1 (use 10baseT) didn't work. Then I got a crossed 10base2 cable and - IT WORKED (for me) without any problems, though I said option=4 (10base2, full duplex). Hope this helps! Regards, Phil "A Firewall is really much like a sophisticated traffic cop; it detects and stops unauthorized or suspicious movement in or out of the network. But security is more than a Firewall; it's a process. You can't just put in a Firewall and think you're secure." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: eth1: Transmit timed out, status 0000, PHY status 0000
On Tue, 16 Jan 2001, Urban Widmark wrote: >Date: Tue, 16 Jan 2001 23:59:33 +0100 (CET) >From: Urban Widmark <[EMAIL PROTECTED]> >To: richard.morgan9 <[EMAIL PROTECTED]> >Cc: Mike A. Harris <[EMAIL PROTECTED]>, > Linux Kernel mailing list <[EMAIL PROTECTED]> >Content-Type: TEXT/PLAIN; charset=US-ASCII >Subject: Re: eth1: Transmit timed out, status , PHY status > >On Tue, 16 Jan 2001, richard.morgan9 wrote: > >> I have the same problem as Urban with a recent DLink 530tx >> (rhine2). Pulling the power cable from my atx psu (while the >> computer was "off") fixed the card, until my next reboot from >> win98. > >I'm not the one with a problem but maybe it has something to do with win98 >and/or the driver used there. I intend to test this myself eventually and >see if I can do something based on Donald Beckers suggestions on eeprom. > >Unless someone else feels like playing with this ... anyone? > >Does everyone seeing this have a Rhine-II, pci id 1106:3065, and not the >older chip found in dfe530tx with pci id 1106:3043? 00:12.0 Ethernet controller: VIA Technologies, Inc.: Unknown device 3065 (rev 42) Subsystem: D-Link System Inc: Unknown device 1400 Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at e800 Memory at e700 (32-bit, non-prefetchable) Expansion ROM at e600 [disabled] Capabilities: [40] Power Management version 2 00:13.0 Ethernet controller: Winbond Electronics Corp W89C940 Flags: medium devsel, IRQ 12 I/O ports at ec00 And I do not have drivers for the dlink card in win98. The 2 cards are in my workstation, one goes to my firewall @ 10Mbit and the other to my build/devel machine at 100mbit which 98 doesn't get to see. It is sure interested in the card at boot time though... EVERY time... ;o( -- Mike A. Harris - Linux advocate - Free Software advocate This message is copyright 2001, all rights reserved. Views expressed are my own, not necessarily shared by my employer. -- Windows 95(n) - 32-bit extensions and graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand 1 bit of competition. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: eth1: Transmit timed out, status 0000, PHY status 0000
On Tue, 16 Jan 2001, richard.morgan9 wrote: > I have the same problem as Urban with a recent DLink 530tx > (rhine2). Pulling the power cable from my atx psu (while the > computer was "off") fixed the card, until my next reboot from > win98. I'm not the one with a problem but maybe it has something to do with win98 and/or the driver used there. I intend to test this myself eventually and see if I can do something based on Donald Beckers suggestions on eeprom. Unless someone else feels like playing with this ... anyone? Does everyone seeing this have a Rhine-II, pci id 1106:3065, and not the older chip found in dfe530tx with pci id 1106:3043? /Urban - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: eth1: Transmit timed out, status 0000, PHY status 0000
>> On Sun, 14 Jan 2001, Urban Widmark wrote: >> >> >> eth1: Transmit timed out, status , PHY status , >> >> resetting... >> >[snip] >> >> Keeps going nonstop until I ifdown eth1. >> >> >> >> Card worked fine 2 days ago... >> > >> >So what did you change? >> >> Nothing. >> >> >Has the machine been up since then? >> >> No. I rebooted to W98 a few times. W98 doesn't have a driver >> installed for that card though - and wont. >> >> >> >> >Someone else with the same symptoms (in 2.4) >> >http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0027.html >> > >> >Becker's reply >> >http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0032.html >> > >> >"Try unplugging the system and doing a really cold boot. A soft-off does >> > not reset the chip. >> >> Tried that too.. didn't work. I switched PCI slots and whatnot >> though and it works again.. >> > >> > If this solves the problem, we will have to add code to re-load the >> > EEPROM info into the chip." >> >> If the problem recurs I will try to test it out more and report >> to the list. >> >> FWIW it is a DLink DFE 530TX. >> snip I have the same problem as Urban with a recent DLink 530tx (rhine2). Pulling the power cable from my atx psu (while the computer was "off") fixed the card, until my next reboot from win98. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: eth1: Transmit timed out, status 0000, PHY status 0000
On Sun, 14 Jan 2001, Urban Widmark wrote: >> eth1: Transmit timed out, status 0000, PHY status , >> resetting... >[snip] >> Keeps going nonstop until I ifdown eth1. >> >> Card worked fine 2 days ago... > >So what did you change? Nothing. >Has the machine been up since then? No. I rebooted to W98 a few times. W98 doesn't have a driver installed for that card though - and wont. >Someone else with the same symptoms (in 2.4) >http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0027.html > >Becker's reply >http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0032.html > >"Try unplugging the system and doing a really cold boot. A soft-off does > not reset the chip. Tried that too.. didn't work. I switched PCI slots and whatnot though and it works again.. > If this solves the problem, we will have to add code to re-load the > EEPROM info into the chip." If the problem recurs I will try to test it out more and report to the list. FWIW it is a DLink DFE 530TX. Thanks for the reply. -- Mike A. Harris - Linux advocate - Free Software advocate This message is copyright 2001, all rights reserved. Views expressed are my own, not necessarily shared by my employer. -- #[Mike A. Harris bash tip #1 - separate history files per virtual console] # Put the following at the bottom of your ~/.bash_profile [ ! -d ~/.bash_histdir ] && mkdir ~/.bash_histdir tty |grep "^/dev/tty[0-9]" >& /dev/null && \ export HISTFILE=~/.bash_histdir/.$(tty | sed -e 's/.*\///') - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: eth1: Transmit timed out, status 0000, PHY status 0000
On Sun, 14 Jan 2001, Mike A. Harris wrote: > Becker's latest via-rhine driver ontop 2.2.18.. > > ... > eth1: Transmit timed out, status , PHY status , > resetting... [snip] > Keeps going nonstop until I ifdown eth1. > > Card worked fine 2 days ago... So what did you change? Has the machine been up since then? Someone else with the same symptoms (in 2.4) http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0027.html Becker's reply http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0032.html "Try unplugging the system and doing a really cold boot. A soft-off does not reset the chip. If this solves the problem, we will have to add code to re-load the EEPROM info into the chip." There is no further reply in that thread. /Urban - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
eth1: Transmit timed out, status 0000, PHY status 0000
What might be a reason I'm seeing this? Becker's latest via-rhine driver ontop 2.2.18.. ... eth1: Transmit timed out, status , PHY status , resetting... eth1: Transmit timed out, status , PHY status , resetting... eth1: Transmit timed out, status , PHY status , resetting... eth1: Transmit timed out, status , PHY status , resetting... eth1: Transmit timed out, status , PHY status , resetting... eth1: Transmit timed out, status , PHY status , resetting... Keeps going nonstop until I ifdown eth1. Card worked fine 2 days ago... -- Mike A. Harris - Linux advocate - Free Software advocate This message is copyright 2001, all rights reserved. Views expressed are my own, not necessarily shared by my employer. -- Windows 95(n) - 32-bit extensions and graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand 1 bit of competition. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
