Posts by mglae

No idea. Can be an issue with the "radeon" kernel driver of your Radeon R9 270X Southern Islands card.

Just use the 8.2.5 installer stick to change the parameter for the installed 9.2.3 system.

Edit: Beside of this control+alt+F3 should work in both X and text console and alt+F3 in text console only.

Sorry for being unclear. That is the syslinux boot screen. Continue to the next with:

MAIN MENU
Welcome to LibreELEC installation tool!
[...]

You have to add the noapic parameter to the installed system too:

1. Boot the install stick again.
2. On the first installer dialog press <Alt>-F3 to get the console screen.
3. Type blkid to list the partitions. Memorize your system partition device (most likely /dev/sda1).
4. mkdir /tmp/mnt;mount <Your Device> /tmp/mnt
5. nano /tmp/mnt/syslinux.cfg, add noapic. Save with <Control>-X
6. reboot

To the APPEND lines, i.e. for installer:

  APPEND boot=UUID=... installer quiet systemd.debug_shell vga=current noapic

Edit: according to your picture you already tried kernel 4.19.36

Add TimeoutSec= parameter to your mount unit, see end of systemd.mount man page.

Try following the advice and add noapic to the kernel command line.

For easiest testing start modifying /syslinux.cfg on the 9.2.3 install stick and boot from it.

What if you use "%f" or '%f' in the comskip command line?

Quote from psycho-kila

Don't know if the problem comes from that but it's really possible,

You can verify the assumption by following this post and depend the mount unit on time-sync.target.

Fuse file system mtpfs is available after installing System Tools addon but there is no integration to the system.

See Pi4 with LE 9.2.1 - slow boot and USB3 SSD problem

Excellent. Is your mother happy again?

Is there any change if you disable mpeg2 hardware acceleration?

OK, -y and -p collide.

Please use e2fsck -yf /dev/data

Use dmesg|less to check for logged errors.

It is most likely a defect file system. You can try to repair remotely, but in worst case (a real damaged file system) you stuck with a not booting system afterwards.

First identify the device: mount|grep ' /storage '. I'm assuming /dev/sda2.

Then force a fsck and reboot:

e2fsck -fy /dev/sda2
systemctl --no-block reboot

Good luck.

chewitt systemd-time-wait-sync does hang randomly on Generic because ntp slew adjusts are not detected. There has to be a jump adjust in the beginning (only be used if the time error is >0.5sec).

Assuming the initial RTC value is always "good enough" we can disable systemd-time-wait-sync on this platform with a drop-in file:

[Unit]
ConditionArchitecture=!x86-64

Quote from chewitt

Having done a bit more reading I have a suspicion we need to start using systemd to handle NTP as this adds a new systemd .target for when the initial NTP sync has completed, which would be useful in this scenario.

Or conman start to support /run/systemd/timesync/synchonized for reliability ...

On RPIs (or any other devices without RTC) time-sync.target already may work today. Start enabling the needed service:

systemctl enable systemd-time-wait-sync

Reboot a few times and check:

systemctl status systemd-time-wait-sync
systemctl status time-sync.target

If time-sync.target is always reached the dependency can be added to the wireguard unit.

Then connect the device again and just use the getedid script.

Get an EDID file from a different monitor supporting all the modes and follow the instructions for Intel devices.

The attached EDID file is only missing the 25Hz mode.