Hi! For Erling: I tried both /dev/wsmouse and /dev/wsmouse0 anyway the result is always that synclient cannot connect to X server. Curious enough, the file autogenerated by X -configure contained /dev/mouse which is not present in /dev. Anyway, I more and more realize that my problem has nothing to do with X, as it's related to kernel and CLI. Running X without xorg.conf the mouse behaves well 90% of the times.
For Neal: thanks a lot for your courtesy and also suggestion, never mind if it couldn't help, but I appreciate a lot :))) Btw, at this point I'm starting to suspect that this AOA110 is really sporting a totally compatible synaptics tablet. Nevertheless, under linux both in CLI and X it performs without a glitch, while after bsd kernel update -current is kinda scrambling CLI behaviour. Interesting enough is that running and shutting down X kinda resets this weirdness, like if X does "reset" some unappropriate setting set at boot by the kernel. I would like to provide some hw log, if I knew how to get it for the tablet, in order for the devs to inquire about this situation. Anybody else could maybe suggest? Thanks Pasha On Wed, Oct 26, 2011 at 2:49 AM, Neal Hogan <nealho...@gmail.com> wrote: > Hey Paolo, > > Sorry for the late response. The issue that you're having seems to be > with X, which would be something I could only vaguely comment on. > There has been a synaptics change, it appears. I like my trackpad > behavior better before the change, but I'm going to give it a few > snaps before I "complain." > > The "synclient-thingy" seems interesting, given the cinfig > possibilities (eg, I can scroll both vertically and horizantally by > enabling a couple if variables). > > > I apologize if I pointed you in the wrong direction. > -Neal > > On 10/24/11, Paolo Aglialoro <paol...@gmail.com> wrote: > > On Sun, Oct 23, 2011 at 4:38 AM, Neal Hogan <nealho...@gmail.com> wrote: > > > >> On Sat, Oct 22, 2011 at 3:49 PM, Paolo Aglialoro <paol...@gmail.com> > >> wrote: > >> > Hi all, > >> > > >> > I own an acer aspire one AOA110. It's running -current. Yesterday I > >> updated > >> > it to Oct19 snapshot, the previous one was from June 2011 (I know, I > >> kinda > >> > neglected this box for a long time). Everything run well with the > >> > update, > >> > but for one hassle with touchpad on CLI. It goes in the following way. > >> > At > >> > the boot time when local daemons are started appears the kernel msg: > >> > > >> > pms0: Synaptics touchpad, firmware 7.2 > >> > > >> > Then, every time I touch the touchpad I get several times the > following > >> > string from kernel: > >> > > >> > pms0: not in sync yet, discard input > >> > > >> > Of course I cannot use the mouse pointer on CLI anymore. It definitely > >> looks > >> > like a regression. > >> > > >> > The strange thing is that if I start X (where trackpad either does not > >> work > >> > or works for a bunch of seconds randomly) and then shut it down, then > >> > the > >> > pointer is back alive in CLI and no more messages are sent from the > >> kernel > >> > to CLI. Then starting X, again pointer gets stuck after a while in > >> graphic > >> > mode. Puzzling. A couple of times, after shutting down X also keyboard > >> > stopped working. It is not a hardware issue, under linux touchpad and > >> > keyboard work normally and with previous kernel they also did. > >> > > >> > In my config wsmoused -2 is started by rc.local. This is my dmesg: > >> > Any clues???? > >> > Thanks > >> > Pasha > >> > > >> > > >> > >> I had a similar situation where my trackpad tap worked and then didn't > >> (I have yet to figure out if that was by design), but then I looked at > >> synclient(1) and was able to config things back to "normal." CHECK IT > >> B4 U WRECK IT :-) > >> > > > > Hi Neal, > > > > thanks for the hint. Considering that in order to run synclient(1) I need > X, > > I tried to run: > > > > X -configure > > > > from root in order to get a xorg.conf file to modify with SHMConfig "on" > in > > [Input Devices] (I had always run X without a xorg.conf file on this > > machine, it always "just worked"). I then got the following errors: > > > > cannot open /dev/wsmouse > > [snip] > > Xorg is not able to detect your mouse > > > > Then trying the edited xorg.conf.new just leads to a nonmoving mouse. The > > output of synclient is just "Failed to connect to X server.". > > So, the problem persists and I cannot audit the synaptics device :( > > > > What to do next? > > Thanks > > > > in my .Xdefaults file, but synclient still complains "can't connect to X > > server".
