Provided you have the latest version of the petitboot
From CoreELEC-Amlogic-ng.arm-9.2-nightly_20200116-Odroid_N2.img.gz extract kernel and system.
N2 in usb mass storage mode - # ums /dev/mmcblk0
Copy files and exit this mode - # ums.
Restart
Neither do turn on my screen (Pioneer PDP-507xa) in SPI mode, which got me worried enough to use: petitboot Recovery Image (20190417) (see the first sentence in this post).
Which fixed things, and then I installed the stable latest petitboot again.
Once more I could run the latest CE nightly from a uSD, although still blind as a bat in SPI mode.
I started to look for a solution for the “flying blind” situation and stumbled upon this.
I installed my emmc, booted CE from my uSD, enabled ssh, and proceeded by coping the latest CE nightly with winSCP to the ‘/var/media/STORAGE/.update’.
Behold, it apparently flashed the emmc, since I have my old system again with the latest nightly CE.
Have not yet found any solution to the bats bashing into the plasma tv situation, sweeping up those buggers is a chore, which would be nice to have fixed. The mentioned usb mass storage mode could very well save my precious N2, although unlikely, if the need would arise.
Although, it mentions to alter the: kernel parameter ‘disable_uhs=<true|false>’? How does one unlock this achievement, being blind?
Hey, can anyone help me work out how to make 4k rips look correct? I’m connected to an LG C8 via a Sony STR-DN1080 ( Home Theatre AV Receiver). I get a picture no problem but I see banding in the picture that I don’t get when playing back directly on the TV (either via USB or via something like Emby).
If I try and echo 420 into the attr file I just get a loss of signal when I try and play back any files.
Is this an HDMI cable issue? Do I need newer better cables?
You may need to configure the AVR and make sure the input/output is set to HDMI 2.0 or Deep Color.
Also, don’t use attr, you can set everything that the system supports through the CE settings.
@TheCoolest Yes I’ve made sure that the HDMI is set to “Enhanced” instead of standard and makes no difference. After I posted last night I tried connecting the N2 directly to the TV, bypassing the amp and same issue. I have HDMI on the TV set to deep colour or whatever the term is but it’s the same. By the way, I realised I posted into the wrong thread as I’m using current stable branch. Is this something that has been fixed/changed in subsequent nightly releases?
This must be something my TV is doing, I have a Windows 10 machine that produces the same banding effect that I’m seeing on coreelec, suggesting it’s an HDMI setting on the TV or something that is introducing this problem.
OK, so I think I’ve solved it…for some reason on the LG TVs, if you label an HDMI input as “PC” it changes something, not sure what. I changed this to something else and it has solved the issue!
@roidy I have no idea, the manual for the TV doesn’t seem to explain what it does. I can’t even think where I read to set the label as that in the first place! It does mean that if you have are running everything via an amp, so single cable to the TV everything then has to be on the same setting. If I ever get round to it I may move my PC straight to the TV and use eARC for the audio to the amp.
@TheCoolest it does support eARC, I think it was added in an update later on. edit* or maybe not, it’s not often I’ve used it so can’t say whether I’ve actually noticed what’s fed to the amp.
OK, new issue I’ve noticed with 4k rips is every so often, like maybe 4-5 times throughout the film there will be a random patch of “broken” pixels that last a split second. I didn’t see this issue before so not sure what else has changed.
Would old HDMI cables manifest this kind of problem as I’ve never seen it before until I changed that TV label setting on my LG Oled TV.
Is it worth enabling the 422 chroma setting under the coreelec settings?