no, the culprit for 0x3a is lilo, but initrd should purposefully ignore that. it should mount the root fs and then do a pivot_root, so the kernel trying to open a root device is unexpected.
Well I patched the lilo mdk source file myself so it's probably my fault (didn't see anything wrong though). I tried to get your package from
no, the fact that lilo writes the major number it sees when it is invoked (3a in your case) cannot be prevented. but initrd ignores this option, so what you are seing is unexpected to me. If you could tell me what your machine prints before the kernel panic i could try to guess what happened
comedia.it but it's not responding, can I get it somewhere else ?thanks for noticing, the server is up again now.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \_______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
