mirror of
https://github.com/AskDavis/Getting-Started-With-ACPI.git
synced 2025-12-31 20:55:58 -08:00
Fix Lint
This commit is contained in:
@@ -8,12 +8,15 @@
|
||||
## Finding the ACPI path
|
||||
|
||||
### On MacOS
|
||||
|
||||
Unfortunately there is no guidance for this yet. Try on Linux or Windows.
|
||||
|
||||
### On Linux
|
||||
|
||||
These steps work on Ubuntu and may work on other distros. If not then try the procedure for Windows.
|
||||
Use the `lspci` command to get your display adapters PCI identification number.
|
||||
The output here will be different on your system!
|
||||
|
||||
```
|
||||
# lspci -D
|
||||
0000:00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
|
||||
@@ -23,16 +26,19 @@ The output here will be different on your system!
|
||||
0000:00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
|
||||
0000:00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
|
||||
```
|
||||
|
||||
Search the output for an entry that looks like your display adapter. E.g: In this example we have `VGA compatible controller` with PCI number `0000:00:02.0`. The format of this number is `domain:bus:device:function`.
|
||||
|
||||
Now use this command from a Terminal to find the ACPI path for your display adapter
|
||||
`# cat /sys/class/pci_bus/<domain:bus>/device/<domain:bus:device:function>/firmware_node/path`
|
||||
|
||||
For example
|
||||
|
||||
```
|
||||
# cat /sys/class/pci_bus/0000:00/device/0000:00:02.0/firmware_node/path
|
||||
\_SB_.PCI0.GFX0 <-- The ACPI path
|
||||
```
|
||||
|
||||
Further details [at this link.](https://unix.stackexchange.com/questions/653143/how-to-get-bios-device-name-from-linux-same-as-windows-device-manager-format)
|
||||
|
||||
### On Windows
|
||||
|
||||
Reference in New Issue
Block a user