Wandboard new kernel

[jurafxp]

andrenam, I had exactly same problem and the only workaround was to enter following command over serial console:

setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk0p2
image=zImage;fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image};fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} dtbs/${fdt_file};bootz ${loadaddr} - ${fdt_addr}

Old kernel 3.0.35 is using uImage, while the new kernel 3.10.17 is using zImage and the uboot is somehow ignoring it..

My main problem was no video on my DVI monitor, so I have reverted on my Yocto image with custom patched kernel.

[pepedog]

Note I don't have a wandboard, but would installing uboot-wandboard have helped?

[andrenam]

@jurafxp: hmm, I can't test that now, because I don't have a serial cable at the moment. But shouldn't this be set when pacman installs the uboot-wandboard-quad package?

@pepedog: according to pacman, I have the latest uboot-wandboard-quad package:
$this->bbcode_second_pass_code('', '
[root@wandboard ~]# pacman -Q | grep uboot-wandboard
uboot-wandboard-quad 2014.01-1
[root@wandboard ~]#')
Note that I already tried to use a new sdcard with a freshly downloaded archlinuxarm-image at may 4th with the latest kernel and the latest uboot image. Maybe, the default settings in the uboot-wandboard-quad package are not suitable in all cases?

[pepedog]

It could help, I believe zImage and dts all fine with default environment.

[kmihelich]

How is your SD card partitioned?

[andrenam]

@pepedog: will try to reinstall the built package and update the kernel tommorow evening.

@kmihelich: the current SD card actually has two partitions: a 4GB ext4 for the root / and a large ext4 data partition.
$this->bbcode_second_pass_code('', '[root@wandboard ~]# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 14,9 GiB, 15931539456 bytes, 31116288 sectors
Units: Sektoren of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000b6046

Gerät Boot Start Ende Blocks Id System
/dev/mmcblk0p1 8192 8394751 4193280 83 Linux
/dev/mmcblk0p2 8394752 31115263 11360256 83 Linux

[root@wandboard ~]# fdisk -l /dev/mmcblk1

Disk /dev/mmcblk1: 14,9 GiB, 15997075456 bytes, 31244288 sectors
Units: Sektoren of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00016a06

Gerät Boot Start Ende Blocks Id System
/dev/mmcblk1p1 2048 31244287 15621120 83 Linux

[root@wandboard ~]#')

$this->bbcode_second_pass_code('', 'root@wandboard ~]# blkid
/dev/mmcblk0: PTUUID="000b6046" PTTYPE="dos"
/dev/mmcblk0p1: LABEL="wandboardarch" UUID="21f112a1-b27b-449b-bc71-c20f25800441" TYPE="ext4" PARTUUID="000b6046-01"
/dev/mmcblk0p2: LABEL="music1" UUID="59f95463-0a6c-4959-888b-d36f07c2ecad" TYPE="ext4" PARTUUID="000b6046-02"
/dev/mmcblk1: PTUUID="00016a06" PTTYPE="dos"
/dev/mmcblk1p1: LABEL="music2" UUID="cd9b6c43-e457-4187-a9b6-1da30b08bc9f" TYPE="ext4" PARTUUID="00016a06-01"
[root@wandboard ~]#')


When I tried a fresh sdcard with a new archlinuxarm-image on may 4th, I created a single ext4 partition for root / on a 8gb sdcard.


BTW: thank you all for helping. I really appreciate it. The community is very active.

[kmihelich]

You're using the partitioning that is expected in the latest U-Boot, which is a first partition for the rootfs where it will pull the kernel from. I don't see any reason why it wouldn't be booting.

The only thing I can think of is that your card has a saved U-Boot environment that is being read in and used instead of the default built-in environment, which is where all the magic is. If you have a spare micro SD, zero the first part (ie. dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=8) to wipe out any possible saved environment, then run through the installation on it. I've lost count of how many times I've recreated my wandboard SD card, so I know it all works.

Other than that, just need to wait for serial to see what's really going on.

[d42b]

I can confirm that an ordinary pacman -Syu breaks the system at this time. With the package "uboot-wandboard-dual" installed or not, the following results in the same unbootable state.

Ever since 2013 my system looks like this:

$this->bbcode_second_pass_code('', '# pacman -Qs wandboard
local/linux-wandboard 3.0.35-6
# (no uboot-wandboard-* package here as uboot was dd'ed onto the sd card when initially preparing it on my desktop)

# ls -1R /boot/
dtbs
uImage

/boot/dtbs:
(empty)
')

pacman -Syu now installs "linux-wandboard-3.10.17-1" which replaces /boot/uImage with zImage and puts imx6dl-wandboard.dtb and imx6q-wandboard.dtb into /boot/dtbs. After shutting down, the system won't come up anymore.

If I install uboot-wandboard-dual and not do pacman -Syu, I still get the uImage replaced with the zImage and the two files are placed in /boot/dtbs, but the system boots just fine afterwards. So I guess it's the update of linux-wandboard from 3.0x to 3.10x that breaks the system.

So what now? Wait until someone fixes something? Or will I never be able to do updates in this installation again?

[kmihelich]

The update to the 3.10 kernel requires the newer U-Boot installed and flashed to the SD card. If the kernel doesn't boot with that installed, you likely have a U-Boot environment saved to the card which is being loaded in place of the default environment of the new U-Boot, which is needed to load the zImage and dtb.

[d42b]

I just found this in my recent bash history, just prior to breaking my system an hour ago:

$this->bbcode_second_pass_quote('', '
')...
(1/1) installing uboot-wandboard-dual [#######################################################] 100%
A new U-Boot version needs to be flashed onto /dev/mmcblk0.
Do you want to do this now? [y|N]
y
542+0 records in
542+0 records out
277504 bytes (278 kB) copied, 0.0234402 s, 11.8 MB/s
[root@wb boot]# ls -l
total 2776
drwxr-xr-x 2 root root 4096 Jul 26 2013 dtbs
-rw-r--r-- 1 root root 277504 Mar 19 22:47 u-boot.imx
-rw-r--r-- 1 root root 2557928 Mar 19 23:48 uImage