Quirk vmm and wifi installation

[stagain]

dear daemonforums!
Thank you for helping new BSD folks like me.
This is the description of what I've done yet:

OpenBSD 6.2 installed by cd0.
I need Wifi
lspci | grep -i wirelessResult: Qualcomm Atheros
downloaded:

athn-firmware-1.1p2.tgz

athn-firmware-1.1p4.tgz

wpa_supplicant-2.6p0.tgz

fw_update athn-firmware

can't find vmm-firmware

fw_update -vvvvv -p vmm-firmware.1.11.0p0.tgz

Installing: vmm-firware
Updating: athn-firmware
Looking for vmm-firmware
can't load quirk: can't locate OpenBSD /Quirks.pm in @INC

Quirks.pm 04/10/18 ->perl file
ports.su/devel/quirks/pkg/DESCR 1.1.1.1 -> quirks txt description
ports.su/devel/quirks/pkg/PLIST 1.3 -> perl config file?
ports.su/devel/quirks/pkg/MAKEFILE -> execute?
Questions:

1. How do I install quirk[s]?

1. Which files do I need for the quirk[s] installation?

1. Which is the correct command to install quirk[s]?

1. If I install quirk[s], will I be able to enable wifi with the downloaded packages? Or do I need index.txt and SHA256.sig?

[jggimi]

Licensed firmware is handled by the fw_update(1) utility. But it uses pkg_add(1), which is used for installing packaged applications that are not included in the base system. The quirks package is a special package used by pkg_add() to handle exceptions to its normal rules, such as when a package changes its name.

The quirks package gets installed automatically along with your very first application package. Until then, you can ignore these messages about the quirks package.

The Package Management chapter of the OpenBSD FAQ may help.
https://www.openbsd.org/faq/faq15.html

[ibara]

Originally Posted by stagain

dear daemonforums!
Thank you for helping new BSD folks like me.
This is the description of what I've done yet:

OpenBSD 6.2 installed by cd0.

I would really push you away from using OpenBSD 6.2 -- if you have to use a release, use 6.3; you may want to consider -current, since it will be very close to 6.4.

Originally Posted by stagain

I need Wifi
lspci | grep -i wirelessResult: Qualcomm Atheros

What does dmesg(8) say about this hardware?

Originally Posted by stagain

downloaded:

athn-firmware-1.1p2.tgz

athn-firmware-1.1p4.tgz

wpa_supplicant-2.6p0.tgz

fw_update athn-firmware

can't find vmm-firmware

fw_update -vvvvv -p vmm-firmware.1.11.0p0.tgz

Installing: vmm-firware
Updating: athn-firmware
Looking for vmm-firmware
can't load quirk: can't locate OpenBSD /Quirks.pm in @INC

Quirks.pm 04/10/18 ->perl file

Originally Posted by stagain

ports.su/devel/quirks/pkg/DESCR 1.1.1.1 -> quirks txt description

No; quirks package description.

Originally Posted by stagain

ports.su/devel/quirks/pkg/PLIST 1.3 -> perl config file?

No; packing list.

Originally Posted by stagain

ports.su/devel/quirks/pkg/MAKEFILE -> execute?

No; port Makefile.

There is missing information here. Do you have Internet access via Ethernet? Do you have no Internet access at all on this machine?

Originally Posted by stagain

Questions:

1. How do I install quirk[s]?

You should not. At least, you should not manually. The package mechanism will do the right thing automatically.

Originally Posted by stagain

1. Which files do I need for the quirk[s] installation?

The quirks package.

Originally Posted by stagain

1. Which is the correct command to install quirk[s]?

You should not do this manually.

Originally Posted by stagain

1. If I install quirk[s], will I be able to enable wifi with the downloaded packages? Or do I need index.txt and SHA256.sig?

The quirks package has nothing to do directly with your wifi issue.

What dmesg(8) says about your hardware is needed to give you an answer.

[stagain]

No Ethernet available, no internet OpenBSD install.

I do have dual boot and my second, nonBSD OS works fine with Wifi without Ethernet.

for dmesg:
vendor "atheros", unknown product not configured. the output is huge though.

It is possible to install quirks manually, good news.
How can I install quirks manually?
Thank you both for the answers.

[ibara]

Originally Posted by stagain

for dmesg:
vendor "atheros", unknown product not configured. the output is huge though.

This means that OpenBSD doesn't recognize the hardware. There's nothing you can do to get this hardware working, save for writing a driver for it (I'm assuming this is ath10k hardware, where OpenBSD only supports ath9k hardware).

[stagain]

If you know a way to install quirks, please let me know.
Giving up is not an option here

[ibara]

Already answered above. Install the quirks package. You still should not do this manually.

[PapaParrot]

for dmesg:
vendor "atheros", unknown product not configured. the output is huge though.

This is no problem, we all know the out put will be long.

ibara >>(I'm assuming this is ath10k hardware, where OpenBSD only supports ath9k hardware).

Ibara, is much more expert then me, so I take his word for it, however "assumptions" are some times wrong, but this is why we need the full dmesg out put.
If the hardware is not supported, installing quirks will not change that.
It is a positive attitude, to not give up, but at the same time, it is not very logical to keep trying something that is not possible, over and over.
You mention the other OS, but not what it is, but you do say it has wifi ? And did you follow the earlier advice, to at least use OpenBsd 6.3 ?
My thoughts, since you are new to OpenBsd, and maybe new to any Unix like system, If this mysterious "other OS" supports a Virtual Machine of some sorts, set up a good VM within your working OS, install OpenBsd to that, you will, or should be able to use the wifi from the other OS, from the VM, exactly how to do that will depend on what Virtual software use, any way Open BSD works very well on a VM , in a virtual environment, and it will give you a chance to get more familiar with how it all works, etc. For now that is all from me.

[jggimi]

Originally Posted by stagain

If you know a way to install quirks, please let me know.

Quirks is not the problem. Firmware is not the problem. The problem is an unsupported hardware component with OpenBSD 6.2. The "not configured" message in your dmesg output indicates the Atheros hardware has no driver.

OpenBSD 6.2 is now a year old, and will be unsupported when OpenBSD 6.4 is released, which will happen any time within the next 2 or 3 weeks. Releases are fixed, no new hardware support is possible with 6.2.

Giving up is not an option here

Good. Attempt to install a snapshot, which as noted will be close to 6.4 when it is released.

• If your Atheros NIC starts working, it should also work with 6.4.
• If your Atheros NIC remains "not configured" then you know your hardware is still not yet supported.