On Sat, 18 Apr 2009 21:07:16 -0700 (PDT) Fred Snurd
<[email protected]> wrote:
> I've installed the 15 April -current snapshot on an Acer Aspire One
> D150-1165 (followed by downloading source & built kernel, userland, &
> xenocara), & starting X through auto-detection or from a generated
> xorg.conf via startx succeeds in displaying the default fvwm(1)
> window manager, but the mouse is frozen. Sometimes I can move it an
> inch or so after starting X, but it quickly freezes. I saw mention
> of adding the following line in a different thread:
>
> Option "AccelMethod" "XAA"
>
> but this didn't change the behavior. I've also substituting in the
> vesa(4) driver in the same Device section, but this didn't change the
> behavior observed either. Below are dmesg(8)
> & /var/log/Xorg.0.log.old outputs.
>
> Any insight on how to unfreeze the mouse/trackpad would be
> appreciated.
Unfortunately, you attached the Xorg.0.log file from when you were
running the vesa driver, so debugging the intel(4) driver issues is a
bit tough. If you can start X, and use ssh from another machine to grab
the log file, it would help.
Make sure you've created the /dev/drm0 device via MAKEDEV
The new intel(4) driver does some (often buggy) rescaling based on the
EDIF data presented by the display via DDC. There are two versions of
DDC that can be used (v1 & v2), and they can be controlled via your
xorg.conf file.
Option "DDC" "false" # shut off both v1 and v2
Option "DDC1" "false" # shut off v1
Option "DDC2" "false" # shut off v2
I've had luck with the latter, DDC2 false, on an older intel chipset
(845) attached to an old CRT.
The new rescaling code in the intel(4) driver is for fixed format
(read unforgiving) LCD displays which show garbage when you get the
resolution/refresh settings wrong. Needless to say, the driver is not
the best at getting things right.
--
J.C. Roberts
