lost+found is normal for ext? file systems and may be created even without error.
LE_SYSTEM can be even formatted FAT32, only LE_DATA needs ext4.
Posts by mglae
-
-
I mounted the LE_SYSTEM partition in Ububtu [...]
That is really odd. You can try the same with grub console. On the grub boot menu press 'c' to open the console. Then:
Codels -l (hd0,5)/I have no experiences with rEFInd but in general you have to pass 'boot=LABEL=LE_SYSTEM disk=LABEL=LE_DATA quiet nosplash' as parameters when booting the KERNEL file.
-
The "ext2" module supports ext2, ext3 and ext4.
error: file `/KERNEL' not found.
Most likely the kernel file is not named "KERNEL". Please keep in mind that ext4 is case sensitive.
-
Better avoid the number game:
Codemenuentry "LibreELEC (KODI)" { insmod part_gpt insmod ext2 search --set=root --label LE_SYSTEM linux /KERNEL boot=LABEL=LE_SYSTEM disk=LABEL=LE_DATA quiet nosplash } -
-
CvH thanks for the testbuild. I only liked to avoid an untested PR.
-
squezzelite dlopen()'s libraries by default. Linking the libraries look promising, but I have no environment to test.
-
The install media can be used to edit or copy files.
-
The CIR likely has a real power button function that is handled by eventlircd. Disabling it needs some effort.
To disable power button handling in eventlircd:
cp /usr/lib/udev/rules.d/98-eventlircd.rules /storage/.config/udev.rules.d
Find the following three lines in the copied file and delete them.
CodeSUBSYSTEMS=="acpi", ATTRS{hid}=="LNXPWRBN", \ ENV{eventlircd_enable}="true", \ ENV{eventlircd_evmap}="default.evmap"After reboot eventlircd handling is disabled but systemd takes over and still powers off the machine.
To disable power button handling in systemd create or extend /storage/.config/autostart.sh with the following line and reboot.
Codesystemd-inhibit --what=handle-power-key sleep 1000d &Now the power event reaches kodi and can be handled with a custom keymap.
Please take a note to update the modified 98-eventlircd.rules file on every LibreELEC update.
-
Can you still add option 3840x2160p59,94?
Just add the corresponding two lines from this thread.
-
Which IR receiver do you use?
-
A possible work flow is to create the autostart.sh containing the two lines with notepad++, saving it with Unix line endings and copy it with winscp.
-
Is there an option to add 3840x2160 / 50 HZ to libreelec
There seem no samples around, but recalculating the 3840x2160p60 modeline (which is in reality 59,94Hz) gives:
Bashxrandr --newmode "3840x2160p50" 495 3840 4016 4104 4400 2160 2168 2178 2250 +hsync +vsync xrandr --addmode DP2 3840x2160p50It's only theory, I have no 4K TV.
-
This MB - ASRock > J3455-ITX
Apollo Lake only supports HDMI 1.4 itself. Therefore ASRock uses a DP-HDMI converter on the board for the HDMI 2.0 connector.
However I am able to manually select 3840x2160p @ 30 Hz on DVI port despite spec saying otherwise?!?? And even 59.94 after sending out the command as above.
It's a HDMI 1.4 interface with an attached DVI connector supporting 30Hz. If it really works with 59.94Hz it is outside the spec.
Is the latest BIOS installed and are you using the same TV HDMI port as for the Amlogic box?From the software side you can try a Milhouse Testbuild using kernel 4.14 and latest graphics drivers. Put it on an USB stick and boot using the "run" option.
-
Forget the "live" mode. It always starts with an empty /storage RAM disk file system and no configuration is possible.
Enjoy the working configuration. -
gwilly7, do you still need the autostart lines after changing the TV's configuration?
-
First things first - am I supposed to get 4k60p output with the DP port using a DP-HDMI cable? Or can I get it right out of the HDMI port on the 3455?
Please check the motherboard specification what is supported on the HDMI port. The xrandr output let me the assume there is an internal DP-HDMI converter.
Does your external DP-HDMI converter support 4k60p?
-
Are you sure using a HDMI 2.0 port on the TV and have it configured for HDMI 2.0?
