From: Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de>
To: alsa-devel@alsa-project.org
Subject: Re: can't insmod patched snd-usb-audio
Date: Sat, 9 Aug 2014 14:46:30 +0200 [thread overview]
Message-ID: <20140809124630.GB7938@x1-orm> (raw)
In-Reply-To: <20140809114001.GA7938@x1-orm>
Got it working. An additional "make modules_prepare" seemed to do the
trick. sorry for the noise...
--
Orm
Am Samstag, den 09. August 2014 um 13:40:01 Uhr (+0200) schrieb Orm Finnendahl:
> Hi,
>
> hope it's ok to post it here as it's not (yet) official alsa: After
> having no issues with Tobias Hoffmann's scarlett alsa mixer patch on
> my older kernels, trying to insmod the patched kernel modules on my
> most current kernel (the patch and documentation obtained with
> "git clone http://github.com/trrichard/alsa-driver_scarlett.git")
> fails with the following message:
>
> root@x1-orm:/usr/src/linux-source-3.14# insmod sound/usb/snd-usbmidi-lib.ko
> insmod: ERROR: could not insert module sound/usb/snd-usbmidi-lib.ko: Unknown symbol in module
>
> root@x1-orm:/usr/src/linux-source-3.14# insmod sound/usb/snd-usb-audio.ko
> insmod: ERROR: could not insert module sound/usb/snd-usb-audio.ko: Unknown symbol in module
>
> I'm on debian testing with 3.14-2-amd64 kernel and followed all the
> instructions in the scarlett kernel patch README (I tried three times
> each with a fresh kernel source tree from scratch to be sure). The
> patch has worked for me on older kernels without any problems.
>
> Does anybody know how to deal with this? Let me know if you need
> further information.
>
> Yours,
> Orm
next prev parent reply other threads:[~2014-08-09 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 11:40 can't insmod patched snd-usb-audio Orm Finnendahl
2014-08-09 12:46 ` Orm Finnendahl [this message]
2014-08-10 11:57 ` Daniel Mack
2014-08-21 0:25 ` Ira Malinich
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=20140809124630.GB7938@x1-orm \
--to=orm.finnendahl@selma.hfmdk-frankfurt.de \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.