Spot on!!! Seems to be over clocked now! Testing out some BluRay rips now.
Thank you so much, this has been bugging me forever yet nobody here was able to get it to work!
This has been covered over and over again in the Rasplex sub forum, did you try searching, dlanor, in particular has explained how to overclock in a number of forum topics in some great detail. Googling would have also thrown up thousands of hits on how to overclock your Pi.
Please do not direspect solution contributors by not looking.
This has been covered over and over again in the Rasplex sub forum, did you try searching, dlanor, in particular has explained how to overclock in a number of forum topics in some great detail. Googling would have also thrown up thousands of hits on how to overclock your Pi.
Please do not direspect solution contributors by not looking.
Regards
I think the problem digiot was having was the same as what i had
Editing the config.txt file on your PC or MAC before installation doesn't seem to work with RC4
I think the problem digiot was having was the same as what i had
Editing the config.txt file on your PC or MAC before installation doesn't seem to work with RC4
It has to be done after install using SSH
I beg to differ, works fine for me, every time using OSX, also for many other users, otherwise this 'issue' would have been reported before now.
I think what may be causing your issue is multiple overclocking settings in the file, the last one in the file takes preference, better to just delete all of the text and just insert your personal settings for overclocking, HDMI settings, overscan settings or what have you.
Personally, I have a standard config.txt file with my settings which I just overwrite the existing file with using Finder after flashing the image, simpler than SSH'ing in after booting and having to use nano.
The file's origin is OpenElec, which Rasplex uses as one of it's core programs, not something built by the Rasplex Devs.
I beg to differ, works fine for me, every time using OSX, also for many other users, otherwise this 'issue' would have been reported before now.
I think what may be causing your issue is multiple overclocking settings in the file, the last one in the file takes preference, better to just delete all of the text and just insert your personal settings for overclocking, HDMI settings, overscan settings or what have you.
Personally, I have a standard config.txt file with my settings which I just overwrite the existing file with using Finder after flashing the image, simpler than SSH'ing in after booting and having to use nano.
The file's origin is OpenElec, which Rasplex uses as one of it's core programs, not something built by the Rasplex Devs.
Regards
I had the exact same process with all previous versions. I had a config.txt pre written with my settings and i just used to overwrite the new 1 every time i done a new install
This didn't work for RC4 when I ssh after install my config.txt has been overwritten back to the original.
I tried this several times each with the same result.
The only way I could get it to work was by using SSH.
Anyway maybe it was just me or something i did, but i would advise you to ssh in and make sure everything is what you expect it to be
I beg to differ, works fine for me, every time using OSX, also for many other users, otherwise this 'issue' would have been reported before now.
I think what may be causing your issue is multiple overclocking settings in the file, the last one in the file takes preference, better to just delete all of the text and just insert your personal settings for overclocking, HDMI settings, overscan settings or what have you.
Regards
That is not the problem I am fairly clued up about this stuff and my config.txt i used to replace the new install config.txt is as follows
Anyway maybe it was just me or something i did, but i would advise you to ssh in and make sure everything is what you expect it to be
Just checked, everything is as it should be, maybe it is 'just me or something i did'.
I will mention this to my colleagues and see if they can remember this ever being raised before (which I'm sure it would have been given the many thousands of users who overclock Rasplex).
I think the issue may have been caused by a mistake(s) made in the config.txt
Maybe if it finds problems with it it reverts back to the original file ?
Anyway looks like it was "me or something i did"
Sorry for any confusion or problems i have caused :wacko:
There is no mechanism for the file to revert back or to replace a changed file.
Just a thought, are you running from an SD card and USB stick, if so, when you SSH in you will be viewing the config.txt on the USB stick and unless you also copied the config.txt to the USB stick after installing the image then you would see the original file. If running Rasplex from a USB stick then you need to copy the modified config.txt to it before booting.
Are you saying that they intentionally made the new RPi hardware incompatible with all existing RPi OS ? That would be pure idiocy on their part !
I sincerely hope it isn't so, but if it is true then I think the days of the RPi are numbered. Without backwards compatibility for the existing user base, the RPi has no real advantage to stave off the growing competition.
The B+ seems to work OK with the latest OPENELEC so likely just a additional set of drivers needed
Hello Guys
I have the same issue with the B+, usb and lan is not working.
As mentioned in the previous comments, it is definitely a driver issue. Does anyone know if there a workaround?
Note : latest openelec works and even archlinux works.
I have the same issue with the B+, usb and lan is not working.
As mentioned in the previous comments, it is definitely a driver issue. Does anyone know if there a workaround?
Note : latest openelec works and even archlinux works.
Rasplex needs to update it's firmware, the next merge with Openelec should fix it, for now use the original Pi.
I'm getting no visual on my tv. My RPi works fine with RaspBMC, but when I try to boot rasplex, I get "mode not supported" on my tv. The green LED on the pi blinks and it looks like it's working on something, but never displays anything on my tv.
I'm getting no visual on my tv. My RPi works fine with RaspBMC, but when I try to boot rasplex, I get "mode not supported" on my tv. The green LED on the pi blinks and it looks like it's working on something, but never displays anything on my tv.
The starting video mode can be changed by editing the "config.txt" file in the FAT partition of the SD card. Since that partition is readable to any normal PC OS, you should be able to edit it regardless of what PC OS you use.
The editing to be done differs depending on what video mode your TV supports and what connection type you use to connect the RPi to the TV. To get the good resolutions like 1080p or 720p you must use the HDMI video port. Normally the HDMI protocol allows the RPi to test with the best resolution, and then try a lower resolution if the first is declined. But some TV manufacturers don't follow the standard protocol well, and then you need to ensure that the RPi tries the compatible mode first.
The other port uses composite video encoding which only supports two resolutions: 50Hz 576i and 60Hz 480i (corresponds to traditional PAL and NTSC TV standards). And if you need to use that port there are several configuration values that must be changed, since the default config.txt file of RasPlex enforces use of the HDMI port.
Please describe what connection you use and what video mode your TV supports, so we can give more detailed help.
There is a document describing all variations, but that's probably a bit much to digest. But here's a link for it anyway.