You are spot on … this is where I left off the other night. I was trying to use mix nerves.system.shell to get a shell booted up to reconfigure the kernel but was running into a bug w/ the docker invocation.

So turns out my stuff was actually working correctly. The issue was that the disable-wifi.dtbo file did not exist on my device. Once I was able to do that by adding the correct lines to my fwup.conf. Here is a diff between my file and the factory rpi4 one:

103c103
<     host-path = "${NERVES_SYSTEM}/images/config.txt"
---
>     host-path = "${NERVES_APP}/config/config.txt"
128a129,131
> file-resource disable-wifi.dtbo {
>     host-path = "${NERVES_SYSTEM}/images/rpi-firmware/overlays/disable-wifi.dtbo"
> }
230a234
>     on-resource disable-wifi.dtbo { fat_write(${BOOT_A_PART_OFFSET}, "overlays/disable-wifi.dtbo") }
294a299
>     on-resource disable-wifi.dtbo { fat_write(${BOOT_A_PART_OFFSET}, "overlays/disable-wifi.dtbo") }
361a367
>     on-resource disable-wifi.dtbo { fat_write(${BOOT_B_PART_OFFSET}, "overlays/disable-wifi.dtbo") }

Going to jump back into that now with trying to get the driver added to the device.

I think that I have two options:

• Copy the .dtbo file and load it manually for my Wifi Adapter
• Reconfigure the kernel to enable the correct module (I believe the support for this chip exists natively in Linux)

The chipset in this device is the Ralink RT5370.

Here is a link from the Debian project for what I believe is the driver: I Challenge Thee

This is kind of a thread-jack at this point but I will report back my findings in case someone else is running into a similar issue.

All of this huge yak shave just to get a different wifi adapter running so I can remote debug while my device is outside (doing some GPS stuff).