[CurlyMo]

And the latest kernel still made my system unbootable:

Code:

Setting up linux-image-3.10.30-armmp (1.0.9) ...

Ethernet light doesn't blink anymore when booting...

[IriDium]

Upgraded to 3rd July - haven't continued as the system becomes unreliable and won't start after that (Work in progress as I believe)
Noticed that the swap is no longer allocated - might be fixed in a later upgrade, but thought I'd mention it.

root@cubox:/etc/ssh# more /var/log/upstart/zram-swap.log

ls: cannot access /sys/block/zram?/reset: No such file or directory
rmmod: ERROR: Module zram is not currently loaded
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 4.0276 s, 133 MB/s
Setting up swapspace version 1, size = 524284 KiB
no label, UUID=1284940c-db4e-4392-a9ad-0ba055c56afc
ls: cannot access /sys/block/zram?/reset: No such file or directory
rmmod: ERROR: Module zram is not currently loaded

[IriDium]

As the swap file is no longer allocated because of a 5th July update, does anyone know how to allocate it manually?

I've tried stopping/starting zram-swap but nothing is allocated.

I guess it's a little bit more complicated than a normal swapon/swapoff. But could that method be used instead to allocate a swapfile?

[AcidZero]

Hi

my cubox-i arrived today an i think xbian a good solution as os. But i had some Problem.

After the boot-screen from solid-run i had a black screen.
I used a 24" PC-Monitor with hdmi to dvi cable.
I tried different resolution in the uEnv.txt but nothing help.

SSH and the other stuff worked.

Any Idee what i can do ?

[IriDium]

Is there any development continuing on this H/W?

I have a "stable" release from about June but since then I have been unable to upgrade due to dependencies.

The main issue is the lack of swap file - which causes buffer issues.

Should we just wait until all the debian updates are completed?

[mk01]

@IriDium

there are lot of updates since June, in DEVEL and STAGING too.

currently blocked packages are those (should not be more)

Code:

Calculating upgrade... Done
The following packages have been kept back:
  libpam-systemd libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 systemd

if you add "partswap" parameter to kernel command line it should work the same way as on RPI. shrink rootfs and create swappartition.

it wasn't (and isn't) the default (on RPI is) but with recent version of xbian packages it should work ok.
(you need one reboot with initramfs for that to work which is by default not used. edit /etc/default/xbian-initramfs and set FORCEINITRAM=yes)

((for partswap to work - create swap partition - your root= needs to be last partition on you boot drive)).

regarding the Debian Jessie stuff, I was in touch with Steve Langasek from Debian (maintainer of upstart and related stuff) and he just confirmed that it is question of time only - and will (must be) resolved before Jessie goes public. So policykit-1 will not force systemd as init system.

---

(13th Jul, 2014 01:39 AM)IriDium Wrote:  As the swap file is no longer allocated because of a 5th July update, does anyone know how to allocate it manually?

I've tried stopping/starting zram-swap but nothing is allocated.

I guess it's a little bit more complicated than a normal swapon/swapoff. But could that method be used instead to allocate a swapfile?

let's see the swapfile on FS as a last resort. the function is still there, only it was turned off by default.
edit /etc/default/zram-swap and SWAPFILE= parameter.

(but again, "swappart" parameter should be way to go)

---

(19th Jul, 2014 12:25 AM)AcidZero Wrote:  Hi

my cubox-i arrived today an i think xbian a good solution as os. But i had some Problem.

After the boot-screen from solid-run i had a black screen.
I used a 24" PC-Monitor with hdmi to dvi cable.
I tried different resolution in the uEnv.txt but nothing help.

SSH and the other stuff worked.

Any Idee what i can do ?

I re-aded some patches from my testing DVI branch https://github.com/mk01/linux-linaro-stable-mx6/tree/DVI a while ago. they should provide minimal DVI support. try kernel from STAGING linux-image-3.10.30-armmp_1.1.0-1-1407266060 .

---

(4th Jul, 2014 10:17 PM)CurlyMo Wrote:  And the latest kernel still made my system unbootable:

Code:

Setting up linux-image-3.10.30-armmp (1.0.9) ...

Ethernet light doesn't blink anymore when booting...

did you find reason for not to boot ?

---

(4th Jul, 2014 08:58 PM)IriDium Wrote:  @mk01 Image http://ivka57.dyndns-ip.com/images/xbian-image-imx6-20140703.img.xz

Doesn't boot :-) - No boot.scr or Uenv.txt

and actual ?
http://xbian.brantje.com/images/

[CurlyMo]

@mk01, i believe there is an issue with the uboot environment not updating properly.

---

Image 27-07-14 boots.
- Kernel update still doesn't work.

Code:

Unpacking linux-image-3.10.30-armmp (1.1.0-1-1407266060) over (1.0.3-1) ...
Setting up linux-image-3.10.30-armmp (1.1.0-1-1407266060) ...
Updating u-boot
35+0 records in
35+0 records out
35840 bytes (36 kB) copied, 0.00302586 s, 11.8 MB/s
236+1 records in
236+1 records out
242008 bytes (242 kB) copied, 0.0194329 s, 12.5 MB/s
CRC check failed
CRC check failed
CRC check failed
CRC check failed
Image Name:   U-Boot script
Created:      Wed Aug  6 00:38:33 2014
Image Type:   ARM Linux Script (uncompressed)
Data Size:    1032 Bytes = 1.01 kB = 0.00 MB
Load Address: 00000000
Entry Point:  00000000
Contents:
   Image 0: 1024 Bytes = 1.00 kB = 0.00 MB

- xbian-config clone feature also doesn't work.
- serial doesn't work after kernel booting.

[mk01]

@CurlyMo

check /etc/uboot-env.conf if the values are ok for your HW (i have no idea and only Cx4p to test).
also you can try "uboot-env" command a bit manually (without param help will be displayed).

this are four steps running during kernel update:

Code:

uboot-env del -i
                uboot-env set < /etc/uboot-env/default.txt
                uboot-env set script boot.scr
                uboot-env set bootdelay 0

it looks like all are failing. Can you try the first step with uppercase I?

Code:

uboot-env del -I

[CurlyMo]

Code:

root@cubox:/home/xbian# uboot-env del -i
CRC check failed
root@cubox:/home/xbian# nano /etc/uboot-env.conf
root@cubox:/home/xbian# uboot-env set < /etc/uboot-env/default.txt
CRC check failed
root@cubox:/home/xbian# uboot-env set script boot.scr
CRC check failed
root@cubox:/home/xbian# uboot-env set bootdelay 0
CRC check failed

Code:

root@cubox:/home/xbian# uboot-env del -I
CRC check failed
Cleared
root@cubox:/home/xbian# uboot-env set < /etc/uboot-env/default.txt
root@cubox:/home/xbian# uboot-env set script boot.scr
root@cubox:/home/xbian# uboot-env set bootdelay 0
root@cubox:/home/xbian#

After a successfull reboot

Code:

root@cubox:/home/xbian# uboot-env del -i
Cleared

Then the kernel update

Code:

Setting up linux-image-3.10.30-armmp (1.1.0-1-1407324673) ...
Updating u-boot
35+0 records in
35+0 records out
35840 bytes (36 kB) copied, 0.00209413 s, 17.1 MB/s
236+1 records in
236+1 records out
242008 bytes (242 kB) copied, 0.0179418 s, 13.5 MB/s
Cleared
Image Name:   U-Boot script
Created:      Wed Aug  6 16:17:58 2014
Image Type:   ARM Linux Script (uncompressed)
Data Size:    1032 Bytes = 1.01 kB = 0.00 MB
Load Address: 00000000
Entry Point:  00000000
Contents:
   Image 0: 1024 Bytes = 1.00 kB = 0.00 MB

Hangs on reboot, starting kernel part.

[mk01]

uboot-env del -i

will completely clear ENV. so it can't boot.

del -I is forcing also if checksum doesn't match.
will change -i for -I

---

keeping user video= works ?

[CurlyMo]

The command actually destroying boot is:

Code:

dd if=/etc/uboot-env/u-boot.img of=/dev/mmcblk0 bs=1K seek=42

When i don't run that command everything works.

[mk01]

the u-boot.img is from 17-jul. last commit was on 11-jul.

https://github.com/SolidRun/u-boot-imx6/commits/imx6

you can ask Rabeeh what it was.
how do you restore booting if flashed u-boot.img breaks it ?

[CurlyMo]

Not, i need to reflash the whole image. Why would you want to update uboot anyway? If you have a working image then that proves uboot is working. Don't fix what ain't...

[mk01]

@CurlyMo

because obviously SPL / uboot affects much more operations as we/you might think.
It is like asking why do we update RPI firmware ?

[CurlyMo]

I always though that u-boot is just a BIOS/UEFI instead of also the firmware.