Summary: | sys-kernel/gentoo-kernel: Error (installing?) nouveau firmware to /lib/firmware/nvidia | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mirko Guenther <renegart> |
Component: | Current packages | Assignee: | Distribution Kernel Project <dist-kernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jstein, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
Kernel Config firmware file permissions dump whole firmware directory |
Description
Mirko Guenther
2023-01-22 10:59:11 UTC
Created attachment 848985 [details]
Build log
Hmm, that's interesting. I presume you're using the generic config and not a customized kernel config? Our -bin builds are done on top of installation image without linux-firmware installed, so I guess this is not strictly necessary. However, this also seems to indicate a permission problem. FWICS all files installed by linux-firmware are world-readable. Not sure if this is necessarily the best approach, though. Oh wait, you are using a custom config. Please include your config then. Created attachment 849079 [details]
Kernel Config
This config work with 'gentoo-sources'
'sys-kernel/linux-firmware' is installed on my system. What are the directory permissions all the way down to: /lib/firmware/nvidia/gp108/sec2/desc.bin ? Created attachment 849357 [details]
firmware file permissions
I've dumped the whole tree of 'nvidia' firmware installed by 'sys-kernel/linux-firmware'
(In reply to Mirko Guenther from comment #7) > Created attachment 849357 [details] > firmware file permissions > > I've dumped the whole tree of 'nvidia' firmware installed by > 'sys-kernel/linux-firmware' I don't see anything obviously wrong here, though portage:portage ownership looks suspicious. Please list the parent directories as well. Created attachment 849888 [details]
dump whole firmware directory
I've attached the whole firmware directory
[drwx------ root root ] firmware That's your problem. If unprivileged users can't access firmware files, you can't expect userpriv builds to work. |