OpenELEC meets Raspberry Pi - part 1 (XBMC)

[tzzhc4]

I took the base Debian image and replaced the kernel.img that comes with it with the KERNEL that compiles from OpenELEC and that boots but it is not finding the SYSTEM file in the same partition (least that is what I am assuming) and I get a "error in mount_disks: mount_part". Am I missing something small or just down the wrong path entirely?

[gavinlew]

Well I've tried to get it booting and unfortunately I have failed.

This is what I've done so far ;

Setup a new SD card following ; http://elinux.org/RPi_Advanced_Setup

Downloaded the Debian .zip as this is needed to extract the files which reside on the FAT32 partition

Placed the following files on the FAT32 partition of the card-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm128_start.elf
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm192_start.elf
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm224_start.elf
-rw-r--r-- 1 gavinlew gavinlew 16528 2012-04-24 20:58 bootcode.bin
-rw-r--r-- 1 gavinlew gavinlew 141 2012-04-24 20:58 cmdline_testmode.txt
-rw-r--r-- 1 gavinlew gavinlew 142 2012-04-24 21:16 cmdline.txt
-rw-r--r-- 1 gavinlew gavinlew 8126852 2012-04-24 20:59 kernel.img
-rw-r--r-- 1 gavinlew gavinlew 314691 2012-04-24 20:58 loader.bin
-rw-r--r-- 1 gavinlew gavinlew 208 2012-04-24 20:58 onetime-config.txt
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 start.elf ** kernel.img is actually the OpenELEC .kernel file (renamed)** start.elf is a copy of arm128_start.elf Edited cmdline.txt to be dwc_otg.lpm_enable=0 rpitestmode=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200
console=tty1 root=/dev/mmcblk0p2 rootfstype=squashfs rootwait Next, used "dd" to write the OpenELEC .system file to the second partition on the SD card dd bs=1M if=OpenELEC-RPi.arm-devel-20120424114828-r10695.system of=/dev/sdb2 Put the newly created card into the Pi, booted up and got system halted errors on screen. From what I can see is the kernel starts to boot then crashes. Any Ideas? 

[drdobsg]

gavinlew said:


Well I've tried to get it booting and unfortunately I have failed.

This is what I've done so far ;

Setup a new SD card following ; http://elinux.org/RPi_Advanced_Setup

Downloaded the Debian .zip as this is needed to extract the files which reside on the FAT32 partition

Placed the following files on the FAT32 partition of the card-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm128_start.elf
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm192_start.elf
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 arm224_start.elf
-rw-r--r-- 1 gavinlew gavinlew 16528 2012-04-24 20:58 bootcode.bin
-rw-r--r-- 1 gavinlew gavinlew 141 2012-04-24 20:58 cmdline_testmode.txt
-rw-r--r-- 1 gavinlew gavinlew 142 2012-04-24 21:16 cmdline.txt
-rw-r--r-- 1 gavinlew gavinlew 8126852 2012-04-24 20:59 kernel.img
-rw-r--r-- 1 gavinlew gavinlew 314691 2012-04-24 20:58 loader.bin
-rw-r--r-- 1 gavinlew gavinlew 208 2012-04-24 20:58 onetime-config.txt
-rw-r--r-- 1 gavinlew gavinlew 2000828 2012-04-24 20:58 start.elf ** kernel.img is actually the OpenELEC .kernel file (renamed)** start.elf is a copy of arm128_start.elf Edited cmdline.txt to be dwc_otg.lpm_enable=0 rpitestmode=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200
console=tty1 root=/dev/mmcblk0p2 rootfstype=squashfs rootwait Next, used "dd" to write the OpenELEC .system file to the second partition on the SD card dd bs=1M if=OpenELEC-RPi.arm-devel-20120424114828-r10695.system of=/dev/sdb2 Put the newly created card into the Pi, booted up and got system halted errors on screen. From what I can see is the kernel starts to boot then crashes. Any Ideas? 

I haven't tried this yet, but: rename the .system file SYSTEM and copy it into the same folder as the KERNEL.  I would imagine you will need to re-size the partition.  When you install OpenElec on a standard PC, I think that is how it works.

[tzzhc4]

drdobsg said:


I haven't tried this yet, but: rename the .system file SYSTEM and copy it into the same folder as the KERNEL.  I would imagine you will need to re-size the partition.  When you install OpenElec on a standard PC, I think that is how it works.


Tried that earlier and it still stops with an error after loading KERNEL.

[Helpme1986]

drdobsg said:


I haven't tried this yet, but: rename the .system file SYSTEM and copy it into the same folder as the KERNEL.  I would imagine you will need to re-size the partition.  When you install OpenElec on a standard PC, I think that is how it works.


I tried this and didnt work, before and after editing cmdline.txt same error as gavinlew

Guess we will have to wait for OpenELEC to release the secret lol

[gavinlew]

The .system file is a squashfs file system, i wonder if we have to pass something in the .txt options file to tell the kernel to boot and decompress it - I'll look at the instructions for building OpenELEC on another device tomorrow and see if that explains anything.

I think DDWRT also uses SquashFS as its filesystem, I wonder if thats booting on a PI - maybe some hints there.

[tzzhc4]

Kernel options looks different for OpenELEC. Do we have the source for SYSTEM wrong? isn't mmcblk0p2 partition 2?

https://github.com/OpenELEC/OpenELEC.tv/pull/324

[tzzhc4]

Would someone who has OpenELEC working please post the output of

cat /proc/cmdline




That looks like all the rest of us need.

[tzzhc4]

This cmdline.txt boots (I copied SYSTEM to the ext4 partition I labeled OE_DATA but after the boot is complete the screen goes black. Network is up and pingable but no display:

boot=LABEL=OE_DATA ssh debugging progress

[tzzhc4]

Ok, got it working. Here is what I did.

4 partitions:

Device Boot      Start         End      Blocks   Id  System
dev/sdb1               1          14      112423+   c  W95 FAT32 (LBA)
dev/sdb2              15          80      530145   83  Linux
dev/sdb3              81        1909    14691442+  83  Linux
dev/sdb4            1910        1961      417690   82  Linux swap / Solaris

The FAT paritions contains the following all from the Debian image /boot partition but the kernel.img if the KERNEL file that the OpenELEC makes. Also I copied in the 128/128 file to that the GPU would have more RAM.

root@localhost:/media/BOOT# cp arm128_start.elf start.elf

root@localhost:/media/BOOT# ls -la /media/BOOT
total 16226
drwx—— 2 root root   16384 1969-12-31 18:00 .
drwxr-xr-x 5 root   root      4096 2012-04-24 19:27 ..
-rwxr-xr-x 1 root root 2029700 2012-04-24 19:14 arm128_start.elf
-rwxr-xr-x 1 root root 2029700 2012-04-24 19:15 arm192_start.elf
-rwxr-xr-x 1 root root 2029700 2012-04-24 19:15 arm224_start.elf
-rwxr-xr-x 1 root root   16528 2012-04-24 19:15 bootcode.bin
-rwxr-xr-x 1 root root     273 2012-04-24 19:15 boot_enable_ssh.rc
-rwxr-xr-x 1 root root      81 2012-04-24 19:16 cmdline.txt
-rwxr-xr-x 1 root root      26 2012-04-24 19:15 issue.txt
-rwxr-xr-x 1 root root 8126852 2012-04-24 19:15 kernel.img
-rwxr-xr-x 1 root root  314691 2012-04-24 19:15 loader.bin
-rwxr-xr-x 1 root root 2029700 2012-04-24 19:15 start.el

cmdline.txt contains:

dwc_otg.lpm_enable=0 boot=LABEL=SYSTEM disk=LABEL=STORAGE ssh debugging progress

Partitions are named BOOT/SYSTEM/STORAGE

/dev/sdb1 on /media/BOOT type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)
/dev/sdb2 on /media/SYSTEM type ext4 (rw,nosuid,nodev,uhelper=udisks)
/dev/sdb3 on /media/STORAGE type ext4 (rw,nosuid,nodev,uhelper=udisks)

The second partitions contains the SYSTEM and KERNEL file that OpenELEC creates and the STORAGE is just empty.

root@localhost:/media/STORAGE#   ls -la /media/STORAGE

total 89364
drwx——    3 root root      4096 Apr 25 00:17 .
drwxr-xr-x   14 root     root           226 Apr 24 08:39 ..
-rw-r–r–    1 root     root       8126852 Apr 25 00:17 KERNEL
-rwxr-xr-x    1 root     root      83357696 Apr 25 00:17 SYSTEM

[cvtj97]

Mine boots to the splash screen, then goes black

[tzzhc4]

cvtj97 said:


Mine boots to the splash screen, then goes black



What cmdline.txt settings are you using?

[cvtj97]

dwc_otg.lpm_enable=0 boot=LABEL=SYSTEM disk=LABEL=STORAGE ssh debugging progress

[tzzhc4]

cvtj97 said:



dwc_otg.lpm_enable=0 boot=LABEL=SYSTEM disk=LABEL=STORAGE ssh debugging progress



Can you ssh into it? Wondering because the first few times before I had all the file in the right place it would come up on the network but I couldn't ssh into it since it wasn't all the way up even though it was pingable. Wondering if yours is coming all the way up but not displaying for some reason. If it isn't pingable than we need to take a few steps back and see what is up.

[cvtj97]

Its pingable but no ssh

What did you name your system file?

[tzzhc4]

cvtj97 said:


Its pingable but no ssh

What did you name your system file?



SYSTEM, here is it mounted after booting all the way.

root ~/mnt # ls -la /flash
total 89364
drwx------    3 openelec openelec      4096 Apr 25 00:17 .
drwxr-xr-x   14 root     root           226 Apr 24 08:39 ..
-rw-r--r--    1 root     root       8126852 Apr 25 00:17 KERNEL
-rwxr-xr-x    1 root     root      83357696 Apr 25 00:17 SYSTEM
drwx------    2 root     root         16384 Apr 25 00:13 lost+found
root ~/mnt #

root ~/mnt # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
none                     60820       116     60704   0% /dev
/dev/mmcblk0p2          521780    106136    389140  21% /flash
/dev/mmcblk0p3        14460840    468796  13257472   3% /storage
/dev/loop0               81408     81408         0 100% /
none                     62284         0     62284   0% /dev/shm
/dev/mmcblk0p1          112186     16206     95980  14% /var/media/BOOT

root ~/mnt # mount
rootfs on / type rootfs (rw)
none on /dev type devtmpfs (rw,relatime,size=60820k,nr_inodes=15205,mode=755)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/mmcblk0p2 on /flash type ext4 (ro,noatime,barrier=1,data=ordered)
/dev/mmcblk0p3 on /storage type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/loop0 on / type squashfs (ro,relatime)
none on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
none on /dev/shm type tmpfs (rw,relatime)
none on /var type ramfs (rw,relatime)
/dev/mmcblk0p1 on /var/media/BOOT type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0077,codepage=cp437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro)

[romland]

Great job with this tzzhc4. That command line works over here, but like cvtj97, my screen goes black after splash. But the difference here is that I can SSH in.

Bit of a crux since I simply don't know enough about OpenELEC to poke around. But will dig a bit. If you have any idea, I'd be happy to hear them

[tzzhc4]

romland said:


Great job with this tzzhc4. That command line works over here, but like cvtj97, my screen goes black after splash. But the difference here is that I can SSH in.

Bit of a crux since I simply don't know enough about OpenELEC to poke around. But will dig a bit. If you have any idea, I'd be happy to hear them



No problemo, just really wanted to get someplace with OpenELEC. The first boot took a lot longer than subsequent boots. Not sure if it sets something up. ssh in (user:root password:openelec) and do a df -k and ps -ef |grep xbmc

You should see everything mounted and the xbmc process:

root ~/mnt # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
none                     60820       116     60704   0% /dev
/dev/mmcblk0p2          521780    106136    389140  21% /flash
/dev/mmcblk0p3        14460840    468796  13257472   3% /storage
/dev/loop0               81408     81408         0 100% /
none                     62284         0     62284   0% /dev/shm
/dev/mmcblk0p1          112186     16206     95980  14% /var/media/BOOT

root ~/mnt # ps -ef |grep xbmc
952 root      19:39 /usr/lib/xbmc/xbmc.bin --standalone -fs --lircdev /var/run/lirc/lircd
1633 root       0:00 grep xbmc

root ~/mnt # df

-k
Filesystem           1K-blocks      Used Available Use% Mounted on
none                     60820       116     60704   0% /dev
/dev/mmcblk0p2          521780    106136    389140  21% /flash
/dev/mmcblk0p3        14460840    468796  13257472   3% /storage
/dev/loop0               81408     81408         0 100% /
none                     62284         0     62284   0% /dev/shm
/dev/mmcblk0p1          112186     16206     95980  14% /var/media/BOOT

[cvtj97]

It works!

Probably had it long ago just didn't let it sit long enough?

Now we need to create an image file like the other OSes, make it a little easier for everyone to get running

[romland]

Yeah. XBMC is the problem, seems an init script gets unhappy.

This goes into an infinite loop (starts/stops/starts…)

/usr/lib/xbmc/xbmc.bin –standalone -fs –lircdev /var/run/lirc/lircd

And this is the only XBMC related thing (not) running. Will poke around in /etc/init.d and see if I can see something

[cvtj97]

tzzhc4

Have you noticed the Pi getting a little warm?

[tzzhc4]

cvtj97 said:


Now we need to create an image file like the other OSes, make it a little easier for everyone to get running



Certainly easy enough to make an image with dd or WinImage. Right now I am running XMBC through some tests (continuous video playback) to see how hot it gets. Want to know if I should print a different case with more vents. So I can crank out an image tomorrow if you want.

[tzzhc4]

cvtj97 said:


tzzhc4

Have you noticed the Pi getting a little warm?



Yeah, it is warm. I am playing a video continuously to see how warm it ends up getting. Right now I have it in this case. If it gets much warmer I will print the top that is completely vented.

http://www.thingiverse.com/der.....tive:27071

http://www.thingiverse.com/thing:16104

[cvtj97]

I'm impressed with the video so far, sound is decent through the tv speakers.  Wish I had a receiver with HDMI, see if DTS works

I have some small heatsinks I'm going to try putting on it.

[tzzhc4]

cvtj97 said:


I'm impressed with the video so far, sound is decent through the tv speakers.  Wish I had a receiver with HDMI, see if DTS works

I have some small heatsinks I'm going to try putting on it.



Yeah, it is pretty impressive for something so small and so cheap! Frankly I can't wait till they are widely available as I want to get 4-5 more and replace some of my more power hungry home automation controllers.

How are you attaching the heatsinks, thermal epoxy or something else?