amdgpu.ids: no such file or directory #1031
Comments
|
The same problem: |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I don't think this issue should get closed, it's still pretty much a problem. |
|
I'm also having the same issue.. My desktop PC is connected with an AMD RX570 GPU. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I have the same problem. I got AMD RX580 GPU
|
|
I have the same problem. When i run "anbox session-manager" i will just stall after message "/usr/share/libdrm/amdgpu.ids: No such file or directory", nothing will happen and I've left it there for minutes. Also, what is weird is that th efile is most certainly there. Bellow is output from "anbox system-info" |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I still get this issue on Fedora 32: |
|
I get this issue on Ubuntu 20.04 with RX470. kutualay@kutualay-ubuntu:~$ anbox system-info |
|
Такая же проблема, видеокарта amd rx 570 4g
|
|
@Lepidos and all, maybe one of you could try to add |
|
Isn't this just due to the snap confinement? The snap container wouldn't have access to anything outside of |
|
It appears the correct way to solve this issue is documented here: https://forum.snapcraft.io/t/amd-oss-graphics-drivers-missing-access-to-amdgpu-ids-file/12067/14 |
|
I have the same problem. I can't understand the instructions in the link by @mainmachine. |
|
One of these commands helped me No idea why the following worked the first time. (I think I forgot one important command) When i but when I it starts :) Hope some guys would be helped having hybrid graphics card |
Did adding layout: |
|
Anybody have a definite fix for the problem
didn't work, and
didn't work |
|
Adding this: and reinstalling unsquashed packet (snap remove / snap try) eliminates this error |
|
so a change in the snapcraft file? |
|
yep |
tried again and it didn't work |
could you open a PR with that change? |
|
I've still the BadAlloc |
|
this should be reopened since it's still an issue (even after 3 years!!) |
|
flatpak support is simply impossible, it is telling that the community has not done it in the 3 years since anbox's launch |
|
I've just tested the fix I proposed above by building a snap using a patch from this pull request and it is working for me. I made my changes, built the snap, ran the geeks-r-us playstore installer, installed minecraft and was able to see the menu, create a world and actually play it,m something I'd not been able to do before :D |
then at least make the snap run in classic mode |
this should be merged and added to the latest snap release |
it runs in devmode which is similar, contributions are welcome |
devmode is fine its just slightly more restriced classic mode but the pr linked in @mainmachine's comment should be merged ASAP |
|
@Etaash-mathamsetty merging on pull requests depends on the maintainers free time |
|
still not merged :( |
omg it finally works, THANKS |
|
I was prompted with the same error. For some reason, it got resolved without any setting any of the aforementioned environment variables, not reinstalling the amdgpu library (the project maintainers should put more effort into the error messages, as they are kind of ambiguous given that issues usually get multiple varying solutions). |
|
Please reopen it's still happening |
[...]
Run the anbox logs collection utility and attach the tar file.
anbox-system-diagnostics-2019-01-20.zip
Please paste the result of
anbox system-infobelow:Please describe your problem:
When I launch the Anbox Session Manager, it complains about no
amdgpu.idsand then just hangs for minutes and doesn't do anything. I checked the file (amdgpu.ids) and it actually does exist.What were you expecting?:
I expected the program to actually do something 😀
Additional info:
Although
anbox system-infodescribes my system asx86,uname -aaccurately givesx86_64:The text was updated successfully, but these errors were encountered: