Contribute
Register

HD 5500 BDWFramebuffer not loading

Status
Not open for further replies.

Attachments

  • CLOVER 2.zip
    2.9 MB · Views: 53
  • RehabMan.zip
    27.2 KB · Views: 51
  • Wesley’s MacBook Air.zip
    436.9 KB · Views: 57
  • IMG_2421.JPG
    IMG_2421.JPG
    176.2 KB · Views: 56
wesleycguirra said:
Sorry here's the files.
Click to expand...

At what stage of the install are you at?
Did you already install, then run ./install_downloads.sh/etc?
Did you follow my guide from scratch for that? Or did you do something else?
Why is there a verbose boot photo and an ioreg.
Verbose boot photo in "problem reporting" files implies you can not boot. The ioreg implies you can.

Your ioreg shows VoodooHDA.kext installed.
My guide does not use VoodooHDA.

Your Clover bootlog shows ACPI files that are not called for by the guide:
28:426 0:000 DSDT found in Clover volume OEM folder: EFI\CLOVER\ACPI\patched\DSDT.aml
28:459 0:000 Inserting ssdt.aml from EFI\CLOVER\ACPI\patched ... Success
28:470 0:011 Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success

The ioreg you provided was not captured after booting with the EFI/Clover you attached.

Clearly, you didn't follow the guide.


Your EFI/Clover/kexts/Other is not per guide.
Please read the guide carefully. Adding more kexts than recommended is not a good idea. You have a bunch of garbage there (USB WiFi kext), and kexts that are not appropriate for Sierra (IntelBacklight.kext).

Note: USB WiFi is not recommended. Read guide for correct WiFi hardware to purchase/install.

And your Clover version is far too old.
Use latest Clover from sourceforge or my Clover fork on bitbucket.

Make sure you set DVMT-prealloc correctly in BIOS (must be 64mb).

My recommendation: Start over from scratch and follow the guide as written.
 
RehabMan said:
At what stage of the install are you at?
Did you already install, then run ./install_downloads.sh/etc?
Did you follow my guide from scratch for that? Or did you do something else?
Why is there a verbose boot photo and an ioreg.
Verbose boot photo in "problem reporting" files implies you can not boot. The ioreg implies you can.

Your ioreg shows VoodooHDA.kext installed.
My guide does not use VoodooHDA.
Clearly, you didn't follow the guide.


Your EFI/Clover/kexts/Other is not per guide.
Please read the guide carefully. Adding more kexts than recommended is not a good idea. You have a bunch of garbage there (USB WiFi kext), and kexts that are not appropriate for Sierra (IntelBacklight.kext).

Note: USB WiFi is not recommended. Read guide for correct WiFi hardware to purchase/install.

And your Clover version is far too old.
Use latest Clover from sourceforge or my Clover fork on bitbucket.

Make sure you set DVMT-prealloc correctly in BIOS (must be 64mb).
Click to expand...
I can boot if I change the ig-platform-id, I followed the guide to solve the problem with BDWFramebuffer as you can see in the #1 post the video isn't with acceleration (3mb).
 
wesleycguirra said:
I can boot if I change the ig-platform-id, I followed the guide to solve the problem with BDWFramebuffer as you can see in the #1 post the video isn't with acceleration (3mb).
Click to expand...

I repeat...

Clearly, you didn't follow the guide.
My recommendation: Start over from scratch and follow the guide as written.

Also, one more thing I see from ioreg.
You have no Intel MEI device on the PCI bus. It is required.
Usually it is due to one or more:
- motherboard defect
- CPU is ES/QS
- bad BIOS flash
- people disabling the IMEI on purpose
- etc/etc
 
fivos1996 said:
Hm... I'm thinking the same about my i3 5005U. But I have an IMEI device on the PCI bus.
Click to expand...

I suppose a non-working/not up to spec IMEI might cause the same issue.
You think your CPU is ES/QS?
 
RehabMan said:
I suppose a non-working/not up to spec IMEI might cause the same issue.
You think your CPU is ES/QS?
Click to expand...
I'm not really sure. My laptop is manufactured early 2016. The i3 5005U came out in early 2015. The problem on this thread doesn't show any random panic like mine does.
 
fivos1996 said:
I'm not really sure. My laptop is manufactured early 2016. The i3 5005U came out in early 2015. The problem on this thread doesn't show any random panic like mine does.
Click to expand...

I think they are different problems.
This case clearly shows no IMEI at all.
 
fivos1996 said:
I'm not really sure. My laptop is manufactured early 2016. The i3 5005U came out in early 2015. The problem on this thread doesn't show any random panic like mine does.
Click to expand...

HP gone cheap on the motherboard. Its got a Soldiered CPU. Cant see how it has a ES/QS CPU unless your laptop is a (Sample Laptop) Verify that IMEI shows up under lspci in Linux.

i3 5005U is a (FCBG) chip which means (Soldiered).
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top