Possitive here. Just try to change to new kernel image. I was forced to
install grub after upgrading to 2.4.10.
Petr
Lilo is fine, back down to the kernel image prior to your current one,
run lilo with your new image, then boot into the new image.
Lilo can now be run just fine.
Something in the pre10 series hosed something which caused the first
instance of lilo to segfault then the next to deadlock waiting on a
page. 2.4.10 proper fixed that. In my case I reverted to 2.4.7-pre6,
ran lilo, then booted into 2.4.10 and ran lilo. Worked like a charm.
('course I had a boot disk at the ready)
David
Petr Titera wrote:
>Possitive here. Just try to change to new kernel image. I was forced to
>install grub after upgrading to 2.4.10.
>
-----BEGIN PGP SIGNED MESSAGE-----
Although its not a bad idea to switch to GRUB in any event. I've
found it to be far superior in terms of userfriendliness and power.
Jonathan
On Tue, 2 Oct 2001, David Ford wrote:
> Lilo is fine, back down to the kernel image prior to your current one,
> run lilo with your new image, then boot into the new image.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBO7pRnMK9HT/YfGeBAQHY/wQAmLadHS8w3KdU5L5GMda2REchyWHYCMCa
Nqm2WJD9GC493VGzmIlnCK05//k1tDmIkACOFJ1Bnw8FO71dNWYyVQOwOO/Mg4pw
Ydd9xgMOvBlrRkeq0ghPG4X8ZfIf1Zw9IFk+q2wDbK8ZmfNq4dt5GPKIKN1E1jII
l6nA5209ry8=
=Zfex
-----END PGP SIGNATURE-----
On Tuesday 02 October 2001 13:55, Petr Titera wrote:
> Possitive here. Just try to change to new kernel image. I was forced to
> install grub after upgrading to 2.4.10.
If this is the case, I'd call that a feature. ; >
Dave
<Well known absolute block offset bootloader hater>
--
The time is now 22:19 (Totalitarian) - http://www.ccops.org/clock.html
>
> If this is the case, I'd call that a feature. ; >
>
> Dave
> <Well known absolute block offset bootloader hater>
I hate it too now. I even booted from image I deleted. God knows what would
happen if I did not noticed it early :))
>
> --
Petr