On Sun, 26 Sep 2010 21:27:37 -0400 (EDT), bri...@aracnet.com wrote: > > and..... IT WORKS ! > > Talking to you from a freshly booted machine :-) > > First time it's booted properly in quite sometime. > > I'm not really clear on what exactly fixed things, although those > missing initrd lines were probably key.
You had several unrelated problems. (1) The initial RAM disk specifications were missing from the two boot menu items in /etc/lilo.conf that used the standard symlinks. Therefore, neither of these two entries would boot at all. (2) Apparently, the specification of the swap partition in /etc/initramfs-tools/conf.d/resume was not valid. Therefore, the other kernels would boot but failed at resume processing. (This is not related to the lilo boot loader. It would have failed with any boot loader.) (3) /etc/kernel-img.conf had postinst_hook and postrm_hook lines that referred to a script that did not exist or could not be found in any of the directories in the path. That method is no longer safe to use anyway because, under certain conditions, it is possible for the hook script to be invoked before the initial RAM file system is updated. That's OK for grub version 1 (grub-legacy), but not for lilo. lilo should not be invoked until *after* the initial RAM file system is updated. (4) hook scripts in /etc/kernel/postinst.d, /etc/kernel/postrm.d, and /etc/initramfs/post-update.d were missing, obsolete, or superfluous. > Thank you very much for your help ! I _really_ appreciate it. You're welcome. Now, with your indulgence, I'd like to suggest some further changes that will make your setup more robust. For example, I notice that you have other kernels in your boot menu, such as 2.6.32-3. This kernel currently will probably not boot. I suggest the following changes in /etc/lilo.conf: Change boot=/dev/sda to boot=/dev/disk/by-id/ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692 Change root=/dev/sda2 to root="UUID=a948d6b6-8395-49a1-9f0f-21a10ceee9c2" In /etc/initramfs-tools/conf.d/resume, change RESUME=/dev/sda4 to RESUME=UUID=558d7790-5914-494d-938f-3387296eed45 You never did post the contents of your /etc/fstab file. I'd still like to see that. > Now that it's working I can go back to try and create a custom > kernel :-) Good luck! I see from other posts that you use an Nvidia graphics card. I now have a new section at the end of my kernel building guide that explains how to create a custom kernel that uses the proprietary Nvidia drivers built the traditional Debian way. It is called "A Specific Example". You may wish to review that section. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1884665001.298704.1285596555275.javamail.r...@md01.wow.synacor.com
