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

[David Guntner]

Easy upgrade from 2010.1 (well, .2 really) to 2011, my ass. :-)

I had a mess of problems trying to get urpmi to update, so I managed to
finally force it to update urpmi & supporting programs upgraded.
However, when doing a:

urpmi --auto-update --replacefiles -v

I'm getting the following output:

getting lock on urpmi
comparing
/var/mandriva/official/2011/x86_64/media/main/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Main/MD5SUM
medium "2011 Main" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/main/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Main Updates/MD5SUM
medium "2011 Main Updates" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/contrib/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib/MD5SUM
medium "2011 Contrib" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/contrib/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib Updates/MD5SUM
medium "2011 Contrib Updates" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/non-free/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Non-Free/MD5SUM
medium "2011 Non-Free" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/non-free/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Non-Free Updates/MD5SUM
medium "2011 Non-Free Updates" is up-to-date
examining synthesis file [/var/lib/urpmi/2011 Main/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Main
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Non-Free/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Non-Free
Updates/synthesis.hdlist.cz]
would install instead of upgrade package
kernel-xen-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-xen-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-doc-2.6.38.7-1-mdv2011.0.noarch
would install instead of upgrade package
kernel-server-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-doc-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-source-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-pvops-doc-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-xen-pvops-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-server-devel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-pvops-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-desktop-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-xen-pvops-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-desktop-devel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-tmb-server-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-vserver-2.6.22.19-1mdv-1-3mdv2009.0.x86_64
would install instead of upgrade package
kernel-kerrighed-2.6.20.21-krg2.4.3-1mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-tmb-laptop-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-netbook-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-netbook-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-openvz-2.6.26-1.openvz1.1mdv-1-1mdv2009.1.x86_64
would install instead of upgrade package kerneloops-0.12-7-mdv2011.0.x86_64
would install instead of upgrade package
kernel-kerrighed-source-2.6.20.21-krg2.4.3-1mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-openvz-source-2.6.26-1.openvz1.1mdv-1-1mdv2009.1.x86_64
would install instead of upgrade package
kernel-tmb-server-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-tmb-laptop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-openvz-devel-2.6.26-1.openvz1.1mdv-1-1mdv2009.1.x86_64
would install instead of upgrade package
kernel-uml-x86_64-2.6.29.2-1mdv2010.0.x86_64
would install instead of upgrade package
kernel-rt-2.6.33.6-1.rt26.1mdv-1-1mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-tmb-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-vserver-devel-2.6.22.19-1mdv-1-3mdv2009.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-uml-modules-2.6.29.2.1mdv2010.0-1-1.x86_64
would install instead of upgrade package
kernel-rt-source-2.6.33.6-1.rt26.1mdv-1-1mdv2011.0.x86_64
would install instead of upgrade package
kernel-uml-2.6.29.2-1mdv2010.0.x86_64
would install instead of upgrade package
kernel-vserver-source-2.6.22.19-1mdv-1-3mdv2009.0.x86_64
would install instead of upgrade package
kernel-netbook-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-uml-x86_64-2.6.29.2.1mdv2010.0-1-1.x86_64
would install instead of upgrade package
kernel-kerrighed-devel-2.6.20.21-krg2.4.3-1mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rt-devel-2.6.33.6-1.rt26.1mdv-1-1mdv2011.0.x86_64
would install instead of upgrade package
kernel-tmb-desktop-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-tmb-desktop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-2.6.39.3-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-2.6.39.3-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-2.6.39.3-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-2.6.39.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-2.6.39.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-2.6.39.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.0-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.0-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.0-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.0-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.0-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.0-2mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.0-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.0-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.0-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.1-0.1.3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.1-0.1.3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.1-0.1.3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.1-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-3.0.1-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-3.0.1-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-3.0.1-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-3.0.1-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.2-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.2-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.2-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-3.0.2-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.2-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-3.0.2-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-3.0.2-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-3.0.2-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.3-3mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.3-4mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.3-4mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.3-4mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-devel-3.0.3-5mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.3-5mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-source-3.0.3-5mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-doc-3.0.3-5-mdv2011.0.noarch
would install instead of upgrade package
kernel-rsbac-server-3.0.3-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.3-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-3.0.3-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-3.0.3-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-3.0.3-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-doc-3.0.3-1-mdv2011.0.noarch
would install instead of upgrade package
kernel-linus-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-doc-3.0.4-1-mdv2011.0.noarch
would install instead of upgrade package
kernel-linus-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-linus-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-desktop-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-doc-3.0.4-1-mdv2011.0.noarch
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-rsbac-server-3.0.4-1mdv-1-1-mdv2011.0.x86_64
getting exclusive lock on rpm
In order to satisfy the
'kernel-rsbac-desktop-devel-3.0.1-1mdv|kernel-server-devel-2.6.38.7-1mnb2|kernel-linus-source-2.6.39.3-3mdv|kernel-tmb-server-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-4mdv|kernel-rsbac-source-3.0.1-1mdv|kernel-linus-devel-3.0.0-3mdv|kernel-linus-source-3.0.3-5mdv|kernel-linus-source-3.0.4-1mdv|kernel-rsbac-server-devel-2.6.38.8-1mdv|kernel-linus-devel-3.0.0-2mdv|kernel-linus-source-3.0.0-1mdv|kernel-linus-devel-2.6.39.3-3mdv|kernel-netbook-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.1-0.1.3mdv|kernel-rsbac-source-2.6.38.7-2mdv|kernel-tmb-source-2.6.38.7-1mdv|kernel-tmb-desktop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-5mdv|kernel-openvz-devel-2.6.26-1.openvz1.1mdv|kernel-linus-source-2.6.38.7-1mdv|kernel-xen-devel-2.6.32.11-2mdv|kernel-vserver-devel-2.6.22.19-1mdv|kernel-openvz-source-2.6.26-1.openvz1.1mdv|kernel-linus-devel-3.0.2-3mdv|kernel-kerrighed-source-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-source-3.0.2-1mdv|kernel-linus-source-3.0.1-0.1.3mdv|kernel-linus-source-3
.0.2-3mdv|kernel-source-2.6.38.7-1mnb2|kernel-netbook-source-2.6.38.7-1mdv|kernel-kerrighed-devel-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-1mdv|kernel-rsbac-server-devel-3.0.1-1mdv|kernel-rsbac-server-devel-3.0.4-1mdv|kernel-rt-source-2.6.33.6-1.rt26.1mdv|kernel-linus-devel-2.6.39.3-2mdv|kernel-rsbac-source-3.0.4-1mdv|kernel-linus-source-3.0.3-3mdv|kernel-linus-source-3.0.0-3mdv|kernel-linus-devel-3.0.0-1mdv|kernel-rsbac-server-devel-3.0.3-1mdv|kernel-rt-devel-2.6.33.6-1.rt26.1mdv|kernel-rsbac-server-devel-2.6.38.7-2mdv|kernel-tmb-laptop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.4-1mdv|kernel-rsbac-desktop-devel-2.6.38.8-1mdv|kernel-rsbac-desktop-devel-3.0.3-1mdv|kernel-xen-pvops-devel-2.6.32.11-2mdv|kernel-rsbac-server-devel-2.6.38.7-1mdv|kernel-linus-source-2.6.39.3-2mdv|kernel-rsbac-source-2.6.38.8-1mdv|kernel-linus-devel-2.6.38.7-1mdv|kernel-rsbac-source-2.6.38.7-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-2mdv|kernel-linus-source-3.0.3-4mdv|kernel-linus-
devel-3.0.3-3mdv|kernel-rsbac-desktop-devel-3.0.2-1mdv|kernel-linus-source-3.0.0-2mdv|kernel-rsbac-desktop-devel-3.0.4-1mdv|kernel-rsbac-source-3.0.3-1mdv|kernel-rsbac-server-devel-3.0.2-1mdv|kernel-vserver-source-2.6.22.19-1mdv'
dependency, one of the following packages is needed:
1- kernel-xen-pvops-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64: XEN
kernel devel files (to install)
2- kernel-xen-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64: XEN kernel
devel files (to install)
3- kernel-server-devel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-server-2.6.38.7-1mnb2 (to install)
4- kernel-source-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64: The Linux source
code for kernel-2.6.38.7-1mnb2 (to install)
5- kernel-vserver-source-2.6.22.19-1mdv-1-3mdv2009.0.x86_64: The source
code for the Linux kernel (to install)
6- kernel-vserver-devel-2.6.22.19-1mdv-1-3mdv2009.0.x86_64: The
kernel-vserver devel files for 3rdparty modules build (to install)
7- kernel-kerrighed-source-2.6.20.21-krg2.4.3-1mdv-1-1mdv2010.1.x86_64:
The source code for the Linux kernel (to install)
8- kernel-kerrighed-devel-2.6.20.21-krg2.4.3-1mdv-1-1mdv2010.1.x86_64:
The kernel-kerrighed devel files for 3rdparty modules build (to install)
9- kernel-rt-devel-2.6.33.6-1.rt26.1mdv-1-1mdv2011.0.x86_64: The
kernel-rt devel files for 3rdparty modules build (to install)
10- kernel-rt-source-2.6.33.6-1.rt26.1mdv-1-1mdv2011.0.x86_64: The
source code for the Linux kernel (to install)
11- kernel-openvz-source-2.6.26-1.openvz1.1mdv-1-1mdv2009.1.x86_64: The
source code for the Linux kernel (to install)
12- kernel-openvz-devel-2.6.26-1.openvz1.1mdv-1-1mdv2009.1.x86_64: The
kernel-openvz devel files for 3rdparty modules build (to install)
13- kernel-netbook-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-netbook devel files for 3rdparty modules build (to install)
14- kernel-rsbac-server-devel-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-2.6.38.7-2mdv (to install)
15- kernel-rsbac-server-devel-3.0.2-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-3.0.2-1mdv (to install)
16- kernel-rsbac-desktop-devel-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-2.6.38.7-2mdv (to install)
17- kernel-netbook-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
source code for the Linux kernel (to install)
18- kernel-rsbac-desktop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-2.6.38.7-1mdv (to install)
19- kernel-linus-source-3.0.0-1mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
20- kernel-linus-source-3.0.2-3mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
21- kernel-rsbac-source-3.0.1-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-3.0.1-1mdv (to install)
22- kernel-linus-source-3.0.1-0.1.3mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
23- kernel-linus-source-3.0.3-4mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
24- kernel-linus-devel-3.0.0-3mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
25- kernel-rsbac-source-3.0.2-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-3.0.2-1mdv (to install)
26- kernel-rsbac-desktop-devel-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-2.6.38.8-1mdv (to install)
27- kernel-linus-devel-2.6.39.3-2mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
28- kernel-linus-devel-2.6.39.3-3mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
29- kernel-linus-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
30- kernel-linus-source-2.6.39.3-2mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
31- kernel-tmb-laptop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-tmb-laptop-2.6.38.7-1mdv (to install)
32- kernel-linus-devel-3.0.3-4mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
33- kernel-rsbac-server-devel-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-2.6.38.8-1mdv (to install)
34- kernel-linus-source-3.0.0-2mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
35- kernel-rsbac-server-devel-3.0.1-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-3.0.1-1mdv (to install)
36- kernel-linus-devel-3.0.3-5mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
37- kernel-linus-source-2.6.39.3-3mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
38- kernel-linus-devel-3.0.0-2mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
39- kernel-rsbac-desktop-devel-3.0.3-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-3.0.3-1mdv (to install)
40- kernel-rsbac-server-devel-3.0.3-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-3.0.3-1mdv (to install)
41- kernel-rsbac-desktop-devel-3.0.2-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-3.0.2-1mdv (to install)
42- kernel-tmb-desktop-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-tmb-desktop-2.6.38.7-1mdv (to install)
43- kernel-linus-devel-3.0.3-3mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
44- kernel-rsbac-server-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-2.6.38.7-1mdv (to install)
45- kernel-tmb-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-tmb-2.6.38.7-1mdv (to install)
46- kernel-rsbac-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-2.6.38.7-1mdv (to install)
47- kernel-linus-devel-3.0.0-1mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
48- kernel-rsbac-desktop-devel-3.0.1-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-3.0.1-1mdv (to install)
49- kernel-linus-devel-3.0.2-3mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
50- kernel-linus-source-3.0.3-3mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
51- kernel-rsbac-source-3.0.3-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-3.0.3-1mdv (to install)
52- kernel-linus-source-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
53- kernel-linus-source-3.0.0-3mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
54- kernel-linus-devel-3.0.1-0.1.3mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
55- kernel-rsbac-source-2.6.38.8-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-2.6.38.8-1mdv (to install)
56- kernel-rsbac-source-2.6.38.7-2mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-2.6.38.7-2mdv (to install)
57- kernel-tmb-server-devel-2.6.38.7-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-tmb-server-2.6.38.7-1mdv (to install)
58- kernel-linus-source-3.0.3-5mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
59- kernel-linus-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The
kernel-linus devel files for 3rdparty modules build (to install)
60- kernel-rsbac-desktop-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-desktop-3.0.4-1mdv (to install)
61- kernel-rsbac-server-devel-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The
kernel-devel files for kernel-rsbac-server-3.0.4-1mdv (to install)
62- kernel-rsbac-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The Linux
source code for kernel-rsbac-3.0.4-1mdv (to install)
63- kernel-linus-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
What is your choice? (1-63)


Sorry for any word-wrapping my mail program may have done there. My
question at this point it two-fold: One, why does it think it needs to
install every possible version of the kernel that there is, and two, how
do I get it to stop $#@!ing trying to do so?

My system is kind-of running, though boot up showed a number of errors.
Some stuff is new, some stuff is old, and I'm running on the current
kernel (kernel-desktop-2.6.33.7-2mnb-1-1mnb2) that 2010.2 has in place,
rather than the newer kernel (kernel-desktop-2.6.38.7-1mnb2-1-1) for
2011, because any attempt to boot that up at this point just causes a
kernel panic and a paperweight where my Linux box used to be. :-)

I even tried doing a "rpm --rebuilddb" to see if maybe it was an issue
with the rpm database, but to no avail. I really don't relish the idea
of installing every possible version (and -devel) of the kernel. I'm
not sure what that would do, and I'd really like to NOT have it install
other programs based on a randomly-selected kernel that I'm only going
to try to remove once the upgrade is over with in order to reclaim disk
space since I really don't need 84 kernels on my system (not that I'm
sure my rather small /boot partition could hold them all, anyway).

Any ideas how to clean up this mess? I'd prefer to not have to just
boot from a downloaded CD and have it do a clean install from the local
.rpm files on my system (restoring settings for things under /etc isn't
my idea of a good time) if I can avoid it.

So, anyone to the rescue? :-)

--Dave

[Brian Schroeder]

Post by David Guntner
Easy upgrade from 2010.1 (well, .2 really) to 2011, my ass. :-)
I had a mess of problems trying to get urpmi to update, so I managed to
finally force it to update urpmi & supporting programs upgraded.
urpmi --auto-update --replacefiles -v

Hi David,

I recently did an upgrade from 2010.2 to 2011. This was the worst
upgrade I have ever experienced! It was painful. Running a standard
boot-install and selecting the upgrade option died before it started.

I didn't get the same errors as you but what I had to do was repeated
applications of

urpmi --auto-update --replacefiles -v

and the gui installer - switching from one to the other whenever I
seemed to run into a brick wall. There were also certain packages that
would not update and which caused major dependency issues. What I had
to do in these cases was to

rpm -e --nodeps OLD_PACKAGE
urpmi NEW_PACKAGE

Sometimes there were problems with this too, and then it would be back
to the command-line/gui install roundabout a few more times and then
urpmi NEW_PACKAGE again.


Eventually I managed to get past all the dependency issues, and
"urpmi --auto-update --replacefiles -v" worked properly to run through
all the rest.

Once that was all done, it was a matter of listing all the 2009 and
2010 packages and one at a time try to remove them. If they just
disappeared then fine. If they threw up 2011 package dependencies I
then had to get that sorted.

Oh, and before I started I downloaded most of the directory tree from
my local mirror onto a 1T USB disk to install from. And I also needed
"rpm --rebuilddb" at one stage too.

As you may imagine, I was actually quite surprised when I got
everything working in the end.

I know this doesn't exactly answer your questions, but I hope it will
help you with your upgrade.

Brian.

[Jim Beard]

Post by David Guntner
urpmi --auto-update --replacefiles -v

Why --replacefiles? This is generally needed when replacing a
newer package with an old one. Other than that, I would want to
see the error messages that would result, rather than have urpmi
or rpm automatically replace files of one package with those of
another.

Post by David Guntner
would install instead of upgrade package
kernel-xen-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64

This "would install" I think is simply a change in the rpm build
system, to make clear that a new kernel will not be an upgrade
(accompanied by removal of the "now-obsolete"kernel) but an
install of a new kernel. I am not sure if urpmi actually intends
to install all the kernels listed.

Post by David Guntner
getting exclusive lock on rpm
In order to satisfy the
'kernel-rsbac-desktop-devel-3.0.1-1mdv|kernel-server-devel-2.6.38.7-1mnb2|kernel-linus-source-2.6.39.3-3mdv|kernel-tmb-server-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-4mdv|kernel-rsbac-source-3.0.1-1mdv|kernel-linus-devel-3.0.0-3mdv|kernel-linus-source-3.0.3-5mdv|kernel-linus-source-3.0.4-1mdv|kernel-rsbac-server-devel-2.6.38.8-1mdv|kernel-linus-devel-3.0.0-2mdv|kernel-linus-source-3.0.0-1mdv|kernel-linus-devel-2.6.39.3-3mdv|kernel-netbook-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.1-0.1.3mdv|kernel-rsbac-source-2.6.38.7-2mdv|kernel-tmb-source-2.6.38.7-1mdv|kernel-tmb-desktop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-5mdv|kernel-openvz-devel-2.6.26-1.openvz1.1mdv|kernel-linus-source-2.6.38.7-1mdv|kernel-xen-devel-2.6.32.11-2mdv|kernel-vserver-devel-2.6.22.19-1mdv|kernel-openvz-sou

rce-2.6.26-1.openvz1.1mdv|kernel-linus-devel-3.0.2-3mdv|kernel-kerrighed-source-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-source-3.0.2-1mdv|kernel-linus-source-3.0.1-0.1.3mdv|kernel-linus-source-
3

Post by David Guntner
.0.2-3mdv|kernel-source-2.6.38.7-1mnb2|kernel-netbook-source-2.6.38.7-1mdv|kernel-kerrighed-devel-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-1mdv|kernel-rsbac-server-devel-3.0.1-1mdv|kernel-rsbac-server-devel-3.0.4-1mdv|kernel-rt-source-2.6.33.6-1.rt26.1mdv|kernel-linus-devel-2.6.39.3-2mdv|kernel-rsbac-source-3.0.4-1mdv|kernel-linus-source-3.0.3-3mdv|kernel-linus-source-3.0.0-3mdv|kernel-linus-devel-3.0.0-1mdv|kernel-rsbac-server-devel-3.0.3-1mdv|kernel-rt-devel-2.6.33.6-1.rt26.1mdv|kernel-rsbac-server-devel-2.6.38.7-2mdv|kernel-tmb-laptop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.4-1mdv|kernel-rsbac-desktop-devel-2.6.38.8-1mdv|kernel-rsbac-desktop-devel-3.0.3-1mdv|kernel-xen-pvops-devel-2.6.32.11-2mdv|kernel-rsbac-server-devel-2.6.38.7-1mdv|kernel-linus-source-2.6.39.3

-2mdv|kernel-rsbac-source-2.6.38.8-1mdv|kernel-linus-devel-2.6.38.7-1mdv|kernel-rsbac-source-2.6.38.7-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-2mdv|kernel-linus-source-3.0.3-4mdv|kernel-linu
s-

Post by David Guntner
devel-3.0.3-3mdv|kernel-rsbac-desktop-devel-3.0.2-1mdv|kernel-linus-source-3.0.0-2mdv|kernel-rsbac-desktop-devel-3.0.4-1mdv|kernel-rsbac-source-3.0.3-1mdv|kernel-rsbac-server-devel-3.0.2-1mdv|kernel-vserver-source-2.6.22.19-1mdv'
1- kernel-xen-pvops-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64: XEN
kernel devel files (to install)

<snip>

Post by David Guntner
63- kernel-linus-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The source
code for the Linux kernel (to install)
What is your choice? (1-63)

One of the 63 choices listed must be selected IF you are to
install the rsbac kernel. I would assume you would not want the
rsbac kernel, so all would be irrelevant.

Post by David Guntner
Sorry for any word-wrapping my mail program may have done there. My
question at this point it two-fold: One, why does it think it needs to
install every possible version of the kernel that there is, and two, how

First, since you are updating, do you have an rsbac kernel
installed on the system? Something installed just to see what it
would do perhaps? If so, uninstalling that would seem in order.

Check also for a xen kernel. Maybe just take a look at all the
kernel packages currently installed to make sure what you have
already:

rpm -qa |grep kernel

If you find a bunch of stuff that shoulld not be there, you might
remove those, or perhaps as a temporary work-around for the
kernel problem edit /etc/urpmi/skip.list to include
kernel
or maybe *kernel* to make sure you get everything kernel-related.
Remember to remove that later, to allow updating the kernel
when that is needed.

Post by David Guntner
My system is kind-of running, though boot up showed a number of errors.
Some stuff is new, some stuff is old, and I'm running on the current
kernel (kernel-desktop-2.6.33.7-2mnb-1-1mnb2) that 2010.2 has in place,
rather than the newer kernel (kernel-desktop-2.6.38.7-1mnb2-1-1) for
2011, because any attempt to boot that up at this point just causes a
kernel panic and a paperweight where my Linux box used to be. :-)

Guessing you probably need to boot into run level 3 and use
XFdrake (as root) from the command line to install the
proprietary drivers for your video card.

Post by David Guntner
I even tried doing a "rpm --rebuilddb" to see if maybe it was an issue
with the rpm database, but to no avail.

For 2011/rpm5, I believe the command you need is
db51_recover -evh /var/lib/rpm

I vaguely remember a need to run some command twice to clean up
things that had gone awry. This may be the command that needed that.

I really don't relish the idea

Post by David Guntner
of installing every possible version (and -devel) of the kernel. I'm
not sure what that would do, and I'd really like to NOT have it install
other programs based on a randomly-selected kernel that I'm only going
to try to remove once the upgrade is over with in order to reclaim disk
space since I really don't need 84 kernels on my system (not that I'm
sure my rather small /boot partition could hold them all, anyway).

If you clean up the kernel packages on your system, update
everything else (using skip.list to ignore kernels), and get
x-windows working, you might try installing/uninstalling kernels
and associated packages using mcc, to make things easy.

Post by David Guntner
Any ideas how to clean up this mess? I'd prefer to not have to just
boot from a downloaded CD and have it do a clean install from the local
.rpm files on my system (restoring settings for things under /etc isn't
my idea of a good time) if I can avoid it.

Clean installs have clear advantages. Restoring something old
that will not work with the new can be problematic, so the
upgrade route is always a bit of a gamble.

Post by David Guntner
So, anyone to the rescue? :-)

Well, you have a few things to try.

Cheers!

jim b.

[Jim Beard]

Post by David Guntner
urpmi --auto-update --replacefiles -v

Why --replacefiles? This is generally needed when replacing a
newer package with an old one. Other than that, I would want to
see the error messages that would result, rather than have urpmi
or rpm automatically replace files of one package with those of
another.

Post by David Guntner
would install instead of upgrade package
kernel-xen-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64

This "would install" I think is simply a change in the rpm build
system, to make clear that a new kernel will not be an upgrade
(accompanied by removal of the "now-obsolete"kernel) but an
install of a new kernel. I am not sure if urpmi actually intends
to install all the kernels listed.

Post by David Guntner
getting exclusive lock on rpm
In order to satisfy the
'kernel-rsbac-desktop-devel-3.0.1-1mdv|kernel-server-devel-2.6.38.7-1mnb2|kernel-linus-source-2.6.39.3-3mdv|kernel-tmb-server-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-4mdv|kernel-rsbac-source-3.0.1-1mdv|kernel-linus-devel-3.0.0-3mdv|kernel-linus-source-3.0.3-5mdv|kernel-linus-source-3.0.4-1mdv|kernel-rsbac-server-devel-2.6.38.8-1mdv|kernel-linus-devel-3.0.0-2mdv|kernel-linus-source-3.0.0-1mdv|kernel-linus-devel-2.6.39.3-3mdv|kernel-netbook-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.1-0.1.3mdv|kernel-rsbac-source-2.6.38.7-2mdv|kernel-tmb-source-2.6.38.7-1mdv|kernel-tmb-desktop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.3-5mdv|kernel-openvz-devel-2.6.26-1.openvz1.1mdv|kernel-linus-source-2.6.38.7-1mdv|kernel-xen-devel-2.6.32.11-2mdv|kernel-vserver-devel-2.6.22.19-1mdv|kernel-openvz-so

urce-2.6.26-1.openvz1.1mdv|kernel-linus-devel-3.0.2-3mdv|kernel-kerrighed-source-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-source-3.0.2-1mdv|kernel-linus-source-3.0.1-0.1.3mdv|kernel-linus-source
-

3

Post by David Guntner
.0.2-3mdv|kernel-source-2.6.38.7-1mnb2|kernel-netbook-source-2.6.38.7-1mdv|kernel-kerrighed-devel-2.6.20.21-krg2.4.3-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-1mdv|kernel-rsbac-server-devel-3.0.1-1mdv|kernel-rsbac-server-devel-3.0.4-1mdv|kernel-rt-source-2.6.33.6-1.rt26.1mdv|kernel-linus-devel-2.6.39.3-2mdv|kernel-rsbac-source-3.0.4-1mdv|kernel-linus-source-3.0.3-3mdv|kernel-linus-source-3.0.0-3mdv|kernel-linus-devel-3.0.0-1mdv|kernel-rsbac-server-devel-3.0.3-1mdv|kernel-rt-devel-2.6.33.6-1.rt26.1mdv|kernel-rsbac-server-devel-2.6.38.7-2mdv|kernel-tmb-laptop-devel-2.6.38.7-1mdv|kernel-linus-devel-3.0.4-1mdv|kernel-rsbac-desktop-devel-2.6.38.8-1mdv|kernel-rsbac-desktop-devel-3.0.3-1mdv|kernel-xen-pvops-devel-2.6.32.11-2mdv|kernel-rsbac-server-devel-2.6.38.7-1mdv|kernel-linus-source-2.6.39.

3-2mdv|kernel-rsbac-source-2.6.38.8-1mdv|kernel-linus-devel-2.6.38.7-1mdv|kernel-rsbac-source-2.6.38.7-1mdv|kernel-rsbac-desktop-devel-2.6.38.7-2mdv|kernel-linus-source-3.0.3-4mdv|kernel-lin
u

s-

Post by David Guntner
devel-3.0.3-3mdv|kernel-rsbac-desktop-devel-3.0.2-1mdv|kernel-linus-source-3.0.0-2mdv|kernel-rsbac-desktop-devel-3.0.4-1mdv|kernel-rsbac-source-3.0.3-1mdv|kernel-rsbac-server-devel-3.0.2-1mdv|kernel-vserver-source-2.6.22.19-1mdv'
1- kernel-xen-pvops-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64: XEN
kernel devel files (to install)

<snip>

Post by David Guntner
63- kernel-linus-source-3.0.4-1mdv-1-1-mdv2011.0.x86_64: The
source
code for the Linux kernel (to install)
What is your choice? (1-63)

One of the 63 choices listed must be selected IF you are to
install the rsbac kernel. I would assume you would not want the
rsbac kernel, so all would be irrelevant.

Post by David Guntner
Sorry for any word-wrapping my mail program may have done
there. My
question at this point it two-fold: One, why does it think it
needs to
install every possible version of the kernel that there is, and two, how

First, since you are updating, do you have an rsbac kernel
installed on the system? Something installed just to see what it
would do perhaps? If so, uninstalling that would seem in order.
Check also for a xen kernel. Maybe just take a look at all the
kernel packages currently installed to make sure what you have
rpm -qa |grep kernel
If you find a bunch of stuff that shoulld not be there, you might
remove those, or perhaps as a temporary work-around for the
kernel problem edit /etc/urpmi/skip.list to include
kernel
or maybe *kernel* to make sure you get everything kernel-related.
Remember to remove that later, to allow updating the kernel when
that is needed.

Post by David Guntner
My system is kind-of running, though boot up showed a number of errors.
Some stuff is new, some stuff is old, and I'm running on the
current
kernel (kernel-desktop-2.6.33.7-2mnb-1-1mnb2) that 2010.2 has
in place,
rather than the newer kernel
(kernel-desktop-2.6.38.7-1mnb2-1-1) for
2011, because any attempt to boot that up at this point just
causes a
kernel panic and a paperweight where my Linux box used to be. :-)

Guessing you probably need to boot into run level 3 and use
XFdrake (as root) from the command line to install the
proprietary drivers for your video card.

Post by David Guntner
I even tried doing a "rpm --rebuilddb" to see if maybe it was
an issue
with the rpm database, but to no avail.

For 2011/rpm5, I believe the command you need is
db51_recover -evh /var/lib/rpm
I vaguely remember a need to run some command twice to clean up
things that had gone awry. This may be the command that needed that.
I really don't relish the idea

Post by David Guntner
of installing every possible version (and -devel) of the
kernel. I'm
not sure what that would do, and I'd really like to NOT have it install
other programs based on a randomly-selected kernel that I'm
only going
to try to remove once the upgrade is over with in order to
reclaim disk
space since I really don't need 84 kernels on my system (not
that I'm
sure my rather small /boot partition could hold them all, anyway).

If you clean up the kernel packages on your system, update
everything else (using skip.list to ignore kernels), and get
x-windows working, you might try installing/uninstalling kernels
and associated packages using mcc, to make things easy.

Post by David Guntner
Any ideas how to clean up this mess? I'd prefer to not have to
just
boot from a downloaded CD and have it do a clean install from
the local
.rpm files on my system (restoring settings for things under
/etc isn't
my idea of a good time) if I can avoid it.

Clean installs have clear advantages. Restoring something old
that will not work with the new can be problematic, so the
upgrade route is always a bit of a gamble.

Post by David Guntner
So, anyone to the rescue? :-)

Well, you have a few things to try.

Adding to the list, if you are having problems booting,
when the grub menu appears, hit Esc and then use e
to edit the boot parameters for the kernel you want.

Adding nokmsboot nomodeset 3 prior to the resume= parameter might
be useful. I personally eliminate any splash parameter, to
automatically get fully verbose listing of what grub is doing.

Cheers!

jim b.

[David Guntner]

Post by David Guntner
urpmi --auto-update --replacefiles -v

Why --replacefiles? This is generally needed when replacing a newer
package with an old one. Other than that, I would want to see the error
messages that would result, rather than have urpmi or rpm automatically
replace files of one package with those of another.

Because I made the mistake of following the release notes that Mandriva
had for the distribution. They also said to use --auto, which was
proving to be problematic so it got dropped.

Post by David Guntner
would install instead of upgrade package
kernel-xen-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64

This "would install" I think is simply a change in the rpm build system,
to make clear that a new kernel will not be an upgrade (accompanied by
removal of the "now-obsolete"kernel) but an install of a new kernel. I
am not sure if urpmi actually intends to install all the kernels listed.

Yea, I get that. :-) However, I don't really NEED to have every
possible version of the kernel installed on my system. Given that my
/boot partition is only 50M, I doubt there's room for them all, either.
<grin>

One of the 63 choices listed must be selected IF you are to install the
rsbac kernel. I would assume you would not want the rsbac kernel, so
all would be irrelevant.

There's the part that's weird. I'm not trying to install any of those,
nor are any of them currently installed on my system. So why it's
trying to install *any* of them is beyond me.

Post by David Guntner
Sorry for any word-wrapping my mail program may have done there. My
question at this point it two-fold: One, why does it think it needs to
install every possible version of the kernel that there is, and two, how

First, since you are updating, do you have an rsbac kernel installed on
the system?

Nope.

Something installed just to see what it would do perhaps?

Nope. :-)

If so, uninstalling that would seem in order.
Check also for a xen kernel. Maybe just take a look at all the kernel
rpm -qa |grep kernel

[***@janet ~]$ rpm -qa|egrep kernel
kernel-firmware-20100217-1mnb2
kernel-desktop-2.6.33.7-2mnb-1-1mnb2
kernel-firmware-extra-20100429-2mnb2
kernel-desktop-devel-2.6.33.7-2mnb-1-1mnb2
lib64kplatokernel7-2.2.2-1mdv2010.1
kernel-desktop-latest-2.6.38.7-1
kernel-desktop-2.6.38.7-1mnb2-1-1
kernel-desktop-devel-latest-2.6.38.7-1
kernel-desktop-devel-2.6.38.7-1mnb2-1-1

If you find a bunch of stuff that shoulld not be there, you might remove
those, or perhaps as a temporary work-around for the kernel problem edit
/etc/urpmi/skip.list to include
kernel
or maybe *kernel* to make sure you get everything kernel-related.
Remember to remove that later, to allow updating the kernel when that
is needed.

Post by David Guntner
My system is kind-of running, though boot up showed a number of errors.
Some stuff is new, some stuff is old, and I'm running on the current
kernel (kernel-desktop-2.6.33.7-2mnb-1-1mnb2) that 2010.2 has in place,
rather than the newer kernel (kernel-desktop-2.6.38.7-1mnb2-1-1) for
2011, because any attempt to boot that up at this point just causes a
kernel panic and a paperweight where my Linux box used to be. :-)

Guessing you probably need to boot into run level 3 and use XFdrake (as
root) from the command line to install the proprietary drivers for your
video card.

I was booting to runlevel 3 at the time. X wasn't involved. Like I
said, I can get the system up currently with the current 2010.2 kernel,
but the current 2011 kernel won't start up. I'm guessing that there's
other stuff which hasn't yet updated that the kernel needs to run.

Post by David Guntner
I even tried doing a "rpm --rebuilddb" to see if maybe it was an issue
with the rpm database, but to no avail.

For 2011/rpm5, I believe the command you need is
db51_recover -evh /var/lib/rpm
I vaguely remember a need to run some command twice to clean up things
that had gone awry. This may be the command that needed that.

I'll give that a try, thanks.

I really don't relish the idea

Post by David Guntner
of installing every possible version (and -devel) of the kernel. I'm
not sure what that would do, and I'd really like to NOT have it install
other programs based on a randomly-selected kernel that I'm only going
to try to remove once the upgrade is over with in order to reclaim disk
space since I really don't need 84 kernels on my system (not that I'm
sure my rather small /boot partition could hold them all, anyway).

If you clean up the kernel packages on your system, update everything
else (using skip.list to ignore kernels), and get x-windows working, you
might try installing/uninstalling kernels and associated packages using
mcc, to make things easy.

I've got X running at the moment. I was considering using the
MandrivaUpdate GUI at this point to deselect the kernels and see if that
would get me to the next step (along the lines of what Brian suggested
in his reply).

Post by David Guntner
Any ideas how to clean up this mess? I'd prefer to not have to just
boot from a downloaded CD and have it do a clean install from the local
.rpm files on my system (restoring settings for things under /etc isn't
my idea of a good time) if I can avoid it.

Clean installs have clear advantages. Restoring something old that will
not work with the new can be problematic, so the upgrade route is always
a bit of a gamble.

Sure, but in the past upgrades for Mandriva have gone so well in recent
releases. It's a shame this one turned into a disaster. I sure hope
they smooth out those problems for future releases.....

Post by David Guntner
So, anyone to the rescue? :-)

Well, you have a few things to try.

Yes I do... :-)

--Dave

[Jim Beard]

Post by David Guntner
kernel-firmware-20100217-1mnb2
kernel-desktop-2.6.33.7-2mnb-1-1mnb2
kernel-firmware-extra-20100429-2mnb2
kernel-desktop-devel-2.6.33.7-2mnb-1-1mnb2

********

Post by David Guntner
lib64kplatokernel7-2.2.2-1mdv2010.1

********

Post by David Guntner
kernel-desktop-latest-2.6.38.7-1
kernel-desktop-2.6.38.7-1mnb2-1-1
kernel-desktop-devel-latest-2.6.38.7-1
kernel-desktop-devel-2.6.38.7-1mnb2-1-1

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.

You later mention that you are using xfs and that may be a
problem. Basically, the xfs module has to be in the initrd image
used to boot, not just out on disk somewhere waiting to be loaded.

Dave Hodgins' instructions to deal with this are:

The /boot/initrd-??? file needs to be recreated
with the correct module. To do this, boot from an install
cd/dvd, mount the root filesystem and run the following ...

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

Note that after booting from the install disk, you have to select
"rescue system" or some such. Also, mkinitrd on a 2011 system
will use dracut to create the initrd, while mkinitrd-mkinitrd
will use the traditional mkinitrd to create it.

initrd-$version.img $version should look something like
initrd-3.1.0-rc8-1.1-desktop.img 3.1.0-rc8-1.1-desktop

Adjust as needed for the kernel you are creating the initrd for.

Cheers!

jim b.

[David Guntner]

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.

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

[***@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 <fwang-***@public.gmane.org>
URL : http://www.koffice.org/
Summary : Koffice 2 core library
Description :
Koffice 2 core library.
[***@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.
Basically, the xfs module has to be in the initrd image used to boot,
not just out on disk somewhere waiting to be loaded.
The /boot/initrd-??? file needs to be recreated
with the correct module. To do this, boot from an install cd/dvd, mount
the root filesystem and run the following ...
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
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... :-)

-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 27 Oct 22 20:30 initrd-2.6.38.7-desktop-1mnb2.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
Adjust as needed for the kernel you are creating the initrd for.

Thanks!

--Dave

[Jim Beard]

Post by David Guntner

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.

Heh. I guess I should have pointed that out; it gave me a "WTF is
that?" moment too, when I first saw it.
Name : lib64kplatokernel7
Version : 2.2.82
Release : 2mdv2011.0
Group : System/Libraries
Size : 1203632 Architecture: x86_64
n6.mandriva.com
URL : http://www.koffice.org/
Summary : Koffice 2 core library
Koffice 2 core library.
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.
Basically, the xfs module has to be in the initrd image used to boot,
not just out on disk somewhere waiting to be loaded.
The /boot/initrd-??? file needs to be recreated
with the correct module. To do this, boot from an install cd/dvd, mount
the root filesystem and run the following ...
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
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... :-)

Actually, the old kernel should make no difference. You will
have the new mkinitrd or dracut, and it will look at the modules
for the new kernel, so it matters not which kernel is running at
the time.

Hence, no need to resort to the rescue-mode install disk.

Post by David Guntner

-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 27 Oct 22 20:30 initrd-2.6.38.7-desktop-1mnb2.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.

With a 27 byte initrd, it is hardly surprising that the system
would not boot.

Post by David Guntner
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?

I have found the dracut initrds are a bit larger than the
mkinitrds, but I find no difference in how they behave. Those
interested in such things claim the dracut software is
technically superior, but it has not been in use as long and may
harbor undetected bugs.

Post by David Guntner

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

Cheers!

jim b.

[David Guntner]

Actually, the old kernel should make no difference. You will have the
new mkinitrd or dracut, and it will look at the modules for the new
kernel, so it matters not which kernel is running at the time.
Hence, no need to resort to the rescue-mode install disk.

Cool.

Post by David Guntner

-rw------- 1 root root 9386626 Oct 9 2010
initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 27 Oct 22 20:30
initrd-2.6.38.7-desktop-1mnb2.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.

With a 27 byte initrd, it is hardly surprising that the system would not
boot.

Yea, kinda what I was thinking. :-) Weird that doing a urpmi
kernel-desktop-latest would result in such a borked initrd image file....

Need 'inst' function, try setting PLYMOUTH_POPULATE_SOURCE_FUNCTIONS to a file that defines it
-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 3346099 Oct 23 10:17 initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd-desktop.img -> initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd.img -> initrd-2.6.38.7-desktop-1mnb2.img

Is that "Need 'inst' function" message anything I really need to worry
about at this point?

The initrd is certainly smaller than the current one. I'll post later
if it worked in getting me up and running on the new kernel; and then I
can go back to trying to get the rest of the 9 million packages upgraded
to 2011....

Post by David Guntner
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?

I have found the dracut initrds are a bit larger than the mkinitrds, but
I find no difference in how they behave. Those interested in such
things claim the dracut software is technically superior, but it has not
been in use as long and may harbor undetected bugs.

Thanks.

--Dave

[David Guntner]

Post by David Guntner

Need 'inst' function, try setting PLYMOUTH_POPULATE_SOURCE_FUNCTIONS to a file that defines it
-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 3346099 Oct 23 10:17 initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd-desktop.img -> initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd.img -> initrd-2.6.38.7-desktop-1mnb2.img

Is that "Need 'inst' function" message anything I really need to worry
about at this point?
The initrd is certainly smaller than the current one. I'll post later
if it worked in getting me up and running on the new kernel; and then I
can go back to trying to get the rest of the 9 million packages upgraded
to 2011....

Ok, after that, I discovered that dracut hadn't yet been installed in
the aborted --auto-update mode. Manually installed it and then ran the
command again. This time I got a considerably larger initrd file....

Post by David Guntner
-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 27555778 Oct 23 18:46 initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd-desktop.img -> initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd.img -> initrd-2.6.38.7-desktop-1mnb2.img

However, still no love on rebooting into the 2.6.38.7 kernel. It goes
so far and then panics again. Last thing on my screen before it does a

Post by David Guntner
uncompression error
VFS: Cannot open root device "UUID=55d60848-4e89-48d4-98fb-9e91089320fe" or unknown-block(0,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swaper Not tainted 2.6.38.7-desktop-1mnb2 #1

My lilo.conf file points "root=" to exactly the same place for both kernels.

Post by David Guntner
I: *** Including module: dash ***
I: *** Including module: i18n ***
I: *** Including module: rpmversion ***
I: *** Including module: network ***
W: Possible missing firmware "atmel_at76c506.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c506-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504a_2958.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504a_2958-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504_2958.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504_2958-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502_3com.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502_3com-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502e.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502e-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502d.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502d-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "iwmc3200wifi-lmac-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "iwmc3200wifi-calib-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "iwmc3200wifi-umac-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "symbol_sp24t_sec_fw" for kernel module "orinoco.ko"
W: Possible missing firmware "symbol_sp24t_prim_fw" for kernel module "orinoco.ko"
W: Possible missing firmware "prism_ap_fw.bin" for kernel module "orinoco.ko"
W: Possible missing firmware "prism_sta_fw.bin" for kernel module "orinoco.ko"
W: Possible missing firmware "isl3890" for kernel module "prism54.ko"
W: Possible missing firmware "isl3886" for kernel module "prism54.ko"
W: Possible missing firmware "isl3877" for kernel module "prism54.ko"
W: Possible missing firmware "zd1201.fw" for kernel module "zd1201.ko"
W: Possible missing firmware "zd1201-ap.fw" for kernel module "zd1201.ko"
W: Possible missing firmware "ctfw_cna.bin" for kernel module "bna.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-09ax-6.0.17.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-09-6.0.17.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-mips-09-6.2.1.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-06-6.0.15.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-mips-06-6.2.1.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2x/bnx2x-e2-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "bnx2x/bnx2x-e1h-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "bnx2x/bnx2x-e1-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "rtl_nic/rtl8168d-2.fw" for kernel module "r8169.ko"
W: Possible missing firmware "rtl_nic/rtl8168d-1.fw" for kernel module "r8169.ko"
W: Possible missing firmware "cxgb3/t3fw-7.10.0.bin" for kernel module "cxgb3.ko"
W: Possible missing firmware "cxgb4/t4fw.bin" for kernel module "cxgb4.ko"
W: Possible missing firmware "myri10ge_rss_eth_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_rss_ethp_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_eth_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_ethp_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "phanfw.bin" for kernel module "netxen_nic.ko"
W: Possible missing firmware "phanfw.bin" for kernel module "qlcnic.ko"
W: Possible missing firmware "rt3090.bin" for kernel module "rt2860sta.ko"
W: Possible missing firmware "rt2860.bin" for kernel module "rt2860sta.ko"
W: Possible missing firmware "rt2870.bin" for kernel module "rt2870sta.ko"
W: Possible missing firmware "prism2_ru.fw" for kernel module "prism2_usb.ko"
I: *** Including module: ifcfg ***
I: *** Including module: plymouth ***
W: Possible missing firmware "radeon/SUMO_rlc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/PALM_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/PALM_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BTC_rlc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_pfp.bin" for kernel module "radeon.ko"
I: *** Including module: btrfs ***
I: *** Including module: crypt ***
I: *** Including module: dm ***
I: Skipping udev rule: 64-device-mapper.rules
I: *** Including module: dmsquash-live ***
I: *** Including module: kernel-modules ***
W: Possible missing firmware "aic94xx-seq.fw" for kernel module "aic94xx.ko"
W: Possible missing firmware "cbfw_fc.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_cna.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_fc.bin" for kernel module "bfa.ko"
I: *** Including module: mdraid ***
I: *** Including module: fcoe ***
I: *** Including module: nfs ***
I: *** Including module: resume ***
I: *** Including module: rootfs-block ***
I: *** Including module: terminfo ***
I: *** Including module: udev-rules ***
I: Skipping udev rule: 50-udev.rules
I: Skipping udev rule: 95-late.rules
I: *** Including module: aufs-mount ***
I: *** Including module: base ***
I: *** Including modules done ***
I: -rw------- 1 root root 27555194 Oct 23 19:08 /boot/initrd-2.6.38.7-desktop-1mnb2.img

I don't see anything that looks like a xfs module being listed there....

Any ideas?

--Dave

[Jim Beard]

Post by David Guntner

Post by David Guntner

Need 'inst' function, try setting PLYMOUTH_POPULATE_SOURCE_FUNCTIONS to a file that defines it
-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 3346099 Oct 23 10:17 initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd-desktop.img -> initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd.img -> initrd-2.6.38.7-desktop-1mnb2.img

Is that "Need 'inst' function" message anything I really need to worry
about at this point?
The initrd is certainly smaller than the current one. I'll post later
if it worked in getting me up and running on the new kernel; and then I
can go back to trying to get the rest of the 9 million packages upgraded
to 2011....

Ok, after that, I discovered that dracut hadn't yet been installed in
the aborted --auto-update mode. Manually installed it and then ran the
command again. This time I got a considerably larger initrd file....

Post by David Guntner
-rw------- 1 root root 9386626 Oct 9 2010 initrd-2.6.33.7-desktop-2mnb.img
-rw------- 1 root root 27555778 Oct 23 18:46 initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd-desktop.img -> initrd-2.6.38.7-desktop-1mnb2.img
lrwxrwxrwx 1 root root 33 Oct 22 20:30 initrd.img -> initrd-2.6.38.7-desktop-1mnb2.img

However, still no love on rebooting into the 2.6.38.7 kernel. It goes
so far and then panics again. Last thing on my screen before it does a

Post by David Guntner
uncompression error
VFS: Cannot open root device "UUID=55d60848-4e89-48d4-98fb-9e91089320fe" or unknown-block(0,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swaper Not tainted 2.6.38.7-desktop-1mnb2 #1

My lilo.conf file points "root=" to exactly the same place for both kernels.

Post by David Guntner
I: *** Including module: dash ***
I: *** Including module: i18n ***
I: *** Including module: rpmversion ***
I: *** Including module: network ***
W: Possible missing firmware "atmel_at76c506.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c506-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504a_2958.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504a_2958-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504_2958.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504_2958-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c504-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502_3com.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502_3com-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502e.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502e-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502d.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502d-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502.bin" for kernel module "atmel.ko"
W: Possible missing firmware "atmel_at76c502-wpa.bin" for kernel module "atmel.ko"
W: Possible missing firmware "iwmc3200wifi-lmac-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "iwmc3200wifi-calib-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "iwmc3200wifi-umac-sdio.bin" for kernel module "iwmc3200wifi.ko"
W: Possible missing firmware "symbol_sp24t_sec_fw" for kernel module "orinoco.ko"
W: Possible missing firmware "symbol_sp24t_prim_fw" for kernel module "orinoco.ko"
W: Possible missing firmware "prism_ap_fw.bin" for kernel module "orinoco.ko"
W: Possible missing firmware "prism_sta_fw.bin" for kernel module "orinoco.ko"
W: Possible missing firmware "isl3890" for kernel module "prism54.ko"
W: Possible missing firmware "isl3886" for kernel module "prism54.ko"
W: Possible missing firmware "isl3877" for kernel module "prism54.ko"
W: Possible missing firmware "zd1201.fw" for kernel module "zd1201.ko"
W: Possible missing firmware "zd1201-ap.fw" for kernel module "zd1201.ko"
W: Possible missing firmware "ctfw_cna.bin" for kernel module "bna.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-09ax-6.0.17.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-09-6.0.17.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-mips-09-6.2.1.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-rv2p-06-6.0.15.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2/bnx2-mips-06-6.2.1.fw" for kernel module "bnx2.ko"
W: Possible missing firmware "bnx2x/bnx2x-e2-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "bnx2x/bnx2x-e1h-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "bnx2x/bnx2x-e1-6.2.5.0.fw" for kernel module "bnx2x.ko"
W: Possible missing firmware "rtl_nic/rtl8168d-2.fw" for kernel module "r8169.ko"
W: Possible missing firmware "rtl_nic/rtl8168d-1.fw" for kernel module "r8169.ko"
W: Possible missing firmware "cxgb3/t3fw-7.10.0.bin" for kernel module "cxgb3.ko"
W: Possible missing firmware "cxgb4/t4fw.bin" for kernel module "cxgb4.ko"
W: Possible missing firmware "myri10ge_rss_eth_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_rss_ethp_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_eth_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "myri10ge_ethp_z8e.dat" for kernel module "myri10ge.ko"
W: Possible missing firmware "phanfw.bin" for kernel module "netxen_nic.ko"
W: Possible missing firmware "phanfw.bin" for kernel module "qlcnic.ko"
W: Possible missing firmware "rt3090.bin" for kernel module "rt2860sta.ko"
W: Possible missing firmware "rt2860.bin" for kernel module "rt2860sta.ko"
W: Possible missing firmware "rt2870.bin" for kernel module "rt2870sta.ko"
W: Possible missing firmware "prism2_ru.fw" for kernel module "prism2_usb.ko"
I: *** Including module: ifcfg ***
I: *** Including module: plymouth ***
W: Possible missing firmware "radeon/SUMO_rlc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/PALM_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/PALM_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/CAICOS_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/TURKS_pfp.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BTC_rlc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_mc.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_me.bin" for kernel module "radeon.ko"
W: Possible missing firmware "radeon/BARTS_pfp.bin" for kernel module "radeon.ko"
I: *** Including module: btrfs ***
I: *** Including module: crypt ***
I: *** Including module: dm ***
I: Skipping udev rule: 64-device-mapper.rules
I: *** Including module: dmsquash-live ***
I: *** Including module: kernel-modules ***
W: Possible missing firmware "aic94xx-seq.fw" for kernel module "aic94xx.ko"
W: Possible missing firmware "cbfw_fc.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_cna.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_fc.bin" for kernel module "bfa.ko"
I: *** Including module: mdraid ***
I: *** Including module: fcoe ***
I: *** Including module: nfs ***
I: *** Including module: resume ***
I: *** Including module: rootfs-block ***
I: *** Including module: terminfo ***
I: *** Including module: udev-rules ***
I: Skipping udev rule: 50-udev.rules
I: Skipping udev rule: 95-late.rules
I: *** Including module: aufs-mount ***
I: *** Including module: base ***
I: *** Including modules done ***
I: -rw------- 1 root root 27555194 Oct 23 19:08 /boot/initrd-2.6.38.7-desktop-1mnb2.img

I don't see anything that looks like a xfs module being listed there....
Any ideas?

This has gone beyond my level of incompetence. The problems
citing radeon are likely indicative of the problems I mentioned
much earlier with needing to boot to level 3 and then install the
proprietary driver using XFdrake, but the rest of the complaints
might as well be written in Greek so far as my understanding goes.

Just for grins, you might change to grub as your bootloader and
see if that makes a difference, but (never using lilo) I
speculate that if you ran lilo after creating the new initrd it
should know what it is doing. The install dvd should have an
option (maybe under rescue mode) to reinstall the bootloader if
you wish to try grub.

Sorry I cannot provide further help.

jim b.

[David Guntner]

This has gone beyond my level of incompetence. The problems citing
radeon are likely indicative of the problems I mentioned much earlier
with needing to boot to level 3 and then install the proprietary driver
using XFdrake, but the rest of the complaints might as well be written
in Greek so far as my understanding goes.

And just to make it even MORE bizarre, the only thing ATI in my system
is the CPU. The motherboard has a NVIDIA chipset on it, and my video
board is NVIDIA as well. So why it's even *thinking* about Radeon, I've
got no idea.

Just for grins, you might change to grub as your bootloader and see if
that makes a difference, but (never using lilo) I speculate that if you
ran lilo after creating the new initrd it should know what it is doing.
The install dvd should have an option (maybe under rescue mode) to
reinstall the bootloader if you wish to try grub.

*blink* You need to run Lilo again after running the mkinitrd program?

Ok, not that I'm expecting that to make any difference at this point
(given the luck I've been having so far), but I'll give it a shot.

Sorry I cannot provide further help.

Well, I certainly appreciate the help and information that you've
offered so far.

You know, if I *do* have to go the "reinstall the $#@!ing thing from a
DVD route because this current kernel has no way of dealing with xfs at
boot time, I just *might* consider doing a clean start and trying that
other Mandriva-like distribution.... :-) (I'm sure that statement will
give David Boles no end of amusement.... <grin>)

--Dave

[David Guntner]

Post by David Guntner
*blink* You need to run Lilo again after running the mkinitrd program?

And the answer to the above question is: I'm an idiot. :-)

Didn't even occur to me to try that. Duh. Well, after running it and

Post by David Guntner
Creating root device.
Mounting root filesystem.
XFS mounting filesystem sda5
Setting up other filesystems.
Switching to new root and running init.
Calling /sbin/tomoyo-init to load policy. Please wait.
184 domains. 5582 ACL entries.
You need to install userland programs for TOMOYO 2.3 and initialize policy configuration.
Please see http://tomoyo.sourceforge.jp/2.3/ for more information.
Kernel panic - not syncing: Profile version 0 is not supported.

Probably due to it not having updated tomoyo to the version being used
by 2011 yet. Decided I really don't need it for my situation anyway,
and removed it. Remembered to rerun lilo *this* time. :-) System is
up, although acting a bit oddly, video-wise. That's due to the X11
stuff still being 2010 as well as the older nvidia driver from 2010.
Once I get those updated, I suspect I'll get some better results.

And so it goes.... :-)

--Dave

[David Guntner]

Post by David Guntner
And so it goes.... :-)

And if I could just figure out *why* "urpmi --auto-update" wants to
install every single version of the kernel there is in the
repository..... :-)

--Dave

[Jim Beard]

Post by David Guntner

Post by David Guntner
And so it goes.... :-)

And if I could just figure out *why* "urpmi --auto-update" wants to
install every single version of the kernel there is in the
repository..... :-)

First, I don't think urpmi wants to install every single version.
I think it is asking for ONE of every single version available.
Pick one (of 63) and that will be enough.

My WAG (which could be way off) is that you still have something
related to tomoyo installed (if you are still getting the long list).

If you really feel adventurous, and have a bunch of room on the
partition where /var is located, you might try (as root, all on
one line of course)

urpmi --downloader wget --auto-update --auto --split-length=0 --test

Urpmi will check to see what you need and download it. Take a
look in /var/cache/urpmi/rpms and install whatever you want from
there. If you get 63 kernels, you can just delete the unwanted
ones (plus anything else you do not want) and then

urpmi /var/cache/urpmi/rpms/*

Cheers!

jim b.

[David Guntner]

Post by David Guntner
And if I could just figure out *why* "urpmi --auto-update" wants to
install every single version of the kernel there is in the
repository..... :-)

First, I don't think urpmi wants to install every single version. I
think it is asking for ONE of every single version available. Pick one
(of 63) and that will be enough.

Tried that once already. It just looped around and then wanted me to
pick one of 62. :-)

My WAG (which could be way off) is that you still have something related
to tomoyo installed (if you are still getting the long list).
If you really feel adventurous, and have a bunch of room on the
partition where /var is located, you might try (as root, all on one line
of course)
urpmi --downloader wget --auto-update --auto --split-length=0 --test
Urpmi will check to see what you need and download it. Take a look in
/var/cache/urpmi/rpms and install whatever you want from there. If you
get 63 kernels, you can just delete the unwanted ones (plus anything
else you do not want) and then
urpmi /var/cache/urpmi/rpms/*

Actually, I've got an rsync of one of the mirrors on my local hard
drive; I always do it that way when I'm upgrading full version since I
don't want to have to wait for downloads while doing it. It's got
everything current. And the stupid thing is still giving me that list.
I've got /^kernel/ in the skip.list file, so it's not going to actually
do anything; but I'd like to be rid of it altogether.

I've got the urpmi --auto-update running now and it seems to be going.
I already know I've got a few items that I'm gonna have to go back and
do manually since it said it couldn't upgrade them due to some missing
dependency or other. I'll have to see how that turns out. When it's
all done I'll again try removing the entry from skip.list and see if
it's *really* going to keep harping on me about the kernels.

I'll let you know how it turns out.... :-)

--Dave

[Jim Beard]

Post by David Guntner
I've got the urpmi --auto-update running now and it seems to be going.
I already know I've got a few items that I'm gonna have to go back and
do manually since it said it couldn't upgrade them due to some missing
dependency or other. I'll have to see how that turns out. When it's
all done I'll again try removing the entry from skip.list and see if
it's *really* going to keep harping on me about the kernels.

Have you run /usr/sbin/remove-unused-packages ?

Among other things, this should get rid of 40 or 50 locales that
you do not use (a few varieties of Chinese, etc). If you have
not run this command, you may have all available locales, and the
initrd for that is large, especially if created by dracut.

Do note that the removal may get carried away and you may have to
put some things back. It is highly recommended by most, though.
(I install into a 100GB partition, and let the installer add
all the localization/internationalization stuff that it is
willing to add, on the theory that a computer system worthy of
the name should support all commonly used languages by default.)

Cheers!

jim b.

[David Guntner]

Post by Jim Beard

Post by David Guntner
I've got the urpmi --auto-update running now and it seems to be going.
I already know I've got a few items that I'm gonna have to go back and
do manually since it said it couldn't upgrade them due to some missing
dependency or other. I'll have to see how that turns out. When it's
all done I'll again try removing the entry from skip.list and see if
it's *really* going to keep harping on me about the kernels.

Have you run /usr/sbin/remove-unused-packages ?
Among other things, this should get rid of 40 or 50 locales that you do
not use (a few varieties of Chinese, etc). If you have not run this
command, you may have all available locales, and the initrd for that is
large, especially if created by dracut.
Do note that the removal may get carried away and you may have to put
some things back. It is highly recommended by most, though. (I install
into a 100GB partition, and let the installer add all the
localization/internationalization stuff that it is willing to add, on
the theory that a computer system worthy of the name should support all
commonly used languages by default.)

I agree with you on that point. :-) But it definitely sounds useful for
saving space on my system, since I don't use any of those other
languages, nor does anyone who has access to it. :-)

I've been a little hesitant to run that command *just yet*. I've still
got one odd message when running the --auto-update that I haven't yet
been able to resolve (there were actually several to start with, but
apparently my big update yesterday and --auto-orphans took care of them,

Post by Jim Beard
lib64kexiv2_8-4.5.67-1mdv2011.0.x86_64 (due to unsatisfied libexiv2.so.9()(64bit))

As soon as that's resolved, I'll be running the command you mention above.

--Dave

[bschroeder-CkBdp7X+]

 
(replying via webmail - not the best)

You could try removing the package it is trying to upgrade.
(I assume that is lib64kexiv....)  Use urpme first to see what
dependencies there are and make a note of anything you consider
relevant.  Assuming that kicks up too much of a fuss, then do it
with   rpm -e --nodeps  followed by urpmi to install the current
version with dependencies taken care of.

I used variations of this idea to sort out a number of issues with
my upgrade.

Brian.

Post by David Guntner
lib64kexiv2_8-4.5.67-1mdv2011.0.x86_64 (due to unsatisfied

libexiv2.so.9()(64bit)) [1]

As soon as that's resolved, I'll be running the command you mention
above.

--Dave



Links:
------
[1] http://webmail.internode.on.net/http:

[David Guntner]

Oh, forgot to mention: I *decidedly* used mkinitrd-mkinitrd to avoid
dracut. The dracut-produced initrd is WAY too big for my situation;
I've got a 54M /dev/sda1-mounted /boot partition because I've never
needed a huge amount of space. With both kernels (2010 & 2011)
currently living there, it's 51% full. When dracut was used, the initrd
produced as so big that my /boot showed 95% full. Not good if I ever
want to put in a second one to boot off of before deleting the old
one... :-)

I'll be running update_alternatives to make that the default mkinitrd
being used from now on as well.... :-)

--Dave

[Jim Beard]

Post by David Guntner

Just for grins, you might change to grub as your bootloader and see if
that makes a difference, but (never using lilo) I speculate that if you
ran lilo after creating the new initrd it should know what it is doing.
The install dvd should have an option (maybe under rescue mode) to
reinstall the bootloader if you wish to try grub.

*blink* You need to run Lilo again after running the mkinitrd program?
Ok, not that I'm expecting that to make any difference at this point
(given the luck I've been having so far), but I'll give it a shot.

Lilo looks for the initrd to boot with by absolute address on the
disk. Rebuild the initrd, and the new one will not be written to
the exact same start address. Lilo will know nothing about it.

So yes, you have to run Lilo any time you tinker with your boot
setup.

Grub on the other hand goes looking for the initrd by name and
general location. If what it needs is there, it will find it.

Cheers!

jim b.

[David Guntner]

Post by Jim Beard

Post by David Guntner
I even tried doing a "rpm --rebuilddb" to see if maybe it was an issue
with the rpm database, but to no avail.

For 2011/rpm5, I believe the command you need is
db51_recover -evh /var/lib/rpm
I vaguely remember a need to run some command twice to clean up things
that had gone awry. This may be the command that needed that.

[***@janet ~ ]# db51_recover -evh /var/lib/rpm
Finding last valid log LSN: file: 25 offset 9644560
Recovery starting from [25][9642307]
Recovery complete at Sat Oct 22 09:35:42 2011
Maximum transaction ID 8000236b Recovery checkpoint [25][9646713]
[***@janet ~ ]#


Is that what the output from that command is supposed to look like?

--Dave

[David Guntner]

Ok, I've made a *slight* bit of headway, but am coming up weird.

The way/rate things are going, I'm getting closer to just throwing up my
hands, saying "frell this noise," and just burn a DVD image and do an
install and then put the online mirrors in place to install the stuff
that doesn't come on the DVD. It would be major time-consuming to do
all that and then reconfigure everything, etc., but I'm starting to
think it would take *less* time than this botched-up upgrade is taking
me.... (Mandriva, if any of your people are still watching this list, I
am SOOOOO disappointed with you on this one. After many updates where
they kept getting better and cleaner and easier to deal with, this one
is a HUGE step backwards. I really hope you fix this for the next
release....)

Thanks to the skip.list file (thanks, Jim), it's no longer trying to
install all those kernels, though it certainly still lists them like it
wants to. Running the urpmi --auto-update -replacefiles -v command
again gets me this far:

getting lock on urpmi
comparing
/var/mandriva/official/2011/x86_64/media/main/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Main/MD5SUM
medium "2011 Main" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/main/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Main Updates/MD5SUM
medium "2011 Main Updates" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/contrib/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib/MD5SUM
medium "2011 Contrib" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/contrib/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib Updates/MD5SUM
medium "2011 Contrib Updates" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/non-free/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Non-Free/MD5SUM
medium "2011 Non-Free" is up-to-date
comparing
/var/mandriva/official/2011/x86_64/media/non-free/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Non-Free Updates/MD5SUM
medium "2011 Non-Free Updates" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/main/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Main32/MD5SUM
medium "2011 Main32" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/main/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Main32 Updates/MD5SUM
medium "2011 Main32 Updates" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/contrib/release/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib32/MD5SUM
medium "2011 Contrib32" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/contrib/updates/media_info/MD5SUM
and /var/lib/urpmi/2011 Contrib32 Updates/MD5SUM
medium "2011 Contrib32 Updates" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/non-free/release/media_info/MD5SUM and
/var/lib/urpmi/2011 Non-Free32/MD5SUM
medium "2011 Non-Free32" is up-to-date
comparing
/var/mandriva/official/2011/i586/media/non-free/updates/media_info/MD5SUM and
/var/lib/urpmi/2011 Non-Free32 Updates/MD5SUM
medium "2011 Non-Free32 Updates" is up-to-date
examining synthesis file [/var/lib/urpmi/2011 Main/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Main
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Non-Free/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Non-Free
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Main32/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Main32
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib32/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Contrib32
Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011
Non-Free32/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/2011 Non-Free32
Updates/synthesis.hdlist.cz]
would install instead of upgrade package
kernel-xen-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-xen-devel-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-doc-2.6.38.7-1-mdv2011.0.noarch
would install instead of upgrade package
kernel-server-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-doc-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-source-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-pvops-doc-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-xen-pvops-source-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
would install instead of upgrade package
kernel-server-devel-2.6.38.7-1mnb2-1-1-mdv2011.0.x86_64
would install instead of upgrade package
kernel-xen-pvops-2.6.32.11-2mdv-1-1mdv2010.1.x86_64
[....]
would install instead of upgrade package
kernel-rsbac-desktop-3.0.3-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-server-3.0.3-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.3-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-desktop586-3.0.3-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-linus-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-linus-devel-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-linus-source-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-desktop586-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-desktop-devel-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-desktop586-devel-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-desktop-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-server-devel-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-source-3.0.4-1mdv-1-1-mdv2011.0.i586
would install instead of upgrade package
kernel-rsbac-server-3.0.4-1mdv-1-1-mdv2011.0.i586
getting exclusive lock on rpm
In order to satisfy the 'gwenhywfar-gui[== 4.1.0]' dependency, one of
the following packages is needed:
1- lib64gwengui-gtk2_0-4.1.0-2-mdv2011.0.x86_64: A multi-platform
helper library for other libraries (to install)
2- lib64gwengui-qt4_0-4.1.0-2-mdv2011.0.x86_64: A multi-platform helper
library for other libraries (to install)
What is your choice? (1-2) 2
Some requested packages cannot be installed:
lib64kexiv2_8-4.5.67-1mdv2011.0.x86_64 (due to unsatisfied
libexiv2.so.9()(64bit))
lib64kritaui7-2.2.82-2mdv2011.0.x86_64 (due to unsatisfied
libexiv2.so.9()(64bit))
libreoffice-core-3.4.2-2.1-mdv2011.0.i586 (due to unsatisfied
libgraphite2.so.2.0.0)
makedev-4.4-12-mdv2011.0.noarch (due to unsatisfied /usr/sbin/useradd[*])
plasma-applet-kimpanel-backend-scim-4.6.0-2-mdv2011.0.x86_64 (due to
unsatisfied plasma-applet-kimpanel[== 4.6.0])
x11-driver-input-evtouch-0.8.8-5-mdv2011.0.x86_64 (due to unsatisfied
xserver-abi(xinput-11)[>= 0])
Continue installation anyway? (Y/n) n
unlocking rpm database


I've looked around with urpmf and so on, but I can't seem to find
anything that supplies libexiv2.so.9 - I can find one that supplies
libkexiv2.so.9, but that's not the same thing and not going to make this
thing happy. Any ideas where I can get it or if I should just let the
system remove those packages or something else?

--Dave

[marek-+rQ6C//pQ3lmU8ui8W1pR+]

Hi

Thanks for your e-mail we will get back to you shortly. Alternatively please phone us at 083 795 4029 or 011 888 5856.

Marek Pawinski
Technical Sales Engineer
AMPPOL Electrical & IT
http://www.amppol-electrical.co.za
marek-+rQ6C//pQ3lmU8ui8W1pR+***@public.gmane.org
Tel: [phone]
Mobile: [phone]
Fax: [phone]

[marek-+rQ6C//pQ3lmU8ui8W1pR+]

Hi

Thanks for your e-mail we will get back to you shortly. Alternatively please phone us at 083 795 4029 or 011 888 5856.

Marek Pawinski
Technical Sales Engineer
AMPPOL Electrical & IT
http://www.amppol-electrical.co.za
marek-+rQ6C//pQ3lmU8ui8W1pR+***@public.gmane.org
Tel: [phone]
Mobile: [phone]
Fax: [phone]

[David Guntner]

Post by marek-+rQ6C//pQ3lmU8ui8W1pR+
Hi
Thanks for your e-mail we will get back to you shortly. Alternatively
please phone us at 083 795 4029 or 011 888 5856.

Really? Dude, you REALLY need to make your vacation auto-responder
smart enough to recognize and exempt mailing list traffic.... :-)

--Dave

[Marek Pawinski]

Post by David Guntner

Post by marek-+rQ6C//pQ3lmU8ui8W1pR+
Hi
Thanks for your e-mail we will get back to you shortly. Alternatively
please phone us at 083 795 4029 or 011 888 5856.

Really? Dude, you REALLY need to make your vacation auto-responder
smart enough to recognize and exempt mailing list traffic.... :-)
--Dave

I am not even subscribed to "Expert' with that e-mail address. This
Ananzi one has not been working for a week and i don't know what the
***@ck is going on between Evolution and Thunderbird running at the same
time with different e-mail address.