Results 1 to 2 of 2
hi everyone! i got a problem. i used this tutorial to test a new kernel:
Digital Hermit - Kernel-Build-HOWTO
-i configured it sucesfully
-i succesfully make my bizimage
- i ...
- 06-15-2007 #1Just Joined!
- Join Date
- Jun 2007
- Posts
- 15
kernel 2.6.21.5 wont work :mad::mad:
hi everyone! i got a problem. i used this tutorial to test a new kernel:
Digital Hermit - Kernel-Build-HOWTO
-i configured it sucesfully
-i succesfully make my bizimage
- i did make module, it took me less then 1 minute...weird
-i did make modules install, again it took me less than 1 minute
- reconfigured lilo to be able to load both on the new kernel and the old one
result:
when i try to boot on the new kernel, i got a black screen.

the older kernel still work, and windows xp havnt been affected.
here are the operations i did in detail:
somebosdy have an ideas what wrong in my process?Code:1-download the more stable kernel around 2-extract it and put it in a folder 3.make menuconfig configured my stuff and saved it 4. make clean (supposed to clean the junk) 5.make bzImage (done after 7 or 8 minutes) 6.make modules (took me less than 1 min) 7.make modules_install (less thn 1 min) 8.cp arch/i386/boot/bzImage /boot/bzImage-2.6.21.5 (copy to boot for lilo) 9. cp System.map /boot/System.map-2.6.21.5 (copy to boot for lilo) 10. ln -s /boot/System.map-2.6.21.5 /boot/System.map (symbolic link) 11. configured lilo .conf this way: image=/boot/bzImage-2.6.21.5 label=test-2.6.21.5 root=/dev/hda2 read-only 12. reboot 13. try to load on kernel 2.6.21.5, give me a blacks screen.
- 06-15-2007 #2Just Joined!
- Join Date
- Jun 2007
- Posts
- 15
after a little search i was able to see something, it was a stupid option in lilo that wasd making the whole system booting in some ****ing resolution that my new kernel was not able to handle.
still, something terribly wrong with my kernel, basic function like make, make copy wont work. it way its not installed.
nothing is detected no drivers have been installed....
i seen some 2.4 module loading in the booting sequences. its not normal.....
so, what happen?


Reply With Quote