forked from respeaker/seeed-voicecard
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Kernel Panic trying to test with arecord #22
Comments
Same issue here. Dmesg shows this:
|
same here removing |
same issue... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using the Seeed Respeaker 4 mic hat: https://files.seeedstudio.com/wiki/ReSpeaker-4-Mic-Array-for-Raspberry-Pi/img/connect2.jpg
The SD card died in my Pi3b voice assistant so I thought I'd try and upgrade it to a Pi4 I was using elsewhere.
Flash latest official Pi Lite version to SD card:
git clone https://github.com/HinTak/seeed-voicecard.git
The default branch is v6.1 so good to go there.
sudo ./install.sh and reboot
After reboot:
arecord -L
Try and record as per the instructions on the wiki:
Kernel Panic when pressing Ctrl+C to stop recording
Seems to be 100% repro rate
I tried using the linked (super old) version of Buster with the drivers pre-installed (https://files.seeedstudio.com/linux/Raspberry%20Pi%204%20reSpeaker/2021-05-07-raspios-buster-armhf-lite-respeaker.img.xz)
That works correctly and I can record, sox to stereo and playback via headphones as expected, so it's not a hardware issue with the hat.
I tried using 32 bit instead of 64 bit, bit that doesn't seem to install correctly,
cannot get card index for seeed4micvoicec
when trying to record.I also tried 64 bit full desktop RPi image in case somehow that was using a different kernel, but no luck there.
It seems lots of people are working OK with 6.1 kernels from various forums around the place, so I am really not sure what is going wrong in my case.
(I did also try the hat on the PI3b with latest Pi OS and that also failed, so it's not specific to the 4)
Any help would be greatly appreciated (via donation!)
The text was updated successfully, but these errors were encountered: