- UtenteRasp
- Posts: 71
- Joined: Sat Jun 27, 2020 7:35 am
Re: STICKY - How to upgrade a Buster image to Bullseye
I also upgraded to Bullseye and I also encountered the same problem with the wifi. It disconnects at every boot. The only solution is to remove connman?srcshelton wrote: ↑Wed Nov 10, 2021 10:03 amOn upgrade following the instructions in the OP, both of the first two RPis I've tested the process on (both RPI4, one slightly customised but the other almost completely stock/pristine) have rebooted into Bullseye reporting that Bluetooth and Wifi are soft-blocked.
Re-enabling Bluetooth is a one-time click on the icon in the Desktop menu-bar/panel, but by the same method Wifi only gets re-enabled on a per-session basis, and is again disabled on reboot.
I found a solution here: viewtopic.php?t=317986
tl;dr - What worked for me was running:
... but the other suggestion of adding:Code: Select all
sudo apt-get remove --purge connman
... to /boot/cmdline.txt also seems like a reasonable (albeit untested by myself) option.Code: Select all
systemd.restore_state=0 rfkill.default_state=1
Re: STICKY - How to upgrade a Buster image to Bullseye
Hi, according to the command; od -An -tx1 /proc/device-tree/emmc2bus/dma-ranges has the C0 chip. So it should be eligible for the 1800Mhz speed on Bullseye. But after upgrading (no problems encountered) after changing the sources, I still get 1500Mhz. So the question is how can I collect my bonus 300Mhz without reinstalling. My kernel is showing Linux rpi-lite 5.10.63-v8+ #1459 SMP PREEMPT Wed Oct 6 16:42:49 BST 2021 aarch64 GNU/Linux with uname-a and PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye) with cat /etc/os-release.
Kind regards,
Henk
Kind regards,
Henk
Re: STICKY - How to upgrade a Buster image to Bullseye
First post followed exactly, and it worked like a charm on a Raspbian 10 system running Pi-Hole.
Rebooted and everything came up fine upgrading from a freshly updated Raspbian 10(buster) to Raspbian 11(Bullseye). (Be sure your existing Raspbian 10 system is fully up-to-date before upgrading to 11(bullseye)).
I had to adjust some settings back in my, , and config files to fix some of my localized settings. But other than that, everything is back up and running flawlessly, including pi-hole.
I can even sync with a pi-hole instance running gravity-sync on Raspbian 10(Buster) still :D
Rebooted and everything came up fine upgrading from a freshly updated Raspbian 10(buster) to Raspbian 11(Bullseye). (Be sure your existing Raspbian 10 system is fully up-to-date before upgrading to 11(bullseye)).
I had to adjust some settings back in my
Code: Select all
/etc/sudoersCode: Select all
/etc/ssh/sshd_configCode: Select all
/etc/snmp/snmpd.confI can even sync with a pi-hole instance running gravity-sync on Raspbian 10(Buster) still :D
Re: STICKY - How to upgrade a Buster image to Bullseye
I tough was some common problem whit an easy fix but i got only jokes.
I'm a little noob on linux but i can say i did everything listed before trying the update and then launch the full upgrade.
Since i also tryed it on a live Pi image i managed to revert back everything, but t i still don' t understand why i get this error when launching the first command "sudo apt-get update"
It say something about missing files on the repo and then close.
didn't missed a step on the guide, i'm good at following them, my pi is a pihole/tvheadnd whit a double tuner and a very strict UFW rules.
Ity may be UFW messed up the upgrade and i have to disable it ?
Edit
I think i have found a mistake, one of the 2 list files missed an "e" becouse i was using a shitty wireless keyb and it was bullsey instead of bullseye.
Upgrading atm, crossfingers.......
I'm a little noob on linux but i can say i did everything listed before trying the update and then launch the full upgrade.
Since i also tryed it on a live Pi image i managed to revert back everything, but t i still don' t understand why i get this error when launching the first command "sudo apt-get update"
It say something about missing files on the repo and then close.
didn't missed a step on the guide, i'm good at following them, my pi is a pihole/tvheadnd whit a double tuner and a very strict UFW rules.
Ity may be UFW messed up the upgrade and i have to disable it ?
Edit
I think i have found a mistake, one of the 2 list files missed an "e" becouse i was using a shitty wireless keyb and it was bullsey instead of bullseye.
Upgrading atm, crossfingers.......
Re: STICKY - How to upgrade a Buster image to Bullseye
Ok, I worked this out. Just in case it helps anyone else - notification-daemon needed adding to autostart.
Re: STICKY - How to upgrade a Buster image to Bullseye
Did NOT work for me. Upgraded from Buster to Bullseye on a Pi 2 hardware. "notification-daemon" wasn ́t even installed.
Installed it manually using "sudo apt install notification-daemon".
Still "sudo service notification-daemon" gives "Unit notification-daemon.service could not be found." and there ́s no entry in lxpanel configuration. It should be "Notification" or sth. like that, right?
The updater plugin by the way was instantly available in lxpanel configuration by the way.
Not sure what to try next, happy for advice.
1) Nextcloud/Pi-hole/Docker/... @ RPi OS @ Pi 5 (8 GB, NVMe)
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
Re: STICKY - How to upgrade a Buster image to Bullseye
Oh god.
Install went all fine but °çcked up my pihole and tvheadend, the new kms driver sux a lot on pi3 and under, we can't even select the resolution we want in VNC, also whit a clean install was pretty messed up vs Buster ( yeah yeah 2 years of updates.... ) but now....
I'll just say "meh" they are starting to drop support for old pi's to fix up the mess that was pi4
PS
I'm not buying a pi4 for a pihole/tvheadend since for a 2-4GB version cost over 80e atm and over 100e the 4GB version, also i still have a 3b+ taking dust that have no use atm, so why i should spend 100e for a new pi ? ( all new cables cost not included )
Bullseyey release even if it was in testing before august, was a big flop, on the interwebz looks like most people agree whit me.
Install went all fine but °çcked up my pihole and tvheadend, the new kms driver sux a lot on pi3 and under, we can't even select the resolution we want in VNC, also whit a clean install was pretty messed up vs Buster ( yeah yeah 2 years of updates.... ) but now....
I'll just say "meh" they are starting to drop support for old pi's to fix up the mess that was pi4
PS
I'm not buying a pi4 for a pihole/tvheadend since for a 2-4GB version cost over 80e atm and over 100e the 4GB version, also i still have a 3b+ taking dust that have no use atm, so why i should spend 100e for a new pi ? ( all new cables cost not included )
Bullseyey release even if it was in testing before august, was a big flop, on the interwebz looks like most people agree whit me.
Re: STICKY - How to upgrade a Buster image to Bullseye
Also the pre-made files i have been using in those last 2 years do not work anymore
wifi plus ssh enabled on boot don't work anymore, putting the 2 files in the boot partition, it doesn't even take the right ip from the modem, like the MAC of the pi ETH was changed, i had a rules to apply that Pi a designated IP, also that don't work anymore.
Bullseye realease = epic fail
Sorry pi foundation but it's the harsh truth. from the start you promised retrocompatibility whit olders pi, now you are walking on the razer blade.
wifi plus ssh enabled on boot don't work anymore, putting the 2 files in the boot partition, it doesn't even take the right ip from the modem, like the MAC of the pi ETH was changed, i had a rules to apply that Pi a designated IP, also that don't work anymore.
Bullseye realease = epic fail
Sorry pi foundation but it's the harsh truth. from the start you promised retrocompatibility whit olders pi, now you are walking on the razer blade.
- JohnAmstrong
- Posts: 23
- Joined: Wed Nov 17, 2021 7:57 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
During the upgrade it asks me if Iwant to keep my current config files or use the newer ones of package maintainer for several packages.
For the thirdy party ones edited by me I could use the newer package maintainer version setting them again but I'm not sure about the ones that I haven't manually edited by myself. What is better to do?
For the thirdy party ones edited by me I could use the newer package maintainer version setting them again but I'm not sure about the ones that I haven't manually edited by myself. What is better to do?
Re: STICKY - How to upgrade a Buster image to Bullseye
Bit of a noob question but I think my problem is related to rfkill...
I'm trying to install Raspberry Pi OS Lite (2021年10月30日 Bullseye Lite) on a Pi Zero W. I have placed wpa_supplicant.conf and ssh files in the boot folder, but the device has only succeeded to connect to wifi on a couple of installations (ie. the Pi has appeared on my network and I've managed to SSH in).
I've had a need to go back and re-image the Pi Zero, but it won't connect to wifi....again. I've repeated the process of writing the image, copy wpa_supplicant.conf and ssh files, rinse and repeat dozens of times before I might eventually have success.
So the problem is intermittent, and I might have success once in very 15 times. The steps I'm taking are accurately repeated every time but the outcome can be different.
This is another thread that refers to the same problem -
viewtopic.php?p=1293506&hilit=How+to+re ... t#p1293506
I wish to alter the image as the thread above suggests. How is this done from a Windows machine with the image written to the SD card?
I'm trying to install Raspberry Pi OS Lite (2021年10月30日 Bullseye Lite) on a Pi Zero W. I have placed wpa_supplicant.conf and ssh files in the boot folder, but the device has only succeeded to connect to wifi on a couple of installations (ie. the Pi has appeared on my network and I've managed to SSH in).
I've had a need to go back and re-image the Pi Zero, but it won't connect to wifi....again. I've repeated the process of writing the image, copy wpa_supplicant.conf and ssh files, rinse and repeat dozens of times before I might eventually have success.
So the problem is intermittent, and I might have success once in very 15 times. The steps I'm taking are accurately repeated every time but the outcome can be different.
This is another thread that refers to the same problem -
viewtopic.php?p=1293506&hilit=How+to+re ... t#p1293506
I wish to alter the image as the thread above suggests. How is this done from a Windows machine with the image written to the SD card?
Re: STICKY - How to upgrade a Buster image to Bullseye
It doesn't run as a systemd service. Add this to /etc/xdg/lxsession/LXDE-pi/autostart:e-raser wrote: ↑Tue Nov 16, 2021 7:15 pmDid NOT work for me. Upgraded from Buster to Bullseye on a Pi 2 hardware. "notification-daemon" wasn ́t even installed.
Installed it manually using "sudo apt install notification-daemon".
Still "sudo service notification-daemon" gives "Unit notification-daemon.service could not be found." and there ́s no entry in lxpanel configuration. It should be "Notification" or sth. like that, right?
The updater plugin by the way was instantly available in lxpanel configuration by the way.
Not sure what to try next, happy for advice.
@/usr/lib/notification-daemon/notification-daemon
Re: STICKY - How to upgrade a Buster image to Bullseye
My headless 3B upgraded following the original instructions after manually fixing two issues post reboot. Both I solved by plugging in a keyboard and monitor and running raspi-config.
1. Like another poster, /etc/systemd/system/dhcpcd.service.d/wait.conf had an incorrect path; raspi-config will fix this by toggling "Network at Boot" under the "System Options" off and on again
2. My Pi is setup with a static IP address assigned to eth0 but the upgrade enabled predictable interface names which results in my primary interface getting changes and picking up my static IP settings; raspi-config will fix this by disabling the feature in "Advanced Options"
1. Like another poster, /etc/systemd/system/dhcpcd.service.d/wait.conf had an incorrect path; raspi-config will fix this by toggling "Network at Boot" under the "System Options" off and on again
2. My Pi is setup with a static IP address assigned to eth0 but the upgrade enabled predictable interface names which results in my primary interface getting changes and picking up my static IP settings; raspi-config will fix this by disabling the feature in "Advanced Options"
Re: STICKY - How to upgrade a Buster image to Bullseye
Not even a fresh install on both pi3b and pi3b+ works so well, this release looks more like a pi4 race to fix bugs and who cares of olders Pis
:?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?:
When the foundation released bullseye in this state after months of testing i can onlly say, epic fail.
:?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?:
When the foundation released bullseye in this state after months of testing i can onlly say, epic fail.
- jamesh
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 35174
- Joined: Sat Jul 30, 2011 7:41 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Actually, we care about older Pi's. And by we, I mean Raspberry Pi Trading Ltd, not the Foundation, who have nothing to do with the HW or SW releases.l0calH0st wrote: ↑Fri Nov 19, 2021 12:40 amNot even a fresh install on both pi3b and pi3b+ works so well, this release looks more like a pi4 race to fix bugs and who cares of olders Pis
:?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?:
When the foundation released bullseye in this state after months of testing i can onlly say, epic fail.
We've always ensured that all our OS' work on all our devices. And that should/will be the case with Bullseye. Despite a lot of testing, when an OS with as many changes in as Bullseye is released, there are always some teething troubles. We've found some really weird edge cases with Mutter recognising display devices for example, that simply didn't come up in testing. So, we do expect a bunch of bugs to be reported after an OS release, and we are currently working to fix all the ones that have been reported. And that will be on ALL platforms.
Releasing a major change like this is a balancing act, we've had people clamouring for Bullseye for months, but we have not released until we thought it was good enough for the majority of people, which we think it is now. There are bound to be bugs, but we fix up those as quickly as we can as they are reported.
So, not an epic fail. Most people are OK, some things need sorting out.
Software guy, working in the applications team.
Re: STICKY - How to upgrade a Buster image to Bullseye
Hi again,
I tried to upgrade a rpi3 B+ that I use as home server to a newer rpi4B 8GB. The problem starts trying to upgrade the OS from buster to bullseye. When I change the sources.list and raspi.list and run.
I don't get any packages that need to be updated. Moreover, when I try to install something manually as for example:
I got the above messge.
OS is still buster as it's depicted here
Any help will be appreciated.
I tried to upgrade a rpi3 B+ that I use as home server to a newer rpi4B 8GB. The problem starts trying to upgrade the OS from buster to bullseye. When I change the sources.list and raspi.list and run.
Code: Select all
apt updateCode: Select all
apt install --reinstall raspberrypi-bootloader raspberrypi-kernel
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of raspberrypi-bootloader is not possible, it cannot be downloaded.
Reinstallation of raspberrypi-kernel is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
OS is still buster as it's depicted here
Code: Select all
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Re: STICKY - How to upgrade a Buster image to Bullseye
Please show the output of "apt policy". That will show which sources your Pi is looking at.
Unreadable squiggle
Re: STICKY - How to upgrade a Buster image to Bullseye
Hi
Thanks for the reply
Code: Select all
apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
-1 http://archive.raspberrypi.org/debian bullseye/main armhf Packages
release o=Raspberry Pi Foundation,a=stable,n=bullseye,l=Raspberry Pi Foundation,c=main,b=armhf
origin archive.raspberrypi.org
500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
release o=Node Source,n=buster,l=Node Source,c=main,b=armhf
origin deb.nodesource.com
-1 https://repos.influxdata.com/debian bullseye/stable armhf Packages
release o=InfluxDB,n=bullseye,l=InfluxDB,c=stable,b=armhf
origin repos.influxdata.com
500 https://download.docker.com/linux/raspbian bullseye/stable armhf Packages
release o=Docker,a=bullseye,l=Docker CE,c=stable,b=armhf
origin download.docker.com
-1 http://raspbian.raspberrypi.org/raspbian bullseye/rpi armhf Packages
release o=Raspbian,a=stable,n=bullseye,l=Raspbian,c=rpi,b=armhf
origin raspbian.raspberrypi.org
-1 http://raspbian.raspberrypi.org/raspbian bullseye/non-free armhf Packages
release o=Raspbian,a=stable,n=bullseye,l=Raspbian,c=non-free,b=armhf
origin raspbian.raspberrypi.org
-1 http://raspbian.raspberrypi.org/raspbian bullseye/contrib armhf Packages
release o=Raspbian,a=stable,n=bullseye,l=Raspbian,c=contrib,b=armhf
origin raspbian.raspberrypi.org
-1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
release o=Raspbian,a=stable,n=bullseye,l=Raspbian,c=main,b=armhf
origin raspbian.raspberrypi.org
Pinned packages:
wireguard-dkms -> 1.0.20210219-1 with priority 100
wireguard-tools -> 1.0.20210223-1 with priority 100
wireguard -> 1.0.20210223-1 with priority 100Re: STICKY - How to upgrade a Buster image to Bullseye
Correct. Have you made any changes to the apt configuration files at any point? In particular any files in /etc/apt/preferences.d/ that might Pin bullseye priority to -1
Unreadable squiggle
Re: STICKY - How to upgrade a Buster image to Bullseye
Hmmm...
under /etc/apt/preferences.d there is a file called "pivpn-limit-bullseye" which has the following contents.
Code: Select all
Package: *
Pin: release n=bullseye
Pin-Priority: -1
Package: wireguard wireguard-dkms wireguard-tools
Pin: release n=bullseye
Pin-Priority: 100Well....I just removed it and voila! 914 packages can be upgraded. I will proceed and wait for the result. I did a backup for the peace of mind :)
Thank you very much. I appreciate your help and time.
Re: STICKY - How to upgrade a Buster image to Bullseye
Very wise. I'm sure everything will upgrade correctly, but backups are always good to have.
Unreadable squiggle
Re: STICKY - How to upgrade a Buster image to Bullseye
Thanks, I will give it a try. Not sure how to test this actually...chrisy wrote: ↑Thu Nov 18, 2021 8:18 pmIt doesn't run as a systemd service. Add this to /etc/xdg/lxsession/LXDE-pi/autostart:e-raser wrote: ↑Tue Nov 16, 2021 7:15 pmDid NOT work for me. Upgraded from Buster to Bullseye on a Pi 2 hardware. "notification-daemon" wasn ́t even installed.
Installed it manually using "sudo apt install notification-daemon".
Still "sudo service notification-daemon" gives "Unit notification-daemon.service could not be found." and there ́s no entry in lxpanel configuration. It should be "Notification" or sth. like that, right?
The updater plugin by the way was instantly available in lxpanel configuration by the way.
Not sure what to try next, happy for advice.
@/usr/lib/notification-daemon/notification-daemon
My LXDE autostart file now contains (just in case something else is missing here - maybe somebody can compare it):
Code: Select all
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
@/usr/lib/notification-daemon/notification-daemon1) Nextcloud/Pi-hole/Docker/... @ RPi OS @ Pi 5 (8 GB, NVMe)
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
Re: STICKY - How to upgrade a Buster image to Bullseye
Easiest way to test is to install libnotify-bin then rune-raser wrote: ↑Sun Nov 21, 2021 9:52 pmThanks, I will give it a try. Not sure how to test this actually...chrisy wrote: ↑Thu Nov 18, 2021 8:18 pmIt doesn't run as a systemd service. Add this to /etc/xdg/lxsession/LXDE-pi/autostart:e-raser wrote: ↑Tue Nov 16, 2021 7:15 pm
Did NOT work for me. Upgraded from Buster to Bullseye on a Pi 2 hardware. "notification-daemon" wasn ́t even installed.
Installed it manually using "sudo apt install notification-daemon".
Still "sudo service notification-daemon" gives "Unit notification-daemon.service could not be found." and there ́s no entry in lxpanel configuration. It should be "Notification" or sth. like that, right?
The updater plugin by the way was instantly available in lxpanel configuration by the way.
Not sure what to try next, happy for advice.
@/usr/lib/notification-daemon/notification-daemon
My LXDE autostart file now contains (just in case something else is missing here - maybe somebody can compare it):Code: Select all
@lxpanel --profile LXDE-pi @pcmanfm --desktop --profile LXDE-pi @xscreensaver -no-splash @/usr/lib/notification-daemon/notification-daemon
Code: Select all
notify-send testRe: STICKY - How to upgrade a Buster image to Bullseye
That proved it works. Perfect, thanks a lot :-)chrisy wrote: ↑Sun Nov 21, 2021 10:16 pmEasiest way to test is to install libnotify-bin then rune-raser wrote: ↑Sun Nov 21, 2021 9:52 pmThanks, I will give it a try. Not sure how to test this actually...
My LXDE autostart file now contains (just in case something else is missing here - maybe somebody can compare it):Code: Select all
@lxpanel --profile LXDE-pi @pcmanfm --desktop --profile LXDE-pi @xscreensaver -no-splash @/usr/lib/notification-daemon/notification-daemonCode: Select all
notify-send test
1) Nextcloud/Pi-hole/Docker/... @ RPi OS @ Pi 5 (8 GB, NVMe)
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
2) Home Assistant @ HA OS @ Pi 5 (8 GB, NVMe)
3) Kodi media center @ LibreELEC @ Pi 4 (4 GB)
4) Testing system @ RPi OS @ Pi 3 B+
5) Backup/restore system (raspiBackup) @ RPi OS Lite @ Pi 2
- easytarget
- Posts: 14
- Joined: Tue Nov 23, 2021 4:30 am
Re: STICKY - How to upgrade a Buster image to Bullseye
Python note; following this upgrade the default python will be broken:
Trying to install 'python' wants to drag you into depreciation valley:
..... followed my me saying 'yikes' and very firmly rejecting the suggested actions.
running: will fix things up, but .. defaulting to python2, 10 months after it was very definitively EOL'd seems like a mis-step.
I had assumed, after reading thisviewtopic.php?t=323289, that the default for 'apt install python' would be a v3.9
Code: Select all
python
-bash: python: command not foundCode: Select all
$ sudo apt install python
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'python-is-python2' instead of 'python'
running:
Code: Select all
$ sudo apt install python-is-python3I had assumed, after reading thisviewtopic.php?t=323289, that the default for 'apt install python' would be a v3.9
Re: STICKY - How to upgrade a Buster image to Bullseye
Still using openbox as a window manager, not entirely sure how to get it to use mutter. Any suggestions?
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