Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to install virtualbox-5.1.12 in Slackware 14.1 & subsequently 14.2, I find it won't load vboxdrv.ko or vboxguest.ko, although it builds them. I've tried with a git of linux-stable-3.19.0-rc6, & slackware's (= Linus') sources version 4.4.14, & 4.4.38. When I check stuff, it looks ropey
Code:
bash-4.3# modprobe vboxdrv.ko
modprobe: FATAL: Module vboxdrv.ko not found in directory /lib/modules/4.4.38
bash-4.3# modprobe vboxguest.ko
modprobe: FATAL: Module vboxguest.ko not found in directory /lib/modules/4.4.38
bash-4.3# ls -lh /lib/modules/4.4.38/misc
total 1.1M
-rw-r--r-- 1 root root 477K Jan 17 16:14 vboxdrv.ko
-rw-r--r-- 1 root root 352K Jan 17 16:13 vboxguest.ko
-rw-r--r-- 1 root root 13K Jan 17 16:14 vboxnetadp.ko
-rw-r--r-- 1 root root 33K Jan 17 16:14 vboxnetflt.ko
-rw-r--r-- 1 root root 30K Jan 17 16:14 vboxpci.ko
-rw-r--r-- 1 root root 57K Jan 17 16:13 vboxsf.ko
-rw-r--r-- 1 root root 62K Jan 17 16:13 vboxvideo.ko
bash-4.3# depmod -eF /boot/System.map-4.4.38
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_mmap
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_global_release
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_pool_unpopulate
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_manager_func
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_global_init
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_device_release
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_kunmap
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_del_sub_from_lru
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_device_init
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_init_mm
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_dma_acc_size
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_tt_init
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_kmap
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_add_to_lru
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_unref
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_mem_global_release
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_mem_global_init
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_init
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_validate
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_bo_move_memcpy
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_tt_fini
depmod: WARNING: /lib/modules/4.4.38/misc/vboxvideo.ko needs unknown symbol ttm_pool_populate
depmod: WARNING: /lib/modules/4.4.38/misc/vboxdrv.ko needs unknown symbol preempt_notifier_inc
depmod: WARNING: /lib/modules/4.4.38/misc/vboxdrv.ko needs unknown symbol preempt_notifier_register
depmod: WARNING: /lib/modules/4.4.38/misc/vboxdrv.ko needs unknown symbol preempt_notifier_dec
depmod: WARNING: /lib/modules/4.4.38/misc/vboxdrv.ko needs unknown symbol preempt_notifier_unregister
All those symbols appear in the kernel source, but not in system includes or libs that I can find The errors vary from kernel to kernel, but they're generically the same (Missing symbols in the kernel source, but not in system includes or libs). I have verified the download, reinstalled virtualbox, and moved kernels but still no joy. Building the checking targets isn't encouraging. Sanity check (make headers_check) was ok; 'make headersdep' produced recursive inclusion errors
1139 errors linux/mmzone.h:735 (which I will spare you)
192 errors from linux/mm.h:904 (ditto)
And excluding those from the output left these
grep -ve'735' -e '904' /usr/src/linux-4.4.38/headers <--an error output file
from net/caif/caif_device.h:13 <-- here
from net/caif/caif_device.h:13 <-- here
from net/caif/caif_device.h:13 <-- here
from net/caif/caif_device.h:13 <-- here
from net/nfc/nfc.h:25 <-- here
from net/nfc/nfc.h:25 <-- here
from net/nfc/nfc.h:25 <-- here
from net/nfc/nfc.h:25 <-- here
from linux/backlight.h:12 <-- here
from linux/mfd/wm8400-audio.h:24 <-- here
from linux/memory_hotplug.h:4 <-- here
Is this kosher? Commenting those lines (in mmzone.h & mm.h) simply sprung errors in other header files. Does it matter? Any thoughts on |Virtualbox?
I recently installed VBox 5.1.12 on Slack 14.2 and didn't have these warnings.
After I used the wget cmd to download it to my home directory I made the .run executable and than as root it runs and fully installs.
Maybe the new 5.1.14 will have what your kernel needs?
Something is evidently missing and the fact that you have tried various kernels and still get pretty much the same/similar errors I think that implies that something is missing.
I looked in the VBox Forum and found 2 threads with similar errors. Maybe they will help you to understand what the problem is. (I hope so)
Thanks for the reply, Ztcoracat. (/thinks: How does somebody PRONOUNCE 'Ztcoracat'?)
Quote:
Originally Posted by Ztcoracat
Something is evidently missing and the fact that you have tried various kernels and still get pretty much the same/similar errors I think that implies that something is missing.
I agree, but I'm unable to find what that something is. The fact that it still manages to puke on the 4.4.14 huge kernel with everything compiled in is disconcerting.
At this stage, I've had this problem on 14.1 & 14.2. This Virtualbox business was a factor in the upgrade. I've tried
* Kernels 3.14.18, 3.19.0-rc6, 4.4.14, & 4.4.38. My own config on the last 3 & slackware's huge 3.14.18, and 4.4.14.
* VirtualBox 5.0.8 & 5.1.12 with matching guest additions & extension pack (Reinstalled just in case).
I'm coming round to thinking maybe it's hardware, or some missing package which I never install. But it seems to be screwing up in the kernel source. It's difficult to think of anything relevant that hasn't been reinstalled. The hardware is
Code:
bash-4.3# lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 IDE interface: Intel Corporation 7 Series Chipset Family 4-port SATA Controller [IDE mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation 7 Series Chipset Family 2-port SATA Controller [IDE mode] (rev 04)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
From memory, that is an i3 CPU with HD4000 GPU & Panther Point chipset. Health reverses never improve memory, though, and I've had one.
On the other links you posted, I did have the symlinks in /boot pointing to 4.4.14, but they're gone now. I don't think ahci is an issue, because it's compiled into the huge kernel, and into mine.
is to a file on my Google drive which is the output of
Code:
ls -1 /var/log/packages > RoseViolet.pkgs
The -1(= number one) gives a single column output. Could you please do the same for your box, download my file, and post the output of
Code:
diff -u RoseViolet.pkgs [your_file] > diff.txt
That will tell me if you have things installed that I haven't, and I can stick some in and see if I can get to the bottom of this mess? I try to keep from installing crap I don't need/use/want like KDE and xf86-video-everything.
You're Welcome.
You pronounce my name like: ze- tee- cora- cat:-
I downloaded your file RoseViolet.pkgs and it's in my Downloads directory.
Quote:
Could you please do the same for your box, download my file, and post the output of
Sure but I'll need your help.
I don't have anything on Google drive. And I'm not sure where my file would be that I could compare to yours. Do you mean all of the packages that are in my /var/log/packages?
bash-4.3# /etc.rc.d/init.d/vboxdrv setup
bash: /etc.rc.d/init.d/vboxdrv: No such file or directory
bash-4.3# /etc/rc.d/init.d/vboxdrv setup
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
This dmesg led me on an interesting chase. If you make a later version of the kernel in the source (as I had, but wpa_supplicant misbehaved) then the version magic is wrong and you need a ‘make distclean’ to restore it. Make clean isn’t enough. In short, your source has to match the running kernel version
Done this way, vboxdrv builds ok without error, which is progress. The Guest additions still crap out on vboxguest, and that needs looking into.
Finally sorted after a fashion.
I removed everything virtualbox I could find including the VMs and started over with 5.1.12. I got that going, although I had to remake the running kernel in the source after a 'make distclean' and copy over the System.map, as the new one had some symbols the original didn't and virtualbox modules puked for the lack of them.
I am thoroughly sick to the teeth of this, and will struggle with guest additions when I recover sufficiently.
There may have been stray stuff from old versions lying around but I don't really understand the refusal to work, or the thing working now
Sorry to hear you had to jump through so many hoops to get it working.
I'm thinking that it should not be that difficult to be able to have and run VBox.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.