Tried Debian 12 live. It does not detect the new disks.
It does see the controller card. Debian 12 live is kernel 6.1.0-22
( almost the same as Antix which works 6.1.60)
Tried mx23.1 ahs live. It does not detect the new disks.
It does see the controller card. MX23 is kernel 6.5.0-1 mx-ahs
I did it in Void, where I have a whole collection of kernels
Tried these
6.6.32_1
6.6.27_1
6.5.13_1
6.3.13_2
6.1.91_1
6.0.19_1
5.19.17_1
5.10.215
None of them can see the new disks. They can all see the controller card
I think we can rule out a kernel regression problem
unless it is a regression combined with something else…
Then I made a discovery.
I have Artix with S6 , which was installed before I fitted the new controller card and disk cage. Artix is Arch based.
So I booted Artix, and guess what…it can see the new disks!
So I have 2 distros that can see the new disks
Artix that was installed long ago, before the new card and disks were fitted
Antix that was installed after the new card and disks were fitted.
and 4 distros (MX, Void, Devuan, and Peppermint), all installed long ago, and none of these can see the new disks…
So what does that mean?
My guess is that I have a boot order problem
The clue is… Artix uses S6 init system… S6 takes care of dependencies between services… all my other distros are sysV or runit, and they dont dynamically take care of dependencies…
So , on that theory, why did Antix work? Antix is sysVinit.?.. because I installed it… when you install the installer sets up the boot order for sysV or runit, and it is fixed thereafter… unless you change it by hand by getting into the rc.x files.
So why did the 2 live systems not work?.. because I need an unusual boot order and they did not have it by default.
How to test my theory?
Make a prediction and see if it is right
OK. I predict if I do a new install of MX ( or anything else) it will see the new disks…
even if I use the same MX as I already have installed…
Tune in tomorrow to see if my brave prediction was confirmed
and
Thank you all. This is getting tiresome.
If you can come up with a better theory, I will be glad to hear and test it.
I have had to install Windows, to get drivers, and then install Linux, and wipe Windows and you may have to install either Ubuntu or use Gentoo, with the ~amd64 flag, to get the latest kernel.
How is LFS? A nightmare!!! For the life of me, I can get as far as the chroot and not be able to enter the chroot!!! I think it has something to do with the export PS1=“(chroot) ${PS1}” but I cannot get the right syntax for the command!!!
./configure execute configure in current directory
…/configure execute configure in the directory above you
Correction ../configure above
…/configure does not make sense to me
Hi Jorge,
I dont know what UNRAID is?.. I am not using raid, just normal disks
My controller is ASM1062, theirs is ASM1061
It says use IOMMU disabled.
I might try disabling iommu with a kernel parameter… I saw that somewhere else too … or maybe in the BIOS
Thanks
Regards
Neville
Agree, init system is a bit late… except that this card supports hotplug and that may involve udev ?
I checked modules… could not see anything meaningful. I may have missed something.
What is a firmware bin? Do you mean packages of firmware?
Do you know if the kernel builds in firmware during install, like it does with modules?.. in other words is having a firmware package enough or does it have to be detected and built in at install time like with a module?.. all those kernels I tested in Void were installed before I added the card and disks… maybe I need to try adding a kernel now that the card and disks are present
I read Jorge’s link , but missed that.
What I saw was disable iommu
You bet.
Do you agree not a kernel regression? I tried a lot of kernels, but only in Void.
