tag:blogger.com,1999:blog-1134723925265805427.post2480137207314389972..comments2023-10-31T14:04:04.105+02:00Comments on Rambling around foo: [help] kernel: same config as debian, but mine doesn't booteddyphttp://www.blogger.com/profile/13986125106284142716noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-1134723925265805427.post-89670471161889368672009-07-02T16:05:46.690+03:002009-07-02T16:05:46.690+03:00your bios may be lying to you. investigate apic=[...your bios may be lying to you. investigate apic=[quiet|verbose|debug], no apic, nomce and friends instead of quiet. dmesg or kernel.log snippets could be helpful.erjcnoreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-36820862550799982722009-06-18T08:11:51.901+03:002009-06-18T08:11:51.901+03:00Maybe you should supply the filesystems by UUID in...Maybe you should supply the filesystems by UUID instead of device name?Martijnhttps://www.blogger.com/profile/10222805960380790142noreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-33297944797752432792009-06-17T21:29:05.811+03:002009-06-17T21:29:05.811+03:00This looks like an initramfs issue rather than a k...This looks like an initramfs issue rather than a kernel issue.<br /><br />What are the contents of /dev at the point that you get the busybox prompt?<br /><br />Does a copy of udev live on the initramfs? Is there a version mismatch there (i.e. an etch udev on the working initramfs and a lenny udev which is 2.6.18-incompatible on the broken initramfs)? Does the new kernel work with the old initramfs?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-14777013693838212552009-06-17T21:21:21.567+03:002009-06-17T21:21:21.567+03:00Are you passing the 'quiet' parameter to t...<i>Are you passing the 'quiet' parameter to the kernel? If so, try removing it to see more output.</i><br /><br />That was a real challenge. I was using lilo as a boot loader since I had /boot on LVM, while lilo is not as flexible as grub when it comes to changing boot parameters easily.<br /><br />I managed to install grub-pc (aka grub2), but still I can't boot my kernel.<br /><br />I'll post an update later tonight.<br /><br /><br />EddyPAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-20005821604146418412009-06-17T21:03:17.342+03:002009-06-17T21:03:17.342+03:00IIRC there was some change to udev and 2.6.18 need...<i>IIRC there was some change to udev and 2.6.18 needs an older<br />udev in order to boot. If you have enough spare disk space it may be<br />better to try and re-create a minimal etch system to boot from to<br />check the regression in suspend/resume.</i><br /><br />You missed the part where I said that the Debian 2.6.18 kernel from Etch is working and mine isn't.<br /><br /><br />EddyP.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-62067977459180242442009-06-17T16:58:20.574+03:002009-06-17T16:58:20.574+03:00Are you passing the 'quiet' parameter to t...Are you passing the 'quiet' parameter to the kernel? If so, try removing it to see more output.Unknownhttps://www.blogger.com/profile/03388907824239791010noreply@blogger.comtag:blogger.com,1999:blog-1134723925265805427.post-79443687128121719622009-06-17T16:55:54.274+03:002009-06-17T16:55:54.274+03:00IIRC there was some change to udev and 2.6.18 need...IIRC there was some change to udev and 2.6.18 needs an older<br />udev in order to boot. If you have enough spare disk space it may be<br />better to try and re-create a minimal etch system to boot from to<br />check the regression in suspend/resume.Kapil Hari Paranjapehttp://www.imsc.res.in/~kapil/noreply@blogger.com