On Fri, 2002-08-09 at 21:11, Mark A. Haun wrote: > I've been trying to get X running on my Compaq Armada M300 laptop (ATI Rage > LT Pro graphics device, 800x600 LCD) using the framebuffer device. The > Linux console is working beautifully at 800x600 using the vesafb driver: > > vesafb: framebuffer at 0x40000000, mapped to 0xc8800000, size 4096k > vesafb: mode is 800x600x24, linelength=2400, pages=1 > vesafb: protected mode interface info at c000:4dba > vesafb: scrolling: redraw > vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0 > Console: switching to colour frame buffer device 100x37 > fb0: VESA VGA frame buffer device > > But the fbdev driver in X (version 4.1.0.1, shipped with Debian > stable/woody) is refusing to start, claiming that any mode I ask for is > invalid: > > (II) FBDev(0): using default device > (II) Running in FRAMEBUFFER Mode > (**) FBDev(0): Depth 24, (--) framebuffer bpp 32 > (==) FBDev(0): RGB weight 888 > (==) FBDev(0): Default visual is TrueColor > (==) FBDev(0): Using gamma correction (1.0, 1.0, 1.0) > (II) FBDev(0): Hardware: VESA VGA (vidmem: 4096k) > --> (II) FBDev(0): Checking Modes against framebuffer device... > --> (II) FBDev(0): mode "800x600" test failed > (II) FBDev(0): Checking Modes against monitor... > (--) FBDev(0): Virtual size is 1024x768 (pitch 1024) > (**) FBDev(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz > (++) FBDev(0): DPI set to (100, 100) > (II) Loading /usr/X11R6/lib/modules/libfb.a > (II) Module fb: vendor="The XFree86 Project" > compiled for 4.1.0.1, module version = 1.0.0 > (**) FBDev(0): Using "Shadow Framebuffer" > (II) Loading /usr/X11R6/lib/modules/libshadow.a > (II) Module shadow: vendor="The XFree86 Project" > compiled for 4.1.0.1, module version = 1.0.0 > (--) Depth 24 pixmap format is 32 bpp > FBIOPUT_VSCREENINFO: Invalid argument > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 > > > (My XF86Config-4 file is appended at the end of this message.) > > I've tried everything I can think of, including: > > -- default bpp of 15 or 16, instead of 24 > -- mode names other than "800x600" (like "defaults," as in 3.3.x) > -- an explicit modeline in the monitor section, with timings given > by 'fbset -x' > > but nothing seems to work. Web searches on this error aren't helping much > either. I always get the same error while "checking modes against > framebuffer device." > > Can anyone tell me what this means?
The fbdev driver asks the framebuffer device if it can display that mode, and it says no. > Is there any way to get more debugging information? I thought running X with > fbdev was a trivial task once the framebuffer console was working. It's supposed to. :) It should fall back to the current mode from console. So if the FBIOPUT_VSCREENINFO ioctl fails, that basically means that vesafb refuses to set the mode it's currently displaying in console... The ati driver (or atyfb in console) doesn't work? -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
