I'd don't know for sure, but given the timings I'd say it's highly unlikely.
You can download the newest version of OpenELEC images for your RPi (2GB and 4GB).
=> build: r11225 (06.06.2012)
If you Raspberry Pi don't boot:
Send me an PM with informations about your SD card. (manufacturer, class, size, model)
Thanks for your help an have fun
Code: Select all
#!/bin/bash # Outer loop for build and image while : do # Inner loop for git pull while : do GIT=$(git pull) echo $GIT if [ "$GIT" = 'Already up-to-date.' ] then echo 'Waiting half an hour for another pull at Git' sleep 1800 else echo 'Kicking off the build and post build processes' break fi done # Delete old build rm -rf build.OpenELEC-RPi.arm-devel # Make release PROJECT=RPi ARCH=arm make release # Deal with dependency bug cp build.OpenELEC-RPi.arm-devel/Python-2.7.3/.objdir-target/libpython2.7.so* build.OpenELEC-RPi.arm-devel/Python-2.7.3/.objdir-target/Modules/ # Make release again PROJECT=RPi ARCH=arm make release # Set env vars for release package name TARBALL=$(ls -t ~/OpenELEC.tv/target | head -1) BUILD=$(echo $TARBALL | sed 's/.tar.bz2//') RELEASE=$(echo $BUILD | sed 's/.*-r/r/') # Copy release build to web server sudo cp ~/OpenELEC.tv/target/$TARBALL /var/www # Unpack release cd ~/OpenELEC.tv/releases tar -xvf ~/OpenELEC.tv/target/$TARBALL # Wipe virtual SD sudo dd if=/dev/zero of=/dev/vdb bs=1M # Move into release working directory cd ~/OpenELEC.tv/releases/$BUILD #Run script to create SD card sudo ../create_sdcard /dev/vdb # Make an image file sudo dd if=/dev/vdb of=../$RELEASE.img bs=1M count=910 # Compress release file zip ../$RELEASE.img.zip ../$RELEASE.img # Remove image file sudo rm ../$RELEASE.img # Copy zipped image to web server sudo cp ../$RELEASE.img.zip /var/www # Go back to OpenELEC directory cd ~/OpenELEC.tv # Loop back to start of script done
Code: Select all
sudo visudo username ALL=(ALL) NOPASSWD:ALL Ctrl-X to exit and Y to save
Hello, I'm a total noob with linux but I am stumbling around achieving little things here and there.funnel wrote:You could try editing .xbmc/userdata/guisettings.xml
Find this line and edit it to WINDOW
and a little lower try changing the resolution until it fits
This worked when I played with it over HDMI.
If you don't want to reboot every time just kill the xbmc process over ssh and will automatically restart it with the new settings.
nice one funnel, that worked a treat - the editing via windows trick is SOO simple once you now about it!!funnel wrote:@neilpercy
You can also edit it from a windows machine by manually typing in explorer RPi's ip \\x.x.x.x. It is in the Userdata folder. The guisettings.xml file is not readonly. If anything goes wrong just delete it and will be recreated with the default settings.
Thanx!!Hansel wrote:Right then, that worked fine. So, my system for some reason doesn't like the new ccache location....Hansel wrote:...
I was just about to switch to the old ccache directory (CCACHE_DIR=$ROOT/$BUILD/.ccache)so I'll let you know how that goes.
Any ideas what's going on there?
Same here. More specifically, freezes when I try to add mt shared music folder as a source. Weirldy I can add my shared pictures folder but if I then try to actually access the pictures it hangs again. Shame, as it looks smart otherwise and would be a great replacement for the XBMC on the Xbox1keenan wrote:Scratch that, getting freezes every time I try to access the SMB share!
Not something I can live with
Code: Select all
root /etc/init.d # rpi-cecd logical_address: 0x8 physical_address: 0x2000 cec_callback: unknown event: reason=0x0001, len=0x04, retval=0x00, param1=0x0020828f, param2=0x00000000, param3=0x00000000, param4=0x00000000
Yes, you only need the files in the boot partition. In most case you only need to update kernel.img and SYSTEM, though occasionally the firmware files are also updated.smuggly wrote: PS can i just copy files from the uncompressed new builds to update? thanks!
why not unpack the build you found at http://sources.openelec.tv/tmp/image/openelec-rpi/ and copy the content of the target/ folder to the "Update" samba share like http://wiki.openelec.tv/index.php?title ... g_OpenELEC ? the bootloader files you find in the 3rdparty/bootloader folder. in this way you dont loose settings and content and thats the official OpenELEC update method.milhouse wrote:
For anyone producing and distributing new builds, would it be possible to zip up just the boot files? That would make updating a lot easier and would allow people to retain their settings and media library. I'd suggest that people only need to use the 2GB/4GB/xGB images files once (to create their SD card), then update the SD card (primary FAT partition) with the contents of the much smaller (and more frequently updated) ZIP files...