I don't know...maybe I'm missing something crucial here, but isn't the
kernel supposed to boot after you've experienced a flawless compile? I
can't get any of the 2.4.x kernels to boot on my Mdk 7.2 system. Just to
see if it was a problem with ReiserFS I reloaded and changed the type of
FS on my drives "back" to ext2fs and STILL when the kernel begins to boot
it will get as far as re-mounting the ROOT fs as read/write, then this
happens;
Checking loopback filesystem [ OK ]
Mounting loopback filesystem [ OK ]
Setting Profile to: _ (at this point it just sits there and the cursor
blinks until I decide to hard boot the machine)
I was told previously that when I was running ReiserFS that there was a
incompatable difference between the 2.2.x Reiser and the 2.4.x version of
ReiserFS. So what stinkin profile is this silly bugger attempting to set?
I've never seen a kernel behave this way.
And this was a standard "developer's" install out-a the box. nothing
special or fancy. Standard ext2fs partitions. As I said before I've
changed AND freshly formatted the drives before doing this install to make
sure that there wasn't a chance for Reiser to complain or anything.
The kernel config was some what plain and standard in it's config. no
strange or exotic drivers needed and the compile/make
modules/modules_install went off without one single error.
Any ideas?
--
Mark
######################################################################
PGP Key: 0x615E2B81 D852 8DDF 0FFE 9F16 73A8 DFC0 6470 7738 5143 0CBA
Mark Weaver |
[EMAIL PROTECTED] |
Network Systems Administrator Assistant |
Destiny Image Publishers |
######################################################################
