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

Re: Bug#260154: PowerMac G3 (beige) sarge d-i Installation Report



On Mon, Jul 19, 2004 at 11:03:00PM +0100, Clive Menzies wrote:
> On (19/07/04 18:36), Sven Luther wrote:
> > On Mon, Jul 19, 2004 at 05:10:15PM +0100, Clive Menzies wrote:
> > > On (19/07/04 17:39), Sven Luther wrote:
> > > > On Sun, Jul 18, 2004 at 10:53:00PM +0100, Clive Menzies wrote:
> > > > > Package: installation-reports
> > > > > 
> > > > > Debian-installer-version: sarge powerpc tcl.1 9 June 2004
> > > > > uname -a: Linux Homer 2.4.25-powerpc #1 mer avr 14 15:38:38 CEST 2004
> > > > > ppc GNU/Linux
> > > > 
> > > > Could you have the 2.6 debian-installer a try also ?
> > > Hi Sven
> > > 
> > > As I reported, when I tried to boot the installer from initrd.gz and
> > > vmlinux from the 2.6 folder, I got a kernel panic - sorry I didn't note
> > > the exact error but it related to USB and my beige G3 doesn't have USB.
> > 
> > Notice that USB is modular, and should not be loaded or even attempted. Could
> > you try to install and boot a 2.6 kernel in your already installed system, and
> > debug it that way ? And fill a bug report against kerne-image-2.6.7-powerpc.
> Hi Sven
> 
> I should point out that I'm somewhat "out of my depth" with all this but
> nevetheless here is where I've got to:
> 
> I installed the 2.6.7-3 kernel, as requested, and I got the usual warning
> about putting initrd.img line in the boot loader.  I checked that the
> symlink was in /boot.  I rebooted into the Mac side and put the 2.6
> initrd.gz and vmlinux files into the Linux Kernels folder in the System
> Folder.  Appended "initrd=/boot/initrd.img" to the BootX's kernel
> arguments, rebooted into Linux and got the following error (I don't know
> how to extract any log messages from the machine and so I copied it):
> cannot open root device "hda6" or unknown block (0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unkown block (0,0)
> 
> I get the same error without appending the initrd argument

Ok, this usually means that your initrd doesn't has the right modules in it.
Please fill a bug report against initrd-tools about it.

> > > I'd be happy to acquire a USB/PCI card but that will take a little
> > > while.  Or is there another image you'd like me to try?
> > 
> > I don't think that is needed, see above.
> > 
> > > If you want me to try booting the 2.6 kernel again and record the error
> > > message, let me know.
> > 
> > Yes, please a full log output would be nice, i suppose that since 2.6.7-3, you
> > should be able to get a serial log on your old world box. This would be the
> > most perfect solution. But again, a bug report should go against the
> > kernel-image-2.6.7-powerpc package.
> I also tried to boot the installer (from the RamDisk option) using the
> 2.6 initrd.gz and vmlinux files and got the following (again I don't
> know how to get this serial log and so I copied it):
> umount: /initrd: Invalid argument
> cp: unable to link '/mnt/usr/share/discover/usb.lst': Operation not
> Permitted
> cp: unable to link to '/mnt/var/log/messages': Operation not Permitted
> Kernel panic: Attempted to kill init!
> <0> Rebooting in 180 seconds

Huh, that's a new one. 

> Do you want me to file all this as a bug against 2.6.7-3 or have I done
> something wrong?

Yes, please.

> Meanwhile, Colin has asked if I can try the quik installer and I've
> downloaded the daily build:
> sarge-powerpc-netinst.iso      18-Jul-2004 22:56   206M
> from
> http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/current/
> 
> and am trying to work out how to use the quik installer .... my brain hurts ;)

No idea about this one.

> Luckily I've got my trusty G4 to work on ;)

Hehe.

Friendly,

Sven Luther



Reply to: