64bit #285
Comments
|
Does it not work? Have you followed the install instructions? |
|
no, it doesn't work, compiling the driver fails |
|
Depends on what kernel versions you are on. If you are on anything other than 5.4/5.5, grep one of the closest number branches from my repo. And click donate when it works... Edit: Afaik raspbian haven't moved onto 5.8 yet (though going to). |
|
Oh, apparently raspbian is going onto v5.10 soon. You need my v5.9 branch for that. |
|
in fact my rasbian is 5.10, how can I install the driver on this kernel? |
|
As I already said, clone my repo, https://github.com/HinTak/seeed-voicecard, use the v5.9 branch (it works with 5.10 too), follows the install instruction. When it works, consider clicking the donate link. |
|
@HinTak I tried to install the 5.9 seeed-voicecard on a Raspberry PI OS 64 bit Kernel 5.10 for the ReSpeaker 4 Mic Array and I am getting this error at the very end, any ideas? DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: Created symlink /etc/systemd/system/sysinit.target.wants/seeed-voicecard.service → /lib/systemd/system/seeed-voicecard.service. Enjoy! |
|
"make.log" shows you either did not read - or did not understand. I wrote 3 times already: you need the v5.9 branch of my repo . The default branch is v5.5, and there is a v5.7 branch, a v4.19 branch, etc. After clone my repo, you need to switch to the v5.9 branch with And I'll write a 3rd time: when it works, consider clicking the donate link. I don't work for seeed studio. |
|
I have just switched the default branch on my repo to v5.9 , since the newest raspbian kernel is 5.10.11 ( I checked myself). It was tagged 20210201 so presumably came out earlier this week. This is the first 5.10.x kernel from raspbian. The last 6 months or so were all v5.4.x . |
|
I did read and understand everything, but when I selected 5.9 I thought github would switch the git link to that version which actually it does not, so I got the wrong versioning. |
|
I guess it is not common knowledge how to switch branch on the web site. If you choose "download tar ball", you do get the branch you choose; but cloning give you the whole repo with every branch, and on your side, it would still show the default branch, until you switch locally. |
|
|
|
@hackebike btw, the 4-mics and 6-mics devices (not the 2-mics @cl84 has) are affected by the crash on the 64-bit OS - see my comment - |
|
@hackebike if you are finding your pi not booting or not being able to use it because of it is crashing, and if you have access to a linux box, you can backtrack and recover by stopping the seeed driver from loading, doing two things (relative to the bottom of the corresponding partitions):
I wrote "access to a linux box" as the 2nd modification can only be done on a linux box. (that partition is not readable by other OSes). The first change is doing-able on other OSes. On linux, two partitions would be auto-mounted under something like "/run/media/yourusername/boot" and "/run/media/yourusername/rootfs" respectively. You need to do both steps, as either would try to load the seeed driver. |
|
thanks for the info, so if I encounter these issues I know what to do. Anyway for now everything looking fine, compilation ok and the tests are ok too. |
|
For a ~$20US (the 4-mics device) or ~$10US (the 2-mics device), understandably after-sale support is limited... but nonetheless, the lack of Seeed Studio staff's mere presence is disappointing. The matrixio device is a bit more expensive but the software code-quality is better. I have had two pulls and haven't heard from their staffer either... you'll need one of my branches for that device too (one of the pulls), if you want to make it work under 5.10. The octo cards are very well-maintained, but they are more for people with more serious sound-processsing use (as in music and hifi), rather than voice-assistant type useage. There is a donate button at https://hintak.github.io if you are feeling generous. |
|
Just wanted to share something else to fix an error. So digging around this command fixed the problem: sudo apt-get -y --reinstall install raspberrypi-kernel I am not familiar with kernel issues, so can't explain why it fixed, maybe you know better. Just wanted to share since others might encounter this issue. This is the kernel version I have: |
|
That's likely a red herring. I think it is a quirk of debian / ubuntu apt system: you need to occasionally do "sudo apt update" to update its knowledge about packages available for upgrading (as opposed to "sudo apt upgrade" which does the actual upgrade). The update is done periodically, once a week, I think, so for very freshly installed system, it may not be knowledgeable about packages available. I just checked the install script - it might be useful to include "apt update" just before install/upgrade. |
|
I have added the fix to install Respeaker Driver for 64 bit Raspbian OS |
|
@WilliamVJacob you missed an "r" in "seed-voicecard" your link, therefore it's broken |
|
@b-mq Thank you so much for letting me know . I have updated the link in the comment |
|
@WilliamVJacob I have had a look at you repo - I think adding "ccflags-y += -fno-stack-protector" is wrong. The other thing is, it is a variation of the --compat-kernel (downgrading kernel) theme... Mostly I am against that, so I have intentionally removed that option in mine: in my opinion the driver code should work with current, and do not require downgrading. (hence I have different branches for what is "current" when raspbian and ubuntu differ) |
|
With the 6 mic array, I was having the same build problem, cloned your repo @HinTak, built and installed. Unfortunately I'm getting Using latest Raspbian kernel, |
|
@Drizzt321 - I have the 6-mic array, and the card works reasonably okay for recording against either 32-bit raspbian or 64-bit ubuntu (I just swap the SD card - same pi + device), the latter unfortunately needing a slightly modified kernel ( https://github.com/HinTak/RaspberryPi-Dev/releases/ ). Do you actually listen to the recorded files? They come out fine despite the occasional I2S SYNC error messages. The I2S SYNC error is generic to a somewhat unhappy sound card (see discussion at raspberrypi/linux#3580 ) and not specific to the respeaker ; and they were there at 4.19.x kernels too, as I wrote in raspberrypi/linux#3580 , so downgrading won't help. #251 is serious but does not affect 32-bit raspbian, so you can stay with that; I don't use my 6-mics often enough to be affected by / or notice anything like #253 . For the occasional recordings I make with the 6-mic array, it works despite some syc error messages. (caveate issue #251 affecting 64-bit raspbian and 32-bit/64-bit ubuntu; for the latter I have a workaround). |
|
@HinTak I'm already using 32-bit Raspbian. Using the 2021-01-11-raspios-buster-armhf-lite.zip image, downloaded from https://www.raspberrypi.org/software/operating-systems/#raspberry-pi-os-32-bit. Unless I'm missing something and turns out that that isn't the proper 32-bit version. I tried it with a 2nd Pi 4, and an old Pi 2, but no luck, same issue. Could it be the ribbon cable somehow has a break somewhere that I can't see? I'm going to try the separate i2c headers on the side of the board next, just in case, but I don't hold out much hope. Any idea what could be wrong? EDIT: Ok, this is interesting. When I use |
|
I have intentionally removed the Edit: you should be able to just use current (5.10, 2021-02-...) without --compat-kernel, using mine. |
|
@HinTak So using your branch with the latest kernel without |
|
@Drizzt321 raspbian has moved to 5.10 in February so The situation after 5.4 is complicated: raspbian moved to 5.10, while ubuntu lts stays at 5.4 (and will do so for another few years) , while ubuntu rolling is on 5.8 at the moment. Hence I have 4 branches. My "v5.5" branch is basically what seeed studio staff merged into the "official" repo. |
|
@HinTak I had the 5.10 kernel, but when I used Unfortunately with your branch, the mic doesn't work for me. Despite the same I2S error, with the official branch and the |
|
@Drizzt321 "doesn't work..." isn't helping... Was there any error messages? If you have simply downgrade rather than wipe / re-install, you can find old syslogs from booting the newer kernels in the past. Look under /var/log/message* . If it is not too large, consider zipping the whole of it and attach here, with "sudo tar -czpvf alllogs.tgz /var/log" |
|
@HinTak The error is the one I gave above in #285 (comment).
And then then the output .wav file from Unfortunately that's the only error I saw in message, dmesg, debug.log. I do have spare mSD cards, so I can pop one in and do a fresh raspbian install and use your branch, or another test one. Is there any kind of debug I could turn on? |
|
@Drizzt321 also a thought - the mixer setting? There is a recording volume there. There were some change in that recently. |
|
@HinTak Hmm...good question. I'll try and find some time tonight/tomorrow to use another mSD and redo from scratch with your branch. Wouldn't it still record seconds of silence though? So wouldn't the .wav file still increase in file size, at a minimum? I'll still give it a try. |
|
There is a "make DEBUG=1" setting for enabling some debug code, but the installation process with that is a bit complicated afterwards, and not useful for somebody who is not sitting in front of the machine... |
|
Yes, I realize arecord dumps from memory on finish so the file size is zero under afterwards. |
|
Stale issue message |
|
@cl84 , Describe the bug To Reproduce
Expected behavior Platform
Relevant log output |
|
Closing the issue due to the lack of activity. |
Hi HinTak, thank you so much for your awesome work! Best wishes, |
|
The 6.5 branch installs and works with the current 64 bit bullseye kernel for raspbian 11 Linux openvpn 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux |
is there any way to install ReSpeaker 2-Mics Pi HAT on 64bit rasbian?
The text was updated successfully, but these errors were encountered: