Jump to content

DSDT IRQ assignment


e60
 Share

6 posts in this topic

Recommended Posts

Hey guys,

 

I am searching for a DSDT hack to specify an IRQ for a device. This is because after waking up from sleep my Sound and LAN are losing their asssigned adresses (asssigned adress is 0) and Snow Leopard won’t wake them up from sleep anymore. Could anyone point me to a way to edit the DSDT? The Board I’m using is a Gigabyte GA-E7AUM-DS2H and the latest DSDT is attached below.

 

Many thanks in advance!

Link to comment
Share on other sites

  • 3 weeks later...
  • 4 weeks later...

Hey guys,

 

somehow I'd totally forgotten about this thread because I didn't really expect anybody to answer anymore. :) So thanks a lot for doing so!

 

@LatinMcG

Which fixes do you exactly mean?

 

@buoo

I've tried to use the Guide you pointed me to, but unfortunately without any effect. :( After waking up from sleep, LAN and Audio are deactivated and I have to restart the system.

 

 

*Edit*

 

Here are two screenshots and the LSPCI results:

 

hdefz8vo.png

 

gigepknu.png

 

 

Audio before waking up from sleep:

 

00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
Subsystem: Giga-byte Technology Unknown device a102
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 23
Region 0: Memory at efff0000 (32-bit, non-prefetchable)
Capabilities: [44] Power Management version 2
	Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
	Status: D0 PME-Enable- DSel=0 DScale=0 PME-

 

 

Audio after waking up from sleep:

 

00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
Subsystem: Giga-byte Technology Unknown device a102
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 0
Capabilities: [44] Power Management version 2
	Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
	Status: D0 PME-Enable- DSel=0 DScale=0 PME-

 

 

Ethernet before waking up from sleep:

 

00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
Subsystem: Giga-byte Technology Unknown device e000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 23
Region 0: Memory at efffb000 (32-bit, non-prefetchable)
Region 1: I/O ports at fc00 [disabled]
Region 2: Memory at efffa000 (32-bit, non-prefetchable)
Region 3: Memory at efff9000 (32-bit, non-prefetchable)
Capabilities: [44] Power Management version 2
	Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
	Status: D0 PME-Enable+ DSel=0 DScale=0 PME-

 

 

Ethernet after waking up from sleep:

 

00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
Subsystem: Giga-byte Technology Unknown device e000
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 0
Region 1: I/O ports at <unassigned> [disabled]
Capabilities: [44] Power Management version 2
	Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
	Status: D0 PME-Enable- DSel=0 DScale=0 PME-

 

 

One thing is really confusing me. As you can see, the IORegistryExplorer shows that both Devices are using IRQ 17, even when the system is returning back from sleep. If I check these values with LSPCI, the results are totally different. As you can see both Devices seem to use IRQ 23 before, and IRQ 0 / unassigned ports after waking up from sleep. So how is that possible?

Link to comment
Share on other sites

One thing is really confusing me. As you can see, the IORegistryExplorer shows that both Devices are using IRQ 17, even when the system is returning back from sleep. If I check these values with LSPCI, the results are totally different. As you can see both Devices seem to use IRQ 23 before, and IRQ 0 / unassigned ports after waking up from sleep. So how is that possible?

hi e60,

 

same issue on a real mac - lspci count +6 for IRQ's. May be a bug? :P

Link to comment
Share on other sites

 Share

×
×
  • Create New...