ArchLinux ARM for CubieTruck : any ideas ?

[Tangente]

$this->bbcode_second_pass_quote('moscar', 'W')hat does your uEnv.txt look like?

[WarheadsSE]

The machid should be removed, correct. This is thanks to the changes we've pulled in.

The PR fixing the display was merged.

[Tangente]

Yup, but it still does not work. What is meant by serial? serial cable/ console/ ..?
The boot screen shows me the two Linux Tuxes and the rest of the screen is black. Using an advanced uEnv.txt also does not work.
Ty

[moscar]

Hello Tangente

You need something like this:

$this->bbcode_second_pass_code('', 'extraargs=disp.screen0_output_type=3 disp.screen0_output_mode=10')

http://linux-sunxi.org/Fex_Guide#disp_i ... figuration

[fabian20]

If you don't own a cable/converter like Prolific PL2303 used for serial connection to cubietruck (see http://linux-sunxi.org/Cubieboard/TTL) you can try adding console=tty0 to your extraargs in uEnv.txt like this:
$this->bbcode_second_pass_code('', 'extraargs=console=tty0 disp.screen0_output_type=3 disp.screen0_output_mode=10')
or for standard VGA output you can leave it like
$this->bbcode_second_pass_code('', 'extraargs=console=tty0')

This should give you kernel messages as soon as you can see the two tuxes, so you can further examine your problem.
See here http://linux-sunxi.org/Kernel_arguments for kernel arguments to tune reserved graphics memory, etc.

[Tangente]

Plugging the SD into my PC and changing the uEnv there doesn't change anything, does it? I haven't checked it out yet but I think my problem then was that I used kernelargs instead of extraargs.

[fabian20]

It sure does if you are booting from SD - it's pretty much your only option

[Tangente]

Uh sorry extremely bad question I meant doesn't change anything more then with serial cable.
Now it hangs at "PCLK=.." but I think I can get it to work on my own.
Thank you for now I just still don't understand why you didn't integrate the extraargs section in the updated uEnv in the alarm repo.

[fabian20]

No problem
With standard VGA output/serial console/partitioning you don't really need entries in uEnv.txt, that's why.

My PR for fixing display on cubietruck was basically reverted, and according to https://github.com/archlinuxarm/PKGBUILDs/commit/9dffd3a07a143e056d66a4f2635c9d26a6e777ab Cubieboard 2 won't boot when FB_SUNXI_LCD gets built into the kernel.

I did some testing to find the most minimalistic set of changes to bring my Cubietruck to show display output and it seems that it would only work when all of FB_SUNXI are statically compiled into the kernel. This is also the recommended default kernel config by Cubietech:
$this->bbcode_second_pass_code('', 'CONFIG_FB_SUNXI=y
CONFIG_FB_SUNXI_RESERVED_MEM=y
CONFIG_FB_SUNXI_UMP=y
CONFIG_FB_SUNXI_LCD=y
CONFIG_FB_SUNXI_HDMI=y
CONFIG_HDMI_CEC=m') (src:http://dl.cubieboard.org/software/a20-cubietruck/lubuntu/ct-lubuntu-nand-v1.00/ct-lubuntu-server-20131026/cubietruck_defconfig) and is also true for any other working Cubietruck distribution I tried.

There was no combination of blacklisting/module loading orders which lead to any success on my board.

After throughouly testing this issue I think that the Cubieboard 2 / Cubietruck can't both completely work with the exact same kernel in place, at least as long as the underlying LCD driver problem hasn't been fixed for Cubieboard 2.

[Sqozz]

Hi Guys,

the past 5 hours i tried to get alarm running on my cubietruck. I stumbled across an old entry (viewtopic.php?f=33&t=6413&hilit=hwpack&start=10#p36642) and tried to make my own alarm sd-card.

Unfortunately the linked hwpack is not available anymore, so i tried to compiled by myself on my arch notebook but this also went wrong. After selecting the cubietruck (./configure cubietruck) and running make it always stop with an error: "recipe for target "u-boot" failed". Is this an dependency problem? Or is there meanwhile an even simpler way to get alarm running on the cubietruck?