|
From: Fredrik N. <no...@no...> - 2003-01-19 16:42:02
|
s=F6n 2003-01-19 klockan 16.41 skrev Antonino Daplas:
> The other patch (in reply to Jak) should hopefully fix the initial=20
> screen corruption on insmod and the kobject trace message.
It did - thanks!
> Can you try running an fbdev-based application, such as X, at 8bpp, just
> to find out if the hardware is incorrectly initialized from the very
> start or if this is more fbcon-related?
I've tried two things. This:
modprobe rivafb <-- loads OK, no visual side effects
modprobe fbcon <-- garbage graphics, complete hang
And this:
modprobe rivafb <-- loads OK, no visual side effects
fbset 640x480-60 <-- screen turns black, complete hang
The mode looks like this:
mode "640x480-60"
# D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz
geometry 640 480 640 480 8
timings 39722 48 16 33 10 96 2
endmode
I haven't found any crash reports or similar in /var/log/messages. The
system simply freezes completely.
Fredrik
|