Hello All,
As for what concerns the blocking point for iasl I solved installing the acpica package via slapt-get. Now the package is being compiled. I will report here about any further showstoppers.
Headed to the two Slackbuilds. Virtualbox-kernel package built correctly, whereas virtualbox package stopped during the making. Here's the output: Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK. Checking for kBuild: found, OK ...
Wiped completely previous installation and run the installer once again, but unfortunately the problem remains. I am wondering if this can be related to the fact that the installer I am using is too old for the kernel running on 15.0 (VirtualBox-6.0.14-133895-Linux_amd64). I will try ...
As usual, you got it right! It was just a matter of changing the setting of CPU operation into the BIOS and now the VM runs flawlessly. Even the 64 bit systems now appear on the drill down list of VM options.
Thanks a bunch, that made my day
Regards,
Antonio
Hello All, As the title says I have Virtualbox 6.0.14 installed on Salix 14.2 64 bit. The laptop I am using has 4 x Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz and 4 Gigs of RAM, so it should be sufficient enough to host distros which don't have particular hardware requirements. The weird thing is ...
That's correct.I retrieved the .usb firmware file long ago from http://www.meier-geinitz.de/sane/gt68xx-backend/ : this has served me well for years since the manufacturer dropped driver support for windows back to the xp days (actually that was one of the reasons that made me ...