pancio

Thanks for your replay. I'll do it manually. Do you know why 'openvpn' client can't open 'tun' device? Is possible that openvpn can not be run with Softether VPN together? Where I may find script which is responsible for run/stop Softether VPN? Regards, Blazej.

Hi Igor, One question regarding Softether VPN... How to uninstall it with any issue? It's not possible by simple uncheck asterisk into your Simple Install Tool. Thanks for your effort! Regards, Blazej

​ Hi, ​ First method: You may try to use ​LiveSuite and OTG mode in order to install any factory image. I'm not sure that it's possible for Armbian images but you may swap existing FS on NAND by this from Armbian (for example from HDD installed for a moment with extracted FS from SDcard). The existing in NAND kernel should work with new FS which you can deploy from HDD. Second method: I suppose that is possible change FS before flash it in NAND (in order do it you should mount iso file and next change FS). Next you should flash NAND using LiveSuite. My advises are theoretically because I had never need to use these but they are first which I might to use... Regards, ​ ​

Are you able to use older kernel for test? I've Orange Pi Plus 2, and when I will found a couple of minutes I may check it for you... Regards,

HI, I'm using Cubietruck with Domoticz since May 2015 non stop. It's platform for control my 12 CT farm (SSD utilization, temperature). This is the best option for me, I'm using standard PC PSU. BTW, for last 3 years my Cubie farm was down only 2 times (one when I moved this and last when I changed router). It's very stable platform.

Hi! Probably you have brand new version of CT with another partitions table (Android?) than needed for Armbian. Solution: Flashing using LiveSuit and last Cubieez version (http://dl.cubieboard.org/model/cubietruck/Image/Cubieez/cubieez-hdmi/). After this step you may flash Ct using Armbian as well.

Thanks for your huge explanation. Of course, you have right regarding that CT+ is a marketing trick (I'm little bit disappointed about USB-SATA bridge too) but I'm looking for best alternative for CT because I suppose that it will be discontinued soon. At this moment I using 12 CT as production servers for many client (reason? 60W power consumption max for all of them) and I want to know which one may be a spare part for. Maybe you may suggest something? Sometime I buying these device only for testing, the same was with CT in the past, which has been the black horse (cheap, fast, energy-saving). Do you know about something better? p.s. Please be forgiving because of my English :-)

Thanks for your reply. Now my understanding is little bit more completely. I'm not a kernel hacker, so I've only one way... waiting. BTW, you said that H3 and A83T are similar, is possible use the same image for OP2+ (this one work properly) and for CT+?

Hi Igor, I'm fresh owner of CB5 (CT2+) board and I'm interesting about your opinion regarding this board. I hope that in near future you will start new branch of Armbian for H8. At this moment, best option for me is still using CT as a production appliance but maybe CT+ will be faster... (instead SATA USB bridge access of course).

Hi, I wrote (actually, I remade) a simple library in order to use I2C based HD44780. Please look into GitHub code: https://github.com/panciunio/pyCT-PCF8574 In my projects based on I2C I using 2 channels voltage converter, so be careful what you do! It's very simple, basic instruction set but easy to use and modify. It's not completely solution because at first you need working I2C layer (smbus). More information you may find on my forum: https://cubieboard.org.pl Sorry, it's only in Polish because of my English... Regards,

Hi, From my point of view if you may boot from NAND boot (3.4.109 kernel's image) is possible that you might mount NAND1 (boot partition) after boot from SD card and just copy files from /boot directory with expected kernel file to /boot on NAND1 partition. Of course you should change path into uEnv.txt regarding root filesystem. If my thinking is wrong please let me know :-) Regards,

Hi, Generally, Wheezy and Jessie are Debian Distro. Trusty is Ubuntu Trusty Tahr LTS Distro for CB/CT. Additionally, Jessie is newest and contains freshly tools and programs - for me best way to make any production environment. If you want most user friendly OS, please choice Trusty Distro (it contains GUI Desktop Environment).

Maybe it's stupid question.... have you root partition on 'mmcblk0' as you wrote above or into mmcblk0p1, eventually mmcblk0p0 (if you haven't alone boot partition)? Regards,

Hi again, Success, it's work! root@ctdev:/boot# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@ctdev:/boot# uname -a Linux ctdev 3.4.107-cubietruck #8 SMP PREEMPT Thu May 14 18:53:36 CEST 2015 armv7l GNU/Linux root@ctdev:/boot# You have disabled i2c(twi) into your config by default (except twi0). Is any reason for this or you don't realize about this fact by accident? Now i may use any devices like i do this on my Raspberry... Thanks Igor for your best work.

Do you asking me about my compilation of your brand or ct-dvk brand? I checked both again: Your config from /lib/config/cubietruck.fex: [twi_para] twi_port = 0 twi_scl = port:PB0<2><default><default><default> twi_sda = port:PB1<2><default><default><default> ;------------------------------------------------------------------------------- ;i2c configuration ;------------------------------------------------------------------------------- [twi0_para] twi0_used = 1 twi0_scl = port:PB0<2><default><default><default> twi0_sda = port:PB1<2><default><default><default> [twi1_para] twi1_used = 0 twi1_scl = port:PB18<2><default><default><default> twi1_sda = port:PB19<2><default><default><default> [twi2_para] twi2_used = 0 twi2_scl = port:PB20<2><default><default><default> twi2_sda = port:PB21<2><default><default><default> config from ct-dkv distro /boot/script.fex: [twi_para] twi_port = 0 twi_scl = port:PB0<2><default><default><default> twi_sda = port:PB1<2><default><default><default> ;------------------------------------------------------------------------------- ;i2c configuration ;------------------------------------------------------------------------------- [twi0_para] twi0_used = 1 twi0_scl = port:PB0<2><default><default><default> twi0_sda = port:PB1<2><default><default><default> [twi1_para] twi1_used = 1 twi1_scl = port:PB18<2><default><default><default> twi1_sda = port:PB19<2><default><default><default> [twi2_para] twi2_used = 1 twi2_scl = port:PB20<2><default><default><default> twi2_sda = port:PB21<2><default><default><default> Now I see that into your config we have disabled twi1_used and twi2_used parameters ... ... so maybe enable it is necessary to proper work :-) I'll make new compilation and I'll try confirm my idea. (or at first i change script.bin/fex into exist distro) BTW, I've permanently connected 1 thing (i2c sd1306 display) for test:

1. Was data wrote completely on SD card? (did you used sync command?) 2. Some SD cards aren't good and CT can't start from them. Did you checked your SD card by mount it into normal Linux distro? If you changed rootfs you must change uEnv.ct for new rootfs, did you?

Hi again, Yesterday and today I compiled two version of CTDebian from your git, 1. Wheeze (3.4.107) and 2. Jessie (the same kernel). Both compilation was finished successfully... but I2c still not working. I decided compile kernel again configuring I2c section manually... for test i used modules for better control what kind of module are using. After boot i loaded i2c-dev and i2c-sunxi modules but I still see the same result ... nothing! For test i prepared new uSD card with ct-dvk distro from Waveshare and again checked some devices... success: root@chird:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@chird:~# root@chird:~# uname -a Linux chird 3.4.79 #26 SMP PREEMPT Wed Apr 2 03:30:40 PDT 2014 armv7l GNU/Linux root@chird:~# so, i compared i2c config section for your brand and ct-dvk but result is the same... What do you think, what may be wrong? I'm very satisfied using your brand of Debian, I've 8 production servers under CTdebian, so must use it on my develop platform too :-)

Thanks for your quick reply... i using your last brand of Debian Jessie with 3.4.107-cubietruck kernel. I've never supposed that kind of Debian is importance (i thought that kernel is important) so i used Jessie for better performance and newest software... For my development environment it's doesn't matter so i may downgrade it to Wheezy. I've favor to you, if you find a couple of minutes - could you please check your CT with Jessie and his report about i2c?

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?