++
Description : ALSA MIDI connection minder
Watches for new MIDI ports (both from hardware devices and from
applications), and uses a rules configuration file to automatically make
connections. Will also handle reconnecting if a port is removed and later
added back, like when a device is
++
Description : ALSA MIDI connection minder
Watches for new MIDI ports (both from hardware devices and from
applications),
and uses a rules configuration file to automatically make connections.
Will also handle reconnecting if a port is removed and later added back,
like
when a device is
: TinyALSA is a small library to interface with ALSA in the
Linux kernel.
TinyALSA is a small library to interface with ALSA in the Linux kernel.
The aims are:
Provide a basic pcm and mixer API.
If it's not absolutely needed, don't add it to the API.
Avoid supporting complex and unnecessary
Package: wnpp
Owner: gregor herrmann
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libmidi-alsa-perl
Version : 1.22
Upstream Author : Peter Billam
* URL : https://metacpan.org/release/MIDI-ALSA
* License
Package: wnpp
Severity: wishlist
Owner: Takashi Sakamoto
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: libhitaki
Version : 0.2.0
Upstream Contact: Takashi Sakamoto
* URL : https://github.com/alsa-project/libhitaki
* License : LGPL-3
Package: wnpp
Severity: wishlist
Owner: Tobias Heider
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: alsa-ucm-conf-asahi
Version : 1
URL : https://github.com/AsahiLinux/alsa-ucm-conf-asahi
* License : BSD-3-Clause
Description : ALSA Use Case
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: bluez-alsa
Version : 2.1.0
Upstream Author : Arkadiusz Bokowy
* URL : https://github.com/Arkq/bluez-alsa
* License : Expat
Programming Lang
for Alsa
C.A.V.A. is a bar spectrum audio visualizer for the Linux terminal using ALSA,
pulseaudio or fifo buffer for input. This program is not intended for
scientific use. It's written to look responsive and aesthetic when used to
visualize music.
Cava would supplement other audio monit
turns a joystick into
a MIDI controller for the ALSA sequencer infrastructure.
.
Its original purpose was to test the MIDI interface of terminatorX but
that turned out to be fun, so it made it here in the hope that it could
be useful for other experiments.
.
For a more detailed description on
turns a joystick into
a MIDI controller for the ALSA sequencer infrastructure.
.
Its original purpose was to test the MIDI interface of terminatorX but
that turned out to be fun, so it made it here in the hope that it could
be useful for other experiments.
.
For a more detailed description on what
Package: wnpp
Severity: wishlist
Owner: Hanno Zulla
* Package name: ruby-alsa-rawmidi
Version : 0.3.1
Upstream Author : Ari Russo
* URL : https://rubygems.org/gems/alsa-rawmidi
* License : Apache-2.0
Programming Lang: Ruby
Description : Realtime MIDI
like that a while ago, and have been happy with PA
> since I did so. But at this point in time, it should not be necessary
> to add it.
>
> > This basically tells ALSA applications - which don't know anything
> > about PA - to use the PulseAudio-ALSA backend. Thus,
>>>>> "Mario" == Mario Lang writes:
Mario> That is what I was thinking as well, but just recently I had
Mario> to killall pulseaudio to be able to access my ALSA device
Mario> again.
Pulseaudio explicitly bypasses the dmix plugin and opens the als
50] main input error: ES_OUT_SET_(GROUP_)PCR is called too late
(pts_delay increased to 320 ms)
[0xf4c11150] main input error: ES_OUT_RESET_PCR called
...
The key point is, first I thought it's some video decoder problems, but I
was wrong!
I've tried different setups and discov
: ALSA to JACK bridge
This package provides two applications, zita-a2j and zita-j2a.
They allow to use an ALSA device as a Jack client, to provide
additional capture (a2j) or playback (j2a) channels.
.
Functionally these are equivalent to the alsa_in and alsa_out
clients that come with
for ALSA
QasTool is a collection of desktop tools for the
Linux sound system ALSA.
.
The tools included are:
- QasConfig - browser for the ALSA configuration tree
- QasHctl - mixer for ALSA's High level Control Interface
- QasMixer - simple mixer with features similar to alsa
Package: wnpp
Severity: wishlist
Owner: Sebastian
Dear Maintainer,
* Package name: qasconfig
Version : 0.2.0
Upstream Author : Sebastian Holtermann
* URL : http://xwmw.org/qasconfig
* License : GPL-3
Programming Lang: C++
Description : ALSA
Alessio Treglia, le Sat 06 Aug 2011 11:25:06 +0200, a écrit :
> This is just to set a beginning point, but I'm not an experienced
> kfreebsd porter, so any help is appreciated :)
Well there is nothing specific to kfreebsd here, you can develop and
test it all on a Linux box.
Samuel
--
To UNSUB
Hi again,
and sorry for the late reply.
On Mon, Aug 1, 2011 at 6:05 PM, Samuel Thibault wrote:
> Understood. But my point is that liboss-salsa already provides
> ALSA-compatibility headers. Digging a bit more, it seems
> libdssialsacompat installs its alsa headers into /usr/include/
DSSI plugins able to compile on non-Linux architectures.
Understood. But my point is that liboss-salsa already provides
ALSA-compatibility headers. Digging a bit more, it seems
libdssialsacompat installs its alsa headers into /usr/include/dssi/alsa,
so there shouldn't be a conflict actually.
Hi Samuel, hi all,
On Sun, Jul 31, 2011 at 11:31 AM, Samuel Thibault wrote:
> Interesting. How can we make this interact with liboss-salsa?
Good point, this library provides just a small compatibility layer to
make DSSI plugins able to compile on non-Linux architectures.
*-bsd porters can sure
Alessio Treglia, le Sun 31 Jul 2011 11:21:52 +0200, a écrit :
> libdssialsacompat is simply an extraction from and repackaging of
> the code from alsa-lib, necessary to support DSSI on non-ALSA
> systems.
Interesting. How can we make this interact with liboss-salsa?
Samuel
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia
* Package name: libdssialsacompat
Version : 1.0.8
Upstream Author : Sean Bolton
* URL : http://smbolton.com/linux.html
* License : GPL
Programming Lang: C
Description : DSSI ALSA compatibility
the sound system ALSA powered by a QT GUI
QasMixer is a graphical mixer application for the Linux sound
architexture ALSA. It is powered by a QT4 GUI with customized slider
and checkbox widgets that dynamically adjust their size to use
the available window space optimally.
By using the ALSA mixer
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia
* Package name: qmidiarp
Version : 0.3.9
Upstream Author : Frank Kober
* URL : http://qmidiarp.sourceforge.net/
* License : GPL
Programming Lang: C++
Description : MIDI arpeggiator for ALSA
adjustable equalizer plugin for ALSA
It can be adjusted using an ALSA compatible mixer, like alsamixergui or
alsamixer.
Alsaequal uses the Eq CAPS LADSPA Plugin for audio processing, actually
alsaequal is a generic LADSPA plugin interface with real-time access to
the LADSPA controls (the LADSPA
: ALSA MIDI Metronome
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100904150155.17524.18834.report...@bird
Package: wnpp
Severity: wishlist
Owner: Adrian Knoth
* Package name: a2jmidid
Version : 6
Upstream Author : Nedko Arnaudov
* URL : http://home.gna.org/a2jmidid/
* License : GPL
Programming Lang: C
Description : daemon for exposing legacy ALSA MIDI in
forge.net/
* License : GPL
Programming Lang: C++
Description : Qt4/C++ wrapper for ALSA sequencer
This library is a C++ wrapper around the ALSA library sequencer interface,
using Qt4 objects, idioms and style. ALSA sequencer provides software
support for MIDI technology on Linux.
--
T
Description : Libsalsa is a library providing an ALSA interface on top of
OSS
This packages provides a compatibility layer between OSS and ALSA: it
is ABI-compatible with libasound (actually using alsa's headers), and
just makes OSS ioctls.
The idea would be to have libsalsa-dev pr
On 2009-02-22 Elimar Riesebieter wrote:
> * Andreas Metzler [090222 17:42 +0100]
>> On 2009-02-22 Elimar Riesebieter wrote:
[...]
>>> I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
>>> amd64 gives:
>>> ...
>>> check
On 2009-02-22 Elimar Riesebieter wrote:
> Package: wnpp
> Severity: normal
> Hi Debian ALSA developers,
> I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
> amd64 gives:
> ...
> checking for strip... strip
> checking for cross-compiler... i4
Package: wnpp
Severity: normal
Hi Debian ALSA developers,
I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
amd64 gives:
...
checking for strip... strip
checking for cross-compiler... i486-i486-pc-linux-gnu-gcc
checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu
ng Lang: C
Description : serial to ALSA MIDI adapter
ttymidi feeds the ALSA MIDI sequencer with MIDI commands read from
standard serial-like devices.
It can be used with devices that don't have a standard 5-pin DIN
connector, but speak (or can be made to speak) the MIDI protocol,
such as th
Wow, that's the first Debian installer that made it all the way
through on this machine.
Thanks!
--alan
On Dec 13, 2007 2:38 AM, Holger Levsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Wednesday 12 December 2007 15:00, Alan Ezust wrote:
> > True, I *can* install debian, except that I was trying t
Hi,
On Wednesday 12 December 2007 15:00, Alan Ezust wrote:
> True, I *can* install debian, except that I was trying to use Etch,
> and etch's installer crashed in the middle of its process, leaving me
> with an un-bootable system, due to the recent-ness of my computer.
You could try the etch inst
oblem was fixed, but knoppix and etch both don't work.
Anyway, I read up some more on bugs.ubuntu.com
https://bugs.launchpad.net/alsa-utils/+bug/29597
This bug explains what's going on with alsaconf.
On Dec 11, 2007 8:27 AM, Josselin Mouette <[EMAIL PROTECTED]> wrote:
> Le ma
mailing list, if ubuntu team isn't
> able to package alsa properly you should rant on UBUNTU ml and forums.
No, if Ubuntu doesn’t work properly, you can simply install Debian
instead.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`.
On Mon, Dec 10, 2007 at 06:21:16PM -0500, Alan Ezust wrote:
> I want to run alsaconf. It's not there.
> i want to run snddevices script. It's not there either.
> I search and search the ubuntu forums. In the end, it seems everyone
> in ubuntu-land must resort to compiling a
On Tuesday 11 December 2007, Alan Ezust wrote:
> I want to run alsaconf. It's not there.
> i want to run snddevices script. It's not there either.
> I search and search the ubuntu forums. In the end, it seems everyone
> in ubuntu-land must resort to compiling alsa from SO
I want to run alsaconf. It's not there.
i want to run snddevices script. It's not there either.
I search and search the ubuntu forums. In the end, it seems everyone
in ubuntu-land must resort to compiling alsa from SOURCE to get sound
on their laptop. WTF?!?
Obviously ubuntu is havi
Package: wnpp
Severity: wishlist
Owner: Samuel Mimram <[EMAIL PROTECTED]>
* Package name: ocaml-alsa
Version : 0.1.0
Upstream Author : Samuel Mimram <[EMAIL PROTECTED]>
* URL : http://savonet.sf.net/
* License : GPL
Programming Lang: ocaml + C
iption : MIDI monitor using ALSA sequencer and KDE user interface
KMidimon can monitor a MIDI data stream, in order to diagnose
a malfunctioning piece of equipment or to examine the contents
of a MIDI sequence during playback.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
On Sun, Sep 17, 2006 at 12:59:27PM +0900, Nobuhiro Iwamatsu wrote:
> Package: wnpp
> Owner: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
> Severity: wishlist
>
> * Package name: btsco
you might want to have a look at pkg-bluetooth (
http://wiki.debian.org/Bluetooth ) as well. Eventually it might be
On Sun, 2006-09-17 at 09:46 +0200, martin f krafft wrote:
> also sprach Nobuhiro Iwamatsu <[EMAIL PROTECTED]> [2006.09.17.0559 +0200]:
> > * Package name: btsco
>
> Please coordinate with Kel and Russell (on CC), who have been
> working on this package for a while. One of the reasons that we h
Hi ,
On Sun, 17 Sep 2006 09:46:04 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
Thank you for your news.
I did not know other people were working.
> Please coordinate with Kel and Russell (on CC), who have been
> working on this package for a while. One of the reasons that we have
> not rel
Hi Nobuhiro,
On Sunday 17 September 2006 17:46, martin f krafft wrote:
> also sprach Nobuhiro Iwamatsu <[EMAIL PROTECTED]> [2006.09.17.0559 +0200]:
> > * Package name: btsco
>
> Please coordinate with Kel and Russell (on CC), who have been
> working on this package for a while. One of the reas
also sprach Nobuhiro Iwamatsu <[EMAIL PROTECTED]> [2006.09.17.0559 +0200]:
> * Package name: btsco
Please coordinate with Kel and Russell (on CC), who have been
working on this package for a while. One of the reasons that we have
not released it yet is because we want to make btsco a daemon th
ming Lang: C
Description : ALSA drivers and daemons for using bluetooth audio devices
This software provides the environment to use the Bluetooth
headphone with linux.
And this is composed of the ALSA device driver for bluetooth
and the software to control.
Currently supports
* Bl
On Sun, Aug 13, 2006 at 03:02:22PM +0100, martin f krafft wrote:
> also sprach Paul Brossier <[EMAIL PROTECTED]> [2006.08.13.1418 +0100]:
> > * Package name: python-alsaaudio
>
> Sweet. An ITP for a package already in unstable...
moo :P
at that time, the package was not listed in bugs.d.o, a
On Sun, Aug 13, 2006 at 07:25:07PM +0100, martin f krafft wrote:
> also sprach Kevin Mark <[EMAIL PROTECTED]> [2006.08.14.1917 +0100]:
> > does that imply that an ITP is not checked against the current available
> > packages? Should there be a check?
>
[..]
> The ITP should have been filed a day o
also sprach Kevin Mark <[EMAIL PROTECTED]> [2006.08.14.1917 +0100]:
> does that imply that an ITP is not checked against the current available
> packages? Should there be a check?
The package was hardly current by the time the ITP was filed. In
fact, I did not check whether it was simply a huge ma
On Sun, Aug 13, 2006 at 03:02:22PM +0100, martin f krafft wrote:
> also sprach Paul Brossier <[EMAIL PROTECTED]> [2006.08.13.1418 +0100]:
> > * Package name: python-alsaaudio
>
> Sweet. An ITP for a package already in unstable...
>
does that imply that an ITP is not checked against the curren
also sprach Pierre Habouzit <[EMAIL PROTECTED]> [2006.08.13.1505 +0100]:
> > > * Package name: python-alsaaudio
> >
> > Sweet. An ITP for a package already in unstable...
>
> well I must be blind or sth, but apt-cache search python alsa answer
> nothing f
Le dim 13 août 2006 16:02, martin f krafft a écrit :
> also sprach Paul Brossier <[EMAIL PROTECTED]> [2006.08.13.1418 +0100]:
> > * Package name: python-alsaaudio
>
> Sweet. An ITP for a package already in unstable...
well I must be blind or sth, but apt-cache sear
also sprach Paul Brossier <[EMAIL PROTECTED]> [2006.08.13.1418 +0100]:
> * Package name: python-alsaaudio
Sweet. An ITP for a package already in unstable...
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud De
tion License
Programming Lang: C and Python
Description : Alsa bindings for Python
The PyAlsaAudio package contains bindings for the ALSA sound api.
--
Two notes:
- the package exists in ubuntu edgy, and i'll start from there to make
the debian version of it.
http://packages.ubu
1.0-0 (>= 1.12.0),
libpng12-0 (>= 1.2.8rel), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxi6,
libxinerama1, libxrandr2, libxrender1 (>= 1:0.9.0.2), zlib1g (>= 1:1.2.1)
Filename: pool/main/g/gamix/gamix_1.99.p14.debian1-3_amd64.deb
Size: 40726
MD5sum: 45107d0ce7ba8b7d0cc23cc648805
First, thanks to those who responded to my earlier call.
In addition to people knowledgeable about the ALSA userspace library
I would like to find someone willing to help maintain the driver side.
ALSA drivers are included in Linux 2.6, but we still ship an alsa-source
package for use with Linux
The ALSA packaging team needs help. We really need someone with expertise
in programming for the ALSA library. If you are able to help us, please
contact us at [EMAIL PROTECTED]
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
Package: wnpp
Severity: wishlist
Owner: "Sam Hocevar (Debian packages)" <[EMAIL PROTECTED]>
* Package name: bse-alsa
Version : 0.6.6
Upstream Author : Tim Janik <[EMAIL PROTECTED]>
* URL : http://beast.gtk.org/beast-ftp/v0.6/
* License
: init_kwifimanager_kamodule
ALSA lib pam_hw.c:494:(snd_pam_hw_start) SNDRV_PCM_IOCTL_START
failed:Broken pipe
I hope this give a general idea, there are many more errors,
and I don't know what I am doing? Help Please
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
On Fri, Aug 05, 2005 at 11:40:45AM -0700, Allyn, MarkX A wrote:
> Is there a maintainer for the ALSA Audio drivers/lib/utils?
> Is there a separate email list?
>
> I have some questions about ALSA on both the production and testing
> releases.
trofast:~# apt-cache show a
Hello:
Is there a maintainer for the ALSA Audio drivers/lib/utils?
Is there a separate email list?
I have some questions about ALSA on both the production and testing
releases.
Thank you
Mark Allyn
Description : modular patch bay for Jack audio and Alsa Midi
Patchage provides a graphical interface to connect jack and midi inputs
and outputs. Each application is presented as one box with inputs on
the left and output on the right. Boxes can be moved around and
arranged to have a clear di
Package: wnpp
Severity: wishlist
Owner: "Itay Ben-Yaacov" <[EMAIL PROTECTED]>
* Package name: bluetooth-alsa
Version : 0.4
Upstream Author : Brad Midgley <[EMAIL PROTECTED]>
* URL : http://sourceforge.net/projects/bluetooth-alsa/
* Lice
On Thu, 10 Mar 2005 22:00:15 +0100, Thomas Hood wrote:
> Here is another idea. We create a new binary package
> "sound-system-chooser" which contains blacklists for both OSS and ALSA and
> provides a debconf interface that the administrator can use to disable
> either or bot
On Thu, 10 Mar 2005 01:10:12 +0100, Josselin Mouette wrote:
> Davide, would you agree with making gnome-media depend on something like
> "alsa-base | kernel-image-2.4", to ensure sound is working properly upon
> installation?
I don't see why gnome-media should be inv
nel-image package add its own file in the
/etc/hotplug/blacklist.d/ directory?
Or if you mean "it doesn't work if you also have a 2.4 kernel-image
installed", how is this any better or worse than if you have alsa-base
blacklisting?
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Thu, 10 Mar 2005 02:50:04 +0100, Steve Langasek wrote:
> Considering you're talking about solutions that require updates to
> kernel-image packages *anyway*, why has no one suggested adding the
> necessary blacklist entries to these packages?
k-i packages aren't the right place to put the blac
Goswin Brederlow writes:
> Thomas Hood <[EMAIL PROTECTED]> writes:
> > So to be clear the alternatives suggested so far are:
> >
> > 1. The two-package approach
> >
> > * oss blacklists ALSA modules
> > * alsa-base blacklists OSS modules
> &
[EMAIL PROTECTED] writes:
>> Thomas Hood <[EMAIL PROTECTED]> writes:
>> > If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a
>> > problem because in that case nothing enforces the mutual exclusion of OSS
>> > and ALSA modules. If
On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> Considering you're talking about solutions that require updates to
> kernel-image packages *anyway*, why has no one suggested adding the
> necessary blacklist entries to these packages? Far better than removing
> Thomas Hood <[EMAIL PROTECTED]> writes:
> > If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a
> > problem because in that case nothing enforces the mutual exclusion of OSS
> > and ALSA modules. If linux26 doesn't install alsa-base then per
Le jeudi 10 mars 2005 à 08:17 +0100, Goswin von Brederlow a écrit :
> The kernel could blacklist alsa modules by default and the alsa-base
> would divert that to blacklist oss. That sounds the simplest.
It isn't possible to divert files in /etc.
--
.''`.
Thomas Hood <[EMAIL PROTECTED]> writes:
> On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
>> Actually, the proposed solution that raised some approval was to split
>> out the ALSA modules, just like the pcmcia modules.
>
>
> I raised this idea on #debian-
On Thu, Mar 10, 2005 at 12:12:37AM +0100, Thomas Hood wrote:
> On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
> > Actually, the proposed solution that raised some approval was to split
> > out the ALSA modules, just like the pcmcia modules.
> I raised this idea on
Le jeudi 10 mars 2005 Ã 00:12 +0100, Thomas Hood a Ãcrit :
> On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
> > Actually, the proposed solution that raised some approval was to split
> > out the ALSA modules, just like the pcmcia modules.
>
>
> I raised thi
Le mercredi 09 mars 2005 Ã 20:33 +0100, Thomas Hood a Ãcrit :
> In theory I guess there should be an oss package that was the homologue of
> the alsa-base package. It would include files that would blacklist ALSA
> modules, just as alsa-base blacklists OSS modules. These packa
On Mon, 07 Mar 2005 20:40:40 +0100, Josselin Mouette wrote:
> Actually, the proposed solution that raised some approval was to split
> out the ALSA modules, just like the pcmcia modules.
I raised this idea on #debian-kernel and it was shot down.[0]
[0]http://lists.alioth.debian.org/pip
On Mon, 07 Mar 2005 00:10:12 +0100, Christoph Hellwig wrote:
> It's not a depency in any way. I play sound just fine with OSS drivers
> without the ALSA mess getting in my way anywhere.
On Mon, 07 Mar 2005 13:50:10 +0100, Josselin Mouette wrote:
> Without alsa-base installe
On Mon, 07 Mar 2005 13:50:10 +0100, Josselin Mouette wrote:
> Without alsa-base installed, hotplug and discover will load both
> modules, resulting in various disasters depending on the hardware. It's
> not because things work with your setup that they are suitable for a
> stab
Le lundi 07 mars 2005 Ã 12:53 -0600, Steve Greenland a Ãcrit :
> On 07-Mar-05, 11:06 (CST), Josselin Mouette <[EMAIL PROTECTED]> wrote:
> > And the workaround we use for this bug is to blacklist one module when
> > two of them provide the same functionality. The blacklist
On 07-Mar-05, 11:06 (CST), Josselin Mouette <[EMAIL PROTECTED]> wrote:
> And the workaround we use for this bug is to blacklist one module when
> two of them provide the same functionality. The blacklists are in the
> alsa-base package, which should then be installed when A
Le lundi 07 mars 2005 à 07:26 -0600, Steve Greenland a écrit :
> > Without alsa-base installed, hotplug and discover will load both
> > modules, resulting in various disasters depending on the hardware. It's
> > not because things work with your setup that they are suitable
On 07-Mar-05, 06:23 (CST), Josselin Mouette <[EMAIL PROTECTED]> wrote:
> Le lundi 07 mars 2005 ? 00:03 +0100, Christoph Hellwig a ?crit :
> > It's not a depency in any way. I play sound just fine with OSS drivers
> > without the ALSA mess getting in my way anywhe
Le lundi 07 mars 2005 à 00:03 +0100, Christoph Hellwig a écrit :
> On Fri, Mar 04, 2005 at 02:41:27PM +0100, Josselin Mouette wrote:
> > When you install an alsa-modules package for the 2.4 kernel, you get
> > alsa-base per the dependencies. However, when you install sarge with a
On Fri, Mar 04, 2005 at 02:41:27PM +0100, Josselin Mouette wrote:
> When you install an alsa-modules package for the 2.4 kernel, you get
> alsa-base per the dependencies. However, when you install sarge with a
> 2.6 kernel, alsa-base doesn't end up being installed.
It's not a
Le dimanche 06 mars 2005 Ã 11:53 +0100, Thomas Hood a Ãcrit :
> On Fri, 04 Mar 2005 20:20:10 +0100, Josselin Mouette wrote:
> > As long as the linux26 installation ends up with both sound modules
> > loaded, that's a bug that needs to be fixed, though. Another option
> >
On Sun, 06 Mar 2005 00:20:13 +0100, Paul Hampson wrote:
> Hmm. I would think that the better solution (the less surprising
> solution) would be to leave out the ALSA modules from the Debian
> kernel package, since we have a seperate package of ALSA modules
> which _does_ depend
Josselin Mouette wrote:
> When you install an alsa-modules package for the 2.4 kernel, you get
> alsa-base per the dependencies. However, when you install sarge with a
> 2.6 kernel, alsa-base doesn't end up being installed. The result is that
> for most sound cards, both OSS and
Hi.
Josselin Mouette wrote:
As long as the linux26 installation ends up with both sound modules
loaded, that's a bug that needs to be fixed, though. Another option
would be to put the alsa modules in separate packages, just like pcmcia
modules.
That definetly sounds much better ;).
Kind re
On Sat, Mar 05, 2005 at 12:01:47PM +0100, Josselin Mouette wrote:
> Le samedi 05 mars 2005 à 00:44 +0100, Goswin von Brederlow a écrit :
> > Exactly. I don't have alsa-base installed on any of my 2.6.x systems
> > and some of them have sound and some don't. None of them
Le samedi 05 mars 2005 à 00:44 +0100, Goswin von Brederlow a écrit :
> Exactly. I don't have alsa-base installed on any of my 2.6.x systems
> and some of them have sound and some don't. None of them have
> problems.
>
> A depends would be too strong. A recommends/sugge
Thomas Viehmann <[EMAIL PROTECTED]> writes:
> Josselin Mouette wrote:
>> 2.6 kernel, alsa-base doesn't end up being installed. The result is that
>> for most sound cards, both OSS and ALSA modules end up installed,
>> resulting in various and random proble
[Nikita V. Youshchenko]
> Maybe it's better just not to provide oss drivers for chips supported
> by alsa? AFAIK OSS will be removed from kernel soon...
It may or may not be removed soon - I note that it isn't listed in
Documentation/feature-removal-schedule.txt in kernel 2.6.11
> When you install an alsa-modules package for the 2.4 kernel, you get
> alsa-base per the dependencies. However, when you install sarge with a
> 2.6 kernel, alsa-base doesn't end up being installed. The result is that
> for most sound cards, both OSS and ALSA modules
Le vendredi 04 mars 2005 à 15:29 +0100, Thomas Viehmann a écrit :
> Josselin Mouette wrote:
> > 2.6 kernel, alsa-base doesn't end up being installed. The result is that
> > for most sound cards, both OSS and ALSA modules end up installed,
> > resulting in various and rand
Josselin Mouette wrote:
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulting in various and random problems. To avoid that, shouldn't the
kernel-image packages for 2.6 depend on alsa-base?
When you install an alsa-modules package for the 2.4 kernel, you get
alsa-base per the dependencies. However, when you install sarge with a
2.6 kernel, alsa-base doesn't end up being installed. The result is that
for most sound cards, both OSS and ALSA modules end up installed,
resulti
1 - 100 of 170 matches
Mail list logo
