Wireless on Cubox-i4pro with Volumio v1.4

Help and Support Help
1

Has anyone out there had any luck getting wifi to work using the new v1.4 on their Cubox-i? It’s almost as if the kernel modules are missing or havent been compiled. I don’t see anything in dmesg either. Version 1.2beta worked like a treat. For now, I’ve had to revert back to the old version.

Any help would be appreciated, I’m anxious to try out the new improvements and features. :smiley:

[code]root@volumio:~# dmesg |grep brcm
root@volumio:~# ifup wlan0
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device “wlan0”
Bind socket to interface: No such device
Failed to bring up wlan0.
root@volumio:~#
[/code]

2

Well, at least I figured out the cause. It seems as though the broadcom wifi kernel modules haven’t been compiled on version 1.4, cubox-i release. :frowning:

Old version 1.2beta:

volumio@volumio:~$ uname -a Linux volumio 3.10.30-15-ARCH #1 SMP Thu Apr 10 07:50:43 MDT 2014 armv7l GNU/Linux volumio@volumio:~$ ls -l /lib/modules/$(uname -r)/kernel/drivers/net/wireless total 28 drwxr-xr-x 4 root root 4096 Apr 20 11:05 ath drwxr-xr-x 2 root root 4096 Apr 20 11:05 b43 drwxr-xr-x 2 root root 4096 Apr 20 11:05 b43legacy drwxr-xr-x 4 root root 4096 Apr 10 13:51 brcm80211 drwxr-xr-x 2 root root 4096 Apr 20 11:05 rt2x00 drwxr-xr-x 3 root root 4096 Apr 10 13:51 rtl818x drwxr-xr-x 5 root root 4096 Apr 20 11:05 rtlwifi

New version 1.4:

root@volumio:~# uname -a Linux volumio 3.0.35 #1 SMP PREEMPT Sat Feb 8 09:07:48 PST 2014 armv7l GNU/Linux root@volumio:~# ls -l /lib/modules/$(uname -r)/kernel/drivers/net/wireless total 4 drwxr-xr-x 3 root root 4096 Jun 17 01:14 ath

3

Hi blueroom,

i confirm that i have the exact same problem as you.
That’s too bad as i can not use my Cubox-i with a wired connection. It means that i can not enjoy Volumio on my Cubox-i since i bought it :frowning:
This was however on top on my wish list for the new 1.4 release
http://volumio.org/forum/bit-updates-new-features-cubietruck-port-and-more-t1310.html#p4983

At rank number 2 on my wish list i had the package dependencies that are broken since Volumio 1.3 and that prevent using apt to install some new software
http://volumio.org/forum/volumio-for-raspberry-3beta-2014-feedback-t1149-20.html#p4675
I need this fixed to be able to stream the artwork contained in my mp3s’ ID3 Tags to the mobile MPD remote i’m using.

@Michelangelo : if you brought a solution to these two issues you could not make me happier (and others for sure) :wink:

esseki

4

Hi Blueroom,

When you wrote :

Do you mean the official 1.2beta version released by Michelangelo ? Or the modified 1.2 version made available by lstein in this post ?

http://volumio.org/forum/solved-wifi-cubox-t1117.html#p4086

Those broadcom wifi kernel modules that are missing, are they supposed to make the internal wifi chipset work, or do you need them for an external wifi USB dongle ?

I’m desperately trying to have a wifi connection working with my Cubox-i4pro and Volumio (whatever the version, 1.2 would be a fine at least) :cry:

Thank you in advance for your answers.

5

Oops, I forgot to mention that. You are correct, The version with the working wifi was the updated version released by Michelangelo.

Also, If I remember correctly; instead of using the GUI to enter the wireless passphrase/etc, I think I added the settings manually to the file /etc/network/interfaces like so:

root@volumio:/home/volumio# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-ssid "SSID_NAME"
wpa-psk "PLAINTEXT_PASSPHRASE"

auto eth0
iface eth0 inet dhcp

Also, because I’m using a USB DAC, I had to use the following solution by Bearington:
has-anyone-tested-volumio-the-cubox-yet-t996-10.html#p4432

6

if you use wpa_passphrase it will generate a key for you to use instead of having your plain text password in the clear…go look at the wifi issues with RasberryPi and see if you can get it resolved.

7

I have the same setup. The wifi option does not work. I enter the ssid and the password but the wlan0 interface shows “no interface present”.

8

Hi Blueroom,

Did Michelangelo provide any version that had wifi working on Cubox ?
I thought the only version was Istein’s ? And unfortunately this one doesn’t work that well for me.

Can you please point me the Michelangelo 1.2 version with wifi working ?

Thank you

9

You can try this out: dropbox.com/s/eqvz9s08thsnf … 024.tar.gz

Volumio 1.4 with the latest 3.10 kernel (including wireless driver). Some other things may be missing though.
I have a Cubox-i1 so wireless and other stuff have not been tested.

Please note that Airplay is configured to output on hw2:0, if you use the Cubox HDMI or SPDIF out, it will not work.
You need to edit /etc/init.d/shairport and change it according to your environment (try “sudo aplay -l” to get the correct hardware id)

M1024

10

The new image does not work for me. No WiFi device found.
CuBox-4pro. Volumio 1.4 with new image.

11

Guys, on my cubox-i4 wireless works. So, it means mine has a different wireless adapter. To make it working I need your help:
I need to know which wireless module does the Cubox-i use.
Please paste the output of:

iwlist

And dmesg

Please note that you don’t need to change anything to make shairport work. It will just use the device you selected as output

12

I got wireless working. :slight_smile:

Big thanks to M1024 for posting the 3.10 kernel version. I’d like to know how to compile my own as it’s quite a bit different then on x86 based distro’s. if anyone can point me to a doc or howto on this, I’d be more than happy to rtfm.

That being said, This is what I had to do to get wireless working on mine.

If after updating to M1024’s version which includes kernel 3.10. Check for the following in dmesg:

brcmfmac: brcmf_sdio_get_fw: fail to request firmware brcm/brcmfmac4330-sdio.txt (-2)
brcmfmac: brcmf_bus_start: brcmf_sdbrcm_bus_init failed -2
brcmfmac: brcmf_sdio_probe: dongle is not responding
brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...

then verify the following files exist:
/lib/firmware/brcm/brcmfmac4329-sdio.txt
/lib/firmware/brcm/brcmfmac4330-sdio.txt

If they don’t, then create them, here are mine:

/lib/firmware/brcm/brcmfmac4329-sdio.txt

# bcm94329sdagb board
# $Copyright (C) 2008 Broadcom Corporation$
# $id$

sromrev=3
vendid=0x14e4
devid=0x432f
boardtype=0x53e

boardrev=0x41

#boardflags=0x1200
boardflags=0x200

# Specify the xtalfreq if it is otherthan 38.4MHz
xtalfreq=37400

aa2g=3
aa5g=0

ag0=255
#tri2g=0x64

# 11g paparams
pa0b0=5542,5542,5542
pa0b1=64244,64244,64244
pa0b2=65202,65202,65202

pa0itssit=62
pa0maxpwr=74
opo=0
mcs2gpo0=0x6666
mcs2gpo1=0x6666

# 11g rssi params
rssismf2g=0xa,0xa,0xa
rssismc2g=0xb,0xb,0xb
rssisav2g=0x3,0x3,0x3
bxa2g=0

# country code
ccode=ALL
cctl=0x0
cckdigfilttype=0
ofdmdigfilttype=1

rxpo2g=0

boardnum=1
macaddr=00:90:4c:c5:00:34

# xtal pu and pd time control variable
# pu time is driver default (0x1501)
#r13t=0x1501

#######
nocrc=1

#for mfgc
otpimagesize=182

# sdio extra configs
hwhdr=0x05ffff031030031003100000

#This generates empty F1, F2 and F3 tuple chains, and may be used if the host SDIO stack does not require the standard tuples.
#RAW1=80 02 fe ff

#This includes the standard FUNCID and FUNCE tuples in the F1, F2, F3 and common CIS.
RAW1=80 32 fe 21 02 0c 00 22 2a 01 01 00 00 c5 0 e6 00 00 00 00 00 40 00 00 ff ff 80 00 00 00 00 00 00 00 00 00 00 c8 00 00 00 00 00 00 00 00 00 00 00 00 00 ff 20 04 D0 2 29 43 21 02 0c 00 22 04 00 20 00 5A
nvramver=4.218.214.0

/lib/firmware/brcm/brcmfmac4330-sdio.txt

# bcm94330wlsdgb.txt
manfid=0x2d0
prodid=0x0552
vendid=0x14e4
devid=0x4360
boardtype=0x0552
boardrev=0x11
# this design has 2.4GHz SP3T switch
boardflags=0x00080200
nocrc=1
xtalfreq=37400
boardnum=22
macaddr=00:90:4c:c5:12:38
ag0=255
aa2g=1
ccode=CN
pa0b0=0x14d0
pa0b1=0xfd98
pa0b2=0xff78
rssismf2g=0xa
rssismc2g=0x3
rssisav2g=0x7
maxp2ga0=0x50
sromrev=3
il0macaddr=00:90:4c:c5:12:38
wl0id=0x431b
cckPwrOffset=5
ofdm2gpo=0x66666666
mcs2gpo0=0x6666
mcs2gpo1=0x6666
swctrlmap_2g=0x04040404,0x02020202,0x02020404,0x10202,0x1ff
swctrlmap_5g=0x00100010,0x00280020,0x00200010,0x14202,0x2f8
rfreg033=0x19
rfreg033_cck=0x1f
dacrate2g=160
txalpfbyp2g=1
bphyscale=17
cckPwrIdxCorr=-15
pacalidx2g=45
txgaintbl=1

Hope this helps.

Also, for the record, I love Volumio. Thanks for all your hard hard work on this. :smiley:

13

I’ll do it this night, once back home from work.

14

Hi Michelangelo,

thank you for helping the ones, like me, who are struggling with wifi on their cubox Volumio setup.
Some information about my setup :

  • i have a cubox-i4pro
  • a volumio 1.4 (the official version released by yourself) freshly installed and not modified at all

[code]Linux volumio 3.0.35 #1 SMP PREEMPT Sat Feb 8 09:07:48 PST 2014 armv7l
___
/_ \ __
__ __ //\ \ __ __ ___ ___ /_\ ___
/\ /\ \ / __\\ \ \ /\ \/\ \ /' __ __\/\ \ / __\
\ \ _/ |/\ \L\ \\ _\ \ _\ /\ /\ /\ \ \ /\ \L\
\ _/ \ _//_\ _/\ _\ _\ _\ _\ _/
// // // // /////////___/

         Free Audiophile Linux Music Player - Version Beta1.4

             C 2013 Michelangelo Guarise - Volumio.org

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.[/code]

  • it means that i have run your commands from my cubox connected with a wired connection as my wifi is not working.

volumio@volumio:~$ sudo iwlist [sudo] password for volumio: Usage: iwlist [interface] scanning [essid NNN] [last] [interface] frequency [interface] channel [interface] bitrate [interface] rate [interface] encryption [interface] keys [interface] power [interface] txpower [interface] retry [interface] ap [interface] accesspoints [interface] peers [interface] event [interface] auth [interface] wpakeys [interface] genie [interface] modulation

volumio@volumio:~$ dmesg Initializing cgroup subsys cpu Linux version 3.0.35 (root@ubuntu) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-14ubuntu2~ppa1) ) #1 SMP PREEMPT Sat Feb 8 09:07:48 PST 2014 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: SolidRun i.MX 6Quad/Dual/DualLite/Solo CuBox-i Board Memory policy: ECC disabled, Data cache writealloc CPU identified as i.MX6Q, silicon rev 1.2 On node 0 totalpages: 458752 free_area_init_node: node 0, pgdat 80b557c0, node_mem_map 8b800000 DMA zone: 368 pages used for memmap DMA zone: 0 pages reserved DMA zone: 46736 pages, LIFO batch:15 Normal zone: 3024 pages used for memmap Normal zone: 318512 pages, LIFO batch:31 HighMem zone: 704 pages used for memmap HighMem zone: 89408 pages, LIFO batch:15 PERCPU: Embedded 7 pages/cpu @8c80e000 s5504 r8192 d14976 u32768 pcpu-alloc: s5504 r8192 d14976 u32768 alloc=8*4096 pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 454656 Kernel command line: root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=hdmi consoleblank=0 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 512MB 1280MB = 1792MB total Memory: 1804964k/1804964k available, 292188k reserved, 360448K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xf4600000 - 0xffe00000 ( 184 MB) vmalloc : 0xea800000 - 0xf2000000 ( 120 MB) lowmem : 0x80000000 - 0xea000000 (1696 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .init : 0x80008000 - 0x8003e000 ( 216 kB) .text : 0x8003e000 - 0x80ae30a0 (10901 kB) .data : 0x80ae4000 - 0x80b568e0 ( 459 kB) .bss : 0x80b56904 - 0x80ba33d8 ( 307 kB) SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Preemptible hierarchical RCU implementation. NR_IRQS:624 MXC GPIO hardware sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms arm_max_freq=1GHz MXC_Early serial console at MMIO 0x2020000 (options '115200') bootconsole [ttymxc0] enabled Console: colour dummy device 80x30 console [tty0] enabled, bootconsole disabled Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 Initializing cgroup subsys cpuacct Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys perf_event CPU: Testing write buffer coherency: ok hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available CPU1: Booted secondary processor CPU2: Booted secondary processor CPU3: Booted secondary processor Brought up 4 CPUs SMP: Total of 4 processors activated (6324.22 BogoMIPS). devtmpfs: initialized print_constraints: dummy: NET: Registered protocol family 16 print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal vmap allocation for size 134221824 failed: use vmalloc=<size> to increase size. Unable to get enet.0 clock hw-breakpoint: found 6 breakpoint and 1 watchpoint registers. hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step. hw-breakpoint: maximum watchpoint size is 4 bytes. L310 cache controller enabled l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B bio: create slab <bio-0> at 0 mxs-dma mxs-dma-apbh: initialized print_constraints: vmmc: 3300 mV SCSI subsystem initialized libata version 3.00 loaded. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Freescale USB OTG Driver loaded, $Revision: 1.55 $ imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) MIPI CSI2 driver module loaded Advanced Linux Sound Architecture Driver Version 1.0.24. Bluetooth: Core ver 2.16 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized cfg80211: Calling CRDA to update world regulatory domain i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method Switching to clocksource mxc_timer1 NET: Registered protocol family 2 IP route cache hash table entries: 65536 (order: 6, 262144 bytes) TCP established hash table entries: 262144 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered UDP hash table entries: 1024 (order: 3, 32768 bytes) UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) NET: Registered protocol family 1 PMU: registered new PMU device of type 0 Static Power Management for Freescale i.MX6 wait mode is enabled for i.MX6 cpaddr = ea880000 suspend_iram_base=ea87c000 PM driver module loaded IMX usb wakeup probe the wakeup pdata is 0xe9eba740 add wake up source irq 75 IMX usb wakeup probe the wakeup pdata is 0xe9ebab80 cpu regulator mode:ldo_enable i.MXC CPU frequency driver highmem bounce pool size: 64 pages JFFS2 version 2.2. (NAND) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. fuse init (API version 7.16) msgmni has been set to 2821 alg: No test for stdrng (krng) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) pwm-backlight pwm-backlight.0: unable to request PWM for backlight pwm-backlight: probe of pwm-backlight.0 failed with error -2 pwm-backlight pwm-backlight.1: unable to request PWM for backlight pwm-backlight: probe of pwm-backlight.1 failed with error -2 MIPI DSI driver module loaded mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1 fbcvt: 1920x1080@60: CVT Name - 2.073M9 imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Console: switching to colour frame buffer device 240x67 mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb _regulator_get: get() with no identifier mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver lcd mxc_sdc_fb mxc_sdc_fb.2: NO mxc display driver found! mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb imx-sdma imx-sdma: loaded firmware 1.1 imx-sdma imx-sdma: initialized Serial: IMX driver imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX [drm] Initialized drm 1.1.0 20060810 [drm] Initialized vivante 1.0.0 20120216 on minor 0 loop: module loaded No sata disk. GPMI NAND driver registered. (IMX) vcan: Virtual CAN interface driver CAN device driver interface flexcan netdevice driver FEC Ethernet Driver fec_enet_mii_bus: probed ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000 fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected add wake up source irq 72 fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200 fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbserial USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usbserial: USB Serial Driver core USB Serial support registered for FTDI USB Serial Device usbcore: registered new interface driver ftdi_sio ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver USB Serial support registered for pl2303 usbcore: registered new interface driver pl2303 pl2303: Prolific PL2303 USB to serial adaptor driver ARC USBOTG Device Controller driver (1 August 2005) mousedev: PS/2 mouse device common for all mice i2c-core: driver [isl29023] using legacy suspend method i2c-core: driver [isl29023] using legacy resume method rtc-pcf8523 2-0068: rtc core: registered rtc-pcf8523 as rtc0 snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc1 i2c /dev entries driver lirc_dev: IR Remote Control driver registered, major 251 IR NEC protocol handler initialized IR RC5(x) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR RC5 (streamzap) protocol handler initialized IR LIRC bridge handler initialized gpio_ir_recv_probe : called gpio_ir_recv_probe : gpio_nr = 73 Requesting gpio Setting direction Registered IR keymap rc-rc6-mce input: gpio_ir_recv as /devices/platform/gpio-rc-recv/rc/rc0/input0 rc0: gpio_ir_recv as /devices/platform/gpio-rc-recv/rc/rc0 rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0 Linux video capture interface: v2.00 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20 i2c-core: driver [mag3110] using legacy suspend method i2c-core: driver [mag3110] using legacy resume method imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1) Bluetooth: Virtual HCI driver ver 1.3 Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCIATH3K protocol initialized Bluetooth: Generic Bluetooth USB driver ver 0.6 usbcore: registered new interface driver btusb sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mmc0: no vmmc regulator found mmc0: SDHCI controller on platform [sdhci-esdhc-imx.0] using DMA sdhci sdhci-esdhc-imx.1: no write-protect pin available! mmc1: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed VPU initialized mxc_asrc registered Galcore version 4.6.9.6622 usb 1-1: new high speed USB device number 2 using fsl-ehci Thermal calibration data is 0x55a4d269 Thermal sensor with ratio = 176 mmc0: queuing unknown CIS tuple 0x80 (2 bytes) mmc0: queuing unknown CIS tuple 0x80 (3 bytes) mmc0: queuing unknown CIS tuple 0x80 (3 bytes) Anatop Thermal registered as thermal_zone0 anatop_thermal_probe: default cooling device is cpufreq! HDMI CEC initialized usbcore: registered new interface driver usbhid mmc0: queuing unknown CIS tuple 0x80 (7 bytes) mmc0: queuing unknown CIS tuple 0x80 (7 bytes) usbhid: USB HID core driver usbcore: registered new interface driver snd-usb-audio mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio mxc_spdif mxc_spdif.0: MXC SPDIF Audio Cirrus Logic CS42888 ALSA SoC Codec Driver i2c-core: driver [cs42888] using legacy suspend method i2c-core: driver [cs42888] using legacy resume method imx_3stack asoc driver asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok ALSA device list: mmc0: new high speed SDIO card at address 0001 #0: imx-spdif #1: imx-hdmi-soc NET: Registered protocol family 26 TCP cubic registered NET: Registered protocol family 17 usb 1-1: device v20b1 p0002 is not supported can: controller area network core (rev 20090105 abi 8) NET: Registered protocol family 29 can: raw protocol (rev 20090105) can: broadcast manager protocol (rev 20090105 t) Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' lib80211_crypt: registered algorithm 'WEP' lib80211_crypt: registered algorithm 'CCMP' lib80211_crypt: registered algorithm 'TKIP' Registering the dns_resolver key type VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 Bus freq driver module loaded Bus freq driver Enabled mxc_dvfs_core_probe DVFS driver module loaded rtc-pcf8523 2-0068: hctosys: unable to read the hardware clock cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4 cannot get ctl value: req = 0x83, wValue = 0x200, wIndex = 0xa00, type = 4 ehci_fsl_bus_suspend begins, Host 1 ehci_fsl_bus_suspend ends, Host 1 Waiting for root device /dev/mmcblk0p1... mmc1: host does not support reading read-only switch. assuming write-enable. mmc1: new high speed SDHC card at address aaaa mmcblk0: mmc1:aaaa SU16G 14.8 GiB mmcblk0: p1 EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240) EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (244) EXT4-fs (mmcblk0p1): recovery complete EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 179:1. devtmpfs: mounted Freeing init memory: 216K udevd[1492]: starting version 175 EXT4-fs (mmcblk0p1): re-mounted. Opts: (null) eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1) PHY: 1:00 - Link is Up - 100/Full RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module.

Just let me know if you want me to run those same commands from a version of Volumio i can connect to wifi with like the ones posted :

15

Nope, shairport works straight with the selected output. No need to change the shairport init script. It is invoked via the WebUI.

16

Ok, found the issue. My Cubox-i uses a different wi-fi chips. Newer cuboxes uses BCM4330. So, I’m going to recompile the kernel. I will also use an universal bootloader to support all the Cubox-i range.
Stay tuned and thanks for the feedbacks!

17

Thanks michelangelo! Let me know if there is anything I can do to help. (ie, further information, testing, etc…) :slight_smile:

18

I posted a new kernel here

solved-wifi-cubox-t1117-10.html#p5495

Use it and report if this solves the issue!