corrupted mouse cursor with fbsplash/matroxfb

[sawatts]

I have just got fbsplash to work on my 2.6.10 kernel with matroxfb (G400), after several kernel rebuilds and reboots. This is a clean installation from Gentoo 2004.3.

This posting summerises a number of issues I have come up against:

• 1. Corrupt mouse curor when returning to X from an virtual framebuffered console.
  2. SOLVED: Kernel options to get boot splash with matroxfb in kernel 2.6.10.
  3. Reduced performance with matroxfb due to fbsplash-required kernel options.
  4. Framebuffer only giving 16bit colour depth to matrox mga in X (xorg).

Corrupt Mouse
when switching back to X (xorg) from a framebuffered console, the mouse cursor is corrupt -- appearing as a rectangle/square of vertical black strips ("barcode"). It still operates as a mouse with its hot spot in the top left of the rectangle.

Any suggestions as to what may be the cause of this?

So far I have just restarted X to clear the problem, though this is not desirable! This has been happening since I got the console fb'ed, and before I managed to get the splash to appear.

Kernel options for matroxfb and fbsplash to work
Inorder to get the fbsplash to appear, I had to compile the kernel without the "Tile Blitting" FB option ('CONFIG_FB_TILEBLITTING'), which is recommended for matroxfb. This enabled the splash screen option ('CONFIG_FB_SPLASH') in menuconfig, which was missing before, and up popped the emergence theme at boot.

Reduced performance of mga with fbsplash options
In X I am noticing slower repainting when dragging windows, which wasnt apparent with tile blitting enabled. I am wondering whether I may be better of using VESAFB-TNG instead of the h/w specific driver?

Cannot get better than 16bit depth in X
Another problem has been that X starts in 16bit depth (1280x1024). I have been trying to get it to start in 24 or 32bit at this resolution, but without any success. This seems to be due to the framebuffer; from 'Xorg.0.log':

Code: Select all

(--) MGA(0): Chipset: "mgag400" (G400)
(==) MGA(0): Depth 16, (==) framebuffer bpp 16
(==) MGA(0): RGB weight 565

This has been the case from before I started trying to get a boot splash screen (when the framebuffer was left to its own devices). It seems to think that there is only 16M on the card (some configurations did report 32MB, but still only produced 16bit depth).



Motherboard: MSI K7D Master-L
Processors: 2 x Athlon MP 1900+
Memory: 1GB RAM
Graphics: Matrox G400 DH MAX
Monitor: Hercules Prophetview PRO920

[stillman]

solved the same problem by commenting out the line "VideoRam 8192" respectively setting it to "VideoRam 4069" (i have a Matrox G100)