Re: Please test the new kernel (2.6.18.dfsg.1-9)
On Tue, Jan 30, 2007 at 07:28:33PM +0000, Stuart Brady wrote:
> I'm not sure if this is due to upgrading to 2.6.18-4, but 'eth0' stopped
> working recently on my SS5. I did a bit of digging in /sys and noticed:
> When I renamed 'eth0' to 'eth0_rename' in /etc/network/interfaces, it
> worked! Any idea what's going on here?
Erm, not really. I'll try to see if I can reproduce it on my SS20.
> Also, I can't install 2.6.18-3 as yaird is failing:
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitrd.yaird to build the ramdisk.
> yaird error: unrecognised device: /sys/devices/root
> yaird error: unrecognised device: /sys/devices/root/ffd2c458
> yaird error: unrecognised device: /sys/devices/root/ffd2c458/ffd2c690
> yaird warning: unrecognised legacy device: /sys/devices/root/ffd2c458/ffd2c690/serio0; trying sunkbd
> yaird error: unrecognised device: /sys/devices/sbus0
> yaird error: unrecognised device: /sys/devices/sbus0/sbus[ffd3ce48]
> yaird error: unrecognised device: /sys/devices/sbus0/sbus[ffd3ce48]/sbus[ffd3d224]
> yaird error: there were errors in this run, aborting now without output (fatal)
> mkinitrd.yaird failed to create initrd image.
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.18-3-sparc32 (--configure):
> subprocess post-installation script returned error exit status 9
> Errors were encountered while processing:
> E: Sub-process /usr/bin/dpkg returned an error code (1)
That looks like bug #396193, which didn't receive any attention from
maintainer for over 3 months now, making yaird pretty much unuseable
on sparc. You can use an alternative (and, currently, default) initrd
creator, initramfs-tools. Installing initramfs-tools, removing yaird,
and running 'dpkg-reconfigure linux-image-2.6.18-4-sparc32' should
generate a working initrd.
Jurij Smakov email@example.com
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC