LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-21-2021, 04:34 PM   #1
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,113

Rep: Reputation: Disabled
kernel panic trying to boot Slackware-current on an external SSD (/ on /dev/sdc5) with kernel-huge (5.15.3 and 5.15.4)


Tried 5.15.3 and 5.15.4, same issue. The device /dev/sdc5 (more generally /dev/sdc) has not been created when needed to switch root during the boot sequence.

However the same kernel installed on Slint64-14.2.1 allows to boot, but in this case / is on an internal drive (/dev/sdb6).

But booting with a generic kernel + initrd works in Slackware with both versions (5.15.3 and 5.15.4) maybe this can give a clue?

PS and OT: As an aside, using the huge kernel 5.15.4 swap in zram fails. it works with the generic one. To try: https://slackware.uk/slint/x86_64/sl...rch-2slint.txz

However I am not too worried, not shipping huge kernels in Slint.

PPS: Follow-up in post #6.

Last edited by Didier Spaier; 11-21-2021 at 05:35 PM. Reason: PS added.
 
Old 11-21-2021, 04:42 PM   #2
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,779

Rep: Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655Reputation: 3655
Honestly, I wonder WHY the Slackware insists to ship those huge kernels...

After all, no other distribution thinks that them are needed.

I for one, I suggest you to ignore the huge kernels - they are just like the tail at humans. It was something useful millions years ago, but today?

Last edited by LuckyCyborg; 11-21-2021 at 04:47 PM.
 
1 members found this post helpful.
Old 11-21-2021, 04:52 PM   #3
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 648
Blog Entries: 2

Rep: Reputation: 514Reputation: 514Reputation: 514Reputation: 514Reputation: 514Reputation: 514
Quote:
Originally Posted by LuckyCyborg View Post
Honestly, I wonder WHY the Slackware insists to ship those huge kernels...

After all, no other distribution thinks that them are needed.

I for one, I suggest you to ignore the huge kernels - they are just like the tail at humans. It was something useful millions years ago, but today?
I recall seeing comments by Pat suggesting his not all that keen on huge kernels as well; that said, he apparently thinks they are valuable enough niche wise to warrant having them around still. Please correct me if I'm wrong here.
 
1 members found this post helpful.
Old 11-21-2021, 05:00 PM   #4
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,828

Rep: Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463
Yes. Some of us still exist that despise initrd and never use it. The only compelling reason for an initrd is for encryption afaik. Didier's problem is not without a reasonable solution but it is apparent that he prefers generic + initrd and Huge is considerable work an d it is reasonable for Didier to not take on that work for his use case. It just isn't everyone's. Thankfully PV is more accommodating.
 
Old 11-21-2021, 05:23 PM   #5
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware
Posts: 1,348

Rep: Reputation: 217Reputation: 217Reputation: 217
As far as I'm concerned, initrd is just one more annoyance to running -current. Once 15 drops, I'm totally fine with running generic and using initrd (in fact, I plan to), but with the 1-3x per week kernel updates, I'm fine saving a few minutes by using huge for now, provided everything works as designed.

I was under the impression that huge existed to allow for as much hardware as possible to boot correctly out of the box. If this is actually the case, then it kind of seems like something worth keeping, but I admit I may be mistaken here.
 
Old 11-21-2021, 05:25 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,113

Original Poster
Rep: Reputation: Disabled
Follow up.

Boot succeeded with kernel-huge-5.15.4 and the initrd built for kernel-generic-5.15.4, thus I assume the the issue is linked to the configuration of the huge kernel.
I list below the modules loaded by the initrd:
Quote:
usb-storage
uas
ehci-hcd
ehci-pci
xhci-hcd
xhci-pci-renesas
xhci-pci
ohci-hcd
ohci-pci
uhci-hcd
hid
usbhid
i2c-core
i2c-hid
hid-generic
video
wmi
rfkill
sparse-keymap
battery
platform_profile
asus-wmi
hid-asus
hid-cherry
hid-logitech
hid-logitech-dj
hid-logitech-hidpp
hid-lenovo
hid-microsoft
hid-multitouch
jbd2
mbcache
ext4
@All: please stay on topic. I don't ship a huge kernel in Slint and no user complained about that so far, but as long as one is shipped in Slackware we should help booting with it.
 
1 members found this post helpful.
Old 11-21-2021, 05:41 PM   #7
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 4,549
Blog Entries: 7

Rep: Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625Reputation: 2625
Quote:
Originally Posted by enorbet View Post
Yes. Some of us still exist that despise initrd and never use it.
The last part of this statement is not true on a technical level, because the Slackware installer is an initrd. You can't install Slackware without using an initrd. This has been true for a very long time. Remember the boot & root floppy disk combination from the 90s?

As for despising it: It's software my friend. I don't see how anyone could have such strong feelings about this.
Quote:
Originally Posted by enorbet View Post
The only compelling reason for an initrd is for encryption afaik.
How about the efficiencies gained by not loading hundreds of unused drivers? Even now, with the huge multi-core CPUs we have, I notice performance differences between the huge and generic kernels.

With that said, I like the concept of the huge kernel being available for a "does it all in an emergency type of situation." But realistically, it has been a long time since I've found myself in a position to need such a thing.
Quote:
Originally Posted by enorbet View Post
Thankfully PV is more accommodating.
The Slackware installer generates an initrd for you, and will automatically configure LILO or eLILO to use it by default.
 
Old 11-21-2021, 08:03 PM   #8
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,601

Rep: Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710Reputation: 8710
Quote:
Originally Posted by enorbet View Post
Thankfully PV is more accommodating.
For the time being.
 
Old 11-21-2021, 09:44 PM   #9
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,828

Rep: Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463
Heheh well rkelsen admittedly "despise" overstates the case but I was just trying to mention my disdain for initrd (which seems an awkward workaround to me) without resulting in my usual wall of text Of course I use it when I have no choice but within a very few minutes of installing I compile my own kernel and use it, with no initrd. I blacklist everything kernel related excepting kernel-firmware in slackpkg+ and use my own through many versions of Current and RCs.

I've tried using the generic config as a starting point and simply adding in what I need but experience has taught me I do better using the config for Huge and removing what I don't need while I alter a few options I prefer. There was a time back in the day that I recall working hard to get bzImage down to floppy size but that became impossible and on-demand loadable modules made it close to meaningless. I have benchmarked in several ways and I don't see any loss in performance my way. In fact, just the opposite.

Additionally since sometime around 1992 I have always multi-booted so automatic bootloader configs are not for me. and I prefer some level of redundancy in bootloaders. So I don't mind manual configuration, I prefer it.
 
Old 11-22-2021, 12:30 AM   #10
_peter
Member
 
Registered: Sep 2014
Location: paris
Distribution: slackware
Posts: 314

Rep: Reputation: Disabled
not much of an help but it works here on an external ssd Didier with or without initrd for 5.15.3: booting with lilo on older hardware & no encryption.

here are the modules used by mkinitrd

Code:
ohci-pci
ehci-pci
xhci-hcd
uhci-hcd
ehci-hcd
hid
usbhid
i2c-hid
hid_generic
hid-asus
hid-cherry
hid-logitech
hid-logitech-dj
hid-logitech-hidpp
hid-lenovo
hid-microsoft
hid_multitouch
jbd2
mbcache
crc32c_intel
crc32c_generic
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware-current, huge: Kernel panic when 'root=UUID' in GRUB configuration luvr Slackware 24 04-21-2022 08:01 AM
Huge kernel boots--Huge.SMP (and generic.smp) kernel will not MTCAT Linux - Newbie 4 02-03-2021 02:11 PM
How to create a single-boot Win 10 ssd from a dual-boot ssd Robert.Thompson Linux - Newbie 5 03-28-2019 02:29 PM
[SOLVED] update-grub is picking up Huge first, advance boot listing will not boot generic kernel gets panic. BW-userx Slackware 30 02-18-2017 05:46 PM
Slackware 13.1 huge smp is not huge cs_strong Slackware 4 11-16-2010 07:41 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:10 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration