SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I'll have to try to remember to try out my VM when I get home to see how it runs. I don't remember anything crazy, but I didn't use it for very long.
This probably will work,
VB versions that I have are from official download site, not testing. These (official) are not working for other users too but I red that test versions are o.k.
So I will try what you suggest.
Thank you very much.
Tried VBox versions suggested by bassmadrigal:
Host during installation reported vboxpci module missing (this is not a big deal - seen it before without any adverse effect)
However:
clients suffer from the same problem as I described above: slow console (Devuan, Slackware, windows) Funtoo not affected.
So temporary back to 5.1.30. No rush though.
thank you again for helping
Last edited by Aeterna; 11-13-2017 at 03:15 PM.
Reason: additional information
so I think what while it is good to try new kernels slackware users (because this is Slackware forum) should be aware that reporting
Quote:
running now with no problems
does not say much about potential kernel issues. I am saying this for the sake of less experienced users trying to learn more and compiling custom kernels.
To learn about kernel it is best to get original Slackware kernel sources as these are tested in more thorough fashion.
There are a new set of dependent configs with 4.4.98, based on CONFIG_NET_DSA = Y
From the 4.4.98 ChangeLog:
Code:
commit f38a3a1c8f1af4335dfdecf6e30d33750c33d1a2
Author: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Date: Mon Jan 9 16:49:26 2017 -0500
net: dsa: select NET_SWITCHDEV
[ Upstream commit 3a89eaa65db68bf53bf92dedc60084f810e1779a ]
The support for DSA Ethernet switch chips depends on TCP/IP networking,
thus explicit that HAVE_NET_DSA depends on INET.
DSA uses SWITCHDEV, thus select it instead of depending on it.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffs from my 4.4.98 vs 4.4.97 Logfile are appended below.
One is when I said 'N' to CONFIG_NET_DSA the second one is when I said 'Y' ...
Looking at the CONFIG_NET_DSA = N diffs, it appears that CONFIG_NET_DSA was 'Y' in Pat's 4.4.88 config ...
I made time this evening to install and boot the 4.4.98.kjh kernels that I built yesterday with the new CONFIG_NET_DSA config set to 'N'.
In order to avoid the forced interactive `make oldconfig` sessions in the future, I also changed my SlackBuild wrapper to use /boot/config-huge-`uname -r` and /boot/config-generic-`uname -r` instead of the Official Slackware 4.4.88 configs.
This way, when 4.4.99 is released, `make oldconfig` will at least know what to do with the CONFIG_NET_DSA config
Otherwise, my automatic kernel Package scripts would continue to stumble over CONFIG_NET_DSA and go interactive each time I build a new kernel with the Official 4.4.88 configs.
Oh yeah, VMWare Workstation and NVIDIA-Linux-x86_64-384.98.run both compiled fine on first boot and 4.4.98.kjh generic is running just fine.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Just installed the 4.14.0 kernel and as mentioned above, there is a problem with VirtualBox. The VB manager comes up, but it won't run the "virtual machine."
The error is,
Quote:
[BKernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/sbin/vboxconfig'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. [/B]
However, it was installed, so I downloaded the latest version, 5.20, and while it installed it behaved as above and there is an error in the install log as follows,
Quote:
VirtualBox 5.2.0 r118431 installer, built 2017-10-18T06:14:42Z.
Testing system setup...
Installing VirtualBox to /opt/VirtualBox
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.14.0/build SUBDIRS=/tmp/vbox.0
SRCROOT=/tmp/vbox.0 -j8 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing."
;\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
and so on.......
I think I'll go back to the 4.13.13 kernel until the dust settles.
Last edited by cwizardone; 11-17-2017 at 12:32 PM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by cwizardone
Just installed the 4.14.0 kernel and as mentioned above, there is a problem with VirtualBox. The VB manager comes up, but it won't run the "virtual machine."
The error is,
However, it was installed, so I downloaded the latest version, 5.20, and while it installed it behaved as above and there is an error in the install log as follows,
and so on.......
I think I'll go back to the 4.13.13 kernel until the dust settles.
you may try two options suggested here:
1) VirtualBox-5.2.1-119001-Linux_amd64.run and Oracle_VM_VirtualBox_Extension_Pack-5.2.1-118994.vbox-extpack
this option was suggested by bassmadrigal https://www.linuxquestions.org/quest...ml#post5780239
while VirtualBox-5.2.1 installed without issues on 4.14, the only working module was vboxdrv.
Clients worked, but I had issues with slow konsole (GUI had no issues)
this works finally, the only error that I have seen is failure of vboxpci module compilation, but it has no effect on the VM clients
clients tested:
Funtoo current - VBoxGuestAdditions 5.1.26 (provided by Funtoo repositories), Funtoo custom kernel 4.13.12
Devuan CERES- VBoxGuestAdditions 5.2.0 (provided by Devuan repositories), Devuan custom kernel 4.13.12
Slackware -current - VBoxGuestAdditions_5.2.1-118995 (Oracle), Slackware custom kernel 4.14.0
FreBSD current - VBoxGuest OSE 5.1.28 (provided by FreeBSD repositories), FreeBSD custom kernel
Windows 8.1 - VBoxGuestAdditions_5.1.31-119015.iso (Oracle)
OpenIndiana Hipster current VBoxGuestAdditions_5.1.30 (OpenIndiana repositories)
So VBoxGuestAddditions version does not matter.
Host Slackware-current running custom kernel 4.14.0
(...4.14.0-x86_64-2.txz).
The hard work is most certainly appreciated,
but it didn't fix any of the problems I experienced with the first release. Back to version 4.13.13, for now.
Last edited by cwizardone; 11-19-2017 at 12:22 AM.
Just installed the 4.14.0 kernel and as mentioned above, there is a problem with VirtualBox. The VB manager comes up, but it won't run the "virtual machine."
The error is,
However, it was installed, so I downloaded the latest version, 5.20, and while it installed it behaved as above and there is an error in the install log as follows,
and so on.......
I think I'll go back to the 4.13.13 kernel until the dust settles.
See my patch here for VBox 5.2.0 with Linux Kernel 4.14.0
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Thanks Willysr and bassplayer69!
I've also had problems as mentioned by bm Tazza, https://www.linuxquestions.org/quest...el-4175617787/
in post #25.
In his case it was KDE, in mine it was Xfce.
After the last batch of upgrades Xfce wouldn't fire up any programs or access the system settings.
Well.... NetworkManager and its applet worked and the Whisker Menu would allow me to logout, but not start any applications. I found out that if I simply logged out of Xfce and then logged back in, the problem disappeared.
I could also log out of Xfce and go into KDE where everything was fine.
When I went back to the 4.13.13 kernel the problem followed, so I deleted my Xfce configuration files and started over and from thereon Xfce worked fine........
UNTIL, I installed the latest 4.14.0 kernel upgrade released last evening and then the problem returned... so it was back to 4.13.13.
Last edited by cwizardone; 11-19-2017 at 09:45 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
