It looks like dirty region visualization is being enabled.
Posts by milhouse
-
-
The memory fix and USB support is now in Raspberry Pi firmware branch=master (has been for a week or two), so use that as per lrusaks instructions. Or upgrade to the LE 8 Beta.
-
Shoog: The 119MB issue has been fixed for a while now, and shouldn't be an issue in my Kodi 18 test builds or the latest LibreELEC 8 beta build (7.95.1), both of which should boot from USB with the full complement of RAM. Which version of LibreELEC are you testing that has this RAM issue?
-
My CM3s turned up today, but they are not CM3s, they are LITEs <big sigh>I guess the testing is delayed somewhat.... unless booting from HDD is easy to do....
RogerIs that what you ordered, or a shipping mistake?
-
-
-
I don't think the "Failed to create static device nodes in /dev" issue has ever been fixed. It's something we're aware of but it's harmless (just a cosmetic issue at startup) and currently a low priority issue.
-
-
bOZU is a single patch that contains three *hunks*.
You certainly need the first hunk. I don't know if you need the second and third hunks, Ubuntu seem to think so (and this patch does apply on top of 304.134 despite being originally based on 304.132).
If it doesn't build with all three hunks then drop the second and third hunks (delete from the second "diff" onwards).
-
Looks like 304.134 requires the equivalent of the 4.9 patch you removed in your first post.
You can try this patch: bOZU, which is from Ubuntu: 304.132-0ubuntu3 : nvidia-graphics-drivers-304 package : Ubuntu
Copy it into the xf86-video-nvidia-legacy/patches directory.
-
Click on the link, they're LibreELEC test builds with Kodi 18a1. You can upgrade by dropping the tar file into the samba Upgrade folder, and you can downgrade back to 7.90.010 using the same method.
-
Do you have this issue with the latest Kodi 18 test build: LibreELEC Testbuilds for x86_64 (Kodi 18.0)
-
Always use master.
-
Please don't post logs to the forum - use a pastebin site and post the link.
7.90.009 is based on the 4.8.12 kernel while 7.90.010 is based on the 4.9.0 kernel - make sure your patch is compatible with the kernel you are building.
-
-
Do you have "Sync playback to display" enabled? If so, turn it off and passthrough should then work (the help text for the Sync option explains that passthrough will be disabled).
-
My kodi 18 test builds include branch=next firmware. Or use the latest official 7.90.xxx release, then update the firmware from branch=next.
As for your cmdline.txt, the following might work (untested, I've only tested network booting):
Note that it's better to use uuids to identify your USB partitions to avoid confusion with any other USB based storage you may have connected, so once you've booted the Pi use blkid to list your uuids, and then change cmdline.txt.
The following is just an example with a system booted from SD card (although it's really not necessary to use UUIDs for SD cards):
Coderpi22:~ # blkid /dev/mmcblk0: PTUUID="bb25af57" PTTYPE="dos" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="System" UUID="9AD8-C43A" TYPE="vfat" PARTUUID="bb25af57-01" /dev/mmcblk0p2: LABEL="Storage" UUID="16d88253-502e-4c3c-8404-1c24bade0213" TYPE="ext4" PARTUUID="bb25af57-02" [code] and then cmdline.txt would become: [code] boot=UUID=9AD8-C43A disk=UUID=16d88253-502e-4c3c-8404-1c24bade0213 quiet ssh
-
Probably some broken or incompatible add-on is causing the new Kodi to crash - a crash log would reveal all. If ssh hasn't been enabled, add "ssh" to the end of the line in cmdline.txt (it's in the root of the SD card), boot the RPi, then login using ssh (username: root, password: libreelec) and run:
then post the link.