doc:appunti:hardware:raspberrypi_nas_kodi
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:appunti:hardware:raspberrypi_nas_kodi [2022/01/31 23:34] – [Raspberry Pi OS Config] niccolo | doc:appunti:hardware:raspberrypi_nas_kodi [2022/08/10 09:49] – [Swap file] niccolo | ||
---|---|---|---|
Line 2: | Line 2: | ||
This page is about configuring **[[wp> | This page is about configuring **[[wp> | ||
+ | |||
+ | ===== RaspiOS 11 Bullseye ===== | ||
+ | |||
+ | Default installation on the **Raspberry Pi 4** of the Raspberry Pi OS based on **Debian 11 Bullseye** is rather satisfactory in terms of optimization; | ||
+ | |||
+ | If your system has undergone some software upgrades, it is recommended to check the content of **config.txt** for obsolete or wrong settings. This is the default content after a vanilla installation: | ||
+ | |||
+ | < | ||
+ | dtparam=audio=on | ||
+ | camera_auto_detect=1 | ||
+ | display_auto_detect=1 | ||
+ | dtoverlay=vc4-kms-v3d | ||
+ | max_framebuffers=2 | ||
+ | disable_overscan=1 | ||
+ | |||
+ | [cm4] | ||
+ | otg_mode=1 | ||
+ | |||
+ | [pi4] | ||
+ | arm_boost=1 | ||
+ | </ | ||
+ | |||
+ | The **vc4-kms-v3d** overlay is particularly important. The GPU of the **Pi 4** is a **VideoCore VI** capable of **OpenGL ES 3.2**, this requires a specific driver, different from the one required e.g. by the Raspberry Pi 3, which has a VideoCore IV GPU capable only of OpenGL ES 2.0. The codename of the driver is **VC4** for the old GPU and **V3D** for the newer one. Loading the **vc4-kms-v3d** overlay, the device tree sorts out which exact node is enabled, be it VC4 or VC6. They both get aliased to " | ||
+ | |||
+ | The **legacy KMS driver** developed for the Raspberry up to version 3 does not work with the newer Pi 4, because video acceleration support was removed from the hardware (the Pi4 is powerfull enough to do 3D video and OpenGL in software). Operating system before Debian 10 Buster required the now obsolete **vc4-fkms-v3d** overlay on the **Raspberry Pi 4**, i.e. the //Fake Kernel Mode Setting// (a software driver based on the now obsoleted DispmanX Broadcom API), because at that time it was the best option. Now we should go with the Linux standard APIs **vc4-kms-v3d**. | ||
+ | |||
+ | Another usefull option is **arm_boost=1**, | ||
+ | |||
+ | Check for other unnecessary configuration options in **[[https:// | ||
+ | |||
+ | ==== Swap file ==== | ||
+ | |||
+ | The default RaspiOS installation will enable a swap file to support system memory. Using the **free** command you can see that a 100 Mb swap file was enabled: | ||
+ | |||
+ | < | ||
+ | | ||
+ | Mem: | ||
+ | Swap: | ||
+ | </ | ||
+ | |||
+ | The swap file is **/ | ||
+ | |||
+ | < | ||
+ | systemctl stop dphys-swapfile.service | ||
+ | systemctl disable dphys-swapfile.service | ||
+ | </ | ||
+ | |||
+ | ==== Web References ==== | ||
+ | |||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | |||
+ | ===== RaspiOS 10 Buster ===== | ||
I installed my Raspberry Pi 4 NAS/ | I installed my Raspberry Pi 4 NAS/ | ||
- | ===== Raspberry Pi OS Config | + | |
+ | ==== Raspberry Pi OS Config ==== | ||
Using the **raspi-config** tool, we configured the following: | Using the **raspi-config** tool, we configured the following: | ||
Line 123: | Line 180: | ||
===== Video codecs and jerky videos ===== | ===== Video codecs and jerky videos ===== | ||
- | To make a long story short: I had to **downgrade the kernel** from **5.10** (as shipped with RaspiOS 2021-01-11 Buster) to the old **4.19**, otherwise there is a bug hitting Kodi and MPEG-4 video files. Here t is the long story I had to learn... | + | To make a long story short: I had to **downgrade the kernel** from **5.10** (as shipped with RaspiOS 2021-01-11 Buster) to the old **4.19**, otherwise there is a bug hitting Kodi and MPEG-4 video files. Here it is the long story I had to learn... |
Coding and decoding of video streams is a very complex task; software used for that purpose (known as //codecs//) can be embedded into the hardware (generally into the GPU) or can be installed as a software libraries. Unfortunately many video formats (codec algorithmas) are not open and there are not free implementations of them, so you have to buy a license to install the library or to unlock the function inside the hardware. | Coding and decoding of video streams is a very complex task; software used for that purpose (known as //codecs//) can be embedded into the hardware (generally into the GPU) or can be installed as a software libraries. Unfortunately many video formats (codec algorithmas) are not open and there are not free implementations of them, so you have to buy a license to install the library or to unlock the function inside the hardware. |
doc/appunti/hardware/raspberrypi_nas_kodi.txt · Last modified: 2023/06/10 17:24 by niccolo