Allo Piano, Allo Kali incompatibility with the official Raspberry Pi kernel 6.6.56 or newer

Help and Support
21

Hey @Zhapox,

Great information. Can you also attach output from dmesg please?

Kind Regards,

22

@nerd Sure! There you go:

dmesg.txt (38.0 KB)

23

Hey @Zhapox,

Can you get:

  1. dmseg 2-5 min after reboot
  2. sudo lsmod
  3. sudo cat /proc/modules

Kind Regards,

24

Hi @nerd ,
sure, here you go:

modules.txt (3.6 KB)
lsmod.txt (3.3 KB)
dmesg_5min_after_rb.txt (24.8 KB)

Edit:
After a longer while below messages occur again in dmesg (following what’s contained in above upload):

[  243.671694] INFO: task alsactl:517 blocked for more than 122 seconds.
[  243.671719]       Tainted: G         C         6.6.56-v7+ #1803
[  243.671724] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  243.671729] task:alsactl         state:D stack:0     pid:517   ppid:1      flags:0x00800001
[  243.671750]  __schedule from schedule+0x54/0xe8
[  243.671774]  schedule from schedule_preempt_disabled+0x14/0x18
[  243.671791]  schedule_preempt_disabled from rwsem_down_read_slowpath+0x220/0x48c
[  243.671809]  rwsem_down_read_slowpath from down_read+0x50/0x100
[  243.671827]  down_read from snd_soc_card_get_kcontrol+0x24/0x7c [snd_soc_core]
[  243.671996]  snd_soc_card_get_kcontrol [snd_soc_core] from snd_soc_limit_volume+0x2c/0x5c [snd_soc_core]
[  243.672219]  snd_soc_limit_volume [snd_soc_core] from pcm512x_set_reg_master+0x108/0x124 [snd_soc_allo_piano_dac_plus]
[  243.672351]  pcm512x_set_reg_master [snd_soc_allo_piano_dac_plus] from snd_ctl_ioctl+0x200/0x9b4 [snd]
[  243.672426]  snd_ctl_ioctl [snd] from sys_ioctl+0x110/0xa20
[  243.672490]  sys_ioctl from __sys_trace_return+0x0/0x10
[  243.672505] Exception stack(0xb8ab9fa8 to 0xb8ab9ff0)
[  243.672514] 9fa0:                   7efeaf4c 00ddad68 00000003 c2c85513 00de3d10 00de3668
[  243.672522] 9fc0: 7efeaf4c 00ddad68 00033aa8 00000036 00000002 00000000 00000000 00000002
[  243.672529] 9fe0: 76f32818 7efea7dc 76e8908c 76d15e3c
[  243.672544] INFO: task alsactl:629 blocked for more than 122 seconds.
[  243.672550]       Tainted: G         C         6.6.56-v7+ #1803
[  243.672555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  243.672560] task:alsactl         state:D stack:0     pid:629   ppid:1      flags:0x00000000
[  243.672572]  __schedule from schedule+0x54/0xe8
[  243.672588]  schedule from schedule_preempt_disabled+0x14/0x18
[  243.672604]  schedule_preempt_disabled from rwsem_down_write_slowpath+0x270/0x670
[  243.672622]  rwsem_down_write_slowpath from down_write+0x58/0x5c
[  243.672640]  down_write from snd_ctl_release+0x5c/0xe8 [snd]
[  243.672701]  snd_ctl_release [snd] from __fput+0xd8/0x288
[  243.672759]  __fput from sys_close+0x30/0x64
[  243.672773]  sys_close from ret_fast_syscall+0x0/0x4c
[  243.672786] Exception stack(0xb8aadfa8 to 0xb8aadff0)
[  243.672794] dfa0:                   7e9aebbc 00033aa8 00000004 81785501 7e9aea0c 00000000
[  243.672803] dfc0: 7e9aebbc 00033aa8 00000004 00000006 0002155c 00021f70 00021650 000341f8
[  243.672810] dfe0: 76eece8c 7e9ae9f8 76e38ee0 76d5f2f0
[  243.672816] INFO: task alsactl:632 blocked for more than 122 seconds.
[  243.672822]       Tainted: G         C         6.6.56-v7+ #1803
[  243.672826] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  243.672830] task:alsactl         state:D stack:0     pid:632   ppid:1      flags:0x00000000
[  243.672841]  __schedule from schedule+0x54/0xe8
[  243.672857]  schedule from schedule_preempt_disabled+0x14/0x18
[  243.672872]  schedule_preempt_disabled from rwsem_down_write_slowpath+0x270/0x670
[  243.672890]  rwsem_down_write_slowpath from down_write+0x58/0x5c
[  243.672907]  down_write from snd_ctl_release+0x5c/0xe8 [snd]
[  243.672968]  snd_ctl_release [snd] from __fput+0xd8/0x288
[  243.673024]  __fput from sys_close+0x30/0x64
[  243.673037]  sys_close from ret_fast_syscall+0x0/0x4c
[  243.673050] Exception stack(0xb8ab1fa8 to 0xb8ab1ff0)
[  243.673058] 1fa0:                   7eff7bdc 00033aa8 00000003 81785501 7eff7a2c 00000000
[  243.673067] 1fc0: 7eff7bdc 00033aa8 00000003 00000006 0002155c 00021f70 00021650 000341f8
[  243.673073] 1fe0: 76f5de8c 7eff7a18 76ea9ee0 76dd02f0
[  243.673105] INFO: task aplay:1105 blocked for more than 122 seconds.
[  243.673111]       Tainted: G         C         6.6.56-v7+ #1803
[  243.673116] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  243.673120] task:aplay           state:D stack:0     pid:1105  ppid:1104   flags:0x00000000
[  243.673131]  __schedule from schedule+0x54/0xe8
[  243.673146]  schedule from schedule_preempt_disabled+0x14/0x18
[  243.673162]  schedule_preempt_disabled from rwsem_down_write_slowpath+0x270/0x670
[  243.673180]  rwsem_down_write_slowpath from down_write+0x58/0x5c
[  243.673198]  down_write from snd_ctl_release+0x5c/0xe8 [snd]
[  243.673258]  snd_ctl_release [snd] from __fput+0xd8/0x288
[  243.673314]  __fput from sys_close+0x30/0x64
[  243.673327]  sys_close from ret_fast_syscall+0x0/0x4c
[  243.673341] Exception stack(0xb8cc9fa8 to 0xb8cc9ff0)
[  243.673349] 9fa0:                   7e825374 0002ec20 00000003 81785501 7e8251c4 00000000
[  243.673357] 9fc0: 7e825374 0002ec20 00000003 00000006 0002f050 0002f040 7e8253d0 7e8256cc
[  243.673364] 9fe0: 76f2ae8c 7e8251b0 76e76ee0 76d9d2f0
25

Hey @Zhapox,

Interesting. The dynamic overlay loader complained about module insertion method, followed by kernel taint. After reboot - “happy dodo”.

Right, few extra checks:

  1. sudo cat /proc/asound/cards
  2. sudo cat /sys/kernel/debug/tracing/trace | grep i2c-1

Content of:

  1. /boot/config.txt
  2. /boot/volumioconfig.txt
  3. /boot/userconfig.txt

Kind Regards,

26

Been using Volumio for 10 years now, only had some minor problems in those years, but the last 4 years I just enjoyed music and never had any issues (that couldn’t be fixed with a newly flashed SD). Untill now, the most recent release. SD Card completely bricked after updating.

Too bad, had been in there for > 2 years, so just flashed a new one with the image, it just won’t work! First start up you’ll see a Volumio screen (I have a built in display), then some more stuff is loaded and the screen freezes/pauses. Then you go to the IP address and see 7 steps to set it up. Language, myVolumio login, Wifi (why, if I may ask?? >> because I don’t select any, I’m on LAN), i2s DAC etc.

But every time (I’ve flashed 3 new SD cards this week!) you can’t get to the last step, the screen freezes, gets a grey overlay and a Volumio logo just turning round and round, as if it’s busy (not).

Who killed this great software? And more importantly: where can I find older versions?

27

Hey @Monoposto013,

I think I am not discovering a wheel by stating that help is as accurate as problem description in details.

Please share details of the screen.

Please share details of the I2S DAC. I must confess - this is the first DAC using I2S ever mentioned, most of the users will choose I2C. Unless this is a typo.

Please describe or detail all connected “etc”.

What would also help, is the debug log:

How would you otherwise complete an initial setup of new installation? I think that the setup screen is guiding through the minimum for the player to function. Personally - I disagree, so do hundreds of users.

Kind Regards,

28

The Raspberry pi 7" screen is working, touch display, nice colors, don’t worry. Has nothing to do with Volumio not responding or getting from a perfectly working setup to not accepting a newly flashed sd.

To read more about i2s: https://volumio.com/raspberry-pi-i2s-dac-sounds-so-good/

I’ve got an Allo Piano 2.1.

The etc. are the remaining steps in setup, I mentioned 4, so I don’t know the other 2 or 3, screen freezes before I get to them. Developers will know the remaining steps. :man_shrugging:

There is no debug log, because there is no working Volumio. :wink:

There may be a couple of 100’s of users relying on Wifi, I personally don’t. I don’t use Wifi for my streaming, so I don’t want to enter credentials in the setup. And I don’t get why there’s no option to select LAN and dismiss Wifi. So in my opinion, Wifi certainly is not qualifying to be in the “minimum for the player to function”. :sweat_smile:

I can’t find older/working Volumio images, where to look for them?
Thanks! Regards,

29

there is a know issue for Allo Piano on the latest version 3.779, currently under investigation

2 Likes
30

Hey @Monoposto013,

Thank you for the details.

Merging with the Piano 2.1 thread,

Kind Regards,

1 Like
31

Hi @nerd ,
as you wished:
sudo cat /proc/asound/cards
cards.txt (274 Bytes)

sudo cat /sys/kernel/debug/tracing/trace | grep i2c-1
Empty response

/boot/config.txt
config.txt (364 Bytes)

/boot/volumioconfig.txt
volumioconfig.txt (366 Bytes)

/boot/userconfig.txt
userconfig.txt (90 Bytes)

32

Hey @Zhapox,

There is no clock association in the dtoverlay’s source code. It seems it has been removed between kernels 5.x and 6.x.

Let’s test this further and enable explicit i2s handling:

Add to the /boot/userconfig.txt

dtparam=i2s=on

Please capture dmesg again.

Kind Regards,

1 Like
33

Thanks man!

Are there (from official source) older Volumio releases available? So I can play some music…

Much appreciated,

34

Hey @Monoposto013,

Unless @Darmur has some aces under his sleeves - this is the previous stable release:

Version Link
v3.757 Direct Download

Kind Regards,

1 Like
35

Hi @nerd ,

I did what you suggested and rebooted (cli shutdown, power off, power on). The Web interface still doesn’t seem to come up and dmesg still indicates issues. Please see below:

volumio@volumio:~$ ls -l /boot/userconfig.txt
-rw-rw-rw- 1 root root 105 Nov 22 16:36 /boot/userconfig.txt
volumio@volumio:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
dtparam=i2s=on

dmesg_5min_after_rb_2.txt (29.7 KB)

36

Hey @Zhapox,

Comment out the dtoverlay line in config.txt and reboot, then run the following:

sudo udevadm monitor -p > udev.txt &
sudo dtoverlay allo-piano-dac-plus-pcm512x-audio

You can then halt the udevadm using fg and Ctrl-C and post the content of udev.txt.

Also post the output of lsmod.

Kind Regards,

37

Hi @nerd ,

Here is your order:

lsmod_2.txt (3.3 KB)
udev.txt (8.3 KB)

38

Dear Volumionauts,

It seems we have kernel regression.

	default:
		snd_soc_component_write(asoc_rtd_to_codec(rtd, 0)->component,
				PCM512x_MUTE, P_DAC_UNMUTE);
		snd_soc_component_write(asoc_rtd_to_codec(rtd, 1)->component,
				PCM512x_MUTE, P_DAC_UNMUTE);
	}

expected:

	default:
		snd_soc_component_write(snd_soc_rtd_to_codec(rtd, 0)->component,
				PCM512x_MUTE, P_DAC_UNMUTE);
		snd_soc_component_write(snd_soc_rtd_to_codec(rtd, 1)->component,
				PCM512x_MUTE, P_DAC_UNMUTE);
	}

I am not sure how I can help further without access to the actual board itself.

Will check internally if any of our devs can assist further.

Kind Regards,

39

Hi @nerd ,

Thanks for the update. If you need any further tests/logs don’t hesitate to ping me.

Best regards,
Kevin

1 Like
40

Maybe don’t do any updates once it’s working (the old saying, if it’s not broken don’t fix it). Doesn’t seem to be any quality of life benefits from any of the updates for a year or so.

It’s much easier doing away with hats to be honest, rpi4 and UBC is much neater and would sound just as good.