On Fri, Dec 09, 2005 at 06:24:56PM +0100, Maximilian Attems wrote: > On Fri, Dec 09, 2005 at 04:35:23PM +0000, Paul Brossier wrote: > > hi > > > > On Wed, Nov 30, 2005 at 07:17:11PM +0100, maximilian attems wrote: > > > please retest with latest initramfs-tools in unstable aka version 0.41. > > > it needs latest udev 0.76-3 too. > > > the various seen timing bugs should be fixed thanks to newer udev. > > > > i could boot a thinkpad on 2.6.14 with an xfs root partition. > > cool. > > > but on the powerpc64, i still get the following messages: > > TCP reno registered > > TCP bic registered > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > RAMDISK: cramfs filesystem found at block 0 > > RAMDISK: Loading 1558KiB [1 disk] into ram disk... done > > VFS: Mounted root (cramfs filesystem) readonly. > > VFS: Cannot open root devide "sda4" or unknown-block(0,0) > > Please append a correct "root=" boot option > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > <0>Rebooting in 180 seconds.. > > > > i have udev 0.76-4 and initramfs-tools 0.41 installed. i suspect it is > > now sata that is making troubles. > > nahh sata working fine over here with initramfs-tools. > > aboves log isn't an initramfs-tools usage, > that's an image generated by initrd-tools. > initrd-tools is known to be buggy for sata discs. > > please try "update-initramfs -u" and check that the initramfs image got > updated > should be the last entry of > ls -lrt /boot > and repost your log then?
mmh. i ran apt-get --reinstall install linux-image... instead. [EMAIL PROTECTED]:~$ sudo update-initramfs -u /boot/initrd.img-2.6.14-2-powerpc64 was been altered. Cannot update. [EMAIL PROTECTED]:~$ sudo update-initramfs -u -t [EMAIL PROTECTED]:~$ ls -lrt /boot | tail -n 1 -rw------- 1 root root 4965455 2005-12-09 17:32 initrd.img-2.6.14-2-powerpc64 [EMAIL PROTECTED]:~$ sudo reboot i now get: ... TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 32768) 8388608 VFS: Cannot open root devide "sda4" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) <0>Rebooting in 180 seconds.. tried a bit harder: [EMAIL PROTECTED]:~$ sudo apt-get --reinstall install linux-image-2.6.14-2-powerpc64 Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 38 not upgraded. Need to get 0B/17.1MB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 169263 files and directories currently installed.) Preparing to replace linux-image-2.6.14-2-powerpc64 2.6.14-4 (using .../linux-image-2.6.14-2-powerpc64_2.6.14-4_powerpc.deb) ... The directory /lib/modules/2.6.14-2-powerpc64 still exists. Continuing as directed. Unpacking replacement linux-image-2.6.14-2-powerpc64 ... run-parts: executing /etc/kernel/postrm.d/mkvmlinuz Setting up linux-image-2.6.14-2-powerpc64 (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. Not touching initrd symlinks since we are being reinstalled (2.6.14-4) Not updating image symbolic links since we are being updated (2.6.14-4) run-parts: executing /etc/kernel/postinst.d/mkvmlinuz adding the following stanza: [EMAIL PROTECTED]:~$ head -n 1 /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/yaird [EMAIL PROTECTED]:~$ sudo apt-get --reinstall install linux-image-2.6.14-2-powerpc64 Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 38 not upgraded. Need to get 0B/17.1MB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 169263 files and directories currently installed.) Preparing to replace linux-image-2.6.14-2-powerpc64 2.6.14-4 (using .../linux-image-2.6.14-2-powerpc64_2.6.14-4_powerpc.deb) ... The directory /lib/modules/2.6.14-2-powerpc64 still exists. Continuing as directed. Unpacking replacement linux-image-2.6.14-2-powerpc64 ... run-parts: executing /etc/kernel/postrm.d/mkvmlinuz Setting up linux-image-2.6.14-2-powerpc64 (2.6.14-4) ... Using /usr/sbin/mkinitramfs to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitramfs /usr/sbin/yaird. Not touching initrd symlinks since we are being reinstalled (2.6.14-4) Not updating image symbolic links since we are being updated (2.6.14-4) run-parts: executing /etc/kernel/postinst.d/mkvmlinuz [EMAIL PROTECTED]:~$ ls -lrt /boot/ | tail -n 1 -rw-r--r-- 1 root root 4964426 2005-12-09 17:44 initrd.img-2.6.14-2-powerpc64 [EMAIL PROTECTED]:~$ sudo reboot but i get the same error as above: RAMDISK: incomplete write (-28 != 32768) 8388608 there is also this line earlier in the bootlog: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize anything else i can try? cheers, piem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
