So, do you have any plan to release new version including missed Ralink firmware for C1+?
Regards,
Yes, but please don’t fish for dates.
I don’t like giving them to avoid disappointing people when I miss them.
Okay, I’ll monitor your update sometimes.
Hi,
Just a simple question:
Can I use any Volumio supported Raspberry Pi HATs on my Odroid C2?
Thanks!
nope, because hardkernel chose to use a different approach to the 40-pin gpio. It is not compatible with an RPi. I2S signals are only on the 7-pin (J7) audio header.
You can use some (simple) dacs as long as you don’t need i2c for them, but you still have to wire them from J7. And select odroiddac, not odroiddac2!!!
1 Like
Thanks!
I can just select these DAC-s on my C2. I guess for the I2S connected DAC should be the HiFi Shield/Shield+ selected.
Am I right? (The Shield DACs aren’t communicate with I2C)
Correct, the HiFi Shield 2 would be the one with I2C and for the C2 this means a customized pcm5121 codec. Instead you need to use the one shown (Shield/Shield+), it will use the pcm5102a codec, which is fine for a simple DAC without volume control.
1 Like
Thanks! 
See Opening Post
Odroid C1/C1+ v3.205 and C2 v3.206 are ready with Ralink firmware support.
Note: this is a community porting, so you will need to test it yourself as I don’t have Ralink devices other than a RT5370.
Kernels are ancient, so hot plug may not work, please boot with wifi device connected.
Let me know if something’s not working, I’ll see to it.
@all, this also includes Volumio updates <= 3.198
Thank you for providing new version.
I found that wifi is not working when I tried to choose an AP.
There was no AP list on the setup UI.
The firmware was detected, but wlan0 was disabled.
So, I tried to enable Wireless Networking in Settings, but it was not working as well.
Jan 27 14:13:00 volumio kernel: ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file ‘rt2870.bin’
Jan 27 14:13:00 volumio iptables[482]: iptables v1.8.2 (nf_tables): unknown option “–dport”
Jan 27 14:13:00 volumio iptables[482]: Try `iptables -h’ or ‘iptables --help’ for more information.
Jan 27 14:13:00 volumio kernel: ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
Jan 27 14:13:34 volumio systemd[1]: Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jan 27 14:13:34 volumio hostapd[1521]: Configuration file: /etc/hostapd/hostapd.conf
Jan 27 14:13:34 volumio hostapd[1521]: Could not read interface wlan0 flags: No such device
Jan 27 14:13:34 volumio hostapd[1521]: nl80211: Driver does not support authentication/association or connect commands
Jan 27 14:13:34 volumio hostapd[1521]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Jan 27 14:13:34 volumio hostapd[1521]: Could not read interface wlan0 flags: No such device
Jan 27 14:13:34 volumio hostapd[1521]: nl80211 driver initialization failed.
Jan 27 14:13:34 volumio hostapd[1521]: wlan0: interface state UNINITIALIZED->DISABLED
Jan 27 14:13:34 volumio hostapd[1521]: wlan0: AP-DISABLED
Jan 27 14:13:34 volumio hostapd[1521]: wlan0: CTRL-EVENT-TERMINATING
Jan 27 14:13:34 volumio hostapd[1521]: hostapd_free_hapd_data: Interface wlan0 wasn’t started
log : http://logs.volumio.org/volumio/1k6J4GO.html
From the log on v2.916, firmware version was 0.29 as below.
[ 61.638274] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file ‘rt2870.bin’
[ 61.649633] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
Would you let me know if there is any solution?
Are these update OTA, as I’m not seeing any option to update.
Yes, you can use OTA.
In case of community portings, you must always be in test mode (via the “volumio.local/dev” page).
This differs from the handling of officially released Volumio images.
Gottcha, thanks.
Thanks for the full log link, the extract you gave does not show the vital issue.
It’s not iptables…
The problem is here
# ifconfig ---------------
eth0: flags=4163 mtu 1500
inet 172.16.11.147 netmask 255.255.255.0 broadcast 172.16.11.255
ether 00:1e:06:20:00:45 txqueuelen 1000 (Ethernet)
RX packets 4659 bytes 475690 (464.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5062 bytes 3866727 (3.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Local Loopback)
RX packets 1337 bytes 152697 (149.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1337 bytes 152697 (149.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlx00266641da97: flags=4099 mtu 1500
ether 00:26:66:41:da:97 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The wifi device shows up as “wlx00266641da97” instead of “wlan0”, Volumio only handles wlan0.
I forgot an import addition to the kernel command line parameters for the C1: net.ifnames=0.
Could you add this to your “bootargs” parameter in “/boot/boot.ini” so that it looks like this:
setenv bootargs "net.ifnames=0 console=ttyS0,115200n8 console=tty0 rootwait rw no_console_suspend vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs} ${enabledac} imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh"
I quickly added it and the Ralink RT5370 dongle now starts in AP mode as expected and can be connected to wifi networks.
Thank you for your quick response.
The iptables log were just copied, not the issue.
I’ll update with the guide you mentioned when i get a chance after work.
Regards,
And the N2+
You already have a working Volumio 3 for N2+ 
Rebuilding all current Volumio 3 portings was not planned yet.
In view of the fixed issues this appears necessary, but will have to wait a little.
1 Like
Adding net.ifnames=0 to boot.ini is working.
However, I couldn’t get https://updates.volumio.org/odroidc1/volumio/3.206/Volumio-3.206-2022-01-27-odroidc1.zip at now, found 404 error.
Thanks,