Re: SPARC SunBlade 2000 fails to find disks: ql2200_fw.bin not found, "Firmware image unavailable." (kernel 2.6.26, Debian lenny)
Hi Jurij e.a.,
Thanks for your quick reply!
Op Wed 3 Feb 2010 om 07:36:50 +0000 schreef Jurij Smakov:
> On Wed, Feb 03, 2010 at 06:23:03PM +0100, Joost van Baal wrote:
> > I'm installing Debian lenny on a SunBlade 2000 sparc for demo-ing at the FOSDEM
> > conference debian booth. ql2200_fw.bin is not found by my kernel, while it
> > _is_ included in the initrd. Booting the system from a Debian installer CD,
> > and supplying ql2200_fw.bin via an USB-stick works just fine: I've installed
> > the complete OS on the system's disks this way.
> > The kernel on disk is vmlinuz-2.6.26-2-sparc64 from
> > linux-image-2.6.26-2-sparc64 package, version 2.6.26-21.
> > /usr/sbin/update-initramfs is from initramfs-tools (0.92o).
> > Any clues on how to get this system to find it's disks is very much
> > appreciated. Unfortunately little time is left for me: the conference is gonna
> > happen in 3 days, while the system is scheduled to get shipped there even
> > earlier....
> Can you check that the firmware file actually makes it to the initrd?
> It's just a gzipped cpio archive, you can extract it like that (in a
> temp directory):
> cp /boot/initrd-<version> initrd.gz
> gzip -d initrd.gz
> cpio -i < initrd
Yes, it is included in the initrd:
~ # mount /dev/sdb1 /mnt
~ # for i in proc sys dev dev/pts; do mount --bind /$i /mnt/$i ;done
~ # chroot /mnt
sh-3.2# mount /usr
sh-3.2# mount /tmp
sh-3.2# cd /tmp
sh-3.2# zcat /boot/initrd.img | cpio -i
sh-3.2# ls -l lib/firmware/ql2*
-rw-r--r-- 1 root root 76802 Feb 3 21:19 lib/firmware/ql2100_fw.bin
-rw-r--r-- 1 root root 84566 Feb 3 21:19 lib/firmware/ql2200_fw.bin <- the right one
-rw-r--r-- 1 root root 123170 Feb 3 21:19 lib/firmware/ql2300_fw.bin
-rw-r--r-- 1 root root 132978 Feb 3 21:19 lib/firmware/ql2322_fw.bin
-rw-r--r-- 1 root root 227884 Feb 3 21:19 lib/firmware/ql2400_fw.bin
-rw-r--r-- 1 root root 198044 Feb 3 21:19 lib/firmware/ql2500_fw.bin
I'll reboot once more and will record the exact kernel error messages.
Perhaps that'll help...