Jump to content

display goes off when AppleIntelFramebufferCapri is loaded


  • Please log in to reply
89 replies to this topic

#81
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male
well this episode still goes on, the other board in this chassis works fine as far as display goes but the two aren't completely interchangeable and I lose most peripherals. but it proves the panel itself is fine. I just tried the latest 10.8.3 beta and no change, it seems the framebuffercapri driver hasn't changed since initial release.

#82
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male
also, the newest iMacs use the AAPL,ig-platform-id 01620006 and 01620007 respectively. which figures, since they dont actually use the HD4000 thats present in the CPUs used.

#83
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male
...i kinda solved the X86PlatformPlugin problem.....kinda in that i solved getting it to load, but not solved why it didnt in the first place

http://www.insanelym...in-not-loading/

#84
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male
I guess this thread is dead in the water, but I finally worked out what's going on!
my system has two display outputs, internal displayport and external VGA.
the system detects the displays and allocates the display pipe, but its using the wrong pipe. i was able to test this by hacking the VGA enabled and running that by itself, which resulted in garbled display in the built in screen, the OS reports the VGA monitor details, but that's not where it sends the picture.
right now port 04 06 uses AAPL,DisplayPipe 00 00 00 00, but it should use AAPL,DisplayPipe 01 00 00 00, and vice versa for 06 02.
unfortunately, I don't (yet!) know how to change this, but that's the problem, and that should solve it.
I may well have to post on other threads to get this answer, but i wanted to update this one and thank everyone again who's contributed thus far :)

#85
kpkp

kpkp

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 433 posts

I guess this thread is dead in the water, but I finally worked out what's going on!
my system has two display outputs, internal displayport and external VGA.
the system detects the displays and allocates the display pipe, but its using the wrong pipe. i was able to test this by hacking the VGA enabled and running that by itself, which resulted in garbled display in the built in screen, the OS reports the VGA monitor details, but that's not where it sends the picture.

I have exactly the same issue on my notebook using i5-3220M, the internal display and displayport work fine, but when i connect the VGA at boot, i get exactly the results you mentioned. If I find anything usefull to solve this problem will share here, please do the same, thx.

Thats what I currently use:
AAPL,ig-platform-id: 01660003, Stolen RAM for FB: 64MB, Pipes: 2, Ports: 4, FBMem: 2
@0, 05 03 00 00 02 00 00 00 30 02 00 00 // (LVDS)
@1, 04 06 00 00 00 08 00 00 06 00 00 00 // (HDMI) - DETECTED
@2, 06 02 00 00 01 00 00 00 30 00 00 00 // (VGA)
@3, 04 06 00 00 00 04 00 00 81 00 00 00 // (DisplayPort)


#86
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male

I have exactly the same issue on my notebook using i5-3220M, the internal display and displayport work fine, but when i connect the VGA at boot, i get exactly the results you mentioned. If I find anything usefull to solve this problem will share here, please do the same, thx.

Thats what I currently use:

AAPL,ig-platform-id: 01660003, Stolen RAM for FB: 64MB, Pipes: 2, Ports: 4, FBMem: 2
@0, 05 03 00 00 02 00 00 00 30 02 00 00 // (LVDS)
@1, 04 06 00 00 00 08 00 00 06 00 00 00 // (HDMI) - DETECTED
@2, 06 02 00 00 01 00 00 00 30 00 00 00 // (VGA)
@3, 04 06 00 00 00 04 00 00 81 00 00 00 // (DisplayPort)


does anything on my blog post help you out?

http://rr7blog.wordpress.com

#87
kpkp

kpkp

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 433 posts

does anything on my blog post help you out?

http://rr7blog.wordpress.com

There is a lot of good information (some new, some I knew), but idk how to apply it in a way to solve my problem (if its even solvable this way).
Just now I tried to connect both external monitors (vga and display port) and all 3 displays get detected (vga, dp, internal), the problem is that the VGA stays blank and i can see the artefacts and even more, i can see my XGA vga display getting pushed on my dp fullHD display. It appears like the driver is trying to push both signals trough DP ignoring the VGA output (could be a hardware limitation since i cant use all 3 displays at the same time in windows neither). But when i connect only the VGA the results dont change.

Its not compleatly impossible since here:
http://www.insanelymac.com/forum/topic/283038-zenbook-prime-fixes-mods-tweaks-etc/
they got it to work, idk what/if they have any issues, but idk it coule be hardware dependent.

#88
Juan Jullian

Juan Jullian

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
After answering some really really funny quizes i can post!

Well, with the appreciated help of kpkp and rehabman from tonymac, i need to know some things to get properly working mi i5 3320m hd4000 gpu.

i have a 6470b probook hp laptop. two users have the same machine. they uses the 08006601 aapl-id with a consequent dsdt patch and their capriFB patch (https://www.dropbox....rCapri.kext.zip)

but when i boot normally, i get a kernel panic. I think is very rare because only appear the image "you need to restart" without a log "breaking" the gray background. When i boot with -x its boot fine, lvds and dp-to-vga works great, and console didn't show anything related to a panic. So i thinks is not a real kernel panic.

When i try other caprifb kext, it works, but only detects the internal display. I think that "kernel panic" is related only with caprifb

So i think i need to patch my own caprifb because i think my machine is sightly different of the other's.

Correct me if im wrong: i need to know my machine's native port configuration and then paste that information in the capri binary, with his structure?

#89
Juan Jullian

Juan Jullian

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts

After answering some really really funny quizes i can post!

Well, with the appreciated help of kpkp and rehabman from tonymac, i need to know some things to get properly working mi i5 3320m hd4000 gpu.

i have a 6470b probook hp laptop. two users have the same machine. they uses the 08006601 aapl-id with a consequent dsdt patch and their capriFB patch (https://www.dropbox....rCapri.kext.zip)

but when i boot normally, i get a kernel panic. I think is very rare because only appear the image "you need to restart" without a log "breaking" the gray background. When i boot with -x its boot fine, lvds and dp-to-vga works great, and console didn't show anything related to a panic. So i thinks is not a real kernel panic.

When i try other caprifb kext, it works, but only detects the internal display. I think that "kernel panic" is related only with caprifb

So i think i need to patch my own caprifb because i think my machine is sightly different of the other's.

Correct me if im wrong: i need to know my machine's native port configuration and then paste that information in the capri binary, with his structure?


Ok, all resolved. i take other capri kext that only worked with internal display and i added the 08006601 ports cfg from shpokas01 (tonymac) kext.

Also, i've found that the binary from shpokas01 is listed as a file (blank sheet icon), while the other is listed as a binary (gray terminal icon), its related with a problem?

Thanks all people

#90
rr7

rr7

    InsanelyMac Protégé

  • Members
  • PipPip
  • 81 posts
  • Gender:Male
well, having tested the newest Ubuntu release, which no longer has the same display issues on my AIO, i'm guessing my issue is nothing more than a bug in the apple ivy bridge frame buffer driver, that simply never affects any real apple hardware, so its never been noted, nor will it probably ever need to be fixed.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy