[tslug] Re: Troubleshooting kernel install
For the benefit of anyone else who is having this trouble, and your email archives, Ben Story suggests the solution to this problem is upgrading to GCC 3.0 or better. I downloaded GCC 3.0.1 last night but I haven't had time yet to figure out how to install it and test. If it doesn't work, I'll let you know, but I'm assuming he's right for now... Sean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sean M. Foy Sent: Monday, September 17, 2001 10:44 AM To: [EMAIL PROTECTED] Subject: [tslug] Re: Troubleshooting kernel install I used make bzImage. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Donald J Bindner Sent: Monday, September 17, 2001 9:26 AM To: [EMAIL PROTECTED] Subject: [tslug] Re: Troubleshooting kernel install On Mon, Sep 17, 2001 at 09:23:24AM -0500, Sean M. Foy wrote: > /boot/vmlinuz-2.4.9 is a real file; /boot/vmlinuz is a symlink to > vmlinuz-2.4.9; /boot/vmlinuz-2.4.9smp does not exist in /boot/. Sorry, typo on my part. > It looks like it is about the right size (1064985), too, judging by the > other vmlinuz-* in that dir. Did you use make zImage or make bzImage? I have sometimes had my kernel grow just a little too large. I use exclusively make bzImage (big zImage) now. -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
I used make bzImage. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Donald J Bindner Sent: Monday, September 17, 2001 9:26 AM To: [EMAIL PROTECTED] Subject: [tslug] Re: Troubleshooting kernel install On Mon, Sep 17, 2001 at 09:23:24AM -0500, Sean M. Foy wrote: > /boot/vmlinuz-2.4.9 is a real file; /boot/vmlinuz is a symlink to > vmlinuz-2.4.9; /boot/vmlinuz-2.4.9smp does not exist in /boot/. Sorry, typo on my part. > It looks like it is about the right size (1064985), too, judging by the > other vmlinuz-* in that dir. Did you use make zImage or make bzImage? I have sometimes had my kernel grow just a little too large. I use exclusively make bzImage (big zImage) now. -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
On Mon, Sep 17, 2001 at 09:23:24AM -0500, Sean M. Foy wrote: > /boot/vmlinuz-2.4.9 is a real file; /boot/vmlinuz is a symlink to > vmlinuz-2.4.9; /boot/vmlinuz-2.4.9smp does not exist in /boot/. Sorry, typo on my part. > It looks like it is about the right size (1064985), too, judging by the > other vmlinuz-* in that dir. Did you use make zImage or make bzImage? I have sometimes had my kernel grow just a little too large. I use exclusively make bzImage (big zImage) now. -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
/boot/vmlinuz-2.4.9 is a real file; /boot/vmlinuz is a symlink to vmlinuz-2.4.9; /boot/vmlinuz-2.4.9smp does not exist in /boot/. It looks like it is about the right size (1064985), too, judging by the other vmlinuz-* in that dir. Thanks, Sean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Donald J Bindner Sent: Monday, September 17, 2001 8:42 AM To: [EMAIL PROTECTED] Subject: [tslug] Re: Troubleshooting kernel install On Sun, Sep 16, 2001 at 08:59:12PM -0500, Sean M. Foy wrote: > I'm using GRUB. I'm really glad to see this. I am using grub on one of my machines, and it is just great. > Although some people seem to think GRUB needs to be reinstalled every time > you add a kernel, there is not universal agreement on this point. I have never had to reinstall grub; I believe that sentiment is just leftover from experience with lilo. I have only needed to edit menu.lst (as you suggest later in your email). > initrd hasn't worked for me since the original (to Mandrake 7.2) > 2.2.17-21mdk; I didn't use it under 2.4.3 and I'm not trying to use it under > 2.4.9. > > So, any other ideas? Did you compile in ramdisk and initrd support (vs. just making them a module?)? Is /boot/vmlinux-2.4.9smp a symbolic link to somewhere problematic or is it a real file? -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
On Sun, Sep 16, 2001 at 08:59:12PM -0500, Sean M. Foy wrote: > I'm using GRUB. I'm really glad to see this. I am using grub on one of my machines, and it is just great. > Although some people seem to think GRUB needs to be reinstalled every time > you add a kernel, there is not universal agreement on this point. I have never had to reinstall grub; I believe that sentiment is just leftover from experience with lilo. I have only needed to edit menu.lst (as you suggest later in your email). > initrd hasn't worked for me since the original (to Mandrake 7.2) > 2.2.17-21mdk; I didn't use it under 2.4.3 and I'm not trying to use it under > 2.4.9. > > So, any other ideas? Did you compile in ramdisk and initrd support (vs. just making them a module?)? Is /boot/vmlinux-2.4.9smp a symbolic link to somewhere problematic or is it a real file? -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
Thanks for the suggestion, but I don't think this is quite it... I'm using GRUB. I did update the lilo.conf file as you can see in my log, merely so that it would stay current in case I wanted to switch to LILO (Ben Story had me do this once on another machine...). Although some people seem to think GRUB needs to be reinstalled every time you add a kernel, there is not universal agreement on this point. But, after your email, I thought I would give that a try, so I ran the install.sh script. That did not change my situation. Those who don't believe in the necessity of reinstalling GRUB say that you're done after you edit menu.lst. Those that do believe in the necessity of reinstalling GRUB say that doing so is the equivalent of running LILO after editing lilo.conf. Just to be sure I'm not consistently overlooking a typo or something, I used GRUB's edit-boot-config-line-just-before-booting option and changed the 9 in vmlinuz-2.4.9 to 3 (so that I could use the kernel I've had working for a while). It worked, so the syntax of that kernel entry in the GRUB menu.lst must be right. But, in case it is useful, here's the section of my GRUB menu.lst: --- title linux-2.4.9smp kernel (hd0,0)/boot/vmlinuz-2.4.9 root=/dev/hda1 mem=256M --- initrd hasn't worked for me since the original (to Mandrake 7.2) 2.2.17-21mdk; I didn't use it under 2.4.3 and I'm not trying to use it under 2.4.9. So, any other ideas? Thanks, SEan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Donald J Bindner Sent: Sunday, September 16, 2001 7:41 PM To: [EMAIL PROTECTED] Subject: [tslug] Re: Troubleshooting kernel install Almost always, the trouble in this situation is that you forgot to update /etc/lilo.conf and run lilo to update the bootloader. Typically the fix is to boot from a floppy or CD (you installation media can usually be used for this) and use it to do these things. Don On Sun, Sep 16, 2001 at 06:25:26PM -0500, Sean M. Foy wrote: > I finally got around to upgrading from 2.4.3 to 2.4.9. After I installed > 2.4.9 and did shutdown -r -t 0 now, my Linux machine failed to come back up. > > So I put a monitor on it and observed that attempting to boot into 2.4.9 > causes the machine to reboot itself immediately after the 2.4.9 option is > selected on the boot menu. I booted into my original kernel and recompiled > 2.4.9, to be sure I hadn't missed some option in xconfig... Same results > after restart. > > I'm not having much luck finding answers in google web and newsgroup > searches. > > Any suggestions as to how I can figure out what the problem is and how to > fix it? > > Here's the relevant section from my logbook; This worked for 2.4.3, and I > followed my steps for 2.4.9: > cd ~sean/software/kernel > bzcat linux-2.4.3.tar.bz2 | tar xvf - > mv linux /usr/src/linux-2.4.3 > cd /usr/src > ln -s linux-2.4.3 linux > cd linux > #next line really only needed if this isn't a fresh compile > #(e.g., kernel tweaking without getting a new kernel) > make mrproper > make xconfig > ensure Processor type and features > MTRR (Memory Type Range Register) > support is YES >this ensures that even on SMP systems with buggy BIOSes, the second > processor cache >will be enabled. > ensure Processor type and features > SMP YES > turn on Networking Options>CONFIG_SYN_COOKIES (TCP syncookie support) > ensure DEC/Tulip networking support YES for FA310TX! > turn on Networking Options>network packet filtering > ensure Enhanced Character Devices > RTC (Real-time clock) support YES > turn on the option to show experimental options and enable ReiserFS > support in File Systems. > #make modules and make modules_install are only necessary if > #the kernel is configured with modules! > make dep && make clean && make bzImage && make install && make modules && > make modules_install > cd /boot > rm System.map > rm vmlinuz > rm modules.info > ln -s (blah blah blah; link to the new System.map, vmlinuz, modules.info) > #create new initrd > #-doesn't seem to work with 2.4.3 and ReiserFS > #(adjust lilo.conf/menu.lst accordingly. > mkinitrd /boot/initrd-2.4.3.img 2.4.3 > #update LILO (not really necessary since we're using GRUB) > xemacs /etc/lilo.conf > #update GRUB > xemacs /boot/grub/menu.lst > bzcat modutils-2.4.5.tar.bz2 | tar xvf - > ensure that man pages listed in INSTALL aren't in /usr/man/1 > ./configure > make > make install > > Thanks, > Sean > > > -- Don Bindner <[EMAIL PROTECTED]>
[tslug] Re: Troubleshooting kernel install
Almost always, the trouble in this situation is that you forgot to update /etc/lilo.conf and run lilo to update the bootloader. Typically the fix is to boot from a floppy or CD (you installation media can usually be used for this) and use it to do these things. Don On Sun, Sep 16, 2001 at 06:25:26PM -0500, Sean M. Foy wrote: > I finally got around to upgrading from 2.4.3 to 2.4.9. After I installed > 2.4.9 and did shutdown -r -t 0 now, my Linux machine failed to come back up. > > So I put a monitor on it and observed that attempting to boot into 2.4.9 > causes the machine to reboot itself immediately after the 2.4.9 option is > selected on the boot menu. I booted into my original kernel and recompiled > 2.4.9, to be sure I hadn't missed some option in xconfig... Same results > after restart. > > I'm not having much luck finding answers in google web and newsgroup > searches. > > Any suggestions as to how I can figure out what the problem is and how to > fix it? > > Here's the relevant section from my logbook; This worked for 2.4.3, and I > followed my steps for 2.4.9: > cd ~sean/software/kernel > bzcat linux-2.4.3.tar.bz2 | tar xvf - > mv linux /usr/src/linux-2.4.3 > cd /usr/src > ln -s linux-2.4.3 linux > cd linux > #next line really only needed if this isn't a fresh compile > #(e.g., kernel tweaking without getting a new kernel) > make mrproper > make xconfig > ensure Processor type and features > MTRR (Memory Type Range Register) > support is YES >this ensures that even on SMP systems with buggy BIOSes, the second > processor cache >will be enabled. > ensure Processor type and features > SMP YES > turn on Networking Options>CONFIG_SYN_COOKIES (TCP syncookie support) > ensure DEC/Tulip networking support YES for FA310TX! > turn on Networking Options>network packet filtering > ensure Enhanced Character Devices > RTC (Real-time clock) support YES > turn on the option to show experimental options and enable ReiserFS > support in File Systems. > #make modules and make modules_install are only necessary if > #the kernel is configured with modules! > make dep && make clean && make bzImage && make install && make modules && > make modules_install > cd /boot > rm System.map > rm vmlinuz > rm modules.info > ln -s (blah blah blah; link to the new System.map, vmlinuz, modules.info) > #create new initrd > #-doesn't seem to work with 2.4.3 and ReiserFS > #(adjust lilo.conf/menu.lst accordingly. > mkinitrd /boot/initrd-2.4.3.img 2.4.3 > #update LILO (not really necessary since we're using GRUB) > xemacs /etc/lilo.conf > #update GRUB > xemacs /boot/grub/menu.lst > bzcat modutils-2.4.5.tar.bz2 | tar xvf - > ensure that man pages listed in INSTALL aren't in /usr/man/1 > ./configure > make > make install > > Thanks, > Sean > > > -- Don Bindner <[EMAIL PROTECTED]>
