72 replies to this topic

[TimeWalker75a]

AppleHDA,
I don't get any popping unless I use headphones. There's definitely sound popping when you wear headphones and it can get you a headache pretty easily in a matter of minutes...but I've never heard it popping during shutdown actually.

[Fred30w]

TimeWalker75a, on 30 January 2013 - 04:36 PM, said:

AppleHDA,
I don't get any popping unless I use headphones. There's definitely sound popping when you wear headphones and it can get you a headache pretty easily in a matter of minutes...but I've never heard it popping during shutdown actually.

I only occasionally get popping when my soundcard is initialized after it sleeps. (Ex: Using soundless app for a few mins or putting the laptop to sleep.)  The popping is fairly quiet and doesn't occur during playback, only when my soundcard is turned on.  During shutdown, my sound card pops when it gets disabled.  By the way, does your sleep function hang occasionally too?  The only guarenteed function that works 100% for me is restart.

[TimeWalker75a]

Sleep works flawlessly here.

[Fred30w]

TimeWalker75a, on 30 January 2013 - 10:12 PM, said:

Sleep works flawlessly here.

For me, sleep has a higher chance of working.  Every now and then, I'll leave my laptop and come back to it stuck. (of course I lost my unsaved data and a forced reboot is necessary)  I'm not sure if there is a correlation, if I freshly log onto OS X and shutdown, it works.  If I wait and start Safari browsing or terminal work for extended periods, I get the shutdown hang.

[dmazar]

Hi there!

If you are still using Clover and EmuVariableUefi driver, please test new version. Details here: http://www.projectos...indpost&p=28411

[TimeWalker75a]

dmazar, on 02 April 2013 - 09:42 PM, said:

Hi there!

If you are still using Clover and EmuVariableUefi driver, please test new version. Details here: http://www.projectos...indpost&p=28411

Thank you for further improving this emulation for crippled machines. I will make sure to test the binaries from April 4th when I'm around my Dell.

[Fred30w]

dmazar, on 02 April 2013 - 09:42 PM, said:

Hi there!

If you are still using Clover and EmuVariableUefi driver, please test new version. Details here: http://www.projectos...indpost&p=28411

Hello dmazar!  I still do use Clover for OS X booting.  Unfortunately, I get a weird screen after the Apple boot screen finishes when updating Clover and your new EmuVariableUefi driver.  Here is a picture.  I have reverted back to an older EmuVariableUefi driver and Clover r904 with shutdown hangs.    20130405_195500.jpg   45.63K   13 downloads

Edited by Fred30w, 06 April 2013 - 01:50 AM.

[TimeWalker75a]

This is due to changes in DualLink injection for HD3000. I've reported this as of it first appeared but it seems its still there, so I'm now forced to disable graphics injector and set custom device-property strings.

[dmazar]

I really do now knot what changed since I did not have HD graphics before. I know that for ProBook I had to use GraphicsInjector=Yes  and DualLink=0 in Graphics section to get screen working. And currently I am using DSDT graphics injection, since Clover does not inject hda-gfx=onboard-1 or something similar.

[TimeWalker75a]

It used to inject AAPL00,DualLink=0x00000000 before the issue appeared, now it seems to inject AAPL01,DualLink with 0 by default or based on the value of the key set.

devprop_add_value(device, "AAPL01,DualLink", (UINT8 *)&DualLink, 1);
...
DualLink = gSettings.DualLink;

In both of these cases the screen is split either in two or in 4 parts on some laptops. Now, because the device id is the same for most laptops there is no universal solution, so
switch (gma_dev->device_id) doesn't really do justice here. Most laptops are fine with AAPL01 and if you'd have defined a special case in the switch for id of 0x0116 some people would end up complaining.

[Fred30w]

dmazar, on 06 April 2013 - 12:34 PM, said:

I really do now knot what changed since I did not have HD graphics before. I know that for ProBook I had to use GraphicsInjector=Yes  and DualLink=0 in Graphics section to get screen working. And currently I am using DSDT graphics injection, since Clover does not inject hda-gfx=onboard-1 or something similar.

Thx dmazar!  Using DualLink = 0 got the screen working great!  So far I like the new Clover and EmuVar, my laptop has a more reliable shutdown than ever (but not perfect).  I do have a question though, has CsmVideoDxe-64 been fixed for Intel HD 3000?  So far when I install that file, I get a blinking cursor at the top left.

Attached Files

•  boot.log.zip   5.75K   1 downloads

[dmazar]

Ok, glad to hear that new version of EmuVariable is working. The version you are using now is test version. New version from installer (once when you'll upgrade Clover) will have less debug output, but the same functionality.

Regarding shutdown, do you have so called "Asus shutdown fix" in DSDT? Like this: http://www.projectos...p?showtopic=904
Without it I have issues with shutdown.

Regarding HD 3000 native res - I can not get it working on my HP ProBook also in UEFI mode. The same symptoms as you have. If I remove the code for PCI Option rom, then ti gets to Clover GUI, but screen is unusable. It just does not work properly for some reason and I do not have time to dig deeper into it. Native res works fine when booting from Clover in BIOS mode.
You may try to use BiosVideo.efi driver from CloverEFI. The function is the same as CsmVideo, but communicates wit BIOS differently. Here: https://dl.dropboxus...r/BiosVideo.efi (remove ScmVideo and add BiosVideo). I have the same issue with this one as with CsmVideo - so, not working here.

[Fred30w]

dmazar, on 25 April 2013 - 10:37 AM, said:

Ok, glad to hear that new version of EmuVariable is working. The version you are using now is test version. New version from installer (once when you'll upgrade Clover) will have less debug output, but the same functionality.

Regarding shutdown, do you have so called "Asus shutdown fix" in DSDT? Like this: http://www.projectos...p?showtopic=904
Without it I have issues with shutdown.

Regarding HD 3000 native res - I can not get it working on my HP ProBook also in UEFI mode. The same symptoms as you have. If I remove the code for PCI Option rom, then ti gets to Clover GUI, but screen is unusable. It just does not work properly for some reason and I do not have time to dig deeper into it. Native res works fine when booting from Clover in BIOS mode.
You may try to use BiosVideo.efi driver from CloverEFI. The function is the same as CsmVideo, but communicates wit BIOS differently. Here: https://dl.dropboxus...r/BiosVideo.efi (remove ScmVideo and add BiosVideo). I have the same issue with this one as with CsmVideo - so, not working here.

Your new BiosVideo seems to work better, now when I boot into Clover GUI, I don't get a blinking cursor but the screen is still blank.  As for the shutdown problem, I believe my DSDT does have the ASUS shutdown fix, although I'm not sure if there is a difference between _PST and PST Methods, because this DSDT has both.

EDIT:  Dmazar, I think your BiosVideo.efi does something right because I enabled PatchVBios and this now in the logs.

0:188 0:000 Starting BiosVideo.efi
0:190 0:001 Using load options 'BiosVideo.efi '
0:190 0:000 BiosVideoDriverEntryPoint!
0:190 0:000 - driver needs connecting
0:197 0:007 2 drivers needs connecting ...
0:197 0:000 PlatformDriverOverrideProtocol not found. Installing ... Success
0:197 0:000 Video driver loaded: disconnect Successdisconnect Success
0:306 0:109 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:306 0:000 VideoBiosPatchNativeFromEdid:
0:306 0:000 Bios: VideoBiosPatchInit(LegacyRegion = Success) = Success
0:306 0:000 VideoBiosUnlock: unlocked
0:310 0:003 Patching: Patch BT_INTEL: Parse Edid: descriptor block 0 is timing descriptor (h_active: 1366, v_active: 768, h_sync_offset: 48, h_sync_width: 32, h_blanking: 212, v_blanking: 22, pixel_clock: 23424, v_sync_offset: 2, v_sync_width: 5)
0:310 0:000 patched 2 time(s)
0:310 0:000 VideoBiosLock: Success
0:338 0:027 BiosVideoDriverBindingStart!
0:338 0:000 BiosVideoCheckForVbe
0:350 0:012 Edid1+
0:350 0:000 found Detail Timing 1366x768
0:350 0:000 timing string @0xFE:SAMSUNG
L�AT
0:350 0:000 timing string @0xFE:LTN156AT24L01
0:362 0:012 Edid0+
0:362 0:000 found Detail Timing 1366x768
0:362 0:000 ... already present
0:362 0:000 timing string @0xFE:SAMSUNG
L�AT
0:362 0:000 timing string @0xFE:LTN156AT24L01
0:363 0:000 0 1366x768 attr=9B - ok, edid+, working, highest, pref=0
0:363 0:000 1 640x480 attr=9B - ok, edid-, 640x480, working
0:363 0:000 2 800x600 attr=9B - ok, edid-, 800x600, working
0:363 0:000 BV new mode: 0 1366x768
0:596 0:232 SetMode pref 0 (0) = Success
0:596 0:000 BiosVideoDriverBindingStart - END: Success!
0:597 0:000 BV new mode: 2 800x600
0:744 0:146 VGA Pci.Hdr.Command=0 - not enabled
0:744 0:000 VGA Pci.Hdr.Command=0 - not enabled
1:074 0:329 LoadDrivers() end

Clover GUI is still a blank screen, but now OS X only shows 800 * 600 on the top left of the screen.

 20130425_221713.jpg   78.24K   8 downloads

Once I adjust the resolution, it's normal again.  Do you know what causes this or a fix?

 20130425_221736.jpg   84.34K   9 downloads

Attached Files

•  boot.log.zip   6.48K   0 downloads
•  DSDT.aml.zip   17.43K   0 downloads