Bringing lo up...

dhUmra · n00b Joined: 05 Feb 2004 Posts: 5

I'm running into an odd problem. I had Gentoo up and running just fine. Kernel 2.4.22 (gentoo-sources, just emerged today so whatever that kernel would have been) and I had XFce up and running perfectly. Installed Enemy Territory (a game) and that worked fine also but when I exited my system would hang for just a little bit everytime I typed anything in with the keyboard. I rebooted and now my system hangs on Bringing lo up...

I searched and another person had a similar problem with lo (whatever it is) and nobody responded. I don't know how to disable lo or what it is or how to get around it or anything. Any help would be great.

turtlendog · Posted: Thu Feb 05, 2004 7:51 am Post subject: lo == loopback network device

lo is your loopback network interface. It's required for lots of things. Something must have changed in your network config.

Maybe you can find out what's going on by changing these lines so that stderr is not discarded. Then you might see a message that tells you what's going on.

dhUmra · n00b Joined: 05 Feb 2004 Posts: 5

The problem is that I don't know how to get past it because it hangs my computer. That is when my computer is booting up. Should I boot with LiveCD and work from there?

krusty_ar · Posted: Thu Feb 05, 2004 12:38 pm Post subject:

I don't know if I understand your quetion correctly, but is this the first time that you reboot since updating your kernel?

I so, you probably missconfigured something there, you should allways make a grub/lilo entry for your previous kernel, in case something goes wrong.

Anyway, if that's the case, booting from the LiveCD and recompiling your kernel with proper settings should solve your problem.
_________________
I am Beta, don't expect correct behaviour from me.
Take part of the adopt an unaswered post initiative

deepthought · Posted: Thu Feb 05, 2004 1:20 pm Post subject:

This is odd. Use the livecd to boot, chroot into your system and try to remove lo from boot services with rc-update. Then reboot. Note that this is *not* the solution to your problem, I just want your box to boot so that we can figure things out.

BTW, it would be nice if you could post /var/log/everything/current (the last 50 lines or so).

Regards,
Alexander
_________________
Out of loyalty to its disregarded comrades, this message feels free to ignore the reader.
Registered Linux User #317705

dhUmra · n00b Joined: 05 Feb 2004 Posts: 5

dhUmra · n00b Joined: 05 Feb 2004 Posts: 5

Outstanding. I'm in XFce right now but without net.lo so, as has been said, this is only a temporary solution. I did a

rc-update add net.lo default

and got some weird messages on the reboot.

I first removed all of my modules in /etc/modules.autoload.d/kernel-2.4 and THEN I readded net.lo to the bootup, thats when I got the weird messages : which I did not backup because I am a n00b and forgot so it is now overwritten.

This is going to sound newbish but...I don't have a /var/log/everything/current, my log directory contains:

lastlog - bunch of @ signs
messages
wtmp
XFree86.0.log
emerge.log
XFree86.0.log.old

and two empty directories:
cups
news

I'm going to go try to put net.lo back in and reboot. I will edit this post if all goes well.

OK, it works great again. Thank you all - I will now describe what I did to resolve it, if, in fact, it did not do it itself.

chrooted into my system after booting in livecd. I then removed /etc/modules.autoload (which prolly didn't do anything but it was bugging me). I then edited /etc/modules.autoload.d/kernel-2.4 and # all of the modules. I then rc-update del net.lo. After that I rebooted and it worked with a lot of errors. I edited /etc/fstab and took out the mounting of the vfat partition (didn't work anyways) and insmod 8139too and then dhcpcd eth0 to see if my internet worked. It did and I then uncommented 8139too in the modules autoload and rebooted. I tried to start X but it died because I also had my USB mouse modules commented and it couldn't initiate a mouse. I RECOMMENTED everything and rc-update add net.lo default and got some weird errors because 8139too module was commented. Again removed net.lo from the boot runlevel and put all the modules back in. Started up, posted here, and then decided to try it again and net.lo came up fine. Confusing but it worked and I probably wasted a lot of time in uncommenting and rebooting and commenting and rebooting. Just thought I would let anybody with this same problem know what happened to me.

Thanks to all of you who helped!

turtlendog · Posted: Thu Feb 05, 2004 7:41 pm Post subject: logs

Here's a tip if you're running sysklogd, add the following to your /etc/syslog.conf

dhUmra · n00b Joined: 05 Feb 2004 Posts: 5

Now my system is hanging on Setting domainname! UG. It worked just fine last boot and now another problem arises. I have restarted a few times and now I must go BACK into livecd and do nothing but remove domainname and readd it.

deepthought · Posted: Fri Feb 06, 2004 12:14 pm Post subject:

The "everything" logfile is already there. Because every syslog developer decided to randomly choose a funny name for the "everything" logfile, it's a complete mess to guess the correct one. For you, it is /var/log/messages which -- as you stated above -- is already there.

Regards,
Alexander
_________________
Out of loyalty to its disregarded comrades, this message feels free to ignore the reader.
Registered Linux User #317705