HD5500 HDMI not working and other problems.

[vatsa131]

I am getting no xhc device regardless of me having 1 usb 3.0 port.
In attached ioreg the optical mouse at hp11 is a usb 3.0 port.

How can I know address of my xhc controller to be added in ssdt? Or how can I enable it?

 

[RehabMan]

I am getting no xhc device regardless of me having 1 usb 3.0 port.
In attached ioreg the optical mouse at hp11 is a usb 3.0 port.

How can I know address of my xhc controller to be added in ssdt? Or how can I enable it?

Check BIOS settings. Maybe you disabled it.
From the PCI list that Clover sees, it is disabled or defective...

0:100  0:000  === [ GetDevices ] ========================================
0:100  0:000  PCI (00|00:00.00) : 8086 1604 class=060000
0:100  0:000  PCI (00|00:02.00) : 8086 1616 class=030000
0:100  0:000   - GFX: Model=Intel HD Graphics 5500 (Intel)
0:100  0:000  PCI (00|00:03.00) : 8086 160C class=040300
0:100  0:000  PCI (00|00:16.00) : 8086 9CBA class=078000
0:100  0:000  PCI (00|00:16.01) : FFFF FFFF class=FFFFFF
0:100  0:000  PCI (00|00:1B.00) : 8086 9CA0 class=040300
0:100  0:000  PCI (00|00:1C.00) : 8086 9C90 class=060400
0:100  0:000  PCI (00|00:1C.02) : 8086 9C94 class=060400
0:100  0:000  PCI (00|06:00.00) : 14E4 43B1 class=028000
0:100  0:000   - WIFI: Vendor=Broadcom
0:100  0:000  PCI (00|00:1C.03) : 8086 9C96 class=060400
0:100  0:000  PCI (00|07:00.00) : 10EC 8136 class=020000
0:100  0:000   - LAN: 0 Vendor=Realtek
0:100  0:000  PCI (00|00:1C.04) : 8086 9C98 class=060400
0:100  0:000  PCI (00|00:1D.00) : 8086 9CA6 class=0C0320
0:100  0:000  PCI (00|00:1F.00) : 8086 9CC3 class=060100
0:100  0:000  PCI (00|00:1F.02) : 8086 9C83 class=010601
0:100  0:000  PCI (00|00:1F.03) : 8086 9CA2 class=0C0500

No PCI device at 00:14.xx... (which is the address for XHC).

If that is not it, attach output from 'lspci -nn' in Linux Terminal.

 

[vatsa131]

No, it is enabled.
Currently in windows it works pretty well.

 

[RehabMan]

No, it is enabled.
Currently in windows it works pretty well.

You forgot:

"If that is not it, attach output from 'lspci -nn' in Linux Terminal."

 

[vatsa131]

So, finally I did manage to get xhc working.

Strangely my internal display is not being detect since last night. Also bluetooth audio os stuttering and eventually headphone keep getting disconnected.

Also, I am getting BCM20702A0 usb 2.0 bus showing maximum throughput of 12mb/sec.(I did manage to get more than that), do I still want to router everything on xhc?

 

[RehabMan]

So, finally I did manage to get xhc working.

Strangely my internal display is not being detect since last night. Also bluetooth audio os stuttering and eventually headphone keep getting disconnected.

Also, I am getting BCM20702A0 usb 2.0 bus showing maximum throughput of 12mb/sec.(I did manage to get more than that), do I still want to router everything on xhc?

Your files in ACPI/origin are too old (from Apr 13).
Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

FYI: Speed stat on your BT controller is normal/expected.

Your ioreg shows USB not implemented correctly. Also CPU PM not implemented. Also google chrome is hooking your USB ports (read FAQ).

 

[vatsa131]

Also CPU PM not implemented.

As you may see, I have added ssdt for pm.

Also google chrome is hooking your USB ports

Disabled it.

Your files in ACPI/origin are too old (from Apr 13).
Read FAQ, "Problem Reporting"

Updated them.

Still no internal display, also battery status doesn't seem to be working now. Everything was working last night and I have not made any changes since then.

 

[RehabMan]

As you may see, I have added ssdt for pm.


Disabled it.


Updated them.

Still no internal display, also battery status doesn't seem to be working now. Everything was working last night and I have not made any changes since then.

Your ioreg shows CPU PM not implemented.
You did not provide complete "Problem Reporting" files.

 

[vatsa131]

kextstat

 

[vatsa131]

What is wrong with my cpu PM?Also, how can I solve it?

Still unable to solve internal display and battery indicator.