Hello.

Been happily using Ubuntu (and other dists previously) on a dual booting box with Win XP Pro for years.

Then a couple of weekends ago I try booting into my Ubuntu dist and found I had no internet connection initially and upon further investigation no no network connection at all (no light on my router).

So I restart machine and boot into Windows XP router light is on and machine is joined onto the network and internet is fine. Same hardware.... same network..............

I have tried a new install of Ubuntu..... problem still exists. I just can't understand what is stopping the network card from working all of sudden in my Ubuntu boot?!

I have not changed anything (and even if I had it is back to a clean install!!). Anyone have a similar problem?! Surely not IRQ conflicts? If so.... why now??

Your help much appreciated.

I have a similar issue with my Sony Vaio. Been dual booting between XP and Linux for years without problems. Then one day a few months ago, was unable to get network connection in Linux. Did the usual troubleshooting, reconfiguring, reinstalling, but just could not get Linux to connect.
However, at some point, I did a cold boot into Linux and got network working. I still do not know why it only works when I cold boot into Linux. I suspect it's probably hardware related.
Sorry I can't be of more help.

One of the many ways Micro$oft displays their "corporate culture" to the world is to have a setting on some devices (I don't know specifically which) such that when windows shuts down, the device is locked. Boot another OS, and the device refuses to respond.

You should boot xp, go into the control panel, and search for internet hardware settings which may be locking the device until next windows boot.

OK...yeah...it is something along these lines....although not pin pointed it yet. I have rolled back an automatic driver update for my network card from our friends at Microsoft in my Windows XP boot (yep that is right!!!).....

Rebooted back into Ubuntu.....the router light which is connected to this card then stays live (which it hasn't been doing once out of Windows) and boots into Linux no problems!!

The new driver appears to work OK in Windows XP but breaks the card for Ubuntu.... bizarre I know.... All I can think initially is that XP puts it into some kind of power save / shutdown state at XP shutdown....... and quite happily wakes it when rebooted back into XP.....

But it doesn't happen in Ubuntu... so rolling back this driver stops this happening at shutdown.... and bingo.... card works for both OS as before.

Hello everybody

Very strange indeed. What kind of networkcard do you use? Wireless? Wired?

Bye

Koen Plessers

Wired.... Realtek RTL8139... although the Microsoft driver update mentioned earlier names it entirely differently (and different manufacturer).

My laptop has a Realtek RTL8139/810x Family NIC. Confirmed the driver that was installed was dated 8/20/07. Rolled back the driver, date changed to 7/13/07. Did warm boot from XP to Linux, but eth0 would not start.
Switched back to XP and installed original driver that came with my laptop, driver dated 11/12/03.
Rebooted back to Linux and eth0 started up right away.

Nice to know I am not alone..... and my sanity is intact.

I have heard of these problems before. Windows can, and does do, strange things to some hardware. Sometimes it leaves it in an "unusual" configuration. Who knows why? (No, there's really no need to answer this, and it's probably not intentional (I hope), just laziness, and ms people making assumptions about how people use their hardware). When you do a "soft" reboot, the hardware remains in an unusual (soft) configuration (Eg. some registers or flags are set strangely), and it will not then work with linux.

For those of you that dual-boot: If you encounter problems with things that used to work with linux, and now suddenly do not (I've never had this happen with linux, but quite often when I used windows), you should boot to your boot loader (grub, lilo, whatever) from a completely dead computer. This means disconnecting it from its power supply (unplug from mains, or disconnect battery from laptop) for 30S or so. That way the hardware can reset itself to its defaults when the power is re-applied and all will be well.

I've found that if you don't fully power down your system DHCP seems to use the last IP's rather than retrieving new ones. You may not have noticed unless you've inserted a router with NAT between you modem and the PC.

try unplugging and replugging card to start with, especially if its been assembled for some time...then i would use a clean boot each time to linux, common problems seem to be happening everywhere, but alas i have a friend who could only get online with linux, not with windoze, he was loving it but not his game mad son....rofl

Hello everybody,
I registered to this forum specifically to post the SOLUTION to this problem that also made me question my sanity. So other desperate Linux users that find this post through google (as I did) can save themselves some trouble.

Boot on windows.
Go to the device manager and get into "properties" for your network card.
In the "Advanced Options" tab select:

Wake-on-lan after shutdown | enable

Reboot into linux. Your network card should be working.

dresb,
Thanks for posting your solution, which is easier than mine!
Unfortunately, I do not have the hardware, or windows, to test it with, but I'm sure it'll help someone else.
And welcome to LQ!

Features like wake on LAN may also be configurable in your BIOS. It is on mine.

Hi just registerd to drop this 'Thank you note' to dresb.

I was also about to question my sanity and could not figure out, what was causing this weird problem as it was intially working.

This was the first time I was looking into Linux but without internet connection it's pretty useless. Luckily found this post through google and this simple change in the windows device config solved the problem!

Thanks again for taking the time to post the SOLUTION.
Now I can really enjoy looking deeper into Linux capabilities :-)