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.
Yes. These things will get resolved. 5.9 had almost exactly the same issues with intel integrated gpu I suffered through for a while. Random frustrating freezes with no discernible logs
Slackware 14.2. Upgraded to 4.19.163 from stock kernel 4.4.240 today and wished I had done it sooner. The 4.19 kernel resolves the issue I have been facing with the fans not working correctly on my Acer Predator 17 with the addition of the driver module ath10k_hwmon-pci-0600. However, it now breaks virtualbox-5.0.40 off of SBo since the kernel module no longer compiles. I have read through and tried all of the resolution proposals on this site which are primarily centered around using a version 6.x of virtualbox with the 5.x kernel with no success. I also found online that virtualbox version 5.2.20 started supporting the 4.19 kernel series. My questions as follows:
* Is anyone on this board using the 4.19.x kernels with virtualbox and having success?
* If so, what did you do?
* Are you using a SlackBuild script, compiling straight, or using a pre-compiled version from www.virtualbox.org?
I am trying to stay with SlackBuild scripts as much as possible to keep the install/upgrade process as clean. Thanks for any assistance.
This is from memory but I could have sworn I fixed the i915 driver not initializing at boot with CONFIG_DRM_I915=y
Likely false but it's worth a try if you're having that issue and can recompile your kernel. And/or I guess you could add it into your initrd
EDIT: Actually maybe it was CONFIG_FB_INTEL which needed to be set and is not configured at all in HUGE kernel
This is from memory but I could have sworn I fixed the i915 driver not initializing at boot with CONFIG_DRM_I915=y
Likely false but it's worth a try if you're having that issue and can recompile your kernel. And/or I guess you could add it into your initrd
EDIT: Actually maybe it was CONFIG_FB_INTEL which needed to be set and is not configured at all in HUGE kernel
I'm using i915 kernel driver, but I didn't mention that, so maybe you were responding to someone else. Anyway, I've also always used the generic kernel and an initrd, I've never booted the huge kernel except during a full install. Hope I don't have to compile a kernel to revert to a previous one. I've done it before, but would rather not have to.
Ya z038 there are multiple issues with different drivers. I'm responding to those who boot into init 3 but the screen blanks out before they get a login prompt though they can still SSH into the box.
I have heard there is a Slackware mirror in United Kingdom which keeps copies of all the old versions of every package. In a recent thread someone mentioned this mirror, but I do not remember the thread nor the URL of the mirror.
I Don't know if this will help finding out why the 5.10 is locking up,
slackware64-current installed on vbox, running 5.10.4 kernel, attempting to compile 5.10.4 kernel locks up with
Code:
make modules_install
is run. It locks up vbox to the point where it won't release the touchpad or keyboard. The only key combo I can get to work is alt-ctrl-f1 to a console and reboot to get out of it. re-installed 5.4.84 kernel no lock up. A hard metal install on this laptop hasn't locked up yet with the 5.10 kernel
Host: Xbuntu 20.04.1 LTS
guest: slackware64-current with latest updates
system: HP laptop core i3 intel graphics
edit: The vboxvga graphics controller was causing the crash. When I changed to vmsvga no crashes. I wonder why the 5.10 crashes with the vboxvga and the 5.4.84 doesn't.
Last edited by colorpurple21859; 01-03-2021 at 09:40 PM.
5.10.4 running smoothly here on laptop and desktop (all Intel).
FWIW, have built and run 5.10.x starting with the RC's without any issues.
May have jinxed it and got my first lockup on resume from suspend to RAM (blank screen, pc unreachable via ssh),
it was just a matter of time I guess.
Rolling back to 5.10.3 which had run for 5 days with no issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.