* [gentoo-user] kernel upgrade and vesafb-tng issue.
@ 2007-02-28 20:16 il-young son
0 siblings, 0 replies; only message in thread
From: il-young son @ 2007-02-28 20:16 UTC (permalink / raw
To: gentoo-user
hello,
here's something weird i ran into after upgrading my kernel from
2.6.18-r6 to 2.6.19-r5. now if i compile the kernel with framebuffer
enabled with vesafb-tng support and set the resolution to anything
other than 640x480-16@-- in grub, i get this error upon booting.
"Block device /dev/sdb3 is not a valid root device."
it then proceeds to ask me to specify the device to boot (or type
"shell" for shell). now at this point if i specify /dev/sdb3 (where
my root partition is -- btw, the new kernel also seems to have
switched what's assigned to sda and sdb) then it continues to boot
fine. so it's definitely detecting sdb3 fine. it seems to be somehow
(however indirectly) associated with enabling framebuffer in the
kernel. if i don't enable it or if i set the resolution to 640x480
with 16-bit colors, it boots without a hitch. does anyone have any
idea as to why this is happening? i have radeon x300 card if that
helps.
somewhat unrelated, i've also noticed with the new kernel, when i run
glxgears it's giving me low fps score. but when i try fgl_glxgears it
looks fine. and also everything else looks fine. fglrxinfo gives me
the right info and glxinfo says "direct rendering : yes". just
curious as to why glxgears would give me a vastly different result
than before.
thanks in advance,
il.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-02-28 20:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-28 20:16 [gentoo-user] kernel upgrade and vesafb-tng issue il-young son
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox