Install on other OS (libreelec/kodi, volumio etc.) #268
Comments
|
The current code has dropped older kernel (4.19) support, I think, and also too much bash-isms. Busybox's emulation of bash isn't up for it, I think. And I have never agreed with the whole check disk space and downgrade kernel thing , so you may have better luck with https://github.com/HinTak/seeed-voicecard . That said, it should be possible to rollback and get 4.19 support back again. (revert commits marked "v5.x" etc) . You probably want to follow some of the raspberrypi dev tips I wrote in the raspberrypi-dev repo. See https://hintak.github.io . |
|
I don't agree with the whole downgrade kernel thing which "Warning: /boot volume" is for. |
|
@HinTak thank you very much for the fast response and the idea. I am trying to manually go through your install.sh script on libreelec.
how far would I need to go back in the git history? I see the bigger changes are starting at around beginning of this year. and adding support for 4.18 at around march 2019. so somewhere in between? |
|
@h4de5 actually 5.4 support (for current raspbian /Ubuntu ) was only merged in summer 2020 (after many months of unhappiness of users being forced to stay in old OSes) - so you only need to roll back a few months. I'll make a v4.19 branch soon - just stay on that branch and you'd be fine, and I'd be interested to know what adjustments you need to make to make it work. Your first 4 points aren't important, if you are happy with staying with one device and hardcoding that into your config.txt . A lot of the complexity is strictly speaking not necessary and only for dynamically detectino which respeaker it is and load the correct one. So that covers half of your 5th point too. To check that you have manually configure correctly you need to read your boot messages ( It is a bit painful without |
|
The v4.19 branch on https://github.com/HinTak/seeed-voicecard is now synced to v5.5 with all the Ubuntu related stuff earlier this year, minus v4.19+ necessary code changes. So you should use that, and possibly let me know of any interesting distro-related modifications needed for you. I don't work for Seeed Studio so maintaining two (current Ubuntu v5.4 and oldish Raspbian 4.19) and tracking a 3rd keeping x86_64 buildable on most current kernel (v5.9) is already beyond what I should... you are welcomed to click on the donate link at the bottom of https://hintak.github.io , if only to pay for a few SD cards to play with different OSes... |
|
wow. thanks a lot. thats the outcome. I also found a way to install there is no still - I now also found a way to install alsamixer through Kodi's multimedia tools (not sure if this helps) PS: I followed your advice about that buttons on your website - keep up the good work! |
|
@h4de5 that seems to have gone better than expected. So now we have a 3rd variants:
Possibly "bash: =~: unknown operand" is another busybox vs bash issue. I think you need to have a look at |
|
mmh. you are making me feel, like we could actually get this thing running.. I had put I also added this stuff (that I found on the internet, but actually have no idea about..) is any of this needed? not sure about: |
|
I have downloaded the LibreELEC image and have a look. So I updated the v4.19 branch. The correct place is Since you seem to be able to run I think we need to see your |
|
dmesgmaybe a stupid question, but should there be any vital signs on the respeaker if its pluged in correctly? like would it light a led or something? I already changed the connector twice because I was not sure - but there is no led on at the moment. |
|
@h4de5 libreELEC has |
install.shseeed-voicecardpulseaudio --startpacmd list-sourcesit is not showing up, right? ``` ``` |
|
@h4de5 okay, your dmesg is half-way to correct - these two lines means your overlay is half-loaded: your question about LEDs: no, the leds are programable and you can play with them (I have a script which makes them do a spinning rainbow...), but they don't automatically light up. @h4de5 since LibreELEC does not have dkms, we need to do things the old-fashioned way: if you do The part of interesting dmesg on raspbian looks like this: This is the 6-mics devices; I believe the 4-mics shows fewer ac10x lines, with a "codec count 1", and does not have the "input: seed-voicecard-headset" lines. It appears that the libreELEC does not ship any dev tools, so unfortunately you may need to install "make", "gcc", "kernel-dev" and perhaps a few other dev-related packages before you can run "make" correctly to generate the "*.ko" files. |
|
@h4de5 I had a look at volumio - it turns out to be just old raspbian, so as far as I see it should just work, if you are careful about kernel header package installation. |
|
My notes - It looks like Volumio is perhaps easier. If your You should be able to download the matching header,
I'll put these in the Volumio section of the above doc. |
|
I had no luck finding a way to get the build tools into kodi. lets assume - just for a moment - that I have no idea about building stuff with make .. what happens if I build it in a docker container that is running within libreelec or even on a separate raspbian installation on that rpi and copy them over? so, you think installation on volumio would be easier? i just checked, and that volumio is running on a rpi3b (not a rpi4). |
|
@h4de5 Volumio seems to be just older raspbian (Jesse), it may indeed be a bit too old for pi4? Not sure about this. |
|
@h4de5 I think volumio would work on pi4 - while most of the system is older raspbian, the kernel is a fairly current one - 20200512 as far as I can see, identical to what I am running on my kernel-version-locked current raspbian). |
|
ok. in this case i'll have a look at volumio later today. btw. I have put |
|
I am on volumio now. sudo ./install.sh./seeed-voicecarddmesgat least arecord is there: I am going through them right now. |
|
this is was my headers look like: |
How old is your volumio installation? As it says 2017, it is antique... |
|
I am wondering myself - its the current volumio (2.853), but I mostly updated it through the service itself - still 2017 seems a little too old. also - not sure if this matters - this installation is running on a berryboot bootloader, with the image located on a iSCSI mount. I tried to download those headers (only after I already tried to run install.sh) |
|
@h4de5 okay, for some strange reason, it is stuck at the older 4.9 kernel. Anyway, the error you saw is because of older compiler (than gcc 5 ... Current is 10, you know...) did not have __has_attribute . I just pushed a fix - please pull and see if you manage to continue compilation? |
should I try to update the berryboot installation? |
|
did I mentioned, that volumio is running on a rpi3 (not a 4) ? maybe thats the difference? |
|
Okay, made a mistake with the fix - pushed a better fix. Likely volumio has a special pi4 build with a more current kernel? I mean, pi 4 did not exist in 2017. |
|
i tried to update some more stuff. getting the latest berryboot version - it seems its running on 64bit now. |
|
According to the berryboot changelog, https://www.berryterminal.com/doku.php/berryboot/changelog , current berryboot is 5.4 based, same as Ubuntu and raspbian... |
|
yes. thats what I hoped to get : the kernel only changed a little - from 4.19.49v6v7 to 4.19.127v64 dmesg$ uname -a $ cat /proc/version |
|
32-bit builds are up - https://github.com/HinTak/berryboot/releases . The usual - you need to add a line to config.txt . Let me know if it works better or not. |
|
The new doc is up as https://github.com/HinTak/RaspberryPi-Dev/blob/master/Customizing-Berryboot.md about how to add the respeaker drivers to berryboot . |
|
@HinTak I am not sure what I am doing wrong, but I the rpi4 cannot boot with that image. I removed all files except the config/cmdline/udev/iscsi from the sdcard and copied your files on it. boot says: |
|
How does it differ from this maxnet/berryboot#673 ? |
|
now there is no boot manager. those messages are coming up before that screen is shown. and the rpi is stopping afterwards. |
|
@h4de5 argh, just re-reading your message - the 32-bit version has a different config.txt - in particular, you canot re-use the 64-bit one. |
|
@HinTak it seems the older kernel img needs another different now the berryboot menu is coming up - but without any images to select, nor an option to add a new one. Also no keyboard or mouse input is accepted. |
|
I saw this comment on the berryboot repo: maxnet/berryboot#645 (comment) now I am trying to find out my blkid |
|
The main differences are two: it has a different |
|
yep. did that: |
|
I think maxnet/berryboot#645 (comment) is not applicable - the pair of zip files should only differ by |
|
i tried to put the UUID into the cmdline like suggested in maxnet/berryboot#645 (comment) - still same problem: just to make sure: it should work on a rpi4 too, right? not only on rpi3? |
|
I should think so - both of them can operate in either 32-bit or 64-bit mode. |
|
@HinTak : sorry for the long delay - I tried out many things, and didn't want to post updates about failures :P so, I startet from scratch (a couple of times) but I could not get the 32bit version up and running. BUUUUT: the 64bit version is finally working on volumio. I am not sure what actually cased the problem. There was an empty /etc/asound.conf and some issues on a docker-container where I was testing for inputs. so - I still have one problem: the record from the mic-array is way too silent. I am using it for speech to text - and even if I am speaking face-to-mic, my system does not recognize the voice correctly. only if I amplify the record, I can hear my voice. |
|
@h4de5 the recording volume is controllable by mixer settings. Run I am hoping Seeed Studio staffer looking into the stability issue instead of me, but that's a lot of hope... |
|
all setup loud and clear :D thank you very much again! is my assumption correct, that now as its working on berryboot, I can get it working on any other distribution that I put on top of that? e.g. Kodi? |
|
You can certainly try :-). |
|
so. i think i finally made it. had some problems getting docker to work on that kodi, and i didn't even need the install script - just some modifications of the asound.conf thanks to your patched berryboot image the respeaker can now be used by a huge amount of rasperry distributions (https://berryboot.alexgoldcheidt.com/) thanks again and happy holidays. |
|
Good to hear. Happy holidays to you too. What are the modification to asound.conf? |
|
after finding card/device id from pcm.!default {
type asym
capture.pcm "mic"
playback.pcm "speaker"
}
pcm.mic {
type plug
slave {
pcm "hw:2,0"
}
}
pcm.speaker {
type plug
slave {
pcm "hw:1,0"
}
} |
|
@h4de5 I made a new 64-bit build As usual, click donate at https://hintak.github.io/ if you are feeling generous :) . |
|
In the latest berryboot + respeaker something seems to be failing with the I get while my config is the same as I built for Alpine in #174. The rest of dmesg looks ok. In the alsa source this is just a warning though, but nonetheless I'm not able to use the array. |
|
@biemster the missing mapping |
|
@biemster Argh yes, the latest berryboot I did was a 5.10.x kernel - yes, it is a known bug I fixed about two months ago. Need a new build. Sorry about that. |
|
@biemster filed new build pull upstream maxnet/berryboot#709 - should have a new build up a day or two |
|
@biemster new build now up at https://github.com/HinTak/berryboot/releases/tag/berryboot-20210624-pi64%2Brespeaker . I am a little curious that more than 1 of you (beside @h4de5 ) uses this combo - is there a club / company out there using this berryboot + respeaker combo? Anyway, please consider making a donation at https://hintak.github.io . The problem with the last build was #290 ; and there are two new issues about building berryboot on newer OSes/compilers, so it has taken some effort. Release notes below: === Fixes respeaker usage against 5.10 ( #290 ) and berry build issues with recent OSes / compilers ( maxnet/berryboot#710 maxnet/berryboot#709 ) Also included (over upstream) is a workaround for the respeaker-caused kernel panic / crash ( #251 ) As usual there is a vanillla build and a +respeaker driver build. |
|
Thanks @HinTak! I'm actually not a user of berryboot (and don't know of any clubs..), but found this thread when I was trying to get my 4mic array working in LibreELEC. That's facing a couple more hurdles, so I'll probably stay on my netbooting Alpine setup tbh. |
|
@biemster argh, I see libreelec 10.0 beta is indeed 5.10 based; the current stable release 9.2 is the same as the last time I looked at libreelec, rather old: LibreELEC 10.0 Beta LibreELEC 9.2 For there record, there is the beginning of how to do a customized image of libreelec here: https://wiki.libreelec.tv/development-1/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I am wondering if it was possible to install and run the 4mic-array on any other OS than raspbian. I would like to install them on Kodi (https://github.com/LibreELEC/LibreELEC.tv) or Volumio (https://github.com/volumio). On both systems the install script fails:
Both systems are running on a RPI4.
kodi:
volumio:
The text was updated successfully, but these errors were encountered: