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.
In the latest kernel 5.4 there may be a configuration conflict, it's for NVIDIA graphics cards,
nvidia_fb and nouveau driver are both enabled.
It does work, but there is a problem with the sensors then,
lm_sensors do not read the GPU temperature. Only when nvidia_fb is turned off, the sensors works completely again.
That is so in my comp. at least.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
Quote:
Originally Posted by pamu1
In the latest kernel 5.4 there may be a configuration conflict, it's for NVIDIA graphics cards,
nvidia_fb and nouveau driver are both enabled.
It does work, but there is a problem with the sensors then,
lm_sensors do not read the GPU temperature. Only when nvidia_fb is turned off, the sensors works completely again.
That is so in my comp. at least.
greetings
Working fine on this box with a Nvidia card and the recent Nvidia long term driver.
Working fine on this box with a Nvidia card and the recent Nvidia long term driver.
It is probably only when used with the open-source nouveau driver. I imagine the blob provides it's own temperature sensor interface and doesn't rely on the kernel nvidia drivers.
i915 0000:00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
I found an arch thread that mentions 5.5-rc2 has the fixes so there's hope. https://bbs.archlinux.org/viewtopic.php?id=250765&p=3
I'm wondering if mainlain really does go into stable? Will fixes in 5.5 flow back into 5.4?
@tramtrist - Sorry to take so long but I had read about the fixes in an extremely active #linux newsfeed on Diaspora and I'm a bit new to it. Finally found it -
I don't know if that helps. I just brought it up because I see so many posts of people with integrated graphics, especially 1915, having difficulties. I always prefer a real graphics card. Even on laptops I'd much rather have an upgradeable chip slot. It seems to me vision is just too high a percentage of perception to skimp or be locked in there but then I'm also have a fairly large monitor and watch a lot of HD videos and game, so I empathize with those who don't need all that. I'd be willing to bet with the numbers I see of such difficulties that it is likely such fixes in Mainline will make there way back to Stable, even if the above linked page is currently of no solid help.
Best wishes for all affected and Happy Holidays all.
No problem at all! Thanks for looking into it. They have to fix the i915.. there's simply too many people with that use case
My next laptop will be AMD integrated graphics most likely.. Maybe an x395 with ryzen? Not sure .. If there was a ~12 inch form factor PC with lenovo style build that had removable graphics card... I'd be ALL over that
I have a bit of news for this thread. apparently the 5.4.6 kernel gives my msi ge62 6qd apache pro laptop problems with prime sync (said laptop has nvidia gtx960m gpu) whereas i have no such problems with the 4.19.86 series kernel. My xorg.conf as well as my modprobe.d configuration file (options nvidia_drm modeset=1) are also correct as far as i can see. I noticed horizontal tearing after upgrading to the newer kernel and setting it up for prime sync (cat /sys/module/nvidia_drm/parameters/modeset yielded an "N" as opposed to a "Y" no matter what i seemed to do). The only way i was able to get properly working prime sync was to downgrade back to 4.19.86. And yes i am using proprietary nvidia drivers.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
The 5.4.6 kernel has been rebuilt:
Quote:
Fri Dec 27 22:54:53 UTC 2019
a/kernel-generic-5.4.6-x86_64-2.txz: Rebuilt.
a/kernel-huge-5.4.6-x86_64-2.txz: Rebuilt.
a/kernel-modules-5.4.6-x86_64-2.txz: Rebuilt.
ap/vim-8.2.0050-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.6-x86-2.txz: Rebuilt.
k/kernel-source-5.4.6-noarch-2.txz: Rebuilt.
Apparently MODULE_SIG was enabled by SECURITY_LOCKDOWN_LSM. We'll turn both
of those off to avoid needlessly tainting the kernel.
-LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY n
-LOCK_DOWN_KERNEL_FORCE_INTEGRITY n
-LOCK_DOWN_KERNEL_FORCE_NONE y
-MODULE_SIG_ALL n
-MODULE_SIG_FORCE n
-MODULE_SIG_FORMAT y
-MODULE_SIG_HASH "sha256"
-MODULE_SIG_KEY "certs/signing_key.pem"
-MODULE_SIG_SHA1 n
-MODULE_SIG_SHA224 n
-MODULE_SIG_SHA256 y
-MODULE_SIG_SHA384 n
-MODULE_SIG_SHA512 n
-SECURITY_LOCKDOWN_LSM_EARLY y
MODULE_SIG y -> n
SECURITY_LOCKDOWN_LSM y -> n
l/imagemagick-7.0.9_12-x86_64-1.txz: Upgraded.
l/libcap-2.29-x86_64-1.txz: Upgraded.
xap/vim-gvim-8.2.0050-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Rebuilt.
usb-and-pxe-installers/usbboot.img: Rebuilt.
+--------------------------+
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
