When I run:
fbset -fb /dev/fb1 '1024x768-70'
the reponse is:
ioclt FBIOPUT_VSCREENINFO: Invalid argument.
fbset -fb /dev/fb0 works fine for any reasonable mode.
fb1 fails the same way for the any workable mode.
fbset -i /dev/fb1 works appropriately, giving the same output as expected as per the HowTo.
I've followed the wiki page except for using the fusion module instead of the patch
lsmod reports:
i2c_matroxfb 9472 0
i2c_algo_bit 12552 1 i2c_matroxfb
fusion 37064 0
matroxfb_maven 19468 0
nls_utf8 6400 1
mga 66432 1
drm 68500 2 mga
...
i2c_ali1563 11012 0
i2c_ali1535 11524 0
i2c_ali15x3 11652 0
snd_pcm 81796 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
i2c_core 25728 5 i2c_algo_bit,matroxfb_maven,i2c_ali1563,i2c_ali1535,i2c_ali15x3
matrox_w1 8192 0
wire 28448 1 matrox_w1
and my .config for this kernel was:
...
CONFIG_FB_MATROX=y
# CONFIG_FB_MATROX_MILLENIUM is not set
# CONFIG_FB_MATROX_MYSTIQUE is not set
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
# CONFIG_FB_RADEON_OLD is not set
...
CONFIG_VGA_CONSOLE=y
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
...
When I try:
fbset -fb /dev/fb1 -xres 800 -yres 600 -depth 16
matroxset -f /dev/fb1 -m 2
the monitor reports that the signal frequency is wrong, which I think I have to fix using fbset, right?
Also, running fbset with -xres 'm' -yres 'n' -depth 'o' does funny things to X if I run it in the terminal instead of going to a virtual terminal, regardless of which fb I use or which values for m and n, although I have no idea how that could be related.
Any advice would be appreciated.
Thanks,
Jonathan Weisz
_______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
