Contribute
Register

HP Probook 4730s

Status
Not open for further replies.
I did not notice any difference in performance or glitches with 8,2 smbios.

A MacBook Pro (8,1) only comes with Intel HD Graphics 3000, but the MacBook Pro (8,2) has the ATI Radeon HD 6490M.

Also with 8,1 smbios, it shows a 13" MacBook Pro, in system information. Where 8,3
shows 17".

I believe 8,2 shows 15" display in the system information, but I can not check it now because my HP 4730s will not turn on anymore. I tried everything I can think of to get it going including a hard reset. I guess it will be going back for warranty.
 
ollopa said:
I did not notice any difference in performance or glitches with 8,2 smbios.

A MacBook Pro (8,1) only comes with Intel HD Graphics 3000, but the MacBook Pro (8,2) has the ATI Radeon HD 6490M.

Also with 8,1 smbios, it shows a 13" MacBook Pro, in system information. Where 8,3
shows 17".

I believe 8,2 shows 15" display in the system information, but I can not check it now because my HP 4730s will not turn on anymore. I tried everything I can think of to get it going including a hard reset. I guess it will be going back for warranty.

8,2 shows 15" yes, and 8,3 shows 17". I've just checked, I've just switched to 8,3, don't know if it helps anything.
 
Interesting information/theory on the problem with 4730s being the resolution, which is not available in any Macbook. It does make quite a bit of sense when you think of it..

There's been the observation of no problems when using an external monitor, which would confirm this. However, if that's true, switching the internal screen to a non-native resolution that macbooks also support (1024x768 or whatever!) should also get rid of the problems - I have 10.7.1 installed, which doesn't have the laggy gfx (but corruption every now and then, which you can get mostly rid of by fixing permissions), so can anyone with 10.7.2+ confirm this?

Also: There *is* a Mac with Intel HD3000 gfx that should support any resolution without problems: The Mac mini! Couldn't we take that as a reference to get rid of the problems?
 
To change topics a little bit, are the ProBooks able to restart with the HDMI monitor still plugged in? On my DV7, I have to unplug the external when I reboot. When it is done booting, I plug back in. Is there a fix for that, and if so, does it apply to non-ProBooks?
 
Anyone able to perform the following:

http://www.insanelymac.com/forum/index. ... 59705&st=0

?

I've got the same symptoms as described but I don't have enough knowledge at the moment to perform what's described there.

I'd just like to know if it solved anything or may solve the errors.

Thanks.
 
trusteh said:
8,2 shows 15" yes, and 8,3 shows 17". I've just checked, I've just switched to 8,3, don't know if it helps anything.

I switched to 8,3. It shows "17 inch Early 2011 MacBook Pro". Since my laptop is 17 inch, it makes more sense to have that identifier. I have not noticed a difference in operation, though. It is running just fine either way, only occasionally does it have a glitch in Mission Control.
 
trusteh said:
Anyone able to perform the following:

http://www.insanelymac.com/forum/index. ... 59705&st=0

?

I've got the same symptoms as described but I don't have enough knowledge at the moment to perform what's described there.

I'd just like to know if it solved anything or may solve the errors.

Thanks.

I've now got the table for my 4730s, and it looks as follows:

0000000: 0102 0300 1007 0000 1007 0000 ............
000000c: 0602 0000 0001 0000 0900 0000 ............
0000018: 0503 0000 0200 0000 3000 0000 ........0...
0000024: 0406 0000 0008 0000 0600 0000 ............
0000030: 0000 0000 0000 0000 0000 0000 ............

But now I'm stuck again, I have no knowledge of editing this :p Anyone does?

I only need VGA for my work's external monitor, or if it works better no external support at all.
 
We've edited that for you ;)

Shouldn't need testing. However, these scripts will allow you to edit them.

Run one to edit the table, write it out, and then run to to save changes and reboot.

Be careful, as you can ruin the kext.
 
blueking said:
We've edited that for you ;)

Shouldn't need testing. However, these scripts will allow you to edit them.

Run one to edit the table, write it out, and then run to to save changes and reboot.

Be careful, as you can ruin the kext.

Thanks for the scripts, makes it a lot easier.

But I'm wondering, did you edit it for the 4530s or also for the 4730s? Since I'm still getting those symptoms and errors in my log..

I might play around with the table to see what happens, need some more research though :p
 
Status
Not open for further replies.
Back
Top