Ok, just to double check, I have tried to compile the last 2.6.16.22
with more or less exactly the same config as before, and it worked
immediately.
I am unsure how to proceed, whether to tak this issue to gentoo-user or
even maybe to the kernel people? It seems that the problem clearly is
loading the ext3/////ext2 driver on startup so the disk can be mounted.
For this try, I compiled everything into the kernel (which, yeah, I
tryed with 2.6.17-rt1 too ;)).
Could someone maybe give adivce on how to proceed with this, since I
think I have circled it so far, that one can say it must have to do
with the new kernel version.
I also found this, looking for changes in the ext3/2 driver:
http://www.linuxdevices.com/news/NS2182308099.html
This does not seem to be a good/detailed source for info, yet it might
be a hint towards the problem.
any clues?
Karsten
Mark Knecht wrote:
On 6/27/06, krgn <k.gebbert@xxxxxxxxx> wrote:
hi Mark,
thanks, that was already very helpful, I saw now actually how different
things are from .16 to .17 so luckily I ended up with a newer,
different
error which is now more complicated to show, since I don't reach a
stage
anymore, where I can grab a log or so.
Bascially, when reaching something like this stage here,
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
..........
VFS: Mounted root (ext2 filesystem) readonly.
Time: tsc clocksource has been installed.
the newer kernel tells me something like it can't mount my root
partition and that 'block(0,0)' is unknown. I double checked against my
old config, changed the new one to the old settings and recompiled, but
no joy. I appended the new config so maybe someone who might have a
clue
what this might be, can have a look.
normally, my root partition is mounted like this:
/dev/hda5 on / type ext3 (rw,noatime,user_xattr)
and I also checked again grub settings and the fstab file, but there
was
nothing strange, so must assume its something about the configuration,
or the kernel again (since my old one boots fine with the same grub
settings)
any idea about VFS?
thanks,
KArsten
Hi Karsten,
(Or is it actually KArsten with two capitals? Please excuse my
confusion there. I'd very much like to address you properly. Thanks.)
I don't really have a clue exactly what this problem is but I took a
look around on web using Google. A few things came up:
1) Did you remember to build ext3 support into the kernel? Note how
mine below says it's mounting ext3.
2) It seems that someone might have had an issue like this caused by
ACPI. You could try acpi=off on your boot command line edited in by
hand or added in grub.
When my AMD64 machine boots I see this:
<SNIP>
ACPI wakeup devices:
HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1
ACPI: (supports S0 S1 S3 S4 S5)
Time: tsc clocksource has been installed.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
*****************************************************************************
*
*
* REMINDER, the following debugging options are turned on in your
.config: *
*
*
*
CONFIG_DEBUG_RT_MUTEXES *
*
CONFIG_DEBUG_PREEMPT *
*
*
* they may increase runtime overhead and
latencies. *
*
*
*****************************************************************************
Freeing unused kernel memory: 188k freed
input: AT Translated Set 2 keyboard as /class/input/input0
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Adding 2008084k swap on /dev/sda10. Priority:-1 extents:1
across:2008084k
EXT3 FS on sda2, internal journal
[drm] Initialized drm 1.0.1 20051102
<SNIP>
Since there is ACPI stuff immediately before and after it seems
worth looking at.
I suppose you don't have a second Linux box to do the null modem
cable trick where you can capture the boot stuff on a different
machine? Helpful during times like these.
Write back with more info and we can keep trying. At least that's
two ideas for now.
Cheers,
Mark
|