Hi there,
I´am new to the Cubietruck and had it working for a few days now.
The Cubietruck is currently running with a SD Card Image that i have installed
with Intructions from: http://archlinuxarm.org/platforms/armv7/allwinner/cubietruck
On this Page there is also a "guide" for installing the mainline kernel via $this->bbcode_second_pass_code('', 'pacman -Syu linux-armv7')
As a prerequisite installing an updated version of uboot (done this with pacman -Syu uboot-cubietruck) is required
for using the mainline kernel.
The System was running after installing the uboot-cubietruck package.
But after installing the linux-armv7 mainline Kernel package the system was unable to boot.
No blinking LED´s ect after that.
So anybody know what iam doing wrong?
I saw that i maybe have to update my boot.scr for using the Mainline Kernel but i did not found any running example for that.
Thanks in advance.
Cubietruck Mainline Kernel installation
28 posts
• Page 1 of 3 • 1, 2, 3
Cubietruck Mainline Kernel installation
by h4xx » Mon Jun 01, 2015 7:14 am
- h4xx
- Posts: 19
- Joined: Wed Dec 25, 2013 12:34 pm
Re: Cubietruck Mainline Kernel installation
by Isgar » Mon Jun 01, 2015 8:45 am
I have exactly the same problem.
When connected to an HDMI display I see this: uboot seems to load the zImage kernel, but then nothing happens. It just displays two tux images on a blank screen. It does not find a initramfs_linux.img, should that exist?
And this is with a new SD card, with the old it throws a ext4_devread error. Even though reinstalling the legacy kernel works fine.
When connected to an HDMI display I see this: uboot seems to load the zImage kernel, but then nothing happens. It just displays two tux images on a blank screen. It does not find a initramfs_linux.img, should that exist?
And this is with a new SD card, with the old it throws a ext4_devread error. Even though reinstalling the legacy kernel works fine.
- Isgar
- Posts: 15
- Joined: Thu Sep 04, 2014 10:45 pm
Re: Cubietruck Mainline Kernel installation
by krabat » Mon Jun 01, 2015 8:05 pm
On Linux mainline support of video output and everything related to multimedia like sound is still pretty poor. Can't tell much about HDMI but missing or faulty HDMI output doesn't necessarily mean the device didn't boot.
The latter applies to LEDs, too. These are switched on via the usual FEX files used on linux-sunxi kernel but not by the DTBs of mainline kernel (they can e. g. be handled by scripts on running systems).
Would be good to know what findings exactly make you believe the device didn't boot.
All in all setting up mainline kernel on Cubietruck without serial console isn't possible in a reasonable way right now, IMHO.
Regarding U-Boot installation of package uboot-cubietruck involves copying u-boot-sunxi-with-spl.bin to the beginning of the SD card. You may want to verify whether this has been working by running
$this->bbcode_second_pass_code('', '
$ dd bs=1 if=/dev/mmcblk0 skip=8192 count=352620 of=uboot_test
')and compare the checksums of u-boot-sunxi-with-spl.bin and uboot_test.
Also, you have to make sure boot.scr is suitable. You may want to compare the checksums of the one provided by package uboot-cubietruck and the one on your device. It's also possible to look at the content by running
$this->bbcode_second_pass_code('', '$ strings /path/to/boot.scr')Note that the boot.{txt,scr} shipping with package uboot-cubietruck expect the FHS on partition one of the SD card. So settings like mount partition one to /boot and place all the rest on different partitions aren't covered. Using initramfs-linux.img is optional, so booting shouldn't be prevented by lack of this file.
The latter applies to LEDs, too. These are switched on via the usual FEX files used on linux-sunxi kernel but not by the DTBs of mainline kernel (they can e. g. be handled by scripts on running systems).
Would be good to know what findings exactly make you believe the device didn't boot.
All in all setting up mainline kernel on Cubietruck without serial console isn't possible in a reasonable way right now, IMHO.
Regarding U-Boot installation of package uboot-cubietruck involves copying u-boot-sunxi-with-spl.bin to the beginning of the SD card. You may want to verify whether this has been working by running
$this->bbcode_second_pass_code('', '
$ dd bs=1 if=/dev/mmcblk0 skip=8192 count=352620 of=uboot_test
')and compare the checksums of u-boot-sunxi-with-spl.bin and uboot_test.
Also, you have to make sure boot.scr is suitable. You may want to compare the checksums of the one provided by package uboot-cubietruck and the one on your device. It's also possible to look at the content by running
$this->bbcode_second_pass_code('', '$ strings /path/to/boot.scr')Note that the boot.{txt,scr} shipping with package uboot-cubietruck expect the FHS on partition one of the SD card. So settings like mount partition one to /boot and place all the rest on different partitions aren't covered. Using initramfs-linux.img is optional, so booting shouldn't be prevented by lack of this file.
- krabat
- Posts: 57
- Joined: Wed Jun 04, 2014 8:03 pm
Re: Cubietruck Mainline Kernel installation
by Abroxa » Tue Jun 02, 2015 3:54 pm
I have the same problem. Connecting to the serial console gives me
endless messages of that:
[4.293874] systemd[1]: Time has been changed
...
...
I also posted that here: viewtopic.php?f=33&t=8833 maybe this thread here is better suited.
Thanks for any help.
endless messages of that:
[4.293874] systemd[1]: Time has been changed
...
...
I also posted that here: viewtopic.php?f=33&t=8833 maybe this thread here is better suited.
Thanks for any help.
- Abroxa
- Posts: 5
- Joined: Fri May 02, 2014 9:10 am
Re: Cubietruck Mainline Kernel installation
by Isgar » Tue Jun 02, 2015 3:59 pm
The uboot is correct. / is the only partition on the sd card. I am pretty sure it doesn't boot, as journalctl doesn't show the boot at all (after switching to legacy kernel).
That makes debugging particularly hard, as I don't have an UART (which is needed for serial console, right?)
That makes debugging particularly hard, as I don't have an UART (which is needed for serial console, right?)
- Isgar
- Posts: 15
- Joined: Thu Sep 04, 2014 10:45 pm
Re: Cubietruck Mainline Kernel installation
by krabat » Tue Jun 02, 2015 5:36 pm
$this->bbcode_second_pass_quote('Isgar', '.').. as I don't have an UART (which is needed for serial console, right?)
If you mean a serial port on the host you want to connect to your Cubietruck then the answer is (fortunately) no. You may use an USB to serial adaptor as described e. g. on linux-sunxi.org/UART or linux-sunxi.org/Cubieboard/TTL. Things you badly have to care for are the voltage as adaptors providing more than 3,3V are available and harm your device and the wiring, in particular to avoid connecting an eventual VCC cable.Personally I'm using this one which is featuring Prolific's PL2303 chipset and working well (not affiliated to the vendor in any way).
Aside from this it's one pretty weird issue. In particular as mainline kernel installed the very same way works well here.
That message regarding time change could be related to the fact that linux-sunxi and mainline kernel seem to use different ways to write to the RTC but actually shouldn't prevent booting.
If journald's failure is related it could help to temporarily set journald directive 'Storage' to 'volatile' or 'none', see man 5 journald.conf.
The message "Failed to run mainloop..." doesn't seem to be specific to Cubietruck: archlinuxarm.org/forum/viewtopic.php?f=58&t=8789.
- krabat
- Posts: 57
- Joined: Wed Jun 04, 2014 8:03 pm
Re: Cubietruck Mainline Kernel installation
by h4xx » Wed Jun 03, 2015 1:47 pm
Today i compared my current uboot with the provided u-boot-sunxi-with-spl.bin.
They have both the same md5 checksum "df9aac7a2ffe8ab7bae51cc372295c0c".
/dev/mmcblk0p1
My boot.scr looks like this :
$this->bbcode_second_pass_code('', 'U-Boot boot script
part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=${console} root=PARTUUID=${uuid} rw rootwait
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then
if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then
setenv bootm_boot_mode sec;
bootm 0x48000000;
fi;
')
Still not having any idea how to solve this.
I played around using old boot.scr entries and generating a new one wit help from http://linux-sunxi.org/Manual_build_howto#boot.cmd with no success.
They have both the same md5 checksum "df9aac7a2ffe8ab7bae51cc372295c0c".
/dev/mmcblk0p1
My boot.scr looks like this :
$this->bbcode_second_pass_code('', 'U-Boot boot script
part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=${console} root=PARTUUID=${uuid} rw rootwait
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then
if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then
setenv bootm_boot_mode sec;
bootm 0x48000000;
fi;
')
Still not having any idea how to solve this.
I played around using old boot.scr entries and generating a new one wit help from http://linux-sunxi.org/Manual_build_howto#boot.cmd with no success.
- h4xx
- Posts: 19
- Joined: Wed Dec 25, 2013 12:34 pm
Re: Cubietruck Mainline Kernel installation
by h4xx » Thu Jun 04, 2015 10:48 am
Got my Cubietruck working now with the mainline kernel.
Changed my boot.scr to output to tty1 again.
$this->bbcode_second_pass_code('', 'part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=tty1 root=PARTUUID=${uuid} rw rootwait
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then
if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then
setenv bootm_boot_mode sec;
bootm 0x48000000;
fi;
fi')
Changed my /etc/systemd/system.conf by adding
$this->bbcode_second_pass_code('', '
LogLevel=notice
')
To get rid of that $this->bbcode_second_pass_quote('', 's')ystemd[1]: Time has been changed
problem.Changed my boot.scr to output to tty1 again.
$this->bbcode_second_pass_code('', 'part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=tty1 root=PARTUUID=${uuid} rw rootwait
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then
if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then
setenv bootm_boot_mode sec;
bootm 0x48000000;
fi;
fi')
Changed my /etc/systemd/system.conf by adding
$this->bbcode_second_pass_code('', '
LogLevel=notice
')
To get rid of that $this->bbcode_second_pass_quote('', 's')ystemd[1]: Time has been changed
My boot process still was throwing out some errors and also takes a bit long.
But i think thats related to my system being messed up by me.
Please check if theese two steps are helping.
- h4xx
- Posts: 19
- Joined: Wed Dec 25, 2013 12:34 pm