On Tue, 13 Mar 2007 21:47:52 +0100, Michael <[EMAIL PROTECTED]> wrote:
> All information I have is that the current ATI drivers, 8.34.8, are
> not compatible with kernel 2.6.20, that is expected later this month.
To add to the confusion:
On my MBPC2D 17" with X1600 I have Debian Testing running w
On Tue, 13 Mar 2007 16:47:52 -0400
Michael <[EMAIL PROTECTED]> wrote:
>
> On Mar 13, 2007, at 2:59 PM, Bradley Hook wrote:
>
> > I have yet to find any reports of the ATI drivers working with the
> > combination of xorg6.9, kernel 2.6.20, and this particular vid card
> > (x1600).
>
> All inform
On Mar 13, 2007, at 2:59 PM, Bradley Hook wrote:
> I have yet to find any reports of the ATI drivers working with the
> combination of xorg6.9, kernel 2.6.20, and this particular vid card
> (x1600).
All information I have is that the current ATI drivers, 8.34.8, are
not compatible with kernel
I've tried the aticonfig command, as well as about a dozen configs
I've found while googling. The very first config I tried was the
output of `aticonfig --initial` on the original xorg.conf that comes
with Slackware 11. I've also copied my WORKING xorg.conf file from the
Slackware 10.2 install, and
I´m running Xorg 7.1 on Debian unstable, so I can´t say if you
have a Problem with Xorg 6.9. But looking at your xorg.conf I
get the feeling that it is just your config that is messed up.
I woul recommend using the aticonfig tool to try to get an
initial working xorg.conf and work on from that. It
I've been trying to upgrade my MBP from Slackware 10.2 to Slackware
11. Most of the hardware has been much easier to configure this go
around, but the display has been giving me major headaches. In
Slackware 10.2, which runs xorg6.8, I was able to run dual-screen with
1680x1050 on each screen with
On Tuesday 13 March 2007 07:24, Christophe HAUSER wrote:
> Hello,
>
> I tried the kernel patch for the touchpad on my Macbook Pro, but I would
> like to disable the "click" using the touchpad (I prefer the Button). Is
> there a way to do this by sysfs ?
it's possible disable it by Xserver, add thi