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 > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) So, for some reason the kernel's aty128fb is rejecting the X server's 1024x768 modes. 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? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]