In the USB settings, USB controller is hard-enabled, I can’t untick it.
And it is set to USB 1.1
I cannot select USB 2 or USB 3.
It seems that this happened when I updated the Extension Pack to 6.1.36-1
VB version VirtualBox Graphical User Interface Version 6.1.34 r150636.
~ inxi -F ✔ 9s
Host: shmuel-manjaro Kernel: 5.18.12-3-MANJARO arch: x86_64 bits: 64
Desktop: GNOME v: 42.3.1 Distro: Manjaro Linux
Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 1203
Info: 8-core model: Intel Core i7-9700 bits: 64 type: MCP cache: L2: 2 MiB
Speed (MHz): avg: 4500 min/max: 800/4700 cores: 1: 4467 2: 4490 3: 4492
4: 4490 5: 4432 6: 4495 7: 4559 8: 4575
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] driver: i915 v: kernel
Device-2: Microdia USB Live camera type: USB
Display: wayland server: X.Org v: 22.1.3 with: Xwayland v: 22.1.3
compositor: gnome-shell driver: X: loaded: modesetting gpu: i915
resolution: 1: 1920x1080~120Hz 2: 1600x900~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
v: 4.6 Mesa 22.1.3
Device-1: Intel 200 Series PCH HD Audio driver: snd_hda_intel
Device-2: Microdia USB Live camera type: USB
Sound Server-1: ALSA v: k5.18.12-3-MANJARO running: yes
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 0.3.56 running: yes
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: a8:5e:45:e2:87:3c
Device-2: Realtek 802.11ac NIC type: USB driver: N/A
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
Report: rfkill ID: hci0 state: up address: see --recommends
Local Storage: total: 2.26 TiB used: 787.52 GiB (34.1%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB
ID-2: /dev/sdb vendor: Toshiba model: HDWD120 size: 1.82 TiB
ID-1: / size: 249.62 GiB used: 110.31 GiB (44.2%) fs: ext4 dev: /dev/sda4
ID-2: /boot/efi size: 96 MiB used: 37.8 MiB (39.3%) fs: vfat
Alert: No swap data was found.
System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 318 Uptime: 3h 37m Memory: 15.49 GiB used: 10.58 GiB (68.3%)
Shell: Zsh inxi: 3.3.19
The versions need to match. Downgrade the extension pack until VB is updated.
Will do. I was prompted by pamac to make the upgrade. I guess AUR, which supplies the extension pack, got ahead of the Manjaro version.
The AUR, as the name suggests, targets Arch and will therefore be ahead of most Manjaro branches (with the possible exception of unstable but there will still be a delay).
So now I have a little problem: AUR offers only Extension Pack 6.1.36-1
or the dev version
I removed Extension Pack 6.1.36-1
with plans to install Extension Pack to 6.1.34
but I don’t see how to do that now…
At least I can enable USB 1 like this. Before the upgrade, I needed to disable USB altogether, or the guest would abort.
Have a look in
/var/tmp/pamac-build-$user/, the previous version may still be there.
Download the extension pack always from virtualbox page, for the virtualbox version you have installed from official repositories
Oracle_VM_VirtualBox_Extension_Pack-6.1.34.vbox-extpack can be downloaded from there too, and install it manually.
A good reason to avoid automated rebuild of custom packages - you know - AUR right?
yes, it was AUR. So what’s the recommended way to keep my AUR packages updated? I do want the updates for Chrome browser, Zoom, and maybe others.
If you have aur enabled in pamac and check for updates it works very well.
Right, and that’s what I have. But in this particular case, it offered me an incompatible upgrade.
Maybe I should just install the AUR version of VirtualBox. What is the downside of that? I assume it is backwards compatible with whatever kernel Manjaro stable is on?
EDIT: I just told pamac to check for updates, and it seems that all is well, since I installed the extension pack the @bogdancovaciu way. I am not offered an update for it from AUR, which is good. But I will probably need to upgrade it manually, as needed.
I have a couple of installed AUR packages myself, and some get updated without having other pending updates, and other need to be updated after a big system update, but the virtualbox extension pack is a special case, and downloading it from virtualbox page was the best practice for me.
In principle there should be no problem to do the
as you did so far.
It upgraded the Extension Pack to 6.1.36-1 which was the latest.The extension is an add on for virtualbox which the latest version is not in the repo yet but will be soon.Pamac did what it was supposed to do it updated.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.