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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Rep:
Quote:
Originally Posted by jkh2cpu
With kernel-6.9.0, I cannot build the newest nvidia driver, and I cannot build a network driver for my 8814au wifi usb driver........
The latest Nvidia production driver-550.78, builds with the 6.9.0 kernel. I have installed it twice. Once with a "roll-your-own" kernel, then removed it, the kernel and the driver, and installed the driver again with the kernel provided in yesterday's -current updates.
Not a cough, hiccup or a sneeze. Everything is working as it should.
Last edited by cwizardone; 05-15-2024 at 12:47 PM.
Appears to yes , i have 3 machines with some ryzen cpus and only fail 1 that is intel.
2 boot fine (amd ryzne s) 1 laptop 1 tower.
1 fail to boot ( intel i7 7500u ) laptop.
Both of my Intel machines (DualCore & i7), boot just fine to the 6.9 kernel
and everything I have run at the cli works just fine. BUT, X will not start.
Right now underway here on this Intel DualCore machine is a compile of the 6.9.0 kernel
using using /boot/config-generic-6.6.30.x64 as a staring point.
slackpkg install k/*
root@glennmcc-server:/# slackpkg search kernel
Looking for kernel in package list. Please wait... DONE
The list below shows all packages with name matching "kernel".
While this looks a lot like what's being reported here, that patch made it into gcc-14.1.0. But there could possibly be more issues like this lurking in gcc-14.
As is usually the case, everything is working great here. I'm getting no crashes or illegal instructions on any of my machines, ranging from old i3/i5/i7 (an older i7 than was reported as problematic here), and even the venerable Phenom II X6 that completely lacks AVX support. I've tried xfce4-terminal, mc, okular, and whatever else had crash reports.
I might take a day off from compiling anything else (i.e. quit digging that hole deeper) and see what I can find. Hints appreciated, of course.
The kernel is another question, but that's also considerably easier to back out.
6.9.0 does not boot on my laptop. Kernel panic. 6.8.0 does boot. I'll try to bisect it.
Code:
4379f91172f39d999919c8e8b2b5e1d665d8972d is the first bad commit
commit 4379f91172f39d999919c8e8b2b5e1d665d8972d
Author: Christian Brauner <brauner@kernel.org>
Date: Tue Jan 23 14:26:23 2024 +0100
power: port block device access to file
Link: https://lore.kernel.org/r/20240123-vfs-bdev-file-v2-6-adbd023e19cc@kernel.org
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Christian Brauner <brauner@kernel.org>
kernel/power/swap.c
It seems to be code reading the hibernation image from disk. I have a swap file, not a partition, so maybe that's why everyone doesn't see this. When I now removed resume= and resume_offset= parameters from the kernel command line, even my laptop boots Pat's 6.9.0 kernel.
lscpu :
Vulnerabilities:
Gather data sampling*: Vulnerable: No microcode
or "Not affected" or "Mitigation: microcode" or "Mitigation: No microcode; AVX disabled" (or something like that)
Some Intel CPUs have no mitigation by microcode (even with last version 2024-05-14), disabling AVX causes "illegal instruction" with mc.
Kernel 6.6 does not disable AVX by default if no microcode mitigation, use append="clearcpuid=avx" in lilo to disable AVX
Kernel 6.9 disables AVX by default if no microcode mitigation, use append="gather_data_sampling=off" in lilo to keep AVX instructions
lscpu :
Vulnerabilities:
Gather data sampling*: Vulnerable: No microcode
or "Not affected" or "Mitigation: microcode" or "Mitigation: No microcode; AVX disabled" (or something like that)
Some Intel CPUs have no mitigation by microcode (even with last version 2024-05-14), disabling AVX causes "illegal instruction" with mc.
Kernel 6.6 does not disable AVX by default if no microcode mitigation, use append="clearcpuid=avx" in lilo to disable AVX
Kernel 6.9 disables AVX by default if no microcode mitigation, use append="gather_data_sampling=off" in lilo to keep AVX instructions
JFB
Ah yes, now we're getting some problems here! I have all my machines running with mitigations=off since I completely lack paranoia over side channel attacks.
Seems like a poor kernel default. /me goes looking to see if there's a Kconfig toggle...
Here is a snippet of code. I was trying to build the nvidia driver with kernel-6.9.0.
It builds find with 6.6.25 and gcc.
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-p2p.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-pat.o
make[3]: *** [scripts/Makefile.build:244: /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv.o] Error 1
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-procfs.o
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-usermap.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[3]: *** [scripts/Makefile.build:244: /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-pci.o] Error 1
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-vm.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[3]: *** [scripts/Makefile.build:244: /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-acpi.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[3]: *** [scripts/Makefile.build:244: /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-nano-timer.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
CC [M] /tmp/selfgz1716/NVIDIA-Linux-x86_64-550.67/kernel/nvidia/nv-vtophys.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
I may have spoken too soon. I downgraded gcc to 13.2 and then rebuilt kernel 6.9 under that gcc, and got the exactly same problems. SDDM not booting, applications randomly crashing, "Illegal instructions" errors... so it should be the kernel or somehting else. Reverted to kernel 6.6.30 and gcc 13.2 for now. I will investigate further.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.