From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Nandakumar Edamana <nandakumar@nandakumar.co.in>
Cc: alsa-devel@alsa-project.org
Subject: Re: Behringer UMC202HD issues and a partial solution
Date: Tue, 18 Jan 2022 16:20:07 -0300 [thread overview]
Message-ID: <YecS5xgtI4Kzbmav@geday> (raw)
In-Reply-To: <7a505959-3111-ffaa-7e03-3d9edcf03a4d@nandakumar.co.in>
On Tue, Jan 18, 2022 at 04:50:12PM +0530, Nandakumar Edamana wrote:
> I feel like I'm doing something wrong with the build and install
> process. Maybe it's been the case for the last couple of days, in which
> case I'm terribly sorry for the incorrect test results.
>
> The problem is, I don't get any printk() outputs at all. I'd given `echo
> "7" > /proc/sys/kernel/printk`, and I even added a usb_audio_dbg() line,
> which didn't get printed either.
>
> Then I saw this:
>
> $ find /lib/modules/ -name 'snd-usb-audio.ko'|xargs ls
> ...
> /lib/modules/5.15.13/extra/usb/snd-usb-audio.ko
> /lib/modules/5.15.13/kernel/sound/usb/snd-usb-audio.ko
> ...
>
> modprobe is using the kernel/ version while my commands were installing
> the extra/ version.
>
> Then I used the following, which also installed the extra/ version:
> sudo make -C /lib/modules/5.15.13/build M=sound modules_install
>
> Are these two versions supposed to exist? What is the solution? Telling
> the kernel build system to choose the correct location or configuring
> modprobe or depmod or something? I tried to look it up, but didn't find
> any official recommendation.
Yes, it will install on extra/ if you are building with the M=sound/usb
option. I guess the 'official' solution is to use the INSTALL_MOD_PATH
environment variable.
But what I do instead is I overwrite
/lib/modules/<kernel_version>/kernel/sound/usb/snd-usb-audio.ko with the newly
built one, and then I run depmod.
>
> Anyway, I ran this:
>
> # Because I have space constraints
> # find /lib/modules/5.15.13/ -name '*.ko' -exec strip --strip-unneeded {} +
> # update-initramfs -u -k 5.15.13
>
> That updated the extra/ version of snd-usb-audio. But even after a
> reboot, this is what I get:
>
> # modprobe -r -v snd-usb-audio
> rmmod snd_usb_audio
> rmmod snd_usbmidi_lib
> # modprobe -v snd_usb_audio dyndbg==p
> insmod /lib/modules/5.15.13/kernel/sound/usb/snd-usbmidi-lib.ko
> insmod /lib/modules/5.15.13/kernel/sound/usb/snd-usb-audio.ko index=-2
> index=-2 index=-2 dyndbg==p
> # dmesg |grep 'implicit:'
>
> Another thing is, even though I'd commented out my clock workaround, I'm
> not getting any clock-related warning at all (I'm sure those went away
> after I edited clock.c, and then performed a build+install).
I noticed that on your dmesg logs, that the warning was nowhere to be
found.
Thank you,
Geraldo Nascimento
>
> --
> Nandakumar Edamana
> https://nandakumar.org
>
prev parent reply other threads:[~2022-01-18 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:37 Behringer UMC202HD issues and a partial solution Nandakumar Edamana
2022-01-13 19:00 ` Geraldo Nascimento
2022-01-14 2:34 ` Nandakumar Edamana
2022-01-14 3:41 ` Geraldo Nascimento
2022-01-14 4:36 ` Nandakumar Edamana
2022-01-14 7:44 ` Geraldo Nascimento
2022-01-14 13:39 ` Nandakumar Edamana
2022-01-14 22:28 ` Geraldo Nascimento
[not found] ` <5fba3e63-6fd2-de1c-1564-ac6b8870e730@nandakumar.co.in>
2022-01-16 1:00 ` Geraldo Nascimento
2022-01-18 11:20 ` Nandakumar Edamana
2022-01-18 19:20 ` Geraldo Nascimento [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YecS5xgtI4Kzbmav@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=nandakumar@nandakumar.co.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).