Re: Not such a smooth upgrade to 2011... Help?

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig229B043C6FAF15671398185F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jim Beard grabbed a keyboard and wrote:
>=20
> What is a "platokernel"?  I have a feeling that this my be triggering
> (as dependencies) the list of kernels that the installer wants to
> provide.  You might try removing that, and see if it makes a difference=
=2E

Heh.  I guess I should have pointed that out; it gave me a "WTF is
that?" moment too, when I first saw it.

[davidg@janet ~]$ urpmq -fi lib64kplatokernel7
Name        : lib64kplatokernel7
Version     : 2.2.82
Release     : 2mdv2011.0
Group       : System/Libraries
Size        : 1203632                      Architecture: x86_64
Source RPM  : koffice-2.2.82-2mdv2011.0.src.rpm   Build Host:
n6.mandriva.com
Packager    : Funda Wang <[email protected]>
URL         : http://www.koffice.org/
Summary     : Koffice 2 core library
Description :
Koffice 2 core library.
[davidg@janet ~]$


So I don't think that's part of the kernel issue.  Odd name they chose,
though...

> You later mention that you are using xfs and that may be a problem.=20
> Basically, the xfs module has to be in the initrd image used to boot,
> not just out on disk somewhere waiting to be loaded.
>=20
> Dave Hodgins' instructions to deal with this are:
>=20
> The /boot/initrd-??? file needs to be recreated
> with the correct module.  To do this, boot from an install cd/dvd, moun=
t
> the root filesystem and run the following ...
>=20
> mount --bind /proc $RootMountPoint/proc -o ro
> mount --bind /sys $RootMountPoint/sys -o ro
> mount --bind /dev $RootMountPoint/dev -o ro
> chroot $RootMountPoint
> mkinitrd -f /boot/initrd-$version.img $version
>=20
> Note that after booting from the install disk, you have to select
> "rescue system" or some such.

Do you know, offhand, if you have to be booted from a DVD in order to do
the above?  My system *will* boot on the hard drive as long as I use the
old kernel.  I suppose I can try to do that from the running system
first; either I'll have an initrd for the new kernel that works, or one
that doesn't, in which case I'm not really out anything... :-)

Wow!  I just checked my /boot partition, and look what I found:

> -rw-------  1 root root 9386626 Oct  9  2010 initrd-2.6.33.7-desktop-2m=
nb.img
> -rw-------  1 root root      27 Oct 22 20:30 initrd-2.6.38.7-desktop-1m=
nb2.img

Maybe that 2.6.38.7 image is why the fscking system can't boot? :-)
I'll definitely try running mkinitrd from the running system to see if
it'll create an initrd I can use; if that fails then I'll boot off a DVD
and try the above.

Thanks for that information, BTW!

> Also, mkinitrd on a 2011 system will use
> dracut to create the initrd, while mkinitrd-mkinitrd will use the
> traditional mkinitrd to create it.

Any functional difference between the two?  Should I care which one is
getting used?

> initrd-$version.img $version should look something like
> initrd-3.1.0-rc8-1.1-desktop.img 3.1.0-rc8-1.1-desktop
>=20
> Adjust as needed for the kernel you are creating the initrd for.

Thanks!

                  --Dave



--------------enig229B043C6FAF15671398185F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6kQCEACgkQvC3peSYrMN5vQwCdEOy4WoSlvfvuJPTuGYvAeWP9
lGEAn0lU1QVlloNemydSXujAn4HRBVSa
=H3SY
-----END PGP SIGNATURE-----

--------------enig229B043C6FAF15671398185F--