 |
Current mood:  sneezy Category: Web, HTML, Tech
I've a bit of a cold today, so I'm not up to much other than sitting down looking at this new computer that I have. I'm not terribly happy with myself over the decision to buy it. Hopefully that will change.
The idea is to get away from the code programming and get with the beats, so it is more than bizarre that I find myself doing this today, especially as the last piece of hardware I care about on the laptop is the Wireless.
Well, I suppose in a way I like knowing that orange means off. Gimme a cable and spare me the radiation any day.
I got those WLAN blues…..!
This entry refers to getting the WLAN light to go blue when you enable the Wireless and turn the WLAN switch to the on position a HP Pavilion dv6770se Laptop. It may work for other Laptops and probably will work for the HP Pavilion dv6000 series.
The mini-PCI in the dv6770se, as far as I can make out, is an "Atheros AR5007EG"
The PCI Device ID in my Machine is PCI/VEN_168C&DEV_001C&SUBSYS_137A103C
The Vista Driver that comes with it also lists a PCI/VEN_168C&DEV_001C&SUBSYS_137B103C
I am currently using the ar5416.sys driver file, but i've also used the file ar5211.sys and they both work.
I have more than 5 different versions of Atheros Drivers that I downloaded, the last one that I installed was from a file called Atheros AR50006x Wireless_XP.zip and I don't remember where I downloaded that from, but I presume it was from a link on the HP forums.
-------------------------------------------------------------------------------------------------------------------------
I figured this out today after my imagination was sparked a little while thinking about some
posts about modifying .inf files on the HP forums to try and get the Hermosa Sound Card working.
I had a look at the netathr.inf file that is present in the preinstalled vista partition under /SWSETUP/Drivers/WLAN
That file only refers to two varieties of the card, so it's a pretty clean, easy to read .inf file.
I decided to have a go a deciphering .inf files. It's amazing really, more than 15 years using windoze and I've never actually done this!
I notice, in the section
[ATHR_DEV_001C.ndi.NTX86]
AddReg = atheros.reg, ledcontrol.reg
ledcontrol.reg eh? Sounds interesting, let us have a look at that section…
[ledcontrol.reg]
HKR, , gpioPinFunc0, 0x00002, "3"
HKR, , gpioFunc0ActHi, 0x00002, "0"
Ok, now i like the sound of that, pin functions sounds like it's what i'm looking for, but where do those registry entries go? What is HKR, , ? Let's have a look around….
In the section [atheros.reg], I find the line
HKR, Ndi..Interfaces, UpperRange, 0, "ndis5"
And a quick search through the registry leads me to HKLM/SYSTEM/CurrentControlSet/Control/Class/{4D36E972-E325-11CE-BFC1-08002bE10318}/0021/Ndi/Interfaces
Now this will most likely vary on your machine, but the best thing to do is a search under HKLM/SYSTEM/CurrentControlSet/Control for "Atheros" and that should pretty quickly lead you to the right section.
I would say at this point that if you are not familiar with editing the registry or if you are a bit clumsy with the delete button and you don't know what rm –rf / means, then you shouldn't make sandwiches after handling solder or install Unix utilities or your windows system and you probably shouldn't worry about your little amberblue light either. I would say that, but then you wouldn't learn anything, and you want to learn something, right?
So let us deduce that that those gpioPinFunc0 and gpioFunc0ActHi keys go in the "root" of the 0021 entry. And that's exactly where I put them. Nothing like trying.. I did ponder for a while over whether they might be Binary DWORD or String Values, then I just added them as string values, restarted the card and wow, the light went blue. (johnsmith127 has since posted over on the HP Forum suggesting they be DWORD Values)
Now a note about rebooting and restarting. It's really not necessary to do this quite as much as is generally recommended on the internet, unless you have a bad coffee habit. Windows and desktop as opposed to server Linux has promoted this rebooting craze. Simply disabling and re-enabling the card in device manager will suffice.
I used to run linux servers built pretty much from stratch and I smile wryly when I see these HOWTOs suggesting a reboot when a simple "kill –HUP xxx" or even a "rmmod xxxx" follwed by "modprobe xxx" would suffice, and be a lot easier than explaining to the entire office why the network had gone down.
I've spent enough of my life watching PC's reboot, and you know what,
so have you! ....Now I'm ranting… happy blue lights.
I wonder does the same magic work on this oh so not hermosa sound card.....
9:28 AM
Powered by  | | English | | Albanian | | Arabic | | Bulgarian | | Catalan | | Chinese | | Croatian | | Czech | | Danish | | Dutch | | Estonian | | Filipino | | Finnish | | French | | Galician | | German | | Greek | | Hebrew | | Hindi | | Hungarian | | Indonesian | | Italian | | Japanese | | Korean | | Latvian | | Lithuanian | | Maltese | | Norwegian | | Polish | | Portuguese | | Romanian | | Russian | | Serbian | | Slovak | | Slovenian | | Spanish | | Swedish | | Thai | | Turkish | | Ukrainian | | Vietnamese |
|