-
Notifications
You must be signed in to change notification settings - Fork 296
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
[Bug]: installation failed on bullseye with make error #335
Comments
See #332 (comment) |
"After further playing around I noticed that the install script wasn't using the source from the git repo to build the module, but what was already present in /lib/modules/. So instead I just did a make, sudo make install and everything sprang back to life." Didn't know what to do... can you give me advice? |
It is as it says, make a fresh clone from my repo (HinTak/seed-voicecard instead of upstream), then type 'make' then "sudo make install" inside, and reboot. |
tried. Sorry. I think I do something wrong. Here is what I do and what I get: pi@raspberrypi:~ $ git clone https://github.com/respeaker/seeed-voicecard |
I said clone my fork, which is https://github.com/HinTak/seeed-voicecard |
Sorry, old man, glasses... you know? ;) Everything works fine now. |
The makefile error happened with HinTak repo |
Doing "sudo make" between clone and "sudo make install" would be useful 😀 |
Thanks for the suggestion, I am going to try a fresh installation. FTR, I tried twice with |
The lxpanel issue is generic to pulsesaudio : https://forums.raspberrypi.com/viewtopic.php?t=295641 and unrelated. |
Hi, now have same problem. After kernel update the mic is not recognized by the pi. Did the same as last time. Error: sudo make gets same error. Tried to use install.sh Error: Deleting module version: 0.3
|
What does "ls -l /lib/modules/6.1.21-v8+/build" says, and does it points at a real place? It says no such file/ directory. You might want to try again? |
The output is: pi@raspberrypi:~ $ ls -l /lib/modules/6.1.21-v8+/build I tried to make the directory but then the error is: pi@raspberrypi:~ $ sudo mkdir /lib/modules/6.1.21-v8+/build What can I do? Please give advice... |
Hier can I solve my Problem? Can anybody help me? |
@bruesche it is not the same problem... but there is a workaround in raspberrypi/firmware#1795 , adding one line in /boot/config.txt |
@bruesche would like to update here that I had the exact same issue. Adding |
FWIW, the initial report and current (since early April) are two different problems. The initial report is simply because upstream seeed studio has stopped updating beyond about 5.13, so won't build against newer kernels. The solution to that is to use one of my v5.x/v6.x branches. (It gets quite messy with a lot of "if kernel version <..." ">=" , so I make new branches when difference is too large for such constructs). The new problem since early April is that raspberrypi people decided that 64-bit kernel on 32-bit system is better than 32-bit kernel on 32-bit system. (Better compiler optimization and resource useage etc). But that specifically does not work for out-of-tree device drivers. They are still working on it - raspberrypi/firmware#1795 - but until they figure it out, you can add one line in/boot/config.txt to go back to a 32-bit kernel on 32-bit system setup. |
Thanks a lot! |
Describe the bug
Do the installation with sudo .install.sh. Refreshed the files from GitHub an get Error:
Reading state information... Done
E: Unable to locate package linux-raspi
E: Unable to locate package linux-headers-raspi
E: Unable to locate package linux-image-raspi
make -j4 KERNELRELEASE=5.15.84-v7l+ -C /lib/modules/5.15.84-v7l+/build M=/var/lib/dkms/seeed-voicecard/0.3/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.15.84-v7l+ (armv7l)
The complet log (install log and Make.log) in the attachment.
The Rhasspy installation didn#t recognized the microphone...
Please help...
Thx
Expected behavior
Installation without errors an a working microphone ;)
Platform
Relevant log output
The text was updated successfully, but these errors were encountered: