B1naryc0de's Posts

Patch first, then install driver, then install the linux agent. Exactly like this: cd /tmp tar zxvf VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374.tar.gz apt-get install make gcc libelf-dev download the 1.15 zip https://sourceforge.net/projects/usb-vhci/files/linux%20kernel%20module/ tar xzvf vhci-hcd-1.15.tar.gz cd vhci-hcd-1.15 patch -p1 < /tmp/VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374/resources/vhci/patch/vhci.patch make clean && make && make install cd /tmp/VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374 ./install_viewagent.sh -A yes -U yes

This is what I see in my logs, weird resets? My network connection is stable and using TCP.   usb 4-1: new SuperSpeed Gen 1 USB device number 2 using usb_vhci_hcd usb 4-1: New USB device found, idVendor=090c, idProduct=4223, bcdDevice=1.00 usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-1: Product: USB usb 4-1: Manufacturer: Verbatim usb 4-1: SerialNumber: 0703765D943GV45456 usb-storage 4-1:1.0: USB Mass Storage device detected scsi host33: usb-storage 4-1:1.0 mtp-probe: checking bus 4, device 2: "/sys/devices/platform/usb_vhci_hcd.0/usb4/4-1" mtp-probe: bus: 4, device: 2 was not an MTP device Then I get another mtp-probe: checking bus 4, device 2: "/sys/devices/platform/usb_vhci_hcd.0/usb4/4-1" mtp-probe: bus: 4, device: 2 was not an MTP device and finally a bunch of resets usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using usb_vhci_hcd usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using usb_vhci_hcd usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using usb_vhci_hcd usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using usb_vhci_hcd

These are the steps i've done to install the driver: cd /tmp tar zxvf VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374.tar.gz apt-get install make gcc libelf-dev download the 1.15 zip https://sourceforge.net/projects/usb-vhci/files/linux%20kernel%20module/ tar xzvf vhci-hcd-1.15.tar.gz cd vhci-hcd-1.15 patch -p1 < /tmp/VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374/resources/vhci/patch/vhci.patch make clean && make && make install cd /tmp/VMware-horizonagent-linux-x86_64-2111.1-8.4.0-19155374 ./install_viewagent.sh -A yes -U yes reboot if I issue a lsmod | grep vhci I don't see the driver, but if I do a modprobe usb_vhci_hcd and perform lsmod | grep vhci again, I can see it's loaded. I'll plug in a USB key at this point on the thin client but nothing ever shows up. I can see the key is detected by the OS with lsusb but no USB key ever shows up. I can't even mount it because it's not showing up as a /dev/sdb device. Thanks for helping!

If I type modprobe usb_vhci_hdi and then type lsmod | grep vhci I do see it, but same results. No USB key shows up and I can mount it either because it's not seen by lsblk. I've also tried formating the key in fat16, fat32 and also NTFS. Still, no keys shows up. Any clue?   Thanks!

I haven't tried using DKMS but even when installing the agent following these instructions:      apt-get install make apt-get install gcc apt-get install libelf-dev Compile and install the VHCI drivers. tar -xzvf vhci-hcd-1.15.tar.gz cd vhci-hcd-1.15 patch -p1 < full-path_to_patch-file make clean && make && make install​   The USB device is seen when typing   lsusb   but never gets mounted. At first I thought it was because it was being patched using an old kernel module I had so I ran   apt autoremove   and rebooted but that didn't fix it. I made a post as well about this and I simply can't find what's wrong. There's also logs in /tmp/vmware-root but they aren't really providing any good info, or I might not be understanding them