Re: [proaudio] 2.6.17-r3 problems |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] 2.6.17-r3 problems
- From: krgn <k.gebbert@xxxxxxxxx>
- Date: Tue, 27 Jun 2006 23:33:24 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Om3cOS9W+r1wl7BBBJAPiepBnLWYYOYbf+J5/gDtV3100jXXMmL2ecy4Skv3qiJLZ1820H+SHO9ZjZPaBLm/djHoc48oxI55W5vGlI3/5f9T2vhgrMC06nt4rwFtHigBmfe5IftBHoV5THFJ/8nkGiUShIVMS0NGWuD5AbLH1PM=
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
Mark Knecht wrote:
On 6/27/06, krgn <k.gebbert@xxxxxxxxx> wrote:
Hi there,
I am, for a while now, trying to compile a rt-kernel from 2.6.17-rcX
upwards and always keep on running into the same problem. First, of
course, I though it has to do with minor changes I always make in the
.config file, so I tried to just use the one I used for 2.6.16-rt-23,
the kernel which works fine for me since a while now. The same problem
keeps occurring, although nothing has changed in the config, so I assume
it is an issue to do with the kernel itself.
Hi Karsten,
While I do not have a clue of a solution for you I will relate that
I could never get 2.6.17-rt1 to boot correctly when I built it
starting with a 2.6.16-rt25.config and doing makeoldconf. It just
wouldn't boot. I then tried building the kernel config completely from
scratch and it booted the first time.
If you have not yet tried that I might suggest removing the 2.6.17
modules directory, building a new config file from scratch and then
building the kernel.
As for the cardbus issue I have no idea. Sorry.
cheers,
Mark