Recent kernel upgrade rendered my etho useless [ SOLVED ]

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

Hey guys,

I recently upgraded my kernel from 2.6.34 to 2.6.36-r5 and everything went smooth, or so I thought. After rebooting, I kept getting errors about my etho device not being found. I rechecked my kernel options for my NIC (RTL8111/8168 B) and as none of the options were compiled. I recompiled the kernel again, this time compiling the "r8169' driver into the kernel, but still no internet. Any ideas or suggestions are welcomed. Please let me know what you would like to see such as :

lspci -k , etc....
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

lspci -k and ifconfig -a would probably be the best right now.
_________________
Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world!

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

Ok I'm using my phone right now, so bare with me. I did the following and still complaints about
Hardware or drivers:

cd /etc/init.d
ln -s net.lo net.eth0
ln -s net.lo net.eth1

rc-update add net.eth0 default
rc-update add net.eth1 default

/etc/init.d/net.eth0 restart
/etc/init.d/net.eth1 restart

Still no go
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

I finally have some time to keep working on this issue. I'm currently chrooted into my box via sysresc....internet working fine via live cd. Here is more info:

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

That helps, but we really need to see the output of lspci -k and ifconfig -a in your kernel, not a livecd kernel. Can you save them to a flash drive and pastebin them from another machine?
_________________
Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world!

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

here is more info:

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

Sorry, this is the only pc i have right now.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

So get the data, save it to the hard drive, and pastebin it from the livecd.

The output of lspci -k and ifconfig -a, from a root shell in your environment in your kernel, would be very helpful right now.
_________________
Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world!

krinn · Watchman Joined: 02 May 2003 Posts: 7470

looks like a common error for me, but of course i might be wrong

reason: you have a firewire card/port... and kernel have an option to use network with firewire. So if you have a kernel where this option is set, the firewire can grab eth0, your network card will then goes to eth1, now easy, if you only configure eth0 like it was configure for the previous kernel : you'll endup with eth0 = firewire = configure to run like like the network card was configure before (same ip, same route...) + your network is now eth1 unconfigure

And udev keep who is who: on previous kernel udev set your network as eth0 and wrote that. But on newer kernel you've forget to set the driver for the network: so no realtek presence BUT udev see someone is also a network: for udev -> ok nobody is eth0, so let the firewire be eth0
Next to that udev wrote down on your new kernel boot that eth0 = the firewire, now that you rebuild your kernel with the network card option, it's too late, udev will keep eth0=firewire and so add eth1 for your network.

if it's that you have many options:
- easiest: disable network for firewire -> CONFIG_FIREWIRE_NET=n and remove the udev persistent file (see name lower). So on next boot udev will record your network as eth0
- remove the route from eth0 and add route to eth1
- blacklist net.eth0 so net.eth1 only will start
- wrote a valid eth1 entry
- or edit /etc/udev/70-persistent-net.rules and set eth0 for realtek and eth1 for the firewire
any of those will work

this is something you can't see in the livecd as the livecd might not handle firewire networking in its kernel.

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

@krinn

"f it's that you have many options:
- easiest: disable network for firewire -> CONFIG_FIREWIRE_NET=n and remove the udev persistent file (see name lower). So on next boot udev will record your network as eth0"

Is this the same as recompiling my kernel and removing the built in option i have for "firewire"?
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

I dont think i have "udev/70-persistent-net.rules" file.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

@TJ,

Here is the info you requested.

krinn · Watchman Joined: 02 May 2003 Posts: 7470

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

@krinn

here is the file:

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

@TJ,

I dont see the driver being used by the live cd:

krinn · Watchman Joined: 02 May 2003 Posts: 7470

krinn · Watchman Joined: 02 May 2003 Posts: 7470

did you check the config from your running kernel that doesn't work for the presence of the firewire network option ?

if your kernel source are in /usr/src/linux just check with

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

Krinn:
You may be right, I don't know what the right driver should be. (I'm not that good! :sob:) However, his lspci -k shows that the kernel isn't loading a driver for that card. So either that driver is wrong or he's not using the kernel he thinks he is.

Snakeo2: Try rebuilding your kernel with the network drivers as modules. Then we can use lsmod as a debug tool, and we can make sure your running kernel matches your .config.
_________________
Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world!

TJNII · l33t Joined: 09 Nov 2003 Posts: 637 Location: for(;;);

Also make sure you are not running lspci inside the chroot.
_________________
Maintaining documentation on upgrades is apparently not within the power of Gentoo
Beware when you emerge -u world!

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

@krinn,

like so:

snakeo2 · Veteran Joined: 01 Jan 2006 Posts: 1237

Ok, went ahead and recompiled kernel, this time adding "r8169" as module and it did the trick.