On Mon, Mar 15, 2004 at 02:58:38PM +0000, Colin Watson wrote: > Package: installation-reports > > INSTALL REPORT > > Debian-installer-version: 20030413, > http://gluck.debian.org/cdimage/testing/daily/powerpc/
I retested with the 20030418 businesscard image, installing from unstable in order to get the new 2.4.25-3 kernel-images. Here are some updates. > kbd-chooser didn't work, and segfaulted when run from tty2; I expected > this, since it's probably #234513 fixed in 0.44 and the CD only had > 0.42. I can use qwerty/us without too many problems, so that wasn't a > killer. kbd-chooser didn't segfault now, but: Mar 19 01:15:47 (none) user.info kbd-chooser[339]: INFO: Setting debian-installer/serial-console to false Mar 19 01:15:47 (none) user.info kbd-chooser[339]: INFO: Setting debian-installer/serial-console to false Mar 19 01:15:47 (none) user.info kbd-chooser[339]: INFO: choose_keymap: keymap = Mar 19 01:15:47 (none) user.info kbd-chooser[339]: INFO: kbd_chooser: setting keymap Mar 19 01:15:47 (none) user.alert kbd-chooser[339]: ERROR **: kbd-chooser: cannot open file Mar 19 01:15:47 (none) user.warn main-menu[216]: WARNING **: Configuring 'kbd-chooser' failed with error code 1 Mar 19 01:15:47 (none) user.warn main-menu[216]: WARNING **: Menu item 'kbd-chooser' failed. > partman couldn't recognize my partition table (partman/unknown_label). I > guess this was the bug fixed in partman 25, so I'll try a newer image as > soon as I get the chance. Fixed, same as in the 20040315 netinst. > yaboot-installer didn't work because libdebian-installer's > subarchitecture-checking support is broken, so I didn't get a boot > loader. Bastian Blank found the problem after I mentioned this on IRC; > yaboot-installer 0.0.13.1 has removed the subarchitecture field for now. This worked, although I still had to remove /var/lib/dpkg/info/yaboot-installer.isinstallable part-way through the install (#238208). I had to tell anna to select yaboot-installer manually. Why? Does it need to be Priority: standard? > I haven't yet tried the second stage, mostly because I forgot the runes > to make my already-installed yaboot use a different partition and > couldn't be bothered to dredge them up. :) This time yaboot-installer worked flawlessly (in fact I was asleep when it ran, I think ...), and the second stage seemed to work fine. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
