I compiled a new kernel today. 2.6.0-test11-bk9 with
today's cvs ruby-2.6
I first tried a monolithic kernel with G550 framebuffer and fbcon.
Unlike previous fbcon attempts this didn't oops!
I got all the normal kernel initialization output,
then init took over and ran the usual scripts.
Everything was fine until it attempted to start xdm.
Nothing happened after that. I also didn't get any gettys
so no opportunities to log in and no console switching.
I also made a kernel without fbcon. The same thing happened,
it booted (this time with no console output after the framebuffer
driver loaded) and got stuck later. X didn't start.
My guess is some sort of Vt problem, as that prevents both
X and getty from starting. I also noticed that the cvs update
updated vt.c
Helge Hafting
|
