gentoo boot procedure [SOLVED]
 

hi,

i have severe problems in getting the 2.6.7 kernel to run properly... currently i run a 2.6.6 without problems. but when i boot with a 2.6.7 ( i tried vanilla, mm1, mm2, mm3, gentoo-dev-sources, rc3) the boot process fails just after having added the swap space. then such strange errors as "input/output error" occur and i can see messages as "read-only filesystem" flushing by.

i now were very happy, if i could disable the nothing-telling output from the init-scripts, e.g.
i even don't have a log file, because the processes can't write on the disk?!?!?

as i said, 2.6.6 works prefectly.
with 2.6.7 i tried the same config, built it new from scratch, and tested also a "minimal" one --> no success, so i guess some tools here on my box conflict with something in the kernel... but what:confused:

2.6.7-rc1 works well... - but to figure out what changes have been made i must read the long (very long) changelogs... if somebody could help me here with just a hint, how to get better messages - feel free :cool:

thank you for all your thoughts and hints

raist.

apparently the system hasn't (or cant) remount the root file system (by default the rootFS is usually mounted read only)

maybe update those boot scripts?

i just updated the system before i've begun to install the new kernel
:confused:
i now tested 2.6.7-rc2... this one boots, but not cleanly: the module for my NIC isn't available in the kernel-config option, so i have no ethernet (e1000 driver)...

i'm still looking for a possibility to disable the "standard boot output" and switch to "verbose" output...

thank you

cheers, raist.

theres at standard output?

i just put in boot splash and told lilo to tell the kernel "splash=verbose" so i never seen the "standard boot output", unless its the status bar (I'm thinking of making a new image and adding that back in, just for the fun of it)

and why not compile in the driver?

i have no boot-splash. i was speaking of the output from the init-scripts. that one i have "fixed" (i disabled the pipe to /dev/null)

concerning the NIC-driver... i found out that this one was a known problem in 2.6.7-rc2. one wasn't able to compile the gigabit drivers, if one has not enabled the 100Mbit option in the kernel config. :rolleyes:

--> rc2 works too so far... now i try to figure out what the problem with the rc2-->rc3 might be...

cheers, raist.

[UPDATE]
i still search a better mean to get usable messages... my "disabling strategy" doesn't do enough:cry:

maybe i've found the bug... the problem seems to reside in a partition table that is inconsistent compared to the physical disk size. my ibm t41p had (i disabled it now, for it doesn't make a difference if it's enabled or disabled) a so-called "predesktop area": some GB at the end of the disk were reserved for the winxp image files. well, it seems as if since 2.6.7-rc3 the inconsistency messes up the system.

so, now i search a possibility to either repair the partition table, resize the partition, ...any other ideas?

but what i should do in order to avoid a huge reinstallation/moving/imaging-session i were very grateful for any idea from anybody :)

thank you.
raistlin.

hi,

i solved it "the hard way": as no tool could repair the partition, i just copied the contents (with the correct flags for "cp", of course ;) ) to an external hd, deleted the buggy partition, recreated a new one and copied the contents back. i have manually provided the size-parameter for the new partition such that the error doesn't occur again.

thank you all for your help

raistlin.