Page 2 of 2

Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 3:29 pm
by wutsinterweb
running the latter brings no result it goes back to a prompt and the cursor stops flashing.

Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 4:34 pm
by WharfRat
Alright, try the same installing VB, but run ps -eo %cpu,command,cputime,nice,%mem --sort=-%cpu|head

Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 5:20 pm
by wutsinterweb

Code: Select all

lenny@lenny:~$ ps -eo %cpu,command,cputime,nice,%mem --sort=-%cpu|head
%CPU COMMAND                         TIME  NI %MEM
14.7 /usr/lib/firefox/firefox -c 06:23:29   0  8.7
10.5 /usr/lib/firefox/firefox    04:34:55   0  9.1
 4.9 cinnamon --replace          02:08:46   0  4.4
 2.9 /usr/lib/firefox/firefox -c 01:15:51   0  4.6
 1.4 /usr/lib/xorg/Xorg -core :0 00:38:08   0  0.9
 0.3 /usr/lib/firefox/firefox -c 00:09:21   0  3.7
 0.0 /sbin/init splash           00:00:03   0  0.1
 0.0 [kthreadd]                  00:00:00   0  0.0
 0.0 [kworker/0:0H]              00:00:00 -20  0.0
lenny@lenny:~$ 

Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 5:24 pm
by wutsinterweb

Code: Select all

lenny@lenny:~$ %CPU COMMAND                         TIME  NI %MEM
bash: fg: %CPU: no such job
lenny@lenny:~$ 14.7 /usr/lib/firefox/firefox -c 06:23:29   0  8.7
14.7: command not found
lenny@lenny:~$ 10.5 /usr/lib/firefox/firefox    04:34:55   0  9.1
10.5: command not found
lenny@lenny:~$  4.9 cinnamon --replace          02:08:46   0  4.4
4.9: command not found
lenny@lenny:~$  2.9 /usr/lib/firefox/firefox -c 01:15:51   0  4.6
2.9: command not found
lenny@lenny:~$  1.4 /usr/lib/xorg/Xorg -core :0 00:38:08   0  0.9
1.4: command not found
lenny@lenny:~$  0.3 /usr/lib/firefox/firefox -c 00:09:21   0  3.7
0.3: command not found
lenny@lenny:~$  0.0 /sbin/init splash           00:00:03   0  0.1
0.0: command not found
lenny@lenny:~$  0.0 [kthreadd]                  00:00:00   0  0.0
0.0: command not found
lenny@lenny:~$  0.0 [kworker/0:0H]              00:00:00 -20  0.0
0.0: command not found
lenny@lenny:~$ lenny@lenny:~$ 
lenny@lenny:~$: command not found
lenny@lenny:~$ 
The above is when running

Code: Select all

lenny@lenny:~$ sudo dpkg --configure -a
Setting up virtualbox-dkms (5.2.10-dfsg-6) ...
Removing old virtualbox-5.2.10 DKMS files...

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.2.10
Kernel:  4.15.0-23-generic (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod...

DKMS: uninstall completed.

------------------------------
Deleting module version: 5.2.10
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-23-generic
Building initial module for 4.15.0-23-generic


Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 6:55 pm
by WharfRat
Well, I don't see any process that's stuck or possibly in an endless loop so I'm pretty much at the end of my rope with this.

You should file a bug report on this.

Re: troubles getting vbox to work dkms

Posted: Mon Jun 18, 2018 7:52 pm
by wutsinterweb
Ok, I will do so and reinstall when post beta is out and do without VB for a while. Thank you for trying so hard and for your dedication.

Re: troubles getting vbox to work dkms

Posted: Tue Jun 19, 2018 8:31 pm
by wutsinterweb
Possible important factor I've realized:

When I installed LM 19.0 I manually partitioned and chose the option to allow OS to run with secure boot enabled.

Now when I initially used the software manager to install Virtualbox it asked for my secure boot password, and I didn't have one so I entered my root password (I don't have my EFI locked down or a password set). After all that we did here I gave up and used software manager to remove VB and the additional VB products and was finally able to use the update manager to update my LM install, but when removing VB I had to give the secure boot password.

I am guessing that if I reinstall the bare metal LM 19.0 (I'll wait for post beta) I'll need to not use the secure boot option and turn it off in BIOS and see what happened after LM install to once again attempt to get VB to work with a VB windows 10 install.

Re: troubles getting vbox to work dkms [UPDATE-Solved]

Posted: Sat Jun 23, 2018 10:30 pm
by wutsinterweb
[solved this, sort of, read ahead here]

I was right to suspect that having the UEFI in my computer set to "Secure Boot" even with the install option of LM 19.0 enabled could have to do with my problem.

When I had tried to install the VB DKMS part, it would ask for the Secure Boot Password, even when I try to NOT use one, and uninstall of DKMS after an attempt or aborted attempt happened and all the rest as previously written.

I decided to see what would happen if I disabled Secure Boot in my UEFI (BIOS) and I was able to run the cleaning operations previously written in this thread and was then able to install VB 5.2 and the DKMS successfully and was immediately able to install Windows 10 AND able to re activate with my license used before my fresh Mint install here.

It seems that Microsoft's Secure Boot is still a major problem for more than just getting Mint installed, but with installing Virtual Box and a VM of Win 10.

I have to say this: Secure Boot has never done anything good for me, I hate it and I am angry at MS for foisting it on consumers, it doesn't work and it only causes headaches.

How can I tell the Devs about this?

Re: troubles getting vbox to work dkms [UPDATE-Solved]

Posted: Sun Jun 24, 2018 8:53 am
by WharfRat
I was surprised to see that you solved the problem by disabling secure boot.

Since you didn't mention the fact that you were being prompted for a secure boot password earlier it was never considered.

The best way to inform the developers is to file a bug at the link I provided earlier.

I'm sure they'll appreciate it and the fact that you also provided the solution.

Good luck :wink:

Re: troubles getting vbox to work dkms [UPDATE-Solved]

Posted: Sun Jun 24, 2018 9:10 pm
by wutsinterweb
I overlooked it because I forgot it wanted the password. Thank you for the help that fixed things once I realized.

Re: troubles getting vbox to work dkms [UPDATE-Solved]

Posted: Wed Jul 04, 2018 6:48 am
by svaens
This fixed it for me too.

When installing linux mint 19, I did NOT choose the secure boot option.
Nonetheless, with 'secure boot' 'Activated' within the BIOS, the dkms process would apparently freeze forever at the line:

Building initial module for 4.15 0 24 generic

and I was unable to get the VirtualBox install to complete; i.e., sudo /sbin/vboxconfig would fail.

After disabling 'secure boot' in the BIOS, these problems are resolved.

VirtualBox 5.2.14 r123301
Linux kernel: 4.15.0-24-generic

Re: troubles getting vbox to work dkms [UPDATE-Solved]

Posted: Mon Aug 20, 2018 9:11 am
by xenopeek
With secure boot enable you need to sign your kernel modules, which you didn't do. Apparently you're supposed to be prompted for this but the prompt isn't displayed. See upstream bug report: https://bugs.launchpad.net/ubuntu/+sour ... ug/1775672.

These are articles for Ubuntu 16.04 on how to sign your kernel modules if you want to enable secure boot (it wouldn't be "secure" boot if you could use unsigned kernel modules after all) but likely with some searching you can find guides for 18.04 (the package base for Mint 19) as well:
https://stegard.net/2016/10/virtualbox- ... untu-fail/
https://computerlinguist.org/make-dkms- ... -1604.html

If the upstream bug is fixed you would be prompted for signing your kernel modules.