On Wed, Nov 14, 2007 at 11:02:28PM -0500, David Nusinow wrote:
On Sun, Nov 04, 2007 at 07:03:39PM +0100, Moritz Muehlenhoff wrote:
David Nusinow wrote:
I've tested the auto detection code David asked for and ran into
a bug: When I start X.org with the auto-generated config (I use
Moritz Muehlenhoff wrote:
I've filed a bug upstream, but the reply doesn't make me believe upstream
is interested in getting this resolved...
It's a well known fact that mixing the kernel foofb driver with Xorg foo
driver can break. You basically have 2 drivers talking to the same
hardware
On Sun, Nov 04, 2007 at 07:03:39PM +0100, Moritz Muehlenhoff wrote:
David Nusinow wrote:
I've tested the auto detection code David asked for and ran into
a bug: When I start X.org with the auto-generated config (I use startx,
since I work on framebuffer console most of the time, on my
David Nusinow wrote:
I've tested the auto detection code David asked for and ran into
a bug: When I start X.org with the auto-generated config (I use startx,
since I work on framebuffer console most of the time, on my notebook
X11 is really just a slim layer beyond MPlayer) the screen
Hi Moritz,
On Fri, Nov 02, 2007 at 11:17:32PM +0100, Moritz Muehlenhoff wrote:
Package: xserver-xorg
Version: 1:7.3+3
Severity: important
I've tested the auto detection code David asked for and ran into
a bug: When I start X.org with the auto-generated config (I use startx,
since I work
Package: xserver-xorg
Version: 1:7.3+3
Severity: important
I've tested the auto detection code David asked for and ran into
a bug: When I start X.org with the auto-generated config (I use startx,
since I work on framebuffer console most of the time, on my notebook
X11 is really just a slim layer
6 matches
Mail list logo
