- g_r_e_g_o_r
- Posts: 2
- Joined: Mon Dec 09, 2024 8:23 pm
Re: STICKY: PINN - An enhanced version of NOOBS.
Thanks for your reply and time taken, I wanted this image because it supports ATARI XL/XE and it contains a lot of different retro games. I've read those instructions and I tried doing it but with no success.procount wrote: ↑Mon Dec 16, 2024 8:02 pmIs there any reason you prefer this image over the more popular Retropie/Recalbox/LibreELEC emulators? Some or all of which support the Atari, plus many other emulators.
This looks a little niche, so I won't be converting it (I have other more important OSes to convert/update when I have the time ;) )
If you want to convert it yourself, please look at https://github.com/procount/pinn/blob/m ... os-version and https://github.com/procount/pinn/wiki/H ... using-PINN. These are just general guidelines and may need adapting if the image is a little out of the ordinary. Each OS needs converting on its own merit, which may require additional skills.
You could always use your Raspberry Pi with Raspberry PI OS installed on it as a Linux computer to do the conversion.
I would like to ask for help with conversion (additional config files) someone who has skills and time needed to make it work. I am even willing to pay or compensate it in some other ways.
Thanks in advance for help.
Re: STICKY: PINN - An enhanced version of NOOBS.
@procount
Konsta released Android TV OS 15 (LineageOS 22 Android TV).
https://konstakang.com/devices/rpi5/LineageOS22-ATV/
When you get some time, if could please add it to PINN
Thanks.
Konsta released Android TV OS 15 (LineageOS 22 Android TV).
https://konstakang.com/devices/rpi5/LineageOS22-ATV/
When you get some time, if could please add it to PINN
Thanks.
Re: STICKY: PINN - An enhanced version of NOOBS.
I've just replaced my rpi4 8gb with the new rpi5 16gb.
PINN works but I've an strange problem: PINN boot is quick as always but then it takes about a minute to start the boot process of the installed OS from PINN.
The curious thing is that it takes about a minute no matter what you do in PINN. Eg:
- Booting PINN and leaving the default OS auto boot makes PINN seems to be hanged during a minute until it suddenly start the OS.
- Booting PINN and enter in it, doing anything inside for 30 seconds and then select Booting the OS make PINN seems to be hanged during about 30 seconds until it suddenly start the OS.
- If you stay in PINN more than a minute the OS is started immediately.
So it just take about a minute... I guess there is some kind of timeout involved but I don't know how to check what.
Raspberry Pi involved is "Raspberry Pi 5 Model B Rev 1.1" with latest bootloader dated January 8.
Another thing, not very important, is that PINN doesn't not show the installed RAM: for my old Raspberry Pi 4 it show 8GB in the right lower corner but it shows nothing for the 16GB one.
PINN version is the latest available: 3.9.4
PINN works but I've an strange problem: PINN boot is quick as always but then it takes about a minute to start the boot process of the installed OS from PINN.
The curious thing is that it takes about a minute no matter what you do in PINN. Eg:
- Booting PINN and leaving the default OS auto boot makes PINN seems to be hanged during a minute until it suddenly start the OS.
- Booting PINN and enter in it, doing anything inside for 30 seconds and then select Booting the OS make PINN seems to be hanged during about 30 seconds until it suddenly start the OS.
- If you stay in PINN more than a minute the OS is started immediately.
So it just take about a minute... I guess there is some kind of timeout involved but I don't know how to check what.
Raspberry Pi involved is "Raspberry Pi 5 Model B Rev 1.1" with latest bootloader dated January 8.
Another thing, not very important, is that PINN doesn't not show the installed RAM: for my old Raspberry Pi 4 it show 8GB in the right lower corner but it shows nothing for the 16GB one.
PINN version is the latest available: 3.9.4
Re: STICKY: PINN - An enhanced version of NOOBS.
Not sure what is causing the 1 min delay, but I will investigate it. Thanks for reporting.
PINN needs updating for the 16GB memory identification as v3.9.4 predates the 16GB model.
PINN needs updating for the 16GB memory identification as v3.9.4 predates the 16GB model.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
Just discovered that PINN version 3.9.4 is available and updated all files on my Pi 3 B Plus PINN RECOVERY FAT16 partition. Unfortunately PINN doesn't initialize with this version. No message to press SHIFT is shown on boot and first OS on SD ist booted instead. config.txt is untouched, cmdline.txt has runinstaller removed and vncshare added, but also tried without vncshare to be sure.
Addiitional test: Used 3.9.4 img file copied it to PINN RECOVERY partition with dd if=pinn-lite.img skip=4 of=/dev/mmcblk0p1 bs=1M (skip=4 is neccessary to skip the partition table and free space in the img). Did successful fsck and mounted the new RECOVERY to remove runinstaller from cmdline.txt. Same result. Looks like support for the Pi 3 B Plus is broken with 3.9.4.
Can you please take a look at it? Many thanks in advance.
Addiitional test: Used 3.9.4 img file copied it to PINN RECOVERY partition with dd if=pinn-lite.img skip=4 of=/dev/mmcblk0p1 bs=1M (skip=4 is neccessary to skip the partition table and free space in the img). Did successful fsck and mounted the new RECOVERY to remove runinstaller from cmdline.txt. Same result. Looks like support for the Pi 3 B Plus is broken with 3.9.4.
Can you please take a look at it? Many thanks in advance.
Re: STICKY: PINN - An enhanced version of NOOBS.
3.9.4 is not officially released yet. I suggest sticking to 3.9.3 for now.
Edit: Check if you have an autoboot.txt file on PINN's recovery partition, and delete it if you do.
Edit: Check if you have an autoboot.txt file on PINN's recovery partition, and delete it if you do.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
Ok, Thanks! Will stick with 3.9.3 for now.
Double checked, I have no autoboot.txt file.
- elim_garak
- Posts: 3
- Joined: Wed Oct 28, 2020 1:29 am
Re: STICKY: PINN - An enhanced version of NOOBS.
First of all thanks for PINN it's a fantastic sofware.
Unfortunately I've encountered a problem.
I was using 3.8 (as shown on the window title bar) and booted to the PINN menu. It asked me to update which I said yes. It then rebooted. I'm not sure if it was a crash or a scheduled reboot because I wasn't asked or warned.
On reboot I'm greeted with a kernel panic:
Searching the web mentioned things like ubuntu. Well I didn't install any new OS nor do I have ubuntu. On the pi4 I have Raspbian and LibreElec and Retropie.
Some posts also mentioned power glitches or corruption. The thing is I've been using this pi4 for several years and has worked fine. So it seems unlikely.
Mounting the pi's SD card on my linux machine I can see that based on the timestamp the majority of the files in /dev/sdc1 have been updated. Files not changed include:
SD card layout:
The contents of /dev/sdc1/cmdline.txt are:
The contents of /dev/sdc6/cmdline.txt are:
The contents of /dev/sdc8/cmdline.txt are:
The contents of /dev/sdc10/cmdline.txt are:
Running fsck hints that something went wrong:
All the other partitions were fine.
Any way to fix this without losing my data?
Makes me wonder if this is just a kernel boot config that is pointing to the wrong partition.
Thanks
Unfortunately I've encountered a problem.
I was using 3.8 (as shown on the window title bar) and booted to the PINN menu. It asked me to update which I said yes. It then rebooted. I'm not sure if it was a crash or a scheduled reboot because I wasn't asked or warned.
On reboot I'm greeted with a kernel panic:
Code: Select all
Kernel panic - not syncing: VFS: unable to mount root fs on "unknown block(1,0)"Some posts also mentioned power glitches or corruption. The thing is I've been using this pi4 for several years and has worked fine. So it seems unlikely.
Mounting the pi's SD card on my linux machine I can see that based on the timestamp the majority of the files in /dev/sdc1 have been updated. Files not changed include:
Code: Select all
defaults
os
overlays
changefirmware
fixup4rc.dat
fixup_rc.dat
overrides.json
pieeprom.sig
pieeprom.upd
recover4.elf
RECOVERY.000
recovery7.img
recovery7l.img
recovery.cmdline
recovery.cmdline.new
recovery.elf
recovery.img
recovery.rfs
riscos-boot.bin
wallpaper.jpg
Code: Select all
sdc 29.8G
├─sdc1 RECOVERY vfat 63M
├─sdc2 1K
├─sdc5 SETTINGS ext4 32M
├─sdc6 boot vfat 256M
├─sdc7 retropie ext4 8.1G
├─sdc8 boot0 vfat 256M
├─sdc9 root ext4 14.6G
├─sdc10 System vfat 512M
└─sdc11 Storage ext4 6.1G
Code: Select all
runinstaller quiet ramdisk_size=65536 root=/dev/ram0 init=/init vt.cur_default=1 elevator=deadline repo_list=http://raw.githubusercontent.com/procount/pinn-os/master/os/repo_list.json loglevel=2 sdhci.debug_quirks2=4
Code: Select all
console=serial0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet loglevel=3 consoleblank=0 plymouth.enable=0 quietCode: Select all
console=serial0,115200 console=tty1 root=/dev/mmcblk0p9 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consolesCode: Select all
boot=LABEL=System disk=LABEL=Storage quietCode: Select all
# fsck.vfat -n /dev/sdc1
fsck.fat 4.2 (2021年01月31日)
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit.
Leaving filesystem unchanged.
# fsck.vfat -n /dev/sdc8
fsck.fat 4.2 (2021年01月31日)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
Not automatically fixing this.
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit.
Leaving filesystem unchanged.
Any way to fix this without losing my data?
Makes me wonder if this is just a kernel boot config that is pointing to the wrong partition.
Thanks
Re: STICKY: PINN - An enhanced version of NOOBS.
It looks to me like the PINN upgrade failed. But don't worry, it should be recoverable.
(If any data is critical, please backup your drive first in case something bad happens or you make a mistake).
The latest versions of PINN have additional kernels for the Pi5, so they require a larger recovery partition as it only just fits in 64MB. Maybe your drive just doesn't quite have enough space on it, although PINN tries to test whether this is the case.
I suggest a manual upgrade to 3.8.8, which is the last version before space became critical.
Please download https://sourceforge.net/projects/pinn/files/archive/pinn-388.zip/download.
Delete all the PINN files and folders in PINN's recovery partition ( on /dev/sdc1 from your previous post).
Unzip pinn-388.zip to this recovery partition.
Edit recovery.cmdline and delete the `runinstaller` option.
Finally, boot PINN and it should now be ok.
If that still fails, repeat using https://sourceforge.net/projects/pinn/files/archive/pinn-387f.zip/download.
Since these are not the latest versions, you will still be asked if you want to upgrade again, but I suggest you click ignore to avoid hitting the same problem again.
If you want to upgrade PINN in the future, I suggest you use a larger recovery partition.
By using the `runinstaller` option it will expand the recovery partition, but at the expense of wiping out all your installed OSes, so make sure you have backed them up first so you can reinstall them.
A safer way would be to install the latest PINN to a new drive and then reinstall your OSes from a backup.
(If you clicked ignore to the upgrade, you would have to check for a manual update - see https://github.com/procount/pinn/blob/m ... idual-oses)
(If any data is critical, please backup your drive first in case something bad happens or you make a mistake).
The latest versions of PINN have additional kernels for the Pi5, so they require a larger recovery partition as it only just fits in 64MB. Maybe your drive just doesn't quite have enough space on it, although PINN tries to test whether this is the case.
I suggest a manual upgrade to 3.8.8, which is the last version before space became critical.
Please download https://sourceforge.net/projects/pinn/files/archive/pinn-388.zip/download.
Delete all the PINN files and folders in PINN's recovery partition ( on /dev/sdc1 from your previous post).
Unzip pinn-388.zip to this recovery partition.
Edit recovery.cmdline and delete the `runinstaller` option.
Finally, boot PINN and it should now be ok.
If that still fails, repeat using https://sourceforge.net/projects/pinn/files/archive/pinn-387f.zip/download.
Since these are not the latest versions, you will still be asked if you want to upgrade again, but I suggest you click ignore to avoid hitting the same problem again.
If you want to upgrade PINN in the future, I suggest you use a larger recovery partition.
By using the `runinstaller` option it will expand the recovery partition, but at the expense of wiping out all your installed OSes, so make sure you have backed them up first so you can reinstall them.
A safer way would be to install the latest PINN to a new drive and then reinstall your OSes from a backup.
(If you clicked ignore to the upgrade, you would have to check for a manual update - see https://github.com/procount/pinn/blob/m ... idual-oses)
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
- elim_garak
- Posts: 3
- Joined: Wed Oct 28, 2020 1:29 am
Re: STICKY: PINN - An enhanced version of NOOBS.
Thank you very much for the quick and detailed answer. That fixed it.procount wrote: ↑Wed Jan 22, 2025 3:11 pmPlease download https://sourceforge.net/projects/pinn/files/archive/pinn-388.zip/download.
Delete all the PINN files and folders in PINN's recovery partition ( on /dev/sdc1 from your previous post).
Unzip pinn-388.zip to this recovery partition.
Edit recovery.cmdline and delete the `runinstaller` option.
I ended unzipping `pinn-392.zip` and it worked fine. It left 374K bytes free on that partition.
I'm guessing the problem was with the "files that weren't updated" that I listed on previous post. The "recovery*" and others. Some leftovers(?) that were taking disk space.
FWIW:
On boot it asked me to update to 3.9.3 which I did. The process seems to to work fine. I then manually reboot but can see that it didn't finish the update because it's still 3.9.2 and asks me to update again.
I suspect this time it really doesn't have any disk space any more. pinn-393.zip is 500K more than pinn-392.zip but I only had 374K free.
TLDR: anyone with the first partition (eg: /dev/sdc1) at 64MB then manually unzipping 3.9.2 and deleting the `runinstaller` option should work fine
A few other questions:
1) would it be possible to repartition (for exampling using gparted on my desktop) to resize things from my current layout:
I would reduce sdc6 to get some free space and then adjust sdc1 and sdc5├─sdc1 RECOVERY vfat 63M
├─sdc2 1K
├─sdc5 SETTINGS ext4 32M
├─sdc6 boot vfat 256M
Would the partition numbers and UUIDs need to remain the same?
2) what is that color gradient before the PINN background shows up? Is that just a test for video display or is it possible to SSH during that stage?
Re: STICKY: PINN - An enhanced version of NOOBS.
1. In principal, yes you could resize the partitions, however....
a) Using parted/Gparted tends to change the Disk Identifier, which affects the partuuids. As long as you remember what it was before and restore it afterwards (with e.g. fdisk), then this can be worked around.
b) Reducing the boot partition sdc6 may cause future problems upgrading the OS, as it often needs some spare space to update (depending on the OS). It is better to resize a rootfs where there is usually more spare space.
c) After resizing and shuffling the logical partitions, you also need to resize the extended partition SDC2 which covers all the logical partitions, before resizing SDC1
d) Always do a backup before attempting any re-partitioning to guard against data loss.
2, The colour gradient square is part of the firmware as a test pattern. The red corner changes to magenta on the secondary display. I think it can be turned off with a config.txt setting. SSH is enabled later once PINN starts.
a) Using parted/Gparted tends to change the Disk Identifier, which affects the partuuids. As long as you remember what it was before and restore it afterwards (with e.g. fdisk), then this can be worked around.
b) Reducing the boot partition sdc6 may cause future problems upgrading the OS, as it often needs some spare space to update (depending on the OS). It is better to resize a rootfs where there is usually more spare space.
c) After resizing and shuffling the logical partitions, you also need to resize the extended partition SDC2 which covers all the logical partitions, before resizing SDC1
d) Always do a backup before attempting any re-partitioning to guard against data loss.
2, The colour gradient square is part of the firmware as a test pattern. The red corner changes to magenta on the secondary display. I think it can be turned off with a config.txt setting. SSH is enabled later once PINN starts.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
I have a few questions
1. Does it support Raspberry Pi 4?
2. If I have a preexisting OS on there, do I download pin, or is there a risk? Is there a way to bypass it?
1. Does it support Raspberry Pi 4?
2. If I have a preexisting OS on there, do I download pin, or is there a risk? Is there a way to bypass it?
Re: STICKY: PINN - An enhanced version of NOOBS.
1. Yes
2. PINN needs to be installed to an empty SD card. If you have something else on there beforehand, it will be wiped.
I would buy a new SD card and install PINN to that. Use PINN to install the OSes you want and copy any data from your old SD card using a USD SD card reader.
Bypass what - PINN? Yes you can bypass to boot directly into the same OS each time if you want, but PINN is also a boot OS selector that allows you to choose which OS you want to boot. If it is bypassed, then you lose this facility.Is there a way to bypass it?
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
- rickwookie
- Posts: 24
- Joined: Sat Mar 03, 2012 11:09 am
Re: STICKY: PINN - An enhanced version of NOOBS.
I come to this thread every few months to see if there's any update to PINN to support either CEC or Joystick input on the Pi5. Sadly, the position seems to be the same as a year ago.
Are either of these features being actively looked into, and if so, what is the sticking point?
Are either of these features being actively looked into, and if so, what is the sticking point?
Re: STICKY: PINN - An enhanced version of NOOBS.
Apologies that it is taking so long. My main concern has been to fix the occasional deadlocks that occur on the PI5 when the network connects, as this instability really annoys me. Sadly the cause is quite elusive, and confusing since the same code runs fine on all models prior to the PI5. I am currently making progress with another avenue of attack, but I think it is important to get the Pi5 version stable first before adding more features which are specific to the Pi5. PINN relied heavily on some features of the previous models, but a lot has changed with the Pi5 requiring many changes (64-bit kernel, DSI, KMS, CEC, D0 stepping etc.). I am just as frustrated since I have more exciting features I want to add but can't get round to. Ar the end of the day, this is just a spare-time hobby as I have a full-time job and family to look after, so please bear with me. Rest assured, it will be looked at, eventually.... ;)rickwookie wrote: ↑Mon Feb 10, 2025 6:18 pmI come to this thread every few months to see if there's any update to PINN to support either CEC or Joystick input on the Pi5. Sadly, the position seems to be the same as a year ago.
Are either of these features being actively looked into, and if so, what is the sticking point?
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
Updated version of Leepspvideo KDE plasma. Please add to PINN
https://drive.google.com/file/d/1e-g97u ... sp=sharing
Custom Raspberry Pi OS. KDE part 5. ##Download now##
https://youtu.be/27aODRutCyQ
https://drive.google.com/file/d/1e-g97u ... sp=sharing
Custom Raspberry Pi OS. KDE part 5. ##Download now##
https://youtu.be/27aODRutCyQ
Re: STICKY: PINN - An enhanced version of NOOBS.
Should this replace the previous version, or is it in addition?
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
It’s all up to date. This is fine to be the only version
Re: STICKY: PINN - An enhanced version of NOOBS.
Gentle reminder, whenever you can.sim_tcr wrote: ↑Fri Jan 03, 2025 4:56 pm@procount
Konsta released Android TV OS 15 (LineageOS 22 Android TV).
https://konstakang.com/devices/rpi5/LineageOS22-ATV/
When you get some time, if could please add it to PINN
Thanks.
- georgen121
- Posts: 1
- Joined: Mon Feb 24, 2025 9:08 am
Re: STICKY: PINN - An enhanced version of NOOBS.
Great work on continuously improving PINN! The added features and fixes make it even more versatile. Thanks for keeping it updated
Re: STICKY: PINN - An enhanced version of NOOBS.
Lineage22-rpi5, Lineage22-rpi5-atv and AOSP15-rpi5 released.sim_tcr wrote: ↑Sun Feb 23, 2025 4:40 amGentle reminder, whenever you can.sim_tcr wrote: ↑Fri Jan 03, 2025 4:56 pm@procount
Konsta released Android TV OS 15 (LineageOS 22 Android TV).
https://konstakang.com/devices/rpi5/LineageOS22-ATV/
When you get some time, if could please add it to PINN
Thanks.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
Thank you @procount.procount wrote: ↑Sat Mar 01, 2025 9:31 pmLineage22-rpi5, Lineage22-rpi5-atv and AOSP15-rpi5 released.sim_tcr wrote: ↑Sun Feb 23, 2025 4:40 amGentle reminder, whenever you can.sim_tcr wrote: ↑Fri Jan 03, 2025 4:56 pm@procount
Konsta released Android TV OS 15 (LineageOS 22 Android TV).
https://konstakang.com/devices/rpi5/LineageOS22-ATV/
When you get some time, if could please add it to PINN
Thanks.
Tested and all works.
Re: STICKY: PINN - An enhanced version of NOOBS.
Lineage22-rpi4, Lineage22-atv-rpi4 and AOSP15-rpi4 also added.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574
Re: STICKY: PINN - An enhanced version of NOOBS.
Thanks for the update.
Raspberry Pi OS (64-bit) with desktop and recommended software
Raspberry Pi 5 Model B 4GB at stock speed (never overclock)
Never overclock your Pi.
Encourage optimization instead.
Raspberry Pi 5 Model B 4GB at stock speed (never overclock)
Never overclock your Pi.
Encourage optimization instead.
- blackestflag
- Posts: 2
- Joined: Fri Mar 07, 2025 3:27 pm
Re: STICKY: PINN - An enhanced version of NOOBS.
Hey everyone, just wanted to say Thank You for this great tool
I am however running into some issues as of late
On a pi4b - 4gb - Rev 1.5, using PINN 3.9.4, I am getting Error 404 when trying to install Batocera on 128gb SD card
From debug.txt
Same thing happens when I try to use the Download feature to download it onto USB drive
I'm assuming it may have something to do with the os_list.json file ?
Any direction would be greatly appreciated.
The end goal is to have lineage and Batocera dual boot, via SD card
I am however running into some issues as of late
On a pi4b - 4gb - Rev 1.5, using PINN 3.9.4, I am getting Error 404 when trying to install Batocera on 128gb SD card
From debug.txt
Code: Select all
Processing OS: "batocera_RPi4"
"/sbin/findfs LABEL=BATOCERA"
"/sbin/findfs: unable to resolve 'LABEL=BATOCERA'
"
Executing: "/sbin/mkfs.fat -n BATOCERA /dev/mmcblk0p6"
Executing: "sh -o pipefail -c "wget --retry-connrefused --read-timeout=120 --tries=inf --no-verbose -O- https://updates.batocera.org/rpi464/stable/last/boot.tar.xz | tee /tmp/fifo | xz -dcT 0 | bsdtar -xf - -C /mnt2 --no-same-owner | sha512sum /tmp/fifo > /tmp/sha1.out.txt""
"https://mirrors.o2switch.fr/batocera/rpi464/stable/last/boot.tar.xz:
2025年03月07日 15:13:01 ERROR 404: Not Found.
xz: (stdin): File format not recognized
"
I'm assuming it may have something to do with the os_list.json file ?
Any direction would be greatly appreciated.
The end goal is to have lineage and Batocera dual boot, via SD card
Last edited by blackestflag on Fri Mar 07, 2025 3:45 pm, edited 1 time in total.
Return to "General discussion"
Jump to
- Community
- General discussion
- Announcements
- Other languages
- Deutsch
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Polski
- Português
- Русский
- Türkçe
- User groups and events
- Raspberry Pi Official Magazine
- Using the Raspberry Pi
- Beginners
- Troubleshooting
- Advanced users
- Assistive technology and accessibility
- Education
- Picademy
- Teaching and learning resources
- Staffroom, classroom and projects
- Astro Pi
- Mathematica
- High Altitude Balloon
- Weather station
- Programming
- C/C++
- Java
- Python
- Scratch
- Other programming languages
- Windows 10 for IoT
- Wolfram Language
- Bare metal, Assembly language
- Graphics programming
- OpenGLES
- OpenVG
- OpenMAX
- General programming discussion
- Projects
- Networking and servers
- Automation, sensing and robotics
- Graphics, sound and multimedia
- Other projects
- Media centres
- Gaming
- AIY Projects
- Hardware and peripherals
- Camera board
- Compute Module
- Official Display
- HATs and other add-ons
- Device Tree
- Interfacing (DSI, CSI, I2C, etc.)
- Keyboard computers (400, 500, 500+)
- Raspberry Pi Pico
- General
- SDK
- MicroPython
- Other RP2040 boards
- Zephyr
- Rust
- AI Accelerator
- AI Camera - IMX500
- Hailo
- Software
- Raspberry Pi OS
- Raspberry Pi Connect
- Raspberry Pi Desktop for PC and Mac
- Beta testing
- Other
- Android
- Debian
- FreeBSD
- Gentoo
- Linux Kernel
- NetBSD
- openSUSE
- Plan 9
- Puppy
- Arch
- Pidora / Fedora
- RISCOS
- Ubuntu
- Ye Olde Pi Shoppe
- For sale
- Wanted
- Off topic
- Off topic discussion