-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with latest release for RPi4 #49
Comments
I have the same problem and the same error number -517 pi@sound1:~ $ uname -a pi@sound1:~ $ dmesg |
has anyone solved this??? |
Well, I've got nonworking audio card on my hands :/ Has anyone solved it, indeed? |
Having just ran in to this problem again and feeling like I had solved it once before, I was pleasantly surprised to find that is the case. See: https://community.blokas.io/t/modep-no-longer-running-following-rpi-update/1115/11 In general, there seems to be some trouble that was introduced to newer kernels that causes trouble for the octo. I have not bisected the kernel updates to locate where the problem was introduced. Based on my last post, we could revert to a working kernel with: I find that now causes trouble, perhaps because the old hexxeh git is deprecated and rpi-update was ported to a new repository. We can take a different approach; see: https://github.com/HinTak/RaspberryPi-Dev/blob/master/Downgrading-Pi-Kernel.md For this most recent problem, I decided to revert to kernel 4.19.118-v7+ To do this:
After a reboot, I see that I am on the new (old) kernel:
After setting up the octo (I have a script I'm working on which I think works better than the octo setup deb, will get that onto github soon) and rebooting, I can confirm I have the octo working, without the errors in dmesg:
I'll work to get something set up for bisecting kernels to test where the problem was introduced soon |
Note, once you are on a working kernel version, make SURE you put the raspberrypi-bootloader raspberrypi-kernel raspberrypi-kernel-headers packages on hold, otherwise an apt-get update or a raspi-update will re-break your stuff. |
Thank you for solving this. I look forward to trying it. Please send any
scripts you develop to me by email as well.
Thanks,
Chris
…On Wed, Jan 11, 2023 at 11:35 PM William Hofferbert < ***@***.***> wrote:
Having just ran in to this problem *again* and feeling like I had solved
it once before, I was pleasantly surprised to find that is the case. See:
https://community.blokas.io/t/modep-no-longer-running-following-rpi-update/1115/11
In general, there seems to be some trouble that was introduced to newer
kernels that causes trouble for the octo. I have not bisected the kernel
updates to locate where the problem was introduced.
Based on my last post, we could revert to a working kernel with:
sudo rpi-update a08ece3d48c3c40bf1b501772af9933249c11c5b
I find that now causes trouble, perhaps because the old hexxeh git is
deprecated and rpi-update was ported to a new repository.
We can take a different approach; see:
https://github.com/HinTak/RaspberryPi-Dev/blob/master/Downgrading-Pi-Kernel.md
For this most recent problem, I decided to revert to kernel 4.19.118-v7+
To do this:
wget -O kernel-headers_armhf.deb
http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-firmware/raspberrypi-kernel-headers_1.20200601-1_armhf.deb
wget -O kernel_armhf.deb
http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-firmware/raspberrypi-kernel_1.20200601-1_armhf.deb
sudo dpkg -i kernel-headers_armhf.deb kernel_armhf.deb sudo apt-mark hold
raspberrypi-bootloader raspberrypi-kernel raspberrypi-kernel-headers
After a reboot, I see that I am on the new (old) kernel:
***@***.***:~ $ uname -a Linux patchbox 4.19.118-v7+ #1311 SMP Mon Apr
27 14:21:24 BST 2020 armv7l GNU/Linux ***@***.***:~ $
After setting up the octo (I have a script I'm working on which I think
works better than the octo setup deb, will get that onto github soon) and
rebooting, I can confirm I have the octo working, without the errors in
dmesg:
***@***.***:~ $ aplay -l **** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM
vc4-hdmi-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1:
audioinjectoroc [audioinjector-octo-soundcard], device 0: AudioInject-HIFI
cs42448-0 [AudioInject-HIFI cs42448-0] Subdevices: 1/1 Subdevice #0:
subdevice #0 ***@***.***:~ $
I'll work to get something set up for bisecting kernels to test where the
problem was introduced soon
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYIU7C3LBCHPDVRB7T3HL3WR6CZNANCNFSM5FTD2KOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I added the script and some better formatted instructions similar to the prior comment here on github: https://github.com/whofferbert/audioinjector-octo-setup The script there might help get the octo set up better than the .deb file (I've always had problems with that installer) Let me know how it goes, hope you can all get your systems back in to a working state. |
Downgrading the kernel fixed my problem (#61) on my RPi3B and CM4 which were originally using the latest kernel version (v6). |
I just installed the 2021/05/07 release of "Raspberry Pi OS with desktop and recommended software" from https://downloads.raspberrypi.org/raspios_full_armhf/images/raspios_full_armhf-2021-05-28/2021-05-07-raspios-buster-armhf-full.zip
I then did a full apt-get update/upgrade dance.
Finally, I followed the "Easy Automatic Setup".
On reboot, I see errors in the dmesg:
Any ideas? I can probe pins with my scope if you want.
I have another board if you think this is a dead board, but I'd really rather not put it into use if it's an RPi4 config problem that's killing them.
Thanks.
The text was updated successfully, but these errors were encountered: