IBM ThinkPad A31p – wifi trouble

Forum Forums New users New Users and General Questions IBM ThinkPad A31p – wifi trouble

  • This topic has 92 replies, 7 voices, and was last updated Jan 5-6:27 pm by Xecure.
Viewing 15 posts - 61 through 75 (of 92 total)
  • Author
    Posts
  • #48967
    Member
    XecureXecure

    It is oK now. I think we can do all the updating from the installed antiX 19 system.

    Sorry for making you go around in circles. I was so focused that the package wasn’t in the repositories that I didn’t try installing it myself on a more updated system. With the last instructions now you can test things on your own installed system.

    I will be online for an hour or so more, so if you can follow the steps during this time, I will answer any question you have.

    #48968
    Member
    AvatarBruceW

    OK. I overcomplicated things.

    Working on this one…

    Hey, with all the work you’ve been doing on my behalf, I’ve got to see this thing through, now.

    • This reply was modified 3 months, 1 week ago by BruceW.
    #48969
    Moderator
    Brian MasinickBrian Masinick

    Great! Glad it is now working!

    Brian Masinick

    #48973
    Member
    AvatarBruceW

    prism2_srec -v wlan0 PK010101.HEX SF010802.HEX

    Regarding Plugging PDR, several places where it says something like the following (first of seven instances):

    Plugging PDR 0x0005 at 0x007e1310 (len=2)
    PDR 0x0005 not found from wlan card PDA. Using default data.
    len=2: 00 01

    Assuming len means length.
    In one place, it says:

    Plug record length mismatch (PDR=0x0001): 12 != 16

    At the end of the output, it says:

    Could not find data position for plugging PDR 0x0413 at 0x0000118a (len=2)
    PDR 0x0413 is not in wlan card PDA and there is no default data. Ignoring plug record.
    Generating CRC-16 (start=0x007e1800, len=65536) at 0x007e17fe
    Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
    After srec file merge
    S3 area count: 5
    addr=0x007E0000..0x007E0B55 (len=2902)
    addr=0x007E0C00..0x007E151F (len=2336)
    addr=0x007E17FE..0x007EEAEF (len=54002)
    addr=0x007F0800..0x007F17FF (len=4096)
    addr=0x007FE000..0x007FECD1 (len=3282)
    Total data length:66618
    OK.
    root@antix1:/home/Bruce/Downloads#

    Looking back up toward the beginning (before the file merge), I found:

    Separate S3 data areas:
    S3 area count: 3
    addr=0x007E0000..0x007E0B55 (len=2902)
    addr=0x007E0C00..0x007E151F (len=2336)
    addr=0x007E17FE..0x007E17FF (len=2)
    Total data length: 5240

    So the file gets bigger, assuming there’s space for it. Are we compatible?

    • This reply was modified 3 months, 1 week ago by BruceW.
    • This reply was modified 3 months, 1 week ago by BruceW.
    • This reply was modified 3 months, 1 week ago by BruceW.
    #48981
    Member
    XecureXecure

    This is the output it gives on my non-PRISM system:

    root@antix1:/home/demo/Downloads# prism2_srec -v wlan0 PK010101.HEX SF010802.HEX
    S3 CRC-16 generation record: start=0x007E17FE len=2 prog=0
    Start address 0x00000000
    srec summary for PK010101.HEX
    Component: 0x0015 1.1.1 (primary firmware)
    Supported platforms:
      0x800c 1.0.0,  0x8013 1.0.0,  0x8017 1.0.0,  0x801b 1.0.0,  0x8022 1.0.0
    Interface compatibility information:
      role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver (3)
      role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
    Separate S3 data areas:
    S3 area count: 3
      addr=0x007E0000..0x007E0B55 (len=2902)
      addr=0x007E0C00..0x007E151F (len=2336)
      addr=0x007E17FE..0x007E17FF (len=2)
    Total data length: 5240
    Start address 0x00000000
    
    S3 CRC-16 generation record: start=0x007E1800 len=65536 prog=1
    Start address 0x00000000
    srec summary for SF010802.HEX
    Component: 0x001f 1.8.2 (station firmware)
    Supported platforms:
      0x800a 1.0.0,  0x800b 1.0.0,  0x800c 1.0.0,  0x800d 1.0.0,  0x8012 1.0.0
      0x8013 1.0.0,  0x8014 1.0.0,  0x8016 1.0.0,  0x8017 1.0.0,  0x8018 1.0.0
      0x801a 1.0.0,  0x801b 1.0.0,  0x801c 1.0.0,  0x8021 1.0.0,  0x8022 1.0.0
      0x8023 1.0.0
    Interface compatibility information:
      role=Supplier variant=2 range=1-15 iface=Station Firmware-Driver (4)
      role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
      role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
      role=Actor    variant=1 range=4-4 iface=Primary Firmware-Driver (3)
    Separate S3 data areas:
    S3 area count: 3
      addr=0x007E1800..0x007EEAEF (len=54000)
      addr=0x007F0800..0x007F17FF (len=4096)
      addr=0x007FE000..0x007FECD1 (len=3282)
    Total data length: 61378
    Start address 0x00000000
    
    ioctl[PRISM2_IOCTL_HOSTAPD]: No such device
    Missing wlan component info
    Could not read wlan RIDs

    Mine does not say OK, because it is not a PRISM chip. My guess is that the HEX files didn’t download properly (check file size
    PK010101.HEX : 16652 bytes
    SF010802.HEX : 185936 bytes
    If they are not this size on your computer, download again.

    But, let us analyze a bit of the previous info we got from other outputs I requested:
    dmesg output:

    [ 23.092066] wifi0: NIC: id=0x8013 v1.0.0
    [ 23.093062] wifi0: PRI: id=0x15 v1.0.0
    [ 23.093214] wifi0: STA: id=0x1f v1.4.2

    Where we have two important parts. The NIC id: id=0x8013 v1.0.0 (lets remember this), and the current station firmware version v1.4.2

    So, does your output state?:

    srec summary for PK010101.HEX
    Component: 0x0015 1.1.1 (primary firmware)
    Supported platforms:
    0x800c 1.0.0, 0x8013 1.0.0

    If it does, then the first file PK010101.HEX is compatible with your chip-

    Also, you should be able to see in the output:

    srec summary for SF010802.HEX
    Component: 0x001f 1.8.2 (station firmware)
    Supported platforms:
    0x800a 1.0.0, 0x800b 1.0.0, 0x800c 1.0.0, 0x800d 1.0.0, 0x8012 1.0.0
    0x8013 1.0.0,

    also stating that this firmware file is compatible with your chip (identified as 0x8013 1.0.0).

    If you see both in the output, then the firmware files should work. If there is an error in the size of the firmware files, then they may have not downloaded correctly. Remove them from the downloads folder and try downloading them again.

    • This reply was modified 3 months, 1 week ago by Xecure. Reason: correct summary
    #48986
    Member
    XecureXecure

    From your output:

    Separate S3 data areas:
    S3 area count: 3
    addr=0x007E0000..0x007E0B55 (len=2902)
    addr=0x007E0C00..0x007E151F (len=2336)
    addr=0x007E17FE..0x007E17FF (len=2)
    Total data length: 5240

    Corresponding to PK010101.HEX file, it seems this file downloaded OK (I get the same output result).

    But, the ending output (where you get the error):

    3 area count: 5
    addr=0x007E0000..0x007E0B55 (len=2902)
    addr=0x007E0C00..0x007E151F (len=2336)
    addr=0x007E17FE..0x007EEAEF (len=54002)
    addr=0x007F0800..0x007F17FF (len=4096)
    addr=0x007FE000..0x007FECD1 (len=3282)
    Total data length:66618

    My data length (with no errors): 61378 is different to yours. This leads me to believe that the SF010802.HEX did not download correctly. Remove it from the Downloads folder and redownload this file again (and try the command again)

    EDIT: It is really late here, so I am going to bed. If after removing and redownloading the SF010802.HEX file you still get the same error, then I think we will have to leave this project for later, and I will try to find a better way to check for file integrity.

    • This reply was modified 3 months, 1 week ago by Xecure.
    #48989
    Member
    AvatarBruceW

    I have those. Checking file sizes.

    #48990
    Member
    AvatarBruceW

    File sizes match. I’m going to the next step, unless you see some other issue.

    #48991
    Member
    AvatarBruceW

    Success! Should I reboot before trying it?

    #48992
    Member
    AvatarBruceW

    invalid-key… Rebooting.

    #48993
    Member
    AvatarBruceW

    After reboot, it works just fine. Accepted my password and brought up the antixforum web site. Thank you sooooooo much!!!

    #48994
    Member
    AvatarBruceW

    Again, thank you soooooo much, Xecure!!!! This is my first post from my IBM Thinkpad A31p, using WPA2 Security. You made it happen!

    #48995
    Moderator
    Brian MasinickBrian Masinick

    Again, thank you soooooo much, Xecure!!!! This is my first post from my IBM Thinkpad A31p, using WPA2 Security. You made it happen!

    Xecure did some research and great work to make it possible and YOU did the work, learning, following the steps and completing the task.

    I think that both of you were necessary to make sure that this works and you both did a good job and stuck with it.

    Each of you deserve thanks for your roles in making it happen and this is exactly what our community does.

    Congratulations!

    Brian Masinick

    #48996
    Member
    AvatarBruceW

    Thank you for your kind comments, Brian Masinick. For all the work Xecure put into this project, I had to see it through. There was no way I was going to let all his work and research go to waste. I think we all learned from this experience. (Second post from A31p.)

    #48998
    Member
    AvatarBruceW

    I should have said “his or her work…”I really know nothing about Xecure, except that he or she is really devoted and REALLY KNOWS HIS/HER STUFF!!!

Viewing 15 posts - 61 through 75 (of 92 total)
  • You must be logged in to reply to this topic.