Re: [qubes-users] mooltipass hardware password manager
Hi, thanks for you help! I dug around a little more, but could not find anything wrong within qubes, the device seems to be recognized as a keyboard, everything looks fine. So I went to test the device itself, and it turns out it simply does not type out the password. So I'll ask the mooltipass people for advice instead. Thanks again, it was very helpful :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/871b926d-a645-44d5-8c3b-0c93ff115336%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] mooltipass hardware password manager
Hi, I have a Mooltipass Mini Hardware Password manager (https://www.themooltipass.com/), which identifies as a USB keyboard in order to input passwords. I can attach the USB device to a VM to connect to the mooltipass mini and put in credentials, but I cannot get it to input the password, neither by attaching it to a VM directly, nor by leaving it in the USB qube via the input proxy. The key events just don't seem to turn up anywhere. I'm running latest stable R4. My USB keyboard, touchpad and touchscreen work, also I don't have any problems with other USB devices. How can I debug this further? journalctl output while connecting: Jan 10 00:21:07 sys-usb kernel: usb 2-1: new full-speed USB device number 10 using xhci_hcd Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device found, idVendor=16d0, idProduct=09a0 Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jan 10 00:21:07 sys-usb kernel: usb 2-1: Product: Mooltipass Jan 10 00:21:07 sys-usb kernel: usb 2-1: Manufacturer: SE Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001B: hiddev96,hidraw1: USB HID v1.11 Device [SE Mooltipass] on usb-:00:07.0-1/input0 Jan 10 00:21:07 sys-usb kernel: input: SE Mooltipass as /devices/pci:00/:00:07.0/usb2/2-1/2-1:1.1/0003:16D0:09A0.001C/input/input36 Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001C: input,hidraw2: USB HID v1.11 Keyboard [SE Mooltipass] on usb-:00:07.0-1/input1 Jan 10 00:21:07 sys-usb mtp-probe[30635]: checking bus 2, device 10: "/sys/devices/pci:00/:00:07.0/usb2/2-1" Jan 10 00:21:07 sys-usb mtp-probe[30635]: bus: 2, device: 10 was not an MTP device Jan 10 00:21:07 sys-usb kernel: audit: type=1130 audit(1547076067.807:236): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 10 00:21:07 sys-usb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 10 00:21:07 sys-usb systemd[1]: Started Qubes input proxy sender (keyboard). Jan 10 00:21:07 sys-usb systemd-logind[436]: Watching system buttons on /dev/input/event6 (SE Mooltipass) lsusb output of the device: Bus 002 Device 010: ID 16d0:09a0 MCS Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize032 idVendor 0x16d0 MCS idProduct 0x09a0 bcdDevice1.00 iManufacturer 1 SE iProduct2 Mooltipass iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 66 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 28 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0
[qubes-users] Re: How to Backup Qubes Using New USB Hard Drive
The short answer is: You do not need to do anything with the disk. Just connect it, as you noticed it gets attached to dom0. Then use the Qubes manager to backup your VMs, they will be stored in one compressed file, so the disk format doesn't matter much. That's all. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bdcc0af9-d036-4a4e-8add-449c858c09d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Thunderbolt Dockingstation: PCI bridges and nested PCI devices
Hi, as I described earlier (https://groups.google.com/forum/#!msg/qubes-users/uk11tSeu5yU/XtNtOErgDQAJ) I'm using an Asus Transformer Pro 3 with the Thunderbolt 3 docking station, but I cannot get the docks Ethernet device inside a qube. I've not made any headway in solving this, but I noticed something that might be the reaseon: /sys/bus/usb/devices/ ├── 1-0:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-0:1.0 ├── 1-1 -> ../../../devices/pci:00/:00:14.0/usb1/1-1 ├── 1-1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1 ├── 1-1:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0 ├── 1-1.1:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0 ├── 1-1.1:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.1 ├── 1-1.1:1.2 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.2 ├── 1-1.1:1.3 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.3 ├── 1-4 -> ../../../devices/pci:00/:00:14.0/usb1/1-4 ├── 1-4:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 ├── 1-4:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 ├── 1-7 -> ../../../devices/pci:00/:00:14.0/usb1/1-7 ├── 1-7:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0 ├── 1-7:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.1 ├── 1-8 -> ../../../devices/pci:00/:00:14.0/usb1/1-8 ├── 1-8:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0 ├── 1-8:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.1 ├── 1-8:1.2 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.2 ├── 2-0:1.0 -> ../../../devices/pci:00/:00:14.0/usb2/2-0:1.0 ├── 2-1 -> ../../../devices/pci:00/:00:14.0/usb2/2-1 ├── 2-1:1.0 -> ../../../devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0 ├── 3-0:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-0:1.0 ├── 3-1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1 ├── 3-1.1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1 ├── 3-1:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1:1.0 ├── 3-1.1:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1:1.0 ├── 3-1.1.2 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2 ├── 3-1.1.2:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.0 ├── 3-1.1.2:1.1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.1 ├── 3-1.1.2:1.2 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.2 ├── 3-1.1.2:1.3 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.3 ├── 3-1.1.4 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4 ├── 3-1.1.4:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4/3-1.1.4:1.0 ├── 3-1.1.4:1.1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4/3-1.1.4:1.1 ├── 4-0:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-0:1.0 ├── 4-1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1 ├── 4-1.1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1 ├── 4-1:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1:1.0 ├── 4-1.1.1 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1.1 ├── 4-1.1:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1:1.0 ├── 4-1.1.1:1.0 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1.1/4-1.1.1:1.0 ├── usb1 -> ../../../devices/pci:00/:00:14.0/usb1 ├── usb2 -> ../../../devices/pci:00/:00:14.0/usb2 ├── usb3 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3 └── usb4 -> ../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4 USB3 and USB4 are the USB devices on the docking station, as you can see those are nested deeper in the structure, below several PCI bridges. I suppose this might be the reason I cannot assign those devices correctly to a qube. Neither assigning the USB device alone, nor all superordinate devices works. Also I cannot enable permissive mode for these devices, it always says "no such device": sudo sh
Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
The only thing I could find is this, from dom0s dmesg: [ 29.251207] xhci_hcd :05:00.0: remove, state 1 [ 29.251216] usb usb4: USB disconnect, device number 1 [ 29.251218] usb 4-1: USB disconnect, device number 2 [ 29.251219] usb 4-1.1: USB disconnect, device number 3 [ 29.251220] usb 4-1.1.1: USB disconnect, device number 4 [ 29.253988] xhci_hcd :05:00.0: USB bus 4 deregistered [ 29.254071] xhci_hcd :05:00.0: remove, state 1 [ 29.254079] usb usb3: USB disconnect, device number 1 [ 29.254081] usb 3-1: USB disconnect, device number 2 [ 29.254084] usb 3-1.1: USB disconnect, device number 3 [ 29.254086] usb 3-1.1.2: USB disconnect, device number 6 [ 29.289813] usb 3-1.1.4: USB disconnect, device number 7 [ 29.290279] usb 3-1.2: USB disconnect, device number 4 [ 29.399835] xhci_hcd :05:00.0: USB bus 3 deregistered [ 29.400369] pciback :05:00.0: seizing device [ 29.400479] xen: registering gsi 18 triggering 0 polarity 1 [ 29.400484] Already setup the GSI :18 [ 29.803790] loop: module loaded [ 30.366119] xen_pciback: vpci: :05:00.0: assign to virtual slot 0 [ 30.366446] pciback :05:00.0: registering for 1 [ 30.367301] xen_pciback: vpci: :3a:00.0: assign to virtual slot 1 [ 30.367631] pciback :3a:00.0: registering for 1 [ 31.693098] xen-blkback: event-channel 17 [ 31.693193] xen-blkback: /local/domain/1/device/vbd/51712:using single page: ring-ref 8 [ 31.693323] xen-blkback: ring-pages:1, event-channel 17, protocol 1 (x86_64-abi) persistent grants [ 31.705391] xen-blkback: event-channel 18 [ 31.705512] xen-blkback: /local/domain/1/device/vbd/51728:using single page: ring-ref 9 [ 31.705603] xen-blkback: ring-pages:1, event-channel 18, protocol 1 (x86_64-abi) persistent grants [ 31.713185] xen-blkback: event-channel 19 [ 31.713372] xen-blkback: /local/domain/1/device/vbd/51744:using single page: ring-ref 10 [ 31.713503] xen-blkback: ring-pages:1, event-channel 19, protocol 1 (x86_64-abi) persistent grants [ 31.721737] xen-blkback: event-channel 20 [ 31.721815] xen-blkback: /local/domain/1/device/vbd/51760:using single page: ring-ref 11 [ 31.721890] xen-blkback: ring-pages:1, event-channel 20, protocol 1 (x86_64-abi) persistent grants [ 32.696932] pciback :05:00.0: Driver tried to write to a read-only configuration space field at offset 0x8a, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. [ 32.697621] pciback :05:00.0: enabling device ( -> 0002) Permissive mode is already enabled for the device, so I think the only remaining thing is to report this to the xen-devel list... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8ccfeef3-4576-4199-aa55-313429e66388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
Am Sonntag, 4. Dezember 2016 22:59:28 UTC+1 schrieb Marek Marczykowski-Górecki: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sun, Dec 04, 2016 at 12:18:23AM -0800, Benjamin Richter wrote: > > Am Sonntag, 4. Dezember 2016 01:33:31 UTC+1 schrieb Marek > > Marczykowski-Górecki: > > > > > > I've attached the ethernet dongle to the same port as the logitech > > > > keyboard, but it does not show up anywhere. > > > > > > If you see the device in dom0 in some configuration, take a look at its > > > sysfs path - it will have a hint on which controller is it. Like this: > > > lrwxrwxrwx 1 root root 0 Dec 4 01:32 /sys/bus/usb/devices/3-1 -> > > > ../../../devices/pci-0/pci:00/:00:02.0/usb3/3-1 > > > > > > - -- > > > Best Regards, > > > Marek Marczykowski-Górecki > > > Invisible Things Lab > > > A: Because it messes up the order in which people normally read text. > > > Q: Why is top-posting such a bad thing? > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v2 > > > > > > iQEcBAEBCAAGBQJYQ2RWAAoJENuP0xzK19csKxMH/3rkY6pxlWVSjltPRc1r2jGn > > > njWyqDEA6Zoe56gAQ3zS1ORX54hgpEw6omZgzB3bY9KI2U3ihLncJ4jF8mVwxa+S > > > rTCFF1Flqp8Olk2jTXc2lobdLcOQBMQXXfNq4GbpHkl0C+ZVIa1n7lndfJI9WA21 > > > TKA3gsW/SY8EgBjYtFO0Emnhr5WMi3jYyt/qSWU8jrYn92IoZnx6CbpQp8xA/S8L > > > KLvt7WUnBjuFX+k4z9hodXHq6eU00YNqOEI4fm0+y92PPSjIGKbDhClCstSMMXRE > > > RqlbJmWpBasYBPm2pOg+1C0Vkeg593TtxahLd2k8MuFZUjrCjY4OXwA7+YkHFRA= > > > =4hF8 > > > -END PGP SIGNATURE- > > > > That's really quite clear, here's a lsusb output from dom0 with both usb > > controllers. Here the ASIX and Realtek ethernet deivces show up on bus 004. > > > > Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit > > Ethernet > > Bus 004 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. > > Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. > > Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 003 Device 004: ID 046d:c51e Logitech, Inc. > > Bus 003 Device 007: ID 1e4e:0898 Cubeternet > > Bus 003 Device 006: ID 0572:1703 Conexant Systems (Rockwell), Inc. > > Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. > > Bus 001 Device 003: ID 8087:0a2a Intel Corp. > > Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > lsusb of dom0 after attaching the controller to sys-net: > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. > > Bus 001 Device 003: ID 8087:0a2a Intel Corp. > > Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > and of sys-net: > > sudo lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 002 Device 004: ID 046d:c51e Logitech, Inc. > > Bus 002 Device 006: ID 1e4e:0898 Cubeternet > > Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. > > Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > The Logitech keyboard attached to the docking station is there, but neither > > the asix dongle nor the docks ethernet port show up. It seems dom0s usb bus > > 004 got lost somewhere. > > Interestingly, if I switch the ethernet dongle and the logitech keyboard, > > the keyboard shows up on another port, but the dongle does not show up. > > > > I have no idea what's going on. > > It looks like none of devices from that bus show up (just root hub). > Anything interesting in dmesg there? I'd recommend looking for more than > just "grep usb" - for example some messages may contain only xhci, or > just pci BDF. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-po
Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
Am Sonntag, 4. Dezember 2016 01:33:31 UTC+1 schrieb Marek Marczykowski-Górecki: > > I've attached the ethernet dongle to the same port as the logitech > > keyboard, but it does not show up anywhere. > > If you see the device in dom0 in some configuration, take a look at its > sysfs path - it will have a hint on which controller is it. Like this: > lrwxrwxrwx 1 root root 0 Dec 4 01:32 /sys/bus/usb/devices/3-1 -> > ../../../devices/pci-0/pci:00/:00:02.0/usb3/3-1 > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYQ2RWAAoJENuP0xzK19csKxMH/3rkY6pxlWVSjltPRc1r2jGn > njWyqDEA6Zoe56gAQ3zS1ORX54hgpEw6omZgzB3bY9KI2U3ihLncJ4jF8mVwxa+S > rTCFF1Flqp8Olk2jTXc2lobdLcOQBMQXXfNq4GbpHkl0C+ZVIa1n7lndfJI9WA21 > TKA3gsW/SY8EgBjYtFO0Emnhr5WMi3jYyt/qSWU8jrYn92IoZnx6CbpQp8xA/S8L > KLvt7WUnBjuFX+k4z9hodXHq6eU00YNqOEI4fm0+y92PPSjIGKbDhClCstSMMXRE > RqlbJmWpBasYBPm2pOg+1C0Vkeg593TtxahLd2k8MuFZUjrCjY4OXwA7+YkHFRA= > =4hF8 > -END PGP SIGNATURE- That's really quite clear, here's a lsusb output from dom0 with both usb controllers. Here the ASIX and Realtek ethernet deivces show up on bus 004. Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 004 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 046d:c51e Logitech, Inc. Bus 003 Device 007: ID 1e4e:0898 Cubeternet Bus 003 Device 006: ID 0572:1703 Conexant Systems (Rockwell), Inc. Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsusb of dom0 after attaching the controller to sys-net: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and of sys-net: sudo lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 046d:c51e Logitech, Inc. Bus 002 Device 006: ID 1e4e:0898 Cubeternet Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The Logitech keyboard attached to the docking station is there, but neither the asix dongle nor the docks ethernet port show up. It seems dom0s usb bus 004 got lost somewhere. Interestingly, if I switch the ethernet dongle and the logitech keyboard, the keyboard shows up on another port, but the dongle does not show up. I have no idea what's going on. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/04d151c7-a36b-4a61-8278-5cafabf141b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
Am Sonntag, 4. Dezember 2016 01:19:45 UTC+1 schrieb Marek Marczykowski-Górecki: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sat, Dec 03, 2016 at 04:14:48PM -0800, Benjamin Richter wrote: > > I have revisited an earlier approach with some more success. > > I attached only the usb controller, not the bridges. This seems to work: > > > > sudo lspci > > 00:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller > > [Alpine Ridge] > > 00:01.0 Network controller: Intel Corporation Wireless 7265 (rev 59) > > > > sudo lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 002 Device 007: ID 046d:c51e Logitech, Inc. > > Bus 002 Device 006: ID 1e4e:0898 Cubeternet > > Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. > > Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > So some devices are there, like the SD card reader, audio device and the > > usb hubs. The usb hubs even work, the Logitec device is an external > > keyboard I connected. > > > > But the ethernet device is not there, nor the usb ethernet dongle that's > > also connected to the usb hub. Both show up on dom0 if I connect them, but > > since dom0 has no networking, I cannot say if they would work. > > Maybe those are on the other USB controller - 00:14.0 ? Try attaching > that too to the sys-net. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYQ2EbAAoJENuP0xzK19cs1wwH/3jZh8JqNh1tqPJmaCxYzBA1 > nmCNJbZ7GDXk19ZJDfMeDsmaZ3OilvhjimAKf/43lvJMjQuzyneCjOwWW6Tef4zQ > CRPb3gVdiE5DdJ1Gq5Yz93VRP41Y26eN26SIKEk6TQAHJCuC9ydrIFC32oi6imsG > H+621Iv4f9zPiPta24fmoFQs2NdfAWZX6NHZpIXUULPZx5DncUsYwLRUttXUEIgg > pgMJGbdsC6X8iRJIT3CpSZcRRgpJJNIdEeiPtk2odbB2yzeL3sapCmZiJAs0iOjw > XMdKRfK9utExA8GH27Tkesiab7HR/PlHO8w2ztphLWxMmNLMEdMGSHQ4xXQM5kM= > =LgKq > -END PGP SIGNATURE- No, that's the integrated controller, which is the source of the trouble, since it also is used for keyboard and touchpad/touchscreen, so I cannot attach that to a VM. I've attached the ethernet dongle to the same port as the logitech keyboard, but it does not show up anywhere. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b0123d96-1802-491d-89d7-3c54dcc65c8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
I have revisited an earlier approach with some more success. I attached only the usb controller, not the bridges. This seems to work: sudo lspci 00:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge] 00:01.0 Network controller: Intel Corporation Wireless 7265 (rev 59) sudo lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 007: ID 046d:c51e Logitech, Inc. Bus 002 Device 006: ID 1e4e:0898 Cubeternet Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So some devices are there, like the SD card reader, audio device and the usb hubs. The usb hubs even work, the Logitec device is an external keyboard I connected. But the ethernet device is not there, nor the usb ethernet dongle that's also connected to the usb hub. Both show up on dom0 if I connect them, but since dom0 has no networking, I cannot say if they would work. I cannot see an error in dmesg either. Am I missing something? Do I need to configure something else to enable the network devices in sys-net? sudo dmesg | grep usb [0.087164] usbcore: registered new interface driver usbfs [0.087164] usbcore: registered new interface driver hub [0.087164] usbcore: registered new device driver usb [0.199812] usbcore: registered new interface driver usbserial [0.199819] usbcore: registered new interface driver usbserial_generic [0.199826] usbserial: USB Serial support registered for generic [1.218031] usbcore: registered new interface driver usbhid [1.218036] usbhid: USB HID core driver [1.899801] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.899805] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.899809] usb usb1: Product: Dummy host controller [1.899813] usb usb1: Manufacturer: Linux 4.4.14-11.pvops.qubes.x86_64 dummy_hcd [1.899817] usb usb1: SerialNumber: dummy_hcd.0 [2.517386] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [2.517394] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [2.517401] usb usb2: Product: xHCI Host Controller [2.517406] usb usb2: Manufacturer: Linux 4.4.14-11.pvops.qubes.x86_64 xhci-hcd [2.517412] usb usb2: SerialNumber: :00:00.0 [2.517988] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003 [2.517994] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [2.518018] usb usb3: Product: xHCI Host Controller [2.518024] usb usb3: Manufacturer: Linux 4.4.14-11.pvops.qubes.x86_64 xhci-hcd [2.518030] usb usb3: SerialNumber: :00:00.0 [2.870258] usb 2-1: new high-speed USB device number 2 using xhci_hcd [3.039597] usb 2-1: New USB device found, idVendor=05e3, idProduct=0610 [3.039641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.039676] usb 2-1: Product: USB2.1 Hub [3.039699] usb 2-1: Manufacturer: GenesysLogic [3.333235] usb 2-1.1: new high-speed USB device number 3 using xhci_hcd [3.458450] usb 2-1.1: New USB device found, idVendor=05e3, idProduct=0610 [3.458501] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.458545] usb 2-1.1: Product: USB2.0 Hub [3.458572] usb 2-1.1: Manufacturer: GenesysLogic [3.582241] usb 2-1.3: new low-speed USB device number 4 using xhci_hcd [3.697415] usb 2-1.3: New USB device found, idVendor=046d, idProduct=c51e [3.697467] usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.698170] usb 2-1.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [3.698255] usb 2-1.3: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes [3.702613] input: HID 046d:c51e as /devices/pci-0/pci:00/:00:00.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:046D:C51E.0001/input/input1 [3.753888] hid-generic 0003:046D:C51E.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 046d:c51e] on usb-:00:00.0-1.3/input0 [3.762024] input: HID 046d:c51e as /devices/pci-0/pci:00/:00:00.0/usb2/2-1/2-1.3/2-1.3:1.1/0003:046D:C51E.0002/input/input2 [3.814541] hid-generic 0003:046D:C51E.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HID 046d:c51e] on usb-:00:00.0-1.3/input1 [3.823050] usb 2-1.1.2: new full-speed USB device number 5 using xhci_hcd [4.128399] usb 2-1.1.2: New USB device found, idVendor=0572, idProduct=1703 [4.128445] usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.128476] usb 2-1.1.2: Product: ASUS USB Audio [4.128496] usb 2-1.1.2: Manufacturer: ASUS [4.128514] usb 2-1.1.2: SerialNumber: sudo dmesg | grep usb [0.087164] usbcore: registered new
[qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
Am Samstag, 3. Dezember 2016 16:32:37 UTC+1 schrieb Grzesiek Chodzicki: > W dniu sobota, 3 grudnia 2016 16:13:41 UTC+1 użytkownik Benjamin Richter > napisał: > > Here I attached the PCI devices of the docking station to sys-net an > > rebooted for good measure. > > As you can see, the bridges show up, but the usb controller and the usb > > devices do not, I have not Idea why. > > > > [user@sys-net ~]$ sudo lspci > > 00:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine > > Ridge 2C 2015] > > 00:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine > > Ridge 2C 2015] > > 00:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine > > Ridge 2C 2015] > > 00:03.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine > > Ridge 2C 2015] > > 00:05.0 Network controller: Intel Corporation Wireless 7265 (rev 59) > > [user@sys-net ~]$ sudo lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Qubes disables hotplugging Thunderbolt/Firewire/Express Card devices for > security reasons ergo this is not a bug it's a feature. Dunno how to disable > that. OK. But this should not prevent the device from being attached to a VM, I think. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29f4057c-9b09-46bd-ba56-4df48bffdc61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues
Here I attached the PCI devices of the docking station to sys-net an rebooted for good measure. As you can see, the bridges show up, but the usb controller and the usb devices do not, I have not Idea why. [user@sys-net ~]$ sudo lspci 00:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 00:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 00:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 00:03.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] 00:05.0 Network controller: Intel Corporation Wireless 7265 (rev 59) [user@sys-net ~]$ sudo lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3cba92f5-4bb5-483e-b605-a64f11df5639%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Asus Transformer 3 Pro T303UA, Thunderbolt issues
Hi, my earlier post seems to have gotten lost somewhere, so here again, in more detail. I've got an Asus Transformer 3 Pro and installed Qubes 3.2 on it. It works surprisingly well. Network, USB, display, touchscreen, keyboard and touchpad are working right away. It's troublesome the tablet has no Ethernet and only one USB controller, which means I cannot simply use a USB-Ethernet device. I haven't tried bluetooth yet. I've also got the Thunderbolt docking station, which contains a HDMI and VGA port, Ethernet, two USB 3 and one USB-C Ports, a SD card reader and audio ports It also charges the tablet while leaving a USB-C port available. Unfortunately, I have not been able to use the docks USB controller inside a VM. I can attach the controller, but the devices (like the integrated ethernet or external USB devices) never show up in the VM. I'll post some logs showing this later. So far the short report on the Transformer 3. Kind regards, Benjamin -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/de9707da-fc6a-49e7-8449-4d0616365185%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASUSTeK_COMPUTER_INC_-T303UA-20161203-131517.yml Description: Binary data Qubes-HCL-ASUSTeK_COMPUTER_INC_-T303UA-20161203-131517.cpio.gz Description: Binary data
