Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / CubieTruck Plus boot from SATA hard drive
« Last post by aragorn2101 on November 20, 2017, 02:26:19 am »

Hey guys,

I've got a CubieTruck Plus (Cubieboard v5) currently booting from EMMC with Linaro Ubuntu 14.04. Everything is fine but I was wondering if I can make it boot from the SATA hard drive. It would be nice to have all the space.

I have noticed that the board does not boot if I put an empty micro SD in. It also does not boot when I connect the SATA hard drive. I would have been happy if it booted just fine with an empty drive plugged in. I could mount it and store all my data or move my home directory there. But it is just not booting.

So, I thought, since it is not booting at all, maybe connecting any drive (micro SD or SATA HD) makes the boot process ignore the EMMC and look for bootloaders on the drives instead.

I have seen that it is possible to burn the linaro image to SD card so that it boots the OS from there instead of EMMC. Is it possible to do the same thing with the SATA hard drive? Can I just clone the micro SD Linaro to the SATA hard drive and boot from there?
2
Tips, Tricks and Guides / How to distinguish different Hardware versions
« Last post by bomilkar on November 17, 2017, 02:24:27 am »
I'm looking for ways to distinguish CubieBoards in software. I know how to read the print on the board and use this:
http://dl.cubieboard.org/model/CubieBoard2/How%20To%20Distinguish%20Your%20CubieBoard2%20Version%20.pdf
to tell the difference between board versions. However, I'm looking for ways in software to distinguish which board I'm currently using. The OS may know what version it's running on, but I guess every distribution has it's own ways to remember the HW configuration. The OS may not even care if it's running on a CB2 20151211 TSD or on a CubieBoard2 20120909 DualCard.

However, the problem I'm trying to solve is much less complex: all I want to know (right now) is whether there is a battery backed up Real Time Clock available or not. I know the 20151211 has a RTC on board, but older versions of the CB2 have no RTC. I'd like know a way for the software to tell the difference.

Any help is greatly appreciated.
3
Download site changed, you can find qbee-x images here
4
Thank you for this image. It runs nicely on my HD TV.
But can anyone get me a Howto and a driver for the Cubiescreen to use with this img. ?

Please, Thank you.
5
Deutsch / openssl Problme
« Last post by harvey186 on November 16, 2017, 07:55:26 am »
Hi, ich habe auf meinem Cubietruck / Linaro OS openssl installiert. Wenn ich nun meinen webserver aufrufe, dann bekomme ich aber immer die Meldung, dass die Verbindung nicht sicher ist. Das Zertifikat wird aber gefunden (siehe Anhang).
Die Zertificate habe ich im unter /etc/ssl/cert abgespeichert.

By the way: Die Meldung bekomme ich sowohl beim lokalen Zugriff, als auch über eine dyndns domain

Wo ist also das Problem ??

Danke
Harvey
6
CubieBoard v5 Hardware (H8/CubieTruck Plus) / Double Output
« Last post by jeaneve on November 14, 2017, 08:16:52 am »
Hello,

i have buy me a cubieboard 5. I install linaro Desktop on a Flash Card. Everything works fine. Now i will use both Video Output HDMI and DP. I want to expand the HDMI Desktop to the DP Display. Is there any possibility to do that.

Thanks for Answers

Greats
Eve
7
I have been playin with armbian and it sounds very good. Any body have been succesfull in enabling a cubiescreen with an armbian image?

I am able to use the screen, but the touch patch is not working, it always disconnect after a period of time sendingme i2c -121 read errors.

Any help would be appreciated!

Regards,
8
Hi drkbcn,

I would like to compile my own version of cubieez for enabling cubiescreen and the mini usb support to the image. Could you please share some guidelines to follow?

Right now I am having problems with the touchscreen driver using an armbian compilation, but I am willing to make it form scratch in order to have a rocksolid image.

Any help would be very appreciated,
9
I am Korean.
So I will simply write down the procedure.
Please understand what I wrote in Google Translator.

My SDCard is 16G.

Windows;

extract the image
>imgrepacker "M1&M1+_Android4.2.2_v2.1.img"

Edit sys_partition.fex in the M1&M1+_Android4.2.2_v2.1.img.dump directory.

;------------------------------>mmcblk0p7/nandd 4G
; 1048576 = 512M to 8388608 = 4G
; 16384 * 256 = 4194304 * 2 = 8388608
[partition]
    name         = system
    size         = 8388608
    downloadfile = "system.fex"
    user_type    = 0x8000

Save and close.

linux

#cd ../sunxi-tools
#./script ../"M1&M1+_Android4.2.2_v2.1.img.dump"/sys_partition.fex

(The script command must be run in the sunxi-tools directory to get sys_partition.bin)

#cd ../"M1&M1+_Android4.2.2_v2.1.img.dump"
#../sunxi-tools/update_mbr sys_partition.bin 4

(The number 4 makes the size of sunxi_mbr.fex 64K. The original sunxi_mbr.fex file included in the image was 64K in size. If it is 1, it becomes 16K.)

The files dlinfo.fex and sunxi_mbr.fex are overwritten.

#../sunxi-tools/simg2img system.fex system.img
#mkdir /mnt/system
#mount -o loop system.img /mnt/system
#../sunxi-tools/make_ext4fs -s -l 4096M -a system ./system.fex /mnt/system

You can leave sys_partition.bin and system.img created here or delete them.
It has no effect when repackaging the image.

Windows;

>imgrepacker "M1&M1+_Android4.2.2_v2.1.img.dump"

Burn the newly created M1&M1+_Android4.2.2_v2.1.img file to the 16G or 8G SDCard with the phoenixcard tool.
Be sure to <startup!> Mode.

Now your mounted system is 4 gigabytes in size.
10
In the meantime, I got a solution:

Code: [Select]
apt install build-essential git
cd /usr/local/src
git clone https://github.com/mmplayer/linux-sunxi.git -b dev/sunxi-3.4 –depth=1
mv /lib/modules/3.4.79/build /lib/modules/3.4.79/build.distributed
ln -s /usr/local/src/linux-sunxi /lib/modules/3.4.79/build
cd linux-sunxi
cp /proc/config.gz .
gzip -d config.gz
mv config .config
make oldconfig
make prepare
make modules_prepare

then, eg. for installing v4l2loopback:
Code: [Select]
apt install v4l2loopback-dkms
modprobe --force v4l2loopback
Still have to "--force" the modprobe command, even if both - kernel and module.ko file info shows up 3.4.79
Pages: [1] 2 3 ... 10