Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Slackware - ARM This forum is for the discussion of Slackware ARM.


  Search this Thread
Old 03-09-2018, 01:36 AM   #31
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 456

Original Poster
Rep: Reputation: 233Reputation: 233Reputation: 233

I don't know yet if my suggestions from the previous post resolved your "looks kind of washed out" issue regarding the Desktop and Kodi, but I'd like to update this thread with some info about the color depth on the Raspberry Pi boards.

Some years ago, by the time I started using the Raspberry Pi boards, the 16bit color depth (high color ~ 65k) was the default/recommended value and the 24bit color depth (true color ~ 16 million) was broken due to some firmware issues. Using the 32bit color depth was not recommended because of the higher memory usage and the performance impact. A more recent thread where the 32bit color depth is not encouraged by the Raspberry Foundation:
16 bit color depth looks indeed washed out and the 24bit (~ 16 million) is a little over the biological color perception limit of the eyes, which is a little over 10 million. Pushing the 32bit color depth doesn't really make sense for watching media content, 24 bit should suffice.

Meanwhile I got used with the limited 16bit color depth and forgot to check if the 24bit color depth is fixed or still broken. Now that stormtracknole reported his poor image quality, I just considered to check it again and I was successful in enabling this 24bit color depth on a Raspberry Pi Zero, running Slackware ARM 14.2, with the official Raspberry Pi kernel 4.4.50+ (and the firmware that comes with it) and only allocating 128MB for the GPU. I haven't noticed any apparent performance impact and I'm able to play full HD streams even at 50fps without frame drops and not using more than 75% of the GPU RAM.

- these are the /boot/config.txt options I'm using now for Kodi 17.4 on the Pi0:
#disabled the ignore_alpha option as it is only needed for the 32bit color depth
1 members found this post helpful.
Old 03-09-2018, 06:35 AM   #32
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,041

Rep: Reputation: 148Reputation: 148
Yes, I was able to figure out shortly after I made my post. I figured that it had something to do with config.txt. Since this is a raspberry pi 3, I went ahead with using framebuffer_depth=32 and framebuffer_ignore_alpha=1 with no issues. I figure that framebuffer_depth=24 should be at least the default setting. Felt like it was Windows 95 for a while there.
1 members found this post helpful.
Old 03-10-2018, 04:09 AM   #33
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 456

Original Poster
Rep: Reputation: 233Reputation: 233Reputation: 233
There is a FAQ page on Kodi dedicated solely for the Raspberry Pi boards, that was updated recently and contains a lot of very useful information. Since I cannot edit my original guide anymore, I'll use this post to update the thread:

I found these recommended GPU Memory setting really important:
"320M on a Pi2 may be appropriate if using higher resolution imageres/fanartres and also higher colour."

To check the health/load/memory usage (including GPU) on the Raspberry Pi boards while running Kodi (general usage too), the following script is very useful:
chmod +x
./ A
In order to protect the SDCard from some intensive storage operations Kodi is doing, I'd suggest to create a RAM filesystem and use it to store the files Kodi is hammering the Card with. I don't know where Kodi is storing the artwork/fanart, since I'm not using this feature, but I've noticed that the database files in .kodi/userdata/Database are really busy. I took them from there and archived them, leaving only a symlink to the Database folder pointing to a tmpfs drive /attic , where I unpack them on system boot - rc.local and archive them back and store on system down/restart - rc.6
Here's my fstab related entry - just for inspiration:
tmpfs            /attic        tmpfs       nodev,nosuid,noatime,nodiratime,size=100M 0 0


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware ARM Raspberry Pi - armv6 and armv7 - optimized FFMPEG with HW Acceleration abga Slackware - ARM 22 04-22-2018 11:05 AM
Raspberry PI 3 + Slackware 14.2 Arm + Kodi tb404 Linux - Software 16 02-04-2017 11:26 PM
Elementary OS on Raspberry Pi3 (arm processors) ?? Marv_Mark elementary OS 3 12-14-2016 06:04 PM > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 03:36 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration