|
From: Helge H. <hel...@ai...> - 2003-10-30 20:04:21
|
On Tue, Oct 28, 2003 at 02:03:58PM +0200, Aivils Stoss wrote: > > >> Current ruby support straight in kernel compiled fb device > >> drivers and fbcon. To test Your matrox figure fbcon into > >> kernel and reboot. > >2.6.0-test6-ruby dies before the first printk if I do that, > >while 2.6.0-test6 works. fbcon on matrox breaks somehow > >with ruby. I don't know what to do to debug this > >further - adding printk's is probably not an option. > > Strange. Normal is 5-10 sec VGA console output until > fb_console_init is called. After fb_console_init You > can read printk only on serial console terminal in case > fbcon is broken. > You are right, there is a few lines of VGA console output. I only see half a second if I'm lucky, because the flat panel screen takes a long time to switch modes. 2.6test6-ruby with fbcon and 2.6test9-ryby with fbcon are the same - they die when switching away from vga. The screen goes black/garbage and then its over. 2.6test6-ruby and 2.6test9-ruby without fbcon works fine, except that I have no text console. All I can do if I quit X is to type blind while looking at a garbage framebuffer. The garbage change as I type, indicating prograss but not all that helpful. 2.6test9-ruby with the single console patch seemed to crash, although it got a little further. It managed to corrupt filesystems, so I believe it got as far as mounting while the screen was showing garbage. The keyboard didn't react to numlock though, so I reset it. Perhaps I try it again. Helge Hafting |