Re: 43p-140 install issues
On Wednesday 12 January 2005 18:03, Sven Luther wrote:
> On Wed, Jan 12, 2005 at 05:28:44PM +0100, Philippe Guyot wrote:
> > On Wednesday 12 January 2005 16:48, Sven Luther wrote:
> > > On Wed, Jan 12, 2005 at 04:14:58PM +0100, Philippe Guyot wrote:
> > > > I tried also boot net then load : ....console=tty0 noinitrd, hoping
> > > > it was able to find root as /dev/sda3 which exists now but always the
> > > > same:
> > > >
> > > > cannot open root device "<NULL>...."
> > > >
> > > > if load: ... root=/dev/sda3 we have
> > > >
> > > > cannot open root device "sda3..."
> > > >
> > > > just for fun load= ... root=/dev/scsi/.../part3 all the same
> > >
> > > This should not be, can you post the full kernel log please ?
> >
> > Here is the output on ttyS0:
> >
> > 0 > boot net
> > LOAD: Waiting 60 seconds for Spanning Tree
> > BOOTP R = 1 BOOTP S = 1
> > FILE: /tftpboot/vmlinuz-prep.initrd
> > Load Addr=0x1000000 Max Size=0x7000000
> > FINAL Packet Count = 10770 Final File Size = 5513751 bytes.
> >
> > loaded at: 01000400 01549FF4
> > relocated to: 00800000 00D49BF4
> > zimage at: 0080A94C 0093E4EC
> > initrd at: 0093F000 00D3F776
> > avail ram: 00400000 00800000
> >
> > Linux/PPC load: console=ttyS0,9600 console=tty0 noinitrd
> > root=/dev/scsi/host0/bus0/target0/lun0/part3
> >
> > Uncompressing Linux...done.
> > Now booting the kernel
> > Total memory = 128MB; using 256kB for hash table (at c0300000)
> > Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian
> > 1:3.3.5-5)) #1 Sat Jan 8 22:01:09 CET 2005
> > PReP architecture
> > IBM planar ID: 000000d5
> > MPIC at 0xfafc0000 (0x3afc0000), length 0x00040000 mapped to 0xeffc0000
> > Built 1 zonelists
> > Kernel command line: console=ttyS0,9600 console=tty0 noinitrd
> > root=/dev/scsi/host0/bus0/target0/lun0/part3
> > OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
> > PID hash table entries: 1024 (order 10: 8192 bytes)
> > time_init: decrementer frequency = 16.618043 MHz
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> > Memory: 122304k available (1732k kernel code, 1060k data, 164k init, 0k
> > highmem)
> > Calibrating delay loop... 231.93 BogoMIPS
> > Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> > checking if image is initramfs...it isn't (no cpio magic); looks like an
> > initrd
> > Freeing initrd memory: 4097k freed
> > NET: Registered protocol family 16
> > PCI: Probing PCI hardware
> > Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
> > PCI: Cannot allocate resource region 0 of device 0000:00:0b.0
> > PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
> > PCI: Cannot allocate resource region 0 of device 0000:00:10.0
> > PCI: Enabling device 0000:00:16.0 (0084 -> 0086)
> > matroxfb: Matrox Mystique 220 (PCI) detected
> > matroxfb: BIOS on your Matrox device does not contain powerup info
> > matroxfb: 640x480x8bpp (virtual: 640x3276)
> > matroxfb: framebuffer at 0xFC000000, mapped to 0xc9005000, size 2097152
> > fb0: MATROX frame buffer device
> > fb0: initializing hardware
> > matroxfb: Pixel PLL not locked after 5 secs
> > Thermal assist unit not available
> > audit: initializing netlink socket (disabled)
> > audit(1105541936.273:0): initialized
> > devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
> > devfs: boot_options: 0x0
> > Initializing Cryptographic API
> > Console: switching to colour frame buffer device 80x30
> > Generic RTC Driver v1.07
> > Macintosh non-volatile memory driver v1.1
> > Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
> > ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> > pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
> > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> > input: Macintosh mouse button emulation
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 33MHz system bus speed for PIO modes; override with
> > idebus=xx mice: PS/2 mouse device common for all mice
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 1024 buckets, 8Kbytes
> > TCP: Hash tables configured (established 8192 bind 16384)
> > VFS: Cannot open root device "scsi/host0/bus0/target0/lun0/part3" or
> > unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
> > <0>Rebooting in 180 seconds..
>
> Oh, i understand, you are trying to boot the d-i kernel, which won't do,
> since the initrd has not the modules on it.
>
> What you want is to boot the kernel on the disk's prep partition, not sure
> how this is done, but you may try something like :
>
> boot disk (or boot disc)
Yes of course, but remember, this doesn't work I presume because of the IO
error when dd'ing to /dev/scsi/........../part1. I reported this before.
And I was dding /boot/vmlinuz-2.6.8-powerpc, not the d-i kernel.
So I was trying netbooting.
>
> Alternatively, you can boot into d-i, and then chroot to your system,
> install ssh or another network client, and move /boot/vmlinuz-2.6.8-powerpc
> to your /tftpboot partition.
I should have think of that myself!
So this kernel should assume that root is /dev/sda3 (or /dev/scsi/.....)
right ?
>
> > > Seems like the scsi driver didn't get loaded or something,
> >
> > Any relationship with the PCI errors ?
> >
> > > can you check if
> > > it is present on the initrd ? mount -t cramfs /boot/initrd.img /mnt or
> > > something such should do.
> >
> > Just now I can't boot, I have to netboot and go reinstall until /target
> > will be available, no ?
>
> Yep.
>
> > And.. /boot/initrd.img is not a device, I don't see how to mount it.
>
> Ah, forgot -o loop, but this is not needed anymore, as we detected your
> problem, you where not using the installed kernel, but the debian-installer
> one, and thus altough it is the same kernel, using the wrong initrd.
I'll do it however, for my knowledge.
>
> Friendly,
>
> Sven Luther
Reply to: