New WLAN Card - Error 10 (Device cannot start)

Message

iam8up · #1 Post by **iam8up** » Sun Mar 05, 2006 12:23 am

I just got off the phone with IBM's Thinkpad Technical Support and this new wifi card is 'not supported by this machine'.

I put in an Atheros 5212 and the previous owner told me he upgraded the motherboard, so I don't know what the model number of it is. It installed the drivers just fine, but it gives me that Error 10 in the device manager.

I know it's common to find this error in driver incompatibility, so I was wondering if there are any suggestions out there or previous resolutions.

Tried on a T30 2366 (as in my sig) with this driver: http://www-307.ibm.com/pc/support/site. ... MIGR-52527

Memphis · #2 Post by **Memphis** » Sun Mar 05, 2006 8:15 am

Possibly, as you said, it´s a driver incompatibility, not a real one, but the .inf-file has to be overworked.
Try the "original"-drivers from Atheros which are not specified to IBM-adapters only - http://tinyurl.com/eyzl3
Version is however not .133 but .71, but they work flawlessly with my Atheros card.

danage · #3 Post by **danage** » Sun Mar 05, 2006 10:32 am

This is a strange phenomenon i have also encountered. However, it can be bypassed. First, compare your PCI ID string. You will find it in the device manager under the tab "details". Is it: PCI\VEN_168C&DEV_1014&SUBSYS_057E1014?

If so, use the generic drivers as Memphis has suggested. If that does not work, you will need to patch you PCI device ID. I can walk you through this if necessary.

iam8up · #4 Post by **iam8up** » Sun Mar 05, 2006 6:14 pm

OK...I downloaded those drivers and then specified which driver to use. Windows says it wasn't compatible, so I don't know if it's the driver or the PCI ID problem now. I was given a list (all of which were 'incompatible') of devices, most being AR500# and my card is an AR5212. The last one on the list was 'Atheros Wireless Network Adapter', which was what I installed it with.

The automatic options, searching and all that, did not pick it up (plus it was looking for updated drivers - these have a lower version number).

The PCI ID starts out similar, but changes...

PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&139E449D&0&10F0

danage · #5 Post by **danage** » Mon Mar 06, 2006 4:17 am

With a text editor, open the ar5211.inf file and change according to your device. Search for:
%ATHER.DeviceDesc.2042% = ATHER_DEV_2042.ndi, PCI\VEN_168C&DEV_0013&SUBSYS_2042168C
and change to
%ATHER.DeviceDesc.2042% = ATHER_DEV_2042.ndi, PCI\VEN_168C&DEV_1014

Then, remove your existing drivers in the device manager. Next, right click the network adapters and select "search for new components". It will ask for Atheros drivers. Use the ones you just "made". It should work.

If not, are you familiar with Linux?

iam8up · #6 Post by **iam8up** » Mon Mar 06, 2006 9:49 am

I couldn't find an ar52*inf in \windows\*.*

I have a 5212 card, not a 5211 if that matters (the drivers I've downloaded both from IBM and the first reply are *5211*, FYI)

I do, however, have a net5211.inf which did not contain that string to replace.

I am somewhat familiar with linux, I have it Ubuntu installed on this machine (with the Atheros card problems) and I have multiple Live CDs

danage · #7 Post by **danage** » Mon Mar 06, 2006 12:01 pm

sorry, i meant net5211.inf. it's in the ndis5x-folder in the zip memphis linked to in his post. replace
%ATHER.DeviceDesc.2022% = ATHER_DEV_2022.ndi, PCI\VEN_168C&DEV_0012&SUBSYS_7005144F
with
%ATHER.DeviceDesc.2022% = ATHER_DEV_2022.ndi, PCI\VEN_168C&DEV_1014

remove your existing drivers from the device manager. scan for new hardware. select "search here for driver" and point to the ndis5x folder. it should prompt installing an "Atheros AR5001X Mini PCI Wireless Network Adapter" which corresponds exactly your existing hardware.

iam8up · #8 Post by **iam8up** » Mon Mar 06, 2006 8:32 pm

I wasn't able to use the search ability to have the card installed (it's already installed, and it needs an updated driver). I forced it to Atheros AR5001X Mini PCI Wireless Network Adapter (using the whole select from list option).

The device still cannot start =(

danage · #9 Post by **danage** » Tue Mar 07, 2006 10:55 am

remove your existing driver in the device manager. browse to c:\windows. press the search button in the symbol bar. make sure you check system and hidden files under extended options. search for "oem". open the oem??.inf files to check which driver information they contain and delete the atheros ones. delete the corresponding .pnf-files as well. search for ar5211.sys. delete all ar5211.sys in \windows and subfolders. re-scan for new hardware in the device manager and install appropriate (=the one you made) driver. you will not be able to use the driver update button, as there is no driver to be updated.

it definately works, i've done it before. the information in your signature is incorrect.

iam8up · #10 Post by **iam8up** » Wed Mar 08, 2006 8:41 pm

Let me get this straight...

You want me to remove the device from the device manager.

Then you want me to search the entire %SYSTEMROOT% for oem??.inf files? Which ones do I delete? After that I then remove *.pnf corresponding files.

Remove ar5211.sys as well.

Install it and specify the device from the 'modified' driver I made?

danage · #11 Post by **danage** » Thu Mar 09, 2006 2:46 am

iam8up wrote:You want me to remove the device from the device manager.

Yes. I do this by pressing delete.

iam8up wrote:Then you want me to search the entire %SYSTEMROOT% for oem??.inf files? Which ones do I delete? After that I then remove *.pnf corresponding files.

You open the .inf files with a text editor to see which ones contain atheros driver information. you delete such .inf-files and the corresponding .pnf-file. (that with the same name but .pnf as an extension). not *.pnf, which would mean you deleted all .pnf-files.

iam8up wrote:Remove ar5211.sys as well.

Only the ones in your \Windows and subfolders.

iam8up wrote:Install it and specify the device from the 'modified' driver I made?

You scan for new hardware. A driver installation dialogue will appear. You pick "search here for drivers" and point to the directory that contains your modified drivers.

Good luck!

iam8up · #12 Post by **iam8up** » Sun Mar 19, 2006 4:20 pm

Finally got around to do this...still not doing it right =(

I removed the drivers, and then had the Device Manager re-scan for hardware changes. It finds a Network Controller but has no idea what it is, so I've obviously removed the drivers correctly.

I then replaced the line and had the new hardware scan that directory for the drivers, and it did not find it.

iam8up · #13 Post by **iam8up** » Wed Mar 22, 2006 6:22 pm

Maybe someone can help me out here...this is what the Device Instance Id says...

PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&139E449D&0&10F0

I added this line in the middle of the file, no idea where I was supposed to put it...

%ATHER.DeviceDesc.2022% = ATHER_DEV_0014, PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&139E449D&0&10F0

danage · #14 Post by **danage** » Thu Mar 23, 2006 7:36 am

proceed as stated in my initial post. if the .inf file does not contain the line (cf. post), make sure to modify the original ibm drivers, not the generic ones.

if this fails, you will need to manually patch the card from ibm device id to atheros generic device id. you can then make the ibm drivers work even with the generic device id. i had the same problem: for some reason windows will not start the card if its id contains 1014, the ibm vendor id string.

but try modifying the drivers first.

iam8up · #15 Post by **iam8up** » Thu Mar 23, 2006 9:26 pm

danage wrote:sorry, i meant net5211.inf. it's in the ndis5x-folder in the zip memphis linked to in his post. replace
%ATHER.DeviceDesc.2022% = ATHER_DEV_2022.ndi, PCI\VEN_168C&DEV_0012&SUBSYS_7005144F
with
%ATHER.DeviceDesc.2022% = ATHER_DEV_2022.ndi, PCI\VEN_168C&DEV_1014

remove your existing drivers from the device manager. scan for new hardware. select "search here for driver" and point to the ndis5x folder. it should prompt installing an "Atheros AR5001X Mini PCI Wireless Network Adapter" which corresponds exactly your existing hardware.

I did exactly that and Windows didn't find them to the device's liking.

wireless4laptop · #16 Post by **wireless4laptop** » Sat Mar 25, 2006 6:34 am

We met this before on T23. If the card is ok, the problem is the issue of driver. Please use Atheros driver from www.driverguide.com.

public user name from us: wireless4laptop_driverguide@yahoo.co.uk
password: 987654

this is right.

iam8up · #17 Post by **iam8up** » Sat Mar 25, 2006 11:23 pm

wireless4laptop wrote:We met this before on T23. If the card is ok, the problem is the issue of driver. Please use Atheros driver from www.driverguide.com.

public user name from us: wireless_driverguide@yahoo.co.uk
password: 987654

That's a bad login, someone changed the password...

iam8up · #18 Post by **iam8up** » Sun Mar 26, 2006 11:14 pm

wireless4laptop wrote:We met this before on T23. If the card is ok, the problem is the issue of driver. Please use Atheros driver from www.driverguide.com.

public user name from us: wireless4laptop_driverguide@yahoo.co.uk
password: 987654

this is right.

HAHAHA!!! It is such a small world out there =P

I bought the card from you!
http://cgi.ebay.com/ws/eBayISAPI.dll?Vi ... :B:EF:US:1

wireless4laptop · #19 Post by **wireless4laptop** » Mon Mar 27, 2006 10:00 am

91P7301 cannot work on T23 (even it uses Atheros 5212A chipset). Don't worry. Contact with us by email. wireless4laptop@hotmail.com.

danage · #20 Post by **danage** » Mon Mar 27, 2006 3:54 pm

i have it working.

iam8up · #21 Post by **iam8up** » Mon Mar 27, 2006 7:22 pm

Please note I have a T30, not a T23 - if that matters.

iam8up · #22 Post by **iam8up** » Wed Mar 29, 2006 12:33 am

danage wrote:i have it working.

Which model do you have?

danage · #23 Post by **danage** » Wed Mar 29, 2006 1:35 am

t30 2367-81g, heavily modified. for all i know, the system type is not relevant to the appearance of the problem. for some reason cards with pci id 1014 are not started in the t30. use the idchanger.c (google) and linux to modify the pci id, for example to: PCI\VEN_168C&DEV_0012&SUBSYS_2022168C
it's fairly easy.

iam8up · #24 Post by **iam8up** » Thu Mar 30, 2006 9:21 pm

danage wrote:t30 2367-81g, heavily modified. for all i know, the system type is not relevant to the appearance of the problem. for some reason cards with pci id 1014 are not started in the t30. use the idchanger.c (google) and linux to modify the pci id, for example to: PCI\VEN_168C&DEV_0012&SUBSYS_2022168C
it's fairly easy.

That C file is not on Google...it's mentioned once, but nothing useful.

I have Ubuntu installed on it, so that's no problem. Could you tell me where to find this idchanger.c and how to use it? What do I change the PCI ID to once I'm there? Can I revert it back?

danage · #25 Post by **danage** » Fri Mar 31, 2006 2:06 pm

It's here. Of course you can revert it back. Should work straight away with Ubuntu. Compile as stated in the guide. Find out your current ID in device manager. Change to the one I sent.

aragorn · #26 Post by **aragorn** » Tue Apr 11, 2006 2:28 pm

danage wrote:It's here. Of course you can revert it back. Should work straight away with Ubuntu. Compile as stated in the guide. Find out your current ID in device manager. Change to the one I sent.

I changed my PCI ID following your example:
PCI\VEN_168C&DEV_0012&SUBSYS_2022168C

Now I think that was not really a good idea - the madwifi driver partially is a binary driver.
The HAL part of the driver has a revision check - the module will not load if the pci id and revision is not known in the binary part - you get the following message:

Code: Select all

kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
kernel: wifi%%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)

Note: One *cannot* revert the pci id back without a working madwifi driver!
And the second thing - even with the changed ID in the .inf file Windows XP does not load the windows drivers - I still get the "Code 10" error on my machine.
How can I get out of this? At the moment my Atheros card is completely unusable...

P.S. My Thinkpad ist a A31p 2653-R9G - not a T30 or T23 - the behaviour seems to be similar to the T30.

aragorn · #27 Post by **aragorn** » Fri Apr 14, 2006 1:29 pm

danage wrote:
Good Luck!

Thank you.

Here http://madwifi.org/ticket/436 is a patch for the if_ath_pci.c - File which allows you to use a card with a not known or broken PCI ID.
Using the patched driver and the idchanger.c I could change my card's ID several times (with adjusting the if_ath_pci.c afterwards) so that finally the Generic Windows Drivers do work now - Great!

danage · #28 Post by **danage** » Sat Apr 15, 2006 10:48 am

aragorn wrote: could change my card's ID several times (with adjusting the if_ath_pci.c afterwards) so that finally the Generic Windows Drivers do work now - Great!

Good job! Congratulations! Would you mind posting the PCI ID you had before and the one you have now plus your chipset number (ar500?)? I'm sure a lot of people are quite interested in this :)

aragorn · #29 Post by **aragorn** » Tue Apr 18, 2006 7:42 am

aragorn wrote: Here http://madwifi.org/ticket/436 is a patch for the if_ath_pci.c - File which allows you to use a card with a not known or broken PCI ID.
Using the patched driver and the idchanger.c I could change my card's ID several times (with adjusting the if_ath_pci.c afterwards) so that finally the Generic Windows Drivers do work now - Great!

Assuming that the "IBM 11a/b/g Wireless LAN Mini PCI Adapter II" is based on AR5004X Chipset and AR5112 Radio Chip I took the generic drivers .inf-file to find a Card ID supporting these chipsets by generating the right registry entries during installation.

The original IBM ID was
PCI\VEN_168C&DEV_1014&SUBSYS_057E1014.

According to the .inf-file I had to make my decision between
ATHER.DeviceDesc.1042 = "Atheros AR5004X Wireless Network Adapter"
ATHER.DeviceDesc.2042 = "Atheros AR5004X Wireless Network Adapter"
- does anyone know a difference between those two cards?

Finally I changed my card's ID to the seond one (2042 sounds better than 1042

) having the ID
PCI\VEN_168C&DEV_0013&SUBSYS_2042168C

danage · #30 Post by **danage** » Tue Apr 18, 2006 9:53 am

aragorn wrote:ATHER.DeviceDesc.1042 = "Atheros AR5004X Wireless Network Adapter"
ATHER.DeviceDesc.2042 = "Atheros AR5004X Wireless Network Adapter"
- does anyone know a difference between those two cards?

Yeah, check this out:

Code: Select all

[ATHER_DEV_1042.ndi]
AddReg          = ATHER_DEV_1042.id.reg, 5211.reg, ATHER.win.reg, 5212.[b]abgcb[/b].reg
[ATHER_DEV_2042.ndi]
AddReg          = ATHER_DEV_2042.id.reg, 5211.reg, ATHER.win.reg, 5212.[b]abgmp[/b].reg

I'm assuming cb stands for CARDBUS (=PCMCIA/PC-Card) and mp stands for MiniPCI. So I guess you made the right choice :)

New WLAN Card - Error 10 (Device cannot start)

New WLAN Card - Error 10 (Device cannot start)

Who is online