Volume control disabled?

2021-11-20 Thread Gunnar Gervin
Hi.
Volume is gone in Bullseye version, too.

In Multimedia > Pulse Audio Volume control :
Speaker has red cross on the speaker in System Volume & Firefox Volume
control.
As a recall it has not been the case before.
I ask you please instruct how remove the 2 red crosses. Using Terminal
commands or whatever I need to do.
(If not I must reinstall to Bionicpup Linux, ugly & w/sound, but extremely
slow.
A script slowed down Youtube, and if I turned it off Youtube did not work.
Hacking or malware, maybe? I doubt Youtube would throw out a potential
customer.)
I will try remove and reinstall Pulse Audio Volume control.
Gunnar


Re: Xfce4 - uninstalled pulseaudio - no volume control for alsa for the panel

2018-07-05 Thread Michael Lange
On Thu, 5 Jul 2018 10:08:05 +1000
Zenaan Harkness  wrote:

> > you might want to have a look at pnmixer.
> > It works with both pulseaudio and plain alsa and should work with any
> > DE's system tray.
> 
> Sounds great. By default, it simply starts, in XFCE, in the tray.
> 
> The man page needs a patch as it says "Any other sound driver like
> OSS or FFADO, or sound server like PulseAudio or Jackd, are currently
> not supported (patches welcome)."
> 
> Clicking on "Mixer" button (after right clicking the tray icon)
> brings up a window which appears to endlessly attempt to connect to
> PulseAudio.
> 
> I thought pulse was not installed. Appears it is.

No, this is because pnmixer uses pavucontrol as default mixer
application. If you want to use pnmixer with plain alsa you can click
"Preferences" from the menu, select the "Behavior" Tab and change the
"Volume Control Command" to something like alsamixergui or whichever gui
mixer you prefer.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

If a man had a child who'd gone anti-social, killed perhaps, he'd still
tend to protect that child.
-- McCoy, "The Ultimate Computer", stardate 4731.3



Re: Xfce4 - uninstalled pulseaudio - no volume control for alsa for the panel

2018-07-04 Thread Zenaan Harkness
On Wed, Jul 04, 2018 at 11:27:07PM +0200, Michael Lange wrote:
> Hi,
> 
> On Wed, 4 Jul 2018 19:54:35 +0200
> Aldo Maggi  wrote:
> 
> > As for the Subject, I' ve uninstalled pulseaudio because after an
> > upgrade I couldn't hear anything from the speakers (it happened already
> > in the past more than once).
> > 
> > Now I have audio again but it appears that there is no plugin for alsa
> > to use in the lower panel.
> > 
> > I've installed "volti", it works but I cannot have it in the lower
> > panel.
> > 
> > Aldo :-)
> 
> you might want to have a look at pnmixer.
> It works with both pulseaudio and plain alsa and should work with any
> DE's system tray.

Sounds great. By default, it simply starts, in XFCE, in the tray.

The man page needs a patch as it says "Any other sound driver like
OSS or FFADO, or sound server like PulseAudio or Jackd, are currently
not supported (patches welcome)."

Clicking on "Mixer" button (after right clicking the tray icon)
brings up a window which appears to endlessly attempt to connect to
PulseAudio.

I thought pulse was not installed. Appears it is.

Time to experiment with removing it again, as I only use ALSA
anyway...

Thanks :)



Re: Xfce4 - uninstalled pulseaudio - no volume control for alsa for the panel

2018-07-04 Thread Michael Lange
Hi,

On Wed, 4 Jul 2018 19:54:35 +0200
Aldo Maggi  wrote:

> As for the Subject, I' ve uninstalled pulseaudio because after an
> upgrade I couldn't hear anything from the speakers (it happened already
> in the past more than once).
> 
> Now I have audio again but it appears that there is no plugin for alsa
> to use in the lower panel.
> 
> I've installed "volti", it works but I cannot have it in the lower
> panel.
> 
> Aldo :-)

you might want to have a look at pnmixer.
It works with both pulseaudio and plain alsa and should work with any
DE's system tray.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

A man either lives life as it happens to him, meets it head-on and
licks it, or he turns his back on it and starts to wither away.
-- Dr. Boyce, "The Menagerie" ("The Cage"), stardate
unknown



Xfce4 - uninstalled pulseaudio - no volume control for alsa for the panel

2018-07-04 Thread Aldo Maggi
As for the Subject, I' ve uninstalled pulseaudio because after an
upgrade I couldn't hear anything from the speakers (it happened already
in the past more than once).

Now I have audio again but it appears that there is no plugin for alsa
to use in the lower panel.

I've installed "volti", it works but I cannot have it in the lower
panel.

Aldo :-)



Re: Volume control

2017-11-19 Thread Rainer Dorsch
On Sonntag, 19. November 2017 11:42:37 CET Georgi Naplatanov wrote:
> On my headset it seems that mute button stops microphone's input and
> it's working on my computer. This may be another "default" thing on your
> configuration.

I think this was my fault, I expected it to work for the speaker, but it 
should work for the mic

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/



Re: Volume control

2017-11-19 Thread Georgi Naplatanov
On 11/19/2017 11:20 AM, Rainer Dorsch wrote:
> Hi Georgi,
> 
> thanks for your quick reply.
> 
> On Sonntag, 19. November 2017 01:12:37 CET Georgi Naplatanov wrote:
>> On 11/18/2017 11:17 PM, Rainer Dorsch wrote:
>>> Hi,
>>>
>>>  
>>>
>>> I have a desktop with external speakers and a Logitech USB headset
>>>
>>>  
>>>
>>> Bus 002 Device 005: ID 046d:0a44 Logitech, Inc. Headset H390
>>>
>>> I use pulseaudio to route the audio to the external speakers, the
>>> headset, or both. That works well.
>>>
>>>  
>>>
>>> The headset has volume control buttons, but they always control the
>>> volume of the external speakers and no the headset. Can anybody tell if
>>> there is a way to fix this?
>>
>> Hi,
>>
>> I have Logitech headset but I don't know exact model number. This is the
>>  output of lsusb:
>>
>> Bus 003 Device 002: ID 046d:0a45 Logitech, Inc.
>>
>> When I use volume control on my headset it changes volume but I have no
>> device attached to analog audio output. When I attach my old headset to
>> analog audio output then the old headset becomes the default. Pulseaudio
>> is very clever sometimes so I guess that the solution for your problem
>> is something very simple. Maybe your default device is not your headset
>> (this is just a guess).
> 
> Indeed, changing the default fixed the problem:
> 
> rd@blackbox:~/.pulse$ cp /etc/pulse/default.pa .
> rd@blackbox:~/.pulse$ diff -u /etc/pulse/default.pa default.pa
> --- /etc/pulse/default.pa   2017-01-20 00:49:55.0 +0100
> +++ default.pa  2017-11-19 09:12:02.704724047 +0100
> @@ -136,5 +136,5 @@
>  load-module module-filter-apply
>  
>  ### Make some devices default
> -#set-default-sink output
> +set-default-sink alsa_output.usb-Logitech_Logitech_USB_Headset-00.analog-
> stereo
>  #set-default-source input
> rd@blackbox:~/.pulse$ 
> 
> Do I really need a full copy of /etc/pulse/default.pa in ~/.pulse? 

I don't know. I don't know much about PulseAudio.

I am
> affraid that I miss changes which package maintainers implement I would 
> prefer to just specify the delta configuration.
> 
> My headset has a mute button, that does not have any effect at all, any ideas 
> how I can fix this?

On my headset it seems that mute button stops microphone's input and
it's working on my computer. This may be another "default" thing on your
configuration.

Kind regards
Georgi



Re: Volume control

2017-11-19 Thread Rainer Dorsch
Hi Georgi,

thanks for your quick reply.

On Sonntag, 19. November 2017 01:12:37 CET Georgi Naplatanov wrote:
> On 11/18/2017 11:17 PM, Rainer Dorsch wrote:
> > Hi,
> > 
> >  
> > 
> > I have a desktop with external speakers and a Logitech USB headset
> > 
> >  
> > 
> > Bus 002 Device 005: ID 046d:0a44 Logitech, Inc. Headset H390
> > 
> > I use pulseaudio to route the audio to the external speakers, the
> > headset, or both. That works well.
> > 
> >  
> > 
> > The headset has volume control buttons, but they always control the
> > volume of the external speakers and no the headset. Can anybody tell if
> > there is a way to fix this?
> 
> Hi,
> 
> I have Logitech headset but I don't know exact model number. This is the
>  output of lsusb:
> 
> Bus 003 Device 002: ID 046d:0a45 Logitech, Inc.
> 
> When I use volume control on my headset it changes volume but I have no
> device attached to analog audio output. When I attach my old headset to
> analog audio output then the old headset becomes the default. Pulseaudio
> is very clever sometimes so I guess that the solution for your problem
> is something very simple. Maybe your default device is not your headset
> (this is just a guess).

Indeed, changing the default fixed the problem:

rd@blackbox:~/.pulse$ cp /etc/pulse/default.pa .
rd@blackbox:~/.pulse$ diff -u /etc/pulse/default.pa default.pa
--- /etc/pulse/default.pa   2017-01-20 00:49:55.0 +0100
+++ default.pa  2017-11-19 09:12:02.704724047 +0100
@@ -136,5 +136,5 @@
 load-module module-filter-apply
 
 ### Make some devices default
-#set-default-sink output
+set-default-sink alsa_output.usb-Logitech_Logitech_USB_Headset-00.analog-
stereo
 #set-default-source input
rd@blackbox:~/.pulse$ 

Do I really need a full copy of /etc/pulse/default.pa in ~/.pulse? I am 
affraid that I miss changes which package maintainers implement I would 
prefer to just specify the delta configuration.

My headset has a mute button, that does not have any effect at all, any ideas 
how I can fix this?

Thanks again
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/



Re: Volume control

2017-11-18 Thread Georgi Naplatanov
On 11/18/2017 11:17 PM, Rainer Dorsch wrote:
> Hi,
> 
>  
> 
> I have a desktop with external speakers and a Logitech USB headset
> 
>  
> 
> Bus 002 Device 005: ID 046d:0a44 Logitech, Inc. Headset H390
> 
> I use pulseaudio to route the audio to the external speakers, the
> headset, or both. That works well.
> 
>  
> 
> The headset has volume control buttons, but they always control the
> volume of the external speakers and no the headset. Can anybody tell if
> there is a way to fix this?

Hi,

I have Logitech headset but I don't know exact model number. This is the
 output of lsusb:

Bus 003 Device 002: ID 046d:0a45 Logitech, Inc.

When I use volume control on my headset it changes volume but I have no
device attached to analog audio output. When I attach my old headset to
analog audio output then the old headset becomes the default. Pulseaudio
is very clever sometimes so I guess that the solution for your problem
is something very simple. Maybe your default device is not your headset
(this is just a guess).

Kind regards
Georgi



Volume control

2017-11-18 Thread Rainer Dorsch
Hi,

I have a desktop with external speakers and a Logitech USB headset

Bus 002 Device 005: ID 046d:0a44 Logitech, Inc. Headset H390

I use pulseaudio to route the audio to the external speakers, the headset, or 
both. That 
works well.

The headset has volume control buttons, but they always control the volume of 
the 
external speakers and no the headset. Can anybody tell if there is a way to fix 
this?

Thanks
Rainer
-- 
Rainer Dorsch
http://bokomoko.de/


Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-24 Thread Nicolas George
Le sextidi 6 thermidor, an CCXXV, Erik Christiansen a écrit :
> When two meters back from a big monitor, with wireless keyboard to
> bridge the gap, and eyes which have made 63 trips around the big shiny
> yellow thing, those tiny flyspecks are worth nothing in terms of user
> interface.

I feel your pain. I myself handle my mouse with chopsticks, so GUI
buttons with a size of less than 400 pixels in both directions are worth
nothing as well. Applications defaults must fit everybody's needs,
including mine. It is unacceptable that I have to fiddle a bit with the
configuration to get something usable with chopsticks. The developers
who decided otherwise should be sent to never-ending hell.



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Erik Christiansen
On 23.07.17 22:00, Martin Read wrote:
> There seem to be some other changes to the upstream glade file between
> version 2.0 and version 3.0, which have some indirect effect on the window
> geometry. Both versions have a nominal default width of 500, yet in the
> version in Debian 8 the window would come up wider than that on my system
> (as noted, it would write a window width of 780 into its configuration
> file).
> 
> In Debian 9, it comes up at 500x400 and only three of the tabs are
> immediately visible, but there are small arrows at either end of the tab
> bar, letting you move right and left along it - which is not a particularly
> obvious feature if you're not expecting it.

When two meters back from a big monitor, with wireless keyboard to
bridge the gap, and eyes which have made 63 trips around the big shiny
yellow thing, those tiny flyspecks are worth nothing in terms of user
interface. There should not be hidden secret panels.

It has now been confirmed that older Debian versions provided all 5
tabs, by overriding the 500x400 misconfiguration. Rather than attempt to
replicate the convoluted override meander, it is simpler to just
implement the proposed fix - and then ponder how a more complicated
alternative might be engineered, later.

On 23.07.17 15:30, Curt wrote:
> I took the scientific route and downloaded the deb for Stretch
> (amd64, my particular sauce) and unpacked it (dpkg -x
> pavucontrol_3.0-3.1_amd64.deb _directory_) and indeed the default
> geometry for the window is set in pavucontrol.glade at 500x400
> (width/height) just as Erik claimed.
> 
> Therefore I declare his rant warranted.
> 
> ;-) 
> 
> (If ever rants are really warranted.)

Admittedly dubious, but when at the bottom of a deep dark pit
demonstrably devoid of any visible way out, there comes a time to
rattle the cage. That two twists of a right-hand mantelpiece support
opens an invisible door to the previously denied access, in no way
provides a usable user interface.

> Maybe this constrained default geometry could be considered a bug that
> should be reported to the proper authorities.

As the perfect is the enemy of the good, at least if it leads to
procrastination, my recommendation is to correct the config error as
proposed, and _then_:
> “We’ll sit around talking about the good old days, when we wished that we 
> were dead.”
> --Samuel Beckett, speculating on the nature of the afterlife.

I'm off-line for a week or so, from an hour's time. If no-one's pushed
this one uphill by then, I'll give it a go. It's a lot of pain from one
small oversight.

Erik



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Martin Read

On 23/07/17 16:48, Curt wrote:

Except that the default 500x400 geometry is the same in Jessie and
Wheezy and seems sufficient since nobody appears to be having any
problems seeing all 5 tabs but Erik.


There seem to be some other changes to the upstream glade file between 
version 2.0 and version 3.0, which have some indirect effect on the 
window geometry. Both versions have a nominal default width of 500, yet 
in the version in Debian 8 the window would come up wider than that on 
my system (as noted, it would write a window width of 780 into its 
configuration file).


In Debian 9, it comes up at 500x400 and only three of the tabs are 
immediately visible, but there are small arrows at either end of the tab 
bar, letting you move right and left along it - which is not a 
particularly obvious feature if you're not expecting it.




Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Curt
On 2017-07-23, Curt  wrote:
>
> I took the scientific route and downloaded the deb for Stretch
> (amd64, my particular sauce) and unpacked it (dpkg -x
> pavucontrol_3.0-3.1_amd64.deb _directory_) and indeed the default
> geometry for the window is set in pavucontrol.glade at 500x400
> (width/height) just as Erik claimed.
>

Except that the default 500x400 geometry is the same in Jessie and
Wheezy and seems sufficient since nobody appears to be having any
problems seeing all 5 tabs but Erik.

-- 
“We’ll sit around talking about the good old days, when we wished that we were 
dead.”
--Samuel Beckett, speculating on the nature of the afterlife.



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Curt
On 2017-07-23, Cindy-Sue Causey  wrote:
> On 7/22/17, Curt  wrote:
>> On 2017-07-22, Ric Moore  wrote:
>>> On 07/22/2017 12:51 AM, Erik Christiansen wrote:
>>>
 There is no rational explanation for failing to make all 5 tabs visible.
>>>
>>> No idea what your problem is, I have always been able to see the tabs.
>>> Ric
>>>
>>
>> Me neither. I've got all five. Ordinary display size here.
>>
>> I've read that the HDMI output on the Udoo depends on the S/PDIF control
>> and
>> installing pulseaudio mutes it. Maybe that has something to do with "The
>> Mysterious Case of the Hidden Tabs."
>
>
> I have 2 to 5 depending on the size of the window. Instead of all five
> reflexively changing size relative to the window size, they do what
> the main Xfce4 desktop toolbar does, for example. They become silently
> hidden behind a drop-down arrow. Or in the case of PulseAudio, a
> drop-left AND drop-right arrow. :)
>

I took the scientific route and downloaded the deb for Stretch
(amd64, my particular sauce) and unpacked it (dpkg -x
pavucontrol_3.0-3.1_amd64.deb _directory_) and indeed the default
geometry for the window is set in pavucontrol.glade at 500x400
(width/height) just as Erik claimed.

Therefore I declare his rant warranted.

;-) 

(If ever rants are really warranted.)

Maybe this constrained default geometry could be considered a bug that
should be reported to the proper authorities.

-- 
“We’ll sit around talking about the good old days, when we wished that we were 
dead.”
--Samuel Beckett, speculating on the nature of the afterlife.



Re: Distro redeemable with this fix. [Was: Can "PulseAudio Volume Control" devs be redeemed?]

2017-07-23 Thread Cindy-Sue Causey
On 7/23/17, Erik Christiansen  wrote:
> On 23.07.17 13:33, Martin Read wrote:
>> The shared data file describing the default window structure of
>> pavucontrol
>> is /usr/share/pavucontrol/pavucontrol.glade. The corresponding file in
>> the
>> pavucontrol-2.0 (found in Debian jessie) and pavucontrol-3.0 (found in
>> Debian stretch) source trees as downloadable from packages.debian.org
>> appears to have no obviously window-size-affecting changes between the
>> two
>> versions.
>
> Grateful thanks for taking the trouble to find the culprit file. A quick
> look in /usr/share/pavucontrol/pavucontrol.glade reveals the problem, at
> lines 694 and 695:
>
>500
>400
>
> FIX: Change default_width to (minimally) 700 for all 5 tabs to display.
>  (600 displays but 4, 500 displays only 3, as we well know by now.)
>  N.B. A width of 800 may be needed for Martin's case, though.
>
>> pavucontrol also reads the human-readable configuration file
>> /home/USERNAME/.config/pavucontrol.ini to determine what the preferred
>> window size for user USERNAME is. If this file is not present, it is
>> created
>> afresh and the default startup geometry is written to it. On my Debian
>> jessie system, this geometry is 780x400 (which, in the context of the
>> rest
>> of my system configuration, is adequate to make the existence of all five
>> tabs apparent).
>
> On the new 9.0.0 install, it is also 500x400 in ~/.config/pavucontrol.ini,
> and that presents only 3 tabs, as we have discussed. It confirms that
> the window size is as configured at installation - not influenced by any
> user action.
>
>> I haven't upgraded to stretch, because I haven't yet been in the mood to
>> spend an hour or more with my computer switched on but effectively
>> unusable
>> while I perform the upgrade, so I can't comment on the default geometry
>> presented by pavucontrol in stretch.
>
> Understood - I'll refrain from mentioning how old the Debian version on
> this host is. It's all the futzing to put back the 101 bits and pieces
> which provide the familiar environment that sporadically interrupts the
> next few days.
>
> Thank you for providing the means of diagnosis, and thereby the fix.


I just responded to the other part of this thread. Another "fix" might
be that the tabs are "trained" to shrink down in size reflexively
relative to the software package's window size, be it two feet wide..
or teeny tiny tablet :)

A fix like this would fal under #usability.. #accessibility (ref: cognition).

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Cindy-Sue Causey
On 7/22/17, Curt  wrote:
> On 2017-07-22, Ric Moore  wrote:
>> On 07/22/2017 12:51 AM, Erik Christiansen wrote:
>>
>>> There is no rational explanation for failing to make all 5 tabs visible.
>>
>> No idea what your problem is, I have always been able to see the tabs.
>> Ric
>>
>
> Me neither. I've got all five. Ordinary display size here.
>
> I've read that the HDMI output on the Udoo depends on the S/PDIF control
> and
> installing pulseaudio mutes it. Maybe that has something to do with "The
> Mysterious Case of the Hidden Tabs."


I have 2 to 5 depending on the size of the window. Instead of all five
reflexively changing size relative to the window size, they do what
the main Xfce4 desktop toolbar does, for example. They become silently
hidden behind a drop-down arrow. Or in the case of PulseAudio, a
drop-left AND drop-right arrow. :)

Neither one is 100% *cognitively friendly*, but no, I don't know of an
alternative that would improve the experience.

Well, no, wait Yes, in fact I do know of an alternative. It would
help if the buttons continued to shrink down reflexively so that all
could fit in *visibly* together.

No, not everyone would like that. That part could be addressed by a
wish list item that asks for a  preference menu toggle switch to turn
that type of feature on and off. :)

My own personal experience is just a fact of #Life related to second
by second memory loss issues. To this very day after YEARS of the
same, I'll STILL lose at least a few seconds *EVERY SINGLE DAY*
wondering where any given window's "button" wandered off to on that
top desktop wide toolbar. That "button" will be there, I will just
have forgotten YET AGAIN to see if a "drop-down" button  hasn't very
quietly and *necessarily* appeared to the far right (in my particular
Xfce4 use case).

Just thinking out loud :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *



Distro redeemable with this fix. [Was: Can "PulseAudio Volume Control" devs be redeemed?]

2017-07-23 Thread Erik Christiansen
On 23.07.17 13:33, Martin Read wrote:
> The shared data file describing the default window structure of pavucontrol
> is /usr/share/pavucontrol/pavucontrol.glade. The corresponding file in the
> pavucontrol-2.0 (found in Debian jessie) and pavucontrol-3.0 (found in
> Debian stretch) source trees as downloadable from packages.debian.org
> appears to have no obviously window-size-affecting changes between the two
> versions.

Grateful thanks for taking the trouble to find the culprit file. A quick
look in /usr/share/pavucontrol/pavucontrol.glade reveals the problem, at
lines 694 and 695:

   500
   400

FIX: Change default_width to (minimally) 700 for all 5 tabs to display.
 (600 displays but 4, 500 displays only 3, as we well know by now.)
 N.B. A width of 800 may be needed for Martin's case, though.

> pavucontrol also reads the human-readable configuration file
> /home/USERNAME/.config/pavucontrol.ini to determine what the preferred
> window size for user USERNAME is. If this file is not present, it is created
> afresh and the default startup geometry is written to it. On my Debian
> jessie system, this geometry is 780x400 (which, in the context of the rest
> of my system configuration, is adequate to make the existence of all five
> tabs apparent).

On the new 9.0.0 install, it is also 500x400 in ~/.config/pavucontrol.ini,
and that presents only 3 tabs, as we have discussed. It confirms that
the window size is as configured at installation - not influenced by any
user action.

> I haven't upgraded to stretch, because I haven't yet been in the mood to
> spend an hour or more with my computer switched on but effectively unusable
> while I perform the upgrade, so I can't comment on the default geometry
> presented by pavucontrol in stretch.

Understood - I'll refrain from mentioning how old the Debian version on
this host is. It's all the futzing to put back the 101 bits and pieces
which provide the familiar environment that sporadically interrupts the
next few days. 

Thank you for providing the means of diagnosis, and thereby the fix.

Erik

P.S. How can ~/.config/pavucontrol.ini, be undisturbed, when I had to
enlarge the window to access the config tab, and that overwrites on
closure? A pristine instance lay minimised and forgotten at the bottom
of the screen, and was closed after the one with the increased window
size, thus restoring the distro default. 



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-23 Thread Martin Read

On 22/07/17 13:20, Erik Christiansen wrote:

What we need to do is examine whether the Debian 9.0.0 distro-smith last
had it shrunken, and it is therefore in that condition in the distro.
If we knew what config file contains the menu gumpf, that could perhaps
be revealed, and minimise the need for speculation and supposition.


The shared data file describing the default window structure of 
pavucontrol is /usr/share/pavucontrol/pavucontrol.glade. The 
corresponding file in the pavucontrol-2.0 (found in Debian jessie) and 
pavucontrol-3.0 (found in Debian stretch) source trees as downloadable 
from packages.debian.org appears to have no obviously 
window-size-affecting changes between the two versions.


pavucontrol also reads the human-readable configuration file 
/home/USERNAME/.config/pavucontrol.ini to determine what the preferred 
window size for user USERNAME is. If this file is not present, it is 
created afresh and the default startup geometry is written to it. On my 
Debian jessie system, this geometry is 780x400 (which, in the context of 
the rest of my system configuration, is adequate to make the existence 
of all five tabs apparent).


I haven't upgraded to stretch, because I haven't yet been in the mood to 
spend an hour or more with my computer switched on but effectively 
unusable while I perform the upgrade, so I can't comment on the default 
geometry presented by pavucontrol in stretch.




Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-22 Thread Erik Christiansen
On 22.07.17 13:47, Ansgar Burchardt wrote:
> Erik Christiansen writes:
> > Aha, if the "PulseAudio Volume Control" window is manually widened, the
> > suppressed tabs become visible. Is it then the Debian 9.0.0 distro-smiths
> > who have set too small a window size in their LXDE menu item invocation?
> 
> It seems to remember what size it was last started with. So if a user
> decides to make it small and hide stuff, it will remember the user's
> wishes.
> 
> Now, the problem is that users don't know what they want, act
> irrational, will never remember what they did earlier (how often does
> one hear "I did nothing, but everything broke"?) and blame everything on
> the software developer. Not to forget some even come up with conspiracy
> theories how Microsoft paid people to make the application window
> smaller ;-)

Firstly, if the window had ever been larger, the 5 tabs would have
shown at least once. They did not at any stage. The word "Configure"
would have been a beacon as I struggled to find configure options.

Secondly, this user did not know that a desktop menu item could be
resized. Until the possibility was raised on list, I considered them
inviolate.

Thirdly, I've had Debian 9.0.0 installed for 2 -3 days now, and with a
monitor nearly a yard wide, I have in that time only enlarged a couple
of uxterms, and set "huge" text size, to better enjoy the wireless
keyboard at range. There has not been any cause for contemplating making
any window smaller.

What we need to do is examine whether the Debian 9.0.0 distro-smith last
had it shrunken, and it is therefore in that condition in the distro.
If we knew what config file contains the menu gumpf, that could perhaps
be revealed, and minimise the need for speculation and supposition.

Erik






Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-22 Thread Ansgar Burchardt
Erik Christiansen writes:
> Aha, if the "PulseAudio Volume Control" window is manually widened, the
> suppressed tabs become visible. Is it then the Debian 9.0.0 distro-smiths
> who have set too small a window size in their LXDE menu item invocation?

It seems to remember what size it was last started with. So if a user
decides to make it small and hide stuff, it will remember the user's
wishes.

Now, the problem is that users don't know what they want, act
irrational, will never remember what they did earlier (how often does
one hear "I did nothing, but everything broke"?) and blame everything on
the software developer. Not to forget some even come up with conspiracy
theories how Microsoft paid people to make the application window
smaller ;-)

Ansgar



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-22 Thread Curt
On 2017-07-22, Erik Christiansen <dva...@internode.on.net> wrote:
> On 22.07.17 09:36, Curt wrote:
>> On 2017-07-22, Ric Moore <wayward4...@gmail.com> wrote:
>> > On 07/22/2017 12:51 AM, Erik Christiansen wrote:
>> >
>> >> There is no rational explanation for failing to make all 5 tabs visible.
>> >
>> > No idea what your problem is, I have always been able to see the tabs. Ric
>> >
>> 
>> Me neither. I've got all five. Ordinary display size here. 
>> 
>> I've read that the HDMI output on the Udoo depends on the S/PDIF control and
>> installing pulseaudio mutes it. Maybe that has something to do with "The
>> Mysterious Case of the Hidden Tabs." 
>
> Aha, if the "PulseAudio Volume Control" window is manually widened, the
> suppressed tabs become visible. Is it then the Debian 9.0.0 distro-smiths
> who have set too small a window size in their LXDE menu item invocation?

Calling all LXDE Debian 9.0.0 "PulseAudio Volume Control" users for
theory validation.

Of course, we assume you didn't "manually" fiddle with the geometry of
the window during some previous invocation, which fiddling it
inconveniently remembered to your profound and vocal dismay.

I mean, we're talking pristine window here, geometrically speaking,
right?

> It is cruel that so small an error causes such a reduction in usability.

Butterfly.

> Erik
>
>


-- 
“We’ll sit around talking about the good old days, when we wished that we were 
dead.”
--Samuel Beckett, speculating on the nature of the afterlife.



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-22 Thread Erik Christiansen
On 22.07.17 09:36, Curt wrote:
> On 2017-07-22, Ric Moore <wayward4...@gmail.com> wrote:
> > On 07/22/2017 12:51 AM, Erik Christiansen wrote:
> >
> >> There is no rational explanation for failing to make all 5 tabs visible.
> >
> > No idea what your problem is, I have always been able to see the tabs. Ric
> >
> 
> Me neither. I've got all five. Ordinary display size here. 
> 
> I've read that the HDMI output on the Udoo depends on the S/PDIF control and
> installing pulseaudio mutes it. Maybe that has something to do with "The
> Mysterious Case of the Hidden Tabs." 

Aha, if the "PulseAudio Volume Control" window is manually widened, the
suppressed tabs become visible. Is it then the Debian 9.0.0 distro-smiths
who have set too small a window size in their LXDE menu item invocation?

It is cruel that so small an error causes such a reduction in usability.

Erik



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-22 Thread Curt
On 2017-07-22, Ric Moore  wrote:
> On 07/22/2017 12:51 AM, Erik Christiansen wrote:
>
>> There is no rational explanation for failing to make all 5 tabs visible.
>
> No idea what your problem is, I have always been able to see the tabs. Ric
>

Me neither. I've got all five. Ordinary display size here. 

I've read that the HDMI output on the Udoo depends on the S/PDIF control and
installing pulseaudio mutes it. Maybe that has something to do with "The
Mysterious Case of the Hidden Tabs." 


-- 
“We’ll sit around talking about the good old days, when we wished that we were 
dead.”
--Samuel Beckett, speculating on the nature of the afterlife.



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-21 Thread Erik Christiansen
On 22.07.17 14:23, Joel Rees wrote:
> On Sat, Jul 22, 2017 at 1:51 PM, Erik Christiansen
> >
> > There is no rational explanation for failing to make all 5 tabs visible.
> >
> > Erik
> > (Who in 30 years of s/w development never let a team member produce crap
> > like that.)
> >
> 
> I think there are two things going on here.
> 
> One is that many devs get huge displays to make it easier to code, and
> then forget what the ordinary-sized displays are like. So they get careless
> about the constraints imposed by ordinary-sized screens.

Uhuh, I always tried to give my s/w team members big screens too, but my
screen is also over two feet wide. The "PulseAudio Volume Control" dev's
perversity here is in forcing two vital tabs off the dialogue window for
no valid reason, when there is over another half yard of display width to
spare!

> Another is that many devs are trying to support tablets without
> designing a separate UI for them. So they cram too much in.

That does not wash. The output config could then be included in the
"Output Ports" tab, where it belongs in the first place. Further, the
"PulseAudio Volume Control" is so damn narrow that it could fit twice on
a tablet, _and_ it wastes 25% of the tab width. The two omitted tabs can
be accommodated with ease.

As there is no plausible reason for obfuscating the two tabs, it is only
arrant disregard for the user which leads to the current abomination.

Erik



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-21 Thread Joel Rees
On Sat, Jul 22, 2017 at 1:51 PM, Erik Christiansen
<dva...@internode.on.net> wrote:
> After two days of trying to google ways to get audio on the hdmi output
> on a shiny new Udoo X86 running debian 9.0.0, sheer gritted-teeth
> determination, smacking the walls of the GUI rat's maze lucked onto the
> deeply concealed interface.
>
> On the LXDE desktop, the "Sound & Video" -> "PulseAudio Volume Control"
> menu item has only 3 widely spaced tabs, underutilising the chosen
> window width, and the "Output Ports" tab offered no management or
> configuration possibilities.
>
> But there are two tiny dark triangles in the corners. Clicking on the RH
> one leads to an unnecessarily hidden tab, "Input Devices", and clicking
> again reveals "Configuration". There, in a "Profile" selection box, it
> is possible to select "Digital Stereo (HDMI) Output". Once selected, it
> even seems to be the power-on default. (Much to my surprise, given the
> user-hostile perversity of the devious GUI design, deliberately made
> unnecessarily narrow, so that two vital tabs could be hidden from the
> user, without the most tenuous rational reason for doing so.)
>
> Granted, the purpose of a GUI is to put access to necessary functions
> at the end of deep maze rat runs - but invisible secret tabs with double
> blind access?! I do believe that some of these devs are being paid by
> Microsoft to paralyse linux. (If not, we know that they were born
> arse-backwards, and have never turned around.)
>
> There is no rational explanation for failing to make all 5 tabs visible.
>
> Erik
> (Who in 30 years of s/w development never let a team member produce crap
> like that.)
>

I think there are two things going on here.

One is that many devs get huge displays to make it easier to code, and
then forget what the ordinary-sized displays are like. So they get careless
about the constraints imposed by ordinary-sized screens.

Another is that many devs are trying to support tablets without
designing a separate UI for them. So they cram too much in.

-- 
Joel Rees

One of these days I'll get someone to pay me
to design a language that combines the best of Forth and C.
Then I'll be able to leap wide instruction sets with a single #ifdef,
run faster than a speeding infinite loop with a #define,
and stop all integer size bugs with my bare cast.
http://defining-computers.blogspot.com/2017/06/reinventing-computers.html

More of my delusions:
http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html
http://reiisi.blogspot.jp/p/novels-i-am-writing.html



Re: Can "PulseAudio Volume Control" devs be redeemed?

2017-07-21 Thread Ric Moore

On 07/22/2017 12:51 AM, Erik Christiansen wrote:


There is no rational explanation for failing to make all 5 tabs visible.


No idea what your problem is, I have always been able to see the tabs. Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html



Can "PulseAudio Volume Control" devs be redeemed?

2017-07-21 Thread Erik Christiansen
After two days of trying to google ways to get audio on the hdmi output
on a shiny new Udoo X86 running debian 9.0.0, sheer gritted-teeth
determination, smacking the walls of the GUI rat's maze lucked onto the
deeply concealed interface.

On the LXDE desktop, the "Sound & Video" -> "PulseAudio Volume Control"
menu item has only 3 widely spaced tabs, underutilising the chosen
window width, and the "Output Ports" tab offered no management or
configuration possibilities.

But there are two tiny dark triangles in the corners. Clicking on the RH
one leads to an unnecessarily hidden tab, "Input Devices", and clicking
again reveals "Configuration". There, in a "Profile" selection box, it
is possible to select "Digital Stereo (HDMI) Output". Once selected, it
even seems to be the power-on default. (Much to my surprise, given the
user-hostile perversity of the devious GUI design, deliberately made
unnecessarily narrow, so that two vital tabs could be hidden from the
user, without the most tenuous rational reason for doing so.)

Granted, the purpose of a GUI is to put access to necessary functions
at the end of deep maze rat runs - but invisible secret tabs with double
blind access?! I do believe that some of these devs are being paid by
Microsoft to paralyse linux. (If not, we know that they were born
arse-backwards, and have never turned around.)

There is no rational explanation for failing to make all 5 tabs visible.

Erik
(Who in 30 years of s/w development never let a team member produce crap
like that.)



sound games-Pulse Audio Volume control- Defaults- maybe SOLVED..

2014-02-19 Thread Paul Cartwright
I have been installing some games from the humble bundle. They work for
linux, but no sound. The problem is, with Pulse-audio, for each app or
game that needs sound I normally have to start the Pulse Audio Sound App
and change the default for output to sb1040 from Built-in Audio Analog.
In the games, I can't do that, so I get no sound. Any suggestions??

ah, I think I found the answer..There is a button with a green check
mark for each audio device, and the default was for the built-in audio (
which doesn't output any sound. Once I clicked the  default to the
sb1040 and started a game, I had sound!


-- 
Paul Cartwright
Registered Linux User #367800 and new counter #561587


-- 
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/5304cc37.70...@gmail.com



Re: audacious : mousewheel volume control

2013-02-16 Thread Rob Owens
On Sat, Feb 16, 2013 at 09:44:14AM +0900, orang Aumori Jepun wrote:
 Sorry , Rob, I replied directly to you, so resend to this list.
 
  In ~/.config/audacious/config, there is a parameter called
  mouse_wheel_change.  I expect that is what you're looking for.
  
  By the way, most software on Linux systems keep user settings in hidden
  files in the user's home directory.  Sometimes they're kept in the
  ~/.config directory, but sometimes they're in a ~/.some_program/
  directory, and sometimes the file is saved directly in the home
  directory as ~/.some_program
 
 Than you very much , Rob, but my config file did'nt have the parameter. So I 
 added the parameter mouse_wheel_change=10 at various positions in the config 
 file , but RESULT = NG.
 And more googling , i found the page
 http://linux.softpedia.com/get/Multimedia/Audio/Audacious-11801.shtml
 that says in the Bugfixes section (bottom of the page),
 · Mouse wheel settings where removed (for now) from properties, because they 
 didn't actually do anything.
 The page is on the audacious version 3.0.9, and the version of audacious of 
 debian squeeze is 2.3.  That means , even though I add the parameter  
 anywhere in the config file, it's no use ?
 
 But  , if your mouse wheel setting of audacious does work , pls let me know 
 your contents of the config file and the version of audacious.
 
Looks like you're right.  That parameter doesn't have any effect on my
system (Squeeze).

On my system, the mouse wheels seems to lower the volume by 5, or raise
it by 4.  And that doesn't change even if I modify the
mouse_wheel_change value.

-Rob


-- 
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/20130216154056.ga7...@aurora.owens.net



Re: audacious : mousewheel volume control

2013-02-16 Thread orang Aumori Jepun
 On my system, the mouse wheels seems to lower the volume by 5, or raise
 it by 4.  And that doesn't change even if I modify the
 mouse_wheel_change value.
 
 -Rob

Anyway , thank you very much for your advices.


--
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/529915.20976...@web100808.mail.kks.yahoo.co.jp



audacious : mousewheel volume control

2013-02-15 Thread orang Aumori Jepun
Hi, all.

I'm using Debian Squeeze.
While I'm using audacious music player, I can increase/decrease audio volume by 
5% with mouse wheel.
But , I want change the 5% to 1% or any value I want.
Anyone please tell me how to do .
Ubuntu hardy had a preference menu to change the value , but debian squeeze 
does'nt.

I downloaded the source of audacious-plugins , and I found in PO file , there 
is a description mouse wheel value .., but I could not go further .

TIA.


--
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/280406.68723...@web100809.mail.kks.yahoo.co.jp



Re: audacious : mousewheel volume control

2013-02-15 Thread Rob Owens
On Fri, Feb 15, 2013 at 09:16:42PM +0900, orang Aumori Jepun wrote:
 Hi, all.
 
 I'm using Debian Squeeze.
 While I'm using audacious music player, I can increase/decrease audio volume 
 by 5% with mouse wheel.
 But , I want change the 5% to 1% or any value I want.
 Anyone please tell me how to do .
 Ubuntu hardy had a preference menu to change the value , but debian squeeze 
 does'nt.
 
 I downloaded the source of audacious-plugins , and I found in PO file , there 
 is a description mouse wheel value .., but I could not go further .
 
In ~/.config/audacious/config, there is a parameter called
mouse_wheel_change.  I expect that is what you're looking for.

By the way, most software on Linux systems keep user settings in hidden
files in the user's home directory.  Sometimes they're kept in the
~/.config directory, but sometimes they're in a ~/.some_program/
directory, and sometimes the file is saved directly in the home
directory as ~/.some_program

Even Ubuntu's preference menu for audacious just makes changes to the
config file based on your mouse clicks.

-Rob


-- 
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/20130215132454.ga30...@aurora.owens.net



Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread José Luis Segura Lucas
Hi all!

Recently I installed Debian on a new computer, and I want to avoid using
Pulseaudio (it is problematic for me, and this is a long discussion on
this and another lists about that).

I tried to uninstall it, and certainly, I have no problem: I have sound
but I don't have any volume control on my Gnome. I know that the Gnome
volume control relays on Pulseaudio, but is there any wait to get a
volume control for Alsa on the Gnome panel?

Best regards and thanks in advance



signature.asc
Description: OpenPGP digital signature


Re: Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread Jude DaShiell
Isn't there a set of galsa packages to graphically control alsa?On Wed, 12 
Sep 2012, Jos? Luis Segura Lucas wrote:

 Hi all!
 
 Recently I installed Debian on a new computer, and I want to avoid using
 Pulseaudio (it is problematic for me, and this is a long discussion on
 this and another lists about that).
 
 I tried to uninstall it, and certainly, I have no problem: I have sound
 but I don't have any volume control on my Gnome. I know that the Gnome
 volume control relays on Pulseaudio, but is there any wait to get a
 volume control for Alsa on the Gnome panel?
 
 Best regards and thanks in advance
 
 

---
jude jdash...@shellworld.net
Adobe fiend for failing to Flash



-- 
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/alpine.bsf.2.01.1209120400490.54...@freire1.furyyjbeyq.arg



Re: Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread Andrei POPESCU
On Mi, 12 sep 12, 09:58:16, José Luis Segura Lucas wrote:
 Hi all!
 
 Recently I installed Debian on a new computer, and I want to avoid using
 Pulseaudio (it is problematic for me, and this is a long discussion on
 this and another lists about that).
 
 I tried to uninstall it, and certainly, I have no problem: I have sound
 but I don't have any volume control on my Gnome. I know that the Gnome
 volume control relays on Pulseaudio, but is there any wait to get a
 volume control for Alsa on the Gnome panel?

A quick 'apt-cache search' shows at least two interesting candidates:

gnome-alsamixer - ALSA sound mixer for GNOME
alsamixergui - graphical soundcard mixer for ALSA soundcard driver

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature


Re: Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread Jon Dowland
On Wed, Sep 12, 2012 at 09:58:16AM +0200, José Luis Segura Lucas wrote:
 Hi all!
 
 Recently I installed Debian on a new computer, and I want to avoid using
 Pulseaudio (it is problematic for me, and this is a long discussion on
 this and another lists about that).
 
 I tried to uninstall it, and certainly, I have no problem: I have sound
 but I don't have any volume control on my Gnome. I know that the Gnome
 volume control relays on Pulseaudio, but is there any wait to get a
 volume control for Alsa on the Gnome panel?

http://packages.debian.org/sid/volumeicon-alsa would appear to do the
trick, but it sits in the status area, not your panel. (for GNOME 3
at least).


-- 
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/20120912125641.GD26534@debian



Re: Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread Camaleón
On Wed, 12 Sep 2012 09:58:16 +0200, José Luis Segura Lucas wrote:

 Recently I installed Debian on a new computer, and I want to avoid using
 Pulseaudio (it is problematic for me, and this is a long discussion on
 this and another lists about that).
 
 I tried to uninstall it, and certainly, I have no problem: I have sound
 but I don't have any volume control on my Gnome. I know that the Gnome
 volume control relays on Pulseaudio, but is there any wait to get a
 volume control for Alsa on the Gnome panel?

Mmm... gnome-media package contains the gnome-volume-control 
application, but this is only available for Squeeze. 

Wheezy has gnome-alsamixer.

Greetings,

-- 
Camaleón


-- 
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/k2q63r$3v1$9...@ger.gmane.org



Re: Removing Pulseaudio with Gnome: volume control missing

2012-09-12 Thread Ralf Mardorf
On Wed, 2012-09-12 at 11:14 +0300, Andrei POPESCU wrote:
 On Mi, 12 sep 12, 09:58:16, José Luis Segura Lucas wrote:
  Hi all!
  
  Recently I installed Debian on a new computer, and I want to avoid using
  Pulseaudio (it is problematic for me, and this is a long discussion on
  this and another lists about that).
  
  I tried to uninstall it, and certainly, I have no problem: I have sound
  but I don't have any volume control on my Gnome. I know that the Gnome
  volume control relays on Pulseaudio, but is there any wait to get a
  volume control for Alsa on the Gnome panel?
 
 A quick 'apt-cache search' shows at least two interesting candidates:
 
 gnome-alsamixer - ALSA sound mixer for GNOME
 alsamixergui - graphical soundcard mixer for ALSA soundcard driver

Many people want at least a master volume for the panel. IIRC somebody
found a solution, it's somewhere in the Ubuntu Studio users or dev
archives. My recommendation is to keep a fixed master volume. Sane
volume control is done by the apps and by the external gear, e.g. an
amplifier. I suspect that laptops have knobs to adjust the volume too.
There's a sane operating range for the output level of an audio card.
It's not wise to misuse this level adjustment as volume control.

Regards,
Ralf


-- 
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/1347460756.1250.43.camel@localhost.localdomain



gnome-volume-control-applet fails

2011-03-05 Thread T o n g

Hi, 

Of the two of the boxes that I have, both of them have problems with 
gnome-volume-control-applet. 

The first box, after I login from gdm, I get

 The panel encountered a problem while loading 
OAFIID:GNOME_MixerApplet. 

If I remove all my gnome/gdk2 configure directories/files, the gnome 
starts OK, but the problem comes again on next login. 

The second box, at least I can see an icon button (without any icon buy 
with tooltop) that is gnome-volume-control-applet, the problem is that 
when I click on it, which suppose to launch the applet, but actually only 
toggle the mute and unmute. 

I don't know how to start gnome-volume-control-applet from the command 
line though, so I don't know if I can start it later in the boot, and I 
can't see anything obviously connected in .xsession-errors.

Anybody also experiencing gnome-volume-control-applet in debian squeeze?

Thanks

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
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/ikua9u$3og$1...@dough.gmane.org



Re: A simple GUI volume control tool for fluxbox

2010-10-04 Thread T o n g
On Fri, 01 Oct 2010 21:45:22 +0530, Sridhar M.A. wrote:

 I do almost everything on command line. Maybe the only GUI tool I
 need is the sound volume control tool, but I don't have it any more
 -- I used to use tkmixer. Now that it's obsoleted, I'm yet to find
 a GUI sound mixer plain and simple enough for me.
 
 Take a look at volumeicon here :
 
http://www.softwarebakery.com/maato/volumeicon.html

BINGO!!! 

FYI,

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586522#10

 . . . volumeicon is the only one that suits my OP . . . 

Thanks a lot. 

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
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/i8csdn$33...@dough.gmane.org



Re: A simple GUI volume control tool for fluxbox

2010-10-03 Thread Hugo Vanwoerkom

Rob Owens wrote:

On Sat, Oct 02, 2010 at 10:02:56AM -0500, hugo vanwoerkom wrote:

Liam O'Toole wrote:

On 2010-10-01, T o n g mlist4sunt...@yahoo.com wrote:
I do almost everything on command line. Maybe the only GUI tool I 
need is the sound volume control tool, but I don't have it any more 
-- I used to use tkmixer. Now that it's obsoleted, I'm yet to find a 
GUI sound mixer plain and simple enough for me. 


You don't even need a GUI tool: a console application like alsamixer
(from the alsa-utils package) will do the job.

That's true but what gets me with alsamixer is remembering the keys for  
left and right up and down.

open the diary search for the page with the keys
QWE = up
ZXC = down.
I don't have to remember with a GUI like with gnome. What's their volume  
control?



Gnome's is gnome-volume-control, which is in the gnome-media package.

There's also gnome-alsamixer and alsamixergui to consider.



That's it.
Thanks.

Hugo


--
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/i8a428$55...@dough.gmane.org



Re: A simple GUI volume control tool for fluxbox

2010-10-02 Thread hugo vanwoerkom

Liam O'Toole wrote:

On 2010-10-01, T o n g mlist4sunt...@yahoo.com wrote:
I do almost everything on command line. Maybe the only GUI tool I need is 
the sound volume control tool, but I don't have it any more -- I used to 
use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
plain and simple enough for me. 



You don't even need a GUI tool: a console application like alsamixer
(from the alsa-utils package) will do the job.



That's true but what gets me with alsamixer is remembering the keys for 
left and right up and down.

open the diary search for the page with the keys
QWE = up
ZXC = down.
I don't have to remember with a GUI like with gnome. What's their volume 
control?


Hugo


--
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/i87hkn$lg...@dough.gmane.org



Re: A simple GUI volume control tool for fluxbox

2010-10-02 Thread Nuno Magalhães
Hi,

If you just want volume control, i use gkrellm's volume plugin. Does
come with other core plugins so maybe not what you want. Keybindings
seem interesting.

iH


-- 
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/aanlktik5f+tj6zue5+cv4t1vi5te0jvk3j=tkst4p...@mail.gmail.com



Re: A simple GUI volume control tool for fluxbox

2010-10-02 Thread Rob Owens
On Sat, Oct 02, 2010 at 10:02:56AM -0500, hugo vanwoerkom wrote:
 Liam O'Toole wrote:
 On 2010-10-01, T o n g mlist4sunt...@yahoo.com wrote:
 I do almost everything on command line. Maybe the only GUI tool I 
 need is the sound volume control tool, but I don't have it any more 
 -- I used to use tkmixer. Now that it's obsoleted, I'm yet to find a 
 GUI sound mixer plain and simple enough for me. 


 You don't even need a GUI tool: a console application like alsamixer
 (from the alsa-utils package) will do the job.


 That's true but what gets me with alsamixer is remembering the keys for  
 left and right up and down.
 open the diary search for the page with the keys
 QWE = up
 ZXC = down.
 I don't have to remember with a GUI like with gnome. What's their volume  
 control?

Gnome's is gnome-volume-control, which is in the gnome-media package.

There's also gnome-alsamixer and alsamixergui to consider.

-Rob


-- 
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/20101002185509.ga19...@aurora.owens.net



Re: A simple GUI volume control tool for fluxbox

2010-10-02 Thread s. keeling
Nuno Magalhães nunomagalh...@eu.ipp.pt:
 
  If you just want volume control, i use gkrellm's volume plugin. Does

That's excellent!  Thanks!


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


--
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/i88gl3$84...@speranza.aioe.org



A simple GUI volume control tool for fluxbox

2010-10-01 Thread T o n g
Hi,

I do almost everything on command line. Maybe the only GUI tool I need is 
the sound volume control tool, but I don't have it any more -- I used to 
use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
plain and simple enough for me. 

Just like Gnome/Windows volume control tool -- nothing fancy and eye 
catching, just out of the way most of the time, but when I need it, it's 
a click away and offer nothing complicated than the main (and PCM) volume 
control. tkmixer used to foot the bill. sigh...

Am I really out of luck now? 

Thanks

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
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/i84une$60...@dough.gmane.org



Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Camaleón
On Fri, 01 Oct 2010 15:28:46 +, T o n g wrote:

 I do almost everything on command line. Maybe the only GUI tool I need
 is the sound volume control tool, but I don't have it any more -- I used
 to use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound
 mixer plain and simple enough for me.
 
 Just like Gnome/Windows volume control tool -- nothing fancy and eye
 catching, just out of the way most of the time, but when I need it, it's
 a click away and offer nothing complicated than the main (and PCM)
 volume control. tkmixer used to foot the bill. sigh...
 
 Am I really out of luck now?

How about gamix, aumix-gtk or wmix?

Greetings,

-- 
Camaleón


-- 
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/pan.2010.10.01.16.13...@gmail.com



Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Sridhar M.A.
On Fri, Oct 01, 2010 at 03:28:46PM +, T o n g wrote:

I do almost everything on command line. Maybe the only GUI tool I need is 
the sound volume control tool, but I don't have it any more -- I used to 
use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
plain and simple enough for me. 

Take a look at volumeicon here :

   http://www.softwarebakery.com/maato/volumeicon.html

HTH,   

-- 
Sridhar M.A. GPG KeyID : F6A35935
  Fingerprint: D172 22C4 7CDC D9CD 62B5  55C1 2A69 D5D8 F6A3 5935

If I knew what brand [of whiskey] he drinks, I would send a barrel or
so to my other generals.
-- Abraham Lincoln, on General Grant


signature.asc
Description: Digital signature


Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Rob Owens
On Fri, Oct 01, 2010 at 03:28:46PM +, T o n g wrote:
 Hi,
 
 I do almost everything on command line. Maybe the only GUI tool I need is 
 the sound volume control tool, but I don't have it any more -- I used to 
 use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
 plain and simple enough for me. 
 
Earlier today I finally set up my Fluxbox keys file to handle this.

# volume settings -- up, down, and mute:
Control Mod1 9 :Exec amixer sset Master,0 1+
Control Mod1 8 :Exec amixer sset Master,0 1-
Control Mod1 0 :Exec amixer sset Master,0 toggle

# microphone settings -- up, down, and mute:
Control Mod1 3 :Exec amixer sset Capture,0 1+
Control Mod1 2 :Exec amixer sset Capture,0 1-
Control Mod1 1 :Exec amixer sset Capture,0 toggle

# alsamixer
Control Mod1 6 :Exec uxterm -font a14 -geometry 70x20 -T alsamixer -e 
alsamixer -V all

Not exactly GUI, but it works.  Note that on my system that runs
pulseaudio, I need slightly different settings.  Let me know if you want
to see them.

-Rob


-- 
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/20101001180328.ga11...@aurora.owens.net



Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Sjoerd Hiemstra
On Fri, 1 Oct 2010 15:28 + (UTC) T o n g  wrote:
 I do almost everything on command line. Maybe the only GUI tool I
 need is the sound volume control tool, but I don't have it any more
 -- I used to use tkmixer. Now that it's obsoleted, I'm yet to find a
 GUI sound mixer plain and simple enough for me.

Using xbindkeys, I assigned
/usr/bin/amixer set PCM 5%+   to   Ctrl+Up
/usr/bin/amixer set PCM 5%-   to   Ctrl+Down

An advantage of xbindkeys is that it works in other WMs and DEs as well.
Not exactly GUI, but I find it even easier than that.


-- 
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/20101001230639.ba328476.shiems...@kpnplanet.nl



Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Liam O'Toole
On 2010-10-01, T o n g mlist4sunt...@yahoo.com wrote:
 I do almost everything on command line. Maybe the only GUI tool I need is 
 the sound volume control tool, but I don't have it any more -- I used to 
 use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
 plain and simple enough for me. 


You don't even need a GUI tool: a console application like alsamixer
(from the alsa-utils package) will do the job.

-- 
Liam O'Toole
Cork, Ireland



-- 
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/slrniacsbv.398.liam.p.oto...@dipsy.tubbynet



Re: A simple GUI volume control tool for fluxbox

2010-10-01 Thread Dale
On Fri, 1 Oct 2010 15:28:46 + (UTC)
T o n g mlist4sunt...@yahoo.com wrote:

 Hi,
 
 I do almost everything on command line. Maybe the only GUI tool I need is 
 the sound volume control tool, but I don't have it any more -- I used to 
 use tkmixer. Now that it's obsoleted, I'm yet to find a GUI sound mixer 
 plain and simple enough for me. 
 
 Just like Gnome/Windows volume control tool -- nothing fancy and eye 
 catching, just out of the way most of the time, but when I need it, it's 
 a click away and offer nothing complicated than the main (and PCM) volume 
 control. tkmixer used to foot the bill. sigh...
 
 Am I really out of luck now? 
 
There is a nice little app called 'FB-Mix'[1] a friend of mine wrote for
Fluxbox.

quote
A simple mixer applet for the system tray

FB-Mix is designed to sit in the Fluxbox system tray and popup an
alsamixer window when clicked. No doubt it works with other window
managers too.

As of version 0.2 volume can also be adjusted using the mouse
scrollwheel when hovering over the icon.
/quote

Regards
Dale

[1] http://sandbox.ltmnet.com/fbmix


-- 
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/20101002105959.52d14...@spock.tux.lan



Making use of volume control keys

2010-05-29 Thread Michael Goetze

Hi list,

I've just gotten a new laptop (Dell Latitude E4200), and it has some 
keys for adjusting the volume, which I'd like to configure to work with 
Debian. I'm using the awesome window manager.


They keys already get usefully recognized, as evidenced by the following 
xev output:


KeyPress event, serial 28, synthetic NO, window 0x281,
root 0x109, subw 0x0, time 8996889, (4,158), root:(665,178),
state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), 
same_screen YES,

XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x281,
root 0x109, subw 0x0, time 8996972, (4,158), root:(665,178),
state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), 
same_screen YES,

XLookupString gives 0 bytes:
XFilterEvent returns: False

Now all I need is for them to interface with my sound hardware. :) I 
tried installing pulseaudio and running gnome-volume-control-applet in 
my systray, but it didn't have any effect. (The hotkeys for setting the 
LCD backlight interfaced nicely with the gnome-power-manager applet.)


Please CC me on replies, as I am not subscribed.

Thanks,
Michael


--
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/4c014323.2010...@mgoetze.net



Re: Making use of volume control keys

2010-05-29 Thread Andrei Popescu
On Sat,29.May.10, 18:38:59, Michael Goetze wrote:
 
 Now all I need is for them to interface with my sound hardware. :) I
 tried installing pulseaudio and running gnome-volume-control-applet
 in my systray, but it didn't have any effect. (The hotkeys for
 setting the LCD backlight interfaced nicely with the
 gnome-power-manager applet.)

I'm setting a keybinding in the WM/DE:

XF86AudioLowerVolume:   amixer set Master 10%-

and so on. See 'man amixer'

 Please CC me on replies, as I am not subscribed.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature


No sound, speaker not muted, volume control in alsamixer non-functional

2010-02-02 Thread Patrick Wiseman
Hello:

On my testing system (ThinkPad T61p, amd64) sound is suddenly broken.
In alsamixer, the controls for headphone and speaker both appear, and
neither is muted, but the up arrow does nothing.  In
/var/lib/alsa/asound.state, where the current state of the sound card
is stored, there are no entries for either Speaker Volume or Headphone
Volume, so I can't correct the problem by editing that file.  Pointers
would be welcome.  Sound was working until recently, but apt-listbug
did not warn me of any issues when last I updated.

Patrick


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



electro-mechanical volume control works in gnome, but not KDE

2009-01-22 Thread Kent West
I'm currently using a wireless Dell keyboard that has a rotary
electro-mechanical volume control on the corner. It controls the volume
in Gnome, out of the box, but not in KDE.

Any suggestions for getting it to control KDE's volume?

Thanks!

-- 
Kent West *)))
http://kentwest.blogspot.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: electro-mechanical volume control works in gnome, but not KDE

2009-01-22 Thread Emanoil Kotsev
Kent West wrote:

 I'm currently using a wireless Dell keyboard that has a rotary
 electro-mechanical volume control on the corner. It controls the volume
 in Gnome, out of the box, but not in KDE.
 
 Any suggestions for getting it to control KDE's volume?
 
 Thanks!
 

configure kde 

Control Panel - Localization - Keyboard layout - Keyboard model

apply and it should work

regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: electro-mechanical volume control works in gnome, but not KDE

2009-01-22 Thread Kent West
Emanoil Kotsev wrote:
 Kent West wrote:

   
 I'm currently using a wireless Dell keyboard that has a rotary
 electro-mechanical volume control on the corner. It controls the volume
 in Gnome, out of the box, but not in KDE.

 Any suggestions for getting it to control KDE's volume?

 Thanks!

 

 configure kde 

 Control Panel - Localization - Keyboard layout - Keyboard model

 apply and it should work

 regards


   
Hmm, KDE 3.5.10; I don't find a Localization, but I do find a
Regional and Accessibility which gets me there.

Unfortunately, I have already given up on the keyboard (I hated the
placement of some of the keys), and moved it a Mac in another room where
it makes more sense anyway.

Maybe in a day or two I'll bring it back to my Debian box, just to see
if I can get it to work now that you've given me a clue toward solving
the problem.

Thanks very much! I appreciate your response!


-- 
Kent West *)))
http://kentwest.blogspot.com



Midi player volume control

2008-11-15 Thread pch

Hi,
I check a few midi player available in debian repository and only one 
work - xmms-midi (xmms plugin). But it play one midi file and can't work 
correctly. What can I do to play midi music?


How can I change volume master  PCM from console?

Thank,
Pawe?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Midi player volume control

2008-11-15 Thread Dean Sutherland
On Sat, 15 Nov 2008 11:49:19 +0100, pch wrote:

 Hi,
 I check a few midi player available in debian repository and only one 
 work - xmms-midi (xmms plugin). But it play one midi file and can't
 work correctly. What can I do to play midi music?
 
 How can I change volume master  PCM from console?
 
 Thank,
 Pawe?
 
 

When I did a little experimenting with playing midi files I used
timidity, but I can't recall what I used for the sound files.

To change the sound volume levels you can use alsamixer or amixer, the
former uses an ncurses interface.

Dean


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Volume control in Pulseaudio?

2008-09-16 Thread Dr. Jennifer Nussbaum
Hi!

I recently installed Pulseaudio because a lot of people said it was the best 
thing, and i'd been having some problems with my audio beforehand. After
following some detailed instructions online i managed to get it running 
smoothly with all my apps.

My one problem is the volume control. The panel volume control app doesnt allow 
you to control Pulseaudio, it only does HDA Intel (Alsa mixer) or Analog 
Devices...(OSS mixer). If i use the Pulseaudio systems, i either have to go to 
Applications - Sound  Video - PulseAudio Volume Control, and then flip 
through a screen or two, or i go t othe panel Pulseaudio Device Chooser item, 
pick Volume Control here, and same thing.

Is there any way to tie a panel object _directly_ into something that will 
control the Pulseaudio volume, so that i can adjust the volume without 
having to click a bunch of times?

Thanks,

Jen


  


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: kde volume control question

2008-07-14 Thread Kamaraju S Kusumanchi
[EMAIL PROTECTED] wrote:

 Quicktip: mouse wheel on kmix icon also commands the single slider that
 ypu selected as master. No clicks needed ;)

Wow! I have been using KDE for years and never even knew about this awesome
tip! Thanks for sharing it!

raju
-- 
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: kde volume control question

2008-07-04 Thread Mumia W..

On 07/03/2008 05:02 PM, Kent West wrote:

[...]
How do I get the volume control in the systray to control the PCM 
control instead of whatever other control it is presumably controlling?


Thanks!



The tiny volume control affects the master volume control; however, 
the master volume is bounded by the PCM volume (for PCM data--whatever 
that is), so if you turn the master volume up to 100%, but PCM is at 
50%, you get 50% volume.


The solution would be to set the PCM volume to an acceptably high level, 
and save the volume state using alsactl store; I think that KDE might 
have a separate way to manage mixer state persistence, so you may have 
to investigate that too.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: kde volume control question

2008-07-04 Thread hbayindir
 I have a couple of different machines doing this.

 Audio works fine, volume control works fine from the mixer, depending on
 which control I move. However, the systray volume control related to
 kmix doesn't control the device in kmix which controls the volume.

 For example, on this machine in front of me, I can be playing some
 audio, but the little blue KDE volume control down by the clock doesn't
 affect the volume, but if I click on the word Mixer when that control
 is open, that will open the mixer window, and I can control the volume
 by moving the PCM control in the Output tab.

 If it's easy enough to explain, I'd like to know how a mixer works (what
 is PCM; what do the green and red lights mean; etc), but that's probably
 more complicated (and may vary depending on hardware) than is suitable
 here, so my real question ...

 How do I get the volume control in the systray to control the PCM
 control instead of whatever other control it is presumably controlling?

 Thanks!

 --
 Kent West
 http://kentwest.blogspot.com




 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]


Hi,

Understanding mixer is not hard. PCM means Pulse Code Mudulation and you
can obtain more information about it from
http://en.wikipedia.org/wiki/PCM. Basically PCM is the digital coded form
of the sound that you here so computer can play with it. Generally PCM is
the where all sound signal is combined so it acts like master. The green
lights mean active. So if a green light is turned off for a channel, that
channel is muted. Similarly red lights in input tab means Recording this
channel.

You can say kmix to play with which slider in single slider mode (i.e.
single click, tray mode or the mode problematic for you). You need the
select the PCM since it's the master. Just right-click to the mixer icon
and select select master channel and select PCM from the appeared window
and select OK. Now your misbehaving slider will control your master out.

Quicktip: mouse wheel on kmix icon also commands the single slider that
ypu selected as master. No clicks needed ;)

Cheers and Regards,

Hakan.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: kde volume control question

2008-07-04 Thread al davis
On Thursday 03 July 2008, Kent West wrote:
 How do I get the volume control in the systray to control the
 PCM control instead of whatever other control it is
 presumably controlling?

Right click on the speaker .. see the menu ...  Select Master 
Channel . and pick one.The little slider is one of the 
sliders in the mixer, and you get to pick which one.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: kde volume control question

2008-07-04 Thread Kent West

[EMAIL PROTECTED] wrote:
You need the select the PCM since it's the master. Just right-click to 
the mixer icon and select select master channel and select PCM from 
the appeared window and select OK. Now your misbehaving slider will 
control your master out.

Quicktip: mouse wheel on kmix icon also commands the single slider that
ypu selected as master. No clicks needed ;)

  

Well that was easy. Wonder why I've never noticed that. Thanks!

And the extra tip is nice also. Thanks again!



--
Kent West
Westing Peacefully - http://kentwest.blogspot.com



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: kde volume control question

2008-07-04 Thread Brad Rogers
On Fri, 04 Jul 2008 08:10:06 -0500
Kent West [EMAIL PROTECTED] wrote:

Hello Kent,

 Well that was easy. Wonder why I've never noticed that. Thanks!

Because..(see sig)

:-)

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent

He looked the wrong way at a policeman
I Predict A Riot - Kaiser Chiefs


signature.asc
Description: PGP signature


kde volume control question

2008-07-03 Thread Kent West

I have a couple of different machines doing this.

Audio works fine, volume control works fine from the mixer, depending on 
which control I move. However, the systray volume control related to 
kmix doesn't control the device in kmix which controls the volume.


For example, on this machine in front of me, I can be playing some 
audio, but the little blue KDE volume control down by the clock doesn't 
affect the volume, but if I click on the word Mixer when that control 
is open, that will open the mixer window, and I can control the volume 
by moving the PCM control in the Output tab.


If it's easy enough to explain, I'd like to know how a mixer works (what 
is PCM; what do the green and red lights mean; etc), but that's probably 
more complicated (and may vary depending on hardware) than is suitable 
here, so my real question ...


How do I get the volume control in the systray to control the PCM 
control instead of whatever other control it is presumably controlling?


Thanks!

--
Kent West
http://kentwest.blogspot.com




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




No volume control GStreamer plugins

2006-12-26 Thread Fritz Wettstein
The volume control panel is marked with a red X and when it is clicked an 
alert No volume control GStreamer plugins and/or devices found pops up.

Debian etch i386 is installed on an Intel-iMac.
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: No volume control GStreamer plugins

2006-12-26 Thread Sven Arvidsson
On Tue, 2006-12-26 at 15:41 +0100, Fritz Wettstein wrote:
 The volume control panel is marked with a red X and when it is clicked an 
 alert No volume control GStreamer plugins and/or devices found pops up.
 
 Debian etch i386 is installed on an Intel-iMac.

Do you have sound working otherwise? Can you run alsamixer from a
terminal and change the mixer settings?

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part


Re: No volume control GStreamer plugins

2006-12-26 Thread Fritz Wettstein

 
 Do you have sound working otherwise? Can you run alsamixer from a terminal 
 and change the mixer settings?
 

I can sudo alsamixer, it starts a ncurses application with some vertical bars, 
but don't know what to do with it.
The lsmod shows nothing what looks sound-related.
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: No volume control GStreamer plugins

2006-12-26 Thread Alan Ianson
On Tue December 26 2006 08:45, Fritz Wettstein wrote:
  Do you have sound working otherwise? Can you run alsamixer from a
  terminal and change the mixer settings?

 I can sudo alsamixer, it starts a ncurses application with some vertical
 bars, but don't know what to do with it. 

Activate each bar with m that you want to work and adjust the volume levels. 
Master and PCM are important. PCM shouldn't be set more than about 74%.

 The lsmod shows nothing what looks 
 sound-related.

That's not good, maybe alsaconfig will get you going.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: No volume control GStreamer plugins

2006-12-26 Thread Sven Arvidsson
On Tue, 2006-12-26 at 17:45 +0100, Fritz Wettstein wrote:
 I can sudo alsamixer, it starts a ncurses application with some vertical 
 bars, but don't know what to do with it.
 The lsmod shows nothing what looks sound-related.

alsamixer should be usable without running it as root, your normal user
should be in group audio.

If you aren't sure that audio is working, that should be your first
priority before worrying about mixers. Find out what kind of sound card
you have (lspci could be a start), if it's supported, install and
configure alsa, etc.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part


Re: No volume control GStreamer plugins

2006-12-26 Thread Fritz Wettstein

Sven Arvidsson wrote:

On Tue, 2006-12-26 at 17:45 +0100, Fritz Wettstein wrote:
  

I can sudo alsamixer, it starts a ncurses application with some vertical bars, 
but don't know what to do with it.
The lsmod shows nothing what looks sound-related.



alsamixer should be usable without running it as root, your normal user
should be in group audio.

If you aren't sure that audio is working, that should be your first
priority before worrying about mixers. Find out what kind of sound card
you have (lspci could be a start), if it's supported, install and
configure alsa, etc.

  
I've added my user to the group audio, then alsaconf. lsmod now shows 
some snd* modules.

I'm now able to adjust the volume the red X has disappeared.
Now I'll go on to learn how to use sound on debian/linux.

Alan and Sven, thanks a lot for the help.

Fritz


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Audigy LS / ALSA Volume control

2006-05-31 Thread Pirkka Jokela

Well, I agree, but I currently have the alsaplayer / alsamixer volume
at 1% that is the lowest possible value and I also have the stereo
amplifier volume at about 1/10. This is not normal. And what if I want
to use headphones attached straight to the computer?

This isn't critical in the sense that I can live totally without the
sound card, but I am really looking forward to having it work
properly.


From some of the alsa material I thought that it would be possible to

chain the ALSA controls so that I could have a pre amplifier that
would reduce the volume before the main alsaplayer / alsamixer volume
control. I haven't figured out any way to actually to this, however.

If I use a sound server like ESD or aRTs or JACK can I use them to
reduce volume before the sound goes to ALSA? If so, which one should I
use?

Thanks again,

  Pirkka


On 5/30/06, Donald Teed [EMAIL PROTECTED] wrote:

It's normal to not turn up the speakers to maximum to avoid
distortion.  Why not control the volume with the speakers
volume control?

On 5/30/06, Pirkka Jokela [EMAIL PROTECTED] wrote:
 Hi,

 I recently bought a new computer and installed Debian unstable for amd64 on
 it. I'm having trouble with my Creative Soundblaster Audigy LS card.

 I am trying to use ALSA with my card and the ca0106 module. I get sound from
 the card, but the sound is really loud and I have to have my volume setting
 at the lowest possible value in alsamixer (or Gnome ALSA mixer) and the
 sound still almost breaks.

 I have tried all the plugs in the sound card and I have the right one as it
 is the only one that works and it is color coded green. I'm using the analog
 out and the card doesn't even have SPDIF, even  though ALSA offers SPDIF
 controls in the mixer.

 I'm able to adjust the volume with a hardware stereo system, but it would
 really help if I could get the volume that comes out of the computer down to
 normal line out levels.



--
Pirkka Jokela


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Audigy LS / ALSA Volume control

2006-05-30 Thread Pirkka Jokela
Hi,I recently bought a new computer and installed Debian unstable for amd64 on it. I'm having trouble with my Creative Soundblaster Audigy LS card.I am trying to use ALSA with my card and the ca0106 module. I get sound from the card, but the sound is really loud and I have to have my volume setting at the lowest possible value in alsamixer (or Gnome ALSA mixer) and the sound still almost breaks.
I have tried all the plugs in the sound card and I have the right one as it is the only one that works and it is color coded green. I'm using the analog out and the card doesn't even have SPDIF, even though ALSA offers SPDIF controls in the mixer.
I'm able to adjust the volume with a hardware stereo system, but it would really help if I could get the volume that comes out of the computer down to normal line out levels.Here is the ALSA configuration file from my system:
--/var/lib/alsa$ cat asound.statestate.CA0106 { control.1 { comment.access 'read write' comment.type INTEGER comment.count 2
 comment.range '0 - 255' iface MIXER name 'Analog Front Playback Volume' value.0 5 value.1 5 } control.2 {
 comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' iface MIXER name 'Analog Rear Playback Volume'
 value.0 0 value.1 0 } control.3 { comment.access 'read write' comment.type INTEGER comment.count 2 
comment.range '0 - 255' iface MIXER name 'Analog Center/LFE Playback Volume' value.0 0 value.1 0 } control.4 { 
comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' iface MIXER name 'Analog Side Playback Volume'
 value.0 0 value.1 0 } control.5 { comment.access 'read write' comment.type INTEGER comment.count 2 
comment.range '0 - 255' iface MIXER name 'SPDIF Front Playback Volume' value.0 0 value.1 0 } control.6 { 
comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' iface MIXER name 'SPDIF Rear Playback Volume'
 value.0 0 value.1 0 } control.7 { comment.access 'read write' comment.type INTEGER comment.count 2 
comment.range '0 - 255' iface MIXER name 'SPDIF Center/LFE Playback Volume' value.0 0 value.1 0 } control.8 { 
comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' iface MIXER name 'SPDIF Unknown Playback Volume'
 value.0 0 value.1 0 } control.9 { comment.access 'read write' comment.type INTEGER comment.count 2 
comment.range '0 - 255' iface MIXER name 'CAPTURE feedback Playback Volume' value.0 0 value.1 0 } control.10 { 
comment.access read comment.type IEC958 comment.count 1 iface PCM name 'IEC958 Playback Mask' value 
 } control.11 { comment.access read comment.type IEC958 comment.count 1 iface PCM name 'IEC958 Playback Mask'
 index 1 value 
 } control.12 { comment.access read comment.type IEC958 comment.count 1 iface PCM name 'IEC958 Playback Mask'
 index 2 value 
 } control.13 { comment.access read comment.type IEC958 comment.count 1 iface PCM name 'IEC958 Playback Mask'
 index 3 value 
 } control.14 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'SPDIF Out'
 value false } control.15 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0
 'SPDIF out' comment.item.1 'i2s mixer out' comment.item.2 'SPDIF in' comment.item.3 'i2s in' comment.item.4 'AC97 in' comment.item.5
 'SRC out' iface MIXER name 'Capture Source' value 'i2s mixer out' } control.16 { comment.access 'read write' 
comment.type IEC958 comment.count 1 iface PCM name 'IEC958 Playback Default' value 

Problem mit gnome-volume-control (snd-ice1724 / ALSA)

2006-05-16 Thread Martin Roll
Hallo!

Ich habe mir vor kurzem eine Terratec Aureon 7.1 Universe in meinen
Rechner eingebaut.

Nach einem Neukompilieren meines Kernels (ich habe ice1724 fest
einkompiliert) schien erstmal alles zu funktionieren bis ich versuchen
wollte, die Lautstärke per gnome-volume-control einzustellen.

Da ich in meinem Rechner noch nen AC97 onboard Chip habe müssten 2
Soundkarten im Mixer auftauchen. Das tun sie auch.

Ich habe dort folgende zwei Einträge:
0: NVidia CK804 (Alsa Mixer)
1:  (Alsa Mixer)

Irgendwie scheint der Mixer die Soundkarte nicht richtig zu erkennen.
Wenn ich dann versuche, auf die Soundkarte 1 zu wechseln, um dort
Lautstärkeeinstellungen vorzunehmen, sehe ich weiterhin die
Einstellungen meines onboard Chips. Versuche ich es weiter, dann stürzt
gnome-volume-control sogar ab.

Über alsamixer lässt sich alles einstellen, allerdings fehlt auch hier
der Name der Soundkarte.


Habe ich irgendetwas vergessen zu konfigurieren oder liegt hier ein Bug vor?


Danke im Voraus.


Gruß,
Martin Roll


P.S.: Auch beim Booten des Rechners erscheint der Name der Karte nicht,
wenn Alsa gestartet wird.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Problem mit gnome-volume-control (snd-ice1724 / ALSA)

2006-05-16 Thread Matthias Jahn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hallo Martin,
probiere mal als root alsaconf auszuführen und dann, wenn möglich, deine
Soundkarte auszuwählen. Das hat bei mir geholfen. Um die Konfiguration
nach dem nächsten Start noch zu haben, musst 'alsactl store' oder so
ähnlich eingeben, aber so genau weiss ich das nicht mehr.

MfG Matthias Jahn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEaace3LUCfBzqoncRAkrTAKCDWyPYiK+XSVboaAMMvGPCO9iSIwCgpPZt
cV4bnd+lZ2J+4xSVQ0Exl7k=
=HlMQ
-END PGP SIGNATURE-


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Problem mit gnome-volume-control (snd-ice1724 / ALSA)

2006-05-16 Thread Martin Roll
Hab ich grad mal probiert. Hat aber leider nichts geholfen. :-(

So weit ich weiß, funktioniert doch das mit alsaconf nur, wenn man den
Soundtreiber als Modul kompiliert (oder?). Ich habs fest einkompiliert
in den Kernel.



Matthias Jahn schrieb:

 Hallo Martin,
 probiere mal als root alsaconf auszuführen und dann, wenn möglich, deine
 Soundkarte auszuwählen. Das hat bei mir geholfen. Um die Konfiguration
 nach dem nächsten Start noch zu haben, musst 'alsactl store' oder so
 ähnlich eingeben, aber so genau weiss ich das nicht mehr.

 MfG Matthias Jahn



-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: No volume control elements and/or devices found after upgrade to etch

2006-02-12 Thread Ismael Valladolid Torres
Luc Saffre escribe:
 I am running Debian on a Dell Latitude 110L notebook. Recently I
 upgraded from sarge to etch. Now my sound system is dead. On each start
 of either KDE or Gnome I get a message box No volume control elements
 and/or devices found.

Maybe you should start from the beginning and check if modules for
your sound card are loaded.

$ lsmod | grep snd
$ cat /proc/asound/cards

If they aren't, maybe installing alsa-utils and running alsaconf as
root could help.

Cordially, Ismael
-- 
Dropping science like when Galileo dropped his orange

 http://lamediahostia.blogspot.com/
 http://www.flickr.com/photos/ivalladt/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



No volume control elements and/or devices found after upgrade to etch

2006-02-11 Thread Luc Saffre
Hello,

I am running Debian on a Dell Latitude 110L notebook. Recently I
upgraded from sarge to etch. Now my sound system is dead. On each start
of either KDE or Gnome I get a message box No volume control elements
and/or devices found.
The same box comes also when I invoke the menu command Applications /
Sound  Video / Volume Control.

I found the following thread :
http://groups.google.com/group/linux.debian.user/browse_frm/thread/fff05336bb96e850/7ea739ca71c5b55e?lnk=stq=etch+%22no+volume+control+elements%22rnum=1#7ea739ca71c5b55e

Like Chinook I also have a kernel 2.6.12-1-386.
Unlike Chinook my message does not specify to run gst-register.
I had gst-register already installed.
I tried gst-register-0.8 as root. Lots of messages about Adding
plugin, ending with:

  Rebuilding user_registry (/root/.gstreamer-0.8/registry.xml) ...
  Loaded 135 plugins with 276 features.

Oops, that wasn't probably necessary to be run as root. I run it again
as luc.
Similar output.

Reboot the notebook. But the problem persits.

Please help me! What can I do next?

Luc


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: /dev/dsp missing gnome applet volume control complaining

2005-12-10 Thread Henry Hollenberg

Colin wrote:

Henry Hollenberg wrote:


When I checked for devices I see no /dev/dsp but there is a /dev/snd and
/dev/sndstat.



Load the snd_pcm_oss kernel module



Anybody else seen gnome Volume Control broken as such?



Use the alsamixergui to change volume with ALSA




That did it.  Thanks Colin. I poked around in 
/usr/src/kernel/Documentation/sound
and found some references as well.  Takes awhile to become a guru

hgh.



--
Henry Hollenberg
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




/dev/dsp missing gnome applet volume control complaining

2005-12-07 Thread Henry Hollenberg

Hey gang,

I'm running sarge on an ibm laptop T40 from emperorlinux.

I just upgraded the empkernel to 2.6.12 which got lots of things
working which I had broken trying to fiddle with sound on my own.

Later, when I tried to get the cdrom player working under gnome:
/usr/bin/gnome-cd but had weak or no sound.

SO, I went to the gnome Volume Control Applet (2.8.2) but it complains
about: Sorry, no mixer elements and/or devices found in an Error dialog.

When I checked for devices I see no /dev/dsp but there is a /dev/snd and
/dev/sndstat.

Anybody else seen gnome Volume Control broken as such?

Is this a side effect of moving from oss to alsa?


I was able to turn the sound up by: apt-get install kde kdm
and using the kde volume control gismo.

lsmod | grep snd:
snd_intel8x0   29504  1
snd_ac97_codec 80120  1 snd_intel8x0
snd_pcm84616  3 snd_intel8x0,snd_ac97_codec
snd_timer  21892  1 snd_pcm
snd47844  5 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore   7904  2 audio,snd
snd_page_alloc  7812  2 snd_intel8x0,snd_pcm


Thanks, hgh.

--
Henry Hollenberg
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: /dev/dsp missing gnome applet volume control complaining

2005-12-07 Thread Leonid Grinberg
This problem has been happening a lot lately. In any case, it has
happened on most computers that I have installed Debian on recently.

I remember being told that the reason is that Alsa is not stable
enough so that it does not get installed by default (or something to
that effect).

Not much help, I know. Sorry.

Leonid Grinberg
[EMAIL PROTECTED]
http://www.lgrinberg.org



Re: /dev/dsp missing gnome applet volume control complaining

2005-12-07 Thread Colin
Henry Hollenberg wrote:
 When I checked for devices I see no /dev/dsp but there is a /dev/snd and
 /dev/sndstat.

Load the snd_pcm_oss kernel module

 Anybody else seen gnome Volume Control broken as such?

Use the alsamixergui to change volume with ALSA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Volume Control problem

2005-01-09 Thread Lucas Lang
alsa hatte ich nicht laufen. m.e. brauche ich das
auch nicht, weil ich auf einem anderen rechner
eine quasi identische debian konfiguration
installiert habe (ohne alsa) und dort das volume
control perfekt funktioniert.

habe trotzdem mal alsa installiert mit

apt-get install alsa-base alsa-utils

installation war erfolgreich, problem hat sich
aber verschlimmert, weil alsaconf sich nicht
starten laesst. ursache ist leider, dass m.e. die
soundkarte nicht mehr erkannt wird (kann auch
keine cd's mehr hoeren, was vorher noch ging):

Starting ALSA.../etc/rc2.d/S20alsa: Error: alsactl
restore failed with message '/etc/rc2.d/S20alsa:
alsa 1: alsactl: command not found'.

und auch mein setmixer geht nicht mehr ;-(

Setting mixer volumes with setmixer... Error
opening /dev/mixer.failed.

was tun? 

ach ja ... hardware ist m.e. ok (andere soundkarte
gleiches modell eingebaut, anderen pci steckplatz
benutzt, error message bleibt)

lucas





 frage: was muss ich machen, damit mein volume
 control funktioniert?

Hast du alsa am laufen? Wenn nicht, installiers
mal und probiers nochmal.
-- 
   bis denne,
 Chrissie


This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Andreas Pakulat
On 09.Jan 2005 - 13:17:55, Lucas Lang wrote:
 habe trotzdem mal alsa installiert mit
 
 apt-get install alsa-base alsa-utils

Da fehlt für dein setmixer noch alsa-oss oder die
OSS-Compatibilitätsmodule.

 installation war erfolgreich, problem hat sich
 aber verschlimmert, weil alsaconf sich nicht
 starten laesst. ursache ist leider, dass m.e. die
 soundkarte nicht mehr erkannt wird (kann auch
 keine cd's mehr hoeren, was vorher noch ging):

?? alsaconf versucht ja gerade die Soundkarte zu finden... Welche
Fehlermeldungen gibt es? Hast du die OSS-Module vorher entladen?

 Starting ALSA.../etc/rc2.d/S20alsa: Error: alsactl
 restore failed with message '/etc/rc2.d/S20alsa:
 alsa 1: alsactl: command not found'.

alsactl gehört zum Paket alsa-utils  , bist du sicher das das korrekt 
installiert
wurde? Was sagt ein which alsactl als root?

 und auch mein setmixer geht nicht mehr ;-(
 
 Setting mixer volumes with setmixer... Error
 opening /dev/mixer.failed.

setmixer versucht per OSS auf den Sound zuzugreifen, wenn aber die
Module entladen wurden kann er das nicht mehr tun.

Es gibt ausreichend gute HowTo's für die Installation von Alsa im
Internet, ausserdem haben die Pakete alsa-base und alsa-utils
Dokumentation in /usr/share/doc/alsa-base bzw alsa-utils abegelegt.

Andreas

-- 
You may be gone tomorrow, but that doesn't mean that you weren't here today.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Lucas Lang
apt-get install alsa-oss  habe ich gemacht

which alsactl  /usr/sbin/alsactl

alsaconf  error message ist
modinfo: snd: no modules found with this name
im weiteren dann
No supported PnP or PCI card found
dito in /var/log/messages
isapnp: Scanning for PnP cards ... No Plug  Play
device found

hast du die oss module entladen was genau meinst
du damit? ich haette das tun sollen? oder wolltest
du dich nur vergewissern, dass ich das nicht
gemacht habe? habe ich naemlich m.e. nicht gemacht.

howtos: klar weiss ich, dass es die gibt. nur ...
eigentlich moechte ich alsa nicht wirklich
installieren, denn ich sehe ja (wegen zweitem
quasi identischen rechner), dass es auch ohne alsa
funktioniert.

gruss
lucas

ps. habe eine kernel version 2.4.27-1-686





 habe trotzdem mal alsa installiert mit

 apt-get install alsa-base alsa-utils

Da fehlt für dein setmixer noch alsa-oss oder die
OSS-Compatibilitätsmodule.

 installation war erfolgreich, problem hat sich
 aber verschlimmert, weil alsaconf sich nicht
 starten laesst. ursache ist leider, dass m.e. die
 soundkarte nicht mehr erkannt wird (kann auch
 keine cd's mehr hoeren, was vorher noch ging):

?? alsaconf versucht ja gerade die Soundkarte zu
finden... Welche
Fehlermeldungen gibt es? Hast du die OSS-Module
vorher entladen?

 Starting ALSA.../etc/rc2.d/S20alsa: Error: alsactl
 restore failed with message '/etc/rc2.d/S20alsa:
 alsa 1: alsactl: command not found'.

alsactl gehört zum Paket alsa-utils  , bist du
sicher das das korrekt installiert
wurde? Was sagt ein which alsactl als root?

 und auch mein setmixer geht nicht mehr ;-(

 Setting mixer volumes with setmixer... Error
 opening /dev/mixer.failed.

setmixer versucht per OSS auf den Sound
zuzugreifen, wenn aber die
Module entladen wurden kann er das nicht mehr tun.

Es gibt ausreichend gute HowTo's für die
Installation von Alsa im
Internet, ausserdem haben die Pakete alsa-base und
alsa-utils
Dokumentation in /usr/share/doc/alsa-base bzw
alsa-utils abegelegt.

Andreas


This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.



Re: Volume Control problem

2005-01-09 Thread Andreas Pakulat
On 09.Jan 2005 - 15:12:25, Lucas Lang wrote:
 alsaconf  error message ist
 modinfo: snd: no modules found with this name
 im weiteren dann
 No supported PnP or PCI card found
 dito in /var/log/messages
 isapnp: Scanning for PnP cards ... No Plug  Play
 device found

Dir fehlen die alsa-Module, diese stecken für 2.4.27er Kernel in einem
extra Paket das alsa-modules-2.4.27 heisst (IIRC, apt-cache search
alsa-modules sollte dir da weiterhelfen)

 hast du die oss module entladen was genau meinst
 du damit? ich haette das tun sollen? oder wolltest
 du dich nur vergewissern, dass ich das nicht
 gemacht habe? habe ich naemlich m.e. nicht gemacht.

Ich meinte ob du das gemacht hast (modprobe -r modulname), aber
eigentlich sollte alsaconf das auch machen.

 howtos: klar weiss ich, dass es die gibt. nur ...
 eigentlich moechte ich alsa nicht wirklich
 installieren, denn ich sehe ja (wegen zweitem
 quasi identischen rechner), dass es auch ohne alsa
 funktioniert.

Hmm, wenn du keine Möglichkeit findest einzustellen ob du Alsa oder
OSS benutzen willst, erzähl doch mal welche Desktopumgebung du benutzt
und welches Programm sich hinter Volume Control verbirgt. In meinem
KDE-Menu Multimedia-Lautstärkeregelung zeigt mir den
gnome-volume-control an... Vielleicht fehlt auch nur ein Treiber für
den Mixer (was für eine Soundkarte hast du?)... Wenn du KDE benutzt:
nimm kmix das ist besser, da KDE ja eh mit artsd läuft... 

Kannst du das ToFu lassen - in Dtl. lesen die meisten Menschen von
oben nach unten. (http://learn.to/quote)

Andreas

-- 
You are the only person to ever get this message.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Lucas Lang
 Dir fehlen die alsa-Module

apt-get install alsa-modules-2.4.27-1-686

ok, aber 7 oder 8 error message, alle
depmod: Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-

 Ich meinte ob du das gemacht hast
 (modprobe -r modulname),

modprobe -r alsa
Note: /etc/modules.conf is more recent than
/lib/modules/2.4.27-1-686/modules.dep

 welche Desktopumgebung du benutzt

gnome

 welches Programm sich hinter Volume Control
verbirgt.

gnome-volume-control

 Vielleicht fehlt auch nur ein Treiber für
den Mixer

wie koennte ich das herausfinden?

 (was für eine Soundkarte hast du?)

soundblaster live

 Kannst du das ToFu lassen

ok, habe ich kapiert *smile*

lucas


This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.



Re: Volume Control problem

2005-01-09 Thread Andreas Pakulat
On 09.Jan 2005 - 17:48:09, Lucas Lang wrote:
  Dir fehlen die alsa-Module
 
 apt-get install alsa-modules-2.4.27-1-686
 
 ok, aber 7 oder 8 error message, alle
 depmod: Unresolved symbols in
 /lib/modules/2.4.27-1-686/updates/alsa/snd-

Das sollte nicht passieren IMHO, welche genau?

  Ich meinte ob du das gemacht hast
  (modprobe -r modulname),
 
 modprobe -r alsa
 Note: /etc/modules.conf is more recent than
 /lib/modules/2.4.27-1-686/modules.dep

Das Modul alsa gibts nicht und ich meinte auch eher sowas wie modprobe
-r sb16 oder sblive (Weiss jetzt nicht wie das OSS-Modul für sbLive
heisst).

  welche Desktopumgebung du benutzt
 
 gnome

Benutzt du den Soundserver von Gnome? Hast du mal ins control-center
geguckt ob da was auffällig ist?

  Vielleicht fehlt auch nur ein Treiber für
 den Mixer
 
 wie koennte ich das herausfinden?

Eventuell gibt dir die config des Kernels da eine Hilfe, ansonsten
wüsste ich auch grad nichts..

  Kannst du das ToFu lassen
 
 ok, habe ich kapiert *smile*

Wenn wir schon dabei sind: Dein Mailprogramm zerstört ausserdem die
Referenzen, aber ich schätze da hast du nicht allzuviel Einfluss
drauf?

Andreas

-- 
Don't you feel more like you do now than you did when you came in?


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Lucas Lang

 apt-get install alsa-modules-2.4.27-1-686 
 ok, aber 7 oder 8 error message,
 welche genau?

Setting up alsa-modules-2.4.27-1-686 (1.0.6a+5) ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-pdaudiocf.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-tea575x-tuner.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-audio.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-lib.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-usx2y.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vx-cs.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxp440.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxpocket.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd.o


mir ist noch was anderes aufgefallen. an sich ist
die soundkarte da:

pci bus 0x cardnum 0x09 function 0x00: vendor
0x1102 device 0x0002
 Creative Labs SB Live! EMU10k1

pci bus 0x cardnum 0x09 function 0x01: vendor
0x1102 device 0x7002
 Creative Labs SB Live! MIDI/Game Port


_aber_ hier laeuft was falsch, vielleicht haengt
das damit zusammen:

Jan  9 11:59:28 localhost kernel: gameport0:
Emu10k1 Gameport at 0xb800 size 8 speed 1217 kHz
Jan  9 11:59:28 localhost kernel: uhci.c: USB
Universal Host Controller Interface driver v1.1
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:get_device PCI ROOT HID fail=0x5
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_







This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Lucas Lang

 apt-get install alsa-modules-2.4.27-1-686
 ok, aber 7 oder 8 error messages

Setting up alsa-modules-2.4.27-1-686 (1.0.6a+5) ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-pdaudiocf.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-tea575x-tuner.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-audio.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-lib.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-usx2y.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vx-cs.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxp440.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxpocket.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd.o


noch was anderes in diesem zusammenhang. ein
scanpci liefert u.a. folgendes resultat:

pci bus 0x cardnum 0x09 function 0x00: vendor
0x1102 device 0x0002
 Creative Labs SB Live! EMU10k1

pci bus 0x cardnum 0x09 function 0x01: vendor
0x1102 device 0x7002
 Creative Labs SB Live! MIDI/Game Port

wo hingegen hier m.e. etwas nicht stimmt:

Jan  9 11:59:28 localhost kernel: gameport0:
Emu10k1 Gameport at 0xb800 size 8 speed 1217 kHz
Jan  9 11:59:28 localhost kernel: uhci.c: USB
Universal Host Controller Interface driver v1.1
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:get_device PCI ROOT HID fail=0x5
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_


This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-09 Thread Michelle Konzack
Am 1997-01-01 01:38:27, schrieb Lucas Lang:

Währe es DIR möglich, Deinem Computer die richtige Zeit beizubringen ?

Ich hasse es , wenn mir meine postgresql Datenbank eine Warnmeldung
schickt, weil ich eine Message von vor über 8 Jahren erhalten habe...

Mittlerweile sind es zwei Messages !

Ich finde es nicht besonderst lustig, laufend irgendwelche Tabellen
manuell löschen zu müssen...


Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Re: Volume Control problem

2005-01-09 Thread Lucas Lang
[hatte ein boot-problem und habe leider zwei
postings mit datum 1/1/97 versandt. sorry]
---

 apt-get install alsa-modules-2.4.27-1-686
 ok, aber 7 oder 8 error messages

Setting up alsa-modules-2.4.27-1-686 (1.0.6a+5) ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-pdaudiocf.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-tea575x-tuner.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-audio.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-lib.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-usb-usx2y.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vx-cs.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxp440.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd-vxpocket.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686/updates/alsa/snd.o


noch was anderes in diesem zusammenhang. ein
scanpci liefert u.a. folgendes resultat:

pci bus 0x cardnum 0x09 function 0x00: vendor
0x1102 device 0x0002
Creative Labs SB Live! EMU10k1

pci bus 0x cardnum 0x09 function 0x01: vendor
0x1102 device 0x7002
Creative Labs SB Live! MIDI/Game Port

wo hingegen hier m.e. etwas nicht stimmt:

Jan  9 11:59:28 localhost kernel: gameport0:
Emu10k1 Gameport at 0xb800 size 8 speed 1217 kHz
Jan  9 11:59:28 localhost kernel: uhci.c: USB
Universal Host Controller Interface driver v1.1
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
Jan  9 11:59:28 localhost kernel: shpchp:
acpi_shpchprm:get_device PCI ROOT HID fail=0x5
Jan  9 11:59:28 localhost kernel: pci_hotplug: PCI
Hot Plug PCI Core version: 0.5
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKA._STA] (Node effeea40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKB._STA] (Node effeeb40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKC._STA] (Node effeec40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-1133:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_EXIST
Jan  9 11:59:28 localhost kernel: ACPI-0154:
*** Error: Method execution failed
[\_SB_.LNKD._STA] (Node effeed40), AE_NOT_


This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Volume Control problem

2005-01-08 Thread Lucas Lang
hallo,

mein volume control (applicationsmultimedia)
funktioniert nicht. fehlermeldung: Sorry, no
mixer elements and/or devices found.

habe in der not das package setmixer installiert,
damit kann ich nun auf der kommandozeile die
laustaerke aendern (bspw.: setmixer -V vol 100
fuer volle lautstaerke).

frage: was muss ich machen, damit mein volume
control funktioniert?

$ uname -r
2.4.27-1-686

lucas



This message was sent from the free private e-mail service by easy.com, the 
portal site owned by Stelios and the easyGroup. This email service is available 
to all members of the public to use for personal reasons only.  Not all 
subscribers to this e-mail service are representatives of an easyGroup company.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: Volume Control problem

2005-01-08 Thread Christian Leitold
Lucas Lang wrote:
hallo,
mein volume control (applicationsmultimedia)
funktioniert nicht. fehlermeldung: Sorry, no
mixer elements and/or devices found.
Könnte sein, dass das volume control ALSA will, und das bei dir nicht 
installiert ist. Ich kann mich jedenfalls erinnern, einmal eine ähnliche 
Fehlermeldung gehabt zu haben, die nach der erfolgreichen Installation 
und Konfiguration von ALSA verschwunden ist.

mfg
Christian Leitold
--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)


Re: Volume Control problem

2005-01-08 Thread Chrissie Brown
On Sat, 08 Jan 2005 21:40:07 +0100, Lucas Lang wrote:


 frage: was muss ich machen, damit mein volume
 control funktioniert?

Hast du alsa am laufen? Wenn nicht, installiers mal und probiers nochmal.
-- 
   bis denne,
 Chrissie


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)




Re: Gnome Volume Control, not the panel applet

2004-12-21 Thread Cliff Flood
Andrea Vettorello wrote:
Ah, should have paid more attention. When you talked above to binding
keys to change volume, are you refering to a particular application or
the Gnome keyboard shortcuts?
Yes, the Gnome Keyboard Shortcuts has a section Sound with 3 
interesting elements, Volume mute, Volume down, Volume up. I have 
them bound to F6, F7, F8. When I press any of these keys I get an 
on-screen display in the middle of the bottom half of my screen to give 
me feedback on the action, a volume indicating bar shortens and 
lengthens or the notes disappear from the icon when I press the mute 
key.
So that all appears well, except this particular aspect of the system is 
changing the volume on the wrong channel of my device.

Where can I change this?
Thanks,
--
Cliph/ff
http://chicks-dig-unix.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



  1   2   >