Re: Unable to boot with debian kernel 2.6.15
Wouter Lueks wrote: However, no matter what I try I keep getting the following error: VFS: unable to mount root fs on unknown-block(0,0) The root-fs is XFS, and the xfs module is included in the initrd module. Link the xfs filesystem statically into your kernel. -- 犬 Chris Burdess They that can give up essential liberty to obtain a little safety deserve neither liberty nor safety. - Benjamin Franklin PGP.sig Description: This is a digitally signed message part
Re: Unable to boot with debian kernel 2.6.15
On Sun, 12 Feb 2006 11:56:08 +, Chris Burdess wrote: Wouter Lueks wrote: However, no matter what I try I keep getting the following error: VFS: unable to mount root fs on unknown-block(0,0) The root-fs is XFS, and the xfs module is included in the initrd module. Link the xfs filesystem statically into your kernel. isn't initramfs/initrd supposed to avoid this kind of problems? I have the same setup and I'm also experiencing the same problem. filippo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to boot with debian kernel 2.6.15
On Sun, 12 Feb 2006 the mental interface of Wouter Lueks told: [...] initrd=/boot/initrd.img-2.6.15-1-powerpc initrd content: Why are you guys using that damn .. initrd? Compile all stuff needed for booting directly into the kernel, throw initrd away and you're happy. initrd just makes sense in the case of distri kernels like the udev ones, where the hardware and choosen fs isn't known by the maintainer ;) Elimar -- We all know Linux is great... it does infinite loops in 5 seconds. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to boot with debian kernel 2.6.15
El Sun, Feb 12, 2006 at 10:45:06AM +0100, Wouter Lueks va escriure: It's been some time since I updated my kernel. I'm currently using a self-compiled 2.6.12 kernel. It thought it was time to check out the stock debian kernels since the seemed to be working very good for a lot of people. So I went ahead and installed the debian kernel and hoped it would boot. However, no matter what I try I keep getting the following error: VFS: unable to mount root fs on unknown-block(0,0) The root-fs is XFS, and the xfs module is included in the initrd module. I couldn't find any major differences with other yaboot.conf files, so I'm a bit at a loss on how to solve this. This is caused by a known bug on yaboot and XFS that afects initrd images build using initramfs and yaird (the old mkinitrd images DO work, though). The bug is not assigned to yaboot, but I've found a that includes an explanation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336993 I solved the issue making a small ext3 /boot partition to put my initrd there and now standard kernels work (I'm using initramfs right now); luckily I made a 1Gb swap partition when I first installed the machine and was able to split that one in two instead of reinstalling. Greetings, Sergio. -- Sergio Talens-Oliag [EMAIL PROTECTED] http://people.debian.org/~sto/ Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 signature.asc Description: Digital signature
Re: Unable to boot with debian kernel 2.6.15
On Sun, Feb 12, 2006 at 10:45:06AM +0100, Wouter Lueks wrote: It's been some time since I updated my kernel. I'm currently using a self-compiled 2.6.12 kernel. It thought it was time to check out the stock debian kernels since the seemed to be working very good for a lot of people. So I went ahead and installed the debian kernel and hoped it would boot. However, no matter what I try I keep getting the following error: VFS: unable to mount root fs on unknown-block(0,0) The root-fs is XFS, and the xfs module is included in the initrd module. I couldn't find any major differences with other yaboot.conf files, so I'm a bit at a loss on how to solve this. Regards, Wouter Lueks Current versions: yaird - 0.0.12-3 yaboot - 1.3.13-4.1 linux-image-2.6.15-1-powerpc - 2.6.15-4 yaboot.conf: boot=/dev/hda2 device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: partition=3 root=/dev/hda3 timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot enableofboot macosx=/dev/hda6 image=/boot/vmlinux-2.6.15-1-powerpc label=Linux read-only initrd=/boot/initrd.img-2.6.15-1-powerpc initrd content: (attached) Can you file a proper bug report against linux-2.6 with title marked [powerpc] ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to boot with debian kernel 2.6.15
On Sun, Feb 12, 2006 at 11:56:08AM +, Chris Burdess wrote: Wouter Lueks wrote: However, no matter what I try I keep getting the following error: VFS: unable to mount root fs on unknown-block(0,0) The root-fs is XFS, and the xfs module is included in the initrd module. Link the xfs filesystem statically into your kernel. No need, that is why we have a ramdisk for. This is probably a (minor and easy to fix) bug in yaird or initramfs-tools package. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to boot with debian kernel 2.6.15
On Sun, Feb 12, 2006 at 04:02:24PM +0100, Elimar Riesebieter wrote: On Sun, 12 Feb 2006 the mental interface of Wouter Lueks told: [...] initrd=/boot/initrd.img-2.6.15-1-powerpc initrd content: Its supposed to be a initramfs ramdisk, not in the initrd format anymore. Why are you guys using that damn .. initrd? Compile all stuff Because the debian kernel is supposed to run on all matter of hardware, from oldworld pmacs, to newer powerbooks, passing by pegasos machine and motorola prep powerstacks. The old 2.4 non-ramdisk kernels did grow immensely upto 5 MB of compressed image, compared to the 1.8MB of compressed image we have now. Also, the ramdisk images make things like suspend-to-ram or nfs root or crypted filesystems easier or even make things possible that would not have been possible in a plain non-ramdisk system. needed for booting directly into the kernel, throw initrd away and you're happy. initrd just makes sense in the case of distri kernels Well, he specifically was mentioning using the debian kernels, did he not ? like the udev ones, where the hardware and choosen fs isn't known by the maintainer ;) what has udev to do with distri kernel ? yaird for example doesn't use udev at all, only initramfs-tools has this failing. yaird and initramfs-tools in MODULES=dep mode, i think, make it easy to chose the modules in function of the information provided in /sys, and easily find which modules are needed and include them in the ramdisk. I feel that this problem is a tool with either initramfs-tools or yaird, and we need a proper bug to be filled against them, including the installation log, to know which of the two was used and is buggy. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
