-
Notifications
You must be signed in to change notification settings - Fork 294
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
Remove Kernel Downgrade #209
Comments
I want to Downgrade by default, so that to ensure that the software can be installed, perhaps you can submit a PR, there is an option is the use of the latest kernel. |
I'm not familiar with patching kernels, driver development. So I won't contribute to the second part - avoid downgrading the kernel for driver installation to succeed. Please do it by your own.. Nevertheless, good job, thank you very much for developing respeaker drivers! P.S. Downgrading the kernel to ensure that the software can be installed is in my opinion a security issue. This may therefore impact lifecyle/acceptance of respeaker driver and hardware. Better find another way without downgrading kernel to ensure that the software can be installed/patched directly. I think this is a design and lifcyle descision you should make at respeaker/seeed-voicecard. |
Oh, so that was why I could not install the 4mic driver.. Anyone know of a fix? |
See also the now closed #192 , I have pushed upstream to fix the kernel header issue - So it is no longer necessary to downgrade the kernel to get matching headers. In fact I have been using the respeaker driver for both up to date stretch and up to date buster for a few months since. Please remove the kernel downgrade. @Pillar1989 |
Actually what is happening to me is it is taking forever in kernel downgrade part in ./install.sh I am using this version of raspbian (as mentioned here: https://www.raspberrypi.org/downloads/raspbian/):
it is not only taking forever but sometimes it just got disconnect from the ssh, pi is not restarting not script failing but just got unresponsive @HinTak as you told above that something was wrong was with raspbian and you said it is now fixed, so if I remove please let me know your opinion however what I have done for now is started downloading raspbian stretch with release name |
someone also tell me the kernel which they are forcing came with which version of raspbian, because I cannot find list of all raspbian with their kernel detail on internet, I will be thankful for now I don't care about anything but I have to complete one of my prototype asap, so may be I will be ending up downloading all raspbian releases and installing each of them for checking their version in worst case, lolz how dumb of me 🤣 |
here is my fork I removed the raspbian version is same as before:
and here is my install log:
lets see what happens after reboot :-D |
worked ;-) |
I'll wait until the kernel downgrade is removed - as @HinTak mentioned this is not needed anymore and should be removed. Actually the state of this driver installation script is some kind of messy and needs to be refactored in my opinion. |
Yeah, that kernel downgrade is a real pain, terrible |
Hallo @Pillar1989 Can we have your input? It's terrible to install on a rpi zero, wait 20+ minutes for nothing. There must be a better way to install those drivers no? |
The available kernel packages are under |
I have put out a pull for this #223 |
Done with #225 |
Hello @KillingJacky, i want to be sure and ask some question. After i do " sudo ./install.sh ", and reboot, arecord -L didnt show me any seeed voice card device. So this mean i have to follow #225 ?? Because after i plug my sd card to raspy3b+, arecord -L show me seeed voice card device. It makes me confused why in raspy4 it can't , in raspy 3b+ it can Im using raspy4 and latest raspbian buster fyi. Thanks, |
You need to look at |
Pardon @HinTak , that mean you just doing normal instalation and success? Now im formatting sd card and trying to install again. Im gonna try what you say, so i have to put cmnd dmesg after i do "sudo ./install.sh " for deebugging right? Please correct me if i wrong |
Oh 1 more , where i can find this command and change it
|
No, you watch dmesg after reboot. Dmesg shows messages from the kernel (whether the driver is loaded, and successful or not) |
see #238 (comment) regarding the unfeasibility of downgrading... |
hi @mxklb
this could be done by ./install argument --keep-kernel |
I don't use seeed-voicecard products anymore, this one is not production ready. This all here is just DIY/WIP stuff .. If you like DIY/WIP, you could stick to seeed-voicecard products. I for myself decided to step away from this vendor (in my opinion at least seeed-voicecard is badly designed & hacky from what I saw..) and use better production ready products. @turmary thaks for this info, this is really unbelievable, I can't get it .. 👍 |
Actually I can't install the 2mic respeaker driver on a vanilla flashed HypriotOS v1.12.0 on a PI4. What happens is, the /boot partition of the OS is too small (~12MB free space) to downgrade the kernel during your install.sh script. So far so good but finally after your script finished, I end up with a bricked OS with read-only file system.
The install.sh script shall therefore
Ok, now I'll get a flashed HypriotOS with bigger /boot partition.
P.S. With former releases of this OS, 2mic respeaker worked. I'll post an issue there too.
install-failure_full-log.txt
The text was updated successfully, but these errors were encountered: