Hello,
I have selected to ignore two USB devices on my Raspi with the Windows client.
Now I would like "un-ignore" them. What is the correct way of doing so?
I have stopped the daemon and manually edited the file /root/config.ini and removed everything from the option "IgnoredDevices".
Strange: the option "IgnoredDevices" only shows one ignored device and not both devices. However, the second missing device is also not listed anymore. It is completely gone from VH-client. I have not tried to reboot yet.
Any idea what's going wrong here?
The now completely missing USB device is a Huawei 3G modem, a USB composite device.
However, it is still working normally as 3G modem on the Raspi.
Cheers,
Christian
Yes there is no way in the
Yes there is no way in the GUI at the moment to unignore devices. To do this edit the c:\Users\your username\AppData\Roaming\vhui.ini and remove the IgnoredDevices entry in there (under windows) and under osx , /Users/your username/Library/Preferences/vhui Preferences.
Update:
Update:
I have rebooted the Raspi and the desktop PC several times with cleaned option "IgnoredDevices".
No chance. The 3G modem is gone from VH client. However, it is working properly on the Raspi.
Also the other USB device which was the only listed ignored device does not show up with the proper name anymore.
It only shows the PID as the name.
So, there seems to be a bug somewhere in VH.
What I do not understand is why a reboot does not help?
Are there any other files that VH uses to store meta data on the server?
Or is it the VH client in Windows which stores additional info in the registry?
Ok, thanks. That was the
Ok, thanks. That was the missing link: c:\Users\your username\AppData\Roaming\vhui.ini
The only thing left is the USB device which only shows
0xec00
as device name in the vh client.root@raspbx:~# lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 2101:8500 ActionStar
Bus 001 Device 005: ID 2101:8501 ActionStar
Bus 001 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
Details
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0xec00
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
I have just learned that 0424
I have just learned that 0424:ec00 is the USB fast ethernet adapter which is included in the USB hub chip.
(SMSC9512/9514 Fast Ethernet Adapter)
This device enumerates as
This device enumerates as being vendor specific.
Any chance the VH server/client shows this as the Rasp USB ethernet adapter properly?
Yes it's the pi Ethernet chip
Yes it's the pi Ethernet chip ,the reason it shows a code and not a name is because the device does not contain a USB string descriptor for the name of the device. Linux figures out its name from USB.ids file. I don't use that file because it has confusing entries for some devices, particularly USB drives.
By-the-way don't share the Ethernet adapter via virtualhere otherwise you will lose you network connection until the pi is hard reset, hence that is why it is ignored by default