On Tue, Sep 20, 2022 at 8:57 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
Someone also reported nosound after 5.19.8 so it sounds like a lot of
the modules either weren't built (at all or correct) or were not
included in the install rpms.
a "find /lib/modules/kernelversion -name "*ko*" -ls | wc -l against it
might tell you if the count is significantly different.
% find /lib/modules/5.19.8-200.fc36.x86_64 -name "*ko*" -ls | wc -l
4097
% find /lib/modules/5.19.9-200.fc36.x86_64 -name "*ko*" -ls | wc -l
1878
Also doing;
diff /boot/config-5.19.[89]* would show if the config files
controlling module builds was different.
% diff /boot/config-5.19.[89]*
3c3
< # Linux/x86_64 5.19.8-200.fc36.x86_64 Kernel Configuration
---
> # Linux/x86_64 5.19.9-200.fc36.x86_64 Kernel Configuration
35c35
< CONFIG_BUILD_SALT="5.19.8-200.fc36.x86_64"
---
> CONFIG_BUILD_SALT="5.19.9-200.fc36.x86_64"
3661c3661
< CONFIG_IWLMEI=m
---
> # CONFIG_IWLMEI is not set
3c3
< # Linux/x86_64 5.19.8-200.fc36.x86_64 Kernel Configuration
---
> # Linux/x86_64 5.19.9-200.fc36.x86_64 Kernel Configuration
35c35
< CONFIG_BUILD_SALT="5.19.8-200.fc36.x86_64"
---
> CONFIG_BUILD_SALT="5.19.9-200.fc36.x86_64"
3661c3661
< CONFIG_IWLMEI=m
---
> # CONFIG_IWLMEI is not set
IWLMEI pulls in a bunch of modules, but over 2000 seems excessive!
% find /lib/modules/5.19.[89]-200.fc36.x86_64 -name "*ko*" | grep hfsplus
/lib/modules/5.19.8-200.fc36.x86_64/kernel/fs/hfsplus/hfsplus.ko.xz
% grep -i hfsplus /boot/config-5.19.[89]*
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_HFSPLUS_FS=m
/boot/config-5.19.9-200.fc36.x86_64:CONFIG_HFSPLUS_FS=m
/lib/modules/5.19.8-200.fc36.x86_64/kernel/fs/hfsplus/hfsplus.ko.xz
% grep -i hfsplus /boot/config-5.19.[89]*
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_HFSPLUS_FS=m
/boot/config-5.19.9-200.fc36.x86_64:CONFIG_HFSPLUS_FS=m
Looks like the 5-19.9 package installation missed hfsplus.ko, needed for dual
boot with macOS. Gnome Software update is showing 5.19.9 as an available
update despite the fact that it was installed a few days ago. I updated using
dnf on the command-line and the system is now booting 5.19.9. Looks like
there was a bad 5.19.9 update that has been fixed.
George N. White III
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue