Posts by HiassofT

Settings->System->Display->Video Calibration.

And, no, 640x480 is not correct - 720x480 is the correct resolution for NTSC. This is the same as on DVDs and includes overscan (like on DVDs).

so long,

Hias

Mario77 most RPi2s are 32bit SOCs (Cortex A7) - only the very latest RPi2 production runs used the same (64bit capable, Cortex-A53) SOC as RPi3.

so long,

Hias

Thanks for checking, you have plenty of space free so we can tick that idea off the list.

so long,

Hias

Is your storage partition full? That would explain why copying the database doesn't work.

ssh in, run "df -h" and post the output

so long,

Hias

This is already supported and if you do a clean installation of LE11 config.txt will contain the instructions how to enable it

###############################################################################
# Use distroconfig-composite.txt instead of distroconfig.txt to enable
# composite video output.
# The composite video mode needs to be configured in cmdline.txt:
# For PAL add: video=Composite-1:720x576@50ie
# For NTSC add: video=Composite-1:720x480@60ie
################################################################################
include distroconfig.txt
#include distroconfig-composite.txt

so long,

Hias

One interesting point in the ntfs-3g docs though is that it mounted the filesystem as read-only when it was dirty or had not too severe errors whereas the ntfs3 kernel driver completely refuses to mount the filesystem in that case.

This could mean users with problems (or problematic behavior / setups) would not have noticed that they had issues in the past whereas they notice the issues now.

With LE10 and before the issues would only show up when trying to write to the drive with LE (eg via SMB), but as lots of those users seem to prefer to write media from their Windows boxes, and use LE only to read the media files, that rarely happened.

so long,

Hias

If the drives worked before, on LE10, and failed at the first attempt with LE11 then one possibility is that the filesystems were already unclean but the old driver didn't care about that - whilst the new driver is more cautious (just a guess though).

Run the filesystem checks/repairs on Windows and keep an eye on it. If it happens again we would need to know what triggered that.

so long,

Hias

Quote from Mario77

Dont take me wrong but as posts about ntfs formated HDD's not mounting are popping up allover the forum..does it really looks like we have to go to the ext4 way or is this some issue that might get fixed one day?

NTFS has always been troublesome in Linux and never was a good choice. It's best to use ext4 and copy stuff via SMB or, if you really really need to connect the drive to other non-linux devices use EXFAT.

No idea if/when anything gets fixed, and so far we don't even know what the users with problem reports did (or what happened on their devices) that caused the NTFS partitions to become dirty so we are completely in the dark here (and my guess is some percentage of the reports are caused by user errors like unplugging the disk or hard pulling the plug while the drive was mounted - in that case any filesystem will get marked dirty).

so long,

Hias

Mar 30 21:44:04.219708 LibreELEC kernel: ntfs3: sda2: volume is dirty and "force" flag is not set!
Mar 30 21:44:04.226378 LibreELEC kernel: ntfs3: sdb2: volume is dirty and "force" flag is not set!

Connect the drives to a windows box and perform a filesystem check/repair.

so long,

Hias

A very popular choice is the Flirc case - I don't have any personal experience with it but other team members are quite happy with it.

Flirc Raspberry Pi 4 Case - Flirc

best Cases from flirctv - Flirc

flirc.tv

Personally I use this "Armor case", as it still lets me access the GPIOs and one can plug in a HAT (eg audio card) with a GPIO "stack" header

Raspberry Pi 4 Aluminum Alloy Heatsink Armor Case

This is an armor aluminum alloy case designed for the Raspberry Pi 4 computer model b by Geekworm. This armor case is only fit to raspberry pi 4 model b;

geekworm.com

There's also a variant which fully covers the RPi and GPIOs:

Geekworm Raspberry Pi 4 Heavy-duty Aluminum Passive Cooling Metal Case (P173)

This Raspberry Pi 4 Aluminum Case Pi 4B Heat Dissipation passve cooling metal case housing is specially designed for the latest Raspberry Pi 4 Model B…

geekworm.com

I also have the latter case but it seems - like with most cases that fully cover the RPi HDMI connectors - that you might not be able to fully insert the HDMI cable if the case or the HDMI connector is just 0.2-0.5mm too wide/thick.

so long,

Hias

Show us your config.txt and cmdline.txt files

In pretty much all cases so far people didn't add the video=... option to cmdline.txt correctly, eg adding the option in a second line (as the cmdline.txt file name suiggest, it has to contain a single line without line breaks).

so long,

Hias

No signal usually means hotplug decect not working because of a bad HDMI cable, bad HDMI connection (eg Argon one cases with notoriously broken HDMI adapter PCB) or monitors/TVs/AVRs not adhering to standards.

Do a clean installation of LE11.0.1 and add vc4.force_hotplug=1 to the end of /flash/cmdline.txt (right after "quiet", everything has to be on a single line) to workaround that.

so long,

Hias

You have to manually switch your CRT to 16:9 mode and use video calibration in kodi to compensate for the stretched / anamorphic display mode.

so long,

Hias

This is expected. Don't fiddle around with distroconfig.txt and stick to the default vc4-kms-v3d dtoverlay.

so long,

Hias

FYI: If you do a clean installation of LE11 config.txt will contain the instructions how to enable composite video:

###############################################################################
# Use distroconfig-composite.txt instead of distroconfig.txt to enable
# composite video output.
# The composite video mode needs to be configured in cmdline.txt:
# For PAL add: video=Composite-1:720x576@50ie
# For NTSC add: video=Composite-1:720x480@60ie
################################################################################
include distroconfig.txt
#include distroconfig-composite.txt

so long,

Hias

Quote from Mario77

Looks like paths to

Code

/sys/class/leds/

changed to:

Code

/sys/devices/platform/leds/leds/

from this version...is that for a reason?

also led0 is now ACT and led1 PWR

RPi kernel finally switched to using the meaningful names ACT/PWR instead of led0/1 which upstream kernel has been using for a while - see https://github.com/raspberrypi/li…dd5811591d6d106

/sys/class/leds/ACT or /sys/class/leds/PWR are still the canonical paths to configure the LEDs, don't worry about the symlinks to /sys/devices/platform, they are automatically filled in by sysfs to point to the actual device node (i.e. it's purely linux kernel internal stuff)

so long,

Hias

Just use screen from the system tools addon. eg

screen /dev/ttyUSB0 115200

so long,

Hias

No worries, we are preparing for a LE11.0.1 release soon so we have only been adding critical updates the last week - when LE11.0.1 is out more updates will follow and thus new nightlies will be built (we build new nightlies only when changes are added).

so long,

Hias