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.
This is a list of issues encountered with the 6.1.xx kernel (and now the generic "huge" kernel) in Slackware64-Current.
Kernel 6.x.x:
Fail to assemble mdadm raid on LSI MegaRAID SAS 2008 controller with initrd. I cannot recall exactly when this started, but I first reported the issue here.
Lenovo T460 touch screen does not work.
Kernel 6.1.6x (generic "huge" kernel):
Fail to boot encrypted ext4 root partition with initrd. 6.1.61 worked. 6.1.60 and 6.1.62 do not. All kernels prior to 6.1.60 boot successfully.
Fail to assemble mdadm raid on LSI MegaRAID SAS 2008 controller with initrd.
Isnt that MegaRaid card a hardware RAID controller which presents all disks connected as a single disk like /dev/sda to the kernel? If so, why would you want to use mdadm to create a RAID? Did you configure the controller to only JBOD?
Isnt that MegaRaid card a hardware RAID controller which presents all disks connected as a single disk like /dev/sda to the kernel? If so, why would you want to use mdadm to create a RAID? Did you configure the controller to only JBOD?
regards Henrik
The controller is configured as JBOD, with all disk presented to the OS under /dev/sdX. mdadm is used to assemble the RAID. Makes it easier to do RAID migration when needed and or swap the controller when they fail. No need to be running around looking for specific controller from specific manufacturer.
Fail to boot encrypted ext4 root partition with initrd. 6.1.61 worked. 6.1.60 and 6.1.62 do not. All kernels prior to 6.1.60 boot successfully.
This issue was completely user error. It was due to limited space on the boot volume. mkinitrd needs better error checking to fail when disk write fail (out of space).
This is a list of issues encountered with the 6.1.xx kernel (and now the generic "huge" kernel) in Slackware64-Current.
Kernel 6.x.x:
Fail to assemble mdadm raid on LSI MegaRAID SAS 2008 controller with initrd. I cannot recall exactly when this started, but I first reported the issue here.
Lenovo T460 touch screen does not work.
[/LIST]
This turned out to be a disk spin-up timing issue. Adding the wait flag (-w) to mkinitrd fixed the issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.