Now I've come across this whole deal with rebranding Broadcom wifi cards and wondered upto what extent HP's whitelist of wifi cards go for the 100TU. There are mainly two (2) essential information about your wifi card or any hardware for that matter I believe, that Mac OS X uses to decide how to treat that specific hardware. Apple's OS is very judgmental and unforgiving at times, racist to be exact:
(1) Subsystem Product ID
(2) Subsystem Vendor ID
I had a question in my head: given that these two are what OS X cares about, I wonder how specific HP is - would it accept the card as long as the Subsystem Product ID remains intact or does it need both to be matching the information on its whitelist?
The answer is IT NEEDS BOTH PIECES OF INFORMATION TO MATCH. If one of that changes, you'll get this:
"104-Unsupported wireless network device detected. System Halted. Remove device and restart."
However, the MSI Wind is here to save the day and saved the day it did:
(1) I popped open the HP Mini 1001TU to extract the now alienated wifi card.
(2) Then I put it in the MSI Wind - I took out its Realtek WiFi card of course.
(3) Booted it up with Ubuntu 9.1 and did prasys' procedure to revert the Broadcom sprom to the original ID's:
- Subsystem Product ID : 0x1508
- Subsystem Vendor ID : 0x103c
*I only had to change the Subsystem Vendor ID as the Product ID wasn't changed before.
(4) I put back the Broadcom card inside the Mini and voilĂ ! My MacBook Mini is its old self again.
Now what's the point of this whole effort? I learned new stuff (or confirmed old stuff) about the HP Mini 1000:
(1) The upper chassis which houses the built-in trackpad has clips and is secured with adhesive on some parts. Careful in prying it off plus careful again when you put it back - make sure the clip near the left side palm rest is secured first.
(2) There's another PCI-e slot inside
(3) The WiFi card, while indeed is a Broadcom, is actually a 4312. To be exact, the label on the actual card reads: Broadcom4312 HMG or BRCM94312 - not sure why there's a "9" in the alternative appellation. All the while, Mac OS X, both Leopard and Snow Leopard, has always seen it as a 4315. I've no idea how that works. I've tried omitting 4315 from the AirPortBRCM4311.kext plugin so that 4312 remained, hoping it would be used. But that only caused the OS reporting that no airport card was installed.
(4) The entire motherboard is housed in the palm rest area. The heatsink and the ram slot's locations contribute a lot why the area feels remarkably toasty. It's an engineering feat alright; fitting an entire netbook system in that confined space but it's still undeniable that the Mini's one hot machine - and that's literally speaking.
Conclusion? I have serious doubts as to whether I'm gonna hackintosh an HP Mini 311 which in turn gives me more doubts as to whether I'm gonna stick with HP when I upgrade to a higher level netbook next year - I can't live without OS X, or rather, I don't reckon I can tolerate a non OSx86-ified netbook among my small collection. Cause come to think of it, there's already this compatibility issue with OS X alone and HP's adding to the equation another compatibility issue with its restrictive, not to mention imbecile, whitelists.
But then HP's netbooks remain on top niche for very good build quality.
P.S. My dear MSI Wind, though I'm extremely grateful to you for salvaging my alienated Broadcom wifi card, the undeniable truth still prevails: your chassis is chancy, your hinges feel flimsy, and your keyboard flexes with keys that are no thicker than an average party plastic cup.
Meanwhile, enjoy the HP Mini 1001TU's porn pics:
1 comment:
You got lucky there resurrecting the machine from a really bad move, it rarely ever happens, or at least it goes that way for me. Once i messed something up, it's time to buy a new one.
Post a Comment