5.04 Ubuntu 3.4.110 Desktop not working on CubieTruck

[NahanniV]

On initial install, It reboots several times then finally gets stuck in a loop with the following two messages:

 

bcmadh_sdmmc mmc1:0001:2: wlan0: (WE) : Wireless Event too big (65535)

[ap6210] scan is not ready

 

After 10min. I pulled the plug and started again, same messages eventually.

 

 

[Igor]

I tested those images. Huh.

You need to add a user otherwise no desktop and it reboots.

[NahanniV]

Thanks for the quick reply Igor,

 

I did not see an opportunity to add a user.

 

Just to be sure, I downloaded again and re-wrote the sd card.

 

Same result.

 

Here is a video of the initial boot:

 

 

Sorry, it's very blurry, but perhaps you can get an Idea of the problem.

 

I can do it again if needed.

 

Cheers,

JM.

 

[tkaiser]

Sorry, it's very blurry, but perhaps you can get an Idea of the problem.

 

In case there was something written like "ext4 errors" or "filesystem mounted read only" then that's the culprit and you end with an endless loop since Armbian wants to restart automagically at least one time, then deactivates this automated reboot which will obviously not work if the filesystem is read-only.

 

So either you provide output that is readable (high resolution images or way better serial console output) or you read yourself whether these messages appear.

[Igor]

Read only mounting due to hardware / bad SD card ? Possible. We need a clear picture at least of 7th second of the video or rather whole boot log with verbosity to full.

[NahanniV]

I think it is able restart.

 

The only thing I see that looks like an error is:

 

The previously mentioned "Wireless Event too big"

 

and

 

[mmc-err] smc 3 err, cmd 52, RTO

[mmc-err] smc 3 err, cmd 52, RTO

[mmc-err] smc 3 err, cmd 8, RTO

 

But I think that is normal probing ?

 

I downloaded image (http://mirror.igorpecovnik.com/Armbian_5.04_Cubietruck_Ubuntu_trusty_3.4.110_desktop.zip) using Chrome in Win10 and wrote SDcard using your supplied imagewriter.exe

All seemed to work OK.

 

"whole boot log with verbosity to full."

How can I set verbosity, and how can I capture the log ?

 

Thanks,

JM.

[Igor]

How can I set verbosity, and how can I capture the log ?

 

Now we are just about to change this that it will be more simple. But currently you need to edit /boot/boot.cmd and change loglevel parameter to 8 for example, recompile boot.cmd to boot.scr (written in at the end of the file) and reboot.

[NahanniV]

Looks like I would need to order a special TTL level cable.

[NahanniV]

I was able to download, flash and test a previous version of Armbian using the same setup: same PC, same SD card reader, same CubieTruck.

 

How could the filesystem become read-only ? Imagewriter created the file system. How can I check that ?

 

Just tried, and same result with another SD card.

[afnm]

Hello NahanniV,

 

where did you get a previous version of Armbian?

Did you manage to make it work with the desktop on Cubietruck?

 

Because I have the exact same problem.

 

Thanks for a hint!