Le Tue, 13 Jun 2006 16:22:24 +1000,
"Claude Yu" <[EMAIL PROTECTED]> a écrit :
> Hi all,
>
> Below is the message I put in Linux Forum early on asking for help but that
> was under Mandrake 2006 distribution and now FC5.
> Yes, I was so naive to move between kernels and thought that the problem
hi alsa-people :)
I'm new to alsa,
I've got two (different) soundcards connected to my PC.
I would like to know if it's possible or not
to send the same output to both soundcards.
I managed to do that by connecting output from first card to line
input of second one, thanks to a jack-double-
Hi Users,
Firstly, I would like to thank all the users that replied to the problem
I had with my Intel HDA sound. The problem was with a version of alsa
that it not have full support. I am still a novice linux and debian user
and the question I would like to ask may seem basic, so I hope you wo
On Tue, 13 Jun 2006, Claude Yu wrote:
> Hi all,
>
> Below is the message I put in Linux Forum early on asking for help but that
> was under Mandrake 2006 distribution and now FC5.
> Yes, I was so naive to move between kernels and thought that the problem
> would have gone.
> I did actually insta
Peter Ho <[EMAIL PROTECTED]> writes:
> My current situation is this. I have an older version of alsa, which I
> obtained using apt-get and then modconf to select the modules for
> snd-hda-intel.
The drivers are part of the kernel. So they are part of your
linux-image-* package.
You shouldn't ne
On Tue, 2006-06-13 at 11:09 +0200, Dominique Michel wrote:
> ??? It is no snd-riptide driver in alsa. I don't know how mandrake can
> found a driver that doesn't exist.
>
> I am affraid at the only thing you can do is to buy a new soundcard if
> you want to have sound in linux with your box. Look
On Tue, 13 Jun 2006 11:59:51 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-06-13 at 11:09 +0200, Dominique Michel wrote:
> > ??? It is no snd-riptide driver in alsa. I don't know how mandrake can
> > found a driver that doesn't exist.
> >
> > I am affraid at the only thing you can do
On Tue, 2006-06-13 at 19:34 +0300, Sergei Steshenko wrote:
> Again, try a live-cd distribution first - it's much simpler than
> compiling ALSA and probably kernel.
>
I think the latest Knoppix should be good - apparently the Riptide
driver is rather new, and it will not be in the kernel until 2.6
Sergei,
Your mail server keep blocking me, can you fix it?
<[EMAIL PROTECTED]>:
194.67.23.20 does not like recipient.
Remote host said: 550 Access from ip address 216.158.38.3 blocked. Visit
http://win.mail.ru/cgi-bin/support_bl?ip=216.158.38.3
Giving up on 194.67.23.20.
Lee
On Tue, 13 Jun 2006, Sergei Steshenko wrote:
> On Tue, 13 Jun 2006 11:59:51 -0400
> Lee Revell <[EMAIL PROTECTED]> wrote:
>
>> On Tue, 2006-06-13 at 11:09 +0200, Dominique Michel wrote:
>>> ??? It is no snd-riptide driver in alsa. I don't know how mandrake can
>>> found a driver that doesn't exist
On Tue, 13 Jun 2006, Lee Revell wrote:
> On Tue, 2006-06-13 at 19:34 +0300, Sergei Steshenko wrote:
>> Again, try a live-cd distribution first - it's much simpler than
>> compiling ALSA and probably kernel.
>>
>
> I think the latest Knoppix should be good - apparently the Riptide
> driver is rathe
On Tue, 2006-06-13 at 10:07 -0700, Bill Unruh wrote:
> On Tue, 13 Jun 2006, Lee Revell wrote:
>
> > On Tue, 2006-06-13 at 19:34 +0300, Sergei Steshenko wrote:
> >> Again, try a live-cd distribution first - it's much simpler than
> >> compiling ALSA and probably kernel.
> >>
> >
> > I think the lat
On Tue, 13 Jun 2006 12:52:28 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> Sergei,
>
> Your mail server keep blocking me, can you fix it?
>
> <[EMAIL PROTECTED]>:
> 194.67.23.20 does not like recipient.
> Remote host said: 550 Access from ip address 216.158.38.3 blocked. Visit
> http://win.mail.
Lee Revell wrote:
> I think it's a problem that FC5 does not have an RPM package containing
> these modules.
>
I think it's a question of cost of maintenance. FC5 is currently on
2.6.12.20 (although you might be forgiven fo thinking is actually
2.6.16-1.2133_FC5). /proc/asound says that we
On Tue, 13 Jun 2006 20:39:08 +0100
John Haxby <[EMAIL PROTECTED]> wrote:
> Lee Revell wrote:
> > I think it's a problem that FC5 does not have an RPM package containing
> > these modules.
> >
> I think it's a question of cost of maintenance. FC5 is currently on
> 2.6.12.20 (although you migh
On Tue, 2006-06-13 at 20:39 +0100, John Haxby wrote:
> Lee Revell wrote:
> > I think it's a problem that FC5 does not have an RPM package containing
> > these modules.
> >
> I think it's a question of cost of maintenance. FC5 is currently on
> 2.6.12.20 (although you might be forgiven fo thin
On Tue, 2006-06-13 at 20:39 +0100, John Haxby wrote:
> On the other hand, perhaps someone would volunteer to de-couple the
> ALSA modules from the rest of the kernel in the kernel build so that
> the ALSA modules can be updated and then we'll get to be able to
> install newer versions of ALSA witho
On Tue, 2006-06-13 at 22:49 +0300, Sergei Steshenko wrote:
> You are "aiming too low".
>
> The true answers are:
>
> 1) drivers running in user space;
Agreed. This would help many things. For example it would solve the
binary only driver issue - vendors that feel the need to develop closed
dri
On Tue, 13 Jun 2006 16:05:40 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-06-13 at 22:49 +0300, Sergei Steshenko wrote:
> > You are "aiming too low".
> >
> > The true answers are:
> >
> > 1) drivers running in user space;
>
> Agreed. This would help many things. For example it w
I'm not going to participate in another binary driver flamewar.
Everything interesting that can be said about the issue has been said.
You're entitled to your opinion.
On Tue, 2006-06-13 at 23:40 +0300, Sergei Steshenko wrote:
> On Tue, 13 Jun 2006 16:05:40 -0400
> Lee Revell <[EMAIL PROTECTED]> w
On Tue, 13 Jun 2006, Lee Revell wrote:
> On Tue, 2006-06-13 at 10:07 -0700, Bill Unruh wrote:
>> On Tue, 13 Jun 2006, Lee Revell wrote:
>>
>>> On Tue, 2006-06-13 at 19:34 +0300, Sergei Steshenko wrote:
Again, try a live-cd distribution first - it's much simpler than
compiling ALSA and pr
On Tue, 13 Jun 2006 16:42:42 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> I'm not going to participate in another binary driver flamewar.
> Everything interesting that can be said about the issue has been said.
> You're entitled to your opinion.
>
> On Tue, 2006-06-13 at 23:40 +0300, Sergei Stes
On Tue, 13 Jun 2006 13:59:36 -0700 (PDT)
Bill Unruh <[EMAIL PROTECTED]> wrote:
> The problem as always id dependencies. Have the modules really beendesinged
> to work on their own, or do they suddenly have weird dependencies to say
> alsalib.
>
Again and again, fully self-contained binary driv
On Tue, 13 Jun 2006, John Haxby wrote:
> Lee Revell wrote:
>> I think it's a problem that FC5 does not have an RPM package containing
>> these modules.
>>
.
>
> On the other hand, perhaps someone would volunteer to de-couple the ALSA
> modules from the rest of the kernel in the kernel build so
On Tue, 13 Jun 2006, Sergei Steshenko wrote:
On Tue, 13 Jun 2006 16:05:40 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
On Tue, 2006-06-13 at 22:49 +0300, Sergei Steshenko wrote:
You are "aiming too low".
The true answers are:
1) drivers running in user space;
Agreed. This would help many
On Tue, 13 Jun 2006 14:19:07 -0700 (PDT)
Bill Unruh <[EMAIL PROTECTED]> wrote:
> Of course it can load that way. That is modules are. The problem is that
> modules are so intimatley connected with the kernel that a module for
> kernel A in general does not have the right entry points for Kernel B.
Bill Unruh wrote:
> The philosophy of Mandrake and Redhat has been that updates are for
> security concerns, not for upgrading the system. Upgrades are handled by
> new releases and that trying to make sure that a particular upgrade works
> together with 3 or 4 different distros would be a logistic
Bill Unruh wrote:
> On Tue, 13 Jun 2006, John Haxby wrote:
>
>>
>> On the other hand, perhaps someone would volunteer to de-couple the ALSA
>> modules from the rest of the kernel in the kernel build so that the ALSA
>> modules can be updated and then we'll get to be able to install newer
>> version
Fernando Lopez-Lezcano wrote:
> Not really necessary. The kernel module utilities have a provision that
> enables you to override the "original" kernel modules. Just put your
> "newer" kernel modules somewhere in:
>
> /lib/modules/`uname -r`/updates/
>
> do a "depmod -a" and those modules should
Hello,
I would like to create a virtual device (pcm) that outputs sound to two pcms
(hw:0,0 and hw:0,4)
How do I write the ,asoundrc file?
Should be a common examople but I could not find one...
--
Yours, Mikhail Ramendik
___
Alsa-user mailing li
On Tue, 2006-06-13 at 23:05 +0100, John Haxby wrote:
> What I was suggesting was pulling out the alsa modules into a
> separate
> kernel-alsa binary RPM, compiled from the same sources as everything
> else. It would then be possible to produce, say, a
> kernel-alsa-1.0.11
> src.rpm that will pr
On Wed, 2006-06-14 at 00:28 +0300, Sergei Steshenko wrote:
> On Tue, 13 Jun 2006 14:19:07 -0700 (PDT)
> Bill Unruh <[EMAIL PROTECTED]> wrote:
>
> > Of course it can load that way. That is modules are. The problem is that
> > modules are so intimatley connected with the kernel that a module for
> >
Hello !
I tested yours advices in a script and this is the result (curiously,
the command modprobe has not writting in the file result but there
produce always the same message : error inserting... no such device).
The problem is that the command 00:10 (the NCTRL port) is not active but
close, a
Hi everybody, I've recently bought this card and it seems to have a midi sequencer and a hardware mixer. I saw in the supported soundcards list that the linux driver doesn't support these options for the moment. I would like to know if these options will be implemented or if it's clearly impossible
On Wed, 2006-06-14 at 01:27 +0200, Frédéric Lenté wrote:
> Hi everybody,
> I've recently bought this card and it seems to have a midi sequencer
> and a hardware mixer. I saw in the supported soundcards list that the
> linux driver doesn't support these options for the moment. I would
> like to kno
On Tue, 13 Jun 2006 19:00:09 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> You do realize that freezing the ABI would amount to freezing kernel
> development, due to the commitment not to break old binary drivers?
>
> Your scheme would have made it impossible to implement suspend/resume or
> r
On Wed, 2006-06-14 at 02:39 +0300, Sergei Steshenko wrote:
> No, I don't.
>
> I realize that there were Windows 95, Windows 98, Windows NT,
> Windows 2000, Windows XP.
>
> Or Solaris 4..10.
>
> Or whatever.
>
> That is, from time to time binary interface specs get updated as
> necessary.
>
> N
https://www.musix.org.ar/wiki/index.php/Anuncio-Musix049#English
Musix 0.49 released!
Download
ftp://ftp.gnu.org/gnu+linux-distros/ututo-e/
https://e.ututo.org.ar/utiles/torrent/
Thanks to the support of the Ututo project, FSF, FSF, Ourproject and to the
usual collaborators, the Musix projec
On Wed, 2006-06-14 at 03:07 +0300, Sergei Steshenko wrote:
> On Tue, 13 Jun 2006 19:43:42 -0400
> Lee Revell <[EMAIL PROTECTED]> wrote:
> > On Wed, 2006-06-14 at 02:39 +0300, Sergei Steshenko wrote:
> > > No, I don't.
> > >
> > > I realize that there were Windows 95, Windows 98, Windows NT,
> > >
On Tue, 2006-06-13 at 23:08 +0100, John Haxby wrote:
> Fernando Lopez-Lezcano wrote:
> > Not really necessary. The kernel module utilities have a provision that
> > enables you to override the "original" kernel modules. Just put your
> > "newer" kernel modules somewhere in:
> >
> > /lib/modules/`
On Wed, 2006-06-14 at 03:07 +0300, Sergei Steshenko wrote:
> One of really nice human features is the ability to understand other
> person's reason.
>
> I want to be able to install updated (ALSA or any Linux for that matter)
> driver
> with no more clicks/keystrokes I need under Windows - howeve
On Tue, 13 Jun 2006 20:50:27 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-06-14 at 03:07 +0300, Sergei Steshenko wrote:
> > One of really nice human features is the ability to understand other
> > person's reason.
> >
> > I want to be able to install updated (ALSA or any Linux for t
On Tue, 13 Jun 2006 19:43:42 -0400
Lee Revell <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-06-14 at 02:39 +0300, Sergei Steshenko wrote:
> > No, I don't.
> >
> > I realize that there were Windows 95, Windows 98, Windows NT,
> > Windows 2000, Windows XP.
> >
> > Or Solaris 4..10.
> >
> > Or whateve
On Tue, 13 Jun 2006 17:15:49 -0700
Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> If your distribution supports it, upgrading alsa kernel modules - for
> example - should be as easy as upgrading any other package (using yum,
> apt-get or the package manager of your choice). I've been doin
Hulin Thibaud wrote:
> # modprobe snd-cs4236 isapnp=0 port=0x530 cport=Ox210 irq=5 dma1=1 dma2=0
x210, not x210
> # cat /sys/devices/pnp0/00:0f/id
> CSC0010
> # cat /sys/devices/pnp0/00:0f/resources
> state = active
> io 0x210-0x217
> # cat /sys/devices/pnp0/00:10/id
> CSC
> # cat /sys/devi
Rene Herman wrote:
> 7) cat /sys/devices/pnp0/00:0f/resources
> 8) echo auto >/sys/devices/pnp0/00:0f/resources
> 9) echo activate >/sys/devices/pnp0/00:0f/resources
Sorry, substitute 00:10 for 00:0f in step 7, 8 and 9.
Rene.
___
Alsa-user mailing li
On Tue, 13 Jun 2006, Fernando Lopez-Lezcano wrote:
>
> Not really necessary. The kernel module utilities have a provision that
> enables you to override the "original" kernel modules. Just put your
> "newer" kernel modules somewhere in:
>
> /lib/modules/`uname -r`/updates/
>
> do a "depmod -a" an
On Tue, 13 Jun 2006 21:41:04 -0700 (PDT)
Bill Unruh <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Jun 2006, Fernando Lopez-Lezcano wrote:
>
> >
> > Not really necessary. The kernel module utilities have a provision that
> > enables you to override the "original" kernel modules. Just put your
> > "newer
48 matches
Mail list logo
