| Linux - Kernel This forum is for all discussion relating to the Linux kernel. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-27-2006, 07:37 AM
|
#1
|
|
Member
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140
Rep:
|
Black screen when booting new 2.6.17 kernel
Hi guys,
I configured and compiled my new 2.6.17 kernel last night, installed it, and when I went to boot it the screen just goes black after decompressing the kernel. I can still hear some hard drive activity so it seems like the rest goes fine.
Note that when installing the kernel I didn't change the symbolinc links pointing to System.map and .config.... Could that be the problem???
Thanks a lot!!!
|
|
|
|
07-27-2006, 10:14 AM
|
#2
|
|
Senior Member
Registered: Oct 2003
Posts: 2,280
Rep: 
|
I don't think that's your problem. If you are using a proprietary binary driver from nvidia or ati, they have to be recompiled whenever you change your kernel. That's the most likely explanation.
|
|
|
|
07-27-2006, 10:19 AM
|
#3
|
|
Senior Member
Registered: Oct 2005
Distribution: Gentoo, Slackware, LFS
Posts: 2,040
Rep: 
|
are you using an initrd when booting? you probably need to update the modules inside it:
Code:
mkinitrd -o initrd 2.6.17
|
|
|
|
07-27-2006, 11:04 AM
|
#4
|
|
Member
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140
Original Poster
Rep:
|
Quote:
|
Originally Posted by kilgoretrout
I don't think that's your problem. If you are using a proprietary binary driver from nvidia or ati, they have to be recompiled whenever you change your kernel. That's the most likely explanation.
|
ok thanks but can you include the driver even if your kernel isn't compiled and running yet? Could you tell me how you do this please?
thanks
|
|
|
|
07-27-2006, 11:06 AM
|
#5
|
|
Member
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140
Original Poster
Rep:
|
Quote:
|
Originally Posted by konsolebox
are you using an initrd when booting? you probably need to update the modules inside it:
Code:
mkinitrd -o initrd 2.6.17
|
Hi, I'm using lilo when booting, what is initrd???
|
|
|
|
07-27-2006, 11:54 AM
|
#6
|
|
Senior Member
Registered: Oct 2003
Posts: 2,280
Rep: 
|
You install the kernel then recompile the graphics driver if you are using the nvidia or ati driver. Which graphics card and driver are you using?
Edit: I reread your inital post and it seems you are not even getting to a command line login. In that case, you likely left some needed drivers/modules out of your kernel or you need to update your initrd per the above post, assuming you have apropriate module support compiled in your kernel. If you are using the nvidia or ati drivers, you will then boot to a command line login where you can login as root and reinstall your graphics driver.
Last edited by kilgoretrout; 07-27-2006 at 12:00 PM.
|
|
|
|
07-27-2006, 04:43 PM
|
#7
|
|
Senior Member
Registered: Oct 2005
Distribution: Gentoo, Slackware, LFS
Posts: 2,040
Rep: 
|
Initrd is the first fs that's loaded by a bootloader like lilo. It's a ramfs image that's loaded to the memory at boot and is read like an ordinary filesystem. It's optional but it's most useful for systems with complicated boot devices just like network bootdisks.
Take a look at these links for more info.
http://www.tldp.org/LDP/Linux-Filesy...ml/initrd.html
http://en.wikipedia.org/wiki/Initrd
It's also called init-ramfs btw.
|
|
|
|
07-28-2006, 07:38 AM
|
#8
|
|
Member
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140
Original Poster
Rep:
|
Quote:
|
Originally Posted by konsolebox
|
Thanks for that!!!!!
Ok, problem solved!!! I think I made a mistake when configuring the thingy. Now it works I can boot on the new kernel and stuff but I get another problem .... so will make another post 
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:03 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|