Re: Kernel 2.6 compile problem - Solved
Russ Cook wrote: David Clymer wrote: On Thu, 2004-10-21 at 07:06, Russ Cook wrote: The problem turned out to be the lack of module-init-tools on my system. An additional problem was that module-init-tools conflicted with modutils already installed. I had to upgrade modutils to most current version first, then install module-init-tools. All is fine now, except that during the process of upgrading all my packages (which probably wasn't necessary) I have lost my /boot/boot.b -> /boot/boot-menu.b . The system boots into vmlinuz-2.6.8 just fine, and my modules load, but I don't have a menu option for booting into the previous kernel. I need to obtain another boot-menu.b somehow. you may need to set a boot delay in /etc/lilo.conf. If you do that, you will be able to select a kernel to boot. Take a look at http://www.linuxheadquarters.com/howto/basic/lilo.shtml or man lilo.conf for more details. -davidc No, the problem APPEARS to be that /boot/boot.b is a symlink pointing to /boot/boot-menu.b . And, boot-menu.b does not exist. I have no *.b files except boot.b . I tried reinstalling lilo and running lilo again, but nothing changed. This confuses me, because I thought the *.b file was the secondary boot loader, phase 2 of the boot process, and the system wouldn't boot without it. So, off to do some more digging. Well David, I guess you were right after all. Holding the left shift key during boot gives me my boot menu, as it always has. I guess I just got confused about the symlink /boot/boot.b which points to a non-existent /boot/boot-menu.b . Anyway, my system now is up and running with kernel 2.6.8. Now on to get sound working under Alsa. Thanks. Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6 compile problem - Solved
David Clymer wrote: On Thu, 2004-10-21 at 07:06, Russ Cook wrote: The problem turned out to be the lack of module-init-tools on my system. An additional problem was that module-init-tools conflicted with modutils already installed. I had to upgrade modutils to most current version first, then install module-init-tools. All is fine now, except that during the process of upgrading all my packages (which probably wasn't necessary) I have lost my /boot/boot.b -> /boot/boot-menu.b . The system boots into vmlinuz-2.6.8 just fine, and my modules load, but I don't have a menu option for booting into the previous kernel. I need to obtain another boot-menu.b somehow. you may need to set a boot delay in /etc/lilo.conf. If you do that, you will be able to select a kernel to boot. Take a look at http://www.linuxheadquarters.com/howto/basic/lilo.shtml or man lilo.conf for more details. -davidc No, the problem APPEARS to be that /boot/boot.b is a symlink pointing to /boot/boot-menu.b . And, boot-menu.b does not exist. I have no *.b files except boot.b . I tried reinstalling lilo and running lilo again, but nothing changed. This confuses me, because I thought the *.b file was the secondary boot loader, phase 2 of the boot process, and the system wouldn't boot without it. So, off to do some more digging. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6 compile problem - Solved
On Thu, 2004-10-21 at 07:06, Russ Cook wrote: > > > > > The problem turned out to be the lack of module-init-tools on my > system. An additional problem was that module-init-tools conflicted > with modutils already installed. I had to upgrade modutils to most > current version first, then install module-init-tools. All is fine now, > except that during the process of upgrading all my packages (which > probably wasn't necessary) I have lost my /boot/boot.b -> > /boot/boot-menu.b . The system boots into vmlinuz-2.6.8 just fine, and > my modules load, but I don't have a menu option for booting into the > previous kernel. I need to obtain another boot-menu.b somehow. > you may need to set a boot delay in /etc/lilo.conf. If you do that, you will be able to select a kernel to boot. Take a look at http://www.linuxheadquarters.com/howto/basic/lilo.shtml or man lilo.conf for more details. -davidc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6 compile problem - Solved
David Clymer wrote: On Mon, 2004-10-18 at 06:29, Russ Cook wrote: David Clymer wrote: On Sun, 2004-10-17 at 19:16, Russ Cook wrote: I'm running unstable on a Pentium 2 machine, kernel 2.4.18. I downloaded the kernel-source-2.6.8 deb package today, updated my config file, and tried to compile the kernel. I got the following errors: make[2] [modins_post] Error 1 make[1] [real_stamp_image] Error 2 Where did you get them? Was this the only output? How did you go about compiling the kernel? What modifications did you make to the config file? David (and the list), In the hope that it might be useful, I've attached the config file. The last compiled files in the process before the error messages, according to the screen output, were in the sound section. If you have ideas for any other output that might be useful, please tell me how to obtain it and I'll be happy to attemp a recompile and send it to you. I was actually hoping to get a few answers to the questions I asked :) Lets start with a play-by-play of your kernel compilation process. What commands did you type from the point where you thought "i'm going to compile a kernel" to the point where you saw the above errors? Then, once you saw the errors, did you attempt to determine what they meant? If so, what did you do? The config file is better than nothing, but is not too useful, since I dont know what *changed* between the original config file and your current one. If you want to get the output from a compile or any other command that produces output, try the following: mycommand 2>&1 > /path/to/your/favorite/file this will redirect everything that usually gets sent to your console to the file that you specified. -davidc ps. have you ever seen ESR's guide to asking good questions? Its a great resource. check it out at: http://www.catb.org/~esr/faqs/smart-questions.html The problem turned out to be the lack of module-init-tools on my system. An additional problem was that module-init-tools conflicted with modutils already installed. I had to upgrade modutils to most current version first, then install module-init-tools. All is fine now, except that during the process of upgrading all my packages (which probably wasn't necessary) I have lost my /boot/boot.b -> /boot/boot-menu.b . The system boots into vmlinuz-2.6.8 just fine, and my modules load, but I don't have a menu option for booting into the previous kernel. I need to obtain another boot-menu.b somehow. Anyway, thanks to all who provided suggestions to my compile problem. Regards, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
