New WLAN Card - Error 10 (Device cannot start)

[iam8up]

So...

I'm not a quick learner and I especially don't learn well when I had to something unparallel to a guide. Could anyone explain to me what exactly I must do to get this Atheros card to work on my T30?

From what I gather...

I need to change the PCI ID on the card, using 'idchanger.c'; this will enable the IBM drivers to work in Windows?

I've already used the great Linux live cd offered on these forums to remove the two stupid errors that BIOS delivers from an alternative mini pci card.

[KF9YR]

Sorry if this double-posts, I think I timed out and I don't see my post

----------------------------------------------------

Hi,

I've been lurking her for about a week. I have a T30 (2366-41U) which I had been using with a IBM High Rate Wireless b card.

I need to use WPA in multiple locations so I decided to upgrade to the 73P4301 card I noticed someone mentioned in one of these forum threads.

I received the card yesterday. I ran the no1802 patch, tried to run the 01C9 patch (get an error that says "EEPROM write failed"), but I am able to press esc and continue.

Win XP Pro was able to detect and install the card, it is using an Atheros driver from 12/27/2004 V 4.0.100.140 (I tried downloading and installing the 12/21/2005 V 4.1.102.133 and that didn't work either).

However the card will not start and is getting the Error Code 10 problem in device manager.

I notice the Device Instance ID is
PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&139E449D&0&10F0

The Model No for this card is AR5BMB-44 (AR5004X WLAN Chipset?).

I looked at the card and the processor chip is the AR5213A-00 so the radio chip should be the AR5112.

I noticed the drivers that the IBM supplies on both their Upgrade site and the CD that came with the card use the NET5211.INF file.

Assuming I'm able to write to the EEEPROM using idchanger.c from linux would I rename the id to PCI\VEN_168C&DEV_0013&SUBSYS_2042168C as aragorn did?

Thanks,

George

[danage]

I notice the Device Instance ID is

Code: Select all

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

The Model No for this card is AR5BMB-44 (AR5004X WLAN chipset?).

This is correct. You have the 5004x card with the codename of "Bartlett", cf. Thinkwiki. This information can be gathered looking at the NET5211.INF file that comes with the IBM drivers. Maybe we should add this information to the wiki?

I received the card yesterday. I ran the no1802 patch, tried to run the 01C9 patch (get an error that says "EEPROM write failed"), but I am able to press esc and continue.

Now, this is strange. I own the same card and the write does not fail. The idchanger might not work for you in this case, cf. 01C9 article in thinkwiki.

Assuming I'm able to write to the EEEPROM using idchanger.c from linux would I rename the id to

Code: Select all

PCI\VEN_168C&DEV_0013&SUBSYS_2042168C

as aragorn did?

You own a different card than he does, with different capabilities, so it would be better to choose an ID that more closely matches your card. Maybe we should put all the information from this thread into a wiki article, to make it less confusing.

Here is how I got that same card running with the original IBM drivers.

Using idchanger.c, I changed the ID to that of the "Clymer" card:

Code: Select all

PCI\VEN_168C&DEV_0013&SUBSYS_04081468

In the NET5211.INF, then changed the line

Code: Select all

%ATHER.DeviceDesc.0014%  = ATHER_DEV_2013,    PCI\VEN_168C&DEV_1014&SUBSYS_057E1014

to

Code: Select all

%ATHER.DeviceDesc.0014%  = ATHER_DEV_2013,    PCI\VEN_168C&DEV_0013&SUBSYS_04081468

As a final step, commented out the "Clymer" line in the .INF file:

Code: Select all

%ATHER.DeviceDesc.1013%  = ATHER_DEV_1013,    PCI\VEN_168C&DEV_0013&SUBSYS_04081468

Background info: I found out that some other routine or BIOS must prevent ANY driver to be loaded (even the generic Atheros driver) as long as an IBM vendor ID (1014) is present in the WLAN card. I suspect the bluetooth drivers, but cannot be sure.

[RS_003]

can some one guide me trough this?

I have a new 39T0081 (Atheros )

And done the no 1802 so it boots in my X31.
But I now I get the code 10 error.

I have tried al drivers posible

[KF9YR]

danage, First of all I'd like to say Thanks for all the help!

I still can't write to the EEPROM on this card...

Here's what I did...

First of all I figured the madwifi driver's were loaded on the linux live CD that fixes the 1802 and 01C9 errors. I don't have linux loaded on my T30 so I put a knoppix live CD in one of my desktop computers and downloaded the idchanger binary from the link you provided earlier in this thread. I copied this onto a floppy.

I then put the linux live 1802 cd in my T30 and started it (in the dock with a floppy drive attached).

I chose no to the 1802 fix and cancelled the 01C9 fix (since it won't write anyways and I thought I'd try the write command in the idchanger binary in case the command was written differently).

I then ran these commands:

lspci -nv (to get the base memory address it returned the following)

02:02.0 Class 0200: 168c:1014 (rev 01)
Subsystem: 1014:057e
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at d0200000 (32-bit, non-prefetchable)
Capabilities: [44] Power Management version 2

mount /dev/fd0 floppy

cd floppy

idchanger -r 0xd0200000

cntrl-c (to stop the read while I could still see the first 8 lines)

Reading 0 current value 0x1014
Reading 1 current value 0x168c
..
Reading 7 current value 0x057e
Reading 8 current value 0x1014

This confirmed your information so I tried running idchanger with the write switch

idchanger -w 0xd0200000 0x0013 ox168c 0x0408 0x1468

I tried this 10-15 times per the Dagarlas website (I'm glad the up arrow brings the previous command in linux!).

Still didn't have any luck. I used idchanger with the read command and the values haven't changed.

I will try bringing the card to work tomorrow.

I bought my T30 when they were coming off lease. There were at least 20 of us that bought one at the same time.

There are still a few that I can use to see if a different laptop makes a difference.

It's strange that you own the same card and can make it work...

Thanks again!

[danage]

Code: Select all

idchanger -w 0xd0200000 0x0013 ox168c 0x0408 0x1468 

This is correct. If it fails, there is 99% certainty that the cards' EEPROM is write protected. IMO it's of no use trying it in another computer.

It's strange that you own the same card and can make it work...

I agree. They must have changed revisions. Could you provide a lspci -n dump here? You can dump the output to a file running lspci in the floppy directory by typing

Code: Select all

lspci -n >output.txt

can some one guide me trough this?

These procedures involve some serious hardware hacking that can permanently damage your system. If you are not familiar with the steps I highly recommend finding an alternate solution since it might not be revertable.

[KF9YR]

Hi,

I think you are correct. This did not work in another T30 at work this morning.

I ran both lspci -n and lspci -nv and here are the results:

Output of lspci -n

00:00.0 Class 0600: 8086:1a30 (rev 04)
00:01.0 Class 0604: 8086:1a31 (rev 04)
00:1d.0 Class 0c03: 8086:2482 (rev 02)
00:1d.1 Class 0c03: 8086:2484 (rev 02)
00:1d.2 Class 0c03: 8086:2487 (rev 02)
00:1e.0 Class 0604: 8086:2448 (rev 42)
00:1f.0 Class 0601: 8086:248c (rev 02)
00:1f.1 Class 0101: 8086:248a (rev 02)
00:1f.3 Class 0c05: 8086:2483 (rev 02)
00:1f.5 Class 0401: 8086:2485 (rev 02)
00:1f.6 Class 0703: 8086:2486 (rev 02)
01:00.0 Class 0300: 1002:4c57
02:00.0 Class 0607: 104c:ac55 (rev 01)
02:00.1 Class 0607: 104c:ac55 (rev 01)
02:02.0 Class 0200: 168c:1014 (rev 01)
02:08.0 Class 0200: 8086:1031 (rev 42)

Output of lspci -nv

00:00.0 Class 0600: 8086:1a30 (rev 04)
Flags: bus master, fast devsel, latency 0
Memory at e0000000 (32-bit, prefetchable)
Capabilities: [e4] #09 [d104]
Capabilities: [a0] AGP version 2.0

00:01.0 Class 0604: 8086:1a31 (rev 04)
Flags: bus master, 66Mhz, fast devsel, latency 96
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 00003000-00003fff
Memory behind bridge: d0100000-d01fffff
Prefetchable memory behind bridge: e8000000-efffffff

00:1d.0 Class 0c03: 8086:2482 (rev 02)
Subsystem: 1014:0220
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1800

00:1d.1 Class 0c03: 8086:2484 (rev 02)
Subsystem: 1014:0220
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1820

00:1d.2 Class 0c03: 8086:2487 (rev 02)
Subsystem: 1014:0220
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1840

00:1e.0 Class 0604: 8086:2448 (rev 42)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=08, sec-latency=168
I/O behind bridge: 00004000-00008fff
Memory behind bridge: d0200000-dfffffff
Prefetchable memory behind bridge: f0000000-f7ffffff

00:1f.0 Class 0601: 8086:248c (rev 02)
Flags: bus master, medium devsel, latency 0

00:1f.1 Class 0101: 8086:248a (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: 1014:0220
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at 1860
Memory at 20000000 (32-bit, non-prefetchable)

00:1f.3 Class 0c05: 8086:2483 (rev 02)
Subsystem: 1014:0220
Flags: medium devsel, IRQ 11
I/O ports at 1880

00:1f.5 Class 0401: 8086:2485 (rev 02)
Subsystem: 1014:0508
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1c00
I/O ports at 18c0

00:1f.6 Class 0703: 8086:2486 (rev 02)
Subsystem: 1014:0223
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 2400
I/O ports at 2000 [size=128]

01:00.0 Class 0300: 1002:4c57
Subsystem: 1014:0517
Flags: bus master, stepping, fast Back2Back, 66Mhz, medium devsel, latency 66, IRQ 11
Memory at e8000000 (32-bit, prefetchable) [size=128M]
I/O ports at 3000 [size=256]
Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2

02:00.0 Class 0607: 104c:ac55 (rev 01)
Subsystem: 1014:0512
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at 50000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=03, subordinate=05, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001

02:00.1 Class 0607: 104c:ac55 (rev 01)
Subsystem: 1014:0512
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at 51000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=06, subordinate=08, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001

02:02.0 Class 0200: 168c:1014 (rev 01)
Subsystem: 1014:057e
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at d0200000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2

02:08.0 Class 0200: 8086:1031 (rev 42)
Subsystem: 1014:0209
Flags: bus master, medium devsel, latency 66, IRQ 11
Memory at d0210000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 8000 [size=64]
Capabilities: [dc] Power Management version 2

[cage]

I got this working thanks to yahoo's cache providing a usable link to idchanger.c