On Mon, Jun 2, 2008 at 9:24 AM, Rogério Brito <[EMAIL PROTECTED]> wrote: > Hi, Michel. Long time no see/talk. :-) > > On Jun 02 2008, Michel Dänzer wrote: >> On Sun, 2008-06-01 at 18:29 -0300, Rogerio Brito wrote: >> > Oh, BTW, one error/warning that I see reported on the machine's >> > console (and that apparently doesn't get included in the X logs) is >> > the following: >> > >> > (many times the following error---at least 20 times in a row) >> > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument >> > (...) >> >> But they are included in the log file: >> >> > (II) R128(0): Not using default mode "1024x768" (unknown reason) >> > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (...) > > Sorry. Missed them while perusing the file. > >> So, for some reason the kernel's aty128fb is rejecting the X server's >> 1024x768 modes. > > Indeed. That's one of the reasons why I tried downloading an older 2.6 > kernel, but the dependencies of modern udev have stopped me from > compiling it (I would try with the kernel released with sarge, i.e., > 2.6.8). > >> Have you tried putting an X mode definition (e.g. obtained by fbset >> -x) of the console 1024x768 mode into the xorg.conf monitor section? > > Yes, I did that when I first reported this bug to Ubuntu, but apparently > the bug went unnoticed for a long time and sorted as "unimportant" (!) > or something like that. > > Anyway, I just tried it again and I'm including here attached both the > xorg.conf and the X log.
FWIW, you might also try commenting out the "Usefbdev" option. IIRC, the driver does work without it. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
