On Wed, Jan 20, 2010 at 6:05 AM, Reg Clemens <reg@xxxxxxx> wrote:
Thanks all, for your suggestions. Finally, I had to re-install Fedora 12 from the DVD (as rescue mode chroot /mnt/sysimag did not help and re-installing GRUB to / bootsector did not work).
However, this time I did the updates through cmd-line (tty) as
# yum -update -y --skip-broken
... (/ after first updating yum and PackageKit /)
Two packages could not be installed due to depsolve problems (mesa-dri-drivers-i686-0:7.7-2.fc12 and mesa-libGL.i686), but that does not seem to have made any difference.
Now, can boot into the new kernel (2.6.31.9-174.fc12.i686.PAE). Though, I have no idea why it updated to the PAE kernel (maybe because the earlier kernel (2.6.31.5-127.fc12.i686.PAE) was also -PAE). This desktop PC has only 2 GB of RAM and Ubuntu 9.04 has a non PAE kernel (2.6.28-17-generic)
Jay
--
Linux User 483705 @ http://counter.li.org/ (Linux Counter)
> This is on a Fedora 12 i386 system (new install from DVD). On doing onlineWell, I had a similar problem with F11.
> update (though PackageKit module) and selecting all updates (about 850 MB) ,
> on rebooting, I find that I cannot boot into the new kernel. Though the new
> kernel with images are there in /etc/boot it still boots into the old
> kernel:
>
> New - 2.6.31.9-174.fc12
> Old - 2.6.31.5-174.fc12
>
> I had selected all packages (green, orange, red) from the Update Applet
> window.
>
> The contents of the /boot dir are as in this image:
> http://www.imagebam.com/image/a17ab164358024
>
> Any suggestions on how to proceed. or anybody else with a similar problem w/
> a wrokaround ?
>
I was doing full installs on 3 separate machines (Im working on a 4th at the
moment)
in both 32 and 64bit mode.
I was able to do the install, but the following boot would fail.
Using the Rescue option on the DVD I was able to boot the system, so it really
seemed
that
(1) the boot block being written was bad
(2) the driver was writing a bad boot block.
I fought this for almost a week, and have no idea what finally solved the
problem.
I tried rewriting the boot block by doing an install of an earlier Fedora in
an unused
partition, and a number of other things... Something finally worked. But I
fear
my next upgrade.
I posted my problem previously to this list, and didnt get any useful
responses,
Im glad at least to see someone else with a similar problem.
Is it possible that Fedora/64 writes a bad boot block?
That it is having problems with some DVD players?
--
Reg.Clemens
reg@xxxxxxx
Thanks all, for your suggestions. Finally, I had to re-install Fedora 12 from the DVD (as rescue mode chroot /mnt/sysimag did not help and re-installing GRUB to / bootsector did not work).
However, this time I did the updates through cmd-line (tty) as
# yum -update -y --skip-broken
... (/ after first updating yum and PackageKit /)
Two packages could not be installed due to depsolve problems (mesa-dri-drivers-i686-0:7.7-2.fc12 and mesa-libGL.i686), but that does not seem to have made any difference.
Now, can boot into the new kernel (2.6.31.9-174.fc12.i686.PAE). Though, I have no idea why it updated to the PAE kernel (maybe because the earlier kernel (2.6.31.5-127.fc12.i686.PAE) was also -PAE). This desktop PC has only 2 GB of RAM and Ubuntu 9.04 has a non PAE kernel (2.6.28-17-generic)
Jay
--
Linux User 483705 @ http://counter.li.org/ (Linux Counter)
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
