Hello, Just re-ran lilo -v, rebooted and it finally loaded the new kernel. Weird, thx for the tips tho! So far so good, I've also tried it on a P3 500 Dell Laptop using grub, no probs whatsoever. Good job guys! Ed Wednesday, March 03, 2004, 9:14:46 AM, you wrote: TD> Hi, TD> If it continues to boot boot the second image, then you need to run lilo TD> again. Just run TD> /sbin/lilo TD> and if it doesn't have any errors, everything should be set (and it will TD> highlight whichever kernel is set at the default kernel, with a *) TD> Troy TD> SC Web Services wrote: >> Hello, >> >> I've just updated to the new kernel on a P3 1Ghz/512 running RH7.3. >> >> After installing the rpm, it gave an error saying name too long. I >> assume this had to do with lilo, so I took a look at my lilo.conf. It >> did indeed enter in the correct path for the entry. Here's what I have >> listed: >> >> #################### >> prompt >> timeout=3 >> default=linux >> boot=/dev/hde >> map=/boot/map >> install=/boot/boot.b >> message=/boot/message >> linear >> >> image=/boot/vmlinuz-2.4.20-30.7.legacy >> label=linux >> root=/dev/hde3 >> read-only >> initrd=/boot/initrd-2.4.20-30.7.legacy.img >> image=/boot/vmlinuz-2.4.20-28.7 >> label=linuxold >> root=/dev/hde3 >> read-only >> initrd=/boot/initrd-2.4.20-28.7.img >> image=/boot/vmlinuz-2.4.20-27.7 >> label=linuxold2 >> root=/dev/hde3 >> read-only >> initrd=/boot/initrd-2.4.20-27.7.img >> image=/boot/vmlinuz-2.4.18-24.7.x >> label=linuxstock >> root=/dev/hde3 >> read-only >> initrd=/boot/initrd-2.4.18-24.7.x.img >> ##################### >> >> So I did a reboot, but for some reason, it continues to boot the >> second entry, image=/boot/vmlinuz-2.4.20-28.7. Can this have something >> to do with the name too long issue? >> >> Sorry if this is the wrong place to ask, just thought someone here may >> shed some light. thx. >> >> Ed >> >> >> >> Tuesday, March 02, 2004, 9:02:21 PM, you wrote: >> >> JK> -----BEGIN PGP SIGNED MESSAGE----- >> JK> Hash: SHA1 >> >> JK> On Tuesday 02 March 2004 17:44, Jim Richardson wrote: >> >>>>Just to be clear, these are the same kernels that have been available >>>>for testing for a while right? I want to make sure that I have this one >>>>allready updated, I have kernel-bigmem-2.4.20-30.7.legacy installed, is >>>>that the same as this release level? thanks, sorry to be obtuse, but I >>>>want to make sure. >> >> >> JK> Yes, they are exactly the same. The sha1sums from this announcement should >> JK> match those of the updates-testing announcement. >> >> >> >> -- >> >> fedora-legacy-list@xxxxxxxxxx >> http://www.redhat.com/mailman/listinfo/fedora-legacy-list
