Search the Community

Hi! I'm trying to use the image Cubietruck_Debian_3.8_jessie_4.0.4.raw with my CubieTruck, but run into problems when trying to use an external LUKS-disk which is encrypted using aes-xts-plain64. 'cryptsetup luksOpen' informs the following: device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/disk/by-uuid/<xxxx>. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info). 'cat /proc/crypto | grep name' lists only this, which seems kinda minimal: name : stdrng name : stdrng name : crc32c name : deflate name : ecb(arc4) name : arc4 name : aes name : des3_ede name : des name : sha224 name : sha256 name : sha1 name : md5 name : md4 Directory /lib/modules/4.0.4-cubietruck/kernel/crypto/ has these files: af_alg.ko algif_rng.ko async_tx ccm.ko crypto_null.ko ctr.ko fcrypt.ko gcm.ko gf128mul.ko ghash-generic.ko pcbc.ko seqiv.ko So, it seems that some crypto modules for the kernel are missing, but I don't know which ones are needed ('aes-xts' or similar, at least, maybe?). Any ideas on what to do? Do I need to compile the kernel to include the modules? Does the older 3.4.x(?) kernel have these included? Thanks.

Hello, I've problem use i2c features on newest CTDebian3.8 Jessie os. Exactly i using CT3 with DVK570 extended board witch deploy any signals from CN8 and CN9 slots. I can't see any i2c devices though that i see two buses after used i2cdetect -l: root@ctdev:~# i2cdetect -l i2c-0 i2c sunxi-i2c.0 I2C adapter i2c-1 i2c sunxi-hdmi-i2c I2C adapter root@ctdev:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@ctdev:~# root@ctdev:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@ctdev:~# I was tested and check buses for a few devices like BMP180, MPU-6050, TTP229-LSF (3V3 power tolerant devices) but i don't see any address after i2cdetect. I'm sure that testing peripherals are ok cause of i was using them on my Raspberry. I need change my dev platform to CT cause of more performance and SATA port... For additional information on DVK570 board SCK was connected to PB18 and SCL was coccected to PB19. Why i don't see i2c-dev modules after load it?

Hi, Looks like kernel config CONFIG_USB_STORAGE_DEBUG=y has been set in the Debian Jessie 4.0.4 build. That means, that when I have I/O to a usb-storage device, systemd-journald is consuming ~70-90% CPU time on consuming debug log lines from the kernel. Is this by purpose? How would I be able to filter or disable all this log content from the kernel to journald?

Hi trying to install Debian on my allwinner a20 board and been running into issues used this link http://mirror.igorpecovnik.com/Cubieboard2_Debian_3.8_jessie_3.4.107.zip the imagewriter doesnt really work for windows 8 keep on crashing and doesnt find the sd card so i used win32imager to write the raw file to the card checked so wrote the filesystem to the card the popped it into my Cubieboard and it detects that there is a sd card and then it messes up took a pic with my camera seems that it tries to tftp boot https://www.dropbox.com/s/nhzir29jyw4bjhf/IMG_20150526_162455.jpg?dl=0

Hello readers, i just tried out the new jessie with 4.0.4. But after start it stops @: ---- Welcome to Debian GNU/LINUX 8 (jessie)! [TIME] Timed out waiting for device dev-ttyS0.device. [DEPEND] Dependency failed for Serial Getty on ttyS0. ----- What am I doing wrong ? Also no LED´s a flickering. Thank you for advice

Hi Igor, nice idea to open this board i have a problem with my wireless connection using your jessie image with kernel 4.0.4 (newest release right now). at the first start i use a wired connection to connect via SSH - this works without any problems. Next step: configure wireless connection My /etc/network/interfaces looks like this: auto eth0 iface eth0 inet static address 192.168.178.150 netmask 255.255.255.0 # hwaddress ether # if you want to set MAC manually # pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838 # # Wired adapter #2 #auto eth1 # iface eth1 inet dhcp # hwaddress ether # if you want to set MAC manually # pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838 # # Wireless adapter #1 auto wlan0 allow-hotplug wlan0 iface wlan0 inet static address 192.168.178.151 netmask 255.255.255.0 gateway 192.168.178.1 wireless-power off wpa-ssid ############### wpa-psk ############ dns-nameservers 192.168.178.1 8.8.8.8 8.8.4.4 # to generate proper encrypted key: wpa_passphrase yourSSID yourpassword # # Local loopback auto lo iface lo inet loopback So i use the static 192.168.178.150 IP for wired connection and 151 for wireless connection. Then i do a reboot. Result: i can connect via 150 and 151 ip adress. thats ok, because both are connected. BUT: as soon as i disconnect the ethernet cable, im not able to connect via wireless connection to 192.168.178.151 when i connect the ethernet cable again -> both are working again O_o ifconfig output: eth0 Link encap:Ethernet HWaddr 02:4b:02:c1:63:11 inet addr:192.168.178.150 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: fe80::4b:2ff:fec1:6311/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:251 errors:0 dropped:0 overruns:0 frame:0 TX packets:386 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18962 (18.5 KiB) TX bytes:36416 (35.5 KiB) Interrupt:45 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:740 (740.0 TX bytes:740 (740.0 wlan0 Link encap:Ethernet HWaddr 98:3b:16:5a:8c:24 inet addr:192.168.178.151 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: fe80::9a3b:16ff:fe5a:8c24/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:535 errors:0 dropped:36 overruns:0 frame:0 TX packets:149 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:52419 (51.1 KiB) TX bytes:13916 (13.5 KiB) iwconfig output: wlan0 IEEE 802.11bgn ESSID:"###########" Mode:Managed Frequency:2.452 GHz Access Point: 34:31:C4:89:21:CA Bit Rate=65 Mb/s Tx-Power=1496 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=70/70 Signal level=-38 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 i just dont get it....everything looks fine, but it just doesnt work. even my router is able to recognize both IPs correcty... do you have an idea? i need to use the wireless connection on this cubietruck..

Hi, thank for your work i need to make a hotspot with cubietruck I test all debian images for cubietruck but impossible Configuration - connexion VGA - ethernet connected - microsdcard 16G sandisk ou 32 g - clavier with doogle usb all image is dowload today ** Cubietruck_Debian_3.7_jessie_4.0.3 last message Welcom to Debian GNU/Linux 8 (jessie)! [TIME] Timed ou waiting for device dev-ttyS0.device. [DEPEND] Dependency failed for serial Getty on ttyS0. ** Cubietruck_Debian_3.7_jessie_3.4.107.raw Cannot Display This video mode ** Cubietruck_Debian_3.7_wheezy_3.4.107.raw Cannot Display This video mode ** Cubietruck_Debian_3.7_wheezy_4.0.3.raw ... failed to bring up eth0 ... [OK] Restarting OpenBSD Secure Shell Server : sshd 15 minutes rient tentative de connexion a ssh KO ** Cubietruck_Debian_3.8_jessie_3.4.107.raw Cannot Display This video mode ** Cubietruck_Debian_3.8_jessie_4.0.4.raw Welcom to Debian GNU/Linux 8 (jessie)! [TIME] Timed ou waiting for device dev-ttyS0.device. [DEPEND] Dependency failed for serial Getty on ttyS0. ** Cubietruck_Debian_3.8_wheezy_3.4.107.raw Cannot Display This video mode ** Cubietruck_Debian_3.8_wheezy_4.0.4.raw ... failed to bring up eth0 ... [OK] Restarting OpenBSD Secure Shell Server : sshd 15 minutes rient tentative de connexion a ssh KO ** Cubietruck_Debian_3.6_jessie_3.4.107.raw : old image , not download today boot: OK update : OK but wifi en mode hotspot don't work if I write in /etc/modules file bcmdhd : I can't see my SSID with my wifi device or bcmdhd op_mode=2 : dont load the module If the bcmdhd module is not load and I execute the commande "modprobe bcmdhd op_mode=2" and start hostapd, I can see my ssid with my wifi device ** Cubietruck_Ubuntu_3.8_trusty_4.0.4.raw [3.628018] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code ~3 minutes ... ... ssh start/running, process961 wait and nothing Have you a solution for me please ? I'm sorry my english is bad, My Linux is better, but not excelent!!!

Hi, I have installed the phoenix suite on a windows seven 64 bits. I start the phoenix suite et make the cubietruck in the mode to flash the nand. Phoenix Suite detect not the cubieboard. It's normal ? How transform your raw file in .img because the phoenix suite accept only the img file ? Is there another method to flash the nand ? Thanks François

Hello, I'm using the Wheezy Image with Kernel 3.4.107-cubietruck, downloaded 25th May 2015, on my Cubietruck. Working through the Guide "Enable Access point mode" I ended up having a running hostapd with a ESSID which my clients can see but can not connect. I tried with default config given by the image (ssid=cubietruck and wpa=2 with wpa_passphrase=12345678). I also tried disabling wpa (wpa=0). But no client can connect. Starting "hostapd /etc/hostapd.conf" prints root@cubietruck:~# hostapd /etc/hostapd.conf Configuration file: /etc/hostapd.conf nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory) Using interface wlan0 with hwaddr 02:1a:11:f2:53:57 and ssid "cubietruck" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED wlan0: STA d4:8f:33:c1:65:74 IEEE 802.11: associated wlan0: AP-STA-CONNECTED d4:8f:33:c1:65:74 wlan0: STA d4:8f:33:c1:65:74 RADIUS: starting accounting session 5560CD08-00000000 wlan0: STA d4:8f:33:c1:65:74 IEEE 802.11: disassociated wlan0: AP-STA-DISCONNECTED d4:8f:33:c1:65:74 ^Cwlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED nl80211: deinit ifname=wlan0 disabled_11b_rates=0 The bold text is what I get, when a clients tries to connect. Any idea how to make hostapd work?