On Wed, 10 Jun 2020 at 11:55, Richard Shaw <hobbes1069(a)gmail.com> wrote:
So the short version...
The current linux firmware package doesn't work with the Wifi on the MS
Surface GO, and the instructions to copy the downloaded board.bin and copy
over firmware-4.bin were incorrect. It actually saw the Wifi adapter after
I did that and it tried scanning for wireless networks but never got any
further.
Since the Killerwifi board.bin and the linux firmware board.bin were the
exact same size (whereas the firmware files were orders of magnitude
larger), I tried replacing board.bin instead and can report after rebooting
that the Wifi now works.
Did you try a newer file from the githhub link? Are there any license
restrictions on Killerwifi's board.bin that prevent you from sending the
link to the upstream URL I posted.
So one thing I am wondering is what is the naming convention for these
files? Could I just save it as board-2.bin and it work? Is there some sort
of search hiearchy?
From what I can tell it looks like udev takes care of it but I don't know
enough about udev to intuit what kind of naming scheme might work without
overriding the existing board file.
The best outcome would be to get upstream to add support for the
"Killerwifi" board (if they don't already have by now) so you don't have
to
worry about losing wifi with each update.
--
George N. White III