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 know that you are a long time slacker and confident in building your own kernels. Still, just to make sure, if you do:
Code:
cat /proc/version
Does the output indicate that the kernel was built recently. A common mistake when upgrading kernel packages is to forget to manually updating the bootloader. I don't think you made that mistake, but just to make sure...
Otherwise, maybe there are some more instructions disabled in the 6.9 kernel?
I for one I have NO issues with the stock 6.9.0 kernel on fancy and modern CPUs like Intel Core2 Duo P8600 on my laptop, and Intel i5-3570s on my mini-PC HP Elite 8300 USDT.
BUT, I use since loong time the parameter "mitigations=off" on the kernel command line, as I do NOT believe on the chimerical hardware security issues from where some smart people earn honest moneys.
BTW, did you noticed that the discovery of these hardware flaws had become a sport after the Google, Intel and AMD started to pay royally for them?
Guys, stop biting on that academic crap before your CPUs will arrive to have the computation power of a Z80 and a ZX Spectrum will start challenging the performances of your fancy box.
My honest suggestion for you is just to add "mitigations=off" on the kernel command line, reboot the box and call a day.
PS. The kernel config can have a nice CONFIG_CPU_MITIGATIONS=n for cutting this crap from its very root. Anyway, the ones skilled enough to be really concerned by these mythical hardware flaws, also are skilled enough to build and deploy their own kernel packages.
Last edited by LuckyCyborg; 05-16-2024 at 02:39 AM.
A few weeks ago I participated in a Linux meeting, where one of the speakers practically demonstrated that the overall impact of Linux mitigations on the current computing power is about 50%.
So, by disabling mitigations, the computing power of your computer doubles.
I believe that the impact of the mitigations is already so great that their general usefulness is questionable. Anyway, today most of the computers that are hacked happen through Social Engineering. Probably 99.99% of them.
Last edited by ZhaoLin1457; 05-16-2024 at 03:57 AM.
For Pat, i have compiled qt6-6.7.1 on same git version, this version compil fine without problem, with 'ninja-1.12.1' and also qtwebengine without the ninja patch.
On the advice of 0XBF, am requesting the inclusion of bcachefs-tools, so that the bcachefs file system, now in the mainline Linux kernel, can be used and managed on Slackware.
I know that you are a long time slacker and confident in building your own kernels. Still, just to make sure, if you do:
Code:
cat /proc/version
Does the output indicate that the kernel was built recently. A common mistake when upgrading kernel packages is to forget to manually updating the bootloader. I don't think you made that mistake, but just to make sure...
Otherwise, maybe there are some more instructions disabled in the 6.9 kernel?
regards Henrik
Yes, lilo was re-run after the upgrade to kernel-generic-6.9.0-x86_64-2
Here's a fresh boot-up to that that system.
cat /proc/version shows that the system is booted to Patrick's new kernel.
And as we see on the startx messages, I added mitigations=off at the lilo boot prompt.
But still, X will not start.
Code:
Welcome to Linux 6.9.0 x86_64 (tty1)
glennmcc-i7 login: root
Password:
Last login: Thu May 16 00:46:56 on tty1
Linux 6.9.0.
You don't have to know how the computer
works, just how to work the computer.
root@glennmcc-i7:~# cat /proc/version
Linux version 6.9.0 (root@z-mp.slackware.lan) (gcc (GCC) 14.1.0, GNU ld version 2.42-slack151) #1 SMP PREEMPT_DYNAMIC Wed May 15 15:18:37 CDT 2024
root@glennmcc-i7:~# startx
xauth: file /root/.serverauth.1162 does not exist
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux glennmcc-i7.net 6.9.0 #1 SMP PREEMPT_DYNAMIC Wed May 15 15:18:37 CDT 2024 x86_64
Kernel command line: BOOT_IMAGE=SlackWare64b ro root=811 vt.default_utf8=0 mitigations=off
Current version of pixman: 0.43.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 16 11:00:10 2024
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
additional information.(EE) (EE) Server terminated with error (1). Closing log file.oundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" forxinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
These are the startx messages from before the upgrade to kernel-generic-6.9.0-x86_64-2
but rather while booted to the kernel I built.
Code:
root@glennmcc-i7:~# startx
xauth: file /root/.serverauth.1240 does not exist
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux glennmcc-i7.net 6.8.9 #2 SMP PREEMPT_DYNAMIC Wed May 15 17:57:30 EDT 2024 x86_64
Kernel command line: BOOT_IMAGE=SlackWare64b ro root=811 vt.default_utf8=0
Current version of pixman: 0.43.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed May 15 18:24:55 2024
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.erver lostp.DisplayManager.AccountsService?libEGL warning: DRI2: failed to authenticateMESA: error: ZINK: fa
As we see, my fresh build of 6.8.9 works fine.
However, my fresh build of 6.9.0 does not.
Code:
root@glennmcc-server:~# startx
xauth: file /root/.serverauth.1203 does not exist
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux glennmcc-server.net 6.9.0 #1 SMP PREEMPT_DYNAMIC Wed May 15 17:12:46 EDT 2024 x86_64
Kernel command line: BOOT_IMAGE=SlackWare64b ro root=811 vt.default_utf8=0
Current version of pixman: 0.43.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed May 15 17:59:38 2024
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
additional information.(EE) (EE) Server terminated with error (1). Closing log file.oundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" forxinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Have now reformatted that partition while booted to slackware64-15.0 on the other HDD
New install underway without choosing to format during the install.
Again... everything except the huge kernel is being installed.
_____________
OK, now it boots but X still will not start
even with mitigations=off added at the lilo boot prompt.
Code:
Welcome to Linux 6.9.0 x86_64 (tty1)
glennmcc-i7-fresh login: root
Password:
Last login: Thu May 16 12:58:27 on tty1
Linux 6.9.0.
The more he talked of his honor the faster we counted our spoons.
-- Ralph Waldo Emerson
root@glennmcc-i7-fresh:~# startx
xauth: file /root/.serverauth.998 does not exist
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux glennmcc-i7-fresh.net 6.9.0 #1 SMP PREEMPT_DYNAMIC Wed May 15 15:18:37 CDT 2024 x86_64
Kernel command line: BOOT_IMAGE=SlackWare64b ro root=811 vt.default_utf8=0 mitigations=off
Current version of pixman: 0.43.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 16 13:00:10 2024
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
ase also check the log file at "/var/log/Xorg.0.log" for additional information.(EE) (EE) Server terminated with error (1). Closing log file.oundation support at http://wiki.x.org for help. (EE) Plexinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Removed the generic kernel, installed the huge kernel, re-ran lilo, rebooted.
Code:
Welcome to Linux 6.9.0 x86_64 (tty1)
glennmcc-i7-fresh login: root
Password:
Last login: Thu May 16 13:00:05 on tty1
Linux 6.9.0.
What fools these mortals be.
-- Lucius Annaeus Seneca
root@glennmcc-i7-fresh:~# startx
xauth: file /root/.serverauth.1021 does not exist
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux glennmcc-i7-fresh.net 6.9.0 #1 SMP PREEMPT_DYNAMIC Wed May 15 15:17:07 CDT 2024 x86_64
Kernel command line: BOOT_IMAGE=SlackWare64b ro root=811 vt.default_utf8=0
Current version of pixman: 0.43.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 16 13:10:34 2024
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
ase also check the log file at "/var/log/Xorg.0.log" for additional information.(EE) (EE) Server terminated with error (1). Closing log file.oundation support at http://wiki.x.org for help. (EE) Plexinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
root@glennmcc-i7-fresh:~# ls -l /boot/vmlinuz
lrwxrwxrwx 1 root root 18 May 16 13:08 /boot/vmlinuz -> vmlinuz-huge-6.9.0
BUT, I use since loong time the parameter "mitigations=off" on the kernel command line, as I do NOT believe on the chimerical hardware security issues from where some smart people earn honest moneys.
Yes, for a PC running Linux where there is only one configured normal user account there is no need to care about those mitigations.
However, for systems with multiple users supposed to have secrets they want to keep for themselves those mitigations should be considered. Examples of such systems are web hotels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
