Hello gkkcph,
A first feedback of a quick test of your “4.12.8” release on a J4205-ITX. As your previous one, the boot stops at login, no user interface available on PC. Need to use network and html to get UI. Except this, all seems to work. But need more test, and specially comparing with current version (on a no Apollo lake µP). The test was with Xmos USB interface (U208) and UD501 DAC in SPDIF.
Hi,
see here my Intel® NUC-Kit NUC6CAYH. (Intel® Celeron® Processor J3455)
works with volumio 2.201 out of the box, only internal wlan is not recognised.
i like the size! (much smaller than ITX Boards)
cost are:
120€ for the nuc kit,
30€ for 4GB DDR3L,
30€ transcend ssd370s 32gb,
10€ WLAN Stick
Booting takes longer than with my pi, also much longer than my ITX (x86) setup, maybe because of the internal wlan.
i was right.
After removing the internal wlan from M.2 port volumio starts in ~36 sec. from button to start melodie.
updating to 2.256 works too.
what a nice toy…
as I can add drivers on 4.9.x/ 4.10 (not sure yet which version we will support), provided they are available, I’m interested to know which pcie wlan module you used.
I made sure to select all supported usb wlan dongles, but may not have included all pcie cards.
Thanks - Gé
thanks for the info, the firmware microcode for a 3168NGW appears to be missing, if you do dmesg it probably shows.
This is caused by the Debian jessie intel wifi firmware package which gets installed during the Volumio build.
Debian jessie is based on kernel version 3.18.x and only covers firmware available at the time, I do not expect it gets updated for newer devices.
This means more firmware code for newer intel devices is missing in Volimio 2.256, but when we switch to Debian stretch this should be solved.
To get it to work with Volumio version 2.256 now, would require you to download the firmware from Intel’s website: https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-3168-ucode-22.361476.0.tgz
Then unpack and copy the contained folder straight into /lib/firmware.
Then you should have
/lib/firmware/iwlwifi-3168-ucode-22.361476.0
with the microcode file
iwlwifi-3168-22.ucode
file in it , incl. a license and README.
Edit: Yes, just confirming support is in Debian stretch package “firmware-iwlwifi”
Thank you very much for the instruction and information gkkpch.
For me it’s easier to wait for the upcoming kernel Version, because the usb wifi works fine.
greetings
I am experimenting with the Intel® NUC-Kit NUC6CAYH. (Intel® Celeron® Processor J3455): what Volumio image should I use? The official version from the download area boots up, but then stops complaining that no console is available and the web interface doesn’t start (I used the wired network).
hi roberto,
i have the same nuc kit.
take the 2.201 image from download.
deactivate in bios (F2) the internal wlan. in boot option choose linux.
that should be all. if you connect a monitor to hdmi you can see the boot prozess… and the ui too.
tip: take only the official updates, not the dev ones
good luck
I find out that the problem is related to the boot from the SD card. If I attach the same SD card to the NUC using a USB card reader, it boots and run, but if I try to boot directly from the SD card inserted in the SD card slot of the NUC, it fails, because Linux doesn’t find the UUID of the root and the boot filesystems or partitions; the message is
findfs unable to resolve uuid CC23-EE0D
findfs unable to resolve uuid 6c0d3184-7851-46c3-919b-ed4c1d379708
Searching a little, I found, in the Intel site, this note:
Intel® NUC products don't support booting from SD cards. We have no plans to add this capability.
I downloaded the firmware and copied it to the Intel NUC NUC6CAYH (it was a little bit tricky, because you cannot ftp as root): now the wireless card works and the hot spot was activated at the first boot after copying the firmware. Then I connected to my wireless network and it worked, too.
Roberto,
could you also produce a log with both 2.201 and 2.256 for me, using the log option on the dev page?
It may point me in the right direction for solving the graphics problem on this NUC (older NUCs work).