jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 31354
Joined: Sat Jul 30, 2011 7:41 pm

STICKY: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 11:01 am

Hi all,

As you may have seen Bullseye has now been released, and it's a big one. It's not just an upgrade to Bullseye, but upgrades in lots of other places as well. Please see the blog post for more gory details.https://www.raspberrypi.com/news/raspbe ... -bullseye/

Please report any issues you may find here.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.

User avatar
DougieLawson
Posts: 42216
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 11:02 am

Thank you. That will keep me a little bit amused until the end of the year.
Torrents downloading now.

When can we expect the RaspiOS lipstick on a Debian X86 pig version?
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

steely_glint
Posts: 2
Joined: Mon Nov 08, 2021 10:59 am

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 11:13 am

Hi, I think the V4l2 /dev/video driver has dropped support for h264
buster$ v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture

[0]: 'YU12' (Planar YUV 4:2:0)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[1]: 'YUYV' (YUYV 4:2:2)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[2]: 'RGB3' (24-bit RGB 8-8-8)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[3]: 'JPEG' (JFIF JPEG, compressed)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[4]: 'H264' (H.264, compressed)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[5]: 'MJPG' (Motion-JPEG, compressed)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[6]: 'YVYU' (YVYU 4:2:2)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[7]: 'VYUY' (VYUY 4:2:2)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[8]: 'UYVY' (UYVY 4:2:2)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[9]: 'NV12' (Y/CbCr 4:2:0)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[10]: 'BGR3' (24-bit BGR 8-8-8)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[11]: 'YV12' (Planar YVU 4:2:0)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[12]: 'NV21' (Y/CrCb 4:2:0)
Size: Stepwise 32x32 - 3280x2464 with step 2/2
[13]: 'RX24' (32-bit XBGR 8-8-8-8)
Size: Stepwise 32x32 - 3280x2464 with step 2/2

I now get :
bullseye$ v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture

[0]: 'YUYV' (YUYV 4:2:2)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[1]: 'UYVY' (UYVY 4:2:2)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[2]: 'YVYU' (YVYU 4:2:2)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[3]: 'VYUY' (VYUY 4:2:2)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[4]: 'RGBP' (16-bit RGB 5-6-5)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[5]: 'RGBR' (16-bit RGB 5-6-5 BE)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[6]: 'RGBO' (16-bit A/XRGB 1-5-5-5)
Size: Stepwise 16x16 - 16376x16376 with step 1/1
[7]: 'RGBQ' (16-bit A/XRGB 1-5-5-5 BE)
... and 40 more none of which are h264.

this is on a Raspberry Pi 3 Model B Rev 1.2 with a pi camera v2.1

Any ideas for getting h264 back ?

Thanks.

Mikael
Posts: 43
Joined: Wed Feb 11, 2015 12:35 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 12:30 pm

Nice! I will start testing this later tonight. By the way, which Mesa version are you using for this release?

busywait
Posts: 142
Joined: Sat May 09, 2020 10:48 pm
Location: Southampton, UK

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:15 pm

Mikael wrote:
Mon Nov 08, 2021 12:30 pm
... By the way, which Mesa version are you using for this release?
pi@rpi-b64:~ $ apt list --installed | grep mesa
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libegl-mesa0/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
libgl1-mesa-dri/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed]
libglapi-mesa/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
libgles2-mesa/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed]
libglx-mesa0/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
mesa-va-drivers/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
mesa-vdpau-drivers/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]

Mikael
Posts: 43
Joined: Wed Feb 11, 2015 12:35 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:31 pm

busywait wrote:
Mon Nov 08, 2021 1:15 pm
Mikael wrote:
Mon Nov 08, 2021 12:30 pm
... By the way, which Mesa version are you using for this release?
pi@rpi-b64:~ $ apt list --installed | grep mesa
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libegl-mesa0/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
libgl1-mesa-dri/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed]
libglapi-mesa/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
libgles2-mesa/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed]
libglx-mesa0/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
mesa-va-drivers/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
mesa-vdpau-drivers/stable,now 20.3.5-1+rpt3+rpi1 arm64 [installed,automatic]
Thanks!

andrum99
Posts: 1639
Joined: Fri Jul 20, 2012 2:41 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:41 pm

kerry_s wrote:
Mon Nov 08, 2021 1:24 pm
i think they should have turned on the edge-tiling & center-new-windows by default. :D
How do I access that config tool thingy on the left in that screenshot? Also, does "edge tiling" do what Windows 10 does, where if you drag a window beyond the left or right of the screen it gives you an option to have it fit one half of the screen, then gives you a choice of which window to fill the other half with? The explanatory text for that option in the screenshot is not hugely helpful in its description.

busywait
Posts: 142
Joined: Sat May 09, 2020 10:48 pm
Location: Southampton, UK

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:48 pm

jamesh wrote:
Mon Nov 08, 2021 11:01 am
Please report any issues you may find here.
Blank screen on first boot/reboot

An observation: 4K screen resolutions are quite fussy about the cable used and/or the core_freq overclock in /boot/config.txt

I have a 3440x1440 monitor, iiyama ProLite XUB3493WQSU. When I booted with the micro-HDMI-to-HDMI adaptor+cable that I usually use then the 64-bit OS image booted to a blank screen. I've found 2 ways to fix this.

1: I tried a white Raspberry Pi branded micro-HDMI to HDMI cable, the desktop appeared
2: Either of these lines in /boot/config.txt enables the desktop to appear with my micro-HDMI adaptor+cable
hdmi_enable_4kp60=1
# or
#core_freq=600
#core_freq=550 did not work!

I made this edit by pressing Ctrl-Alt-F1 while staring at a blank screen during the first boot and editing /boot/config.txt. (Ctrl-Alt-F1/F2/... did not have any effect on a second boot, only during the first boot).

Equally easy, the /boot/config.txt file can be edited from another PC.

Other things that I tried that did not work:

#This did not help, X still caused a blank screen with my usual adaptor+HDMI cable
hdmi_group=1
hdmi_mode=16

#This did not help, X still caused a blank screen with my usual adaptor+HDMI cable
hdmi_safe_mode=1
Last edited by busywait on Mon Nov 08, 2021 2:09 pm, edited 1 time in total.

cjan
Posts: 969
Joined: Sun May 06, 2012 12:00 am

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:49 pm

panel color transparency not function or broken.

carldani
Posts: 70
Joined: Wed Jan 11, 2012 12:08 am

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 1:54 pm

vcdbg is missing in the 64 bit image. I will use the old statically compiled version for now.

User avatar
kerry_s
Posts: 4065
Joined: Thu Jan 30, 2020 7:14 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 2:07 pm

andrum99 wrote:
Mon Nov 08, 2021 1:41 pm
kerry_s wrote:
Mon Nov 08, 2021 1:24 pm
i think they should have turned on the edge-tiling & center-new-windows by default. :D
How do I access that config tool thingy on the left in that screenshot? Also, does "edge tiling" do what Windows 10 does, where if you drag a window beyond the left or right of the screen it gives you an option to have it fit one half of the screen, then gives you a choice of which window to fill the other half with? The explanatory text for that option in the screenshot is not hugely helpful in its description.

Code: Select all

sudo apt install dconf-editor
org> gnome> mutter

yes, dragging to edge resizes to half screen.

andrum99
Posts: 1639
Joined: Fri Jul 20, 2012 2:41 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 2:26 pm

kerry_s wrote:
Mon Nov 08, 2021 2:07 pm

Code: Select all

sudo apt install dconf-editor
org> gnome> mutter

yes, dragging to edge resizes to half screen.
Thanks - that seems to work well, and would certainly be a useful addition to the defaults. I'm not a fan of centring windows by default though.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6110
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 2:56 pm

busywait wrote:
Mon Nov 08, 2021 1:48 pm
1: I tried a white Raspberry Pi branded micro-HDMI to HDMI cable, the desktop appeared
If it works with a high quality cable, and doesn't with a low quality cable, then it's not something we will be trying to fix.
High resolution / refresh rates require a high quality cable.
busywait wrote:
Mon Nov 08, 2021 1:48 pm

Code: Select all

hdmi_group=1
hdmi_mode=16
hdmi_safe_mode=1
Note that the hdmi_* options are generally interpreted by the firmware and are not considered by the arm-side kms driver.
You generally want to use the "video=" option in cmdline.txt, which is a standard linux/kms options. See here.

(hdmi_enable_4kp60=1 actually controls clocks, rather than hdmi output, and does apply to both kms and fkms).

aBUGSworstnightmare
Posts: 5389
Joined: Tue Jun 30, 2015 1:35 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 3:15 pm

CPUFreq frontend applet is not shown in taskbar
Bildschirmfoto 2021-11-08 um 16.13.06.jpg
Bildschirmfoto 2021-11-08 um 16.13.06.jpg (81.05 KiB) Viewed 27689 times

Raspberry Pi in use is a Zero 2 W.

DarkElvenAngel
Posts: 2263
Joined: Tue Mar 20, 2018 9:53 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 3:21 pm

Is there a way to suppress the device tree notices?

I get two notices on boot.

Code: Select all

Failed to load HAT overlay

Code: Select all

dterror: not a valid FDT - err - 9
This is with the Argon Artik Hat will l test with the argon one case and report back if I see anything.

DarkElvenAngel
Posts: 2263
Joined: Tue Mar 20, 2018 9:53 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 3:33 pm

DarkElvenAngel wrote: Is there a way to suppress the device tree notices?

I get two notices on boot.

Code: Select all

Failed to load HAT overlay

Code: Select all

dterror: not a valid FDT - err - 9
This is with the Argon Artik Hat will l test with the argon one case and report back if I see anything.
The Argon one v1 and v2 do not produce these messages.

However my Pi 4 2Gb was hanging on Shutdown I'm not sure the issue there and the 4 and 8 Gb units shut down just fine.

busywait
Posts: 142
Joined: Sat May 09, 2020 10:48 pm
Location: Southampton, UK

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 3:35 pm

dom wrote:
Mon Nov 08, 2021 2:56 pm
If it works with a high quality cable, and doesn't with a low quality cable, then it's not something we will be trying to fix.
High resolution / refresh rates require a high quality cable.
I'll agree that they are *different* cable arrangements :) (And it seems that both support the highest resolution and refresh rate).

Thanks for the KMS video config links - helpful to know about. A simple "uncomment this" reconfiguration seems kinder and more helpful for first-boot users that don't yet have appropriate cables. The hdmi_safe_mode=1 line in config.txt jumps out as an obvious setting for this. Does the documentation need an update to say that it is ignored in the new OS?

Maybe a conservative default configuration could avoid the black screen on the first boot for people who don't yet have a matching cable? Perhaps default to 1080p as a maximum until the user chooses a higher resolution later with the standard "click here to accept" fallback behaviour?

User avatar
rpiMike
Posts: 2169
Joined: Fri Aug 10, 2012 12:38 pm
Location: Cumbria, UK

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 3:48 pm

If you add the 'CPUFreq frontend' panel applet to the taskbar, nothing appears on the taskbar!

Edit: I see aBUGSworstnightmare already reported.

User avatar
CheezPi
Posts: 57
Joined: Sun Sep 15, 2019 6:47 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 4:44 pm

Okay, so I do have one issue so far: the desktop won't fit my old ONN 10" TV...again.

Also, the sudo nano boot config thing didn't work out, so I might need to figure it out again. However, Bullseye boots up great otherwise, but now I'm back to using overscan again.

My TV/monitor resolution is again "1366x768" btw.

I still appreciate your hard work though. Thanks.
Amateur musician and Raspberry Pi enthusiast.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 31354
Joined: Sat Jul 30, 2011 7:41 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 4:50 pm

CheezPi wrote:
Mon Nov 08, 2021 4:44 pm
Okay, so I do have one issue so far: the desktop won't fit my old ONN 10" TV...again.

Also, the sudo nano boot config thing didn't work out, so I might need to figure it out again. However, Bullseye boots up great otherwise, but now I'm back to using overscan again.

My TV/monitor resolution is again "1366x768" btw.

I still appreciate your hard work though. Thanks.
1366x768 is the PITA one. The HW cannot support it directly, so will revert to the next resolution down, 720p I guess. That may be causing the borders.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.

spl23
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 459
Joined: Fri Dec 26, 2014 11:02 am

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 4:53 pm

aBUGSworstnightmare wrote:
Mon Nov 08, 2021 3:15 pm
CPUFreq frontend applet is not shown in taskbar
I'm afraid that's an upstream plugin that we have never supported - you can use the CPU Temperature and CPU Usage plugins, but it looks as if something in that plugin was incompatible with GTK+3 and didn't move across properly when we rebuilt everything. I'll have a look and see if it is anything obvious.

spl23
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 459
Joined: Fri Dec 26, 2014 11:02 am

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 4:54 pm

DarkElvenAngel wrote:
Mon Nov 08, 2021 3:21 pm
Is there a way to suppress the device tree notices?
Not just those, no, but you can turn off all notifications by disabling them in the Appearance page of Panel Settings.

User avatar
CheezPi
Posts: 57
Joined: Sun Sep 15, 2019 6:47 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 4:56 pm

jamesh wrote:
Mon Nov 08, 2021 4:50 pm
CheezPi wrote:
Mon Nov 08, 2021 4:44 pm
Okay, so I do have one issue so far: the desktop won't fit my old ONN 10" TV...again.

Also, the sudo nano boot config thing didn't work out, so I might need to figure it out again. However, Bullseye boots up great otherwise, but now I'm back to using overscan again.

My TV/monitor resolution is again "1366x768" btw.

I still appreciate your hard work though. Thanks.
1366x768 is the PITA one. The HW cannot support it directly, so will revert to the next resolution down, 720p I guess. That may be causing the borders.
So, which settings should I put on config.txt now, may I ask?
Amateur musician and Raspberry Pi enthusiast.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 31354
Joined: Sat Jul 30, 2011 7:41 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 5:19 pm

CheezPi wrote:
Mon Nov 08, 2021 4:56 pm
jamesh wrote:
Mon Nov 08, 2021 4:50 pm
CheezPi wrote:
Mon Nov 08, 2021 4:44 pm
Okay, so I do have one issue so far: the desktop won't fit my old ONN 10" TV...again.

Also, the sudo nano boot config thing didn't work out, so I might need to figure it out again. However, Bullseye boots up great otherwise, but now I'm back to using overscan again.

My TV/monitor resolution is again "1366x768" btw.

I still appreciate your hard work though. Thanks.
1366x768 is the PITA one. The HW cannot support it directly, so will revert to the next resolution down, 720p I guess. That may be causing the borders.
So, which settings should I put on config.txt now, may I ask?
I'll have to check. I think there might be some runes which allow the use of a specific set of numbers for timing to try and bodge it in KMS like we did with the legacy graphics stack, but I don't know what they are.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.

aBUGSworstnightmare
Posts: 5389
Joined: Tue Jun 30, 2015 1:35 pm

Re: Bullseye - Comments and bug reports thread.

Mon Nov 08, 2021 5:33 pm

jamesh wrote:
Mon Nov 08, 2021 5:19 pm
CheezPi wrote:
Mon Nov 08, 2021 4:56 pm
jamesh wrote:
Mon Nov 08, 2021 4:50 pm


1366x768 is the PITA one. The HW cannot support it directly, so will revert to the next resolution down, 720p I guess. That may be causing the borders.
So, which settings should I put on config.txt now, may I ask?
I'll have to check. I think there might be some runes which allow the use of a specific set of numbers for timing to try and bodge it in KMS like we did with the legacy graphics stack, but I don't know what they are.
try adding a new mode (1360x768 or 1364x768 pixels (works fine with KMS and Pi4 as well) by following this guide https://askubuntu.com/questions/377937/ ... resolution

Return to “Raspberry Pi OS”