KillerBerthier
Posts: 39
Joined: Thu May 05, 2016 4:28 pm

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 12:21 pm

Hi,

I installed the ARM64 RPiOS lite from 2021-04-09, but for some reason I cannot open the SPI device. I tried using raspi-config (w/o any error) and manually writing dtparam=spi=on in /boot/config.txt. Both cannot enable the SPI device after reboot (“ls: cannot access '/dev/spi*': No such file or directory”).

Everything works fine with the standard ARM32 RPiOS lite.

Is this a known issue? Am I missing something?

cjclm7
Posts: 14
Joined: Thu Oct 15, 2020 8:15 am

STICKY: Buster bug report thread

Sat May 15, 2021 1:06 pm

No soundcard on Pi 400 running 64bit raspbian?

Code: Select all

aplay -l
aplay: device_list:272: no soundcards found...

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

Code: Select all

uname -a
Linux pi4tor 5.10.33-v7l+ #1415 SMP Fri Apr 30 15:50:57 BST 2021 armv7l GNU/Linux

Code: Select all

uname -m
armv7l

User avatar
pasdechance
Posts: 87
Joined: Mon Nov 30, 2020 7:27 pm
Location: France
Contact: Website

Re: STICKY: Buster bug report thread

Sat May 15, 2021 1:23 pm

cjclm7 wrote:
Sat May 15, 2021 1:06 pm
No soundcard on Pi 400 running 64bit raspbian?

Code: Select all

aplay -l
aplay: device_list:272: no soundcards found...

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

Code: Select all

uname -a
Linux pi4tor 5.10.33-v7l+ #1415 SMP Fri Apr 30 15:50:57 BST 2021 armv7l GNU/Linux

Code: Select all

uname -m
armv7l
Just to confirm, what is your pi attached to? Monitor with speakers? USB DAC? BT?

I also use the 64-bit version on my Pi400 and haven't had sound issues.

You can also try this

Code: Select all

sudo apt update
sudo apt full-upgrade

Code: Select all

sudo apt purge bluealsa
sudo apt install pulseaudio-module-bluetooth
Now reboot.

To swap over the volume and input selector on the taskbar from ALSA to PulseAudio, after your Raspberry Pi has restarted, right-click a blank area on the taskbar and choose Add / Remove Panel Items. Find the plugin labelled Volume Control (ALSA/BT) in the list, select it and click Remove; then click the Add button, find the plugin labelled Volume Control (PulseAudio) and click Add. Alternatively, just open the Appearance Settings application from the Preferences section of the Main Menu, go to the Defaults tab and press one of the Set Defaults buttons.

Once you have updated, execute the following in a terminal window, which should fix this:

Code: Select all

rm ~/.asoundrc
To remove the old Audio Preferences application, which will not work with PulseAudio, do:

Code: Select all

sudo apt purge pimixer

Code: Select all

sudo apt update
sudo apt full-upgrade
reboot
pasdechance
English/French
Debian, Raspberry Pi OS 64-bit Beta, LibreElec

cjclm7
Posts: 14
Joined: Thu Oct 15, 2020 8:15 am

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 1:55 pm

pasdechance,

many, many thanks for your help. I have followed (very carefully) all your steps but still no sound output.

My Pi 400 is connected through HDMI to a Samsung TV Q70 Series. All is working fine with video (4k output at 60Hz) but no sound.

I am fully available to give information about my configuration. Here some outputs from the terminal (feel free to ask others):

I get no sound output from:
aplay /usr/share/sounds/alsa/Front_Center.wav

Output from uname -m: armv7l
Output from uname -a: Linux pi4 5.10.17-v7l+ #1414 SMP Fri Apr 30 13:20:47 BST 2021 armv7l GNU/Linux
Output from aplay -l: aplay: device_list:272: no soundcards found...

Code: Select all

inxi -A
Audio:     Device-1: bcm2711-hdmi0 driver: N/A 
           Device-2: bcm2711-hdmi1 driver: N/A

User avatar
pasdechance
Posts: 87
Joined: Mon Nov 30, 2020 7:27 pm
Location: France
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:18 pm

I tried ¯\_ (ツ) _/¯

Have you bothered changing which HDMI out you are using? Or using a different HDMI cable? I know, that should not be an issue due to the error, but someone is bound to ask later.

If you go through the raspi-config and set the audio does it change anything? What is everything set to in alsamixer?
pasdechance
English/French
Debian, Raspberry Pi OS 64-bit Beta, LibreElec

User avatar
pasdechance
Posts: 87
Joined: Mon Nov 30, 2020 7:27 pm
Location: France
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:22 pm

And do you have pavucontrol installed?
pasdechance
English/French
Debian, Raspberry Pi OS 64-bit Beta, LibreElec

fruitoftheloom
Posts: 26841
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:27 pm

pasdechance wrote:
Sat May 15, 2021 2:22 pm
And do you have pavucontrol installed?

cjclm7 is not running RaspiOS64, see his other trillion posts.............................
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

cjclm7
Posts: 14
Joined: Thu Oct 15, 2020 8:15 am

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:28 pm

yes, I have tried !

The HDMI cable has no issues. Video through the HDMI is 4k @ 60Hz, only issue was the sound through HDMI.

Anyway, other changes tried after your post: added arm_64bit=1 and dtparam=audio=on to /boot/config.txt and i am getting different outputs on previous commands:

Code: Select all

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 8/8

Code: Select all

inxi -A
Audio:     Device-1: bcm2835-audio driver: bcm2835_audio 
           Device-2: bcm2711-hdmi0 driver: N/A 
           Device-3: bcm2711-hdmi1 driver: N/A 
           Sound Server: ALSA v: k5.10.17-v8+
and now the sound is working fine through HDMI

cjclm7
Posts: 14
Joined: Thu Oct 15, 2020 8:15 am

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:31 pm

fruitoftheloom wrote:
Sat May 15, 2021 2:27 pm

cjclm7 is not running RaspiOS64, see his other trillion posts.............................

Code: Select all

uname -m
aarch64
yes "fruitoftheloom", I am running RaspiOS64... and your aggressive attitude is unnecessary.... sorry we have disturbed you

fruitoftheloom
Posts: 26841
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:37 pm

cjclm7 wrote:
yes "fruitoftheloom", I am running RaspiOS64... and your aggressive attitude is unnecessary.... sorry we have disturbed you

Raspbian is 32bit userland not 64bit userland as explained in the other post, all you have undertaken is to enable a 64bit kernel :?
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 13973
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:41 pm

cjclm7 wrote:
Sat May 15, 2021 2:31 pm
fruitoftheloom wrote:
Sat May 15, 2021 2:27 pm

cjclm7 is not running RaspiOS64, see his other trillion posts.............................

Code: Select all

uname -m
aarch64
yes "fruitoftheloom", I am running RaspiOS64... and your aggressive attitude is unnecessary.... sorry we have disturbed you
Then do you know that the 64-bit Raspios is still in BETA? errors you encounter MUST be posted in the 64-bit feedback thread.

And stop spamming all over this forum, any more copies will be deleted and you will get some time off from this forum!!!

you should try the regular 32-bit version first!

there recently have been big changes in how sound operates in RaspiOS (32-bit) (see https://www.raspberrypi.org/blog/new-ra ... mber-2020/ ) so there are plenty of posts from people who have experienced sound problems, also the RPI400 does NOT have Analog sound outputs!

fruitoftheloom
Posts: 26841
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:49 pm

mahjongg wrote:
Sat May 15, 2021 2:41 pm
cjclm7 wrote:
Sat May 15, 2021 2:31 pm
fruitoftheloom wrote:
Sat May 15, 2021 2:27 pm

cjclm7 is not running RaspiOS64, see his other trillion posts.............................

Code: Select all

uname -m
aarch64
yes "fruitoftheloom", I am running RaspiOS64... and your aggressive attitude is unnecessary.... sorry we have disturbed you
Then do you know that the 64-bit Raspios is still in BETA? errors you encounter MUST be posted in the 64-bit feedback thread.

And stop spamming all over this forum, any more copies will be deleted and you will get some time off from this forum!!!

you should try the regular 32-bit version first!

there recently have been big changes in how sound operates in RaspiOS (32-bit) (see https://www.raspberrypi.org/blog/new-ra ... mber-2020/ ) so there are plenty of posts from people who have experienced sound problems, also the RPI400 does NOT have Analog sound outputs!

Mahjong he is running Raspbian RaspiOS 32bit with 64bit kernel, not a full blown RaspiOS64 Beta OS.
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

User avatar
pasdechance
Posts: 87
Joined: Mon Nov 30, 2020 7:27 pm
Location: France
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sat May 15, 2021 2:52 pm

fruitoftheloom wrote:
Sat May 15, 2021 2:27 pm
pasdechance wrote:
Sat May 15, 2021 2:22 pm
And do you have pavucontrol installed?

cjclm7 is not running RaspiOS64, see his other trillion posts.............................
Ah, I see that now.

cjclm7, I think you could reinstall the official OS (the one you download from the main site) or try the 64-bit image (that you can find at the top of this thread). Once installed do full-upgrade. Sometimes starting from scratch is easier than looking for the source of the problem in terms of time and effort spent. I had no problems with the official image or the 64-bit beta when it comes to sound. As noted by the others, the 64-bit image is currently beta. The official image should work out of the box unless there is something wrong with one of your cables or other hardware.
pasdechance
English/French
Debian, Raspberry Pi OS 64-bit Beta, LibreElec

User avatar
clicky
Posts: 535
Joined: Thu Oct 25, 2012 7:34 am

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Sun May 16, 2021 1:48 pm

Quick question or two (and apologies if it is well known fact - I did put some effort in trying to figure it out + find any resources here or elsewhere):

wiringpi's /usr/bin/gpio doesn't work for me on

Code: Select all

Linux desktop-pi.thenet 5.10.33-v8+ #1415 SMP PREEMPT Fri Apr 30 15:53:26 BST 2021 aarch64 GNU/Linux
So, questions are:
- is it me just me?
- or is there a fix/workaround, etc?
- is it well known fact it won't
- or is it not yet sorted/ported?

BTW by 'not working' I mean 'gpio' command doesn't change state of the pins. Using python or /sys/class/gpio works perfectly fine...

cl.ement05
Posts: 11
Joined: Mon Nov 23, 2020 8:39 am

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 17, 2021 3:25 pm

Are there any changelogs for https://downloads.raspberrypi.org/raspi ... 021-04-09/ march update ??

When are these images expected to become stable ?

User avatar
davidcoton
Posts: 6256
Joined: Mon Sep 01, 2014 2:37 pm
Location: Cambridge, UK
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 17, 2021 3:46 pm

cl.ement05 wrote:
Mon May 17, 2021 3:25 pm
When are these images expected to become stable ?
The standard answer is "when they are ready".
I would not expect a full release until Bullseye stable is out and integrated,
but then RPiOS32-Buster was launched before Debian Buster was stable.
Location: 345th cell on the right of the 210th row of L2 cache

User avatar
bensimmo
Posts: 5330
Joined: Sun Dec 28, 2014 3:02 pm
Location: East Yorkshire

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 17, 2021 5:51 pm

cl.ement05 wrote:
Mon May 17, 2021 3:25 pm
Are there any changelogs for https://downloads.raspberrypi.org/raspi ... 021-04-09/ march update ??

When are these images expected to become stable ?
Probably the same as the 32 version
https://downloads.raspberrypi.org/raspi ... _notes.txt
It mentions 64 bit.
Though it might not be everything.

User avatar
davidcoton
Posts: 6256
Joined: Mon Sep 01, 2014 2:37 pm
Location: Cambridge, UK
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Tue May 18, 2021 3:46 pm

During sudo apt full-upgrade today, on a Pi4B 4GB, RPiOS-64 neither Bluetooth not WiFi are in use:

Code: Select all

Unpacking pi-bluetooth (0.1.16) over (0.1.15) ...
Setting up pi-bluetooth (0.1.16) ...
Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.
Job for hciuart.service failed because the control process exited with error code.

Code: Select all

pi@rpi4B4:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2021-05-18 16:38:13 BST; 2min 20s ago
  Process: 15693 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

May 18 16:37:43 rpi4B4 systemd[1]: Starting Configure Bluetooth Modems connected by UART...
May 18 16:38:13 rpi4B4 btuart[15693]: Initialization timed out.
May 18 16:38:13 rpi4B4 btuart[15693]: bcm43xx_init
May 18 16:38:13 rpi4B4 systemd[1]: hciuart.service: Control process exited, code=exited, status=1/F
May 18 16:38:13 rpi4B4 systemd[1]: hciuart.service: Failed with result 'exit-code'.
May 18 16:38:13 rpi4B4 systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.

Code: Select all

pi@rpi4B4:~ $ journalctl -xe
-- Subject: A start job for unit hciuart.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit hciuart.service has finished with a failure.
-- 
-- The job identifier is 3004 and the job result is failed.
May 18 16:38:14 rpi4B4 sudo[15438]: pam_unix(sudo:session): session closed for user root
May 18 16:43:17 rpi4B4 PackageKit[15409]: daemon quit
May 18 16:43:17 rpi4B4 systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit packagekit.service has exited.
-- 
-- The process' exit code is 'killed' and its exit status is 15.
May 18 16:43:17 rpi4B4 systemd[1]: packagekit.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit packagekit.service has successfully entered the 'dead' state.
Location: 345th cell on the right of the 210th row of L2 cache

fruitoftheloom
Posts: 26841
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Tue May 18, 2021 4:22 pm

davidcoton wrote:
Tue May 18, 2021 3:46 pm
During sudo apt full-upgrade today, on a Pi4B 4GB, RPiOS-64 neither Bluetooth not WiFi are in use:

Code: Select all

Unpacking pi-bluetooth (0.1.16) over (0.1.15) ...
Setting up pi-bluetooth (0.1.16) ...
Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.
Job for hciuart.service failed because the control process exited with error code.

Code: Select all

pi@rpi4B4:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2021-05-18 16:38:13 BST; 2min 20s ago
  Process: 15693 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

May 18 16:37:43 rpi4B4 systemd[1]: Starting Configure Bluetooth Modems connected by UART...
May 18 16:38:13 rpi4B4 btuart[15693]: Initialization timed out.
May 18 16:38:13 rpi4B4 btuart[15693]: bcm43xx_init
May 18 16:38:13 rpi4B4 systemd[1]: hciuart.service: Control process exited, code=exited, status=1/F
May 18 16:38:13 rpi4B4 systemd[1]: hciuart.service: Failed with result 'exit-code'.
May 18 16:38:13 rpi4B4 systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.

Code: Select all

pi@rpi4B4:~ $ journalctl -xe
-- Subject: A start job for unit hciuart.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit hciuart.service has finished with a failure.
-- 
-- The job identifier is 3004 and the job result is failed.
May 18 16:38:14 rpi4B4 sudo[15438]: pam_unix(sudo:session): session closed for user root
May 18 16:43:17 rpi4B4 PackageKit[15409]: daemon quit
May 18 16:43:17 rpi4B4 systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit packagekit.service has exited.
-- 
-- The process' exit code is 'killed' and its exit status is 15.
May 18 16:43:17 rpi4B4 systemd[1]: packagekit.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit packagekit.service has successfully entered the 'dead' state.

I lost Bluetooth completely with full-upgrade relating to pi-bluetooth package update, but rebooting restored without further issues ;)
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

User avatar
boyinhell
Posts: 8
Joined: Sat Mar 25, 2017 2:26 am
Location: Singapore
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Wed May 19, 2021 7:32 am

same here. hciuart.service stopped working after upgrade. Reboot fix it.
Building memories...

User avatar
boyinhell
Posts: 8
Joined: Sat Mar 25, 2017 2:26 am
Location: Singapore
Contact: Website

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Wed May 19, 2021 7:34 am

Is there any timeline about 64bit official launch? It's been beta for more than a year..
Building memories...

fruitoftheloom
Posts: 26841
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Wed May 19, 2021 8:13 am

boyinhell wrote:
Wed May 19, 2021 7:34 am
Is there any timeline about 64bit official launch? It's been beta for more than a year..

Ask and answered several times, latest:

viewtopic.php?f=63&t=275372&start=775#p1866154
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

SMH17
Posts: 9
Joined: Tue Aug 25, 2020 9:16 pm

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 24, 2021 8:07 pm

Is the issue list updated?
Known issues
1) There is no hardware video acceleration in VLC or Chromium
2) libraspberrypi0, libraspberrypi-dev and libraspberrypi-doc have been moved out of /opt/vc/* and into /usr/* instead (making it more standard). Any code built against these libraries will require changing to refer to a more standard location (/usr/lib/ rather than /opt/vc/lib)
3) Due to 2) Many packages that expect libGLESv2.so libEGL etc will require rebuilding.
4) raspberrypi-bootloader and raspberrypi-kernel contain useless non-64bit binaries and is missing the work done to minimise the delay between files being deleted and installed to /boot
5) There is no Wolfram Mathematica built for AArch64
6) Minecraft shim layer requires rebuilding to cope with 2)
7) VLC needs rebuild (not available)
8) VNC server not rebuilt yet for 64bit
I have tried Raspberry Pi OS 64 nearly a year ago and issue list seems about the same. :cry:

tibbe
Posts: 19
Joined: Mon Dec 07, 2020 6:19 pm

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 24, 2021 8:41 pm

Any downsides to just running ubuntu 64-bit?

SMH17
Posts: 9
Joined: Tue Aug 25, 2020 9:16 pm

Re: STICKY: Raspberry Pi OS (64 bit) beta test version feedback

Mon May 24, 2021 9:18 pm

tibbe wrote:
Mon May 24, 2021 8:41 pm
Any downsides to just running ubuntu 64-bit?
Ubuntu is bloated and not optimized around Raspberry as RaspiOs. It's a pity the 64 bit version is still a not fully working beta.

Return to “General discussion”