Extensions: Merge modules and runtime - #907
Conversation
Installer builds for 2d5ff51Do not use these installers for production systems. They are intended for testing purposes only. They will update to the latest PR build, which will break your install eventually.
|
`broadcom-sta-common` is just docs as we don't ship `/etc/modprobe.d/broadcom-sta-common.conf`, and it isn't needed if we are doing kernel arguments.
|
@lewisgoddard I didn't see 610 was still in multiverse... Should be drop down one version, or keep 610 since it will probably be out of multiverse on elementaryOS release? |
Installer builds for f07a6d7Do not use these installers for production systems. They are intended for testing purposes only. They will update to the latest PR build, which will break your install eventually.
|
|
I'm not sure, that's probably a question for @danirabbit:
Multiverse is likely to have a newer package available, which will support newer hardware sooner. Shipping multiple options would be hard because sysupdate has no concept of mutually exclusive features. We have Explanation: multiverse is only enabled for the NVIDIA driver extension.
Explanation: Block everything else from it so no other image can pull from multiverse.
Package: *
Pin: release c=multiverse
Pin-Priority: -1
Package: /nvidia/
Pin: release c=multiverse
Pin-Priority: 500 |
|
Maybe we could also just add /etc/apt/sources.list.d/multiverse.list to the mkosi.sandbox of the Nvidia image? So only that image has that repo enabled |
|
That's kind of my second option, but I'm not sure it works. Will mkosi honor the setting placed outside the main sandbox? I don't think so, and package lists are not currently refreshed. You can try it if you want, but the apt preferences file accomplishes the same thing. |
ryonakano
left a comment
There was a problem hiding this comment.
I can confirm that with this branch the Wi-Fi module is detected and the list of access points are displayed in Network Indicator with just running sudo updatectl enable --now driver-broadcom and then reboot.
Installer builds for df6ef14Do not use these installers for production systems. They are intended for testing purposes only. They will update to the latest PR build, which will break your install eventually.
|
|
@lewisgoddard I used your approch, if it looks good, you can merge this. Thanks |
A bunch of cleanup changes, now that @ryonakano confirmed this was working.
It's possible existing daily install can't upgrade with theses name changes, drivers will probably have to be disabled+removed before upgrading.
Fix #878