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: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,026
Rep:
Quote:
Edit in: Just for chuckles I plugged in a bluetooth USB dongle and rebooted. No problem
..and what would you expect?
This seems to be the last message from the booting kernel. For whatever reason, someone messed up bluetooth (if device worked before). That is all. Why would you expect that bluetooth is the cause of boot failure?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,186
Original Poster
Rep:
It appears the kernel message board system went down at approximately 08:20 UTC, this morning. I've checked four different boards and not a one of them has been updated since that time.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,186
Original Poster
Rep:
The message boards have come back to life and apparently updates were posted earlier, but have disappeared into the mist.
Here is what I've found so far and they are scheduled to be released on Wednesday, 13 September 2023.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,026
Rep:
Quote:
Originally Posted by marav
I was impatient. It finally boots after more than 5 minutes ...
But it cannot go into hibernation for whatever reason
That is good. You can check in the logs what is causing boot delay.
security measures: LSM early and LSM integrity/confidentiality when enabled and forced forced from kernel will disable hibernation (security measure)
with boot message
Quote:
Lockdown: elogind-daemon: hibernation is restricted; see man kernel_lockdown.7
and hibernation option is gone from the menu.
but I assume that you did not enable any of these.
Also failing bluetooth should not affect boot at all
Hopefully you will see the reason for both boot delay and failing hibernation in the boot logs.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,186
Original Poster
Rep:
A good summery of the changes and additions to the 6.6 Kernel.
Quote:
Linux 6.6 Features Include The EEVDF Scheduler, Shadow Stack, Intel IVSC, AMD DBC & More
By Michael Larabel. 12 September 2023.
With the Linux 6.6 merge window over, here's a look at the most interesting new features, hardware support, and other changes to find with this kernel that will debut as stable around the end of October......
I'm announcing the release of the 6.4.16 kernel.
NOTE, this is the LAST 6.4.y release, this branch is now end-of-life.
All users must move to the 6.5.y branch at this point in time.
I found a way to have my "own" .config file for my laptop. I tested it with 6.5.2 and 6.5.3 and it looks ok.
Also NVIDIA drivers works ok.
Its faster at boot now, not big different but the most good for me , I need 7 minutes to download build and install a generic kernel
I use
Code:
make localmodconfig
and old config not needed.
Here is what I do:
1) boot from a generic Slackware kernel.
2) startx and plugin every external device you use in your laptop (mouse, usb/hdd, headset etc)
3) Open your browser to a online site for test mic and camera, or open zoom, skype something which will keep in use mic and camera during .config creation.
We are doing these because only modules that now are in lsmod will be in the config file.
These are the commands I used to build and install...
Code:
make localmodconfig
make -j$(getconf _NPROCESSORS_ONLN)
make modules_install
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 6.5.3 > file.sh
cp arch/x86_64/boot/bzImage /boot/vmlinuz-6.5.3
sed -i 's/mkinitrd -c/mkinitrd/g' file.sh
sh file.sh
grub-mkconfig -o /boot/grub/grub.cfg
If I found something is missing I will add it in config and rebuild... its only 7 minutes
If anyone have suggestions... plz
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.