VBox - USB device not recognised  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
chippy52
Posts: 62
Joined: Wed Jul 29, 2009 6:05 pm

VBox - USB device not recognised

#1 Post by chippy52 »

Code: Select all

System:    Kernel: 6.1.0-10mx-ahs2-amd64 [6.1.38-2~mx21ahs] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10mx-ahs2-amd64 root=UUID=<filter> ro quiet 
           splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: <filter> 
           UEFI-[Legacy]: American Megatrends v: 5603 date: 07/28/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ family: 17 (23) 
           model-id: 8 stepping: 2 microcode: 800820D cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102197 
           Speed: 1374 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1374 
           2: 1550 3: 1550 4: 1550 5: 1610 6: 1550 7: 1550 8: 1550 9: 1550 10: 1550 11: 1550 
           12: 1550 13: 2764 14: 1550 15: 1550 16: 1550 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT vulnerable 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: ASUSTeK driver: nvidia v: 525.116.04 
           bus-ID: 09:00.0 chip-ID: 10de:1c81 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x292mm (20.6x11.5") 
           s-diag: 600mm (23.6") 
           Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
           diag: 598mm (23.5") 
           OpenGL: renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2 v: 4.6.0 NVIDIA 525.116.04 
           direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus-ID: 09:00.1 chip-ID: 10de:0fb9 class-ID: 0403 
           Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 0b:00.3 chip-ID: 1022:1457 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-10mx-ahs2-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus-ID: 07:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 465.53 GiB (39.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP size: 238.47 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 32B2T6TA temp: 30.9 C scheme: MBR 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: CC43 scheme: GPT 
Partition: ID-1: / raw-size: 215.96 GiB size: 211.51 GiB (97.94%) used: 11.86 GiB (5.6%) fs: ext4 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-2: /home raw-size: 14.65 GiB size: 14.32 GiB (97.74%) used: 2.6 GiB (18.2%) fs: ext4 
           dev: /dev/nvme0n1p3 maj-min: 259:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.86 GiB used: 24.8 MiB (0.3%) priority: -2 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2502 lib: 1414 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mx.debian.nz/mx/repo/ bullseye main non-free
           2: deb http://mx.debian.nz/mx/repo/ bullseye ahs
Info:      Processes: 310 Uptime: 53m wakeups: 1 Memory: 7.68 GiB used: 5.09 GiB (66.2%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
Virtualbox was updated recently to 7.0.10. Now my W7 guest no longer sees my printer. On boot up a warning message appears, clicking on the message the attached screen comes up
USB.PNG
I have booted into the printer install media but the printer is not visible. Any advice as to what course of action I should take. ( IE reinstall earlier version )
You do not have the required permissions to view the files attached to this post.
MX-KDE-18.9_x64 KDE
AMD Ryzen7 2700, 8GB DDR4, nVidia GeForce GTX 1050, Samsung nvme2.0 SSD 950 evo 250GB, Seagate 1TB

User avatar
FullScale4Me
Posts: 1089
Joined: Fri Jan 08, 2021 11:30 pm

Re: VBox - USB device not recognised

#2 Post by FullScale4Me »

For USB drives to show up as a choice in VB they have to be unmounted on the host PC.
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

User avatar
Stevo
Developer
Posts: 14614
Joined: Fri Dec 15, 2006 7:07 pm

Re: VBox - USB device not recognised

#3 Post by Stevo »

Is the matching virtualbox-ext-pack package installed?
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

User avatar
FullScale4Me
Posts: 1089
Joined: Fri Jan 08, 2021 11:30 pm

Re: VBox - USB device not recognised

#4 Post by FullScale4Me »

I was able to duplicate *part* of your issue. I did three things to restore USB:
  • Reinstalled Guest Additions.
  • In the Guest settings I selected USB 2 instead of USB 3.
  • I rebooted the host.
After this visibility of all USB devices resumed. USB thumb drives, USB 3 SATA drive enclosures and my webcam. I've heard whispers of USB 3.0 emulation not being solid. Don't ask for a URL, I have none.
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

User avatar
chippy52
Posts: 62
Joined: Wed Jul 29, 2009 6:05 pm

Re: VBox - USB device not recognised  [Solved]

#5 Post by chippy52 »

Thanks for the response. This is printer specific as all other USB devices work fine.
The extension pack matches as per log file clip
VBox log.png
After hours of reading I found a link on the Oracle site for USB 3 host controller drivers for W7 which work around this issue. The USB 1 & 2 controllers don't work.
You do not have the required permissions to view the files attached to this post.
MX-KDE-18.9_x64 KDE
AMD Ryzen7 2700, 8GB DDR4, nVidia GeForce GTX 1050, Samsung nvme2.0 SSD 950 evo 250GB, Seagate 1TB

User avatar
l0dr3
Posts: 463
Joined: Wed Jun 28, 2023 11:06 am

Re: VBox - USB device not recognised

#6 Post by l0dr3 »

chippy52 wrote: Wed Aug 09, 2023 9:58 pm After hours of reading I found a link on the Oracle site for USB 3 host controller drivers for W7 which work around this issue.
Hi, @chippy52

Plz answer me the question:

Does this now work in VBox v7.xx scenarios with the LATEST official Intel USB3 drivers from

https://www.intel.com/content/www/us/en ... amily.html

or do we still have to use the older ones from

https://web.archive.org/web/20190109222 ... uct=65855

?

for back-ref of the problem and the solutions so far:
https://unix.stackexchange.com/question ... -0-devices
https://us.informatiweb.net/tutorials/i ... ows-7.html

kind regards

l0dr3

User avatar
chippy52
Posts: 62
Joined: Wed Jul 29, 2009 6:05 pm

Re: VBox - USB device not recognised

#7 Post by chippy52 »

I used the archives.org download.
MX-KDE-18.9_x64 KDE
AMD Ryzen7 2700, 8GB DDR4, nVidia GeForce GTX 1050, Samsung nvme2.0 SSD 950 evo 250GB, Seagate 1TB

User avatar
l0dr3
Posts: 463
Joined: Wed Jun 28, 2023 11:06 am

Re: VBox - USB device not recognised

#8 Post by l0dr3 »

chippy52 wrote: Thu Aug 10, 2023 3:12 pm I used the archives.org download.
Thx! for confirming that to me - so no substantial change since ~2019, with VBox v5.2 and v6.x.x branches.

kind regards

l0dr3

Post Reply

Return to “MX KDE Official Release”