[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#246770: PowerMac 7200 install report - not entirely easy

On Sat, May 01, 2004 at 12:13:15AM +0100, Jonathan McDowell wrote:
> However there was nothing viewable on tty 3 or 4 (where I'd expect the
> logs to be based on i386 + m68k installs). I was able to view these by
> cat /dev/vcc/{3,4} on tty 2; I assume it was some issue in setting up the
> framebuffer? tty 2 had dark blue writing rather than the white I'd
> expect. 

All strange, and nothing I recognize ...

> Gets 70% through installing the base system and hits a problem. Looking
> at tty 3 it's an issue with installing the kernel to the HD.
> "You are attempting to install an initrd kernel image (version
> 2.4.25-powerpc-small)
> This will not working unless you have configured your boot loader to use
> initrd. (An initrd image is a kernel image that expects to use an
> INITial Ram Disk to mount a minimal root file system into RAM and use
> that for booting).
> I repeat, You need to configure your boot loader -- please read your
> bootloader documentation for details on how to add initrd images.
> If you have already done so, and you wish to get rid of this message,
> please put
>   `do_initrd = Yes'
> in /etc/kernel-img.conf. Not this is optional, but if you do not,
> you'll continue to see this message whenever you install a kernel
> image image using initrd.
> Do you want to stop not? [Y/n]Ok, Aborting.
> dpkg: error processing /cdrom/pool/main/k/kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-powerpc-small-pmac_2.4.25-4_powerpc.deb (--unpack)
> "

Ugh. Hello, screaming nightmare. It's unduly painful to have initrd
kernels for some subarchitectures but not others, because you only get
to specify a default at build-time in rootskel, i.e. one choice per

Sven, how about initrd support in all powerpc 2.4 kernels? :-) It seems
to work fairly happily for 2.6 now, with trunk of everything relevant in
d-i ...

> Running base-config it assumed my keyboard was USB; it's not, it's ADB.
> I wasn't asked about this and it meant I had to change from alt to
> option for switching VTs (at the very least; I haven't noticed any other
> broken keys yet).

I think that's just conflation of hardware and keymap. You do *not* want
an ADB keymap, trust me ...


Colin Watson                                  [cjwatson@flatline.org.uk]

Reply to: