error compiling alsa driver 1.0.9b on slackware 10.2

salviadud · 11-13-2005, 07:18 PM

i get this error message after I do make, proceeding ./configure

Code:

/home/dude/alsa-driver-1.0.9b/usb/usbaudio.c: In function 
`deactivate_urbs':
/home/dude/alsa-driver-1.0.9b/usb/usbaudio.c:713: error: 
`URB_ASYNC_UNLINK' undeclared (first use in this function)
/home/dude/alsa-driver-1.0.9b/usb/usbaudio.c:713: error: (Each undeclared 
identifier is reported only once
/home/dude/alsa-driver-1.0.9b/usb/usbaudio.c:713: error: for each function 
it appears in.)
make[4]: *** [/home/dude/alsa-driver-1.0.9b/usb/usbaudio.o] Error 1
make[3]: *** [/home/dude/alsa-driver-1.0.9b/usb] Error 2
make[2]: *** [_module_/home/dude/alsa-driver-1.0.9b] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14.2'
make: *** [compile] Error 2

i suspect i need to deactive something in the kernel?

something about usb audio... makes no sense, i just got a pci card or something. hehe

please help dudes.

rkelsen · 11-13-2005, 07:42 PM

Why not use the alsa drivers in the kernel? They're the same thing.

salviadud · 11-13-2005, 07:44 PM

The reason i don't use alsa from the kernel, is because im not sure what the hell is my soundcard...

if i would like to deactive usb sound on the makefile... what makefile should I edit?

rkelsen · 11-13-2005, 09:32 PM

Quote:

Originally posted by salviadud
The reason i don't use alsa from the kernel, is because im not sure what the hell is my soundcard...

So build all of the modules.

salviadud · 11-13-2005, 10:35 PM

should i build them as modules <M> or built into the kernel <*>?

still, i don't like it that way. perhaps i should go back to 2.6.13?

rkelsen · 11-13-2005, 11:02 PM

Quote:

Originally posted by salviadud
should i build them as modules <M> or built into the kernel <*>?

still, i don't like it that way. perhaps i should go back to 2.6.13?

Modules <M> are the best option.

What is the difference between doing it this way and building the driver package? IMO, including them as part of the kernel build is the cleanest option.

jong357 · 11-13-2005, 11:23 PM

Yea, this happened to me as well as soon as I switched to 2.6.14.... The latest tarballs from alsa have fixed this but I'm still getting some other problems afterwards when trying to run alsamixer.

salviadud · 11-14-2005, 01:44 AM

guys, im sorry i even started this thread, i already reverted to 2.6.13.1 and well, it works... im happy with that. the linux kernel gets tweaked so much, i wonder why.......

well. anyways, when they get to fix 2.6.14, ill give it a shot, maybe.

thanx a lot anyways.

rkelsen · 11-14-2005, 02:16 AM

Quote:

Originally posted by salviadud
guys, im sorry i even started this thread, i already reverted to 2.6.13.1 and well, it works... im happy with that. the linux kernel gets tweaked so much, i wonder why.......

2.6.14 with alsa on Slackware 10.2 works fine for me here. Maybe there was an incorrect option selected in your kernel config.

The kernel is always being tweaked for several reasons. Not least of these are security fixes and drivers for new hardware.

Now that you have it working under 2.6.13.1, run an 'lsmod' to see which modules are being loaded. Modify your 2.6.14 kernel config to suit. Hint: the alsa module names all start with 'snd'

salviadud · 11-14-2005, 04:36 AM

I'm sorry again, when I said kernel 2.6.14, I meant, 2.6.14.2

so... maybe that one in specific has some trouble there...

security fixes, I agree, gotta be tight. still I don't run a website or have very useful info. just the usual honeypot pr0n and music.

maybe I'll try 2.6.14... but, in the meantime... ill get some sleep. hehe