Michel =?ISO-8859-1?Q?D=E4nzer?= <[EMAIL PROTECTED]> wrote: > 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?
atyfb doesn't seem to like my laptop's 3D Rage LT Pro. I corresponded with another Compaq laptop owner who has never gotten atyfb to work either. A few times I was scared I was going to damage my LCD (strange flashing bars, etc.). Even the exact same mode that works fine with vesafb does not work with atyfb... > BTW, have you tried 8, or whatever depth the console has? I'm not sure > if vesafb can change the depth, if not that could explain the failure. I tried 8 also, but the fbdev server still doesn't think the mode is supported by the framebuffer device. I found that the framebuffer server in XFree86 3.3.6 works for me, at least partially. Unfortunately, it won't let me set a virtual display size, so it's out. For now, I've settled on a solution that worked for another Compaq laptop user: vesafb on the console, and ati server for X. It seems to work fine. It would be interesting to know why fbdev in XFree 4.1.0 isn't playing well with vesafb, though. Seems a rather unlikely place for a problem to crop up! Mark [EMAIL PROTECTED] _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
