Posts by Tomaszj

I had pink screen since very beginning of booting, even on the bootloader splash screen and Android.

I have contacted GearBest and they said this is hardware fault (sent me replacement).

Tim_Taylor

Unfortunately this parameter does not work.

ukdaveuk

Your parameter makes the screen red-ish. Still not good:

LE red — imgbb.com

I guess the problem is either low level (firmware) or must be hardware fault ...

Thanks

Hi Team,

After a month of using LibreELEC kernel from kszaq's build (i use different userland based on Gentoo) on my S905W TV box i get a pink screen on the monitor:

LE — imgbb.com

I'm 99% sure this is hardware failure (HDMI port probably got damaged) and not LibreELEC kernel fault but asking just in case:

1) is there any setting which could persist in the firmware or bootloader config which could cause this?

2) can LlibreELEC interfere with low level firmware or bootloader config at all (something like changing efivars for EFI firmware in x86 world)?

I'm booting my system only from USB, never touched internal Android installation which works ok except for the very same pink screen:

Android — imgbb.com

I have tried swapping the monitors, TV and HDMI cables, its definitely something in the box itself as everything worked a week ago and stopped this Monday.

Just need to figure out if this is software related (maybe bootloader is forced to display different color depth) or a hardware failure.

Tried to contact Gearbest support but they are hopeless, giving advices like:

"Confirm the current broadcast channel is encoded channel or not, and whether the user license has expired."

Google has many hits for very same problem but different solutions, eg here::

nothing works for my case.

Thank you in advance for any hints in this matter.

Swapped USB stick and it works now. Booting from micro SD also works.

Cant believe the solution was so simple!

Thanks for your help.

I am able to manually mount partitions from the debug shell just fine.

Booting continues (kind of) when i start init again. I doubt its an usb stick fault.

At first look seems to be a bug in the init script but it works for other users so its a bit confusing.

I was going to modify init (hammer approach - always mount /dev/sda partitions) and see how it goes but i cant find the ramdisk.

Is is built directly into the kernel? That would make things more complicated ...

Have no experience with ARM whatsoever thus asking here.

(Any developer documentation link? Would stop wasting your time. I'm developing and maintaining x86 linux distro built practically from scratch so i should be familiar with most of this stuff.)

Thanks

Hi team,

(Sorry for hijacking but W95 is mentioned here already)

Got my cheapo W95 TV Box yesterday (S905W) and i cant boot kszaq's or any other build on it.

Using 'Reboot to libreelec' app from Play Store and booting from usb stick. Burned using official LibreElec tool.

First i got 'Could not mount LABEL=LIBREELEC' error but blkid shows that device and all partitions are available and correct. Manual mounting works.

I though 'delay issue' so i ran /init script again, splash started but booting stopped again at the 'switch_root' stage. Could not do anything now as /proc and /dev are 'mount move' to /sysroot i guess.

Tested following builds:

LibreELEC-S905.arm-8.2-8.2.2.3.img.gz

LibreELEC-S905.arm-8.90.2.img.gz

and device trees:

gxl_p212_2g.dtb

gxl_p212_2g_nand.dtb

gxl_p212_2g_slowemmc.dtb

Here are photos if they could be of any help:

IMG 20180118 143751 — imgbb.com

IMG 20180118 143903 — imgbb.com

Would be grateful for any pointers what i'm doing wrong or what else i could try.

Thanks