After a kernel upgrade, Virtualbox instructs you to run “/etc/init.d/vboxdrv setup” as root. When you try this on Arch, you get an error message, however:
bash: /etc/init.d/vboxdrv: No such file or directory
Turns out that on Arch, there’s a different path to follow. As root, do:
/usr/bin/vbox_build_module
Followed by:
modprobe -r vboxdrv
And you should be set! Still, if you’re not, please don’t hold me responsible. Everything you do as root is your own responsibility!
Had an error message when opening KMyMoney in opensuse:
kmymoney: symbol lookup error: kmymoney: undefined symbol: _ZN14KMyMoneyPlugin14ImporterPlugin16staticMetaObjectEv
Solution: updating KMyMoney!
Something I miss in comparison with Arch, or even Ubuntu: the constant (rolling) updating of your total system. I know selecting all possible updates is possible somehow in Yast, but still…
At work, I sometimes need Windows for legacy programs, or for not messing up the layout of protected Word documents. For all these little things, VirtualBox (non OSE for me) works like a charm. Since my switch from Ubuntu to openSUSE, however, I was unable to use the virtual windows disk (vdi file) I created under Ubuntu: right after booting up Windows, I would get a glimpse of a BSOD (blue screen), and Windows would reboot (not even leaving me time to study the BSOD). Booting into safe mode wouldn’t help.
Not wanting to create yet another virtual disk, I set out on an epic quest: a veritable search-and-destroy-the-cause mission. What finally fixed the whole thing, was setting the IDE Controller Type (Settings – General – Advanced) to PIX3 instead of PIX4. Apparently, the default setings are different between different distro’s.