# Missing driver: drivers/usb/serial/f81232.c **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-9\ **Created:** [June 12, 2025, 3:36pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778 "2025-06-12T15:36:34Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![lenny8819](https://avatars.discourse-cdn.com/v4/letter/l/b5a626/32.png) [@lenny8819](https://forums.rockylinux.org/u/lenny8819)\ **Post date:** [June 12, 2025, 3:36pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/1 "2025-06-12T15:36:34Z")
Hello everyone, We are missing a serial driver in Rocky Linux 9. It is available via ELrepo, but SecureBoot makes this difficult. Can it be rebuilt into Rocky 9? Lenny ---
**Author:** ![lenny8819](https://avatars.discourse-cdn.com/v4/letter/l/b5a626/32.png) [@lenny8819](https://forums.rockylinux.org/u/lenny8819)\ **Post date:** [July 24, 2025, 2:07pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/2 "2025-07-24T14:07:43Z")
Obviously not an option? ☹ ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [July 24, 2025, 2:31pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/3 "2025-07-24T14:31:41Z")
Nope, you have to ask elrepo if they can help with it. Otherwise you have to disable secure boot. Rocky is based on RHEL, that means if it’s not in RHEL, it’s not in Rocky. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [July 25, 2025, 6:50am UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/4 "2025-07-25T06:50:02Z")
> [@lenny8819](#): > > It is available via ELrepo, but SecureBoot makes this difficult. What in Secure Boot is an issue? ---
**Author:** ![lenny8819](https://avatars.discourse-cdn.com/v4/letter/l/b5a626/32.png) [@lenny8819](https://forums.rockylinux.org/u/lenny8819)\ **Post date:** [August 21, 2025, 2:06pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/5 "2025-08-21T14:06:40Z")
ELrepos helped us very quickly, but this causes the signature to be spoken by the kernel and Secure Boot no longer allows the system to boot. Of course, I could sign and distribute certificates manually, but this is not an option for several thousand systems. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [August 21, 2025, 8:20pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/6 "2025-08-21T20:20:02Z")
ELRepo signs the kernel modules that they build for EL kernels and they distribute their certificate. See [secureboot [ELRepo Wiki]](https://elrepo.org/wiki/doku.php?id=secureboot) Running _mokutil --import_ remotely is trivial. Alas, visiting “several thousand systems” to complete the import procedure is obviously not feasible. About as hard as disabling the Secure Boot on them. ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [August 21, 2025, 8:21pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/7 "2025-08-21T20:21:07Z")
> [@jlehtone](#): > > Running _mokutil --import_ remotely is trivial. > > Alas, visiting “several thousand systems” to complete the import procedure is obviously not feasible. About as hard as disabling the Secure Boot on them. Ansible could help with that, in terms of distributing the certificate to import. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [August 21, 2025, 9:24pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/8 "2025-08-21T21:24:47Z")
Yes. ELRepo’s `elrepo-release` package does provide the `/etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der` “Distribute” is thus like `ansible all -m dnf -a 'name=elrepo-release'` ---
**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\ **Post date:** [August 21, 2025, 10:35pm UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/9 "2025-08-21T22:35:36Z")
OK, but how does it get into the “BIOS”? ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [August 22, 2025, 6:24am UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/10 "2025-08-22T06:24:05Z")
You run mokutil (which copies key from file to somewhere – to a “ToDo list”) and reboot. On boot the UEFI does run “Enroll key dialog” (rather than bootloader). In the dialog you confirm that you really want the certificate into “BIOS”. That is, the dialog transfers the key from ToDo list into the “BIOS” (and then reboots). The ELRepo wiki has screenshots from the steps. The enrollment has to be confirmed “on seat”. Otherwise any remote hacker could inject their certificates. * * * Compare the above to: Reboot. Enter UEFI setup. Disable Secure Boot. Reboot. That too is an “on seat” procedure. ---
**Author:** ![jbkt23](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jbkt23](https://forums.rockylinux.org/u/jbkt23)\ **Post date:** [August 22, 2025, 10:44am UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/11 "2025-08-22T10:44:49Z")
> [@jlehtone](#): > > On boot the UEFI does run “Enroll key dialog” (rather than bootloader). > In the dialog you confirm that you really want the certificate into “BIOS”. > That is, the dialog transfers the key from ToDo list into the “BIOS” (and then reboots). Some motherboards require you to enter the bios to enroll the key. On my Lenovos the procedure is as described but my machine with a Gygabite MB you have to enter the bios to do the enrollment. So I see Secure boot as a consumer feature that protects individual machines out of the box. For specialized industry applications with unique applications and hardware another security approach needs to be applied. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [October 21, 2025, 10:45am UTC](https://forums.rockylinux.org/t/missing-driver-drivers-usb-serial-f81232-c/18778/12 "2025-10-21T10:45:31Z")
Closed on October 21, 2025, 10:45am UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.