Re: eth0 (Realtek 8139) suddenly not working
Andrew Vaughan <[EMAIL PROTECTED]> writes: > Hi > On Sunday 17 September 2006 23:19, Peter Thomassen wrote: >> Hi, >> >> I'm still introducing a friend of mine to Linux by phone. >> >> Yesterday and the days before, his Realtek 8139 NCI worked out of the box >> using DHCP. Today, no IP is received over DHCP; instead, the boot script >> does several tries after different intervals and finally gives up. >> > [snip] >> After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd >> it; then ifdown eth0, ifup eth0. No success. >> >> Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. I >> don't know what to do -- do you? >> >> Thanks, >> Peter > > I've had something similar happen with my desktop. > > Similar hardware, realtek 8139 PCI ethernet card. > > If I hibernate the computer from windows (either 2000 or vista), windows > somehow disables the NIC. The router no longer shows a connection. > > Linux doesn't manage to enable the NIC during bootup, (the moduels are > loaded, it thinks the interface is up, but the router still shows no > connection) and I need to boot windows to fix things. After wasting many hours over the past several years trying to get a Netgear card with the Realtek chip running reliably in various machines running various releases of Debian, I finally got smart, took a pair of pliers, and physically removed the PCI connector, by bending and twisting. A hammer and anvil repeatedly applied over the surface of the card would have been quicker and just as effective, and likely would have been more satisfying. My conclusion is that life is too short to waste it messing around with Netgear apparatus. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Hi On Sunday 17 September 2006 23:19, Peter Thomassen wrote: > Hi, > > I'm still introducing a friend of mine to Linux by phone. > > Yesterday and the days before, his Realtek 8139 NCI worked out of the box > using DHCP. Today, no IP is received over DHCP; instead, the boot script > does several tries after different intervals and finally gives up. > [snip] > After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd > it; then ifdown eth0, ifup eth0. No success. > > Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. I > don't know what to do -- do you? > > Thanks, > Peter I've had something similar happen with my desktop. Similar hardware, realtek 8139 PCI ethernet card. If I hibernate the computer from windows (either 2000 or vista), windows somehow disables the NIC. The router no longer shows a connection. Linux doesn't manage to enable the NIC during bootup, (the moduels are loaded, it thinks the interface is up, but the router still shows no connection) and I need to boot windows to fix things. Andrew V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
On Mon, 2006-09-18 at 22:49 +0200, Peter Thomassen wrote: > > I ask because I have a sound card that disappears if I do this. > > It will only work if I shut down and then boot into Linux. Blast from the past! This brings back memories from the good old BeOS days when you *had* to boot into Windows first and then warm reboot to get some hardware to work... Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
On Mon, Sep 18, 2006 at 10:49:11PM +0200, Peter Thomassen wrote: > George Borisov schrieb am Montag, 18. September 2006 15:36: > > Did it by any chance stop working after you rebooted into Debian > > from Windows? > > > > I ask because I have a sound card that disappears if I do this. > > It will only work if I shut down and then boot into Linux. > > Hey, thanks, that did the trick! Strange issue ... seems to be a bug, but a > bug of what? BIOS, Windows? Linux? some register isn't getting reset in a warm reboot? hard to say whether that's a bug or a feature, but it does point out the reason for tech support telling people to actually shutdown for 30 seconds or so and then restarting (this assumes you use one of those OSes that requires regular rebooting :) A signature.asc Description: Digital signature
Re: eth0 (Realtek 8139) suddenly not working
George Borisov schrieb am Montag, 18. September 2006 15:36: > Did it by any chance stop working after you rebooted into Debian > from Windows? > > I ask because I have a sound card that disappears if I do this. > It will only work if I shut down and then boot into Linux. Hey, thanks, that did the trick! Strange issue ... seems to be a bug, but a bug of what? BIOS, Windows? Linux? Thanks again, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Peter Thomassen wrote: Bill Smith schrieb am Montag, 18. September 2006 18:09: worth replacing the card, preferably with a 3com or intel based one. That's not that easy as it's a notebook ... Can you turn it off in the bios and try a slot in one? -- Bill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Bill Smith schrieb am Montag, 18. September 2006 18:09: > worth replacing the card, preferably with a 3com or intel based one. That's not that easy as it's a notebook ... Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
steef wrote: Peter Thomassen wrote: Hi, I'm still introducing a friend of mine to Linux by phone. Yesterday and the days before, his Realtek 8139 NCI worked out of the box using DHCP. Today, no IP is received over DHCP; instead, the boot script does several tries after different intervals and finally gives up. I googled around and found a hint that the Firewire interface can occupy eth0, and indeed, eth1 was present (which I assumed to be the NIC), but replacing eth0 by eth1 in /etc/network/interfaces didn't work. Also undoing that change, blacklisting eth1394 in /etc/modules.d/blacklist and rebooting didn't solve it. After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd it; then ifdown eth0, ifup eth0. No success. Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. I don't know what to do -- do you? Thanks, Peter maybe a stupid remark, but could this be a hardware-fault of the realtek ethernetcard? i remember that in my machines two gave up for unclear reasons. Could well be the problem, I too have had realteks just stop working, worth replacing the card, preferably with a 3com or intel based one. -- Bill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Peter Thomassen wrote: > > I don't think so because on the same system, Windows XP is installed where > the card can be used without a problem (with DCHP, too). Did it by any chance stop working after you rebooted into Debian from Windows? I ask because I have a sound card that disappears if I do this. It will only work if I shut down and then boot into Linux. Hope this helps, -- George Borisov DXSolutions Ltd signature.asc Description: OpenPGP digital signature
Re: eth0 (Realtek 8139) suddenly not working
steef schrieb am Montag, 18. September 2006 11:35: > maybe a stupid remark, but could this be a hardware-fault of the realtek > ethernetcard? i remember that in my machines two gave up for unclear > reasons. I don't think so because on the same system, Windows XP is installed where the card can be used without a problem (with DCHP, too). Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Peter Thomassen wrote: Hi, I'm still introducing a friend of mine to Linux by phone. Yesterday and the days before, his Realtek 8139 NCI worked out of the box using DHCP. Today, no IP is received over DHCP; instead, the boot script does several tries after different intervals and finally gives up. I googled around and found a hint that the Firewire interface can occupy eth0, and indeed, eth1 was present (which I assumed to be the NIC), but replacing eth0 by eth1 in /etc/network/interfaces didn't work. Also undoing that change, blacklisting eth1394 in /etc/modules.d/blacklist and rebooting didn't solve it. After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd it; then ifdown eth0, ifup eth0. No success. Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. I don't know what to do -- do you? Thanks, Peter maybe a stupid remark, but could this be a hardware-fault of the realtek ethernetcard? i remember that in my machines two gave up for unclear reasons. regards, steef groningen, holland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
Derek schrieb am Sonntag, 17. September 2006 21:21: > I had this problem on my powermac, And it worked before, too? Maybe, one should file a bug on this ... > I ended up just compiling my own kernel > without any of the eth1394 stuff. Hmm, this will be difficult to do since currently, the kernel sources aren't installed and we have to do that without an internet connection. To do it in one run: Which dependencies are necessary for this? And, of course: Are there any other chances to make networking work again? Thanks, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 (Realtek 8139) suddenly not working
I had this problem on my powermac,I ended up just compiling my own kernel without any of the eth1394 stuff.On 9/17/06, Peter Thomassen < [EMAIL PROTECTED]> wrote:Hi,I'm still introducing a friend of mine to Linux by phone. Yesterday and the days before, his Realtek 8139 NCI worked out of the boxusing DHCP. Today, no IP is received over DHCP; instead, the boot scriptdoes several tries after different intervals and finally gives up. I googled around and found a hint that the Firewire interface can occupyeth0, and indeed, eth1 was present (which I assumed to be the NIC), butreplacing eth0 by eth1 in /etc/network/interfaces didn't work. Also undoing that change, blacklisting eth1394 in /etc/modules.d/blacklist and rebootingdidn't solve it.After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd it;then ifdown eth0, ifup eth0. No success. Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. Idon't know what to do -- do you?Thanks,Peter--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
eth0 (Realtek 8139) suddenly not working
Hi, I'm still introducing a friend of mine to Linux by phone. Yesterday and the days before, his Realtek 8139 NCI worked out of the box using DHCP. Today, no IP is received over DHCP; instead, the boot script does several tries after different intervals and finally gives up. I googled around and found a hint that the Firewire interface can occupy eth0, and indeed, eth1 was present (which I assumed to be the NIC), but replacing eth0 by eth1 in /etc/network/interfaces didn't work. Also undoing that change, blacklisting eth1394 in /etc/modules.d/blacklist and rebooting didn't solve it. After the reboot, I noticed that 8139too wasn't loaded, so we modprobe'd it; then ifdown eth0, ifup eth0. No success. Maybe it's useful to know that dmesg says that eth0 is a Realtek 8139. I don't know what to do -- do you? Thanks, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
