[alsa-devel] Gitcompile for Kernel 3.2?
Hi all,
Having cloned alsa-driver and alsa-kmirror, my gitcompile and sudo make install-modules goes smoothly. However, the modules won't load. First errors in dmesg are: [ 24.415466] snd_hwdep: disagrees about version of symbol snd_info_register [ 24.415475] snd_hwdep: Unknown symbol snd_info_register (err -22) [ 24.415489] snd_hwdep: disagrees about version of symbol snd_info_create_module_entry [ 24.415495] snd_hwdep: Unknown symbol snd_info_create_module_entry (err -22) ... and so on. My initial assumption is that kmirror is specific to a 2.6 kernel, while I'm running 3.2, though some of what I've read seems to contradict this. I've tried foregoing kmirror for a full 3.2 kernel source, but that failed on gitcompile. I also tried with kmirror on a 2.6 kernel, but those modules also failed to load. I initially thought my problems stemmed from trying to do this against a lowlatency kernel, but I've subsequently had the same against vanilla Ubuntu kernels. Would someone kindly point me in the right direction? * Is it possible to compile and load a subset of alsa modules without having full kernel sources on hand? * If so, is this restricted to particular kernels (docs seem to suggest 2.6, 3.0 and 3.2 are supported)? * If not, is alsa-driver expected to compile against 3.2 sources as is (mine fails on some of the patching - presumably the make dep step)? * Does the alsa-driver.new.git merge address this, or is development expected to take place in a 2.6 environment?
Sorry if any or all of this is incoherent (please help me to clarify), but any pointers would be greatly appreciated. What might be pertinent: Ubuntu 12.04 (kernels 3.2.0 and 2.6.38 tested), gcc 4.6.3, anything else? I am attempting to add device support for a multi-port MIDI interface. I managed to get a working prototype running a year ago, but had to shelve the project due to work pressures. I'd really love to get it back up and submitted.
Kind regards, Mark Brand.
________________________________
NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
At Sun, 5 Aug 2012 13:25:18 +0000, Brand, Mark (Mr) (Summerstrand Campus South) wrote:
Hi all,
Having cloned alsa-driver and alsa-kmirror, my gitcompile and sudo make install-modules goes smoothly. However, the modules won't load. First errors in dmesg are: [ 24.415466] snd_hwdep: disagrees about version of symbol snd_info_register [ 24.415475] snd_hwdep: Unknown symbol snd_info_register (err -22) [ 24.415489] snd_hwdep: disagrees about version of symbol snd_info_create_module_entry [ 24.415495] snd_hwdep: Unknown symbol snd_info_create_module_entry (err -22) ... and so on.
Could you try the following tree (or alsa-driver snpashot)?
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver.git ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
Takashi Iwai wrote:
Could you try the following tree (or alsa-driver snpashot)?
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver.git ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The git url couldn't be found (should I go with alsa-driver-build.git?), but I have pulled the tarball, thank you. It wouldn't compile on my 3.2 lowlatency machine (with or without ALSAKERNELDIR set to 3.2.0-lowlatency source). I'll carry it home and try on a vanilla 3.2 kernel tonight. Would you mind clarifying for me: is it necessary to have kernel source on hand or not?
Thanks, Mark Brand.
________________________________
NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
At Mon, 6 Aug 2012 11:52:53 +0000, Brand, Mark (Mr) (Summerstrand Campus South) wrote:
Takashi Iwai wrote:
Could you try the following tree (or alsa-driver snpashot)?
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver.git ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The git url couldn't be found (should I go with alsa-driver-build.git?),
Yes, sorry for the typo.
but I have pulled the tarball, thank you. It wouldn't compile on my 3.2 lowlatency machine (with or without ALSAKERNELDIR set to 3.2.0-lowlatency source). I'll carry it home and try on a vanilla 3.2 kernel tonight. Would you mind clarifying for me: is it necessary to have kernel source on hand or not?
Well, it depends on the error you got...
Takashi
Takashi Iwai wrote:
Well, it depends on the error you got...
Yes of course, sorry. When I:
mark@ubuntustudio:~/workspace/alsa-driver-build$ ALSAKERNELDIR=/usr/src/linux-lowlatency-3.2.0 ./gitcompile --with-moddir=updates
I get:
cp ../../alsa-kernel/include/core.h . patch -p0 -i core.patch core.h patching file core.h Hunk #1 succeeded at 104 (offset -1 lines). [snip] Hunk #7 FAILED at 449. 1 out of 7 hunks FAILED -- saving rejects to file core.h.rej make[3]: *** [core.h] Error 1 make[3]: Leaving directory `/home/mark/workspace/alsa-driver-build/include/sound' make[2]: *** [prepare] Error 2 make[2]: Leaving directory `/home/mark/workspace/alsa-driver-build/include/sound' make[1]: *** [prepare] Error 2 make[1]: Leaving directory `/home/mark/workspace/alsa-driver-build/include' make: *** [dep] Error 1
So this is my attempt to build against the 3.2.0-lowlatency kernel. I'll try tonight (at home) against the vanilla 3.2 kernel.
________________________________
NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
At Mon, 6 Aug 2012 14:43:35 +0000, Brand, Mark (Mr) (Summerstrand Campus South) wrote:
Takashi Iwai wrote:
Well, it depends on the error you got...
Yes of course, sorry. When I:
mark@ubuntustudio:~/workspace/alsa-driver-build$ ALSAKERNELDIR=/usr/src/linux-lowlatency-3.2.0 ./gitcompile --with-moddir=updates
alsa-driver-build git tree is strictly coupled with sound git tree. You can't use it for other kernels for $ALSAKERNELDIR.
Of course, you can _build_ the drivers included in sound git tree for your kernel. It's a completely different issue. With the command sequence above, you were trying to build the driver code of your 3.2.x kernel with the alsa-driver build stub for 3.6. This doesn't work.
That is, prepare both alsa-driver-build.git and sound.git trees in the same directory. Then run ./gitcompile without ALSAKERNELDIR.
Takashi
1000 apologies for my noob-ness, but I'm still not getting it. I think I understand why it can't be expected to work as is, but I don't know how best to proceed.
That is, prepare both alsa-driver-build.git and sound.git trees in the same directory. Then run ./gitcompile without ALSAKERNELDIR.
Please help me understand what is meant by 'prepare'. Does this refer to a make step, or copying files from the appropriate kernel source, or... ? I haven't been able to clone sound.git either (I get "RPC failed - result=18" and 'protocol error: bad pack header', though alsa-driver-build clones just fine), so I'm assuming it's similar to kmirror.git? If alsa-driver-build is specific to 3.6 (Is that what was implied?), then what modifications would typically be required? And as stupid as this sounds, I'm not entirely sure I understand what is meant by "same directory"! alsa-driver-build and sound next to each other, or sound inside alsa-driver-build? Again, my profuse apologies for being the "weakest link"! Thank you for your patience…
________________________________
NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
At Tue, 7 Aug 2012 10:24:54 +0000, Brand, Mark (Mr) (Summerstrand Campus South) wrote:
1000 apologies for my noob-ness, but I'm still not getting it. I think I understand why it can't be expected to work as is, but I don't know how best to proceed.
That is, prepare both alsa-driver-build.git and sound.git trees in the same directory. Then run ./gitcompile without ALSAKERNELDIR.
Please help me understand what is meant by 'prepare'. Does this refer to a make step, or copying files from the appropriate kernel source, or... ? I haven't been able to clone sound.git either (I get "RPC failed - result=18" and 'protocol error: bad pack header', though alsa-driver-build clones just fine), so I'm assuming it's similar to kmirror.git? If alsa-driver-build is specific to 3.6 (Is that what was implied?), then what modifications would typically be required? And as stupid as this sounds, I'm not entirely sure I understand what is meant by "same directory"! alsa-driver-build and sound next to each other, or sound inside alsa-driver-build? Again, my profuse apologies for being the "weakest link"! Thank you for your patience…
% mkdir $HOME/build % cd $HOME/build % git clone git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git % git clone git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git % cd alsa-driver-build % ./gitcompile --with-debug=full --enable-dynamic-minors --with-moddir=updates % sudo make install-modules
Takashi
Just to close out this thread: all of my problems seem to have stemmed from overzealous use of the --with-cards option <sheepish grin>. Both the alsa-driver-build.git/sound.git and alsa-driver.git/kmirror.git approaches gitcompile just fine on Ubuntu 12.04 and Ubuntu-Studio 12.04 (with 3.2 vanilla and lowlatency kernels, respectively) when compiled as suggested below. I think I've lost pulseaudio somewhere in the process, but I'll hunt that down some other day. Thank-you again, Takashi.
Mark Brand.
-----Original Message----- From: Takashi Iwai [mailto:tiwai@suse.de] Sent: 07 August 2012 12:31 PM To: Brand, Mark (Mr) (Summerstrand Campus South) Cc: alsa-devel@alsa-project.org Subject: Re: [alsa-devel] Gitcompile for Kernel 3.2?
% mkdir $HOME/build % cd $HOME/build % git clone git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git % git clone git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git % cd alsa-driver-build % ./gitcompile --with-debug=full --enable-dynamic-minors --with-moddir=updates % sudo make install-modules
Takashi
________________________________
NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
participants (2)
-
Brand, Mark (Mr) (Summerstrand Campus South) -
Takashi Iwai