usb 2-3: new full-speed USB device number 12 using xhci_hcd ACPI Error: Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) usb 2-3: USB disconnect, device number 5 usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-3: New USB device found, idVendor=045e, idProduct=07a9 usb 2-3: new full-speed USB device number 11 using xhci_hcd ACPI Error: Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) usb 2-3: USB disconnect, device number 4 Here is the pertinent kernel log chunk from SysRescueCD's v3.4.66 kernel: no input events are fired (tested with xev).Īny idea where I can continue with my troubleshoot? That looks promising but the keyboard does not work. (**) MICROSOFT SAM: (accel) acceleration threshold: 4 (**) MICROSOFT SAM: (accel) acceleration factor: 2.000 (**) MICROSOFT SAM: (accel) acceleration profile 0 (**) MICROSOFT SAM: (accel) keeping acceleration scheme 1 (II) evdev: MICROSOFT SAM: initialized for absolute axes. (WW) evdev: MICROSOFT SAM: touchpads, tablets and touchscreens ignore relative axes. (II) XINPUT: Adding extended input device "MICROSOFT SAM" (type: KEYBOARD, id 9) (**) evdev: MICROSOFT SAM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (**) evdev: MICROSOFT SAM: YAxisMapping: buttons 4 and 5 (II) evdev: MICROSOFT SAM: Configuring as keyboard (II) evdev: MICROSOFT SAM: Configuring as tablet (-) evdev: MICROSOFT SAM: Found absolute tablet. (-) evdev: MICROSOFT SAM: Found x and y absolute axes
(-) evdev: MICROSOFT SAM: Found absolute axes (-) evdev: MICROSOFT SAM: Found x and y relative axes (-) evdev: MICROSOFT SAM: Found relative axes (-) evdev: MICROSOFT SAM: Found 3 mouse buttons (-) evdev: MICROSOFT SAM: Vendor 0x45e Product 0x799 (**) evdev: MICROSOFT SAM: Device: "/dev/input/event3"
(**) MICROSOFT SAM: always reports core events
(II) Using input driver 'evdev' for 'MICROSOFT SAM' (**) MICROSOFT SAM: Applying InputClass "evdev tablet catchall" (**) MICROSOFT SAM: Applying InputClass "evdev keyboard catchall" (**) MICROSOFT SAM: Applying InputClass "evdev pointer catchall" (II) config/udev: Adding input device MICROSOFT SAM (/dev/input/event3) (II) This device may have been added with another device file.
(II) No input driver specified, ignoring this device. (II) config/udev: Adding input device MICROSOFT SAM (/dev/input/mouse0) (II) config/udev: removing device MICROSOFT SAM The Xorg.log show the following right after snapping the keyboard on: The keyboard is referred to as "MICROSOFT SAM" and is removed and added everytime I snap the keyboard on and off. The Xorg log shows various entries for the keyboard. > manufacturer "MICROSOFT", product name "SAM". I can confirm that neither wifi nor my touch cover 2 work.
Hi Guys, just received my Pro 2 yesterday and installed ubuntu today.
I really hope to be able to get Ubuntu to work with the touch/type cover 2 keyboard+trackpad, while running under a USB flash drive, before I would be confident in wiping out Windows 8.1 from the main internal drive.
Does anyone have any suggestions on a fix for this, such as a different Ubuntu ISO image or a different kernel module for the cover 2 keyboard? Your assumption of a kernel driver regression for the touch/type cover 2 may likely be true. It could be a kernel regression.Īs previously mentioned with Ubuntu 13.10 ISO, with live USB, X windows works great for me with pen and touch inputs on the Surface Pro 2, even though the touch/type cover 2 is dead. However, the alternate 3.10.x kernel on the same liveUSB lost support for the keyboard and the mouse, but was able to boot to X. The input devices seemed to be coming from USB device 045e:07a9 -> manufacturer "MICROSOFT", product name "SAM". I was also getting data out of the touchpad via some device files in /dev/input/, but wasn't able to load X. I booted SystemRescueCd 3.8.1 off liveUSB, and the keyboard was working well in the console with the default kernel, version 3.4.