I tried 15.nov CVS ruby. It is similiar to 29.oct ruby in that
it works without framebuffer console, and hang with it.
My previous attempts with 29.oct ruby and G550 framebuffer consoles
was with devfs. Running without devfs still crashes.
There are some things I wonder about.
Ruby without framebuffer console is compiled with vga console
(it isn't even possible to deselect it in menuconfig)
But I don't get a useable vga console. The framebuffer (without
console) takes over and there is no switching back.
Perhaps this isn't ruby specific, but I wonder if it is
supposed to be that way?
The use of dumbcon is another thing. I use dumbcon=1 because
I found that in a howto. Will that be unnecessary when
the framebuffer consoles work someday?
I have the understanding that "dumbcon" is something that
attach a keyboard to a vt, so X may get keyboard input,
while the dumbcon actually doesn't display anything.
I happen to have two framebuffers, so running consoles on both,
with one keyboard on each ought to be possible. There seem to
be no need for a "dumbcon" then, the second framebuffer ought
to get a keyboard and set of vt's just like the first one. But
how do I arrange that? How can I tell the kernel which
keyboard goes with what framebuffer?
Helge Hafting
|
