alsa driver
Hi I don't know how to install alsa drivers on my potato machine with the 2.4.2 kernel. I downloaded from the potato server the following packages and I succesfully installed them alsa-base_0.4.1i-5.deb alsa-headers_0.4.1i-5.deb alsa-source_0.4.1i-5.deb alsaconf_0.4.2-3.deb alsaplayer-alsa_0.99.26-2.1.deb alsaplayer-esd_0.99.26-2.1.deb alsaplayer-oss_0.99.26-2.1.deb alsaplayer_0.99.26-2.1.deb alsautils_0.4.1-5.deb asmixer_0.5-4.deb aumix_2-1.deb I also downloaded alsa-driver-0.4.tar.gz but when I try to compile this I get this: gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o memory.o memory.c memory.c: In function `snd_malloc_pages_R838db77d': memory.c:45: warning: implicit declaration of function `MAP_NR' gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o info.o info.c ... info.c:685: warning: initialization from incompatible pointer type info.c:691: warning: excess elements in struct initializer info.c:691: warning: (near initialization for `snd_info_card_link_inode_operations') info.c: In function `snd_info_card_register': info.c:784: structure has no member named `ops' info.c: In function `snd_info_create_device_R3271fcb6': info.c:954: structure has no member named `ops' info.c: In function `snd_info_register_R5d82e39c': info.c:1057: structure has no member named `ops' make[1]: *** [info.o] Error 1 make[1]: Leaving directory `/usr/src/modules/alsa-driver-0.4/kernel' make: *** [compile] Error 1 /usr/src/modules/alsa-driver-0.4# ... When I try to start the TkAlsaMixer (from the ALSA homepage) I get this: "Original error: The ALSA sound driver was not detected in this system." What do I miss ?? TIA! Philipp
Re: alsa driver
On Wed, 28 Mar 2001, Philipp Bliedung wrote: > Hi > > I don't know how to install alsa drivers on my potato machine with the > 2.4.2 kernel. > I downloaded from the potato server the following packages and I > succesfully installed them > > alsa-base_0.4.1i-5.deb > alsa-headers_0.4.1i-5.deb > alsa-source_0.4.1i-5.deb > alsaconf_0.4.2-3.deb > alsaplayer-alsa_0.99.26-2.1.deb > alsaplayer-esd_0.99.26-2.1.deb > alsaplayer-oss_0.99.26-2.1.deb > alsaplayer_0.99.26-2.1.deb > alsautils_0.4.1-5.deb > asmixer_0.5-4.deb > aumix_2-1.deb > > I also downloaded alsa-driver-0.4.tar.gz but when I try to compile this > I get this: > Don't really know, you did compile a kernel selecting sound but no specific card ? The kernel source directory being accessed during compilation of the alsa drivers is the one you want? > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: alsa driver
On Wed, 28 Mar 2001, Christopher Mosley wrote: > > > On Wed, 28 Mar 2001, Philipp Bliedung wrote: > > > Hi > > > > I don't know how to install alsa drivers on my potato machine with the > > 2.4.2 kernel. > > I downloaded from the potato server the following packages and I > > succesfully installed them > > > > alsa-base_0.4.1i-5.deb > > alsa-headers_0.4.1i-5.deb > > alsa-source_0.4.1i-5.deb > > alsaconf_0.4.2-3.deb > > alsaplayer-alsa_0.99.26-2.1.deb > > alsaplayer-esd_0.99.26-2.1.deb > > alsaplayer-oss_0.99.26-2.1.deb > > alsaplayer_0.99.26-2.1.deb > > alsautils_0.4.1-5.deb > > asmixer_0.5-4.deb > > aumix_2-1.deb > > > > I also downloaded alsa-driver-0.4.tar.gz but when I try to compile this > > I get this: > > > Don't really know, you did compile a kernel selecting sound but no > specific card ? The kernel source directory being accessed during > compilation of the alsa drivers is the one you want? that last part should be: ... compilation of the alsa drivers is the one you want to select. > > > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: alsa driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The potato alsa packages are very out of date. I would recommend downloading the source tarballs and using ALSA that way. Sean On Wednesday 28 March 2001 11:33, Philipp Bliedung wrote: > Hi > > I don't know how to install alsa drivers on my potato machine with the > 2.4.2 kernel. > I downloaded from the potato server the following packages and I > succesfully installed them > > alsa-base_0.4.1i-5.deb > alsa-headers_0.4.1i-5.deb > alsa-source_0.4.1i-5.deb > alsaconf_0.4.2-3.deb > alsaplayer-alsa_0.99.26-2.1.deb > alsaplayer-esd_0.99.26-2.1.deb > alsaplayer-oss_0.99.26-2.1.deb > alsaplayer_0.99.26-2.1.deb > alsautils_0.4.1-5.deb > asmixer_0.5-4.deb > aumix_2-1.deb > > I also downloaded alsa-driver-0.4.tar.gz but when I try to compile this > I get this: > > gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 > -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes > -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o memory.o > memory.c > memory.c: In function `snd_malloc_pages_R838db77d': > memory.c:45: warning: implicit declaration of function `MAP_NR' > gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 > -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes > -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o info.o > info.c > ... > info.c:685: warning: initialization from incompatible pointer type > info.c:691: warning: excess elements in struct initializer > info.c:691: warning: (near initialization for > `snd_info_card_link_inode_operations') > info.c: In function `snd_info_card_register': > info.c:784: structure has no member named `ops' > info.c: In function `snd_info_create_device_R3271fcb6': > info.c:954: structure has no member named `ops' > info.c: In function `snd_info_register_R5d82e39c': > info.c:1057: structure has no member named `ops' > make[1]: *** [info.o] Error 1 > make[1]: Leaving directory `/usr/src/modules/alsa-driver-0.4/kernel' > make: *** [compile] Error 1 > /usr/src/modules/alsa-driver-0.4# > ... > When I try to start the TkAlsaMixer (from the ALSA homepage) I get this: > > "Original error: The ALSA sound driver was not detected in this system." > > What do I miss ?? > > TIA! > Philipp - -- You don't have to think too hard when you talk to teachers. -- J. D. Salinger -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6wnbi16C1pcgeMvkRArJEAKDGYgY1W+A5X4wqFM6iurvFlv6feQCeKjXj 0x+cJwBJeGDtMHIajXElgYI= =w8K7 -END PGP SIGNATURE-
Re: alsa driver
HI, I'm instead tracking unstable but alsa drivers produce a nice kernel panic when unloading (using 2.4.2). This didn't happened with 2.4.0 or 2.4.2-ac26/28 Fabio Philipp Bliedung wrote: > > Hi > > I don't know how to install alsa drivers on my potato machine with the > 2.4.2 kernel. > I downloaded from the potato server the following packages and I > succesfully installed them > > alsa-base_0.4.1i-5.deb > alsa-headers_0.4.1i-5.deb > alsa-source_0.4.1i-5.deb > alsaconf_0.4.2-3.deb > alsaplayer-alsa_0.99.26-2.1.deb > alsaplayer-esd_0.99.26-2.1.deb > alsaplayer-oss_0.99.26-2.1.deb > alsaplayer_0.99.26-2.1.deb > alsautils_0.4.1-5.deb > asmixer_0.5-4.deb > aumix_2-1.deb > > I also downloaded alsa-driver-0.4.tar.gz but when I try to compile this > I get this: > > gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 > -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes > -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o memory.o > memory.c > memory.c: In function `snd_malloc_pages_R838db77d': > memory.c:45: warning: implicit declaration of function `MAP_NR' > gcc -DALSA_BUILD -O2 -m486 -malign-loops=2 -malign-jumps=2 > -malign-functions=2 -DCPU=686 -DLINUX -Wall -Wstrict-prototypes > -fomit-frame-pointer -pipe -I/usr/src/linux/include -I.. -c -o info.o > info.c > ... > info.c:685: warning: initialization from incompatible pointer type > info.c:691: warning: excess elements in struct initializer > info.c:691: warning: (near initialization for > `snd_info_card_link_inode_operations') > info.c: In function `snd_info_card_register': > info.c:784: structure has no member named `ops' > info.c: In function `snd_info_create_device_R3271fcb6': > info.c:954: structure has no member named `ops' > info.c: In function `snd_info_register_R5d82e39c': > info.c:1057: structure has no member named `ops' > make[1]: *** [info.o] Error 1 > make[1]: Leaving directory `/usr/src/modules/alsa-driver-0.4/kernel' > make: *** [compile] Error 1 > /usr/src/modules/alsa-driver-0.4# > ... > When I try to start the TkAlsaMixer (from the ALSA homepage) I get this: > > "Original error: The ALSA sound driver was not detected in this system." > > What do I miss ?? > > TIA! > Philipp > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Missing ALSA driver?
Hi guys, We installed Sarge / 2.6 kernel + ALSA on a Dell computer. Some documents claim that we need a particular driver: "emu10k1x" to handle Dell's variation of the SBLive! card. However, that particular driver doesn't seem to have come with Sarge's version of ALSA. Does anyone know why we might be missing this and/or what the most reasonable way to remedy the problem is? Thanks, Christian -- Christian Convey Computer Scientist, Naval Undersea Warfare Center Newport, RI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
alsa driver configuration
hello all. I am trying to configure alsa drivers on an unstable box. I compiled them with make-kpkg without a problem and the deb installed. Following instructions on the web I added a file alsa to /etc/modutils... which debconf prompted and moved to /etc/alsa/modutils/0.9 and linked back. I do not get any errors until I try to run alsamixer, which causes a function snd_ctl_open failed for default: no such file or directory. I was wondering just how to set this default? Thank you in advance for any assistance. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with alsa driver.
Hello :) i'm actually trying to install alsa driver. But is such expecting some problems ... When i use 'modprobe snd-sb16' command, the driver isn't recognize my card, he said it's not here or busy. My card is a Pnp card, so i have configured isapnp tools, and all seems to be allright... If someone as a way.. Bye :) -- Pierre Dupuis ([EMAIL PROTECTED]) MusicReview (http://home.nordnet.fr/~pdupuis) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing ALSA driver?
BTW, the output of "lspci -v" for this card is: :02:09.0 Multimedia audio controller: Creative Labs [SB Live! Value] EMU10k1X Subsystem: Creative Labs: Unknown device 1003 Flags: bus master, medium devsel, latency 64, IRQ 193 I/O ports at ec60 [size=32] Capabilities: [dc] Power Management version 2 Christian Convey wrote: Hi guys, We installed Sarge / 2.6 kernel + ALSA on a Dell computer. Some documents claim that we need a particular driver: "emu10k1x" to handle Dell's variation of the SBLive! card. However, that particular driver doesn't seem to have come with Sarge's version of ALSA. Does anyone know why we might be missing this and/or what the most reasonable way to remedy the problem is? Thanks, Christian -- Christian Convey Computer Scientist, Naval Undersea Warfare Center Newport, RI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing ALSA driver?
On Fri, Dec 03, 2004 at 02:14:45PM -0500, Christian Convey wrote: > Does anyone know why we might be missing this and/or what the most > reasonable way to remedy the problem is? Have you installed alsa-source? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing ALSA driver?
On Fri, 03 Dec 2004 20:20:08 +0100, Christian Convey wrote: > Some documents claim that we need a particular driver: "emu10k1x" to > handle Dell's variation of the SBLive! card. However, that particular > driver doesn't seem to have come with Sarge's version of ALSA. The ALSA driver is named 'snd-emu10k1x'. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing ALSA driver?
Thanks. I did rebuild alsa, and it seems I successfully caused that driver to be created. Then I ran "make install", then "depmod", and rebooted (just in case - windows habit). Then I ran "alsaconf" and the card was found! Now when I run "lsmod", life look good: emu10k1_gp 3584 0 gameport4512 1 emu10k1_gp However, things still don't seem to work right. When I run "alsamixer" I get this: alsamixer: function snd_ctl_open failed for default: No such device When I run 'dmesg' I get 298 of lines of output that look similar to this: snd_emu10k1x: Unknown symbol snd_rawmidi_set_ops snd_emu10k1x: Unknown symbol snd_rawmidi_receive snd_emu10k1x: Unknown symbol snd_rawmidi_transmit snd_emu10k1x: Unknown symbol snd_rawmidi_new snd_emu10k1x: Unknown symbol snd_rawmidi_set_ops snd_emu10k1x: Unknown symbol snd_rawmidi_receive snd_emu10k1x: Unknown symbol snd_rawmidi_transmit snd_emu10k1x: Unknown symbol snd_rawmidi_new And idea what I might be doing wrong? Thanks again for the help. - Christian Thomas Hood wrote: On Fri, 2004-12-03 at 20:49, Christian Convey wrote: Thanks, but when I "modprobe snd-emu10k1x" I get a not-found error. If you get a current alsa-modules package the emu10k1x driver is in there. E.g., alsa-modules-2.4.27-1-686 version 1.0.6a+5 contains the file /lib/modules/2.4.27-1-686/updates/alsa/snd-emu10k1x. If there is no alsa-modules package available in the archive that matches your kernel version then you can build one from alsa-source using the make-kpkg utility. -- Christian Convey Computer Scientist, Naval Undersea Warfare Center Newport, RI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing ALSA driver?
On Fri, Dec 03, 2004 at 03:39:42PM -0500, Christian Convey wrote: > Then I ran "make install", then "depmod", and rebooted (just in case - In Debian you shouldn't run "make install." Use make-kpkg to build your kernel and modules, then install with dpkg. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa driver configuration
-- Mark Whaite <[EMAIL PROTECTED]> wrote
(on Monday, 27 January 2003, 10:02 AM -0800):
> I am trying to configure alsa drivers on an unstable box. I compiled
> them with make-kpkg without a problem and the deb installed.
> Following instructions on the web I added a file alsa to
> /etc/modutils... which debconf prompted and moved to
> /etc/alsa/modutils/0.9 and linked back. I do not get any errors until
> I try to run alsamixer, which causes a function snd_ctl_open failed
> for default: no such file or directory. I was wondering just how to
> set this default? Thank you in advance for any assistance.
But did you run '/etc/init.d/alsa start' as root? If so, and no errors
occurred, what does 'lsmod' (again, as root) return? -- do you see your
soundcard listed ("snd-cardname")?
Also, did you create the sound devices? I.e., do /dev/mixer* and
/dev/dsp*, etc., exist? If not, you may need to run
'/usr/share/doc/alsa-base/examples/snddevices', again as root, to create
them. Then run '/etc/init.d/alsa stop && /etc/init.d/alsa start' again
and see what happens.
Something else I had happen recently: I was using a stock kernel, but
needed to compile lirc and alsa drivers, which require full kernel
source. The problem was that I didn't give the kernel a revision name
matching the stock kernel, which meant that even once the modules
installed, they weren't in the appropriate place for the active kernel.
(I could have solved it using the appropriate kernel revision name, but
I did it instead by compiling and installing my own kernel using
make-kpkg, and then compiling and installing the modules.)
--
Matthew Weier O'Phinney
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa driver configuration
On Mon, 2003-01-27 at 13:55, Matthew Weier O'Phinney wrote:
But did you run '/etc/init.d/alsa start' as root? If so, and no errors
occurred, what does 'lsmod' (again, as root) return? -- do you see your
soundcard listed ("snd-cardname")?
It just isn't working on unstable, and I don't know why. I can load the various modules by hand--but /etc/init.d/alsa, although it gives no errors, loads no sound modules and unloads soundcore if it is already loaded.
Re: alsa driver configuration
On Tue, Jan 28, 2003 at 12:46:11PM -0600, Michael D. Harnois wrote:
> On Mon, 2003-01-27 at 13:55, Matthew Weier O'Phinney wrote:
>
> > But did you run '/etc/init.d/alsa start' as root? If so, and no errors
> > occurred, what does 'lsmod' (again, as root) return? -- do you see your
> > soundcard listed ("snd-cardname")?
>
> It just isn't working on unstable, and I don't know why. I can load the
> various modules by hand--but /etc/init.d/alsa, although it gives no
> errors, loads no sound modules and unloads soundcore if it is already
> loaded.
Have a look at your module configuration file. I believe that alsa or
the alsa source packager renamed the modules from snd-card-foo.o to
snd-foo.o and you'll need to take "-card" out of the module name
accordingly.
Alternatively, you might want to just grab the sample version out of
the examples directory (in the also source's /usr/share/doc directory)
and read the documentation for the last line or two you need to tag
on.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa driver configuration
On Wed, 2003-01-29 at 10:41, Brian McGroarty wrote: > Have a look at your module configuration file. I believe that alsa or > the alsa source packager renamed the modules from snd-card-foo.o to > snd-foo.o and you'll need to take "-card" out of the module name > accordingly. > > Alternatively, you might want to just grab the sample version out of > the examples directory (in the also source's /usr/share/doc directory) > and read the documentation for the last line or two you need to tag > on. > A great idea, but unfortunately, it made no difference :( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Building ALSA Driver in Debian
I have 2.2.17 Debian on a Dell 4100 with SoundBlasterPCI_64V which I've guessed to use the ens1371 driver. The ALSA INSTALL documentation has, so far, seemed to get me the furthest. Here is some hopefully important output. I would appreciate any guidance anyone has to help me get sound from my speakers. Thank you. Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #15 Fri May 11 19:41:04 /etc/localtime 2001 ./configure --with-sequencer=yes --with-oss=yes --with-card-ens1371 alsaconf, selecting ens1371 and soundblaster PCI 64 128,128,128. Loading driver: Starting sound driver: (ens1371) . Setting the PCM volume to 100% and the Master output volume to 50% The ALSA sound driver was not detected in this system. Could not initialize the mixer, the card was probably not detected correctly. Computer01:/usr/src/modules/alsa-driver# lsmod Module Size Used by snd-mixer-oss 4436 0 (unused) snd-mixer 29552 0 [snd-mixer-oss] snd44960 0 [snd-mixer-oss snd-mixer] Computer01:/usr/src/modules/alsa-driver# modprobe snd-ens1371 /lib/modules/2.2.17/sound/snd-seq-device.o: unresolved symbol snd_device_new_R222bb4a0 /lib/modules/2.2.17/sound/snd-seq-device.o: insmod /lib/modules/2.2.17/sound/snd-seq-device.o failed /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_info_free_entry_Rad4ecc07 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_device_free_R3250731f /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_unregister_device_R734c711d /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_info_create_entry_R069a6063 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_control_register_ioctl_Re946b9c1 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol __wake_up_R083f3f66 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_control_unregister_ioctl_R7ad2059c /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_info_unregister_R3fd0d924 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_register_device_R0fd687a8 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol __pollwait_R9e07a1aa /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_info_register_Ra40dd393 /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol snd_device_new_R222bb4a0 /lib/modules/2.2.17/sound/snd-timer.o: insmod /lib/modules/2.2.17/sound/snd-timer.o failed /lib/modules/2.2.17/sound/snd-timer.o: insmod snd-ens1371 failed Patrick Greenwood Omaha, Nebraska USA __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
installing alsa-driver-linuxant under Debian
Hi, I've reported a problem in the linmodems mailing-list, but perhaps someone can help me here. This is quite urgent (I hope to have some answer before tomorrow). I'm trying to build alsa-driver-linuxant on a Debian/unstable machine (amd64). I got the alsa-driver-linuxant Debian package from the Linuxant web site; this is a package that contains the sources, that need to be compiled (this is normally done in the postinst script, but the build fails). So, if someone here has managed to build the driver under Debian (or has some URL about someone who did), I'd be very interested. For the moment, I did the following. First the kernel sources must be installed (the headers are not sufficient): # apt-get install linux-source-2.6.30 $ cd /usr/src $ atool -eqx linux-source-2.6.30.tar.bz2 $ cd linux-source-2.6.30 $ make oldconfig && make prepare # cd /usr/lib/alsa-driver-linuxant # ./configure --with-kernel=/usr/src/linux-source-2.6.30 --with-build=/usr/src/linux-kbuild-2.6.30 # make but "make" fails with an error about scripts/genksyms/genksyms that can't be found. I could solve this error by adding GENKSYMS = /usr/src/linux-kbuild-2.6.30/scripts/genksyms/genksyms to the Makefile.conf (in /usr/lib/alsa-driver-linuxant). Then I tried "make" again, but got the following error: /bin/sh: scripts/mod/modpost: No such file or directory scripts/mod/modpost is also in /usr/src/linux-kbuild-2.6.30, but I don't know which file to modify in order to provide the path. Just in case, I tried MODPOST = /usr/src/linux-kbuild-2.6.30/scripts/mod/modpost in alsa-driver-linuxant's Makefile.conf, but this has no effect. TIA for any information, -- Vincent Lefèvre - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Kernel 2.4.17 and Alsa driver 0.5.12
Hi All, can alsa driver 0.5.12a be run with kernel 2.4.17? the doc talks only about 2.0 and 2.2 kernels? Are they upward compatible or are there any known problems? thanks, deva Get free e-mail and a permanent address at http://www.amexmail.com/?A=1
Re: Building ALSA Driver in Debian
Hey, You're also supposed to add a bunch of stuff to the /etc/modules.conf file too (actually in Debian, you add it to /etc/modutils/, and then run update-modutils) check out http://www.alsa-project.org/alsa-doc/alsa-howto/ Cameron Matheson On Sat, May 12, 2001 at 10:55:47PM -0700, Patrick Greenwood wrote: > I have 2.2.17 Debian on a Dell 4100 with SoundBlasterPCI_64V which I've > guessed > to use the ens1371 driver. The ALSA INSTALL documentation has, so far, seemed > to get me the furthest. Here is some hopefully important output. I would > appreciate any guidance anyone has to help me get sound from my speakers. > Thank > you. > > Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version 2.95.2 2220 (Debian > GNU/Linux)) #15 Fri May 11 19:41:04 /etc/localtime 2001 > > ./configure --with-sequencer=yes --with-oss=yes --with-card-ens1371 > > alsaconf, selecting ens1371 and soundblaster PCI 64 128,128,128. > > Loading driver: > Starting sound driver: (ens1371) . > Setting the PCM volume to 100% and the Master output volume to 50% > The ALSA sound driver was not detected in this system. > Could not initialize the mixer, the card was probably > not detected correctly. > > Computer01:/usr/src/modules/alsa-driver# lsmod > Module Size Used by > snd-mixer-oss 4436 0 (unused) > snd-mixer 29552 0 [snd-mixer-oss] > snd 44960 0 [snd-mixer-oss snd-mixer] > > Computer01:/usr/src/modules/alsa-driver# modprobe snd-ens1371 > /lib/modules/2.2.17/sound/snd-seq-device.o: unresolved symbol > snd_device_new_R222bb4a0 > /lib/modules/2.2.17/sound/snd-seq-device.o: insmod > /lib/modules/2.2.17/sound/snd-seq-device.o failed > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_info_free_entry_Rad4ecc07 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_device_free_R3250731f > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_unregister_device_R734c711d > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_info_create_entry_R069a6063 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_control_register_ioctl_Re946b9c1 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol __wake_up_R083f3f66 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_control_unregister_ioctl_R7ad2059c > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_info_unregister_R3fd0d924 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_register_device_R0fd687a8 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol __pollwait_R9e07a1aa > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_info_register_Ra40dd393 > /lib/modules/2.2.17/sound/snd-timer.o: unresolved symbol > snd_device_new_R222bb4a0 > /lib/modules/2.2.17/sound/snd-timer.o: insmod > /lib/modules/2.2.17/sound/snd-timer.o failed > /lib/modules/2.2.17/sound/snd-timer.o: insmod snd-ens1371 failed > > Patrick Greenwood > Omaha, Nebraska USA > > > __ > Do You Yahoo!? > Yahoo! Auctions - buy the things you want at great prices > http://auctions.yahoo.com/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Compiling alsa-driver-1.0.17 for Debian etch
Dear All
*This email just sums up what I did to compile the alsa-driver-1.0.17
with the hope that it might
be useful to someone else.* (1) to (6) is information provided by Nigel
Henry (see 'Alsa not
working properly' on debian-user@lists.debian.org). I am using etch
(see system information).
Following Nigel I:
(1) Downloaded alsa driver 1.0.17 to /path/to/alsa_driver.
(2) Installed build-essential, kernel-package and linux-headers-2.6.18-6.
(3) Changed to /path/to/alsa_driver and unpacked tar-file using 'tar
xjvf alsa-driver-1.0.17.tar.bz2'.
(4) Changed to alsa-driver-1.0.17 (directory with unpacked files).
(5) Typed './configure'.
(6) Typed 'make'.
After (6) I got the following error-messages:
/path/to/Alsa_drivers/alsa-driver-1.0.17/acore/rtctimer.c:4: error:
redefinition of 'is_power_of_2'
/path/to/Alsa_drivers/alsa-driver-1.0.17/include/adriver.h:1424: error:
previous definition of 'is_power_of_2' was here
make[3]: *** [/path/to/Alsa_drivers/alsa-driver-1.0.17/acore/rtctimer.o]
Fehler 1
make[2]: *** [/path/to/Alsa_drivers/alsa-driver-1.0.17/acore] Fehler 2
make[1]: *** [_module_/path/to/Alsa_drivers/alsa-driver-1.0.17] Fehler 2
make: *** [compile] Fehler 2
By commenting out (/* static inline ... */)
static inline int is_power_of_2(unsigned long n)
{
return (n != 0 && ((n & (n - 1)) == 0));
}
in '/path/to/Alsa_drivers/alsa-driver-1.0.17/acore/rtctimer.c' I typed
'make' again and everything worked fine.
(7) Typed 'make install' to complete the job.
(8) Rebooted the laptop.
(9) Saw the right version nr in '/proc/asound/version'
(10) Alsa control seemed to work better so far.
s.
System information
*uname -a* tells me that I am using *Linux foosys 2.6.18-6-686 #1 SMP
Thu Oct 9 15:52:18 UTC 2008 i686 GNU/Linux*.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem in installing alsa driver on Etch
I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or Fedora. On Ubuntu/Kubuntu I just install the build-essential, kernel-package, and the kernel headers for the running kernel, then a simple ./configure, make, and as root, make install, and the alsa driver is upgraded. I have installed the same packages on my Etch install for the etchnhalf kernel. Both the AMD64, and the x86 versions of the kernel are installed. On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, gets the sound working. The etchnhalf kernel also uses alsa driver 1.0.15, but in this case there is no sound. I know the sound works ok on this Etch install, as I have a 2.6.26 kernel from the Musix repo installed, which uses alsa driver 1.0.16. Now the problem: Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to find a soundcard. I have a 1.0.15 alsa driver (and later ones) from the Alsa site. I want to see if the alsa driver 1.0.15 from the Alsa site is in some way different from the one installed with the etchnhalf kernel. Now to simply upgrade the driver. Having unpacked the driver, I cd to the driver folder, and run ./configure, and I don't see any problems. Then I run make, which runs for a bit, then stops with the problem below. make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/pcmcia' make[2]: Entering directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[1]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15' make -C /lib/modules/2.6.24-etchnhalf.1-486/build SUBDIRS=/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15 CPP="gcc -E" CC="gcc" modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop. make[2]: *** [/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore] Error 2 make[1]: *** [_module_/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' make: *** [compile] Error 2 [EMAIL PROTECTED]:~/Downloads/Alsa-drivers/alsa-driver-1.0.15$ The relevant lines where the problem appears are below. make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop. I don't understand what I need to do to fix this, as the makefile which is below, doesn't make any reference to CFLAGS, and have no idea where to add the line EXTRA_CFLAGS, if that's all is needed. Makefile for alsa-driver-1.0.15/acore below. ifndef SND_TOPDIR SND_TOPDIR=.. endif include $(SND_TOPDIR)/toplevel.config include $(SND_TOPDIR)/Makefile.conf clean-files := info.c pcm.c pcm_native.c control.c hwdep.c init.c rawmidi.c \ sound.c timer.c memalloc.c misc.c export-objs := control.o device.o info.o info_oss.o init.o isadma.o memory.o \ misc.o misc_driver.o sound.o sound_oss.o \ pcm.o pcm_lib.o pcm_memory.o pcm_misc.o pcm_native.o \ rawmidi.o timer.o hwdep.o memalloc.o wrappers.o include $(SND_TOPDIR)/alsa-kernel/core/Makefile snd-objs += wrappers.o misc_driver.o ifeq ($(CONFIG_SND_DEBUG_MEMORY),y) snd-objs += memory_debug.o endif snd-page-alloc-objs += memory_wrapper.o snd-hpet-objs := hpetimer.o obj-$(CONFIG_SND_HPET) += snd-hpet.o obj-$(CONFIG_SND_BIT32_EMUL) += ioctl32/ include $(SND_TOPDIR)/Rules.make info.c: info.inc info.patch $(SND_TOPDIR)/alsa-kernel/core/info.c pcm.c: pcm.patch $(SND_TOPDIR)/alsa-kernel/core/pcm.c pcm_native.c: pcm_native.patch $(SND_TOPDIR)/alsa-kernel/core/pcm_native.c control.c: control.patch $(SND_TOPDIR)/alsa-kernel/core/control.c hwdep.c: hwdep.patch $(SND_TOPDIR)/alsa-kernel/core/hwdep.c init.c: init.patch $(SND_TOPDIR)/alsa-kernel/core/init.c rawmidi.c: rawmidi.patch $(SND_TOPDIR)/alsa-kernel/core/rawmidi.c sound.c: sound.patch $(SND_TOPDIR)/alsa-kernel/core/sound.c timer.c: timer.patch $(SND_TOPDIR)/alsa-kernel/core/timer.c memalloc.c: memalloc.patch memalloc.inc memalloc.inc1 $(SND_TOPDIR)/alsa-kernel/core/memalloc.c misc.c: misc.patch $(SND_TOPDIR)/alsa-kernel/core/misc.c Any help with this problem will be very gratefully received. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ASUS u52 builtin microphone (alsa-driver-linuxant)
Hello Everyone, So I've been trying to get my laptop (ASUS u52) microphone to work. First off, if anybody knows how to get the builtin microphone to work without bothering with alsa-driver-linuxant, or if I didn't know the correct google-foo to find a binary package for alsa-driver-linuxant that works with debian, then please cut me off. Beginning how I (unsuccessfully) attempted to solve the problem, I read at [1] that the workarounds at [2] worked for the u52. It says that installing the linuxant alsa drivers fixes problems with the microphone. So, I grab the latest version of the driver, unzip, and try to install the deb package. It fails on configure, so I install the kernel sources, make menuconfig (just accepting the defaults), etc until I have a completely prepared source distribution. After copying over version.h from /usr/include/linux, alsa-driver-linuxant configures correctly. Here's where it begins to fall apart. I'm running debian unstable amd64 on linux kernel version 2.6.39. First I find that include/linux/smp_lock.h was removed from kernel 2.6.39. I try to get away with just copying over the blob from version 2.6.38 (which seemed to work). However, now CC is complaining about implicit declaration of functions, which means the headers are all included but the functions aren't there anymore AFAIK, which means that the interface changed, which makes me think that the whole driver is incompatible with kernel 2.6.39. Is this true? Is it possible for me to run the driver without downgrading the kernel? Though I suppose it is an option... Thanks for any and all help, rbmj PS: If exact errors would help, I can supply. This seems like a bigger issue (again, AFAIK) then just a normal compilation error. [1] http://ubuntuforums.org/showthread.php?t=1668887 [2] http://ubuntuforums.org/showthread.php?t=1460790 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110710182045.4f1fc...@blairasus.mason.homeunix.org
The ALSA driver in potato is very outdated :-(
Hi All, I had some troubles with ALSA drivers, provided with potato. I sent a message to one of their developers, and this is what I received: > you are using a very old version of ALSA. > please upgrade your driver/libs from www.alsa-project.org > > all azt2320 cards are well supported now. So now I have two questions. 1) How can I upgrade the ALSA drivers in potato so that I wouldn't break the debian packaging system (Is there something like kernel-package available for them)? 2) Are there any plans to upgrade the ALSA drivers for potato (eg. placing the new version in proposed-updates)? -- Greetings Wojciech M. Zabolotny http://www.ise.pw.edu.pl/~wzab <--> [EMAIL PROTECTED] http://www.gnupg.org Gnu Privacy Guard - protect your mail & data with the FREE cryptographic system
SB PCI64 - alsa driver or kernel 2.2.x ?
Hello, I'm desperate SB 64 PCI user trying to get that card to live. I've tried alsa 0.3.0pre4, and followed all the instructions for SB PCI cards, module is loaded, mixer is up but no sound is coming out of speaker. I'm using kde 1.1.2. I kindly ask for any help, experience on using alsa on SB PCI card. Can I somehow track the problem ? And also, like said somewhere, kernels 2.2.x do have support for SB PCI cards, but the question is which kernel is stable enough to put it on without too much risk. In some thread in debian user it was 2.2.6 or 2.2.7 recomended for this matter. Is there any change on this ? Thanks for answers. Regards, Robert Rozman [EMAIL PROTECTED]
Re: Problem in installing alsa driver on Etch
Nigel Henry wrote: I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or Fedora. On Ubuntu/Kubuntu I just install the build-essential, kernel-package, and the kernel headers for the running kernel, then a simple ./configure, make, and as root, make install, and the alsa driver is upgraded. I have installed the same packages on my Etch install for the etchnhalf kernel. Both the AMD64, and the x86 versions of the kernel are installed. On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, gets the sound working. The etchnhalf kernel also uses alsa driver 1.0.15, but in this case there is no sound. I know the sound works ok on this Etch install, as I have a 2.6.26 kernel from the Musix repo installed, which uses alsa driver 1.0.16. Now the problem: Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to find a soundcard. I have a 1.0.15 alsa driver (and later ones) from the Alsa site. I want to see if the alsa driver 1.0.15 from the Alsa site is in some way different from the one installed with the etchnhalf kernel. Now to simply upgrade the driver. Having unpacked the driver, I cd to the driver folder, and run ./configure, and I don't see any problems. Then I run make, which runs for a bit, then stops with the problem below. make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/pcmcia' make[2]: Entering directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[1]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15' make -C /lib/modules/2.6.24-etchnhalf.1-486/build SUBDIRS=/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15 CPP="gcc -E" CC="gcc" modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop. make[2]: *** [/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore] Error 2 make[1]: *** [_module_/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' make: *** [compile] Error 2 [EMAIL PROTECTED]:~/Downloads/Alsa-drivers/alsa-driver-1.0.15$ The relevant lines where the problem appears are below. make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop. I don't understand what I need to do to fix this, as the makefile which is below, doesn't make any reference to CFLAGS, and have no idea where to add the line EXTRA_CFLAGS, if that's all is needed. Makefile for alsa-driver-1.0.15/acore below. ifndef SND_TOPDIR SND_TOPDIR=.. endif include $(SND_TOPDIR)/toplevel.config include $(SND_TOPDIR)/Makefile.conf clean-files := info.c pcm.c pcm_native.c control.c hwdep.c init.c rawmidi.c \ sound.c timer.c memalloc.c misc.c export-objs := control.o device.o info.o info_oss.o init.o isadma.o memory.o \ misc.o misc_driver.o sound.o sound_oss.o \ pcm.o pcm_lib.o pcm_memory.o pcm_misc.o pcm_native.o \ rawmidi.o timer.o hwdep.o memalloc.o wrappers.o include $(SND_TOPDIR)/alsa-kernel/core/Makefile snd-objs += wrappers.o misc_driver.o ifeq ($(CONFIG_SND_DEBUG_MEMORY),y) snd-objs += memory_debug.o endif snd-page-alloc-objs += memory_wrapper.o snd-hpet-objs := hpetimer.o obj-$(CONFIG_SND_HPET) += snd-hpet.o obj-$(CONFIG_SND_BIT32_EMUL) += ioctl32/ include $(SND_TOPDIR)/Rules.make info.c: info.inc info.patch $(SND_TOPDIR)/alsa-kernel/core/info.c pcm.c: pcm.patch $(SND_TOPDIR)/alsa-kernel/core/pcm.c pcm_native.c: pcm_native.patch $(SND_TOPDIR)/alsa-kernel/core/pcm_native.c control.c: control.patch $(SND_TOPDIR)/alsa-kernel/core/control.c hwdep.c: hwdep.patch $(SND_TOPDIR)/alsa-kernel/core/hwdep.c init.c: init.patch $(SND_TOPDIR)/alsa-kernel/core/init.c rawmidi.c: rawmidi.patch $(SND_TOPDIR)/alsa-kernel/core/rawmidi.c sound.c: sound.patch $(SND_TOPDIR)/alsa-kernel/core/sound.c timer.c: timer.patch $(SND_TOPDIR)/alsa-kernel/core/timer.c memalloc.c: memalloc.patch memalloc.inc memalloc.inc1 $(SND_TOPDIR)/alsa-kernel/core/memalloc.c misc.c: misc.patch $(SND_TOPDIR)/alsa-kernel/core/misc.c Any help with this problem will be very gratefully received. Nigel. yee seem to have done all the things right. yet: see on 'their' alsasite for how exactly to install (under etch or lenny. does not make a diffrence technically) i am afriad to tell you all the things you know already but nevertheless: on my machine (etch and lenny (24,5
Re: Problem in installing alsa driver on Etch
On Wed, Dec 3, 2008 at 05:35, steef <[EMAIL PROTECTED]> wrote: > Nigel Henry wrote: >> >> I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or Fedora. >> On Ubuntu/Kubuntu I just install the build-essential, kernel-package, and >> the kernel headers for the running kernel, then a simple ./configure, make, >> and as root, make install, and the alsa driver is upgraded. >> >> I have installed the same packages on my Etch install for the etchnhalf >> kernel. Both the AMD64, and the x86 versions of the kernel are installed. >> >> On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound >> doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, gets >> the sound working. >> >> The etchnhalf kernel also uses alsa driver 1.0.15, but in this case there >> is no sound. >> >> I know the sound works ok on this Etch install, as I have a 2.6.26 kernel >> from the Musix repo installed, which uses alsa driver 1.0.16. >> >> Now the problem: >> >> Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to find >> a soundcard. I have a 1.0.15 alsa driver (and later ones) from the Alsa >> site. I want to see if the alsa driver 1.0.15 from the Alsa site is in some >> way different from the one installed with the etchnhalf kernel. Now to >> simply upgrade the driver. Having unpacked the driver, I cd to the driver >> folder, and run ./configure, and I don't see any problems. Then I run make, >> which runs for a bit, then stops with the problem below. >> >> make[2]: Leaving directory >> `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/pcmcia' >> make[2]: Entering directory >> `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' >> make[2]: Leaving directory >> `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' >> make[1]: Leaving directory >> `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15' >> make -C /lib/modules/2.6.24-etchnhalf.1-486/build >> SUBDIRS=/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15 CPP="gcc -E" >> CC="gcc" modules >> make[1]: Entering directory >> `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' >> scripts/Makefile.build:46: *** CFLAGS was changed in >> "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix >> it to use EXTRA_CFLAGS. Stop. >> make[2]: *** >> [/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore] Error 2 >> make[1]: *** >> [_module_/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15] Error 2 >> make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' >> make: *** [compile] Error 2 >> [EMAIL PROTECTED]:~/Downloads/Alsa-drivers/alsa-driver-1.0.15$ >> >> The relevant lines where the problem appears are below. >> >> make[1]: Entering directory >> `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' >> scripts/Makefile.build:46: *** CFLAGS was changed in >> "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix >> it to use EXTRA_CFLAGS. Stop. >> >> I don't understand what I need to do to fix this, as the makefile which is >> below, doesn't make any reference to CFLAGS, and have no idea where to add >> the line EXTRA_CFLAGS, if that's all is needed. >> Any help with this problem will be very gratefully received. Do you have the correct header files for that kernel? > > yee seem to have done all the things right. > > yet: > > see on 'their' alsasite for how exactly to install (under etch or lenny. > does not make a diffrence technically) > > i am afriad to tell you all the things you know already but nevertheless: > > on my machine (etch and lenny (24,5) > > i made as root /usr/src/alsa after having installed the 'appropriate' > kernel-headers. > > I downloaded from the alsawebsite the newest alsadriver into /usr/src/alsa > and unpacked the package there. > > 1. i downloaded the alsa-library (libs) and alsa-utils into my > home-directory. > > 2. i did: (for years already) in /usr/src/alsa as root > ./configure --with-cards=[your-card] (in my case hda-intel) > make > and make install. this will install your chosen driver(s) into the > kernel-modules library. > > 3. i unzip and install alsa-lib and alsa-utils as root in my home-directory. I have found that this is not necessarily needed, e.g. alsa-drivers 1.0.18 works fine with everything else being 1.0.17 > 4. i reboot No need for that, just sudo modprobe snd-hda-intel > and do as user $alsamixer to get the channels working. > > you still can do #alsaconf to look for the appropriate drivers and install > these sounddrivers (with some reserve) the alsa-chaps seem to have the > intention to remove this trait. alsaconf is really meant for some cases of ISA cards, and often using alsaconf on pci cards just confuses the primary issue(s). Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem in installing alsa driver on Etch
On Wednesday 03 December 2008 20:38, Kelly Clowers wrote: > On Wed, Dec 3, 2008 at 05:35, steef <[EMAIL PROTECTED]> wrote: > > Nigel Henry wrote: > >> I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or > >> Fedora. On Ubuntu/Kubuntu I just install the build-essential, > >> kernel-package, and the kernel headers for the running kernel, then a > >> simple ./configure, make, and as root, make install, and the alsa driver > >> is upgraded. > >> > >> I have installed the same packages on my Etch install for the etchnhalf > >> kernel. Both the AMD64, and the x86 versions of the kernel are > >> installed. > >> > >> On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound > >> doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, > >> gets the sound working. > >> > >> The etchnhalf kernel also uses alsa driver 1.0.15, but in this case > >> there is no sound. > >> > >> I know the sound works ok on this Etch install, as I have a 2.6.26 > >> kernel from the Musix repo installed, which uses alsa driver 1.0.16. > >> > >> Now the problem: > >> > >> Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to > >> find a soundcard. I have a 1.0.15 alsa driver (and later ones) from the > >> Alsa site. I want to see if the alsa driver 1.0.15 from the Alsa site is > >> in some way different from the one installed with the etchnhalf kernel. > >> Now to simply upgrade the driver. Having unpacked the driver, I cd to > >> the driver folder, and run ./configure, and I don't see any problems. > >> Then I run make, which runs for a bit, then stops with the problem > >> below. > > Do you have the correct header files for that kernel? The header files for 2.6.18-6-686, and for etchnhalf x86, and AMD64 kernels are installed. I just tried to upgrade the alsa driver on another machine (Etch again) which has kernel version 2.6.18-5 on it. As I normally do, I did this from where the 1.0.15 alsa driver was located in my /home/user directory. ./configure ran to completion with no problems, and make also ran to completion. I didn't run make install as root because the sounds are working fine on this machine, which has an audigy2 soundblaster card. Now I switch back to the other machine, which has the hda intel card, and try the same procedure with the 2.6.18-6 kernel. ./configure runs to completion. Make also runs to completion. Now I run as root make install, and it runs to completion. I reboot, and now cat /proc/asound/version shows 1.0.15 for the 2.6.18-6 kernel. I'd tried this back in October with the same kernel, but couldn't upgrade the alsa driver. The only difference today is that after make ran to completion, I su'ed to root, and ran make -n install, which I thought might give some output without actually upgrading the alsa driver. I did get some output, which didn't say much, then ran make install which upgraded the alsa driver from 1.0.12rc1 to 1.0.15. None of this explains why make is throwing in the towel when trying to upgrade the alsa driver with the etchnhalf kernels, with the following output. make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in "/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop. And I get the same with the AMD64 kernel. It's all a bit academic, as the Musix 2.6.26 kernel, using alsa driver 1.0.16 has working sounds, and now having upgraded the alsa driver on the 2.6.18-6 kernel from 1.0.12rc1 to 1.0.15, that also has working sounds for the hda intel card on my Asus M2N-X Plus mobo. I think I'll leave the etchnhalf kernels alone for a while, on the premise that, If it works, don't mess with it, and the sounds are working with 2 kernels, but not the etchnhalf ones. Nigel. > Kelly Clowers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem in installing alsa driver on Etch
Nigel Henry wrote: On Wednesday 03 December 2008 20:38, Kelly Clowers wrote: On Wed, Dec 3, 2008 at 05:35, steef <[EMAIL PROTECTED]> wrote: <...> I think I'll leave the etchnhalf kernels alone for a while, on the premise that, If it works, don't mess with it, and the sounds are working with 2 kernels, but not the etchnhalf ones. mm this is intriguing, the more because i am listening right now on a etchnhalf_loaded machine to one of my favoured jazz_music_files. but, of course: the chance on a ceteris-paribus construction seems minimal. steef <.> -- steef van duin publicist, research-journalist -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ASUS u52 builtin microphone (alsa-driver-linuxant)
On Sun, 10 Jul 2011 18:20:45 -0400 "Robert Blair Mason Jr." wrote: > Hello Everyone, > > So I've been trying to get my laptop (ASUS u52) microphone to work. > First off, if anybody knows how to get the builtin microphone to work > without bothering with alsa-driver-linuxant, or if I didn't know the > correct google-foo to find a binary package for alsa-driver-linuxant > that works with debian, then please cut me off. > > Beginning how I (unsuccessfully) attempted to solve the problem, I > read at [1] that the workarounds at [2] worked for the u52. It says > that installing the linuxant alsa drivers fixes problems with the > microphone. So, I grab the latest version of the driver, unzip, and > try to install the deb package. It fails on configure, so I install > the kernel sources, make menuconfig (just accepting the defaults), etc > until I have a completely prepared source distribution. After copying > over version.h from /usr/include/linux, alsa-driver-linuxant > configures correctly. > > Here's where it begins to fall apart. I'm running debian unstable > amd64 on linux kernel version 2.6.39. First I find that > include/linux/smp_lock.h was removed from kernel 2.6.39. I try to get > away with just copying over the blob from version 2.6.38 (which seemed > to work). However, now CC is complaining about implicit declaration > of functions, which means the headers are all included but the > functions aren't there anymore AFAIK, which means that the interface > changed, which makes me think that the whole driver is incompatible > with kernel 2.6.39. Is this true? > > Is it possible for me to run the driver without downgrading the > kernel? Though I suppose it is an option... > > Thanks for any and all help, > > rbmj > > PS: If exact errors would help, I can supply. This seems like a > bigger issue (again, AFAIK) then just a normal compilation error. > > [1] http://ubuntuforums.org/showthread.php?t=1668887 > [2] http://ubuntuforums.org/showthread.php?t=1460790 > > Update: I went through some of the code and started to replace some of the lines that caused errors with the latest alsa-driver git blobs. These fixed some of the errors, but not all of them. However, after giving up, installing pulseaudio, giving up on that, rebooting a few times, updating a few times, giving up on that, and then forgetting about it, the microphone magically started working. -- rbmj -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110718145556.16ce7...@blairasus.mason.homeunix.org
Re: The ALSA driver in potato is very outdated :-(
On Wed, 14 Jun 2000, Wojciech Zabolotny wrote: > So now I have two questions. > 1) How can I upgrade the ALSA drivers in potato so that I wouldn't break >the debian packaging system (Is there something like kernel-package >available for them)? Add the apt source.conf lines for woody, run apt-get install alsa-source (and whatever other alsa apps you might use). You can then remove the source.conf lines for woody after you upgrade all the alsa stuff. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: The ALSA driver in potato is very outdated :-(
On Wed, Jun 14, 2000 at 03:09:16PM +0200, Wojciech Zabolotny wrote: > Hi All, > > I had some troubles with ALSA drivers, provided with potato. > I sent a message to one of their developers, and this is what I received: > > > you are using a very old version of ALSA. > > please upgrade your driver/libs from www.alsa-project.org > > > > all azt2320 cards are well supported now. > > So now I have two questions. > 1) How can I upgrade the ALSA drivers in potato so that I wouldn't break >the debian packaging system (Is there something like kernel-package >available for them)? If you install the ALSA source package, it installs in /usr/src/modules. Running make-kpkg modules_image from usr/src/linux /should package up everything /usr/src/modules (and not make modules included with the kernel). I'm not sure if the source of the debian package was modified to make this work or not... [snip] > Greetings > Wojciech M. Zabolotny > http://www.ise.pw.edu.pl/~wzab <--> [EMAIL PROTECTED] > > http://www.gnupg.org Gnu Privacy Guard - protect your mail & data > with the FREE cryptographic system > -- Pat Mahoney <[EMAIL PROTECTED]> He knows not how to know who knows not also how to unknow. -- Sir Richard Burton
Re: The ALSA driver in potato is very outdated :-(
I installed the following debs from the woody archive or from incoming.debian.org. My kernel is a 2.2.15 that I compiled myself. In order to install the alsa-modules package I had to give the "--force-depends" option to dpkg. alsa-base_0.5.8a-1.deb alsa-modules-2.2.15_0.5.8a-1+2.2.15-1_i386.deb alsa-utils_0.5.8-1.deb esound-common_0.2.18-2.deb esound-alsa_0.2.18-2.deb libasound1_0.5.8-1.deb libesd-alsa0_0.2.18-2.deb gamix_1.09p11-1.deb Tip: If you use xmms, choose the esd output plugin. -- Thomas Hood > Hi All, > > I had some troubles with ALSA drivers, provided with potato. > I sent a message to one of their developers, and this is what I received: > > > you are using a very old version of ALSA. > > please upgrade your driver/libs from www.alsa-project.org > > > > all azt2320 cards are well supported now. > > So now I have two questions. > 1) How can I upgrade the ALSA drivers in potato so that I wouldn't break >the debian packaging system (Is there something like kernel-package >available for them)? > 2) Are there any plans to upgrade the ALSA drivers for potato >(eg. placing the new version in proposed-updates)?
How to get the ALSA driver to start at boot?
I managed to get my sound setup to the point where I can get sound by running 'modprobe snd-via8233' and some commands for unmuting the appropriate channels. However, I would prefer the driver being loaded by the ALSA entry in /etc/init.d, since the alsa config files seem to load the driver with a bunch of options and perhaps I need them later [also, simply throwing the driver in /etc/modules seems like an ad-hoc solution, something I don't like by principle]. Now it says in the 'INSTALL' doc (that comes with alsa-drivers) that one has to add some aliases to /etc/modules.conf. I think (I'm not very good at reading bash-scripts yet) that /etc/init.d/alsa also looks for a 'snd-card-0' alias, created in /etc/modules.conf (one of the requested aliases) and despite adding the requested lines to modules.conf, those lines have dissapeared from modules.conf again [which, I gather from the remarks in modules.conf, was to be expected]. Consequently, alsa fails at boottime. BTW, I couldn't use alsaconf, because that doesn't support my driver yet. P.S. I think a correct setup also unmutes the mixer automagically, but assuming I can't get it to work other than using the ad-hoc solution: in what file should I put the commands that unmute the mixers? sincerely -- Ivo Wever [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get the ALSA driver to start at boot?
On Fri, Jun 14, 2002 at 04:00:04PM +0200, Ivo Wever wrote: > I managed to get my sound setup to the point where I can get sound > by running 'modprobe snd-via8233' and some commands for unmuting the > appropriate channels. However, I would prefer the driver being loaded by > the ALSA entry in /etc/init.d, since the alsa config files seem to load > the driver with a bunch of options and perhaps I need them later > [also, simply throwing the driver in /etc/modules seems like an ad-hoc > solution, something I don't like by principle]. I'm assuming that you're using ALSA 0.9. > Now it says in the 'INSTALL' doc (that comes with alsa-drivers) that one > has to add some aliases to /etc/modules.conf. I think (I'm not very good > at reading bash-scripts yet) that /etc/init.d/alsa also looks for a > 'snd-card-0' alias, created in /etc/modules.conf (one of the requested > aliases) and despite adding the requested lines to modules.conf, those > lines have dissapeared from modules.conf again [which, I gather from the > remarks in modules.conf, was to be expected]. Consequently, alsa fails > at boottime. You should add the correct module lines (that you would put in modconf) in /etc/alsa/modutils/0.9 > P.S. I think a correct setup also unmutes the mixer automagically, but > assuming I can't get it to work other than using the ad-hoc solution: in > what file should I put the commands that unmute the mixers? When you shut down, alsa-utils should have an init.d script that saves your current mixer settings, and will restore them on the next boot. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get the ALSA driver to start at boot?
Simon Law wrote: Ivo Wever wrote: I'm assuming that you're using ALSA 0.9. Yes, I am. You should add the correct module lines (that you would put in modconf) in /etc/alsa/modutils/0.9 I couldn't gather the format of a module line from the alsa docs and it isn't in the example. What should such a line look like? sincerely, -- Ivo Wever [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get the ALSA driver to start at boot?
On Fri, 2002-06-14 at 07:18, Ivo Wever wrote: > Simon Law wrote: > > You should add the correct module lines (that you would put in > > modconf) in /etc/alsa/modutils/0.9 > > > I couldn't gather the format of a module line from the alsa docs and it > isn't in the example. What should such a line look like? > Here's what I added to /etc/modutils/aliases: # ALSA portion alias char-major-116 snd # OSS/Free portion alias char-major-14 soundcore #ALSA portion alias snd-card-0 snd-cmipci # OSS/Free portion alias sound-slot-0 snd-card-0 # OSS/Free portion - card #1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-12 snd-pcm-oss Replace the snd-cmipci above with snd-via8233. You can also place the lines above in their own file under /etc/modutils/. Run /sbin/update-modules to regenerate the /etc/modules.conf file. Install alsa-utils and use alsamixer-0.9 to set your output levels. That should do it. Steven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Solved: How to get the ALSA driver to start at boot?
Steven Yap wrote: Ivo Wever wrote: Simon Law wrote: You should add the correct module lines (that you would put in modconf) in /etc/alsa/modutils/0.9 I couldn't gather the format of a module line from the alsa docs and it isn't in the example. What should such a line look like? Here's what I added to /etc/modutils/aliases: [..] Replace the snd-cmipci above with snd-via8233. You can also place the lines above in their own file under /etc/modutils/. Run /sbin/update-modules to regenerate the /etc/modules.conf file. Thanks, it worked. I now even have sound under X, even though artsd doesn't start with the option for alsa-compatability. I've yet to figure out why :) sincerely, -- Ivo Wever [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Solved: How to get the ALSA driver to start at boot?
- Original Message - From: "Ivo Wever" <[EMAIL PROTECTED]> To: "debian-user" Sent: Monday, June 17, 2002 1:37 AM Subject: Solved: How to get the ALSA driver to start at boot? > Thanks, it worked. I now even have sound under X, even though artsd > doesn't start with the option for alsa-compatability. I've yet to > figure out why :) > Hi! The artsd from libarts-alsa doesn't like alsa 0.5 when the alsa option is activated, I think. If you have alsa 0.5 you'll have to install 0.9.x or so. Or just keep the OSS setting or "autodetect" ;). And you might have to run /usr/share/doc/alsa-base/examples/snddevices once if you haven't done so yet (creates the alsa devices in /dev). Cheers, Stephan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problem with alsa driver for Sound blaster 16 in etch (kernel 2.6)
I have used sb16 since kernel 2.0 It still works with both oss and alsa in sarge(kernel 2.4): oss: isa-pnp isapnp_disable=1 sound uart401 sb io=0x220 irq=5 dma=1 dma16=5 alsa: isa-pnp isapnp_disable=1 snd-sb16 isapnp=0 but in etch (kernel 2.6), oss driver works I pass noisapnp kernel option during boot but alsa does not work it should work but after I reinstall etch it doesn't work no matter how hard I try -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
pulseaudio blaming alsa driver [was: Re: youtube videos choppy in Testing and Iceape]
H.S. wrote: > H.S. wrote: >> Hello, >> >> Since I upgraded a few weeks ago after the release of Lenny, I have >> noticed that youtube videos in Iceape browser are kind of choppy. This >> wasn't the case earlier before the upgrade. >> >> Anybody else also having this problem? >> >> Thanks. > > Further problems. I am using Ekiga. I have noticed that since last few > weeks, the audio from ekiga is also getting random short pauses (very > short, like clicks). This was not there earlier. > > Nobody else is having problems in Testing since the release in video and > audio playbacks? > > Thanks. > I think the problem is with alsa. I just noticed that I am getting these message in /var/log/syslog: Apr 4 23:15:12 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:15:16 red last message repeated 11 times Apr 4 23:15:16 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:15:17 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:15:44 red last message repeated 74 times Apr 4 23:15:44 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:15:45 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:15:57 red last message repeated 33 times Apr 4 23:15:57 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:15:57 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:16:01 red last message repeated 11 times Apr 4 23:16:01 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:16:02 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:16:09 red last message repeated 20 times Apr 4 23:16:09 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:16:09 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:16:40 red last message repeated 81 times Apr 4 23:16:47 red last message repeated 21 times Apr 4 23:16:48 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:16:48 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:17:00 red last message repeated 34 times Apr 4 23:17:01 red /USR/SBIN/CRON[9643]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 4 23:17:01 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:17:10 red last message repeated 24 times Anybody know what is going one? Thanks. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem with alsa driver for Sound blaster 16 in etch (kernel 2.6)
Long Wind wrote: > but in etch (kernel 2.6), oss driver works > I pass noisapnp kernel option during boot > but alsa does not work do you have snd-oss loaded - just post lsmod | grep snd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: pulseaudio blaming alsa driver [was: Re: youtube videos choppy in Testing and Iceape]
On Sat,04.Apr.09, 23:21:27, H.S. wrote: > Apr 4 23:16:48 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us > up to write new data to the device, but there was actually nothing to > write! Most likely this is an ALSA driver bug. Please report this issue > to the PulseAudio developers. ... > Anybody know what is going one? Did you try taking pulseaudio out of the equation? (BTW, why do you need pulseaudio on the local machine?) Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: pulseaudio blaming alsa driver [was: Re: youtube videos choppy in Testing and Iceape]
Andrei Popescu wrote: > On Sat,04.Apr.09, 23:21:27, H.S. wrote: > >> Apr 4 23:16:48 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us >> up to write new data to the device, but there was actually nothing to >> write! Most likely this is an ALSA driver bug. Please report this issue >> to the PulseAudio developers. > ... >> Anybody know what is going one? > > Did you try taking pulseaudio out of the equation? (BTW, why do you need > pulseaudio on the local machine?) > > Regards, > Andrei hmm .. I am trying to kill pulseaudio and work without it, but it appears that as soon as I start and audio/video application PA also starts. PA is actually a great piece of software. I can hotplut a USB headset and start using it seamlessly. I can use my PCI audio for one application and USB headset for another. I can route audio from one sink to another without having to restart an application! It is quite neat. Not to mention the fact that I can set volume for each individual application. Other than that, of course, there is that network sound thing. But by far the most useful thing for my on my desktop is the ease with which to attach an audio device (USB, e.g.) and start using it. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
(solved) Re: problem with alsa driver for Sound blaster 16 in etch (kernel 2.6)
Thanks! For alsa driver to work in etch(kernel 2.6) the two modules below are needed: snd-sb16 isapnp=0 snd-mixer-oss On Thu, Sep 17, 2009 at 7:24 PM, Emanoil Kotsev wrote: > Long Wind wrote: > >> but in etch (kernel 2.6), oss driver works >> I pass noisapnp kernel option during boot >> but alsa does not work > > do you have snd-oss loaded - just post > > lsmod | grep snd > > > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
