On Sun, 2008-11-30 at 16:29 -0600, Javier Vasquez wrote:

Also, the server flag:

Option "AutoAddDevices" "False"

Doesn't help getting this solved...

Input devices have nothing to do with video devices. I think it's a conflict between your framebuffer console and xorg which causes this problem. Framebuffer consoles and Xorg videodrivers have always been a problem here, it's two direct hardware access things competing against eachother. Sometimes it works, sometimes it doesn't.

On 12/1/08, Javier Vasquez wrote:

On 11/30/08, Jan de Groot wrote:

...

On Sun, 2008-11-30 at 16:29 -0600, Javier Vasquez wrote:

...

Also, the server flag:

Option "AutoAddDevices" "False"

Doesn't help getting this solved...

Input devices have nothing to do with video devices. I think it's a conflict between your framebuffer console and xorg which causes this problem. Framebuffer consoles and Xorg videodrivers have always been a problem here, it's two direct hardware access things competing against eachother. Sometimes it works, sometimes it doesn't.

Well, it wasn't a problem before the last update to 1.5.3. I had the following uncommented in the device section:

# Option "UseFBDev" "true"

Now that I have commented it out, I still got the problem (of course after rebooting since I can't restart X). Moreover, just in case, I also removed atyfb (modprobe -r, and then startx), and the problem persists...

So I'm not sure if the problem is a frame buffer one.

-- Javier

OK, I'm done with trials, no luck... I filed a bug then, 12327... thanks, -- Javier

On 12/2/08, Javier Vasquez wrote:

On 12/2/08, Javier Vasquez wrote:

...

On 12/1/08, Javier Vasquez wrote:

...

On 11/30/08, Jan de Groot wrote:

...

On Sun, 2008-11-30 at 16:29 -0600, Javier Vasquez wrote:

...

Also, the server flag:

Option "AutoAddDevices" "False"

Doesn't help getting this solved...

Input devices have nothing to do with video devices. I think it's a conflict between your framebuffer console and xorg which causes this problem. Framebuffer consoles and Xorg videodrivers have always been a problem here, it's two direct hardware access things competing against eachother. Sometimes it works, sometimes it doesn't.

Well, it wasn't a problem before the last update to 1.5.3. I had the following uncommented in the device section:

# Option "UseFBDev" "true"

Now that I have commented it out, I still got the problem (of course after rebooting since I can't restart X). Moreover, just in case, I also removed atyfb (modprobe -r, and then startx), and the problem persists...

So I'm not sure if the problem is a frame buffer one.

-- Javier

OK, I'm done with trials, no luck... I filed a bug then, 12327...

thanks,

-- Javier

I missed one trial, removing the vga mode from boot parameter (which activates vesa FB Ibelieve). When doing it the problem vanishes...

I requested a bug closure, hopefully it'll close...

I was left with with pretty big fonts at the console though, which I don't like. I was using terminus v16b under 1024x768 before, but that's too big now. I tried v14b, but that didn't make a difference, and v12n is not supported, it fails... So I tried alt-8x8, and I like the size, but I don't like the font which at this size looks a bit ugly... any recommendations are welcome...

Thanks,

-- Javier

Hmm, it looks like I can't set a font smaller than the 16, since I lose the fonts when closing X... :( -- Javier

On Sun, Nov 30, 2008 at 9:08 PM, Amanai wrote:

On Sun, 30 Nov 2008 14:12:58 -0800, Javier Vasquez wrote:

...

However I have trouble with the screen. I'm using the mach64 driver with 1280x1024 mode and 24 bits depth, and whenever I try to switch to console (with atyfb @ 1024x768) all I get is a balck screen and the monitor complaining with out of sync... Also when terminating my X session, exiting fluxbox (I use startx to get into X), I get the same thing, so I never can get back to console.

Your best bet is to file a bug report if one hasn't already been opened.

Confirm,

ATI Radeon catalyst driver can't change the resolution it goes always back to 1024x768 founds getting ugly.

This doesn't sound at all like the OP's problem. Similar to the above, you should file a bug report--a separate bug report in this case. For what it's worth, I too use the catalyst driver (ATI X1400) and have no problems whatsoever with the latest Xorg and my resolution of 1680x1050. It may very well be card-dependant so providing those little details in the report could help.