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

Re: d-i dated 2004 07 13 failled to boot on a sparc sunblade 100



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Joel

On Wednesday 14 July 2004 16:10, Joel Soete wrote:
> Hello Frederik,
>
> [...]
>
> > > Finaly I download the last sarges-netinstall.iso dated of this
> > > 2004 07 13 where the kernel (the 2.4.26) panic also because:
> > > [...]
> > > RAMDISK:Couldn't find valid RAM Disk image starting at 0.
> > > ...
> > > Kernel panic: VFS: Unable to mount root fs.
> > >
> > > Any idea (boot net?)?
> >
> > You probably tried the sarge_d-i branch:
> > http://gluck.debian.org/cdimage/testing/sarge_d-i/sparc/20040713/sa
> >rge-sparc-netinst.iso
>
> There was in fact in:
> http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/sparc/ tree
> :)

I believe they are the same. 

> > Try instead the sid_d-i branch:
> > http://gluck.debian.org/cdimage/testing/sid_d-i/sparc/20040713/sarg
> >e-sparc-netinst.iso
> >
> > Let us know if it works.
>
> And just launch it but still failled at the same place with same
> message (Kernel
> panic: VFS: Unable to mount root fs.)
>
> umm as said, i am not familiar with d-i (that is a long time that I
> installed my woody pc and pre-woody hppa boxes, so I don't remember
> all details :( ), but I don't understand this message: just after
> "ENTER" to start the install a ramdisk is well found and loaded, then
> during the load of the kernel,
> this one tries again to load (i suppose another) ramdisk which this
> time it doesn't find?
>
> The questions are:
> a) does it need this second ramdisk?
> b) if yes where is it supposed to look for on the cd, in the first
> ramdisk?

I'm no expert on d-i. I just assumed that you would have more luck using 
sid_d-i, since there have been made some recent progress to these 
images that allowed me and other to get past a kernel panic that looks 
similar to yours 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254808 and other 
similar reports).

I think the best think you can do is to provide a complete dump of the 
entire boot process (e.g. using a serial console, if you have a serial 
cable for this purpose). This should reveal every little detail that 
may help the d-i developers on this mailinglist (maybe debian-sparc 
will be interested as well).

- -- 
Frederik Dannemare | mailto:frederik@dannemare.net
GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu
Key fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E B5A8
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA9c3ILSX61ZxOtagRAvx4AKCKglBr2fjn+pOOnpWjT3lqb0PtKACfZ0MT
vhZsL5cMCH//Rj6Hsz0X1mA=
=OeDQ
-----END PGP SIGNATURE-----



Reply to: