Posts by HiassofT

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

Yes, that's a known issue in kodi with no fix yet so far.

see also https://github.com/xbmc/xbmc/pull/18741

so long,

Hias

Your RPi is running out of memory - which is a well known problem. Only devices with at least 1GB of RAM are supported in LibreELEC 10 and newer.

so long,

Hias

Meestor_X thanks for the new log, this looks fine now.

The next step will be that you create a bug report on the RPi linux repo here https://github.com/raspberrypi/linux/issues

The key point to creating a useful bug report is to provide as much as useful information as possible upfront so the devs can unterstand, reproduce, analyze and then fix the issue.

RPi devs use a standard issue template that you have to fill out and provide the necessary info. Best have a look at it first, then take your time to collect the info and fill it out and submit it once you have all the info.

Check through the items I listed here RE: LibreElec v11 on RPI3 won't start and include all this info in the bug report.

I'd suggest using a meaningful title like "RPi3 boot regression with Sandisk Extreme Endurance 256GB since kernel 5.15".

Start with mentioning boot issues with current RPiOS bullseye image and post the error message you got on screen and/or attach a picture of it.

Also mention that you get the same issue with LibreELEC and kernel 6.1 and attach the dmesg you captured - that should be very helpful to devs.

Run "raspinfo" on the working RPiOS legacy / Buster image to collect the info the devs usually want.

Mention the results of rpi-update to latest 5.10 and first 5.15 kernels/firmwares, as mentioned in my list.

Also feel free to post a link to this forum thread as a reference.

Very likely RPi devs will then come back to you with more questions or will ask you to test some kernels with rpi-update - be patient, depending on their current workload this could take anything from a few minutes to months.

If you want to proofread or check your bug report before you submit it on the RPi repo then just post a draft of it here in this thread and I'll have a look and comment on it.

so long,

Hias

The power supply is only half of the important bits, the other half is cables.

Lots of power supplies don't maintain to provide stable 5V under load (and you might not see the dips with a multimeter, all computers nowadays can generate very short current spikes when the CPUs have lots of stuff to do and you'll see the voltage drops only with a scope - been checking that 10+ years ago on original RPi).

Also lots of USB cables are poorly made, have thin 5V and GND strains, thus a high resistance and drop A LOT of (milli-)volts under high currents. Finding proper cables isn't easy (most of them are just crap).

So, to summarize, if you don't want to pay the 7 bucks (or whatever they cost nowadsays) for an official RPi power supply you are going to have to endure a lot of pain and spend a lot more money on chargers/power supplies and cables until you find a working combination.

Plus, users with power supply issues who don't understand that simple fact that a computer won't work without proper powering (would your car run properly if you filled in the wrong fuel?) have cost us developers (and RPi engineers) enormous amounts of time that we could have better spent otherwise.

so long,

Hias

RPis don't "always" complain about low power, only when the power is too low - which is about the worst thing you can do to an RPi as it is known to cause all sorts of problems.

I have about two dozens of RPis here, starting from the very first RPi to RPi4 and RPI400 and none of them reports power problems when powered by the official RPi power supplies.

I've had lots of problems though with phone chargers, USB hubs and 3rd-party power supplies in the very early days before RPi started shipping their official power supply. Since then I retired all those crappy devices and switched to official power supplies and never had any issues again.

I suggest you do the same thing.

so long,

Hias

You are still having power issues

<2>[    5.388985] hwmon hwmon0: Undervoltage detected!
<6>[    5.462544] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
<5>[    5.471394] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
<3>[   13.708922] mmc0: timeout waiting for hardware interrupt.

so long,

Hias

The log is complete now, however the log shows you are having power problem - and the mmc issues start right after the first undervoltage message

[    5.395065] hwmon hwmon0: Undervoltage detected!
...
[   13.714953] mmc0: timeout waiting for hardware interrupt

As I wrote above you need to fix the power issues first, no need to dig any further before that as the issues are very likely correlated.

so long,

Hias

Try with librespot uninstalled - the addon seems to block kodi from using the HDMI audio device.

so long,

Hias

Adding log_buf_len=4M to cmdline.txt didn't seem to have worked, the log is still cut off. Make sure everything is on the same line and if you edited the file on Windows use Notepad++ or some other editor that can cope with unix line endings - windows editor adding windows line endings usually cause havoc.

However, I spotted a more serious issue in your first dmesg, your RPi is suffering from power problems. You need to fix this first, use the official RPi power supply, power problems are usually causing the exact same issues you are experiencing.

so long,

Hias