Kernel-image update Probleme bei UCS 2.4 Sec2

german

#1

Hallo Univention Forum,

nach erfolgreichen Updates bis UCS 2.4-1-2
(als letztes wurde das Sec2 installiert)
wollte ich 2.4-2 installieren, dies wollte er aber nicht durchführen, da das Sec anscheinend doch nicht ganz installiert wurde, obwohl schon Systemstand 2.4-1-2 angezeigt wurde.

bei einem Ausführen von univention-actualise wird folgendes ausgegeben

root@server:# univention-actualise
Running apt-get update
Setting pkgdb/scan
File: /etc/apt/apt.conf.d/60invoke
File: /etc/apt/apt.conf.d/60invoke
Upgrading system
Setting up linux-image-2.6.18-ucs160-686 (2.6.18.dfsg.1-18.160.201011120945) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
initrd.img(/boot/initrd.img-2.6.18-ucs160-686
) points to /boot/initrd.img-2.6.18-ucs160-686
 (/boot/initrd.img-2.6.18-ucs160-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 588.
vmlinuz(/boot/vmlinuz-2.6.18-ucs160-686
) points to /boot/vmlinuz-2.6.18-ucs160-686
 (/boot/vmlinuz-2.6.18-ucs160-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 588.
You already have a LILO configuration in /etc/lilo.conf
Do we really want to run bootloader lilo?
Error setting debconf flags in shared/kernel-image/really-run-bootloader: Unsupported command "bootsplash" (full line was "Bootsplash disabled. (see /etc/default/bootsplash)") received from confmodule. at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 1246, <STDIN> line 3.
dpkg: error processing linux-image-2.6.18-ucs160-686 (--configure):
 subprocess post-installation script returned error exit status 9
dpkg: dependency problems prevent configuration of univention-kernel-image-2.6.18:
 univention-kernel-image-2.6.18 depends on linux-image-2.6.18-ucs160-686; however:
  Package linux-image-2.6.18-ucs160-686 is not configured yet.
dpkg: error processing univention-kernel-image-2.6.18 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.18-ucs160-686
 univention-kernel-image-2.6.18
E: failed to configure packets, see /var/log/univention/actualise.log for details.
Setting pkgdb/scan
File: /etc/apt/apt.conf.d/60invoke
File: /etc/apt/apt.conf.d/60invoke
Reading package lists... Done
Building dependency tree
Reading state information... Done

/var/log/univention/actualise.log

Reading package lists... Setting up linux-image-2.6.18-ucs160-686 (2.6.18.dfsg.1-18.160.201011120945) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. initrd.img(/boot/initrd.img-2.6.18-ucs160-686 ) points to /boot/initrd.img-2.6.18-ucs160-686 (/boot/initrd.img-2.6.18-ucs160-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 588. vmlinuz(/boot/vmlinuz-2.6.18-ucs160-686 ) points to /boot/vmlinuz-2.6.18-ucs160-686 (/boot/vmlinuz-2.6.18-ucs160-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 588. You already have a LILO configuration in /etc/lilo.conf Do we really want to run bootloader lilo? Error setting debconf flags in shared/kernel-image/really-run-bootloader: Unsupported command "bootsplash" (full line was "Bootsplash disabled. ( see /etc/default/bootsplash)") received from confmodule. at /var/lib/dpkg/info/linux-image-2.6.18-ucs160-686.postinst line 1246, <STDIN> line 3. dpkg: error processing linux-image-2.6.18-ucs160-686 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of univention-kernel-image-2.6.18: univention-kernel-image-2.6.18 depends on linux-image-2.6.18-ucs160-686; however: Package linux-image-2.6.18-ucs160-686 is not configured yet. dpkg: error processing univention-kernel-image-2.6.18 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-ucs160-686 univention-kernel-image-2.6.18 ***** Starting univention-actualise at Thu Dec 1 12:20:37 2011


#2

Hallo,

dieses Verhalten kann auf älteren Systemen bei der Verwendung von Lilo auftreten.
Folgender SDB-Artikel sollte Ihre Fragen beantworten.

Mit freundlichen Grüßen,
Tim Petersen


#3

Danke, das hat problemfrei funktioniert