Re: [[newbie] Wrong Kernel Reported]
Cindy Bartorillo [EMAIL PROTECTED] wrote: I just took a deep breath and updated my kernel from the 2.2.15-4 that came with my brand-new Mandrake 7.1 to the 2.2.16-9 that the Update feature said I needed. As recommended I downloaded the rpm's myself and installed them by hand. Everything seems to have gone OK. But when I rebooted, the opening screen says I have 2.2.15-4, and so does the KDE Control Center, and so does the Netscape site. I have the new 2.2.16-9 directory and the links in /boot definitely point to the new kernel. So why won't anyone acknowledge it? CindyB === Did you add the new kernel to /etc/lilo.conf, make it the default, and rerun /sbin/lilo ? Mike ~~~ "I'd rather have a bottle in front of me than a frontal lobotomy." --Tom Waits ~~~ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
Re: [newbie] Wrong Kernel Reported
Cindy Bartorillo wrote: I just took a deep breath and updated my kernel from the 2.2.15-4 that came with my brand-new Mandrake 7.1 to the 2.2.16-9 that the Update feature said I needed. As recommended I downloaded the rpm's myself and installed them by hand. Everything seems to have gone OK. But when I rebooted, the opening screen says I have 2.2.15-4, and so does the KDE Control Center, and so does the Netscape site. I have the new 2.2.16-9 directory and the links in /boot definitely point to the new kernel. So why won't anyone acknowledge it? CindyB Did you make sure that lilo is aware of the new kernel? You need to edit /etc/lilo.conf to point to your new kernel, then re-run lilo to enable lilo to find the new kernel. Regards, Ozz.
Re: [newbie] Wrong Kernel Reported
My lilo.conf reads: image=/boot/vmlinuz which is a link to the new kernel. So I figured I shouldn't have to change anything. Does lilo need to be rerun anyway? I'd really like to understand what goes on here. Harvey Janson wrote: Hi Cindyb, You downloaded Kernel 2.2.16-9, but did you tell your system this was the kernel you wanted used? 1. Open /etc/lilo.conf with a text editor (ex: pico /etc/lilo.conf). Change image=/boot/vmlinuz-2.2.15-4 to image=/boot/vmlinuz-2.2.16-9 2. Tell lilo to make the change by entering /sbin/lilo on the command line. 3. Reboot. Everything should be fine. If not, send another e-mail. Harvey On Sun, 13 Aug 2000, you wrote: I just took a deep breath and updated my kernel from the 2.2.15-4 that came with my brand-new Mandrake 7.1 to the 2.2.16-9 that the Update feature said I needed. As recommended I downloaded the rpm's myself and installed them by hand. Everything seems to have gone OK. But when I rebooted, the opening screen says I have 2.2.15-4, and so does the KDE Control Center, and so does the Netscape site. I have the new 2.2.16-9 directory and the links in /boot definitely point to the new kernel. So why won't anyone acknowledge it? CindyB
Re: [newbie] Wrong Kernel Reported
Cindy Bartorillo wrote: My lilo.conf reads: image=/boot/vmlinuz which is a link to the new kernel. So I figured I shouldn't have to change anything. Does lilo need to be rerun anyway? I'd really like to understand what goes on here. Yes, lilo does indeed need to be rerun anyway. Regards, Ozz.
Re: [newbie] Wrong Kernel Reported
Tom Brinkman wrote:
On Mon, 14 Aug 2000, you wrote:
My lilo.conf reads:
image=/boot/vmlinuz
which is a link to the new kernel. So I figured I shouldn't have to change
anything.
Does lilo need to be rerun anyway? I'd really like to understand what goes on here.
Read this whole page Cindy, it explains it all pretty well.
http://mandrakeuser.org/install/kupgrade3.html
The Mandrake kerenel rpms' make the changes to both grub and
lilo. Grub will automagically pick up the change on re-boot, but
you must run '/sbin/lilo' (as root) to make the change to the new
kernel if you use lilo. With both it's a good idea to review their
config files ('lilo.conf', grub's 'menu.lst') before rebooting or
running '/sbin/lilo'. I always make sure my bootdisk is working
also, in case I need to boot the old kernel.
--
~~ Tom Brinkman[EMAIL PROTECTED]
Actually, I had a printout of that page in my hand as I did the upgrade, but since I
didn't compile anything and changed absolutely nothing in the lilo.conf file (Part 2
says
to rerun if you've changed *anything* in lilo.conf), it didn't seem like I needed to
rerun. I'm learning, though. Slowly. :-)
CindyB
Re: [newbie] Wrong Kernel Reported
Hi Cindy Did you change your LILO configuration file to reflect the kernel changes then run /sbin/lilo? The RPM may not have done this. Ron Cindy Bartorillo [EMAIL PROTECTED] said: I just took a deep breath and updated my kernel from the 2.2.15-4 that came with my brand-new Mandrake 7.1 to the 2.2.16-9 that the Update feature said I needed. As recommended I downloaded the rpm's myself and installed them by hand. Everything seems to have gone OK. But when I rebooted, the opening screen says I have 2.2.15-4, and so does the KDE Control Center, and so does the Netscape site. I have the new 2.2.16-9 directory and the links in /boot definitely point to the new kernel. So why won't anyone acknowledge it? CindyB --
Re: [newbie] Wrong Kernel Reported
Hi Cindyb, You downloaded Kernel 2.2.16-9, but did you tell your system this was the kernel you wanted used? 1. Open /etc/lilo.conf with a text editor (ex: pico /etc/lilo.conf). Change image=/boot/vmlinuz-2.2.15-4 to image=/boot/vmlinuz-2.2.16-9 2. Tell lilo to make the change by entering /sbin/lilo on the command line. 3. Reboot. Everything should be fine. If not, send another e-mail. Harvey On Sun, 13 Aug 2000, you wrote: I just took a deep breath and updated my kernel from the 2.2.15-4 that came with my brand-new Mandrake 7.1 to the 2.2.16-9 that the Update feature said I needed. As recommended I downloaded the rpm's myself and installed them by hand. Everything seems to have gone OK. But when I rebooted, the opening screen says I have 2.2.15-4, and so does the KDE Control Center, and so does the Netscape site. I have the new 2.2.16-9 directory and the links in /boot definitely point to the new kernel. So why won't anyone acknowledge it? CindyB
