Issue with wpi firmware

[jenright]

I have an old Dell Latitude D420 laptop that I'm trying to get a wireless card working on. I couldn't get an ethernet cord to work either, so just using one temporarily with fw_update isn't an option. After putting the file on a SD card and mounting/changing directory, using pkg_add renders the following:

# pkg_add wpi-firmware-3.2p1.tgz
Fatal error: Ustar [file:./wpi-firmware-3.2p1.tgz] [?]: Not an ustar archive header 
at /usr/libdata/per15/OpenBSD/Ustar.pm line 89.

I tried the older versions of the firmware and got the same error. Any advice to get it working?

It might also be worth noting that the byte size for the file in the 5.6 folder on the OpenBSD firmware site is 65935, but in the old folder it's 65976 (41 bytes larger). I got the same error message with both versions, however.

[albator]

The man page of fw_update(1) says:
The files are in the format required by pkg_add(1), but direct use of pkg_add is discouraged.
-p path
Use the firmware found at path, being either a local directory or a URL, instead of the default location.

Do you get an error when listing the content of the archive?

# tar tvzf wpi-firmware-3.2p1.tgz

By the way, there is an error in your error message ;-)

Originally Posted by jenright

Not an ustar archive header at /usr/libdata/perl15/OpenBSD/Ustar.pm line 89.

[jenright]

1. For pkg_add, I was using it locally. If I was able to get ethernet working, I would have just used fw_update like the man page says.

2. The tar tvzf code reported the following:

# tar tvzf wpi-firmware-3.2p1.tgz
tar: Cannot identify format. Searching...
tar: Cpio file name length 48031 is out of range
tar: Invalid header, starting valid header search.
tar: End of archive volume 1 reached

3. The other error message I posted had 'per15' as one word with no slash after 'per'.

[jggimi]

Hello, and welcome.

What checksum tests have you run against http://firmware.openbsd.org/5.6/wpi-firmware-3.2p1.tgz to confirm you have obtained the file without error?

My quick test of this file:

MD5: 5D1A2FD85A8AB4624CDB2E174538E159
SHA1: 036164CA39A379A7B0732CBBB6D14F97C7ED380C
SHA256: F37146C1247F58FB20CD414850195C9C36D0F98B0931B40945 DDE3EC6571FE09

[albator]

Originally Posted by jenright

If I was able to get ethernet working, I would have just used fw_update like the man page says.

And the man page says... You can use "either a local directory or a URL".
But obviously the file you downloaded is not correct.

[jggimi]

That was my guess; hence my recommendation to checksum. Either the file is not being obtained without errors, or the wrong file is being obtained. The Project's packaged firmware files should all be acquired from http://firmware.openbsd.org.

[jenright]

Thanks jggimi. I noticed that the MD5 on the last file was wrong, so I downloaded it again and got the correct MD5, SHA1 and SHA256 hashes. However, I got another error as follows:

# pkg_add wpi-firmware-3.2p1.tgz
Package signed by untrusted party openbsd-56-fw
Fatal error: wpi-firmware-3.2p1 is corrupted
at usr/libdata/per15/OpenBSD/PkgAdd.pm line 696.

Any ideas this time? Let me know if I need to provide more information.

[jggimi]

Don't use pkg_add(1). With the advent of signed systems, there are three different sets of signatures used: base system, packages, and firmware.

Use fw_update(1) with the -p option, as previously advised.

[jenright]

I tried the following:

# mount -t msdos /dev/sd0i /mnt/flashmem
# fw_update -p /mnt/flashmem/wpi-firmware-3.2p1.tgz

and didn't get any error messages (or messages of any sort) when I hit enter. When I rebooted, it still had the following error as part of the bootup dmesg:

wpi0: error, 2, could not read firmware wpi-3945abg
wpi0: could not read firmware
wpi0: no link ........... sleeping

It seems like it should be working now, so is there anything else missing? I turned the switch on the side of the laptop for wireless on and still got this error. Thanks to all for the help so far.

[jggimi]

You didn't run fw_update(1) with the correct syntax. It's not the same as pkg_add(1). It's -p path [driver]. Example:

# fw_update -p /mnt/flashmem wpi

You can add -v one or more times for detailed output.

# fw_update -vp /mnt/flashmem wpi

[jenright]

Okay, that fixed it. Thanks again for all your help.