Stefan Sperling <s...@stsp.name> wrote: > On Mon, Oct 18, 2021 at 07:14:57PM +0200, Richard Ulmer wrote: > > > Something else you could try is downgrading the firmware image. > > > This can be done without patching the kernel by swapping out the > > > firmware file: > > > > > > mv /etc/firmware/iwm-7265D-29 /etc/firmware/iwm-7265D-29.orig > > > cp /etc/firmware/iwm-7265-17 /etc/firmware/iwm-7265D-29 > > > > > > The 7265-17 image was used in OpenBSD 6.9. > > > The 7265D-29 image is used in OpenBSD 7.0. > > > > > > -current now defaults to the 7265-17 again, because we found out (a bit > > > too late for the release) that the 7265D-29 firmware was causing issues. > > > > I did this and my WI-FI seems to be stable again. Thanks a lot! > > OK, good to know. > > 7265D works with the linux iwlwifi driver and it worked fine when I tested > it with 7265 iwm(4) in an x250 thinkpad with a pepwave access point. Later, > some people reported various failures that all looked slightly different. > It took a while until Landry bisected the problem down to the change in > firmware version. The original problem reports we received looked like > badly connected antennas, hardware issues, or 802.11 protocol interop > problems, and all this led us down several wrong paths in our investigation. > Which is why it took some time until this workaround was found. > > > > Please try a -current kernel. There have been several improvements since > > > the 7.0 release tag. Perhaps your problem has already been fixed? > > > > > > If the problem still occurs, please enable 'ifconfig iwm0 debug' and > > > wait for it to trigger again. The driver should then print additional > > > messages to /var/log/messages providing more context about the error. > > > > I have never set up a -current OpenBSD, so I'm not comfortable with > > this. Sorry. I could however try to catch the error with 'ifconfig iwm0 > > debug' enabled. Would that help you, even if I'm not on -current? > > Not really. There is nothing the driver does differently so any failure > messages we can see in dmesg will just be a symptom of the underlying issue. > Somehow 7265D firmware is unhappy with our driver in some cases. > It's not high on my list of things to fix, given that development time is > always limited, a workaround is known, and there are more interesting > problems to solve. But it would be good to fix this eventually, since the > 7265D firmware looks better on paper since it has received more maintenance > from Intel than the older ones, which might include security fixes for > all we can tell (intel doesn't publish any wifi firmware changelogs).
OK, thanks for the info and thanks for your work! I'll leave the problem be for now, since the workaround works well for me. If I happen to set up a -current installation in the future, I'll give 'ifconfig iwm0 debug' a shot and let you know.
