Bug#233864: kbd-chooser crash - man-db error
Package: installation-reports
Debian-installer-version: netinst cd from http://people.debian.org/cdimage/
testing/daily/powerpc/20040219/
uname -a: Linux (none) 2.4.22-powerpc #1 Mon Feb 2 14:15:53 CET 2004 ppc
unknown
Date: 2004-02-20 12:00
Method: that's an oldworld machine, so: copied vmlinux in "/Dossier système/
Linux kernels" and root.bin in "/Dossier système/". I've booted the
installation with BootX (args: "video=atyfb:vmode:14,cmode:32 devfs=mount
DEBCONF_PRIORITY=medium" and "high".
Machine: Apple Powerbook Wallstreet II ('98) M4753
Processor: Sonnet G3@500 update processor card (replacing a 266MHz G3)
Memory: 192Mb
Root Device: ide, /dev/hda9
Root Size/partition table: just using /dev/hda9 and /dev/hda10 for swap (for
now)
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [ E]
Configure network HW: [ O]
Config network: [ O]
Detect CD: [ O]
Load installer modules: [ O]
Detect hard drives: [ O]
Partition hard drives: [ O]
Create file systems: [ O]
Mount partitions: [O ]
Install base system: [ E]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Initial boot: doesn't work on oldworld PPC. BootX works. Yeah, it's a known
problem. What about providing BootX in the cdrom and adding this hint to
debian-installer documentation?
kbd-chooser: crashes with "Configuring 'kbd-chooser' failed with error 139" on
tty4
Tried it with en_US and fr_FR
After a little fiddling, it appears to be a kernel/ramdisk image problem.
If I use the kernel from 20040219 netinst with 20040218 netinst cdrom, it
crashes.
If I use the kernel from 20040218 netinst with 20040219 netinst cdrom, it
works.
At the end of the base system installation, the installer fails with an error
127. In /var/log/messages:
dpkg:error processing man-db (--configure):
subprocess post-installation script returned error exit status 1
(...)
Errors were encountered while processing:
man-db
/usr/sbin/debootstrap: 1: sleep: not found
the "sleep not found" error might not be related...
Reply to: