A small, affordable computer with free resources to help people learn, make things, and have fun
https://forums.raspberrypi.com/
Not sure if I mix it up with the screen driver but some features will only be offered to Pi‘s with at least 2 GB of RAM - so plenty of older models won’t get it. Just read the release note blog article, it should be stated there.
I have Pi 4's with 4 GB RAM, so I guess it should work. wmctrl -m gives me openbox as wm. I can do a mutter --replace to get it work, but would ideally want something out of the box. Changing /etc/xdg/lxsession/LXDE_pi/desktop.conf helps, but remote desktop connections (VNC, RDP) still fallback to openbox.
Same for me here. I just upgraded manually from Buster to Bullseye on my RPi 4 with 8GB.henkiew wrote: ↑Sat Nov 13, 2021 1:40 pmHi, 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
Code: Select all
# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
...
# uname -a
Linux himbeere69.fritz.box 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux
root@himbeere69:~# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 144.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
...
Hardware : BCM2711
Revision : d03114
Serial : 10000000d21ea7da
Model : Raspberry Pi 4 Model B Rev 1.4
# grep arm_freq /boot/config.txt
#arm_freq=800
Code: Select all
hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19Code: Select all
1 System Options
S2 Audio
Code: Select all
1 System Options
I am running into this issue now on port 53. Could you help with steps to solve it?linuxusr80 wrote: ↑Mon Nov 08, 2021 7:56 pmPlease note if you have pihole installed, connman will enable itself on port 53. Disabling connman service resolves. in addition if you have a static ip address, eth0 is renamed and eth0 is disabled. you need to update in you dhcpcs.conf file.
Resolved here:ralphrmartin wrote: ↑Sat Nov 27, 2021 3:20 pmAfter upgrading a headless rpi 4 which does not have a monitor connected, I am getting a lot of messages likeCode: Select all
hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
You could use the netstat command to identify what is locking port 53tobe2d wrote: ↑Sun Nov 28, 2021 7:36 pmI am running into this issue now on port 53. Could you help with steps to solve it?linuxusr80 wrote: ↑Mon Nov 08, 2021 7:56 pmPlease note if you have pihole installed, connman will enable itself on port 53. Disabling connman service resolves. in addition if you have a static ip address, eth0 is renamed and eth0 is disabled. you need to update in you dhcpcs.conf file.
Code: Select all
$ sudo netstat -nltup | grep :53
Code: Select all
$ sudo apt-get install network-manager network-manager-gnome
Code: Select all
$ sudo apt-get remove connman
Code: Select all
$ sudo netstat -nltup | grep :53
Code: Select all
$ sudo systemctl stop unbound
$ sudo systemctl disable unbound
Code: Select all
$ pihole restartdns
$ pihole status
nikal wrote: ↑Sat Nov 20, 2021 7:40 pmHmmm...
under /etc/apt/preferences.d there is a file called "pivpn-limit-bullseye" which has the following contents.
A long time ago I had tested pivpn but changed my mind and did a manual installation/setup of standalone openvpn. For some reason pivpn doesn't like bullseye. Probably wireguard is the reason...anyway.Code: Select all
Package: * Pin: release n=bullseye Pin-Priority: -1 Package: wireguard wireguard-dkms wireguard-tools Pin: release n=bullseye Pin-Priority: 100
Well....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 :) <- THIS! Thanks a lot! I had the exact same issue.
Thank you very much. I appreciate your help and time.
Perfect! Made my day! :-)ElDavo wrote: ↑Tue Nov 09, 2021 5:40 pmIn case you have no (wired only) network after the update, check if you have this file:The content of the file in my case was:Code: Select all
/etc/systemd/system/dhcpcd.service.d/wait.confDelete this file to make dhcpcd run again.Code: Select all
[Service] ExecStart= ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w
Now you should start another process to make things more portable. I don't see any hardware dependencies, it is all software, likely headless. Generic Debian Buster to Bullseye (AMD64) was quite painless in my experience, but Raspbian is heavily tweaked. You run 32-bit software, also fit for old ARMv6, on a 8GB 4-core ARM64 platform. A lot of changes/improvement is possible.Paul-12TA wrote: ↑Tue Dec 07, 2021 8:10 pmI have an image under Buster that is working very nicely for me 24/7 on an 8gb RPi4. I have installed many programs that are all working well e.g. it's a web server for a wikis (including for others) plus other stuff, influxdb, grafana, node-red, MQTT server, ufw, public key SSH, shared folders with W10 etc. It has been a long involved incremental process over many hours.
There is now legacy Raspbian Buster, look at the download page for more info. Maybe that is easier and better way forward.Should I just ignore Bullseye for the next year or so?
Should I wait for news, hoping that the upgrade process will evolve and mature and improve so that it works?
You can make you own RPi4 into a stable host for virtual machines. I would move the whole 32-bit stuff ('image') into a virtual machine. The same RPi4 should run 64-bit OS with libvirt/KVM running this virtual machine. It needs al lot of tricks, good understanding of EFI, booting, networking, etc, but I do this for quite some time now. It helps if you have extra RPi4 (or RPi3) for practice/testing.Or should move everything onto a stable hosted virtual machine environment on the web, as I have my own domain? And give up on the RPi4 as it has faltered so badly.
davidcoton wrote: ↑Thu Dec 09, 2021 11:21 amFTFY.
RPiOS was separated from Raspbian to enable RPiOS to go its own way, supporting ARM64 and leaving its Raspbian roots behind.
Code: Select all
# cat /usr/lib/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
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"
# cat /usr/lib/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Yes, there are some inconsistencies internally. But I believe the nearest we have to an "official" naming is to use RPiOS-32 and RPiOS-64.redvli wrote: ↑Fri Dec 10, 2021 11:15 amdavidcoton wrote: ↑Thu Dec 09, 2021 11:21 amFTFY.
RPiOS was separated from Raspbian to enable RPiOS to go its own way, supporting ARM64 and leaving its Raspbian roots behind.Both run 64-bit kernel in my case. But to differentiate in scripts, I am using identifiers "raspbian" and "raspios", as I also have 32-bit "debian" armv7 in a KVM and 64-bit "debian" armv8 in a KVM. The 'debian's use EFI for booting and can be treated equally for certain scripts/functionality.Code: Select all
# cat /usr/lib/os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye 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" # cat /usr/lib/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
What the marketeers want is this:davidcoton wrote: ↑Fri Dec 10, 2021 12:14 pmYes, there are some inconsistencies internally. But I believe the nearest we have to an "official" naming is to use RPiOS-32 and RPiOS-64.
The RPi versions are distinctly different from Raspbian (still available, I believe), straight Debian or any other Debian-based distros for Pi.
I'm just suggesting that you would do better to use a name that does not cause confusion, since Raspbian is not the same as RPiOS. There is presumably a reason for RPT not to have updated the reported name -- personally it doesn't concern me, I don't need to use that data. If it did, I would submit a PR. Since it doesn't, I'll leave the engineers to work on something more useful.redvli wrote: ↑Fri Dec 10, 2021 3:32 pmWhat the marketeers want is this:davidcoton wrote: ↑Fri Dec 10, 2021 12:14 pmYes, there are some inconsistencies internally. But I believe the nearest we have to an "official" naming is to use RPiOS-32 and RPiOS-64.
The RPi versions are distinctly different from Raspbian (still available, I believe), straight Debian or any other Debian-based distros for Pi.
https://www.raspberrypi.com/software/operating-systems/
If you want some change, you should make make sure you get a change request accepted that changes the line
ID=raspbian
in /usr/lib/os-release
into something else in all the images in the above URL. Otherwise 32-bit will stay raspbian for me and 64-bit an unfinished port of debian, where quite some stuff that makes an RPi interesting doesn't work. So I run OpenSuSE Tumbleweed aarch64 on my 8GB Pi4.
I can think of a few reasons. One being that RPT don't produce the package that reports the name. Another being that the majority of the software in 32-bit RaspiOS is from the Raspbian repository, with the majority being directly from the Debian repository for 64-bit RaspiOS.davidcoton wrote: ↑Fri Dec 10, 2021 4:47 pmThere is presumably a reason for RPT not to have updated the reported name
Just as a datapoint, this worked perfectly for me on this Raspberry Pi 3 Model B+ whose workloads are UniFi Controller and Resilio Sync.spl23 wrote: ↑Mon Nov 08, 2021 10:58 amFirst off - we really do not recommend doing this, and we don't support it!
The only recommended way to upgrade to bullseye is to download and flash a clean bullseye image, and transfer your data and applications across. But if you really want to try to upgrade an existing buster image to bullseye, this is a method we have found to work on a clean install of the last released buster image. This does of course not guarantee it will work on your image, which will have all sorts of subtle differences from the clean image as a result of changes made while you used it - but it works for us.
First - and I cannot stress this enough - use dd or the SD Card Copier application to MAKE A BACKUP OF YOUR CARD. There is a non-zero chance that this upgrade will trash your system and leave you with an unbootable card. So don't say we didn't warn you! (Did I mention that we do not recommend doing this...?)
Edit /etc/apt/sources.list, and replace every occurrence of the word "buster" with "bullseye".
Do the same for any .list files in /etc/apt/sources.list.d/
Code: Select all
sudo apt updateThis will take a while to run. Answer "yes" to any questions during the install.Code: Select all
sudo apt install libgcc-8-dev gcc-8-base
Again, this will take a while, and again, answer "yes" to any questions during the install.Code: Select all
sudo apt full-upgrade
When it completes, edit /boot/config.txt.
Comment out any lines which contain "dtoverlay=vc4-fkms-v3d" by putting a # sign at the start of the line.
At the bottom of the file, in the [all] section, add the line "dtoverlay=vc4-kms-v3d" - note that is "kms", not "fkms".
Now reboot and cross your fingers...
If your system comes back up, it should now be running bullseye. You will probably need to reset any custom display resolution you had before.
As above - we do not support this process; it may work for you, or it may not. If you get it to work, or if you have problems, feel free to use this thread to share your experiences to help each other. Good luck!
Code: Select all
# apt upgrade --without-new-pkgsCode: Select all
# apt full-upgradeCode: Select all
dtoverlayCode: Select all
vc4-kms-v3dCode: Select all
dtoverlay=i2c,vc4-kms-v3dfirst for safety.# apt install aptitude
Code: Select all
nCode: Select all
cat /etc/os-releaseCode: Select all
pi@raspberrypi:~ $ sudo nano /etc/apt/sources.list
[sudo] Passwort für pi:
pi@raspberrypi:~ $ sudo nano /etc/apt/sources.list.d/raspi.list
pi@raspberrypi:~ $ sudo apt update
OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Holen:2 http://archive.raspberrypi.org/debian bullseye InRelease [23,5 kB]
Holen:3 http://raspbian.raspberrypi.org/raspbian bullseye/contrib armhf Packages [60,2 kB]
Holen:4 http://raspbian.raspberrypi.org/raspbian bullseye/non-free armhf Packages [106 kB]
Holen:5 http://raspbian.raspberrypi.org/raspbian bullseye/rpi armhf Packages [1.360 B]
Holen:6 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [243 kB]
Es wurden 435 kB in 1 s geholt (390 kB/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Alle Pakete sind aktuell.
pi@raspberrypi:~ $ sudo apt install libgcc-8-dev gcc-8-base
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
gcc-8-base ist schon die neueste Version (8.3.0-6+rpi1).
libgcc-8-dev ist schon die neueste Version (8.3.0-6+rpi1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
pi@raspberrypi:~ $ sudo apt full-upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
pi@raspberrypi:~ $ 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"Can you show us the output of the "apt policy" command?frRySuuZ9FFDQw wrote: ↑Thu Dec 23, 2021 11:47 amprobably anybody can give me a hint why nothing happens on my RPi4 with RaspberryOS Lite.
Code: Select all
deb http://raspbian.raspberrypi.org/raspbian/ bullseye mainCan you show us the output of the "apt policy" command?
Code: Select all
Paketdateien:
100 /var/lib/dpkg/status
release a=now
500 http://archive.raspberrypi.org/debian buster/main armhf Packages
release o=Raspberry Pi Foundation,a=oldstable,n=buster,l=Raspberry Pi Foundation,c=main,b=armhf
origin archive.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
500 http://raspbian.raspberrypi.org/raspbian buster/rpi armhf Packages
release o=Raspbian,a=oldstable,n=buster,l=Raspbian,c=rpi,b=armhf
origin raspbian.raspberrypi.org
500 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages
release o=Raspbian,a=oldstable,n=buster,l=Raspbian,c=non-free,b=armhf
origin raspbian.raspberrypi.org
500 http://raspbian.raspberrypi.org/raspbian buster/contrib armhf Packages
release o=Raspbian,a=oldstable,n=buster,l=Raspbian,c=contrib,b=armhf
origin raspbian.raspberrypi.org
500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
release o=Raspbian,a=oldstable,n=buster,l=Raspbian,c=main,b=armhf
origin raspbian.raspberrypi.org
Mit Pinning verwaltete Pakete:
wireguard-dkms -> 1.0.20210219-1 mit Priorität 100
wireguard-tools -> 1.0.20210223-1 mit Priorität 100
wireguard -> 1.0.20210223-1 mit Priorität 100
Code: Select all
-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
Ahhh :D
Code: Select all
pivpn-limit-bullseyeCode: Select all
Package: *
Pin: release n=bullseye
Pin-Priority: -1
Package: wireguard wireguard-dkms wireguard-tools
Pin: release n=bullseye
Pin-Priority: 100