Weblog entry #14 for Grimnar

Reboot from hell.
Posted by Grimnar on Wed 15 Nov 2006 at 14:17
Tags: none.
Today I was doing this" rel="nofollow">http://www.debian-administration.org/users/Grimnar/weblog/13">this; and came to a point where I was suppose to reboot. Did that and now none of my network devices works? what the hell happend and how do I fix them?

Only get this messages.

eth0: error fetching interface information: Device not found

This happens to all my devices (2). The used to work flawlessy and no troubles at all.

How can I remedy this without re-install? Since the server is my gateway im kinda in a rush after a bad day at work.

Luckily I live in a appartment complex and thus still have some kind of wlan to "borrow" in the mean time.

 

Comments on this Entry

Posted by Nilshar (88.191.xx.xx) on Wed 15 Nov 2006 at 16:22
[ Send Message | View Weblogs ]
You changed the kernel ?

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Wed 15 Nov 2006 at 17:05
[ Send Message | View Weblogs ]
nope. Nothing has changed.

[ Parent | Reply to this comment ]

Posted by dkg (216.254.xx.xx) on Wed 15 Nov 2006 at 18:34
[ Send Message | View dkg's Scratchpad | View Weblogs ]
You don't mention what flavor of debian you have installed on this machine, or what model of NIC are in the machine. Are you running udev or hotplug? What version is your kernel? are you sure the appropriate modules for your hardware are loaded in your kernel?

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Wed 15 Nov 2006 at 18:48
[ Send Message | View Weblogs ]
Sorry about that.

Im running testing, (2.6.12-1-k7) and having 2x realtek 8139too cards.
And you are correct, I just installed udev when I suddenly got these problems.

Now, I've been doing some testing on my own.
I added alias 8138too eth0 in /etc/modutils and the same in /etc/modutils/aliases
Then I removed udev, and now it all works. But what part of my process that actually worked, remains to be untold at this moment.

[ Parent | Reply to this comment ]

Posted by dkg (216.254.xx.xx) on Wed 15 Nov 2006 at 19:06
[ Send Message | View dkg's Scratchpad | View Weblogs ]
I recommend using a more up-to-date kernel than 2.6.12, especially if you are using the latest udev in etch. Is the machine up-to-date otherwise?

i don't understand your last paragraph either: /etc/modutils is a directory, not a file, so you can't add alias 8138too eth0 to it, afaik. Is that a typo?

/etc/modutils is part of the old (deprecated) modutils module-handling infrastructure. As the package description says:

These utilities are intended to make a Linux modular 2.2 or 2.4 kernel manageable for all users, administrators and distribution maintainers. For 2.6 kernels, you should use the module-init-tools package.
Configuration files for module-init-tools are stored in /etc/modprobe.d. But for a setup as straightforward as what you've described, i'd recommend not tweaking those files at all. Move to a modern kernel (maybe install linux-image-k7 to track the latest kernel), re-install udev, and reboot. udev in its current state in etch does seem to have gotten many of the bugs ironed out. I find it pretty handy.

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Wed 15 Nov 2006 at 19:26
[ Send Message | View Weblogs ]
Nevermind my typos! Everything works!:D

Now back to buisness. Since my last time updating the kernel, some stuff has changed I see. Its now linux-image (ethc) and the old kernel-image for Sarge. This
never occured to me, so no wonder I did not find any new kernels then.
So, I will go on with installing a new kernel.


Going to install: linux-image-2.6.17-2-k7.

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Wed 15 Nov 2006 at 19:33
[ Send Message | View Weblogs ]
Okay, now I got my 2.6.2.17 up and working, and ps aux | grep udev shows some positive stuff. Network is also working. I guess its time to continue on this. Hopefully someone will continue to help me out. Thanks for the help guys!:)

[ Parent | Reply to this comment ]

Posted by dkg (216.254.xx.xx) on Wed 15 Nov 2006 at 19:58
[ Send Message | View dkg's Scratchpad | View Weblogs ]
I really do recommend installing linux-image-k7 as well. It's a metapackage that tracks the latest kernel available for your platform. It takes up almost no room on the system, but it means that apt-get dist-upgrade will recommend a new kernel to install when it's available.

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Wed 15 Nov 2006 at 20:03
[ Send Message | View Weblogs ]
Sorry, forgot to mention that. That's installed. :)

[ Parent | Reply to this comment ]

Posted by Anonymous (59.178.xx.xx) on Thu 16 Nov 2006 at 18:18
Howdy,

I was trying to explain your problem and offer a solution when the goose-stepping, jackbooted purity filter kicked in and stopped me from posting. Anyway, it's now an article at: http://www.debian-administration.org/articles/463

[ Parent | Reply to this comment ]

Posted by Grimnar (85.221.xx.xx) on Thu 16 Nov 2006 at 23:30
[ Send Message | View Weblogs ]
Thanks alot, I will look into it. Seemed a bit extreme for me, but I will try it.

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search