Problems with 2.1 install on Cubox and Cubox-i

[jpearn]

Hi,

I have both version of the Cubox, Armada / Freescale so I have tried the 2.1 images out. On the original Cubox, the image boots fine however I am unable to load any wifi USB device as I continue to get 'firmware not loaded', even though the firmware is in /lib/firmware. I have 6 different USB wifi devices and this is repeatable for all vendors.
On the Cubox-i the 1st hurdle was the read-only filesystem, fixed by adding rw to uEnv.txt . Lightdm would not start and after checking through all the logs, X was complaining of no displays found leading me to no /dev/fb0 created. That is as far as I can get as I think this has to do with the device tree (DTB) files ? The good thing though is that the USB wifi devices are picked up and firmware files load fine . . .

Any help to get one of these units working would be great !

[jpearn]

Well 2.1.2 fixed the rw issue on Cubox-i but still not showing any framebuffer device
Old style Cubox still not loading firmware even though firmware is present in /lib/firmware.

[steev]

Can you give me some dmesg ouput from both?

I don't have a Cubox-i, so I blindly make that image, and I don't see the same issue here with the Cubox; so I'd like some dmesg output; preferably insert all of the non-working usb wifi devices and then post the dmesg output.

And the dmesg output of the Cubox-i will help to determine why you may not have any framebuffer there.

[jpearn]

Here is the one from the Cubox, my I is WIP with something else for now !

[ 7.773857] usbcore: registered new interface driver cdc_wdm
[ 7.778184] Initializing USB Mass Storage driver...
[ 7.781963] usbcore: registered new interface driver usb-storage
[ 7.786683] USB Mass Storage support registered.
[ 7.790096] usbcore: registered new interface driver synaptics_usb
[ 7.795260] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[ 7.799907] i2c /dev entries driver
[ 7.803568] lirc_dev: IR Remote Control driver registered, major 252
[ 7.808676] IR NEC protocol handler initialized
[ 7.811880] IR RC5(x) protocol handler initialized
[ 7.815413] IR RC6 protocol handler initialized
[ 7.818620] IR JVC protocol handler initialized
[ 7.821825] IR Sony protocol handler initialized
[ 7.825136] IR RC5 (streamzap) protocol handler initialized
[ 7.829376] IR SANYO protocol handler initialized
[ 7.832754] IR MCE Keyboard/mouse protocol handler initialized
[ 7.837277] IR LIRC bridge handler initialized
[ 7.840467] Registered IR keymap rc-empty
[ 7.843561] input: gpio_ir_recv as /devices/platform/gpio-rc-recv/rc/rc0/input0
[ 7.849740] rc0: gpio_ir_recv as /devices/platform/gpio-rc-recv/rc/rc0
[ 7.858825] switching to TEMP
[ 7.865829] input: MCE IR Keyboard/Mouse (gpio-rc-recv) as /devices/virtual/input/input1
[ 7.872941] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0
[ 7.880253] sdhci: Secure Digital Host Controller Interface driver
[ 7.885167] sdhci: Copyright(c) Pierre Ossman
[ 7.888524] sdhci-pltfm: SDHCI platform and OF driver helper
[ 7.893082] Registered led device: mmc0::
[ 7.903170] ata1: SATA link down (SStatus 0 SControl F300)
[ 7.933119] mmc0: SDHCI controller on sdhci-dove.0 [sdhci-dove.0] using DMA
[ 7.938984] Registered led device: mmc1::
[ 7.973120] mmc1: SDHCI controller on sdhci-dove.1 [sdhci-dove.1] using DMA
[ 7.979035] Registered led device: cubox:red:health
[ 7.979673] usbcore: registered new interface driver usbhid
[ 7.984005] usbhid: USB HID core driver
[ 8.002293] mmc0: new high speed SDHC card at address e624
[ 8.006534] si5351 0-0060: registered si5351 i2c client
[ 8.010441] si5351 0-0060: external clock setup : clkdev = d0182ca0
[ 8.015732] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[ 8.019770] cubox_extclk_setup : add alias 'extclk/dovefb.0' to clkout0 w 0
[ 8.025486] usb 1-1: new low-speed USB device number 2 using orion-ehci
[ 8.030875] mmcblk0: p1
[ 8.033188] external clock setup done
[ 8.041574] cs42l51-codec 0-004a: failed to read I2C
[ 8.057868] kirkwood-i2s kirkwood-i2s.1: found external clock
[ 8.188810] input: Riitek Micro Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0/input/input2
[ 8.197476] hid-generic 0003:1997:0409.0001: input,hidraw0: USB HID v1.11 Keyboard [Riitek Micro Keyboard] on usb-orion-ehci.0-1/input0
[ 8.215359] input: Riitek Micro Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.1/input/input3
[ 8.223964] hid-generic 0003:1997:0409.0002: input,hidraw1: USB HID v1.11 Mouse [Riitek Micro Keyboard] on usb-orion-ehci.0-1/input1
[ 8.063583] >>> kirkwood_spdif_probe : pdev = c07a9140, pdev->id = 1
[ 9.083871] kirkwood-spdif-audio kirkwood-spdif-audio.1: dit-hifi <-> kirkwood-i2s.1 mapping ok
[ 9.092661] oprofile: no performance counters
[ 9.095770] oprofile: using timer interrupt.
[ 9.098972] TCP: cubic registered
[ 9.100972] NET: Registered protocol family 17
[ 9.104129] lib80211: common routines for IEEE802.11 drivers
[ 9.108460] lib80211_crypt: registered algorithm 'NULL'
[ 9.108464] lib80211_crypt: registered algorithm 'WEP'
[ 9.108469] lib80211_crypt: registered algorithm 'CCMP'
[ 9.108473] lib80211_crypt: registered algorithm 'TKIP'
[ 9.108688] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5
[ 9.115043] ThumbEE CPU extension supported.
[ 9.117989] PJ4 iWMMXt coprocessor enabled.
[ 9.121864] Dove FB driver:
[ 9.152286] Initialize /proc/mv_lcd0
[ 9.154567] use cat /proc/mv_lcd0 to see reg settings
[ 9.187166] dovefb dovefb.0: use ref clock extclk
[ 9.190922] o Kernel parameter: 1920x1080-32@60.
[ 9.194413] o Failed to read EDID information,using driver resolutions table.
[ 9.200409] found <1920x1080@60>, pixclock=6734
[ 9.203632] set_clock_divider : setup reference clk to 148500148
[ 9.220937] Setting HDMI TX resolution to 1920x1080p @ 60
[ 9.225019] HDMI TX - FOUND exact resolution 16
[ 9.228852] set_clock_divider : setup reference clk to 148500148
[ 9.232886] Setting HDMI TX resolution to 1920x1080p @ 60
[ 9.232890] HDMI TX - FOUND exact resolution 16
[ 9.261360] Console: switching to colour frame buffer device 240x67
[ 9.304735] o dovefb: frame buffer device was successfully loaded.
[ 9.309907] hdmicec(tda19989) 1.3.0 compiled: Mar 17 2016 00:07:41 -ioctl (2009-10-15)
[ 9.316514] hdmicec:cec_init:.verbose mode
[ 9.319340] hdmicec:this_i2c_probe:called
[ 9.322036] hdmicec:this_i2c_probe:HDMI CEC SW Version:1.4 compatibility:0
[ 9.327596] hdmicec declared as a playback device type
[ 9.335290] hdmicec:cec_standbyn --> standby
[ 9.338841] hdmitx(tda19989) 1.3.0 compiled: Mar 17 2016 00:07:43 -ioctl (2009-10-15)
[ 9.603166] HDMI TX SW Version:5.3 compatibility:0
[ 9.616750] HDMI Int multi-transition
[ 9.641201] hdmi HPD inactive
[ 9.656716] hdmi Rx device inactive
[ 9.672510] hdmi HPD active
[ 9.684641] hdmi Rx device active
[ 10.332963] rtc-mv rtc-mv: setting system clock to 2016-02-26 02:18:53 UTC (1456453133)
[ 10.340682] ALSA device list:
[ 10.342341] #0: Kirkwood SPDIF
[ 11.421333] hdmi EDID received
[ 11.667342] EXT4-fs (mmcblk0p1): recovery complete
[ 11.683123] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 11.689918] VFS: Mounted root (ext4 filesystem) on device 179:1.
[ 11.704260] devtmpfs: mounted
[ 11.706178] Freeing init memory: 196K
[ 11.984614] systemd[1]: Failed to insert module 'autofs4': No such file or directory
[ 12.014936] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 12.031893] systemd[1]: Detected architecture arm.
[ 12.054169] systemd[1]: Set hostname to <kali>.
[ 12.471342] systemd[1]: Reached target Swap.
[ 12.493532] systemd[1]: Listening on Journal Socket.
[ 12.513451] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 12.543253] systemd[1]: Reached target Remote File Systems (Pre).
[ 12.563318] systemd[1]: Reached target Remote File Systems.
[ 12.583373] systemd[1]: Listening on udev Control Socket.
[ 12.603354] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 12.633318] systemd[1]: Listening on Syslog Socket.
[ 12.653732] systemd[1]: Created slice System Slice.
[ 12.675397] systemd[1]: Mounting Debug File System...
[ 12.706540] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 12.728297] systemd[1]: Created slice system-getty.slice.
[ 12.758004] systemd[1]: Starting Load Kernel Modules...
[ 12.792523] systemd[1]: Listening on Journal Socket (/dev/log).
[ 12.815660] systemd[1]: Starting Journal Service...
[ 12.843327] systemd[1]: Reached target Encrypted Volumes.
[ 12.867829] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 12.886873] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 12.923387] systemd[1]: Reached target Paths.
[ 12.936295] systemd[1]: Created slice User and Session Slice.
[ 12.973343] systemd[1]: Reached target Slices.
[ 12.983778] systemd[1]: Listening on udev Kernel Socket.
[ 13.003785] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 13.028185] systemd[1]: Mounted Debug File System.
[ 13.053632] systemd[1]: Started Journal Service.
[ 13.711839] systemd-journald[720]: Received request to flush runtime journal from PID 1
[ 22.028857] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 23.163264] mv643xx_eth_port mv643xx_eth_port.0: eth0: link down
[ 26.165310] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 27.273497] mv643xx_eth_port mv643xx_eth_port.0: eth0: link down
[ 30.331735] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 245.747261] hdmi HPD inactive
[ 245.756553] hdmi Rx device inactive
[ 268.168329] usb 1-1: USB disconnect, device number 2
[ 273.813329] usb 1-1: new high-speed USB device number 3 using orion-ehci
[ 275.203601] usb 1-1: ath9k_htc: Failed to get firmware htc_9271.fw
[ 275.209123] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
[ 275.219608] usb 1-1: ath9k_htc: USB layer deinitialized
[ 275.228538] usbcore: registered new interface driver ath9k_htc
root@kali:~#

[jpearn]

Both of the firmwares are in /lib/firmware

[ 560.988000] usb 1-1: new high-speed USB device number 4 using orion-ehci
[ 562.282101] rtl8192cu: Chip version 0x10
[ 562.366460] rtl8192cu: MAC address: 00:1f:1f:bf:35:06
[ 562.370647] rtl8192cu: Board Type 0
[ 562.373075] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 562.377598] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
[ 562.388290] rtlwifi: Firmware rtlwifi/rtl8192cufw.bin not available
[ 562.398727] usbcore: registered new interface driver rtl8192cu

[steev]

Can you do an ls -lah of /lib/firmware/* and post the output here? The only thing I can possibly think is that... somehow the inkernel firmware loader isn't working properly. I won't be able to get to it tomorrow (easter and all that), but this coming week I'll look into it.

And whenever the -i is available to debug, I'd love to look into the issue.

[jpearn]

/lib/firmware/rtlwifi:
total 780K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 11K Mar 17 05:08 rtl8188efw.bin
-rw-r--r-- 1 root root 14K Mar 17 05:08 rtl8188eufw.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cfw.bin
-rw-r--r-- 1 root root 15K Mar 17 05:08 rtl8192cfwU.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cfwU_B.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cufw.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cufw_A.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cufw_B.bin
-rw-r--r-- 1 root root 16K Mar 17 05:08 rtl8192cufw_TMSC.bin
-rw-r--r-- 1 root root 31K Mar 17 05:08 rtl8192defw.bin
-rw-r--r-- 1 root root 32K Mar 17 05:08 rtl8192eefw.bin
-rw-r--r-- 1 root root 25K Mar 17 05:08 rtl8192eu_ap_wowlan.bin
-rw-r--r-- 1 root root 32K Mar 17 05:08 rtl8192eu_nic.bin
-rw-r--r-- 1 root root 26K Mar 17 05:08 rtl8192eu_wowlan.bin
-rw-r--r-- 1 root root 79K Mar 17 05:08 rtl8192sefw.bin
-rw-r--r-- 1 root root 120K Mar 17 05:08 rtl8712u.bin
-rw-r--r-- 1 root root 22K Mar 17 05:08 rtl8723aufw_A.bin
-rw-r--r-- 1 root root 24K Mar 17 05:08 rtl8723aufw_B.bin
-rw-r--r-- 1 root root 19K Mar 17 05:08 rtl8723aufw_B_NoBT.bin
-rw-r--r-- 1 root root 31K Mar 17 05:08 rtl8723befw.bin
-rw-r--r-- 1 root root 21K Mar 17 05:08 rtl8723bu_ap_wowlan.bin
-rw-r--r-- 1 root root 32K Mar 17 05:08 rtl8723bu_nic.bin
-rw-r--r-- 1 root root 26K Mar 17 05:08 rtl8723bu_wowlan.bin
-rw-r--r-- 1 root root 12K Mar 17 05:08 rtl8723fw.bin
-rw-r--r-- 1 root root 23K Mar 17 05:08 rtl8723fw_B.bin
-rw-r--r-- 1 root root 29K Mar 17 05:08 rtl8821aefw.bin
-rw-r--r-- 1 root root 20K Mar 17 05:08 rtl8821aefw_wowlan.bin

/lib/firmware/sb16:
total 36K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 1.3K Mar 17 05:08 alaw_main.csp
-rw-r--r-- 1 root root 1.9K Mar 17 05:08 ima_adpcm_capture.csp
-rw-r--r-- 1 root root 1.1K Mar 17 05:08 ima_adpcm_init.csp
-rw-r--r-- 1 root root 1.9K Mar 17 05:08 ima_adpcm_playback.csp
-rw-r--r-- 1 root root 1.3K Mar 17 05:08 mulaw_main.csp

/lib/firmware/slicoss:
total 292K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 97K Mar 17 05:08 gbdownload.sys
-rw-r--r-- 1 root root 2.6K Mar 17 05:08 gbrcvucode.sys
-rw-r--r-- 1 root root 81K Mar 17 05:08 oasisdbgdownload.sys
-rw-r--r-- 1 root root 81K Mar 17 05:08 oasisdownload.sys
-rw-r--r-- 1 root root 2.6K Mar 17 05:08 oasisrcvucode.sys

/lib/firmware/sun:
total 20K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 2.3K Mar 17 05:08 cassini.bin

/lib/firmware/sxg:
total 136K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 62K Mar 17 05:08 saharadbgdownloadB.sys
-rw-r--r-- 1 root root 53K Mar 17 05:08 saharadownloadB.sys

/lib/firmware/tehuti:
total 60K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 42K Mar 17 05:08 bdx.bin

/lib/firmware/ti-connectivity:
total 8.2M
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 48K Mar 17 05:08 TIInit_7.2.31.bts
-rw-r--r-- 1 root root 190K Mar 17 05:08 wl1251-fw.bin
-rw-r--r-- 1 root root 752 Mar 17 05:08 wl1251-nvs.bin
-rw-r--r-- 1 root root 268K Mar 17 05:08 wl1271-fw-2.bin
-rw-r--r-- 1 root root 267K Mar 17 05:08 wl1271-fw-ap.bin
-rw-r--r-- 1 root root 266K Mar 17 05:08 wl1271-fw.bin
lrwxrwxrwx 1 root root 14 Mar 17 05:08 wl1271-nvs.bin -> wl127x-nvs.bin
-rw-r--r-- 1 root root 274K Mar 17 05:08 wl127x-fw-3.bin
-rw-r--r-- 1 root root 255K Mar 17 05:08 wl127x-fw-4-mr.bin
-rw-r--r-- 1 root root 256K Mar 17 05:08 wl127x-fw-4-plt.bin
-rw-r--r-- 1 root root 271K Mar 17 05:08 wl127x-fw-4-sr.bin
-rw-r--r-- 1 root root 347K Mar 17 05:08 wl127x-fw-5-mr.bin
-rw-r--r-- 1 root root 345K Mar 17 05:08 wl127x-fw-5-plt.bin
-rw-r--r-- 1 root root 363K Mar 17 05:08 wl127x-fw-5-sr.bin
-rw-r--r-- 1 root root 262K Mar 17 05:08 wl127x-fw-plt-3.bin
-rw-r--r-- 1 root root 912 Mar 17 05:08 wl127x-nvs.bin
-rw-r--r-- 1 root root 279K Mar 17 05:08 wl128x-fw-3.bin
-rw-r--r-- 1 root root 259K Mar 17 05:08 wl128x-fw-4-mr.bin
-rw-r--r-- 1 root root 264K Mar 17 05:08 wl128x-fw-4-plt.bin
-rw-r--r-- 1 root root 278K Mar 17 05:08 wl128x-fw-4-sr.bin
-rw-r--r-- 1 root root 351K Mar 17 05:08 wl128x-fw-5-mr.bin
-rw-r--r-- 1 root root 353K Mar 17 05:08 wl128x-fw-5-plt.bin
-rw-r--r-- 1 root root 371K Mar 17 05:08 wl128x-fw-5-sr.bin
-rw-r--r-- 1 root root 260K Mar 17 05:08 wl128x-fw-ap.bin
-rw-r--r-- 1 root root 266K Mar 17 05:08 wl128x-fw-plt-3.bin
-rw-r--r-- 1 root root 267K Mar 17 05:08 wl128x-fw.bin
-rw-r--r-- 1 root root 1.1K Mar 17 05:08 wl128x-nvs.bin
lrwxrwxrwx 1 root root 14 Mar 17 05:08 wl12xx-nvs.bin -> wl127x-nvs.bin
-rw-r--r-- 1 root root 625K Mar 17 05:08 wl18xx-fw-2.bin
-rw-r--r-- 1 root root 658K Mar 17 05:08 wl18xx-fw-3.bin
-rw-r--r-- 1 root root 722K Mar 17 05:08 wl18xx-fw-4.bin
-rw-r--r-- 1 root root 405K Mar 17 05:08 wl18xx-fw.bin

/lib/firmware/ti-keystone:
total 20K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 1.8K Mar 17 05:08 ks2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin

/lib/firmware/tigon:
total 36K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 2.7K Mar 17 05:08 tg3.bin
-rw-r--r-- 1 root root 144 Mar 17 05:08 tg357766.bin
-rw-r--r-- 1 root root 6.9K Mar 17 05:08 tg3_tso.bin
-rw-r--r-- 1 root root 3.8K Mar 17 05:08 tg3_tso5.bin

/lib/firmware/ttusb-budget:
total 32K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 13K Mar 17 05:08 dspbootcode.bin

/lib/firmware/ueagle-atm:
total 2.2M
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 22K Mar 17 05:08 930-fpga.bin
-rw-r--r-- 1 root root 137 Mar 17 05:08 CMV4p.bin.v2
-rw-r--r-- 1 root root 71 Mar 17 05:08 CMV9i.bin
-rw-r--r-- 1 root root 61 Mar 17 05:08 CMV9p.bin
-rw-r--r-- 1 root root 161 Mar 17 05:08 CMVei.bin
-rw-r--r-- 1 root root 161 Mar 17 05:08 CMVeiWO.bin
-rw-r--r-- 1 root root 161 Mar 17 05:08 CMVep.bin
-rw-r--r-- 1 root root 151 Mar 17 05:08 CMVepES.bin
-rw-r--r-- 1 root root 151 Mar 17 05:08 CMVepES03.bin
-rw-r--r-- 1 root root 151 Mar 17 05:08 CMVepFR.bin
-rw-r--r-- 1 root root 151 Mar 17 05:08 CMVepFR04.bin
-rw-r--r-- 1 root root 181 Mar 17 05:08 CMVepFR10.bin
-rw-r--r-- 1 root root 161 Mar 17 05:08 CMVepIT.bin
-rw-r--r-- 1 root root 151 Mar 17 05:08 CMVepWO.bin
-rw-r--r-- 1 root root 446K Mar 17 05:08 DSP4p.bin
-rw-r--r-- 1 root root 332K Mar 17 05:08 DSP9i.bin
-rw-r--r-- 1 root root 427K Mar 17 05:08 DSP9p.bin
-rw-r--r-- 1 root root 437K Mar 17 05:08 DSPei.bin
-rw-r--r-- 1 root root 418K Mar 17 05:08 DSPep.bin
-rw-r--r-- 1 root root 7.6K Mar 17 05:08 adi930.fw
-rw-r--r-- 1 root root 11K Mar 17 05:08 eagleI.fw
-rw-r--r-- 1 root root 11K Mar 17 05:08 eagleII.fw
-rw-r--r-- 1 root root 11K Mar 17 05:08 eagleIII.fw
-rw-r--r-- 1 root root 11K Mar 17 05:08 eagleIV.fw

/lib/firmware/usbdux:
total 92K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 462 Mar 17 05:08 Makefile_dux
-rw-r--r-- 1 root root 3.8K Mar 17 05:08 fx2-include.asm
-rw-r--r-- 1 root root 25K Mar 17 05:08 usbdux_firmware.asm
-rw-r--r-- 1 root root 9.2K Mar 17 05:08 usbduxfast_firmware.asm
-rw-r--r-- 1 root root 28K Mar 17 05:08 usbduxsigma_firmware.asm

/lib/firmware/vicam:
total 20K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 2.1K Mar 17 05:08 firmware.fw

/lib/firmware/vxge:
total 840K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 471K Mar 17 05:08 X3fw-pxe.ncf
-rw-r--r-- 1 root root 351K Mar 17 05:08 X3fw.ncf

/lib/firmware/yam:
total 32K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 5.2K Mar 17 05:08 1200.bin
-rw-r--r-- 1 root root 5.2K Mar 17 05:08 9600.bin

/lib/firmware/yamaha:
total 60K
drwxr-xr-x 2 root root 4.0K Mar 17 05:08 .
drwxr-xr-x 73 root root 12K Mar 17 05:08 ..
-rw-r--r-- 1 root root 12K Mar 17 05:08 ds1_ctrl.fw
-rw-r--r-- 1 root root 128 Mar 17 05:08 ds1_dsp.fw
-rw-r--r-- 1 root root 12K Mar 17 05:08 ds1e_ctrl.fw
-rw-r--r-- 1 root root 16K Mar 17 05:08 yss225_registers.bin
root@kali:~#

[jpearn]

And some more . . .

[hamx0r]

I'm seeing the same misbehaving Light Display Manager on version 2.1.2. During boot, i can see the following from the Cubox-i4 serial console:

[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.

The log file gives the same as the OP:

root@kali:~# tail /var/log/Xorg.0.log 
[   141.162] (EE) No devices detected.
[   141.162] (EE) 
Fatal server error:
[   141.162] (EE) no screens found(EE) 
[   141.162] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   141.162] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Is this an issue relating to the different GPUs of the Cubox-i variants? Some have the GC880 while others have GC2000. The Cubox-i4 Pro uses the GC2000. Does anyone have an i1 or i2 which works with the 2.1 image? Those two have the GC880 GPU. given the official blog on how to install on the i4 Pro, I'd assume the image should work.

[gslebrch]

I'm seeing the same misbehaving Light Display Manager on version 2.1.2. During boot, i can see the following from the Cubox-i4 serial console:

[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.

The log file gives the same as the OP:

root@kali:~# tail /var/log/Xorg.0.log 
[   141.162] (EE) No devices detected.
[   141.162] (EE) 
Fatal server error:
[   141.162] (EE) no screens found(EE) 
[   141.162] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   141.162] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Is this an issue relating to the different GPUs of the Cubox-i variants? Some have the GC880 while others have GC2000. The Cubox-i4 Pro uses the GC2000. Does anyone have an i1 or i2 which works with the 2.1 image? Those two have the GC880 GPU. given the official blog on how to install on the i4 Pro, I'd assume the image should work.

Same Issue - Any Resolution - Would love to solve this issue for the New Year. I have tried to install drivers etc... No luck. Please help...