Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Please help I don't know what to do. I have recompiled the kernel from fresh sources (2.6.1). The computer was booting up previously. The last time i shut down there was an error closing gdm, but everything else shutdown fine.
Anybody have any ideas? An explanation of how these kernel oops might happen would be awesome.
My guess is that the kernel oops happens during the hwclock call of the clock init.d script. Anyway to stop this?
Update: I moved hwclock from /sbin to another directory using my rescue cd, and it passes the system clock call with an error, but now when it wants to startx i get a system hang and a black screen (no lights on keyboard, caps lock doesn't change lights, etc.).
My distro is gentoo.
This is going to be my last try with linux, I'll be back in winblows soon.
Please. Anybody. If you don't know the answer, do you know where i could look for answers? Or any suggestions? Is this a lost cause? Do you need more information? How do i get that information? I'm semi-newbish
I don't know what you have going there, but if you compiled the kernel when you are realively new to this stuff, my bet is that your boot loader is not setup correctly. You need to check to see if you are poiting to the correct kernel and see if the old one is removed or has changed names.
I don't know how gentoo does things, but if you can get to the cli, then look at your either lilo.conf or grub.conf and check to see if your information lines up with the correct vmlinuz for the kernel or maybe the init file, which can be called different things, eh.
So, log in, goto /boot and see what's there. Open another terminal and see what /etc/lilo.conf or etc/grub.conf look like. You can draw a lot from there without further explanation by me. See if you can figure out if the information in that file lines up with the new kernel that you build (/boot), I assume without problems. If not, change your settings to match up with the latest kernel in /boot and maybe init file.
If it's not that, then I wouldn't know unless I was there to go from each point to the next, I'm afraid. Sorry about that. But, that is probably the place where most folks will get lost, imo, on the first time of compiling their own kernel.
Hope this helps, and I hope you don't give up because of this gentoo thing. There are other distros, and in time, you won't blink twice at this type of situation, and you will know what's up or the direction to take next.
Thanks so much for the reply. I think I'm going in the right direction in recompiling the kernel with different options. I'm pretty sure I have grub configured correctly because I moved the old kernel out. Thanks, I'll let you know if i fix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.