Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modules list reset when updating RR #1534

Open
marboroman opened this issue Jun 25, 2024 · 3 comments
Open

modules list reset when updating RR #1534

marboroman opened this issue Jun 25, 2024 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@marboroman
Copy link

marboroman commented Jun 25, 2024

Modules become all selected after updating RR. Need to inspect them all again to deselect unnecessary. The correct attitude is to preserve previous selections and add new modules unselected.

@wjz304
Copy link
Contributor

wjz304 commented Jun 26, 2024

Because some changes in drivers are difficult to handle,

For example

  1. 24.6.7 A driver depends on B, you select A and B, but A in 24.6.8 depends on B and C, there is no good way to only add C selection
  2. X driver exists in 24.6.7, but X driver is removed in 24.6.8,
  3. N1 driver exists in 24.6.7, but it is upgraded to N2 driver in 24.6.8, and the name changes

So currently select all to avoid some problems

@RROrg RROrg deleted a comment from github-actions bot Jun 26, 2024
@marboroman
Copy link
Author

ok, please let us know also these things:

  1. if there are few versions of one drivers exist and all selected (i915, r8125) which one is used? are there any priorities or everything is just determined in alphabetical order?

  2. what is affected by the number of connected modules? loading time? free space on some system partitions? Does it make sense to disable those modules that you know for sure will never be needed (virtio on baremetal, wifi on wired configurations and so on)?

@wjz304
Copy link
Contributor

wjz304 commented Jun 26, 2024

  1. Yes, just determined in alphabetical order.
  2. It has no impact. The driver loading relies on eudev to automatically identify the hardware id. When you don't have device A, even if driver A exists, it will not be loaded (not loading failure, but no loading process).
    As for the space, in fact, all the current drivers add up to less than 10M.
    When there is no conflict, disabling does not make much sense.

@wjz304 wjz304 added the documentation Improvements or additions to documentation label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants