Re: DMI mismatch on OEM-rebranded laptops causing driver issues (LAPBC710 / Avell B.On)
Yuri Musachio wrote:
> Hey everyone, how’s it going?
> (Feel free to correct me if I’m wrong...)
>
> When we install Debian on a computer and Linux is installed, part of the process during the kernel build involves checking some DMI information from your machine.
> Some computers (maybe most of them), through a partner or reseller, modify certain information on the motherboard by injecting custom values like:
> Serial key (used for Windows), product name, vendor, etc.
>
> Sometimes, the Linux kernel project doesn’t have those reseller/vendor entries listed, so the DMI data doesn’t match any known model in the kernel database.
> In my case, I’m using an Intel NUC LAPBC710 laptop kit, but the reseller in Brazil branded it as "Avell B.On".
> Even though the LAPBC710 model is listed in the Linux database (for example), this mismatch can make it harder to properly install or detect some components for correct driver usage.
> A classic example for me is SOF (the audio driver).
>
> So the question is:
> How do you guys deal with DMI info that doesn’t match what’s listed in the kernel?
> Maybe submit some kind of patch to the kernel with a DMI match override?
>
> Since this info is mostly “read-only,” is there any tool or installer option in Debian that can help it recognize the correct model name or DMI string?
Mostly, the kernel ignores DMI data. Instead, it enumerates
devices on each bus and matches IDs.
You can update to the newest PCI ids with:
sudo update-pciids
and make intermediate changes with the udev mechanism.
-dsr-
Reply to: