1) ubiquity already does list-oem which can query from ubuntu-drivers-common if any oem stuff needs to happen
2) ubuntu-drivers-common should provide '--package-list' option on the regular list command too
3) this way ubiquity can run 'list' with '--package-list' ahead of the prepare stage to peak, if any dkms modules would get installed.
4) then ubiquity would be able to show the right ui when people tick third-party drivers, i.e. determine if mok is needed or not.
5) under secureboot however, I don't think ubiquity should be trying to install any dkms drivers as they will all fail to load. Thus it can even skip calling `install` on them altogether.
1) ubiquity already does list-oem which can query from ubuntu- drivers- common if any oem stuff needs to happen
2) ubuntu- drivers- common should provide '--package-list' option on the regular list command too
3) this way ubiquity can run 'list' with '--package-list' ahead of the prepare stage to peak, if any dkms modules would get installed.
4) then ubiquity would be able to show the right ui when people tick third-party drivers, i.e. determine if mok is needed or not.
5) under secureboot however, I don't think ubiquity should be trying to install any dkms drivers as they will all fail to load. Thus it can even skip calling `install` on them altogether.