Overclock is not working like it works on Raspbmc and Openelec

Hello,

 

i switched from XBMC to PLEX with my Raspberry.

 

Now i have the Problem that Overclock is not working. 

 

With Raspbmc and Openelec-XBMC i could easy run with 1000/500/500/6 Settings.

 

Now with Rasplex i dont get him to run above 800.

 

Is there something i missed ? Is there a Version where it is working ?

 

i tried Current / .18 /.20

 

 

 

Thanks a lot

 

Without seeing your "config.txt" content it's impossible to say what you may have missed in it.

You also don't say how you did the editing of it, which also matters, as some editing methods only affect a temporary copy, replaced at next boot.

I always set up my overclocking simply by editing the "config.txt" file in the small FAT partition of the SDcard and (if used) USB3 stick.

I do this by connecting the device to a Windows computer and using my normal text editor (UltraEdit) to edit the "config.txt" file.

Another factor to consider is that overclocking can only be used safely with a fast SDcard and USB3 sticks.

Doing it with a slow SDcard and/or a USB2 stick is to invite disaster (corrupted storage content).

I also avoid using the top overclock and overvoltage settings, as going that close to the limits is always risky.

So the settings I use are more like 950/450/450/4 (assuming I understand your notation correctly).

I've used these settings with each RasPlex version from 9.9.18 through 9.9.20 (the latest currently available),

and they work fine for me with all class10 SDcards and USB3 sticks.

Best regards: dlanor

it´s a Class 10 SD Card and i edit the config.txt on my windows-pc via Notepad.

When i used Open-elec i made it like that and it worked. thats why i dont know whats wrong.

It worked with Open Elec and Raspbmc. And now witch Rasplex its not working the same way.

it´s a Class 10 SD Card and i edit the config.txt on my windows-pc via Notepad.
 
When i used Open-elec i made it like that and it worked. thats why i dont know whats wrong.


Neither do I. RasPlex is also based on OpenELEC, so basic things like "config.txt" should work the same.
But of course there are slight differencies between the files, which might trip you up.
 

It worked with Open Elec and Raspbmc. And now witch Rasplex its not working the same way.


But for me it IS working pretty much the same way, though there are a few pitfalls to avoid.

For example:
The "config.txt" contains duplicate entries for a few things, some of which are commented out.
Now if you were to edit only the first entry of such a duplicate pair, then the second one could override your change.

Like I said before, we need to see the contents of your "config.txt" file, in order to give specific advice.

Also, since you are trying to speed up your RasPlex, you really should consider using the USB3 method.
This alone had a much greater effect for my setup than just overclocking had. (But I do use both now.)

Best regards: dlanor

OK. Tomorrow i am home again and take a look on the differences of my config.txt´s.

Is there a Topic about the USB 3 method ?

@dlanor : If you could make an USB3 tutorial, i could pin this one out on the forums :)

1. flash both sd-card and usb drive from raqsplex installer

2. replace the original content of cmdline.txt on the sd-card with
this : "boot=/dev/sda1 disk=/dev/sda2 quiet oprofile.timer=1"

from

https://forums.plex.tv/topic/63442-rasplex-running-from-usb/

Without seeing your "config.txt" content it's impossible to say what you may have missed in it.

You also don't say how you did the editing of it, which also matters, as some editing methods only affect a temporary copy, replaced at next boot.

I always set up my overclocking simply by editing the "config.txt" file in the small FAT partition of the SDcard and (if used) USB3 stick.

I do this by connecting the device to a Windows computer and using my normal text editor (UltraEdit) to edit the "config.txt" file.

Another factor to consider is that overclocking can only be used safely with a fast SDcard and USB3 sticks.

Doing it with a slow SDcard and/or a USB2 stick is to invite disaster (corrupted storage content).

How does using a USB3 stick make a difference? The Pi only supports USB 2.0...

With a USB3.0 stick u get the Maximum out of your USB 2.0 interface.

And this is more then most of Sd-Cards do.

And i think the more important point is that while u overclock there may occur errors on your sd-card.

this is not happening with an USB stick.

Thats what i read the last 2 days. hope this is right so far

With a USB3.0 stick u get the Maximum out of your USB 2.0 interface.
 
And this is more then most of Sd-Cards do.

Indeed, and most USB2 sticks do not even come close to the limits of a standard USB2 port, such as the RPi has.
But a good USB3 stick will allow the USB2 port to be used to the maximum capacity of the RPi.
And with some sensible overclocking, that capacity itself can be raised a bit higher.
 

And i think the more important point is that while u overclock there may occur errors on your sd-card.
this is not happening with an USB stick.

 
To be perfectly clear, it's only USB3 sticks that are useful for RasPlex.
Many common USB2 sticks are even slower than class 4 SDcards, making it pointless to use them with an RPi.
 

Thats what i read the last 2 days. hope this is right so far

 
I agree with almost everything you said in your posts, though some clarification was in order.
There are also some additional measures I take to ensure best results, such as expanding the main storage partitions.
There's also some doubt about the best way to deal with "cmdline.txt", as some users report loss of SSH access.

Here is my own install procedure for best results:

1: Use RasPlex installer or "Win32 Disk Imager" twice, to install the RasPlex image both on the SDcard and the USB3 stick.

2: Use the free edition of "Paragon Partition Manager" to expand the Ext4 partition (2nd partition) to fill out the unused area.
NB: This is important only for the USB3 stick, but I do it for the SDcard as well, just in case I later decide to use it stand-alone (which also requires re-editing its "cmdline.txt".) Expanding the USB3 partition might be unnecessary for a small Plex library, but for a large one it really is important, and in any case it would be pointless to leave 14GB of a 16GB stick completely unusable for RasPlex cache storage.

3: Edit the "cmdline.txt" file of both SDcard and USB3 stick to contain the following line:

boot=/dev/sda1 disk=/dev/sda2 ssh quiet oprofile.timer=1

NB: Having the same command line both on SDcard and USB3 stick ensures consistent behaviour for all hard and soft reboot methods.

4: If you want overclocking you can add the following near the end of your "config.txt" files like I do (again for BOTH devices).

arm_freq=950
core_freq=450
sdram_freq=450
over_voltage=4

As you can see by comparing these settings to the examples higher up in that file, I've chosen to go 50 MHz lower than the maximum frequencies shown in those examples, and 2 steps lower with the overvoltage level. Going higher would increase the risk of damage and I don't think the speed gain it would give is worth that risk.

Also, if your RPi is enclosed by some small cupboard or other unventilated container, then you should not overclock at all.

My own RPi has a standard RPi cover (with ventilation slits) and is sitting behind my TV set on top of a Netgear switch, but with air access on the other 5 sides, and it has no heat problems. It's been running 24/7 for quite a while now, so I think I would have noticed such problems by now.

Btw: If anyone thinks it would be useful to quote any part of this post elsewhere, you are free to do so.

Best regards: dlanor

Rasplex adds some own values to the config.txt file, near the bottom.

The important part  is:

 over_voltage=0

if you made your entries in the overclocking section of the config file your over_voltage values gets overwritten. Using such high values without over_voltage probably is the cause of your problems.

over voltage was 6 all the time.

ordered a new 5.25 V - 2 A power suply and an USB 3 stick.

Gonna bring him to the maximum these days

Is there some particular reason Rasplex doesnt use F2FS? I note that Raspbmc moved to that as it solved any SD card corruption on more demanding overclocks and is generally more responsive. I no longer need to use USB installs to be able to overclock Pi safely to 1ghz. Would be nice if Rasplex allowed same safety.

Is there some particular reason Rasplex doesnt use F2FS? I note that Raspbmc moved to that as it solved any SD card corruption on more demanding overclocks and is generally more responsive. I no longer need to use USB installs to be able to overclock Pi safely to 1ghz. Would be nice if Rasplex allowed same safety.

RasPlex is based on the combination of a port of "Plex Home Theater" with a modified RPi "OpenELEC" implementation.

If/when that implementation switches to F2FS instead of Ext4, then I guess the following RasPlex releases will use the same.

As for needing USB installs for 1GHz, that has never been the case.

What you do need is a storage medium which can handle the shorter write cycles resulting from overclocking.

USB3 drives are good at that, but so are Class10 SD cards.

I've never had any corruption issues with my Class10 SD cards, overclocked to 1000, 500, 500, 6. (arm, core, sdram, over_voltage)

After the recent improvements to RasPlex speed, both in GUI and in playback, I seldom bother with the USB3 sticks for my RPi.

I still use USB3 sticks with non-RasPlex setups though, including my BerryBoot setup where I use a large USB3 drive to hold the installed OS images. Those images also include various RasPlex versions, and when accessed through BerryBoot's virtual filesystem method all of them benefit from USB3 speed for their storage. (Though top quality Class10 SDHC cards filling UHS-1 specs come close to the same results.)

Best regards: dlanor

from
 
https://forums.plex.tv/topic/63442-rasplex-running-from-usb/


Don't forget to add the 'growstorage' to the cmdline.txt file on the USB or you'll find that you run out of storage, as happened to a fellow poster in the forum.

Don't forget to add the 'growstorage' to the cmdline.txt file on the USB or you'll find that you run out of storage, as happened to a fellow poster in the forum.


I'm sorry Ned, but I think that's wrong, according to my own past experience.
The 'growstorage' command had no effect at all for a USB drive.
That command only worked for a 'pure' SD card installation.

If that has been changed it is news to me...

The Ext4 partition of a USB stick needs to be extended by some real partitioning tool.

I've used the free edition of "Paragon Partition Manager" to do this on my Win7 system.
Linux systems should have native tools for Ext4 partition management.
As for Mac OSX systems, I have no clue...

Btw: since I mentioned BerryBoot above I should also add that when using BerryBoot there is no need for the user to extend the USB partition, as BerryBoot will handle its formatting on its own. (A truly weird multi-partitioning scheme :D )

Best regards: dlanor

@dlanor

Great work!

I followed your guideline, as I had some issues with speed and high bitrate movies.

With your setup I am able to play my "reference movie", an extract of "Earth" with temporary bitrates of 73 mbps

on rasplex without stuttering, even PHT  on my iMac is not capable of playing it untranscoded (strange!).

Greetings

Unlight

@dlanor
 
Great work!
 
I followed your guideline, as I had some issues with speed and high bitrate movies.
With your setup I am able to play my "reference movie", an extract of "Earth" with temporary bitrates of 73 mbps
on rasplex without stuttering, even PHT  on my iMac is not capable of playing it untranscoded (strange!).


I'm glad it worked out so well for you. :)

Best regards: dlanor

One quick question :

What about updates? I assume the update process just writes to the sd? Can I just flash the usb stick with winimager and place it back?


Unlight

One quick question :
What about updates? I assume the update process just writes to the sd? Can I just flash the usb stick with winimager and place it back?


That's a very good question, and I find it particularly interesting since I'm not 100% sure of its answer (yet).

There's no strong reason for it to be SD card specific though, as an update doesn't replace the OS.
The update files are placed in the existing filesystem and used from there by the update routine.
So this means that it does have the ability to replace files within that filesystem, on any device.
Thus it should replace files on SD if running from SD, but do it on USB if running from USB.

But there could still be problems in the coding which may interfere with the update process on USB.
The only way to tell for sure whether it works or not is to try it, so that's what I'll do.

I'm going to test auto-updating of an rc5 build to the new 0.4.1 version.
This is a test I have already performed for a normal SD card installation, where I know it works.

I will now do this test both for a SDcard+USB3 combo installation, and also for a BerryBoot installation on USB3.
I expect that the first update test will work well, but I'm more doubtful about the update under BerryBoot.

In my next post here I will report on the results of those tests.

Best regards: dlanor