You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
In archlinux can't start linux-samus4 kernel, normal kernel works ok #214
Not sure if I actually solved it (can someone tell me how to verify that i'm running the right kernel version?) But I was able to to run mkinitcpio -g /boot/initramfs-linux-samus4.img -k /boot/vmlinuz-linux-samus4 and it looks like that might have solved it ¯_(ツ)_/¯
Same issue with the newest build, after upgrade the kernel stopped working, I used kinitcpio -g /boot/initramfs-linux-samus4.img -k /boot/vmlinuz-linux-samus4. Now the kernel loads but the bdrw-rt5677 isn't recognized, and there's no sound.
I believe I've narrowed it down to the changes to scripts/config in commit f73a2cd, probably related to the change to "Update config to vanilla kernel" per changelog. I don't know specifically what changes in the config file are causing the issue (there are a ton). I can say that compiling a kernel based on the config file in this and later commits takes about twice as long and compiles a very large number of things the previous config file didn't (e.g. all of drivers/staging)... and yet the resulting initrd.img file is significantly smaller (28MB vs 11.5MB).
We could just revert the change by taking the scripts/config from aa7a5b3, running yes '' | make oldconfig on it for the current kernel branch and committing the result. Alternatively, we could take a recent generic .config from one of the distros as those seem to be fine as well.
FYI I had to revert to the vanilla kernel config (and re-tweak for optimizations) because the old config caused too many issues in the new version of the kernel (sound and suspend would not work for example). That being said the current config could be optimized further - it does build a lot of modules that are not actually used (note that this does not affect performance in any meaningful way, just build time). I am not sure why this would make a difference in how the kernel is loaded or how ALSA needs to be configured though...
Activity
Aesop7 commentedon May 21, 2018
Not sure if I actually solved it (can someone tell me how to verify that i'm running the right kernel version?) But I was able to to run
mkinitcpio -g /boot/initramfs-linux-samus4.img -k /boot/vmlinuz-linux-samus4and it looks like that might have solved it ¯_(ツ)_/¯SimionKreimer commentedon May 22, 2018
Thanks I tried that fix, and now the kernel loads, but the sound doesn't work.
SimionKreimer commentedon May 22, 2018
Same issue with the newest build, after upgrade the kernel stopped working, I used kinitcpio -g /boot/initramfs-linux-samus4.img -k /boot/vmlinuz-linux-samus4. Now the kernel loads but the bdrw-rt5677 isn't recognized, and there's no sound.
sprc commentedon May 24, 2018
Also affects Ubuntu.
SimionKreimer commentedon May 24, 2018
I reinstalled Antergos, had this issue again, used Aesop7's fix and after spending some time to get alsa to work again was able to get the sound back.
sprc commentedon May 26, 2018
I believe I've narrowed it down to the changes to scripts/config in commit f73a2cd, probably related to the change to "Update config to vanilla kernel" per changelog. I don't know specifically what changes in the config file are causing the issue (there are a ton). I can say that compiling a kernel based on the config file in this and later commits takes about twice as long and compiles a very large number of things the previous config file didn't (e.g. all of drivers/staging)... and yet the resulting initrd.img file is significantly smaller (28MB vs 11.5MB).
We could just revert the change by taking the scripts/config from aa7a5b3, running
yes '' | make oldconfigon it for the current kernel branch and committing the result. Alternatively, we could take a recent generic .config from one of the distros as those seem to be fine as well.I suspect this is also what's behind issue #208.
raphael commentedon May 28, 2018
FYI I had to revert to the vanilla kernel config (and re-tweak for optimizations) because the old config caused too many issues in the new version of the kernel (sound and suspend would not work for example). That being said the current config could be optimized further - it does build a lot of modules that are not actually used (note that this does not affect performance in any meaningful way, just build time). I am not sure why this would make a difference in how the kernel is loaded or how ALSA needs to be configured though...