Skip to content
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

fix detection of kernel modules on 64-bit image #7

Merged
merged 1 commit into from
Aug 2, 2023

Conversation

hellow554
Copy link

The lib modules folder looks like /lib/modules/6.1.21-v8+/build, which means that the previous regex doesn't capture anything after the - and therefore it fails to detect the kernel version.
The regex now aligns with the other detection method and this works fine on my machine™

The lib modules folder looks like `/lib/modules/6.1.21-v8+/build`, which
means that the previous regex doesn't capture anything after the `-` and
therefore it fails to detect the kernel version.
The regex now aligns with the other detection method and this works fine
on my machine™
@HinTak
Copy link
Owner

HinTak commented Jul 7, 2023

Thanks for working on this. Looking at it, I rather think the correct answer is "^/", don't you think so?

@hellow554
Copy link
Author

hellow554 commented Jul 7, 2023

I just used what's already there ;)
I can change both if you like

@HinTak
Copy link
Owner

HinTak commented Jul 7, 2023

Yes, please (and some minimal testing too...). Thanks a lot.

@HinTak
Copy link
Owner

HinTak commented Jul 7, 2023

Argh, hang on, is this 64-bit kernel on 32-bit userland or 64-bit on 64-bit? The former does not work yet (upstream problem, missing kernel headers). I assume it is the latter as you have gotten it working?

@hellow554
Copy link
Author

64-bit on 64-bit

yes, it was that one.
I got it working after doing this fix ;)

I currently don't have hardware to test on, so that's the best I can do

@uelpenich
Copy link

uelpenich commented Jul 31, 2023

Thanks for working on this. Looking at it, I rather think the correct answer is "^/", don't you think so?

Works for me, please insert this correction into the install.sh

(Debian Bullseye 6.12.1-v8+, 64bit Kernel 64Bit User)

@HinTak HinTak merged commit f25e765 into HinTak:v6.1 Aug 2, 2023
@HinTak
Copy link
Owner

HinTak commented Aug 2, 2023

Thanks for testing. I have merged this but will also put the result of the discussion in after the merge.

@uelpenich
Copy link

Thanks for merging fast.

This is my working configuration:

Hardware: Raspberry Pi 4 with 4GByte memory, ReSpeaker 4 mic array

OS: Raspberry Pi OS with desktop, Image 2023-05-03-raspios-bullseye-arm64.img

Raspberry Pi configuration: Interfaces SSH, VNC, SPI, I2C

PulseAudio issue: due to the Taskbar plugin problem with lxplug-volumepuls I removed it:
refer to https://forums.raspberrypi.com/viewtopic.php?t=293630#p1774697

sudo apt purge lxplug-volumepulse

You may install the Alsa plugin instead:

sudo apt install lxplug-volume

Install seeed-voicecard:

git clone https://github.com/HinTak/seeed-voicecard
cd seeed-voicecard
sudo ./install.sh
sudo reboot

You may use Audacity to show seeed-voicecard working (2 channels only):

sudo apt install audacity -y

Suggestion to @HinTak
Change in Install seeed-voicecard section the line git clone https://github.com/respeaker/seeed-voicecard to git clone https://github.com/HinTak/seeed-voicecard

Thank you for your work

@HinTak
Copy link
Owner

HinTak commented Aug 3, 2023

Thanks. I have updated to URL now (only on the tip, v.6.3/v6.4). The volume control related crash seems to be quite well-known. I read that most just recommend removing the plug-in. Good you have found an answer without removing it completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants