Bug#264963: Installation report for Apple Blue & White G3 400 from netinstall CD (powerpc, RC1)

[Sven Luther <sven.luther@wanadoo.fr>]

On Wed, Aug 11, 2004 at 07:15:28PM -0500, Evilpig wrote:
> On Wed, 11 Aug 2004 18:35:27 +0100, Colin Watson <cjwatson@debian.org> wrote:
> > It's not in the lspci output because it's not a PCI card.
> > 
> > I thought I'd fixed this one, so I'd like the reporter to show me the
> > output of the following two commands, which you should be able to run on
> > tty2:
> > 
> >   ls -l "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac"
> > 
> >   find "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)" -type f -name compatible | xargs grep bmac
> > 
> > If the second command gives you a filename, I'd also like to see what's
> > in the device_type file in the same directory.
> 
> I will gladly do this as soon as I am able to boot into Debian.  I
> thought maybe I could do this from the installer after telling it to
> load the bmac driver, but no such luck.  The first command gave me "No
> such file or directory" (also a "find /proc -name bmac" turns up
> nothing).
> 
> As instructed, I added the pcilynx module to /etc/hotplug/blacklist
> and "skip pcilynx" to /etc/discover.conf.  Unfortunately, I was not
> able to do this by booting "Linux emergency".  Although it did
> successfully boot up that way, my keyboard didn't work, so was unable
> to do anything at all.  My guess is that it doesn't load the USB
> modules (which would be problematic since that is the only type of
> keyboard that this machine can be used with...).

Well, the same happens on my pegasos with ps/2 keyboard. I suppose that
mkinitrd should add at least the keyboard modules to the initrd, which is nice
to have when a manual fsck is needed. Maybe you could provide a followup to
bug report #264839 ?

Friendly,

Sven Luther