matroxfb not working after trying to upgrade to 2.6.3
Quoted 7 lines · Juha
I've got a problem with matroxfb not working in either 2.4.23 or 2.6.3 after trying to upgrade to 2.6 series. My videocard is a G400 and it's built as a module. Previously, when I modprobed the module, it would register itself in
/etc/log/syslog, but now nothing is printed in the syslog when inserting the modules. And I don't understand, what has changed. These are the parameters I give to lilo on boot:
Quoted 6 lines
Feb 23 14:06:27 linux kernel: Kernel command line: auto BOOT_IMAGE=Linux roroot=303 video=matrox:vesa:0x115
And this is my .config:
CONFIG_FB_MATROX=m
Do not build it as a module. It is not going to work in usual configurations. Also, did you built CONFIG_FRAMEBUFFER_CONSOLE as a module and insmod-ded it AFTER matroxfb?
Quoted 4 lines
but when I try to use matroxset, with both 2.4 and 2.6, I get:
bash:# matroxset -f
/dev/fb0-m 2
ioctl failed: Device or resource busy
Probably output #1 is already used by someone else. Build everything to the kernel, you'll get much saner defaults then, as it forces correct order for crtc2 & maven initializations.
What reports 'matroxset -f /dev/fb0 -m' and 'matroxset -f /dev/fb1 -m' ? Does not second one report that /dev/fb1 is currently displayed on that output?
Petr
Quoted 3 lines · Petr Vandrovec <VANDROVE <at> vc.cvut.cz> writes:
Quoted 1 line
CONFIG_FB_MATROX=mDo not build it as a module. It is not going to work in usual configurations.
Building FB_MATROX into the kernel fixed the problem, so thanks alot Petr for the quick help!!
Quoted 3 lines
What reports 'matroxset -f
/dev/fb0-m' and 'matroxset -f/dev/fb1-m' ? Does not second one report that/dev/fb1is currently displayed on that output?
The fb0 was mapped to crtc1 and fb1 to crtc2, and even matroxset -m 5 option wouldn't unmap them. But everything works now :)
juhis