Test patch for: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 0 to 0 which makes no sense.

Asked by Brent on 2020-01-16

Hi;

I reported this issue (https://bugzilla.kernel.org/show_bug.cgi?id=206221) which now has a patch available to test; and would like to find out what options I have for testing it.

Is there anyway to get the update running without a full re-install of my system?

Thanks,
Brent

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2020-01-16
Last reply:
2020-01-16
Manfred Hampl (m-hampl) said : #1

As far as I can see this patch modifies a source file that is used when compiling the kernel.

Testing most probably requires
- downloading the source for the kernel packages
- applying the patch
- building a new version of the kernel packages with the modified source
- booting that new kernel.

Instructions how to build your own version of the kernel on Ubuntu is described in https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

Brent (brentgracey) said : #2

Thanks for those pointers
So at the moment; I only have one machine
If I build the path-ed kernel and then install the three-package set on my build system, is there a way to "roll back" to my current kernel afterwards?

Thanks

Manfred Hampl (m-hampl) said : #3

Yes, you can roll back to an older Ubuntu-provided version of the kernel.

An early step of booting is starting the grub boot loader, and that offers the choice between different kernels that are available on your system. You can always go back to the previous one (as long as you haven't manually removed it).

As a preparation you could consider activating the display of the grub boot loader by setting "GRUB_TIMEOUT_STYLE=menu" in /etc/default/grub and running "sudo update-grub" afterwards.

Remarks: I assume that you need more than just these three packages, additionally linux-modules-(version)-generic and linux-modules-extra-(version)-generic. (Perhaps you have to "fakeroot debian/rules binary" instead of "fakeroot debian/rules binary-headers binary-generic binary-perarch").

And: I have never tried building a kernel myself.

Can you help with this problem?

Provide an answer of your own, or ask Brent for more information if necessary.

To post a message you must log in.