Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
cant boot ater upgrading to a new kernel
#1

Hey guys, i have compiled new kernel couple of days ago, 2.6.17.13, and everything went good, no errors. after reboot my lilo loaded, i did see my new kernel there, since i have configured lilo before, picked my new kernel, and it is starting to boot, it iwll go to a screen where it is starting to load modules, and right after that i am starting to see a colored lines across my screen, and there is more and more of them, and after a minute they are filling out my whole screen and i cant see anything but those colored lines :( i know one thing for sure it is not gettgin to startx, and before i notices that those lines started to appear as soon as my wireless module was executed, so i thought that was a problem, i removed that kernel, and reconfigured my config where i have excluded ipw2200bg modules, and other wireless support, recompiled again.... rebooted...... SAME THING!!! driving me nuts, i have tryed everything that i know, and nothing works, please help

 

i am using slackware 10.2

Reply
#2
are you sure you dont have any hardware issue ? possible video card going bye bye perhaps ?
Reply
#3
defenetly not, my previous kernel works just fine, i am still able to boot into that kernel without any problems, and able to play CSS on that kernel, so that is not an issue, it is some kind of configuration issue, and i cant figure out what it is..... :(
Reply
#4
can you ssh into the box after the lines start appearing on your screen ?
Reply
#5

Hi,

 

Have you tried taking a copy of your pervious kernel's .config file and placing it into your

new kernel source directory??

Reply
#6

copy the .config from the /usr/src/linux-??? of your previous kernel in to the /usr/src/linux dir of your new kernel.

 

In the new kernel's dir, run make oldconfig. If there are differences between the config of the old kernel and the new kernel, the script will prompt you for each of them and offer you the choice of Yes/No/Module (where applicable) for each of them. Answer them all and at the end, the script will write you a new .config.

 

After that completes, run make menuconfig and make any additional changes you need/want to make for the new kernel.

 

Then make && make install_modules etc

 

One suggestion, when changing to a new kernel, if you have other changes you need to make, make them one at a time and compile and boot into your new kernel at each step. If you make several changes and one of them breaks the system, it is sometimes hard to figure out which caused the break.

 

P38

Reply
#7
Hi guys, i was looking through my topics and found this one :)the reason why this was happening is i was setting clocl too high it should of being set at 250 and it was set to 1000 instead. i didnt try to ssh into my box, reason for this is that my ssh module was not loading on startup, i disabled that, at least it was disabled on that time. Recently i installed Slack11 on 2.6.17.13 and i compiled second kernel 2.6.19, everything works great. if someone needs xorg, or .config i wuuld be more than glad to share :)thanks for your help guys
Reply
#8
thanks for updating the post !
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)