Re: 43p-140 install issues
On Tuesday 11 January 2005 13:19, Sven Luther wrote:
> On Mon, Jan 10, 2005 at 04:59:31PM +0100, Philippe Guyot wrote:
> > On Monday 10 January 2005 11:42, Philippe Guyot wrote:
> > > On Monday 10 January 2005 11:44, Sven Luther wrote:
> > > > On Mon, Jan 10, 2005 at 11:27:02AM +0100, Philippe Guyot wrote:
> > > > > On Thursday 06 January 2005 15:33, you wrote:
> > > > > > On Thursday 06 January 2005 14:57, you wrote:
> > > > > > > On Thu, Jan 06, 2005 at 12:19:46PM +0100, Philippe Guyot wrote:
> > > > > > > > On Wednesday 05 January 2005 12:41, you wrote:
> > > > > > > > > On Wed, Jan 05, 2005 at 10:31:35AM +0100, Philippe Guyot
wrote:
> > > > > > > > > > On Tuesday 04 January 2005 19:21, you wrote:
> > > > > > > > > > > Ok, so you got a 43P-140 (Tiger1), good to know.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I only have trouble with device 0000:00:01.1, which is
> > > > > > > > > > > the SL82C105 ide chip, but as i have no connector for
> > > > > > > > > > > those anyway, it is not troublesomoe.
> > > > > > > > > >
> > > > > > > > > > I think this box hasn't a real ide device, as far as I
> > > > > > > > > > can see. disks, cdrom,tape are on scsi.
> > > > > > > > >
> > > > > > > > > Ah, but then what are those other devices ?
> > > > > > > >
> > > > > > > > If this can help, output of lspci:
> > > > > > > > > > > > PCI: Cannot allocate resource region 0 of device
> > > > > > > > > > > > 0000:00:0b.0
> > > > > > > >
> > > > > > > > 00:0b.0 ISA bridge: IBM Fire Coral (rev 03)
> > > > > > > >
> > > > > > > > > > > > PCI: Cannot allocate resource region 0 of device
> > > > > > > > > > > > 0000:00:0c.0
> > > > > > > >
> > > > > > > > 00:0c.0 Ethernet controller: Advanced Micro Devices [AMD]
> > > > > > > > 79c970 [PCnet LANCE] (rev 16)
> > > > > > > >
> > > > > > > > > > > > PCI: Cannot allocate resource region 0 of device
> > > > > > > > > > > > 0000:00:10.0
> > > > > > > >
> > > > > > > > 00:10.0 SCSI storage controller: LSI Logic / Symbios Logic
> > > > > > > > (formerly NCR)
> > > > > > >
> > > > > > > So these three are baddly mapped, at least
> > > > > > >
> > > > > > > > > > > > PCI: Cannot allocate resource region 1 of device
> > > > > > > > > > > > 0000:00:12.0 PCI: Cannot allocate resource region 2
> > > > > > > > > > > > of device 0000:00:12.0
> > > > > > > >
> > > > > > > > 53c825 (rev 13)
> > > > > > > > 00:12.0 Communication controller: Synaptel: Unknown device
> > > > > > > > 0111 (rev b1)
> > > > > > >
> > > > > > > No idea why there are two ressource regions here though. No
> > > > > > > idea whay this synaptel part is anyway.
> > > > > >
> > > > > > This is an X25 communication card.
> > > > > > It seems make no problem for woody when booting.
> > > > > > I don't really have plans to use it, I may remove it from the
> > > > > > box.
> > > > >
> > > > > So did I.
> > > > > I tested again this morning, netbooting
> > > > > /~luther/d-i/images/daily/powerpc/netboot/vmlinuz-prep.initrd (08
> > > > > jan 22:01).
> > > > >
> > > > > as previously, mapping problem it seems:
> > > > >
> > > > > 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
> > > > >
> > > > > of course those errors disapear because of synaptel out of the box:
> > > > > > > > > PCI: Cannot allocate resource region 1 of device
> > > > > > > > > 0000:00:12.0 PCI: Cannot allocate resource region 2 of
> > > > > > > > > device 0000:00:12.0
> > > >
> > > > As expected.
> > > >
> > > > > and the same final VFS problem:
> > > > >
> > > > > RAMDISK: Compressed image found at block 0
> > > > > VFS: Mounted root (cramfs filesystem) readonly.
> > > > > VFS: Cannot open root device "<NULL>" or unknown-block(8,3)
> > > > > Please append a correct "root=" boot option
> > > > > Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
> > > > > <0>Rebooting in 180 seconds..
> > > > >
> > > > > Just for testing purposes, if it could help a little
> > > > >
> > > > > linux/ppc load: console=ttyS0,9600 root=/dev/sda2 (woody)
> > > > > VFS: Cannot open root device "sda2"
> > > >
> > > > What kernel was that again ?
> > >
> > > /~luther/d-i/images/daily/powerpc/netboot/vmlinuz-prep.initrd (08 jan
> > > 22:01).
> > >
> > > > I think you have a serious pci irq mapping
> > > > trouble, which need to be fixed. Could you investigate this with the
> > > > prep knowledgeable guys on this list ?
> > >
> > > Will be happy to do that with the help of other persons
> >
> > It seems to me there are two issues in that.
> >
> > 1) The pci irq mapping problem I have no infos more yet.
> >
> > 2) the "cannot open root device" problem for which it seems to exist a
> > workaround:
> > "load :console=ttyS0,9600 root=/dev/ram"
> >
> > Despite of these 2 subsequent messages:
> >
> > FATAL: module usbkbd not found
> > FATAL: module hid not found
> >
> >
> > the install goes on rather nicely, I stopped just before repartitionning
> > the scsi disk. (do not want to kill my running woody just now ! I am not
> > sure of consequences of pci problem).
>
> Did d-i find your scsi controller ?
Yes, partman sees the partitions already on the scsi disk.
> And your network card ?
Yes, it was able to download stuff for install.
>If so, it may
> not be so problematic the errors above.
>
> > Because of workaround 2, I can't do the job with my graphic card (Matrox)
> > unless I find something like console=vga.....
>
> console=tty0
I tried with console=/dev/console but there was nothing but the penguin image
on the screen. I will try again with tty0.....
>
> Friendly,
>
> Sven Luther
Reply to: