HP ProBook Installer 6.1: 4x30s and 4x40s support

[sean2e]

HP ProBook Installer 6.1 (beta): Ivy bridge support

You don't have to keep it open. Your log from the failure are still in /var/log/install.log.

If you open up Console, then look on the left in /var/log/install.log, you can search (command-F, Edit->Find, %F, etc), probably for ProBook, or ProBookInstaller, and you should find the log for your install.

Once you find the log you can copy paste the error or the entire log.. select it, then Edit->Copy. Paste it here, or if it is large, put it in .txt file, zip it and attach to post.

Hope this is right :/

 

[philip_petev]

HP ProBook Installer 6.1 (beta): Ivy bridge support

Hope this is right :/

It fails to create prelinked kernel because of... com.apple.driver.AppleUSBBluetoothHCIController!!! WTF!

You're running your system with vanilla IOBluetoothFamily.kext, right?

 

[RehabMan]

HP ProBook Installer 6.1 (beta): Ivy bridge support

Hope this is right :/

Your error is caused by kextcache not rebuilding clean. Problem is BT kexts. Did you install rolled-back/patched BT kexts at some point? Because you get this error if you're using a system kext that was built for a different version than the one you're running (that's what the comment 'Make sure your kext has been built against the correct headers.' means).

Jun 24 05:15:14 192-168-1-100.tpgi.com.au installd[672]: PackageKit: kextcache -system-caches
Jun 24 05:15:17 192-168-1-100.tpgi.com.au installd[672]: PackageKit: kextcache -update-volume / -Installer
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: kxld[com.apple.driver.AppleUSBBluetoothHCIController]: The vtable 'vtable for AppleUSBBluetoothHCIController' is malformed. Make sure your kext has been built against the correct headers.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Link failed (error code 5).
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Prelink failed for com.apple.driver.AppleUSBBluetoothHCIController; aborting prelink.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Failed to generate prelinked kernel.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Child process /usr/sbin/kextcache[729] exited with status 71.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

I'm assuming AppleUSBBluetoothHCIController is somewhere in IOBluetoothFamily.kext, but I'm not sure. You should restore it to the stock kext and if you're not sure how (or if this class is not in that kext), do a fresh install starting w/ genuine Mac App Store image.

 

[RehabMan]

HP ProBook Installer 6.1 (beta): Ivy bridge support

See how there is three install.log/s is that right?

The others are archives. Once the log gets to a certain size, older info is compressed.

 

[philip_petev]

HP ProBook Installer 6.1 (beta): Ivy bridge support

Your error is caused by kextcache not rebuilding clean. Problem is BT kexts. Did you install rolled-back/patched BT kexts at some point? Because you get this error if you're using a system kext that was built for a different version than the one you're running (that's what the comment 'Make sure your kext has been built against the correct headers.' means).

Jun 24 05:15:14 192-168-1-100.tpgi.com.au installd[672]: PackageKit: kextcache -system-caches
Jun 24 05:15:17 192-168-1-100.tpgi.com.au installd[672]: PackageKit: kextcache -update-volume / -Installer
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: kxld[com.apple.driver.AppleUSBBluetoothHCIController]: The vtable 'vtable for AppleUSBBluetoothHCIController' is malformed. Make sure your kext has been built against the correct headers.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Link failed (error code 5).
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Prelink failed for com.apple.driver.AppleUSBBluetoothHCIController; aborting prelink.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Failed to generate prelinked kernel.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Child process /usr/sbin/kextcache[729] exited with status 71.
Jun 24 05:15:21 192-168-1-100.tpgi.com.au installd[672]: kextcache: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

I'm assuming AppleUSBBluetoothHCIController is somewhere in IOBluetoothFamily.kext, but I'm not sure. You should restore it to the stock kext and if you're not sure how (or if this class is not in that kext), do a fresh install starting w/ genuine Mac App Store image.

Actually, there is no such kext inside IOBluetoothFamily.kext, at least not in IOBluetoothFamily.kext 10.8.4 and Spotlight can't find anything with that name. I don't have such on both my desktop and laptop. Maybe it exist in some older version of IOBluetoothFamily.kext.

 

[RehabMan]

HP ProBook Installer 6.1 (beta): Ivy bridge support

Actually, there is no such kext inside IOBluetoothFamily.kext, at least not in IOBluetoothFamily.kext 10.8.4 and Spotlight can't find anything with that name. I don't have such on both my desktop and laptop. Maybe it exist in some older version of IOBluetoothFamily.kext.

This is a classname, so if it is there it will be buried in an Info.plist inside of a kext as the value to an IOClass key. It is a little bit hard to find unless you grep all Info.plist /S/L/E. You'd have to use something like this:

find /System/Library/Extensions -type f -iname Info.plist -exec grep -H AppleUSBBluetoothHCIController {} \;

On my system, it didn't find anything. So it probably was part of an older version... Or it is an internal class which you'd have to see by using 'nm' (which lists symbols in a binary)...

At any rate, the issue is BT related, and is probably the result of mucking with system BT kexts a bit much.

 

[sean2e]

HP ProBook Installer 6.1 (beta): Ivy bridge support

This is a classname, so if it is there it will be buried in an Info.plist inside of a kext as the value to an IOClass key. It is a little bit hard to find unless you grep all Info.plist /S/L/E. You'd have to use something like this:

find /System/Library/Extensions -type f -iname Info.plist -exec grep -H AppleUSBBluetoothHCIController {} \;

On my system, it didn't find anything. So it probably was part of an older version...

At any rate, the issue is BT related, and is probably the result of mucking with system BT kexts a bit much.

I have recently tried to get a usb wifi dongle to work? Other then that I cant think of anything else ive added as I used the last installer (just before .4 came out) to get mu USB 3.0 to work and it installed fine. I don't have BT or WiFi right now anyway as the card i got of eBay can be seen by the system but is ultimately dead.. So you guys suggest a fresh install?

 

[philip_petev]

HP ProBook Installer 6.1 (beta): Ivy bridge support

I have recently tried to get a usb wifi dongle to work? Other then that I cant think of anything else ive added as I used the last installer (just before .4 came out) to get mu USB 3.0 to work and it installed fine. I don't have BT or WiFi right now anyway as the card i got of eBay can be seen by the system but is ultimately dead.. So you guys suggest a fresh install?

No, just restore your vanilla IOBluetoothFamily.kext and you're good to go.

 

[RehabMan]

HP ProBook Installer 6.1 (beta): Ivy bridge support

I have recently tried to get a usb wifi dongle to work? Other then that I cant think of anything else ive added as I used the last installer (just before .4 came out) to get mu USB 3.0 to work and it installed fine. I don't have BT or WiFi right now anyway as the card i got of eBay can be seen by the system but is ultimately dead.. So you guys suggest a fresh install?

It could be buried somewhere in IOUSBFamily too... I'm really not sure where that class lives...

But yes, I suggest a fresh install.

Assuming kextcache was clean before, one thing to always check after installing something new (device drivers/kexts):

- rebuild cache with Kext Wizard
- while it is running, look at system.log and make sure kextcache rebuild is clean
- if not, undo what you just did... (or restore to backup)

I think a lot of people just install stuff, never look at system.log to see if it is successful, and meanwhile use their system not knowing their kextcache is broken. Then along comes an update or an update to the ProBook Installer, and then the error shows up. At this point, days/weeks/months have passed since they caused the problem, but they've just now found out about it and, of course, have no idea what caused it.

 

[philip_petev]

HP ProBook Installer 6.1 (beta): Ivy bridge support

Side note: you can search for a kext by its classname with Kext Wizard, the last page, Loaded, but as the name says, you can find there only the kexts, which are currently loaded.