Jump to content

HP 6520s, 6720s, 6820s, 550 SL Install Package


BlackCH
 Share

1,448 posts in this topic

Recommended Posts

Hi guys BlackCH and yushir, please see this information for "No backlight after resume" problem:

 

- It seems to be a generalized problem about "DRIVERS", on OS X, linux and windows, by simplified google searching I get this: http://www.google.co.ve/search?hl=es&q...q=&gs_rfai=

 

- Slice said something about the graphics drivers from 10.6.1 (AppleIntelGMAX3100FB v1.6.2) HERE and HERE.

 

- smaver42 said related to AppleIntelIntegratedFramebuffer from 10.6.2 to solve it, courtesy: http://www.meklort.com/?p=167#comment-1853 And confirmed by TonyCr in this post: http://ipis-osx.wikidot.com/forum/t-231566.

 

Good Luck...

P.D. I will post my DSDT Update 1 soon jejeje, with some structural changes and some graphics hack- injection, but Im testing it now... Im considering this reply to yushir1 by Slice: http://www.projectosx.com/forum/index.php?...entry7046

Link to comment
Share on other sites

why has no one tried my method? like I said ive had brightness working since day 1!!!!! (unless the deviceID has something to do with it)

Agree with you!... but please, tell me one thing, because its relevant to know, if you have installed vanilla (untouched 10.6.3) IOPCIFamily.kext in S/L/E?

 

Additionally, maybe you want to try installing the driver AppleIntelGMAX3100FB v1.6.2 from 10.6.1... In theory have no backlight problems before and after sleep. Also, If not works, you have the possibility to installing the AppleIntelIntegratedFramebuffer from 10.6.2 for test.

 

In other hands, talking about mirror display possibility with 64 bit display drivers on 64 bit mode. I think, Its not good option, because fan control limitation, and the most important because 64 bit mode have nothing to do for sleep capability... its the information I know, and its confirmed at least in my case, because even screen sleep not worked.

 

Note just for record: I haven´t "absolutely any problem" with sleep before and after wake, because my display (monitor) backlight works 100% with stock drivers.

Link to comment
Share on other sites

why has no one tried my method? like I said ive had brightness working since day 1!!!!! (unless the deviceID has something to do with it)

 

I just tried. Doesnt seems to work here:

 

Installed the x3100FB kext from 10.5.1 combo update along with the string for GMA950 in my boot plist.

On reboot I got a 16 bit color desktop (very pixelated) and invisible mouse pointer. Maybe needs more testing but I really would like to find a more cleaner solution.

 

Notice Im not using any hacked kexts; only 3rd party extensions

 

 

@Yushir:

Y porque no mirar en la AppleBacklight.kext? El plist de esta kext tiene una lista que parecen ser diferentes displays con diferentes configuraciones para cada uno...

 

@juanerson

podrias subir tu ioreg (ioreg -lw0 en la terminal); quisiera comparar tu seccion del backlight

Link to comment
Share on other sites

@BlackCh

 

Diria que esa lista es para las pantallas externas que tienen backlight, como el AppleCinema display. Pero pensandolo bien quizas podamos introducir nuestros propios valores.

 

Por otro lado el problema que tenemos es el modo en que se baja el display, si te fijas en el DSDT de splice inyecta directamente esos valores de forma que OS X no los tenga que autodetectar, que parece ser donde falla.

 

Podriamos provar a inyectar nuestros propios valores en el DSDT de tal forma que funcionara como nosotros deseamos, pudiendo así (si llegara a funcionar) obtener un brightness más suave y bueno que con el brightness ACPI.

Link to comment
Share on other sites

@BlackCH. Te adjunto lo que me pediste.

 

@BlackCH y yushir, por si quieren intentarlo:

Adicionalmente dentro del .zip va un .dsl con el Method_DSM que estoy probando y utilizando en mi laptop, algunos relacionados directamente con el backlight ni siquiera los necesito en mi caso particular, pero los estoy implementando paso a paso (uno a uno), porque de golpe todos no van a funcionar. Hasta los momentos solamente utilizo los que resultan más simples (e inofensivos jejeje), pero creo que pueden ser efectivos para corregir el problema del backlight. Les recomiendo además de los que tengo habilitados, agregar (descomentar) como prueba:

 

- AAPL,BacklightRestore (no lo he probado aún).

EDITO: funcionó perfectamente aquí, ya lo he agregado a mi método DSM, parece dar mejores resultados o tal vez sea solo mi impresión, pero me gusta más el brillo con este valor cargado desde mi DSDT, de hecho veo algunas entradas adicionales desde el IORegisryExplorer en C099@2. Sinceramente estoy reconsiderando que tal vez si sean necesarios estos valores.

 

- AAPL01,DualLink (este lo necesitas si tu pantalla es 1440x900 como la de Slice). En 1280x800 no funciona.

 

EDITO 1: El siguiente valor tomado del IOReg macbook3,1 también funcionó aquí:

"AAPL01,BacklightIntensity",

Buffer (0x04)

{

0x2D, 0x00, 0x00, 0x00 //probablemente 0x56 (Slice) también funcione; probé 0x50 y no funcionó en mi laptop.

},

 

Opcionalmente, tal vez también quieran probar:

- AAPL,NumDisplays

- AAPL,NumFramebuffers

- AAPL00,blackscreen-preferences

- AAPL01,blackscreen-preferences

- Y los que dicen "Slice adjustments". Especialmente AAPL01,InverterFrequency.

 

Notas:

1) Por favor, para que la pantalla no te haga cosas espeluznantes, inicialmente prueba sin los valores opcionales.

 

2) No sé si es realmente necesario, pero algo que me ha resultado útil en los casos que he perdido la pantalla, y lo cual ya hago de manera regular, es borrar los perfiles en /Librería/ColorSync/Profiles/Displays entre prueba y prueba. Eso elimina los perfiles malos... y el bueno se recrea en el próximo inicio del sistema.

 

3) Es necesario apagar la laptop por varios minutos, yo la dejo 10 minutos entre prueba y prueba. De otra manera, no serán confiables las pruebas, ya que por experiencia propia en mi caso estuve todo un día inyectando y probando de todo y me lo tomaba en cada reinicio. Pero a la mañana siguiente cuando me disponía a desayunar, enciendo la laptop y me llevo la sorpresa (nada grata por supuesto), en vez de mostrarme la pantalla de login... OMG! freddy kruger rasgó la pantalla y la mando al carajo jajaja... es decir, la combinación de valores no funcionó y tuve que volver a empezar desde cero.

 

4) También va mi IORegistry tomado con los valores inyectados al DSDT, para comprobación de la gráfica (sección C099@2). Igualmente adjunto el MacBook3,1_original.ioreg que fue de donde obtuve los valores para inyectar al DSDT... y como complemento revisé la respuesta de Slice a yushir AQUI.

 

Espero que sea útil. Saludos.

Archivo_comprimido.zip

Link to comment
Share on other sites

I blackch. I want to restore a backup of time machine from the install Dvd... i've tried your boot cd, but i've a blocked screen at this point: warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.

 

Any suggestions? Or an alternative method to restore my backup

Link to comment
Share on other sites

@BlackCH. Te adjunto lo que me pediste.

Espero que sea útil. Saludos.

Gracias!

 

 

 

I blackch. I want to restore a backup of time machine from the install Dvd... i've tried your boot cd, but i've a blocked screen at this point: warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.

Any suggestions? Or an alternative method to restore my backup

 

One thing before: Please dont quote the first post like that (the whole post), It makes the topic difficult to read. Theres no need to do that. Can you please edit your post and clean that up? Thanks

 

As for your question; the boot cd its meant for the 10.6 retail disc only, other install discs versions would probably not work with it.

Which retail disc are you using?

 

An alternative method to get what you want done will be to dump the install dvd content onto an external HD, then install chameleon and kexts to that HD, then boot from it

Link to comment
Share on other sites

Sorry BlackCH... i've solved with another boot cd, with no-sata and with cpus=1

My disc is a retail version of Snow Leopard (10.6)

 

Thats very strange... I will do some doublecheck on the files I posted to see if I mistake some of them as it should work without the need of disabling SATA or CPU cores...

Thanks for the feedback anyway, and for editing your post too (I didnt want to sound rude)

Can you point me to the boot CD you used?

Link to comment
Share on other sites

Sorry BlackCH... i've solved with another boot cd, with no-sata and with cpus=1

My disc is a retail version of Snow Leopard (10.6)

 

I think the problem might be related with the GMAx3100. Yours has a different id.... (but still should work in vesa mode with my boot CD, so IDK).

Link to comment
Share on other sites

Report: Does not work on 6520s (CPU Core2Duo T7520 2.0Ghz)

It seems to improperly stop (not hang, not panic) during first boot, thus user cannot go to the Mac Installation Welcome Screen.

Need to know full specs (GMAx3100 dev ID, wifi card model, etc). Please make a signature

I've tested on my HP 6720s only, but Im sure we can make it work on yours. PM me your full specs

 

In the meantime you can try this:

 

boot with the flag

-s

 

when prompt appears type (press enter after each line):

/sbin/fsck -fy (wait until finishes)

/sbin/mount -uw /

sudo mkdir /Extra/GMA

sudo cp -R /System/Library/Extensions/AppleIntelGMAX3100* /Extra/GMA

sudo rm -R /System/Library/Extensions/AppleIntelGMAX3100*

exit

 

see if that solves the problem. Let me know

 

 

i get a kernel panic after instaling dsdt, extra, extensions and sleepwatcher on my hp dv 6580

i try cpus=1

cpus=2

-x

arch=i386

but no result

Off course; the packages are not designed for HP Pavillon DV6580,

Link to comment
Share on other sites

i get a kernel panic after instaling dsdt, extra, extensions and sleepwatcher on my hp dv 6580

 

i try cpus=1

cpus=2

-x

arch=i386

but no result

 

I think this topic is meant for HP 6520s, Hp 6720s, HP 6820s and HP 550.

 

Need to know full specs (GMAx3100 dev ID, wifi card model, etc). Please make a signature

I've tested on my HP 6720s only, but Im sure we can make it work on yours. PM me your full specs

 

In the meantime you can try this:

 

boot with the flag

-s

 

when prompt appears type (press enter after each line):

/sbin/fsck -fy (wait until finishes)

/sbin/mount -uw /

sudo mkdir /Extra/GMA

sudo cp -R /System/Library/Extensions/AppleIntelGMAX3100* /Extra/GMA

sudo rm -R /System/Library/Extensions/AppleIntelGMAX3100*

exit

 

see if that solves the problem. Let me know

 

Thanks,

 

/sbin/fsck -fy returns "...appears to be OK"

/sbin/mount -uw / returns "Permission denied"

sudo mkdir /Extra/GMA returns "sudo: Command not found"

Link to comment
Share on other sites

Thanks,

/sbin/fsck -fy returns "...appears to be OK"

/sbin/mount -uw / returns "Permission denied"

sudo mkdir /Extra/GMA returns "sudo: Command not found"

 

make it like this:

/sbin/fsck -fy (wait until finishes)

/sbin/mount -uw /

mkdir /Extra/GMA

cp -R /System/Library/Extensions/AppleIntelGMAX3100* /Extra/GMA

rm -R /System/Library/Extensions/AppleIntelGMAX3100*

 

 

Double check the second line (it must be entered exactly- theres a space between "-uw" and "/"). If you dont get pass this line without errors the following lines wont work.

If it doesnt give you the permissions to do so then boot again the retail DVD and use Disk Utility to fix disk permissions, then try again this.

 

If still doesnt work boot with

-x

 

then remove all the AppleIntelGMAX3100* .kexts you found in /System/Library/Extensions/ (make a backup of them)

 

next re-boot with

-f

Link to comment
Share on other sites

@BlackCH, Hi friend... I don´t know which device is card reader in DSDT, but I think the "Sleep doesnt work when a card is plugged onto the card reader slot (instant wake-up)" problem can be fixed by commenting this part of the specific code device, for example:

/*

Name (_PRW, Package (0x02)

{

0x0A,

0x05

})

*/

 

If does not work, try commenting the Method (_PSW, 1, NotSerialized).

Note: Its just for sleep purposes, I meant "instant wake problems"... and maybe this modification produces indirect (secondary) effect to the device.

Link to comment
Share on other sites

@BlackCH, Hi friend... I don´t know which device is card reader in DSDT

Hi juanerson, thanks for the suggestion. I havent look into it yet (I dont use the card reader so much), but I notice the card reader plugs into the EHCI device (if you look at the IOReg tree when a card is inserted) so I dont know if it is defined in the DSDT because it behaves like an external USB device.

By the way, I was trying to use the VoodooSDHC.kext (yushir mentioned it) but I cannot get it to load. Does it need any plist edit?

Link to comment
Share on other sites

Hi juanerson, thanks for the suggestion...

Ok, then you can try commenting the entry Name (_PRW, Package (0x02) for both EHCI devices, preventing wake up from usb 2.0 devices. If not works add this to the EHC1 and EHC2, in the Method (_DSM, 4, NotSerialized) after "device-id":

 

"AAPL,clock-id",

Buffer (One)

{

0x01 /*for EHC2 is 0x02*/

},

 

"AAPL,current-available",

0x04B0,

"AAPL,current-extra",

0x02BC,

"AAPL,current-in-sleep",

0x03E8,

Buffer (One)

{

0x00

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

Link to comment
Share on other sites

make it like this:

/sbin/fsck -fy (wait until finishes)

/sbin/mount -uw /

mkdir /Extra/GMA

cp -R /System/Library/Extensions/AppleIntelGMAX3100* /Extra/GMA

rm -R /System/Library/Extensions/AppleIntelGMAX3100*

 

 

Double check the second line (it must be entered exactly- theres a space between "-uw" and "/"). If you dont get pass this line without errors the following lines wont work.

If it doesnt give you the permissions to do so then boot again the retail DVD and use Disk Utility to fix disk permissions, then try again this.

 

If still doesnt work boot with

-x

 

then remove all the AppleIntelGMAX3100* .kexts you found in /System/Library/Extensions/ (make a backup of them)

 

next re-boot with

-f

 

Thanks to your before suggestion, I take a look at my Graphic card device ID and it is indeed not 2a02 but 2a12. Another problem, not sure, is that 6720s use motherboard GL950 while 6520s use GM950.

 

I tried your method (to remove Gmx3100 kext) unsuccessfully, but I managed to boot with http://www.mediafire.com/?dzlwmnoyiyn and install. After installation, I would try to install your post-installation with GM X3100 removed and report.

 

PS: the boot before is meant to be used only for installation, as it leaks of USB, bluetooth, cardreader, Graphic, Sound; Lan and WLan works

Link to comment
Share on other sites

Thanks to your before suggestion, I take a look at my Graphic card device ID and it is indeed not 2a02 but 2a12. Another problem, not sure, is that 6720s use motherboard GL950 while 6520s use GM950.

 

I tried your method (to remove Gmx3100 kext) unsuccessfully, but I managed to boot with http://www.mediafire.com/?dzlwmnoyiyn and install. After installation, I would try to install your post-installation with GM X3100 removed and report.

 

PS: the boot before is meant to be used only for installation, as it leaks of USB, bluetooth, cardreader, Graphic, Sound; Lan and WLan works

 

Report: still fail after remove AppleGMAX3100* kext :((

Link to comment
Share on other sites

Ok, then you can try commenting the entry Name (_PRW, Package (0x02) for both EHCI devices, preventing wake up from usb 2.0 devices. If not works add this to the EHC1 and EHC2, in the Method (_DSM, 4, NotSerialized) after "device-id":

That worked like a charm! Thanks again my friend!

 

 

Report: still fail after remove AppleGMAX3100* kext ;)(

Does the problem happens only after you install the packages I provided?

After deleting the kexts you need to boot with -f flag

Link to comment
Share on other sites

That worked like a charm! Thanks again my friend!

 

 

 

Does the problem happens only after you install the packages I provided?

After deleting the kexts you need to boot with -f flag

 

Report: it seems the problem comes from the DSDT. At first, I installed (another) package for booting (using nullcpupowermanagerment.kext without DSDT) and it worked, of course, without USB. But later, I only copyed DSDT, and then it sucked. The last thing I could read was something about fakesmc cannot find something.

 

My strategy, now, is to reinstall (again!!!) SL, boot without DSDT, use DSDTse to extract. I think I may upload here so that you all can compare with original DSDT extracted from 6720s, as well as help me to patch some cool stuffs into this one.

 

Thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...