On Thu 20 Mar 2003 11:02, Quel Qun posted as excerpted below: > However, I have the same problem with a laptop where 2.4.19 boots fine > and there is no file system corruption (reiserfs partitions). > 2.4.21 refuses to boot further than the HD check. > > This is a real problem since the install floppy uses the same kernel and > does not boot either.
That's a bit interesting. I filter subjects with kernel in them as I use the stock kernel, not Mdk's, compiled myself with some stuff directly compiled, not modularized, and don't do pre's, only full releases of stable. Thus, I'm still on 2.4.20, and with all the stuff I've seen flying around about 21-pre-whatever, I'm beginning to thing that's a wise decision. As for ReiserFS, have you always used the no-tail option? Here, I dumped no-tail and initrd some time ago, with no problems so far direct booting ReiserFS on all partitions, from LILO directly to a boot partition with Reiser on it, without the no-tail option either. Of course, as I'm using Reiser native, I compiled it directly into the kernel, rather than as a module, as well. Perhaps that's it? As I said, tho, no problems whatsoever with it, here. However, it's possible that .21preX has problems, perhaps with initrd and module loading for that, perhaps related to no-tail or the lack of it, perhaps something else. I suppose that's why they call it pre, altho it could be a Mdk kernel patch conflict, rather than something in the main kernel. Has anyone looked into whether they have the same problems with the kernel.org mainline kernel, and if so, at what official pre patch level it triggers? (As mentioned, I normally filter subject lines w/ kernel in them, so don't change the subject to include that if you want me to continue following the thread. Otherwise, whatever.) -- Duncan "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin
