You could be right I never tried the command under Xubuntu. I only tried it in Jesse and after I move to LXDE.
Sent from my iPhone > On Nov 26, 2014, at 7:54 PM, Michael Schmitz <schmitz...@gmail.com> wrote: > > Thanks Herminio, > > so just to clarify - you had never used the 'trackpad' util before on > Xubuntu or Debian Jessie, and instead used other system settings > features to control the function of your trackpad? > > I initially thought from your bug description that the 'trackpad' tool > suddenly stopped working, after it had worked fine before. Now it > looks more likely that the 'trackpad' tool would not have worked for > you in Xubuntu either. > > Regards, > > Michael Schmitz > > > On Thu, Nov 27, 2014 at 4:42 AM, Herminio Hernandez, Jr. > <herminio.hernande...@gmail.com> wrote: >> Xubuntu 12.04 shipped by defaul with the 3.11 kernel. The release notes are >> here. The version of Jesse I am using is the Beta 2 running the 3.16-2 >> kernel. The only real change was the DE. When I was running MATE in the >> system setting I was able enable tap to click. However in LXDE I was not >> forcing to try the cli option. Here is my complet dmesg. >> >> On Tue, Nov 25, 2014 at 7:28 PM, Michael Schmitz <schmitz...@gmail.com> >> wrote: >>> >>> Herminio, >>> >>> can you send a complete dmesg log, not just the part where devices are >>> listed? Ben Herrenschmidt would like to have a look at the log. >>> >>> Also - what kernel versions did you run on the Xubuntu and Jessie >>> installations? Any boot messages retained from those >>> (/var/log/kern/log)? >>> >>> Regards, >>> >>> Michael Schmitz >>> >>> >>> On Wed, Nov 26, 2014 at 12:04 PM, Herminio Hernandez, Jr. >>> <herminio.hernande...@gmail.com> wrote: >>>> No problem any way I can help >>>> >>>> On Tue, Nov 25, 2014 at 5:01 PM, Michael Schmitz <schmitz...@gmail.com> >>>> wrote: >>>>> >>>>> Hi Herminio, >>>>> >>>>> thanks, that device tree demonstrates substantial differences between >>>>> the old PowerBook5,5 hardware and the newer 5,6 one. No mention of ADB >>>>> or trackpad in your device tree. >>>>> >>>>> I'll seek clarification from Ben Herrenschmidt about the changes to >>>>> the macio-adb driver in the 3.x kernels ... >>>>> >>>>> Thanks for your help! >>>>> >>>>> Regards, >>>>> >>>>> Michael Schmitz >>>>> >>>>> On Wed, Nov 26, 2014 at 11:30 AM, Herminio Hernandez, Jr. >>>>> <herminio.hernande...@gmail.com> wrote: >>>>>> sorry no attachment >>>>>> >>>>>> On Tue, Nov 25, 2014 at 4:30 PM, Herminio Hernandez, Jr. >>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>> >>>>>>> try this >>>>>>> >>>>>>> On Tue, Nov 25, 2014 at 3:35 PM, Michael Schmitz >>>>>>> <schmitz...@gmail.com> >>>>>>> wrote: >>>>>>>> >>>>>>>> Herminio, >>>>>>>> >>>>>>>> I got one approx. 20 minutes ago which only contained a symbolic >>>>>>>> link >>>>>>>> to /sys/firmware/devicetree/base - what I need is that >>>>>>>> /sys/firmware/devicetree/base path packed up, >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Michael Schmitz >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Nov 26, 2014 at 10:29 AM, Herminio Hernandez, Jr. >>>>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>>>> did youget my attachment? >>>>>>>>> >>>>>>>>> On Tue, Nov 25, 2014 at 3:27 PM, Michael Schmitz >>>>>>>>> <schmitz...@gmail.com> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> OK, that should help - I would still need your OF device tree to >>>>>>>>>> see >>>>>>>>>> what the 3.x kernels' ADB driver should make of the ADB I/O >>>>>>>>>> requests >>>>>>>>>> from trackpad. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Michael Schmitz >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Nov 26, 2014 at 10:20 AM, Herminio Hernandez, Jr. >>>>>>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>>>>>> I found a work around I was able to get two finger right >>>>>>>>>>> working >>>>>>>>>>> by >>>>>>>>>>> using >>>>>>>>>>> this command synclient TapButton2=3. I added that to my >>>>>>>>>>> 50-synaptics >>>>>>>>>>> file >>>>>>>>>>> so it will stick on reboot. >>>>>>>>>>> >>>>>>>>>>> On Tue, Nov 25, 2014 at 3:15 PM, Michael Schmitz >>>>>>>>>>> <schmitz...@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Herminio, >>>>>>>>>>>> >>>>>>>>>>>> that just contains a symbolic link - could you please tar up >>>>>>>>>>>> /sys/firmware/devicetree/base/ now? >>>>>>>>>>>> >>>>>>>>>>>> Assuming, of course, that directory exists ... >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> >>>>>>>>>>>> Michael Schmitz >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Nov 26, 2014 at 10:04 AM, Herminio Hernandez, Jr. >>>>>>>>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>>>>>>>> Here you go! >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Nov 25, 2014 at 2:53 PM, Michael Schmitz >>>>>>>>>>>>> <schmitz...@gmail.com> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Herminio, >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Nov 26, 2014 at 8:37 AM, Herminio Hernandez, Jr. >>>>>>>>>>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>>>>>>>>>> The command returned nothing. Here is from the kernel >>>>>>>>>>>>>>> config >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ sudo cat >>>>>>>>>>>>>>> /usr/src/linux-headers-3.16.0-4-powerpc/.config |grep >>>>>>>>>>>>>>> ADB >>>>>>>>>>>>>>> CONFIG_ADB=y >>>>>>>>>>>>>>> CONFIG_ADB_CUDA=y >>>>>>>>>>>>>>> CONFIG_ADB_PMU=y >>>>>>>>>>>>>>> CONFIG_ADB_PMU_LED=y >>>>>>>>>>>>>>> CONFIG_ADB_MACIO=y >>>>>>>>>>>>>>> CONFIG_INPUT_ADBHID=y >>>>>>>>>>>>>>> CONFIG_NET_TEAM_MODE_LOADBALANCE=m >>>>>>>>>>>>>> >>>>>>>>>>>>>> The necessary ADB support is there, but the device tree >>>>>>>>>>>>>> shows >>>>>>>>>>>>>> no >>>>>>>>>>>>>> ADB >>>>>>>>>>>>>> devices. You have not had the main board exchanged since >>>>>>>>>>>>>> using >>>>>>>>>>>>>> Xubuntu, by any chance? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can you tar up the contents of /proc/device-tree for me to >>>>>>>>>>>>>> compare >>>>>>>>>>>>>> with what I have on my PowerBook? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Michael Schmitz >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Nov 25, 2014 at 1:22 PM, Michael Schmitz >>>>>>>>>>>>>>> <schmitz...@gmail.com> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Herminio, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> your keyboard and trackpad appear to be USB devices, >>>>>>>>>>>>>>>> instead >>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>> ADB >>>>>>>>>>>>>>>> ones. My PowerBook (5,5) has the ADB ones - I recall >>>>>>>>>>>>>>>> that >>>>>>>>>>>>>>>> Apple >>>>>>>>>>>>>>>> changed the keyboard/trackpad to USB later on. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The trackpad tool from powerpc-utils only supports the >>>>>>>>>>>>>>>> ADB >>>>>>>>>>>>>>>> hardware >>>>>>>>>>>>>>>> variant. sorry. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm fairly certain this has been raised in the past - >>>>>>>>>>>>>>>> while >>>>>>>>>>>>>>>> support >>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>> program the trackpad via USB could be added in >>>>>>>>>>>>>>>> principle, >>>>>>>>>>>>>>>> what is >>>>>>>>>>>>>>>> needed is a detailed description of the commands >>>>>>>>>>>>>>>> necessary >>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>> detect >>>>>>>>>>>>>>>> and reprogram the trackpad device. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> You report that the trackpad setting was working when >>>>>>>>>>>>>>>> you >>>>>>>>>>>>>>>> used >>>>>>>>>>>>>>>> Xubuntu >>>>>>>>>>>>>>>> and Jessie - this suggests that your hardware is in >>>>>>>>>>>>>>>> fact >>>>>>>>>>>>>>>> capable >>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>> addressing the trackpad as ADB device, and the LXDE >>>>>>>>>>>>>>>> kernel >>>>>>>>>>>>>>>> instead >>>>>>>>>>>>>>>> exposes the ADB devices as USB ones. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Could you please check that the command >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> find /proc/device-tree -type d -name adb >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> returns one path name, and this path contains a >>>>>>>>>>>>>>>> 'mouse@3' >>>>>>>>>>>>>>>> or >>>>>>>>>>>>>>>> similar >>>>>>>>>>>>>>>> directory? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Could you also check that the option CONFIG_ADB is >>>>>>>>>>>>>>>> enabled >>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>> your >>>>>>>>>>>>>>>> kernel's config? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Michael Schmitz >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Nov 26, 2014 at 5:03 AM, Herminio Hernandez, >>>>>>>>>>>>>>>> Jr. >>>>>>>>>>>>>>>> <herminio.hernande...@gmail.com> wrote: >>>>>>>>>>>>>>>>> I am running Apple PowerBook G4. This was working >>>>>>>>>>>>>>>>> when I >>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>> Xubuntu >>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>> also when I was running the MATE desktop when I >>>>>>>>>>>>>>>>> installed >>>>>>>>>>>>>>>>> Jesse. >>>>>>>>>>>>>>>>> It >>>>>>>>>>>>>>>>> was >>>>>>>>>>>>>>>>> just >>>>>>>>>>>>>>>>> slowing down my system so I moved to LXDE as my >>>>>>>>>>>>>>>>> desktop. >>>>>>>>>>>>>>>>> bellow >>>>>>>>>>>>>>>>> are >>>>>>>>>>>>>>>>> my >>>>>>>>>>>>>>>>> logs. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ cat /proc/cpuinfo >>>>>>>>>>>>>>>>> processor : 0 >>>>>>>>>>>>>>>>> cpu : 7447A, altivec supported >>>>>>>>>>>>>>>>> clock : 833.333000MHz >>>>>>>>>>>>>>>>> revision : 1.2 (pvr 8003 0102) >>>>>>>>>>>>>>>>> bogomips : 36.86 >>>>>>>>>>>>>>>>> timebase : 18432000 >>>>>>>>>>>>>>>>> platform : PowerMac >>>>>>>>>>>>>>>>> model : PowerBook5,6 >>>>>>>>>>>>>>>>> machine : PowerBook5,6 >>>>>>>>>>>>>>>>> motherboard : PowerBook5,6 MacRISC3 Power Macintosh >>>>>>>>>>>>>>>>> detected as : 287 (PowerBook G4 15") >>>>>>>>>>>>>>>>> pmac flags : 0000001b >>>>>>>>>>>>>>>>> L2 cache : 512K unified >>>>>>>>>>>>>>>>> pmac-generation : NewWorld >>>>>>>>>>>>>>>>> Memory : 2048 MB >>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ uname -a >>>>>>>>>>>>>>>>> Linux debian-ppc 3.16-2-powerpc #1 Debian 3.16.3-2 >>>>>>>>>>>>>>>>> (2014-09-20) >>>>>>>>>>>>>>>>> ppc >>>>>>>>>>>>>>>>> GNU/Linux >>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ dmesg |grep device >>>>>>>>>>>>>>>>> [ 0.000229] Console: colour dummy device 80x25 >>>>>>>>>>>>>>>>> [ 0.001498] Initializing cgroup subsys devices >>>>>>>>>>>>>>>>> [ 0.030250] device-tree: Duplicate name in >>>>>>>>>>>>>>>>> PowerPC,G4@0, >>>>>>>>>>>>>>>>> renamed >>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>> "l2-cache#1" >>>>>>>>>>>>>>>>> [ 0.045852] vgaarb: device added: >>>>>>>>>>>>>>>>> PCI:0000:00:10.0,decodes=io+mem,owns=mem,locks=none >>>>>>>>>>>>>>>>> [ 0.062275] pci 0001:10:19.0: Can't enable PCI >>>>>>>>>>>>>>>>> device, >>>>>>>>>>>>>>>>> BIOS >>>>>>>>>>>>>>>>> handoff >>>>>>>>>>>>>>>>> failed. >>>>>>>>>>>>>>>>> [ 0.062296] pci 0001:10:1a.0: enabling device >>>>>>>>>>>>>>>>> (0000 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0002) >>>>>>>>>>>>>>>>> [ 0.114960] pci 0001:10:1b.0: enabling device >>>>>>>>>>>>>>>>> (0000 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0002) >>>>>>>>>>>>>>>>> [ 0.170924] pci 0001:10:1b.1: enabling device >>>>>>>>>>>>>>>>> (0000 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0002) >>>>>>>>>>>>>>>>> [ 0.226921] pci 0001:10:1b.2: enabling device >>>>>>>>>>>>>>>>> (0004 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0006) >>>>>>>>>>>>>>>>> [ 0.988432] radeonfb 0000:00:10.0: enabling device >>>>>>>>>>>>>>>>> (0006 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0007) >>>>>>>>>>>>>>>>> [ 2.034168] Console: switching to colour frame >>>>>>>>>>>>>>>>> buffer >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> 160x53 >>>>>>>>>>>>>>>>> [ 2.123200] pata-pci-macio 0002:24:0d.0: enabling >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> (0000 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0002) >>>>>>>>>>>>>>>>> [ 3.160097] mousedev: PS/2 mouse device common for >>>>>>>>>>>>>>>>> all >>>>>>>>>>>>>>>>> mice >>>>>>>>>>>>>>>>> [ 3.168453] input: PMU as >>>>>>>>>>>>>>>>> /devices/virtual/input/input0 >>>>>>>>>>>>>>>>> [ 3.492861] b43-pci-bridge 0001:10:12.0: enabling >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> (0004 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0006) >>>>>>>>>>>>>>>>> [ 3.503014] usbcore: registered new device driver >>>>>>>>>>>>>>>>> usb >>>>>>>>>>>>>>>>> [ 3.529009] ssb: Sonics Silicon Backplane found on >>>>>>>>>>>>>>>>> PCI >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> 0001:10:12.0 >>>>>>>>>>>>>>>>> [ 3.534501] firewire_ohci 0002:24:0e.0: enabling >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> (0000 >>>>>>>>>>>>>>>>> -> >>>>>>>>>>>>>>>>> 0002) >>>>>>>>>>>>>>>>> [ 3.539111] usb usb1: New USB device found, >>>>>>>>>>>>>>>>> idVendor=1d6b, >>>>>>>>>>>>>>>>> idProduct=0002 >>>>>>>>>>>>>>>>> [ 3.539116] usb usb1: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=3, >>>>>>>>>>>>>>>>> Product=2, >>>>>>>>>>>>>>>>> SerialNumber=1 >>>>>>>>>>>>>>>>> [ 3.586970] firewire_ohci 0002:24:0e.0: added OHCI >>>>>>>>>>>>>>>>> v1.10 >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> as >>>>>>>>>>>>>>>>> card >>>>>>>>>>>>>>>>> 0, 8 IR + 8 IT contexts, quirks 0x0 >>>>>>>>>>>>>>>>> [ 3.614863] usb usb2: New USB device found, >>>>>>>>>>>>>>>>> idVendor=1d6b, >>>>>>>>>>>>>>>>> idProduct=0001 >>>>>>>>>>>>>>>>> [ 3.614873] usb usb2: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=3, >>>>>>>>>>>>>>>>> Product=2, >>>>>>>>>>>>>>>>> SerialNumber=1 >>>>>>>>>>>>>>>>> [ 3.690648] usb usb3: New USB device found, >>>>>>>>>>>>>>>>> idVendor=1d6b, >>>>>>>>>>>>>>>>> idProduct=0001 >>>>>>>>>>>>>>>>> [ 3.690659] usb usb3: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=3, >>>>>>>>>>>>>>>>> Product=2, >>>>>>>>>>>>>>>>> SerialNumber=1 >>>>>>>>>>>>>>>>> [ 3.766567] usb usb4: New USB device found, >>>>>>>>>>>>>>>>> idVendor=1d6b, >>>>>>>>>>>>>>>>> idProduct=0001 >>>>>>>>>>>>>>>>> [ 3.766573] usb usb4: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=3, >>>>>>>>>>>>>>>>> Product=2, >>>>>>>>>>>>>>>>> SerialNumber=1 >>>>>>>>>>>>>>>>> [ 3.950986] usb 2-1: new full-speed USB device >>>>>>>>>>>>>>>>> number >>>>>>>>>>>>>>>>> 2 >>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>> ohci-pci >>>>>>>>>>>>>>>>> [ 4.089414] firewire_core 0002:24:0e.0: created >>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>> fw0: >>>>>>>>>>>>>>>>> GUID >>>>>>>>>>>>>>>>> 001124fffe84c4ea, S800 >>>>>>>>>>>>>>>>> [ 4.167986] usb 2-1: New USB device found, >>>>>>>>>>>>>>>>> idVendor=05ac, >>>>>>>>>>>>>>>>> idProduct=1000 >>>>>>>>>>>>>>>>> [ 4.167995] usb 2-1: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=0, >>>>>>>>>>>>>>>>> Product=0, >>>>>>>>>>>>>>>>> SerialNumber=0 >>>>>>>>>>>>>>>>> [ 4.318962] usb 2-2: new full-speed USB device >>>>>>>>>>>>>>>>> number >>>>>>>>>>>>>>>>> 3 >>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>> ohci-pci >>>>>>>>>>>>>>>>> [ 4.493965] usb 2-2: New USB device found, >>>>>>>>>>>>>>>>> idVendor=05ac, >>>>>>>>>>>>>>>>> idProduct=020e >>>>>>>>>>>>>>>>> [ 4.493975] usb 2-2: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=1, >>>>>>>>>>>>>>>>> Product=2, >>>>>>>>>>>>>>>>> SerialNumber=0 >>>>>>>>>>>>>>>>> [ 7.690753] lp: driver loaded but no devices found >>>>>>>>>>>>>>>>> [ 12.915824] usb 2-1: USB disconnect, device number >>>>>>>>>>>>>>>>> 2 >>>>>>>>>>>>>>>>> [ 13.274941] usb 2-1: new full-speed USB device >>>>>>>>>>>>>>>>> number >>>>>>>>>>>>>>>>> 4 >>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>> ohci-pci >>>>>>>>>>>>>>>>> [ 13.728988] usb 2-1: New USB device found, >>>>>>>>>>>>>>>>> idVendor=05ac, >>>>>>>>>>>>>>>>> idProduct=8205 >>>>>>>>>>>>>>>>> [ 13.729000] usb 2-1: New USB device strings: >>>>>>>>>>>>>>>>> Mfr=0, >>>>>>>>>>>>>>>>> Product=0, >>>>>>>>>>>>>>>>> SerialNumber=0 >>>>>>>>>>>>>>>>> [ 13.804872] input: appletouch as >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> /devices/pci0001:10/0001:10:1a.0/usb2/2-2/2-2:1.1/input/input1 >>>>>>>>>>>>>>>>> [ 13.978699] input: Apple Computer Apple Internal >>>>>>>>>>>>>>>>> Keyboard/Trackpad >>>>>>>>>>>>>>>>> as >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> /devices/pci0001:10/0001:10:1a.0/usb2/2-2/2-2:1.0/0003:05AC:020E.0003/input/input2 >>>>>>>>>>>>>>>>> [ 13.984661] input: Apple Computer Apple Internal >>>>>>>>>>>>>>>>> Keyboard/Trackpad >>>>>>>>>>>>>>>>> as >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> /devices/pci0001:10/0001:10:1a.0/usb2/2-2/2-2:1.2/0003:05AC:020E.0004/input/input3 >>>>>>>>>>>>>>>>> [ 15.052443] Bluetooth: HCI device and connection >>>>>>>>>>>>>>>>> manager >>>>>>>>>>>>>>>>> initialized >>>>>>>>>>>>>>>>> [ 47.274555] input: Mouseemu virtual keyboard as >>>>>>>>>>>>>>>>> /devices/virtual/input/input4 >>>>>>>>>>>>>>>>> [ 47.277738] input: Mouseemu virtual mouse as >>>>>>>>>>>>>>>>> /devices/virtual/input/input5 >>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~$ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Nov 25, 2014 at 2:07 AM, Michael Schmitz >>>>>>>>>>>>>>>>> <schmitz...@gmail.com> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> what hardware exactly does this happen on? Please >>>>>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>>>>> a >>>>>>>>>>>>>>>>>> copy >>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>> your >>>>>>>>>>>>>>>>>> boot log detailing the devices detected. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Note that the existence of /dev/adb does not >>>>>>>>>>>>>>>>>> necessarily >>>>>>>>>>>>>>>>>> imply >>>>>>>>>>>>>>>>>> presence >>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>> ADB support by your hardware, or the presence of a >>>>>>>>>>>>>>>>>> trackpad >>>>>>>>>>>>>>>>>> device >>>>>>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>> ADB bus in particular. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Michael Schmitz >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Package: powerpc-utils >>>>>>>>>>>>>>>>>>> Version: 1.1.3-25 >>>>>>>>>>>>>>>>>>> Severity: normal >>>>>>>>>>>>>>>>>>> File: /sbin/trackpad >>>>>>>>>>>>>>>>>>> Tags: d-i >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Dear Maintainer, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> For some reason I am getting this error when I try >>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>> enable >>>>>>>>>>>>>>>>>>> tap >>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>> click >>>>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>>>> the trackpad command. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~/Documents$ sudo trackpad >>>>>>>>>>>>>>>>>>> tap >>>>>>>>>>>>>>>>>>> [sudo] password for rican-linux: >>>>>>>>>>>>>>>>>>> writing /dev/adb: No such device or address >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> However I do have that device... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~/Documents$ ls -l /dev/adb >>>>>>>>>>>>>>>>>>> crw------- 1 root root 56, 0 Nov 24 21:44 /dev/adb >>>>>>>>>>>>>>>>>>> rican-linux@debian-ppc:~/Documents$ >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- System Information: >>>>>>>>>>>>>>>>>>> Debian Release: jessie/sid >>>>>>>>>>>>>>>>>>> APT prefers testing-updates >>>>>>>>>>>>>>>>>>> APT policy: (500, 'testing-updates'), (500, >>>>>>>>>>>>>>>>>>> 'testing') >>>>>>>>>>>>>>>>>>> Architecture: powerpc (ppc) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Kernel: Linux 3.16-2-powerpc >>>>>>>>>>>>>>>>>>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 >>>>>>>>>>>>>>>>>>> (charmap=UTF-8) >>>>>>>>>>>>>>>>>>> Shell: /bin/sh linked to /bin/dash >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Versions of packages powerpc-utils depends on: >>>>>>>>>>>>>>>>>>> ii libc6 2.19-13 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> powerpc-utils recommends no packages. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> powerpc-utils suggests no packages. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- no debconf information >> >> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org