SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
For some strange reason, a bunch of services aren't starting up anymore at boot! All I did was change my BIOS settings for apm (which shouldn't have any effect on things like dhcp client) and I disabled the loading of the APM module in rc.modules. I don't understand what is going on. Gnome hangs on the splash screen when I try to start it, no matter the runlevel. I am posting this by way of starting dhcpcd manually and using lynx in console! Can anyone help me figure out what went wrong?
I managed to get fsck to run automatically, and it fixed about a dozen different problems, corrupted inodes, etc. I tried rebooting after, and now I get a huge list of module errors, all the same one, telling me that modprobe can't find some module (apparently one that got fscked up).
And ... X just started after all, and gnome to boot, after about 60 seconds of being idle ... anyone care to explain?
Edit: dhcpcd STILL isn't loading at boot, and now all my gnome apps are crashing ad lib.
Last edited by stevenhasty; 08-16-2003 at 12:43 PM.
Apparently this seems like a serious file-system error and I cannot help with that.
But I want to tell you two situations I encountered starting X with Gnome in slackware 9.0:
1. Login in console mode, start midnight-commander (mc), work for a while in his own shell (CTRL+O) and at command line, type "startx". X will start, but gnome will stay for ever at splash screen. If you kill X (CTRL+ALT+BACKSPACE) and then exit from mc's shell, and then startx again, everything will be okay.
2. Once I had troubles starting gnome when the network config file were a mess. At that time I was learning about DNS client configuration, and I was playing with /etc/hosts and /etc/resolv.conf. After that, my box was unable to use "localhost" as 127.0.0.1 I was unaware at that time, and when I started x, gnome failed to start in the same way (frozen screen).