OSMC's September update is here

sam_nazarko · 2 October 2016 19:37

OSMC's September update is here. These changes come in light, as Kodi Jarvis (v16) is very stable as it nears its end of its life. We have been working on preparing OSMC for Kodi Krypton (v17) and will be offering some test builds for all platforms shortly.

This is a companion discussion topic for the original entry at https://osmc.tv/2016/10/osmcs-september-update-is-here/

chanc397 · 2 October 2016 23:37

Hi

can i downgrade from kodi Krypton testbuild to the new September update?

sam_nazarko · 2 October 2016 23:38

I assume you’re running a Kodi Krypton test build for Raspberry Pi, as at the time of writing, there aren’t any test builds for other platforms.

You can indeed downgrade back to Kodi Jarvis. The instructions for doing this are in the same test thread that you installed Kodi Krypton from

NoahAndrews · 3 October 2016 01:22

What’s this Raspberry Pi 2+ you speak of? I couldn’t find anything about it on Google or the Raspberry Pi website.

paulwebster · 3 October 2016 06:30

RPi2+ is Pi2 with CPU from RPi3 (clocked lower).
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=160578

Forst · 3 October 2016 10:52

I’m guessing downloadable images will be available later?

sam_nazarko · 3 October 2016 10:57

Yes, but for now you can install the August version and upgrade

nsoltani · 3 October 2016 13:47

Hi! Does this update bring automatic detection of raspberry pi 3 and correct overclock settings? Installed three days ago using NOOBS and have had to set configure manually to get normal cpu freq. Thank you for the hard work!!

sam_nazarko · 3 October 2016 15:10

Hello,

The overclock settings in NOOBS are already correct for Raspberry Pi 2 / Pi 3 and have been since the device was released. We do not change the default clock speed for these devices, as there is no real need to do so. This remains unchanged in this update:

github.com

osmc/osmc/blob/master/installer/noobs/build.sh#L41


      
          	mv boot-${1}.tar.xz ../../
          	rm -rf *
          	popd
          	# NOOBS modifications, i.e. future 'health' script would be in .
          	echo -e "Creating root tarball"
          	UNC_TS_SIZE_ROOT=$(du -h --max-depth=0 . | awk {'print $1'} | tr -d 'M')
          	echo "noobs" > vendor
          	tar -cf - * | xz -9 -c - > root-${1}.tar.xz
          	mv root-${1}.tar.xz ../
          	popd
          	# Set uncompressed tarball sizes
          	sed -e s/UNC_TS_SIZE_BOOT/${UNC_TS_SIZE_BOOT}/ -i partitions-pi$(echo ${1:3:4}).json
          	sed -e s/UNC_TS_SIZE_ROOT/${UNC_TS_SIZE_ROOT}/ -i partitions-pi$(echo ${1:3:4}).json
          	echo -e "Creating marketing tarball"
          	tar -cf marketing.tar slides_vga slides
          	rm -rf output
          	rm -rf vga_slides
          }
          echo -e "Building NOOBS filesystem image"
          make clean
          build_fs_image "$1"

Piero87 · 3 October 2016 16:55

Hi! I have just updated osmc, how can I use the new skin in the image?

ooZee · 3 October 2016 16:59

I think here’s your answer:

lennvilardi · 3 October 2016 20:44

The skin looks amazing, can’t wait to test it !

John_Cavanaugh · 4 October 2016 04:24

Ive lost audio since I did the upgrade on my RPI3.

Any ideas??

fzinken · 4 October 2016 04:35

Well first idea, please don’t use the “News” thread as a troubleshooting thread but open a new thread with a respective title and the required information for troubleshooting

For your specific audio problem the crucial information to tell is what audio sink you are using.

Phileas50 · 4 October 2016 06:35

When I do a dist-upgrade in Apple TV 1 I get : dpkg;error processing archive --unpack Unable to clean mess surrounding /.boot/configure-4.2.3-17-OSMC before installing another version: Read only file system. How can I overcome this? Thank you in advance.

fzinken · 4 October 2016 06:52

As said in the post above please refrain from using the “News” thread to post individual problems.

Phileas50 · 4 October 2016 07:03

Thank you and sorry about that. Won’t happen again

sleeksorrow · 4 October 2016 10:05

This is just FYI to inform people who see this issue:

The new kernel rbp1-image-4.4.16-6-osmc brings two symlinks:

lrwxrwxrwx root/root 0 2016-10-02 17:14 ./lib/modules/4.4.16-6-osmc/source → /mnt/package/kernel-osmc/src/linux-4.4.16
lrwxrwxrwx root/root 0 2016-10-02 17:14 ./lib/modules/4.4.16-6-osmc/build → /mnt/package/kernel-osmc/src/linux-4.4.16

Obviously, these destinations are nonexistent in our productive pi and lead to these console messages at installation:

Hmm. There is a symbolic link /lib/modules/4.4.16-6-osmc/build
However, I can not read it: File or Directory not found
Therefore, I am deleting /lib/modules/4.4.16-6-osmc/build

Hmm. The package shipped with a symbolic link /lib/modules/4.4.16-6-osmc/source
However, I can not read the target: File or Directory not found
Therefore, I am deleting /lib/modules/4.4.16-6-osmc/source

These messages do not have any negative effect and can be ignored.

sam_nazarko · 4 October 2016 10:13

This isn’t an issue, and this message has been visible for some time. It’s usually just the case that most people update via the official method, and not the command line, and don’t see this.

sleeksorrow · 4 October 2016 11:00

indeed. That’s what I wrote (“This is just FYI to inform people who see this issue” … “do not have any negative effect and can be ignored”)