I just purchased an Intel NUC, because it says Intel NUC supported.
I am using the latest dev image.
Using Wifi internal does not work (Intel® Wireless-AC 3168 M.2).
How can I fix this with Wifi? I would like to use wifi-connect with this one.
Thank you
I switched off the device and rebooted, and now I have to devices in the dashboard. It says online, but I cant access the device. Rebooted again. I receive a 3rd device in the dashboard It is also not showing any IP.
I changed the HDD inside, now I reach post-provisioning stage. I removed the USB pen. Restarted. But it will not change the state to online.
Inside I am stuck at the command
Mounting resin inactive root partition mountpoint…
EXT4-fs (sda3): mounted filesystem wirth ordered data mode. Opts: (null)
I even copied all ucodes for 3168 from git linux firmware repo.
It won’t move.
If I plug in the LAN connection and reboot. The device provisions! So it has to do with the Wifi something I believe.
STATUS boot from HDD (Post provision finished with LAN connection) Wifi is not being detected (even in ifconfig host os shell)
@floion I have added all files containing iwlwifi 3168 ucode files to /lib/firmware. It will not provision via wifi. Is there a special resin firmware for this?
Yes, that should work.
I checked the linux-firmware version we have for the Intel NUC now and apparently there is also a newer firmware: iwlwifi-3168-27.ucode
You could try to package that one like you showed above. If that works, maybe you could consider doing a pull request in the resin-intel repository? I opened an issue to track this request yesterday: https://github.com/resin-os/resin-intel/issues/107
Also, do you build using barys “-d” build switch? If not, can you add that flag? It is the development flag which allows console login to the OS so you can login and we can check what failed eventually
@jgentes which version was the one that previously worked for you?
And when you say you had to use non-wifi to get it provision, what were the exact symptoms? Did it never show up in the dashboard if you only had the wifi configured (no eth plugged in) but did it automatically shutdown after the first boot? (that is the boot where it should install resinOS to internal storage and then just shutdown)
Ok, if everything runs, I will make a pull request.
So, after like 20h I managed to create a successful image. Settings up balena daemon with permissions.
I used ./barys -d. Do I need the -resinio flag, too?
I received multiple files inside the /build folder.
I copied (replaced) the resin-img file which I have built, with the one inside /opt/ of my USB stick.
So I flashed the USB to my HDD. Removed the USB and booted up using the HDD (Post-provisioning). From the logs I see that WIFI is now being accepted.
Now it is stuck at
> [OK] Reached target Sockets.
I rebooted again.
Now it is stuck at
> EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
If you want a resin.io managed image, then you need to build using the “–resinio” flag.
You should burn to the USB stick the following image file (and more exactly, the image file that this points to):
I copied build/tmp/deploy/images/genericx86-64/resin-image-flasher-genericx86-64.resinos-img
to a new folder and rename.resinos-img to .img (So that etcher can load it). Burn to USB.
Copying to USB Stick manually:
Next I placed myiwlwifi-3168-22.ucode file into /lib/firmware
I placed resin-wifi01 from my preconfigured image into the newly baked one system connections folder.
Same thing I did for placing the config.json file of the preconfigured image to my newly baked one.
Boot up with USB Stick. Shutsdown, but does not show the device on the dashboard. No post-provisioning.
Remove the USB Stick. Boot from HDD.
Halts at following message:
> [OK] Started Config.json path watch
> Starting Docker Socket for the API.
> usb 1-8: new full-speed USB device number 8 using xhci_hcd
One thing first. If you build it with the changes you mentioned above, you should already have that firmware in there. Did you not build it with your changes?
Second, can you disable resin-init-flasher.service from running? You could delete the symlink from the USB stick that makes it run or just rename the script so the service does not execute it. Mount the USB thumb drive on your computer and rename the script
<USB stick mount location>/usr/bin/resin-init-flasher
to something else.
Then boot with the USB stick again. It won’t provision this time but it won’t shutdown either so you can press CTRL + ALT + F2 and get to a login prompt if it is a development image.
Once you login, wait a half a minute to a minute to give the vpn service some time to auth. Then execute
journalctl --no-pager -u openvpn-resin
and paste the output here.
Also, check with
ifconfig
if there is any wifi interface with IP assigned. If not, run
journalctl --no-pager -u NetworkManager
and paste the output here while also double checking that the resin-wifi01 file is present in
/mnt/boot/system-connections/
and has the correct credentials (don’t paste that file here as it has your wifi credentials)
One thing first. If you build it with the changes you mentioned above, you should already have that firmware in there. Did you not build it with your changes?
@floion I think it was the previous rev (2.7.8)… I just tried it again and it did shutdown properly and I rebooted as with a normal provisioning, but it just never shows up on resin.io