Page 1 of 15 12311 ... LastLast
Results 1 to 10 of 146

Thread: Will Ubuntu work on the Surface Pro 2 like it did on the original?

  1. #1
    Join Date
    Dec 2007
    Location
    Norfolk
    Beans
    63
    Distro
    Ubuntu 11.04 Natty Narwhal

    Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Hi, I was wondering if anyone could answer this before I purchase one. I would have thought that it should work seeing as the Secure Boot feature can still be disabled, although I understand there were WiFi issues with the original Surface Pro so I would imagine that these may still be present in the Pro 2. I understand there is a fix for the original however and am hopeful.

    Thanks in advance for your input

  2. #2
    Join Date
    Oct 2013
    Beans
    4

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Hi. I have the Surface Pro 2 and installed Ubuntu 13.10 on it. The wifi/bluetooth does not work by default. It's the same wifi hardware as before (Marvell 350N), so would I expect the solutions for Surface Pro 1 to work. I tried a few, but could not manage to get the wifi to work. I also manually installed the latest Saucy mainline kernel (v3.11.6), but wifi still does not work. I have some experience with Linux/Ubuntu. I'm currently using my Nexus 4 as a USB modem to access internet; this works out of the box.

  3. #3
    Join Date
    Oct 2013
    Beans
    10

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Radu,

    Are you using a type cover or a touch cover? I tried dual booting with Ubuntu 13 and 14 and neither was able to recognize the type cover 2. Got it to install fine, but it is not fun having to use the on screen keyboard for all the first install stuff.

  4. #4
    Join Date
    Nov 2013
    Beans
    1

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    hi radu,
    which version of Ubuntu did you use ? (12.04 or 13.10) & ( amd64 OR X86 ).
    thanks.

  5. #5
    Join Date
    Nov 2013
    Beans
    16

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    @gubskilldreams: confirmed with Ubuntu 13.10 (standard release and even saucy daily), I am also unable to get my Surface Pro 2 with type cover 2 to work with Ubuntu. (The keyboard & trackpad are dead, not even the caps lock lights up when pressed, indicating that it is not receiving interrupts and hence a lack of driver support.) The strangest thing is that the Grub bootloader works properly with the keyboard in the type cover 2, even though it does not work in Ubuntu.

    I am able to boot via USB drive the live Ubuntu distribution on my Surface Pro and the pen & touch inputs work great, especially with an external USB keyboard, but the bluetooth+WiFi networking does not work.

    I cannot find any info on how to get the Type Cover 2 and networking to work under Ubuntu on my Surface Pro 2.

  6. #6
    Join Date
    Jan 2007
    Beans
    95
    Distro
    Ubuntu

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    I booted SystemRescueCd 3.8.1 off liveUSB, and the keyboard was working well in the console with the default kernel, version 3.4.<something>. I was also getting data out of the touchpad via some device files in /dev/input/, but wasn't able to load X. The input devices seemed to be coming from USB device 045e:07a9 -> manufacturer "MICROSOFT", product name "SAM".

    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. It could be a kernel regression.

  7. #7
    Join Date
    Oct 2013
    Beans
    4

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    In installed Ubuntu 13.10 amd64. I get the same behavior as alicia4542 with the type keyboard 2: it works in grub but not in Ubuntu.

  8. #8
    Join Date
    Nov 2013
    Beans
    16

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Quote Originally Posted by PointSource View Post
    I booted SystemRescueCd 3.8.1 off liveUSB, and the keyboard was working well in the console with the default kernel, version 3.4.<something>. I was also getting data out of the touchpad via some device files in /dev/input/, but wasn't able to load X. The input devices seemed to be coming from USB device 045e:07a9 -> manufacturer "MICROSOFT", product name "SAM".
    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. It could be a kernel regression.
    As 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.

    Your assumption of a kernel driver regression for the touch/type cover 2 may likely be true. But I am not sure how to address this. 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?

    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.

    Thank you in advance.

  9. #9
    Join Date
    May 2008
    Beans
    13

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Hi Guys, just received my Pro 2 yesterday and installed ubuntu today.

    I can confirm that neither wifi nor my touch cover 2 work. Bluetooth seems fine.

    For the keyboard

    I fully aggree with PointSource.
    Quote Originally Posted by PointSource View Post
    -> manufacturer "MICROSOFT", product name "SAM"..
    the Xorg log shows various entries for the keyboard. It seems that plug and play works. The keyboard is referred to as "MICROSOFT SAM" and is removed and added everytime I snap the keyboard on and off.

    the Xorg.log show the following right after snapping the keyboard on:
    Code:
    [  1625.773] (II) config/udev: removing device MICROSOFT SAM
    [  1625.804] (II) evdev: MICROSOFT SAM: Close
    [  1625.804] (II) UnloadModule: "evdev"
    [  1626.172] (II) config/udev: Adding input device MICROSOFT SAM (/dev/input/mouse0)
    [  1626.172] (II) No input driver specified, ignoring this device.
    [  1626.172] (II) This device may have been added with another device file.
    [  1626.174] (II) config/udev: Adding input device MICROSOFT SAM (/dev/input/event3)
    [  1626.174] (**) MICROSOFT SAM: Applying InputClass "evdev pointer catchall"
    [  1626.174] (**) MICROSOFT SAM: Applying InputClass "evdev keyboard catchall"
    [  1626.174] (**) MICROSOFT SAM: Applying InputClass "evdev tablet catchall"
    [  1626.174] (II) Using input driver 'evdev' for 'MICROSOFT SAM'
    [  1626.174] (**) MICROSOFT SAM: always reports core events
    [  1626.174] (**) evdev: MICROSOFT SAM: Device: "/dev/input/event3"
    [  1626.174] (--) evdev: MICROSOFT SAM: Vendor 0x45e Product 0x799
    [  1626.174] (--) evdev: MICROSOFT SAM: Found 3 mouse buttons
    [  1626.174] (--) evdev: MICROSOFT SAM: Found relative axes
    [  1626.174] (--) evdev: MICROSOFT SAM: Found x and y relative axes
    [  1626.174] (--) evdev: MICROSOFT SAM: Found absolute axes
    [  1626.174] (--) evdev: MICROSOFT SAM: Found x and y absolute axes
    [  1626.174] (--) evdev: MICROSOFT SAM: Found absolute tablet.
    [  1626.174] (--) evdev: MICROSOFT SAM: Found keys
    [  1626.174] (II) evdev: MICROSOFT SAM: Configuring as tablet
    [  1626.174] (II) evdev: MICROSOFT SAM: Configuring as keyboard
    [  1626.174] (**) evdev: MICROSOFT SAM: YAxisMapping: buttons 4 and 5
    [  1626.174] (**) evdev: MICROSOFT SAM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  1626.174] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1/input/input17/event3"
    [  1626.174] (II) XINPUT: Adding extended input device "MICROSOFT SAM" (type: KEYBOARD, id 9)
    [  1626.174] (**) Option "xkb_rules" "evdev"
    [  1626.174] (**) Option "xkb_model" "pc105"
    [  1626.174] (**) Option "xkb_layout" "us"
    [  1626.174] (WW) evdev: MICROSOFT SAM: touchpads, tablets and touchscreens ignore relative axes.
    [  1626.174] (II) evdev: MICROSOFT SAM: initialized for absolute axes.
    [  1626.174] (**) MICROSOFT SAM: (accel) keeping acceleration scheme 1
    [  1626.174] (**) MICROSOFT SAM: (accel) acceleration profile 0
    [  1626.174] (**) MICROSOFT SAM: (accel) acceleration factor: 2.000
    [  1626.174] (**) MICROSOFT SAM: (accel) acceleration threshold: 4
    that looks promising but the keyboard does not work. no input events are fired (tested with xev).

    any idea where I can continue with my troubleshoot?

  10. #10
    Join Date
    Jan 2007
    Beans
    95
    Distro
    Ubuntu

    Re: Will Ubuntu work on the Surface Pro 2 like it did on the original?

    Quote Originally Posted by alicia4542 View Post
    Your assumption of a kernel driver regression for the touch/type cover 2 may likely be true. But I am not sure how to address this. 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?
    Here is the pertinent kernel log chunk from SysRescueCD's v3.4.66 kernel:
    Code:
    [   61.954231] usb 2-3: USB disconnect, device number 4
    [   61.960162] ACPI Error: [\SB__.IADP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
    [   61.960182] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._Q41] (Node ffff880119a96438), AE_NOT_FOUND (20120320/psparse-536)
    [   62.324511] usb 2-3: new full-speed USB device number 11 using xhci_hcd
    [   62.337459] usb 2-3: New USB device found, idVendor=045e, idProduct=07a9
    [   62.337469] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [   62.337474] usb 2-3: Product: SAM
    [   62.337478] usb 2-3: Manufacturer: MICROSOFT
    [   62.337482] usb 2-3: SerialNumber: 0.1.0000
    [   62.342602] generic-usb 0003:045E:07A9.000A: logical range invalid 0 -1
    [   62.342630] generic-usb 0003:045E:07A9.000A: item 0 1 0 11 parsing failed
    [   62.342660] generic-usb: probe of 0003:045E:07A9.000A failed with error -22
    [   62.345318] input: MICROSOFT SAM as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1/input/input9
    [   62.345710] generic-usb 0003:045E:07A9.000B: input,hidraw0: USB HID v1.11 Keyboard [MICROSOFT SAM] on usb-0000:00:14.0-3/input1
    [   62.349718] input: MICROSOFT SAM as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input10
    [   62.350018] generic-usb 0003:045E:07A9.000C: input,hiddev0,hidraw7: USB HID v1.11 Keyboard [MICROSOFT SAM] on usb-0000:00:14.0-3/input2
    And from ubuntu's v3.11.0 kernel:
    Code:
    [  124.249057] usb 2-3: USB disconnect, device number 5
    [  124.259049] ACPI Error: [\SB__.IADP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359)
    [  124.259072] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._Q41] (Node ffff880119ab1438), AE_NOT_FOUND (20130517/psparse-536)
    [  124.619306] usb 2-3: new full-speed USB device number 12 using xhci_hcd
    [  124.637245] usb 2-3: New USB device found, idVendor=045e, idProduct=07a9
    [  124.637255] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  124.637260] usb 2-3: Product: SAM
    [  124.637264] usb 2-3: Manufacturer: MICROSOFT
    [  124.637268] usb 2-3: SerialNumber: 0.1.0000
    [  124.650270] input: MICROSOFT SAM as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.1/input/input18
    [  124.650541] hid-generic 0003:045E:07A9.000B: input,hidraw1: USB HID v1.11 Keyboard [MICROSOFT SAM] on usb-0000:00:14.0-3/input1
    [  124.654093] hid-multitouch 0003:045E:07A9.000C: HID_DG_INPUTMODE out of range
    [  124.654151] hid-multitouch 0003:045E:07A9.000C: No inputs registered, leaving
    [  124.654337] hid-multitouch 0003:045E:07A9.000C: hiddev0,hidraw8: USB HID v1.11 Keyboard [MICROSOFT SAM] on usb-0000:00:14.0-3/input2
    You'll notice that for HID device "0003:045E:07A9.000C", the kernels are loading different hid sub-drivers; "generic-usb" (which I think is now called hid-generic?) vs "hid-multitouch". While multitouch support might be neccesary for the type cover's integrated touchpad, for the time being it'd be better to have the keyboard working. I still haven't figured out how to unbind and re-bind the device to the other driver yet.

    Quote Originally Posted by alicia4542 View Post
    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.
    You can dual-boot the Surface, just resize Window's partition down a bit. Don't forget to create a recovery drive before you do anything, so you can get back to a clean slate if things go wrong.

    Quote Originally Posted by ubootfanat View Post
    the Xorg log shows various entries for the keyboard. It seems that plug and play works. The keyboard is referred to as "MICROSOFT SAM" and is removed and added everytime I snap the keyboard on and off.

    that looks promising but the keyboard does not work. no input events are fired (tested with xev).

    any idea where I can continue with my troubleshoot?
    If you run:
    Code:
    # cat /dev/hidraw8
    (or the hidraw number that comes from the "hid-multitouch 0003:045E:07A9.xxxx"... line in your kernel log, you'll see that the keyboard and mouse are spewing out data, linux just isn't interpreting it right. The input device that Xorg is registering is actually the windows key capacitive touch button under the screen, as far as I can tell.

    As for wifi, this kernel bug: Bug 64111 - mwifiex_usb USB8797 fails to start seems to indicate it might be a problem with the USB3 controller rather than the wireless card. I haven't tried the steps listed there yet, but I managed to get the device half-working with a firmware extracted from "C:\Windows\System32\drivers\mwlu97w8x64.sys" under Win8.1, but didn't keep it because I was worried messing around with the firmware would do permanent damage to the wireless chip.

Page 1 of 15 12311 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •