Re: [Linux-fbdev-devel] bugs in G450 framebuffer console under linux 2.4.17

[Petr V. <van...@vc...>]

On Sun, Dec 23, 2001 at 05:05:08PM -0600, Carl Wilhelm Soderstrom wrote:
> 1. if one doesn't specify a video= option at boot time; the console will
> hang, and the machine soon locks up. (I know it is locked because my
> LCD panel attached to the serial port displays no information, and I tried
> pinging it across the network).

Which option you need to specify to 'video='? You are probably using
vesafb together with matroxfb, or matroxfb together with vga16fb. It
does not work. And after I looked into your dmesg - are you sure that
it does not die due to atyfb? And G450 driver in kernel cannot initialize
G450 from scratch (== you must use matrox as primary device, initialized
by BIOS).

> 2. if one does boot; and then tries to start X (even XFree86 -configure as
> root), the system will lock completely. (tho I *did* have one successful
> startx once; and can't figure out why; since it always failed with a hard
> lockup otherwise). no X log is generated. it just locks immediately. the
> time that it did boot sucessfully; I couldn't see anything unusual in the
> log; tho I'm not an X programmer by any stretch. :)

Make sure that you are not running mga driver from Matrox. Besides of that,
it works everywhere else... Make sure that /proc/fb lists only Matrox
framebuffers, not something else:

ppc:/cdrom# cat /proc/fb
0 MATROX VGA
1 MATROX CRTC2

And of course - are you sure that X do not die because of they are enabling
legacy VGA, causing PCI parity error, and thus bringing your box down?

> 3. trying to use fbset on the second head of the G450 will fail, like so:
> root@steel:~# fbset -fb /dev/fb2 '640x480-75'
> ioctl FBIOPUT_VSCREENINFO: Invalid argument
> root@steel:~# fbset -fb /dev/fb2 '1280x1024-75'
> ioctl FBIOPUT_VSCREENINFO: Invalid argument
> root@steel:~# fbset -fb /dev/fb2 1280x1024-75 
> ioctl FBIOPUT_VSCREENINFO: Invalid argument

Fix your /etc/fbset.modes. Secondary head (as documented) cannot do 8bpp,
it can do only 16bpp and 32bpp.

> the first time you run this, it gives:
> Warning: Remapping obsolete /dev/fb* minor 64 to 2

Fix your /dev/fb* nodes. If you are not running 2.2.x kernels, /dev/fb1
should be  29,1, /dev/fb2 should be 29,2 and so on.

> what debugging information should I include? I saved a dmesg and my kernel
> .config file as well. rather than load the list with them, I put them at:
> http://copper.redchrome.org/~chrome/2.4.17-dmesg
> http://copper.redchrome.org/~chrome/2.4.17-config
> 
> I'm new to this list. How can I help debug this? 

Remove either atyfb + ATI or matroxfb + G450 from your box, and try again...
						Petr Vandrovec
						van...@vc...