-
Notifications
You must be signed in to change notification settings - Fork 165
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
Wrong BusID in generated xorg.conf #471
Comments
I think I have the same issue on my machine. I didn't get as far a configuring optimus manager yet (I am trying to learn about how it all works before configuring power management) so no config file.
When I get optimus-manager to create the xorg config I can't start X. It crashes out as it can't find the BusID. If I manually edit the xorg config it produces, removing the first part of the ID ( Happy to debug if needed or provide any more information desired. |
Same here on a ASUS TUF DASH F15(2022), which is a laptop rated as "out of the box" for I dont know for sure what is the root cause of the Domain colum being added as a default behavior on I was unable to start X with Optimus, until I saw some
The behavior on Xorg config files was the same as reported by @hnsl and @JoshuaCrewe , and I've managed to create some overrides to FIX that extra zero after the
Pretty much I've manually replaced the Maybe a solution to this would be to generate this pci data using
Since for most motherboards the Domain on PCI is likely zero, that information could be ignored from Xorg configuration files. On my laptop, the only hardware that is in another domain are: CPU pci controller + NVME:
Another approach would be handling this first column appropriately with the format Setting BUSID in xorg.conf - Answer 2 In this case, Nvidia GPU which is being generated as I'll try later to use that format on my laptop as well and report back here |
Same issue on a Dell Precision 3571. Also for me cutting out the domain prefix fixed the issue. |
Maybe adding an option for the format in the |
Same problem |
Fixed at #551 |
Describe the bug
The xorg config is invalid on my system. To get optimus-manager to work I need to patch pci.py:
Removing the first part with [1:]
My system looks like this:
But my xorg.conf NEEDS to have all PCI formats like so:
Note that the initial "0000:" must be dropped, or xorg cannot find the corresponding BusID and will crash. This is true for all PCI devices on my system.
Why this is the case I have no idea. Maybe I'm using NVIDIA KMS instead of regular kernel KMS and they have different BusID format? I don't know.
System info
Please include :
5.15.10-arch1-1
GNOME
GDM
ACER Swift 5
1.4-3
/etc/optimus-manager/optimus-manager.conf
, if you made oneNone
The text was updated successfully, but these errors were encountered: