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

[BlackCH]

For latest iasl you need to fix memory length in lines 788, 795 in the dsdt u include in first post. The correct memory lengths are: a) line 788 0xFEE00000 and b.) line 795 0x11FF000.

 

I wonder if "newly added sbus support" section in lines 895 and following are useful in my 6710b.

 

Which DSDT version? there are a few in the 1st post. I cannot find it in the last DSDT posted.

Maybe you can post the sections that needs modifications, so we can apply them to the new files

 

About SMBUS, I dont know if we really need that. Theres no kext loaded on macbook's IOReg, but the device is present on the IOReg tree

[Einstein_ein]

Which DSDT version? there are a few in the 1st post. I cannot find it in the last DSDT posted.

Maybe you can post the sections that needs modifications, so we can apply them to the new files

 

About SMBUS, I dont know if we really need that. Theres no kext loaded on macbook's IOReg, but the device is present on the IOReg tree

 

Update 12-11-2009

New dsdt:

Attached File HP6720s_dsdt_3.1.dsl.zip ( 26.24K ) Number of downloads: 613

 

Isn't this the latest?

Changes

a) line 788 from 0x00000000, // Length

0xFEE00000, // Length, fixed as 0xFEDFFFFF - 0x00000000 + 1 = 0xFEE00000

b.) line 795 from 0x011FEFFF, // Length

0x11FF000, // Length, fixed as 0xFFFFFFFF - 0xFEE01000 + 1 = 0x11FF000

 

If you use latest iasl (v.2010-04-28) u get errors in compilation. To cpmpile it correctly you need to fix memory lengths according to the above rule i.e. Correct length = Translated into hex(Range Maximum - Range minimum + 1).

Hope that helped

[BlackCH]

Update 12-11-2009

New dsdt:

Attached File HP6720s_dsdt_3.1.dsl.zip ( 26.24K ) Number of downloads: 613

 

Isn't this the latest?

 

Theres a newer DSDT in the first post. Please check if the problem exist with that one

Thanks for the info anyway. I will look into it

 

EDIT:

 

DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
				0x00000000,		 // Granularity
				0x00000000,		 // Range Minimum
				0xFEDFFFFF,		 // Range Maximum
				0x00000000,		 // Translation Offset
				0xFEE00000,		 // Length
				,, _Y02, AddressRangeMemory, TypeStatic)
			DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
				0x00000000,		 // Granularity
				0xFEE01000,		 // Range Minimum
				0xFFFFFFFF,		 // Range Maximum
				0x00000000,		 // Translation Offset
				0x011FF000,		 // Length
				,, , AddressRangeMemory, TypeStatic)

 

Would this be ok then?

[dakku]

@BlackCH, thanks for the fan values, worked perfectly fine, fan is not so noisy anymore. Now if someone can tell me whats the permissions on their sleepwatcher.plist file it can start loading the daemon without giving me permission error.

[Einstein_ein]

Theres a newer DSDT in the first post. Please check if the problem exist with that one

Thanks for the info anyway. I will look into it

 

EDIT:

 

DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
				0x00000000,		 // Granularity
				0x00000000,		 // Range Minimum
				0xFEDFFFFF,		 // Range Maximum
				0x00000000,		 // Translation Offset
				0xFEE00000,		 // Length
				,, _Y02, AddressRangeMemory, TypeStatic)
			DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
				0x00000000,		 // Granularity
				0xFEE01000,		 // Range Minimum
				0xFFFFFFFF,		 // Range Maximum
				0x00000000,		 // Translation Offset
				0x011FF000,		 // Length
				,, , AddressRangeMemory, TypeStatic)

 

Would this be ok then?

yep

[BlackCH]

@BlackCH, thanks for the fan values, worked perfectly fine, fan is not so noisy anymore. Now if someone can tell me whats the permissions on their sleepwatcher.plist file it can start loading the daemon without giving me permission error.

open the Terminal and then type:

sudo -s
Password

Download Sleepwatcher 2.1 and unpack in your desktop

Then follow the instructions for upgrade in the sleepwatcher 2.1 readme (just copy and paste every command line to the terminal- press enter after each one!)

Then edit the rc.sleep and rc.wakeup files inside /etc folder (/etc folder is hidden) like I posted here

 

Or try the SleepWatcher package on the first post (I posted today). Just run it. Should do everything by itself (please let me know if it doesnt!)

[juanerson]

@BlackCH, thank you very much for the S.L. bootCD... I will try some day. I like all the set included, especially some of your additions to the DSDT like Sudden Motion Sensor (SMS0) and ALS0 devices... + AnV fakesmc.kext, now please I have some questions in spanish, please sorry:

 

1) El SMS tiene varias funciones según he leído, pero cuál es la más importante o útil? Y cuales riesgos conlleva tenerlo activado?. Ya me di cuenta y me llevé un susto con la pantalla oscura (aquí es de día) cuando reinicié el sistema jajaja, luego al ver en las preferencias de pantalla esta increíble función "Ajustar el brillo automáticamente cuando cambie la luz ambiental", espectacular, nunca había visto esa función en mi vida... y la transición de brillo es aún más suave. Cual es el dispositivo que se encarga de tal función, SMS o ALS? Ya le he inyectado todo eso al mío también jeje.

 

2) Por favor me puedes dar el link del foro de AnV? Para hacerle seguimiento a su variante de fakesmc, tu sabes... Por cierto, yo le hice unos ajustes al de netkas siguiendo los pasos de prasys para lo de smc-santa rosa y la versión SMC, pero esto parece que no tiene efecto, sino que es sencillamente estético... que sabes al respecto?

EDIT: AnV fakesmc post HERE.

 

3) La última jejeje, por favor hay algo importante que corregir en el DSDT según lo comentado por Einstein_ein? Porque si el problema es exclusivo del último compilador, no veo problema si no lo usamos. Además debo mencionar que hace tiempo que vengo probando esos últimos compiladores del gran mitch_de, sin éxito relevante, ni siquiera aparente en ninguno, es decir, que no noto que optimice algo más en nuestros DSDTs, siempre me salen la misma cantidad de optimizaciones y el mismo warning que con DSDTSE 1.4.3 (Disassembler/compiler version 20091214).

 

Saludos Cordiales.

[dakku]

I have followed all the instructions! The problem i have is that my plist file has permissions for me (user) and not root. Hence why sudo command will not work (root has no permissions for it). I need to change the permission on that file from user (me) to root (sudo) so that it will load on boot up even before my user account is loaded. If I type launchctl load /Library/LaunchDaemons/de.bernhard-baehr.sleepwatcher.plist (without sudo) the plist file loads, but with sudo it doesnt.

 

Edit: Done. thanks

[BlackCH]

1) El SMS tiene varias funciones según he leído, pero cuál es la más importante o útil?

Bueno yo me preguntaba lo mismo, haha! Para que sirven sin tener el hardware presente? la verdad que no estoy seguro. Habria que enterarse un poco mas del tema (sobre todo como funciona en los macs verdaderos) y seguir el topico de Andy. El ALS es el que se encarga de medir la luz ambiente (Ambient Light Sensor); ninguno de estos dispositivos esta realmente presente en nuestras maquinas (o si?)....de todas maneras los kexts cargan

Esta el la version del fakesmc incluida en el pack: http://www.insanelymac.com/forum/index.php...t&p=1455317

3) La última jejeje, por favor hay algo importante que corregir en el DSDT según lo comentado por Einstein_ein?

En mi opinion, si estas correcciones no implican ningun problema con las versiones anteriores de IASL, habria que añadirlas para evitarle problemas a otros usuarios....

Yo personalmente uso TextWrangler para editar los archivos .dsl y iASLme (v20090903 es el que tengo!) para compilarlos. Si necesito hacer algun 'dump' uso algun disco de linux o everest en XP

[yushir]

This post may not be in the line, but it might useful. Do you know of an app called f.lux? It changes the color intensity of your display based on your current location and time. I've using it for a while and at leas you should give it a try .

 

I'm trying out the new fakesmc, works really great (it's a pitty i don't have a smooth brightness though).

 

May you have a look at the following loader: http://www.insanelymac.com/forum/index.php?showtopic=216726

 

It's called ANV ACPI Loader, it's chamaleon pre-rc5. Should we give it a try.

[alemate23]

Great idea! My vote is for Slice´s bootloader, it seems more clean on booting process, but I don´t know why. Im feeling more stable, and I don´t worried about randoms unexpected KPs... because if I understood fine, the author made it to solve that problems of chameleon... related to ACPI calls or something improvement.

 

And this is the list of CPU replacement for 6720s:

Intel Core 2 Duo processors:

T9300 2.50-GHz processor (6-MB L2 cache, 800-MHz FSB)

T8300 2.40-GHz processor (3-MB L2 cache, 800-MHz FSB)

T8100 2.10-GHz processor (3-MB L2 cache, 800-MHz FSB)

T7800 2.60-GHz processor (4-MB L2 cache, 800-MHz FSB)

T7700 2.40-GHz processor (4-MB L2 cache, 800-MHz FSB)

T7500 2.20-GHz processor (4-MB L2 cache, 800-MHz FSB)

T7300 2.00-GHz processor (4-MB L2 cache, 800-MHz FSB)

T7250 2.00-GHz processor (2-MB L2 cache, 800-MHz FSB)

T7100 1.80-GHz processor (2-MB L2 cache, 800-MHz FSB)

T5550 1.83-GHz processor (2-MB L2 cache, 800-MHz FSB)

T5470 1.60-GHz processor (2-MB L2 cache, 800-MHz FSB)

T5450 1.66-GHz processor (2-MB L2 cache, 667-MHz FSB)

T5270 1.40-GHz processor (2-MB L2 cache, 800-MHz FSB)

Intel Pentium Dual-Core processors:

T2310 1.46-GHz processor (1-MB L2 cache, 533-MHz FSB)

Intel Celeron M processors:

550 2.00-GHz processor (1-MB L2 cache, 533-MHz FSB)

540 1.86-GHz processor (1-MB L2 cache, 533-MHz FSB)

530 1.73-GHz processor (1-MB L2 cache, 533-MHz FSB)

Spare part number respectively:

463050-001, 463049-001, 463048-001, 459465-001, 446894-001, 446893-001, 446892-001, 459463-001,

446891-001, 459464-001, 456575-001, 454598-001, 462345-001, 462619-001, 446889-001, 446888-001,

459462-001.

 

And any chipset compatible with hp 6720s??? i want to upgrade my notebook with a new video card, changing my chipset or motherboard

[yushir]

Graphics are integrated with the motherboard, you should change your motherboard.

[BlackCH]

Guys, can you post your battery time duration? mine hardly gets over 1:30 hrs

[smilenkovski]

Guys, can you post your battery time duration? mine hardly gets over 1:30 hrs

Hi to all!

New Boot CD!!!

Bravo for blackch.

I was busy for a while but now I'm back and very happy with everything happening on these threads. One of these days we should make an order in our guides on installing SL on HP 6270s and HP 550. Finally, we can say that we have an almost perfect hackbooks. Thank you for your hard work guys especially to juanerson for pioneer research in dsdt area for this laptop.

[juanerson]

Guys, can you post your battery time duration? mine hardly gets over 1:30 hrs

Mine 2:30 hrs on "hard work" and usb wifi plugged (receiving) and 30% brightness... so, without usb wifi 3:00 hrs... then, on minimum conditions, min level of brightness and no wifi, just excel or word open 3:30 - 3:45 hrs. Normally, Im not a hardly user on battery... just browsing and office work. System profile show this information (if is useful and reliable of course):

Carga restante (mAh): 3931

Capacidad de plena carga (mAh): 3931

Número de ciclos: 0

Condición: Normal

Voltaje (mV): 12548

 

Nota: Por favor, para descartar un deficiente speedsteping, te recomiendo utilizar la extensión legacy que subí dentro de la carpeta /Extra/Extensions en el tópico de smilenkovski, o también la puedes descargar en este mismo tópico en el (post 193). Sinceramente, no sé si tendrá algo que ver, pero vale la pena probar, ya que me di cuenta que en el bootCD va la primera que subí aquí (la que está dentro de speedstep_and_more.zip - post 170), la cual a los pocos días mejoré y publiqué posteriormente con el código (info.plist) correctamente (o secuencialmente) organizado valga la redundancia. Puedes comparar ambos info.plist para ver los cambios, sobre todo en la apertura y cierre en todas las secciones y subsecciones de dicho archivo... a eso me refiero con la secuencia, porque el anterior era un desastre... tenía muchos errores, porque no lo había copiado con un editor adecuado como textmate. Saludos.

 

EDITO: Por favor disculpa mi lapsus, es cierto que en el bootCD va una legacy para 10.6 (a secas)... sin embargo, me había adelantado al pensar que eran la misma o que estaba estructurada muy similar a la primera legacy que subí para la 10.6.2... Ahora bien, reitero que la legacy del post 193 para la 10.6.3 está completamente limpia en cuanto a estructura. De nuevo, perdón por mi confusión.

[BlackCH]

System profile show this information (if is useful and reliable of course):

Carga restante (mAh): 3931

Capacidad de plena carga (mAh): 3931

Número de ciclos: 0

Condición: Normal

Voltaje (mV): 12548

 

Gracias por el dato. Creo que lo que pasa es que mi bateria esta bastante deteriorada:

Charge remaining (mAh):	1614
 Fully charged:	Yes
 Full charge capacity (mAh):	1676

La capacidad maxima de carga es menos de la mitad que la tuya (suponiendo que estos datos son correctos). Tendria que verlo si en windows es lo mismo.

 

Sinceramente, no sé si tendrá algo que ver, pero vale la pena probar, ya que me di cuenta que en el bootCD va la primera que subí aquí (la que está dentro de speedstep_and_more.zip - post 170), la cual a los pocos días mejoré y publiqué posteriormente con el código (info.plist) correctamente (o secuencialmente) organizado valga la redundancia. Puedes comparar ambos info.plist para ver los cambios, sobre todo en la apertura y cierre en todas las secciones y subsecciones de dicho archivo... a eso me refiero con la secuencia, porque el anterior era un desastre... tenía muchos errores, porque no lo había copiado con un editor adecuado como textmate. Saludos.

 

There are two different set of kexts in the last install package:

One for 10.6 (the one loaded when booting from the boot CD) and one for 10.6.3 (the one contained in the HP6720s_Installer.PKG)

The legacy kext for speedstep for booting the retail disc is the same that was included in first install package I posted (25-09-2009). That is used only to boot to a 10.6 install or 10.6 retail disc. The kext included in the HP6720s_Installer.PKG is the one you posted in post #193 and it should be installed after updating the system to 10.6.3.

I've seen a lot of 10.6.3 retail discs in the net lately, so maybe will be wise to do a bootCD for that too, as the one currently posted wont work correctly

[buoo]

Excuse me

 

Is the last DSDT good for iDeneb 10.5.8 ?

[yushir]

Agree with Juanerson, i've got similar values on my battery, around 3900 mA.

 

Mine lasts about 2h and a half (with brightness at about 30% when i had it, it lasted at foremost 3 hours and a half - 4 hours). Yet at 100% usage hardly lasts 1 hour and 30 min.

 

@buoo Yes, the lastest DSDT posted is fine for any OS X.

[BlackCH]

Yet at 100% usage hardly lasts 1 hour and 30 min.

do you mean brightness @ 100%?

[yushir]

I mean brightness&cpu at 100%.

[lordsoth]

Yes, I installed those x1350 kexst and got full resolution, but I had mouse tearing, and kernel panic, and then i tried installing voodoo kernel mentioned in that post, and being a noob, i ended up with no kernel

So i installed ideneb again, but now i would like to install dsdt from this page, (to get ati working properly) but i would need some pointers, as i couldn't find much useful stuff on installing dsdt on Google.

Do you know any good post or tutorial on this topic ?

 

my hardware is

T2310 (1M Cache, 2x 1.46 GHz, 533 MHz FSB)

2gb ram

250 gb samsung

x1350 ati

 

p.s. i just reinstaled ideneb, and I've selected one of modded kernels based on the voodoo kernel, and now it works with both cores !

So only thing keeping me from fully functional hackintosh is graphic card.

Can you tell me what to do it kexs stops me from entering os, like command that disables all drivers and boots in safe mode (i tried -x but i dont think thad did the job)

Also i use bootloader, so i cant press f8 (it simply doesent do anything), i can pres "s" when selecting which drive to boot from, is that any good, or is there some other way ?

thx

 

Dong's ATI HD framebuffer is a quite promising solution, the latest kext for 10.5 causes KP at start a couple times, but if your system starts once it works properly from that point. (native resolution, qe/ci full support)

http://www.insanelymac.com/forum/index.php?showtopic=190586

[alemate23]

has anyone solved the problem of blacklight after sleep?

[yushir]

Not yet, i'm pretty busy right now. I guess it could be solved by directly writing to the GMA brightness register using reggie_se to get brightness to 100% but guess the controls would still not work (using the patched FB).

[BlackCH]

Not yet, i'm pretty busy right now. I guess it could be solved by directly writing to the GMA brightness register using reggie_se to get brightness to 100% but guess the controls would still not work (using the patched FB).

If we figure out to which address and how to write the values, then we could implement a couple of sell scripts and call them by assigned keystrokes (with keymaestro for instance).

 

Here theres a lot of references on using that method:

http://ipis-osx.wikidot.com/forum/t-91753/brightness-control

 

In the case of the GMA950 the brightness can be set with:

sudo reggie_se -D PCI -i 16 -w 255 -a 0xF4 -B 32

Understand what this line does: is writting the value 255 (-w 255) to the pci device nr 16 (-D PCI -i 16), register address F4 (-a 0xF4), register lenght 32 bits (-B 32).

The PCI 16 is in this case the 'Display Controller Device' which in my 6720s is PCI nr 20. You could use reggie to see this:

sudo reggie_se -x -D PentiumM

it will display a list of devices and their index numbers

 

The LBB (legacy backlight brightness) control register of the G945 chipset (GMA950) is at 0xF4-F7 (32 bits lenght) ( Mobile Intel® 945 Express Chipset Family datasheet, page 299). The first 8 bits (@ F4) are the ones containing the backlight brightness value

 

For the G965 it seems to be at the same address (Mobile Intel® 965 Express Chipset Family datasheet, page 428), but I've been trying to write to that register without any luck....

 

EDIT:

 

I've done some testings.

Using the patched x3100FB.kext (I posted some weeks ago) Im able to see the F4 register value changing along the brightness (using FN+F7/F8 and reading the register with reggie_se:

reggie_se -D PCI -i 20 -r -a 0xF4 -B 32

but using reggie_se to write to it

reggie_se -w 2 -D PCI -i 20 -a 0xF4 -B 32

doesnt seems to work.

 

Using the stock (unpatched) x3100FB the register is always stuck at the same value (82 hex), even when the brightness is changed. Again in this case write to the register address doesnt make any effect

 

EDIT 2:

 

I just noticed when the stock (unpatched) x3100FB is used, the value stored in the F4 register address still changes by pressing FN+F7/F8 keys (but the screen brightness remains the same)

[yushir]

Please note that the interrupt is handled by software. That is BIOS loads a default routine to handle it but OS can overwrite it. In this case the interrupt is ignored. You can see what i'm talking about in the LBES register.

 

I guess that the patch consists of eliminating one string in the framebuffer, the one that assigns a custom routine to the backlight interrupt. Thus it will only handle it not when the register is written (that's done automatically when using ACPI calls and fn+f7/f8 by hardware) but when certain key is pressed.

 

We should look in the way FreeBSD handles this. Because at the end, OS X is a simple copy of FreeBSD with a fancy interface.

 

EDIT: Seems mirror worked on 64 bits http://www.insanelymac.com/forum/index.php...t&p=1419106

 

EDIT2: Juanerson has reason, slice's post might be also the solution to our brightness problem.