purtroppo il 15 mancherĂ² anche io...
...lowe
----Messaggio
originale----
Da: [EMAIL PROTECTED]
Data: 23-ago-
2007 8.53 AM
A: <[email protected]>
Ogg: Alsa-user
Digest, Vol 16, Issue 24
Send Alsa-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the
World Wide Web, visit
https://lists.sourceforge.
net/lists/listinfo/alsa-user
or, via email, send a message with subject
or body 'help' to
[EMAIL PROTECTED]
You can
reach the person managing the list at
[EMAIL PROTECTED]
sourceforge.net
When replying, please edit your Subject line so it is
more specific
than "Re: Contents of Alsa-user digest..."
Today's
Topics:
1. 2 questions about amixer's output (Zbigniew Baniewski)
2. Re: Invalid CTL (Clemens Ladisch)
3. Re: 2 questions about
amixer's output (Clemens Ladisch)
4. can't get sound on gateway
mx8711 laptop with intel 82801G
(Robert P. J. Day)
5. Re:
Invalid CTL (Loris Caren)
6. Is CX20549 the same as Conexant 5045
for model= options
(Nigel Henry)
7. Re: can't get sound on
gateway mx8711 laptop with intel
82801G (Joris Huizer)
8. Re:
can't get sound on gateway mx8711 laptop with intel
82801G
(Robert P. J. Day)
9. Re: Is CX20549 the same as Conexant 5045 for
model= options
(Bill Unruh)
10. Re: Invalid CTL (Clemens
Ladisch)
----------------------------------------------------------------------
Message: 1
Date: Wed, 22 Aug 2007 16:02:56 +0200
From: Zbigniew
Baniewski <[EMAIL PROTECTED]>
Subject: [Alsa-user] 2 questions about
amixer's output
To: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type:
text/plain; charset=iso-8859-2
1. Does there exist an easy way to
distinguish "output devices" from
"capture devices"? There's not
always appropriate remark in the device's
"name" field.
2. Some
devices have "access" field like: "rw---R--". What this big "R" does
mean?
--
pozdrawiam / regards
Zbigniew Baniewski
------------------------------
Message: 2
Date: Wed, 22 Aug 2007 17:07:
53 +0200
From: Clemens Ladisch <[EMAIL PROTECTED]>
Subject: Re:
[Alsa-user] Invalid CTL
To: Loris Caren <[EMAIL PROTECTED]>
Cc:
[email protected]
Message-ID: <46CC5149.
[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Loris Caren wrote:
> When I try 'amixer contents' (with sound modules
loaded) I get error message
> ALSA lib control.c:909 Invalid CTL
default control default open error
>
> Note that I'm running on a
minimal embedded system
Probably the configuration files in
/usr/share/alsa/ are missing.
Does "aplay -L" output anything?
Regards,
Clemens
------------------------------
Message: 3
Date:
Wed, 22 Aug 2007 17:15:19 +0200
From: Clemens Ladisch
<[EMAIL PROTECTED]>
Subject: Re: [Alsa-user] 2 questions about
amixer's output
To: Zbigniew Baniewski <[EMAIL PROTECTED]>
Cc: alsa-
[EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]
com>
Content-Type: text/plain; charset=us-ascii
Zbigniew Baniewski
wrote:
> 1. Does there exist an easy way to distinguish "output
devices" from
> "capture devices"? There's not always appropriate
remark in the device's
> "name" field.
Only the name determines
whether the control is for playback or capture.
Some controls have an
ambiguous functions, and some drivers give their
controls ambiguous
names.
> 2. Some devices have "access" field like: "rw---R--". What
this big "R" does
> mean?
rwivlRWC
r readable
w
writable
i inactive
v volatile
l locked
R
tlv-readable
W tlv-writable
C tlv-commandable
"TLV" is
additional data about the control, like dB scale information.
HTH
Clemens
------------------------------
Message: 4
Date: Wed, 22 Aug
2007 13:52:32 -0400 (EDT)
From: "Robert P. J. Day" <[EMAIL PROTECTED]
com>
Subject: [Alsa-user] can't get sound on gateway mx8711 laptop
with
intel 82801G
To: ALSA user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
i've been fighting for
the last few hours, and exchanging some
posts on the fedora test
mailing list, trying to get functioning sound
on my gateway laptop.
i'm an alsa newbie, so please take that into
account.
yesterday, i
installed f8-t1 on this gateway mx8711 and, during the
install, the
sound test worked fine. since then, nothing.
running "system-config-
soundcard" displays the following:
Vendor: Intel Corporation
Model: 82801G (ICH7 Family) High Definition Audio Controller
Module:
snd-hda-intel
Device settings
PCM Device STAC92XX Analog
originally, /etc/modprobe.conf contained the line:
options snd-hda-
intel index=0
but based on what i read in the ALSA config file, i
matched the laptop
and model and changed that to read:
options snd-
hda-intel model=m2-2
so far, nothing's worked, so i'm definitely open
to suggestions.
as a start, if one wanted to report a non-working
sound card, what
is the minimal amount of info to supply? what files
should be listed?
what commands run? and so on. thanks.
rday
p.s.
i also suppose a decent tutorial on ALSA architecture wouldn't
hurt.
any pointers?
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel
Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
------------------------------
Message: 5
Date: Wed, 22 Aug 2007 21:
52:03 +0100
From: Loris Caren <[EMAIL PROTECTED]>
Subject: Re:
[Alsa-user] Invalid CTL
To: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain;
charset="iso-8859-1"
On Wednesday 22 August 2007 16:07, you wrote:
>
Loris Caren wrote:
> > When I try 'amixer contents' (with sound modules
loaded) I get
> > error message ALSA lib control.c:909 Invalid CTL
default control
> > default open error
> >
> > Note that I'm running on
a minimal embedded system
>
> Does "aplay -L" output anything?
aplay -L
produces similar 'Invalid CTL' barfs.
> Probably the configuration
files in /usr/share/alsa/ are missing.
That sounds interesting, I
definitely haven't put these on my embedded
system.
On my FC3 dev
machine, theres quite a bit in this directory - can
anybody tell me
how much of it is needed or how I can create it?
------------------------------
Message: 6
Date: Wed, 22 Aug 2007 23:43:
19 +0200
From: Nigel Henry <[EMAIL PROTECTED]>
Subject: [Alsa-
user] Is CX20549 the same as Conexant 5045 for model=
options
To: alsa-
[EMAIL PROTECTED]
Message-ID: <200708222343.19821.cave.
[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Folks on the french debian user list are having problems with hda
intel. I
googled a bit and found a post from Takashi, which suggested
reading the doc
ALSA-configuration.txt, which is in the alsa driver
tarball.
I posted ALSA-configuration.txt to the list, and a couple of
guys appear to
have resolved their hda-intel problems from info in the
doc.
Someone still has a problem with their Toshiba P100, hda-intel,
and the
Conexant CX20549 codec.
A bit more googling this afternoon
turned up this:
commit 82f30040ada635d5d42a244b6eb84607d9881f5a
Author: Tobin Davis <[EMAIL PROTECTED]>
Date: Tue Feb 13 12:45:44
2007 +0100
[ALSA] hda-codec - More fixes for Conexant HD Audio
support
Renamed Conexant 5045 to CX20549 (Venice) per Conexant
Documentation
Renamed Conexant 5047 to CX20551 (Waikiki) per
Conexant Documentation
Fixed automute on HP Laptops with CX20551
codec.
Fixed recording issues on Toshiba Satelite P100/P105 series
laptops
Added HP DV8000, DV2000Z, Fujitsu Si1520 support
More
work to be done on CX20549 based systems, but CX20551 Systems are
much better now.
Signed-off-by: Tobin Davis <[EMAIL PROTECTED]
net>
Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]>
Signed-off-by:
Jaroslav Kysela <[EMAIL PROTECTED]>
Is this saying that the CX20549 is the
same thing as the Conexant 5045, as far
as model= options are
concerned?
There appears to be only one option for the Conexant 5045,
apart from the test
option, and I dont know if he's using the
model=laptop option, but appears to
be having problems with the mike,
headphones, and line in.
He's using a Toshiba P100 on Debian Etch,
with the 2.6.21-rc5 kernel.
Alsamixer is 1.0.14rc2, which shows
CX20549 (Venice)
Any suggestions would be welcome. I can ask him to
post his amixer output if
that will help perhaps.
Nigel.
------------------------------
Message: 7
Date: Wed, 22 Aug 2007 14:44:
21 -0700 (PDT)
From: Joris Huizer <[EMAIL PROTECTED]>
Subject: Re:
[Alsa-user] can't get sound on gateway mx8711 laptop with
intel 82801G
To: ALSA user list <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain;
charset=iso-8859-1
--- "Robert P. J. Day" <[EMAIL PROTECTED]>
wrote:
>
> i've been fighting for the last few hours, and
>
exchanging some
> posts on the fedora test mailing list, trying to get
> functioning sound
> on my gateway laptop. i'm an alsa newbie, so
please
> take that into
> account.
>
> yesterday, i installed f8-t1
on this gateway
> mx8711 and, during the
> install, the sound test
worked fine. since then,
> nothing.
Assuming the problem is "just" no
sound output - you
must unmute the sound card, as the default settings
are to have it completely mute. You can change those
settings by
running 'alsamixer' on the command line
and changing them. Use 'm' to
mute/unmute and
'up'/'down' keys to increase/decrease sound volume.
It's worth checking at least
regards,
Joris
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's
Comedy with an Edge to see
what's on, when.
http://tv.yahoo.com/collections/222
------------------------------
Message: 8
Date: Wed, 22 Aug 2007 17:54:
39 -0400 (EDT)
From: "Robert P. J. Day" <[EMAIL PROTECTED]>
Subject: Re: [Alsa-user] can't get sound on gateway mx8711 laptop with
intel 82801G
To: Joris Huizer <[EMAIL PROTECTED]>
Cc: ALSA user
list <[email protected]>
Message-ID: <Pine.LNX.
[EMAIL PROTECTED]>
Content-Type:
TEXT/PLAIN; charset=US-ASCII
On Wed, 22 Aug 2007, Joris Huizer wrote:
>
> --- "Robert P. J. Day" <[EMAIL PROTECTED]> wrote:
>
> >
> >
i've been fighting for the last few hours, and
> > exchanging some
> >
posts on the fedora test mailing list, trying to get
> > functioning
sound
> > on my gateway laptop. i'm an alsa newbie, so please
> > take
that into
> > account.
> >
> > yesterday, i installed f8-t1 on this
gateway
> > mx8711 and, during the
> > install, the sound test worked
fine. since then,
> > nothing.
>
> Assuming the problem is "just" no
sound output - you must unmute the
> sound card, as the default
settings are to have it completely mute.
> You can change those
settings by running 'alsamixer' on the command
> line and changing
them. Use 'm' to mute/unmute and 'up'/'down' keys
> to
increase/decrease sound volume.
>
> It's worth checking at least
actually, i messed with alsaunmute earlier and finally got sound when
i'm running the cd player, but still nothing when i'm playing embedded
youtube videos. so i'm guessing this is something other than a simple
sound configuration. is there some reason playing cds would work, and
youtube videos wouldn't?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel
Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
------------------------------
Message: 9
Date: Wed, 22 Aug 2007 22:
19:26 -0700 (PDT)
From: Bill Unruh <[EMAIL PROTECTED]>
Subject: Re:
[Alsa-user] Is CX20549 the same as Conexant 5045 for
model= options
To: Nigel Henry <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
sourceforge.net
Message-ID: <[EMAIL PROTECTED]
physics.ubc.ca>
Content-Type: TEXT/PLAIN; charset=US-ASCII;
format=flowed
On Wed, 22 Aug 2007, Nigel Henry wrote:
> Folks on the
french debian user list are having problems with hda intel. I
> googled
a bit and found a post from Takashi, which suggested reading the doc
>
ALSA-configuration.txt, which is in the alsa driver tarball.
>
> I
posted ALSA-configuration.txt to the list, and a couple of guys appear
to
> have resolved their hda-intel problems from info in the doc.
I am
confused by that information. It talks about different codecs. But
none
correspond it seems to for example the Realtek codecs on the Toshiba
U300.
Using alsa 1.0.14 I get with the default two sliders for output,
nothing
for input. And no sound comes out of eitehr speakers or
headphones.
And yes, they are unmuted and the volume sliders are all
the way up.
>
> Someone still has a problem with their Toshiba P100,
hda-intel, and the
> Conexant CX20549 codec.
>
> A bit more googling
this afternoon turned up this:
>
> commit
82f30040ada635d5d42a244b6eb84607d9881f5a
> Author: Tobin Davis
<[EMAIL PROTECTED]>
> Date: Tue Feb 13 12:45:44 2007 +0100
>
>
[ALSA] hda-codec - More fixes for Conexant HD Audio support
>
>
Renamed Conexant 5045 to CX20549 (Venice) per Conexant Documentation
> Renamed Conexant 5047 to CX20551 (Waikiki) per Conexant
Documentation
> Fixed automute on HP Laptops with CX20551 codec.
> Fixed recording issues on Toshiba Satelite P100/P105 series
laptops
> Added HP DV8000, DV2000Z, Fujitsu Si1520 support
> More
work to be done on CX20549 based systems, but CX20551 Systems are
>
much better now.
>
> Signed-off-by: Tobin Davis <[EMAIL PROTECTED]
net>
> Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]>
> Signed-off-
by: Jaroslav Kysela <[EMAIL PROTECTED]>
>
> Is this saying that the CX20549
is the same thing as the Conexant 5045, as far
> as model= options are
concerned?
>
> There appears to be only one option for the Conexant
5045, apart from the test
> option, and I dont know if he's using the
model=laptop option, but appears to
> be having problems with the mike,
headphones, and line in.
>
> He's using a Toshiba P100 on Debian Etch,
with the 2.6.21-rc5 kernel.
> Alsamixer is 1.0.14rc2, which shows
CX20549 (Venice)
>
> Any suggestions would be welcome. I can ask him to
post his amixer output if
> that will help perhaps.
>
------------------------------
Message: 10
Date: Thu, 23 Aug 2007 08:
54:53 +0200
From: Clemens Ladisch <[EMAIL PROTECTED]>
Subject:
Re: [Alsa-user] Invalid CTL
To: Loris Caren <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <46CD2F3D.
[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Loris Caren wrote:
> On Wednesday 22 August 2007 16:07, you wrote:
> >
Probably the configuration files in /usr/share/alsa/ are missing.
>
>
That sounds interesting, I definitely haven't put these on my embedded
> system.
> On my FC3 dev machine, theres quite a bit in this directory
- can
> anybody tell me how much of it is needed or how I can create
it?
Which files are needed depends on the driver.
You can try deleting
any unneeded card-specific files from the cards
subdirectory.
These
files are installed when you run alsa-lib's "make install", or you
can
copy them manually from the alsa-lib/src/conf/ directory (see the
Makefile.am files in these directories).
HTH
Clemens
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through
log files to find problems? Stop.
Now Search log events and
configuration files using AJAX and a browser.
Download your FREE copy
of Splunk now >> http://get.splunk.com/
------------------------------
_______________________________________________
Alsa-user mailing list
[email protected]
https://lists.sourceforge.
net/lists/listinfo/alsa-user
End of Alsa-user Digest, Vol 16, Issue
24
*****************************************
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Alsa-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-user