On 2011-10-06 20:00 +0200, Harry Putnam wrote: > Sven Joachim <svenj...@gmx.de> writes: > >> It might have been easier to just restore the whole file. And >> http://wiki.debian.org/XStrikeForce/HowToRandR12 might have some >> additional useful information for you. > > I didn't see discussion of a bug that causes the mouse NOT to pan out > into a Virtual screen size... although there is such a bug. > > I've had good help finding the appropriate xandr commands and can see > the screen enlarge, but the mouse will not go past the edge. Far as I > understood its because of code in some other aspect of things that is > preventing it.
If you can't find a bug report about this problem, feel free to open one yourself. >> I get the same error, but there actually is an xorg.conf.new in the >> current directory. "Xorg -configure" does not load the dri module, >> which seems to be the cause for this error. > > This is pretty raunchy of me, but I never thought to look. There was > no indication whatever that a file had been written. But there it is. > > Is the dri module essential for starting X? I don't think so, but it's loaded automatically (when running Xorg without the -configure switch), although this can be disabled. > Do you know which package it is in. It's in xserver-xorg-core. > Also does the Nouveau driver prevent other drivers such as nv from > loading. Nouveau needs Kernel Modesetting, and both nv and vesa are not compatible with that and will refuse to load if the nouveau.ko kernel module is loaded with modesetting enabled (default). > Or is nv even available anymore? Not in Debian wheezy: http://bugs.debian.org/612189. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87sjn62c6r....@turtle.gmx.de
