July 06, 2020, 05:25:21 am


Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - almochris

What is the error exactly?

I have used the same kernel before but on the cubietruck it said something like "GMAC disabled" in the boot up messages. This turned out to be because I was using a cubieboard script.bin by mistake and there was no GMAC section.

What does syslog say when you plug in the USB device?

This should print out the vendor & product id of the device, and maybe give the /dev/ device name (eg /dev/sg1 or whatever)

You could read this page https://wiki.archlinux.org/index.php/udev to find out more about udev. I'm wondering if you have got the SUBSYSTEM identifier wrong?

Anyway try running
udevadm info -a -n [device name]
and see what that gives you.
Introduce yourself / Re: GuL
August 07, 2014, 11:55:05 am
Hi GuL,

You may want to re-post this in one of the other sub-forums in order to get more views and replies, maybe one in the http://www.cubieforums.com/index.php/board,22.0.html or http://www.cubieforums.com/index.php/board,18.0.html sections.

There is nothing stopping you removing or installing software from one of these user-supplied images using the usual apt-get way, and possibly you might get more support in these forums eg if you used cubian or cubieez.

I personally rolled my own debian using instructions on the http://linux-sunxi.org/Main_Page . that process is more time consuming than using a pre-built image though.


Quote from: mikelangeloz on July 08, 2014, 12:51:17 am

Dear Cubietruck users, I'm really happy to announce that Volumio has been released for Cubietruck!!

mikelangeloz, well done, this looks like a really good project!
So just to be clear:

Was your problem caused by overclocking or was it the voltage parameters in script.bin being slightly off for your board?

I am wondering if the best practice is to use the voltage params posted by slovenia in the post http://www.cubieforums.com/index.php/topic,2590.msg17824.html#msg17824
You can install the slim package to handle graphical desktop logins (at least on debian)

Edit /etc/slim.conf and make sure the "default_user" and "auto_login" variables are set appropriately
I don't know how cubian does it, but I have a debian on my cubieboard and I use the usbmount package.

This is a very handy package for this type of thing. You can write scripts to run when a particular USB drive is mounted for example. (Put them in /etc/usbmount/mount.d/ )

If cubian is using usbmount, then have a look at /etc/usbmount/usbmount.conf and change the MOUNTOPTIONS variable removing the noexec flag.

There are several different methods in use for auto-mounting USB drives, like I say I'm not sure if cubian uses this one.
I also don't see a problem with a CT here either. I did an overnight test downloading 50 dvd iso images over the local subnet and all downloads went OK,  no errors in syslog, all md5 checksums correct, thats 180 GB of material.

I am running a self built debian wheezy, kernel version 3.4.79.

As jiv says above, it could be a number of things. I would try easiest first, try swapping the ethernet cable, then try a different image. I'd be surprised if a dodgy power source only caused intermittent network problems but you never know.
Have a look at this page:


Also, see this for instructions on how to build a root-fs, in particuiar debian wheezy using debootstrap:


I would suggest using an existing linux image as the basis for development, then replace the root-fs using the above instructions, then replace the kernel/u-boot only if you feel you need/want to do that.
Cubieboard v2 OS (A20 Based) / Re: A20 boot process
March 07, 2014, 03:54:12 am
Quote from: patwood on March 06, 2014, 11:37:13 am
So somehow, booting the SD linux trashed the mbr on your nand (and maybe other stuff?)

What version of linux did you boot from SD that trashed the nand?

For my case, I was using an early-ish version of cubian on the SD. This same SD card works with no corruption on the rev A cubieboard 2 boards. Once I have flashed the rev B board with the lubuntu image, I can boot using the same SD without corruption also.

I don't know if this is only an issue with the stock version of android that the cubieboard comes pre-flashed with, or whether it is a problem with all android images.
See this thread:


It seems there is some strange issue with the rev B cubieboards. If you boot using an SD card then you will corrupt the nand and/or the partition table somehow.

I would suggest reflashing your cubieboard using phoenixsuit/livesuit with your image of choice. If you flash with a linaro/lubuntu image on the nand then you can boot with the SD card as many times as you want. It seems android on nand/linux on sd can't co-exist at the minute.
Cubieboard v2 OS (A20 Based) / Re: A20 boot process
March 06, 2014, 05:03:45 am
Quote from: patwood on March 05, 2014, 01:02:57 am
Do you have any way to capture the debug output on your serial port?  This would tell a lot more about why the board isn't booting. 

Here is the serial console output for a "bricked" cubieboard. This came flashed with android, we then booted using a linux SD card. Inspecting the partition table using /proc/partitions showed no partitions at all.

Then when the SD image was powered off, we tried to boot android from nand again. this is the result.
Cubieboard v2 OS (A20 Based) / Re: A20 boot process
March 06, 2014, 04:42:24 am
Actually I forgot I am not using patwood's u-boot exactly. I made a couple of local modifications to make sure boot.scr was read correctly. See this post for details:


Cubieboard v2 OS (A20 Based) / Re: A20 boot process
March 06, 2014, 04:04:47 am
I am using patwood's u-boot and using a SATA disk as root too. I am using boot.scr to specify the root partition, maybe you could try this as well.

I placed u-boot-bin in the linux directory on nand1 (nanda). To create a boot.scr, first create a boot.cmd file with the following contents:

setenv machid 0x000010bb
setenv bootargs console=ttyS0,115200 consoleblank=0 root=/dev/sda1 rootwait panic=10
fatload nand 0:1 0x43000000 script.bin
fatload nand 0:1 0x48000000 uImage
bootm 0x48000000

This assumes script.bin and uImage are also on nand1, which is a FAT partition.

With the rev A boards, I had script.bin and uImage on nand3, which was ext4. In that case boot.cmd was as follows:

setenv machid 0x000010bb
setenv bootargs console=ttyS0,115200 consoleblank=0 root=/dev/sda1 rootwait panic=10
ext4load nand 0:3 0x43000000 script.bin
ext4load nand 0:3 0x48000000 uImage
bootm 0x48000000

Now convert the boot.cmd in to a boot.scr file by doing the following:

mkimage -C none -A arm -T script -d boot.cmd boot.scr

I moved both files to nand1 (nanda). you don't need to move boot.cmd, that's just for reference.

You may or may not need the machid line. It would be obvious if you do if you had a serial console to view the boot messages. It's very much worth obtaining the necessary cabling to do that.  You could try the boot.cmd with and without that line and see which works.

If you still have no joy I think you'd have to get the serial console going to make any further progress.

Cubieboard v2 OS (A20 Based) / Re: A20 boot process
March 05, 2014, 04:03:26 am

As tomg noted earlier in this thread, you can recover the revB board by flashing with a linaro nand image. We had to use Phoenixsuit from Windows to accomplish this. Once the linaro image is on there, you should be able to boot up with an SD card image without corrupting the nand. The linaro boot partition has u-boot, script.bin etc. so you should be able to use this partition as a basis for further modifications.

Annoyingly, using dd to copy the linaro nand image from a working cubieboard's nand to another (bricked) one does not work. The only sure way seems to be to use phoenixsuit to recover it unfortunately.