Originally posted by sophisticles
View Post
Announcement
Collapse
No announcement yet.
AlmaLinux 9.4 Beta Restores Support For Some Hardware Deprecated By RHEL
Collapse
X
-
Originally posted by rene View Postremoving good old and mission critical tested hw support by removing PCI IDs? What ridiculously unserious Linux distribution is that even, ..?!?!?! Sad.
- Likes 3
Comment
-
Originally posted by sophisticles View PostI guess bit-for-bit identical went out the window.
Rocky is still trying to be bug for bug identical to RHEL though.
- Likes 3
Comment
-
Originally posted by andyprough View PostIf IBM doesn't watch out they'll create a situation where the best version of RHEL comes from someone else. Like how they lost control of the PC market to the clone makers in the 80s.
- Likes 1
Comment
-
Originally posted by You- View PostThe actual announcement stated "The following device drivers were modified to re-add PCI IDs for hardware disabled in upstream". Maybe those drivers were deprecated in RHEL 8.x? it is unclear.
It would be clearer to state they have re-added support for hardware disabled in RHEL9.
The RH mpt3sas.ko spits a message about your HBA being unsupported and ignores the HBA.
I guess Alma builds these kernel modules with the unsupported pci ids un-commented out.
A PITA from RH. I can understand when you certify your OS against hardware that dropping old, largely non-production hardware from your certified hardware list makes sense. But making the drivers available through a legacy/uncertified/unsupported hardware stream to keep legacy hardware running for as long as there is upstream support (retaining the RH unsupported message) would also make sense.
I thought I would have to either build a custom kernel from the RH sources or a custom mpt3sas kmod which is more of an irritation than anything else.
Comment
-
Originally posted by toves View PostI can understand when you certify your OS against hardware that dropping old, largely non-production hardware from your certified hardware list makes sense. But making the drivers available through a legacy/uncertified/unsupported hardware stream to keep legacy hardware running for as long as there is upstream support (retaining the RH unsupported message) would also make sense.
I thought I would have to either build a custom kernel from the RH sources or a custom mpt3sas kmod which is more of an irritation than anything else.
Comment
Comment