-
Notifications
You must be signed in to change notification settings - Fork 126
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
fix: dvb extension as it was missing modules #575
base: main
Are you sure you want to change the base?
Conversation
Make sure all modules listed here are added: siderolabs/pkgs#1102 (comment) That's all the new modules that got added, that's the right way to pull in an extension providing modules |
you could also add |
Yes, but as this extension is related to cx23885, not all of those should be needed. The idea of mine was to provide bare minimal modules. Not every single built one. |
ahh then you'll have to split the pkgs PR, find the base list of dvb modules (there might be a lot of dependencies), then another diff when cx23885 is enabled |
e11f247
to
c808ebd
Compare
This is easier. |
Okay, so progress but it still seems to be unable to fully work, possibly related to the fact there's no /dev/dvb? I did try this in machine config, but did not see anywhere that it was applied:
|
cd8cecc
to
f0039e6
Compare
I found that we are actually missing a driver. |
It seems that some modules were missing and it has a dependency on v4l-uvc-drivers. Signed-off-by: Skyler Mäntysaari <sm+git@skym.fi>
Happy to report it works, even if the group on the devices is root. That should be video, but I don't know what's the best way to have it do that. I'm also not sure if we should let the blacklists stay, as I think a user might want udev to load the driver. |
@frezbo What do you think about if we should let udev handle the loading as the devices should have proper groups than just root applied to them..? |
it's not about udev, since talos doesn't have |
@@ -1,11 +1,188 @@ | |||
modules.order | |||
modules.alias |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need these, it'll be generated by depmod
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
modinfo would disagree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you have a reproducer, since depmod should re-create a final data based on the modules available
But it should still be able to use the numeric value for group? This udev rule seems to do nothing:
|
@dsseng do we disable group/user handling in udevd? |
I believe we do not explicitly disable anything. Yet what's the purpose of adding groups to these nodes? Video group is how it (was) managed on desktop, now I guess logind also overtook this (or about to do so). In Kubernetes environment groups would likely be annoying rather than useful as you give access with volumes when running pods |
If the device nodes don't get group properly set, I cannot run a workload unprivileged and just have it use the group and have access to the tuners. As the situation stands, tvheadend (my workload) cannot see (or to actually use) the devices due to permissions if not running privileged. Just mounting them as volumes will not be sufficient due to owner AND group being root aka uid 0 / gid 0. |
It seems that sound related modules are indeed required.