#27 CONFIG_BLK_DEV_LOOP=m and root fs on loop device

[Notch-1]

hi, i have some trouble booting a 2.6.24 (and 2.6.18 before) kernel with CONFIG_BLK_DEV_LOOP=m:

VFS: Cannot open root device "loop0" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
0030 39070080 hda driver: ide-disk
0301 3807373 hda1
0302 1 hda2
0303 23703907 hda3
0305 11454282 hda5
0306 96327 hda6
0700 3993600 loop0 (driver?)
0701 20480 loop1 (driver?)
0800 7831552 sda driver: sd
0801 7831520 sda1
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

As you can see i have the root filesystem in a loop device, but with CONFIG_BLK_DEV_LOOP=y it always worked fine! The loading of the image (to loop0) is performed by the initrd, as the loading of the loop.ko module (when needed).
If i try to mount loop0 (modifying the initrd's linuxrc script) i can see the full content, BUT when init try to mount it as root filesystem i got the kernel panic... I think this prove that the module is loaded and working.......at initrd time!
Should you help me? I'd like to use loop-aes modules instead of the original loop.ko, but i need to solve this before...
Thanks

[Jari Ruusu]

Logged In: YES
user_id=238645
Originator: NO

You didn't say what kind of initrd you are using. If you
are using one created using build-initrd.sh, then please
post the config you are using. If something else, please
post it so that I can see what it does.

Also try root=700 (loop0) or root=701 (loop1) kernel
command line parameters. Please show me your bootloader
config so that I can see what it does.

[Notch-1]

Logged In: YES
user_id=2104652
Originator: YES

root=700 solved the problem, thank you very much