[nitrus]

[quote=122280]Hello again
I have now used this dualboot and tweaked it into my prefered settning regarding background pictures etc.
I just have one last (?) question;
How do I edit the config.txt?
I wanna overclock it a little and mostly, add my codes for the
decode_MPG2=0x00000000
decode_WVC1=0x00000000
I keep gettin errors both from SSH and WinSCP that I am not allowed to edit the file.
[/quote]

I think OpenELEC should allow you to edit the files with the default root/openelec combination of username/password.

As for other types of OSes like Raspbian and RetroPie, you’d need root permissions to edit the file.
In order to login through WinSCP as ‘root’, you’d first need to set a root password. You can google how to do that.
Or you could login as pi/raspberry with SSH or your preferred method and then edit the file with nano:
$ sudo nano /boot/config.txt

[nitrus]

Ah yes, thanks for the clarification. In truth I had read this forum post in the meantime:
http://openelec.tv/forum/120-news-announcements/80664-beta-openelec-7-0-beta-1-released

It says “The OpenELEC 7.0 Beta 1 (internal version 6.95.1) release has been published.”
There is nothing internal about 6.95.1 if you’re giving that to the world.
But code-wise, OS_VERSION is “7.0”, and OPENELEC_VERSION is “6.95.1”, so it’s kinda/sorta valid, although it does make me cringe.
The 6.95.1 tag and 7.0 master branch differ quite a bit, so the non-beta 7.0 might be quite different, depending on what point in time/commit they decide to tag from when they finally release it.

It’s not how conventional RC and Beta release naming works, but hey, who am I to tell the devs ,the people who actually make the product their business.
So sorry for the confusion and hijacking the thread with nonsense, not gonna do it any further, I promise!

Bottomline: Smithers’ releases are top notch, no matter what version of OpenELEC they’re including! :D

[nitrus]

Where do you guys get your OpenELEC 7 beta versions, short of building it yourself?

As of now (March 30th, GMT+2 slightly past morning time) I can still only see 6.95.1 both on their official page and github releases.
Furthermore, I don’t see a release candidate/source tag for 7.0 on github, only the code branch.

Granted, the 6.95.1 version does have Jarvis, which I personally was most interested in.

[nitrus]

Hi again Steve
Thank you for the NOOBS link, much obliged!

I’ve one more thing to add here:
There seems to be an OpenELEC offshoot called LibreELEC. It’s running Jarvis (Kodi 16)

I’ll PM you links and my findings, if you want to test that out for future builds, as I will certainly be doing :)

It seems they’re in the early stages, but I can see myself switching just because I’m impatient for the OpenELEC 7.0 version…

Cheers,
Nitrus

[nitrus]

Hi smithers,
Just wanted to say your builds are immensely awesome, I’ve used them often in the past, now I’ve switched to making my custom OSes and use your NOOBS files, which are PERFECT.

I’ve tested with RPi2 and RPi3 and it works great so far.

Main reason for custom OSes is that I want to pack a shutdown button script which I trigger via GPIOs, then drill a hole in the case and glue a momentary button. It’s easier on the power connector, and not-so-techy friends and family can shutdown without the risk of filesystem corruption. And I don’t have to explain SSH.

I can’t believe loading OSes from USB still hasn’t made it in the official NOOBS release, as it’s incredibly useful. I’ve seen somewhere that you do actually refer to an “official build of NOOBS USB version”, where can one find this, if it exists?

I’ve tried PINN, which is a NOOBS fork, yet not NOOBS, (https://github.com/procount/pinn), but I couldn’t switch to another OS with it for some reason. Installed the OS, but not displayed it as an option afterwards.

In any case, you’ve said that you’re using a “dirty workaround” in order to support RPi3, and in the PINN release I see that there’s a rpi3 overlay. Now, I can’t pretend to understand how NOOBS works, I haven’t looked at the code at all, just thought that it might give you an idea if you’re still working on something like that.

Cheers, and keep bringing the joy!

EDIT: Also, have a gander at this:
http://downloads.raspberrypi.org/os_list.json
…and the subsequent relevant partition files etc.
If you’re already hosting the tarballs, this could be used for a network install. Not sure whether it uses local storage or cache/RAM for this, so it may still be keeping the files on the SD card, which wouldn’t be that useful.
EDIT2: After I JUST wrote this, I noticed there is a new official NOOBS version from today, if it makes any difference.

[Author]

Posts