"Francisco Zabala" < [EMAIL PROTECTED]> wrote:
I have a similar problem. After I restart my computer xmms says that
there isn't a soundcard. So:
1. I have to execute ./snddevices
2. Then, run alsa-config
3. Then run alsamixer (to unmute)
And then I have sound again. Any suggestions to avoid ha
On 1/7/07, Andrei Popescu <[EMAIL PROTECTED]> wrote:On Sat, 6 Jan
2007 16:27:14 -0800
"Francisco Zabala" <[EMAIL PROTECTED]> wrote:
I have a similar problem. After I restart my computer xmms says that
there isn't a soundcard. So:
1. I have to execute ./snddevices
2. Then, run alsa-config
3. The
On Sat, 6 Jan 2007 16:27:14 -0800
"Francisco Zabala" <[EMAIL PROTECTED]> wrote:
> I have a similar problem. After I restart my computer xmms says that
> there isn't a soundcard. So:
> 1. I have to execute ./snddevices
> 2. Then, run alsa-config
> 3. Then run alsamixer (to unmute)
>
> And then I
I have a similar problem. After I restart my computer xmms says that there
isn't a soundcard. So:
1. I have to execute ./snddevices
2. Then, run alsa-config
3. Then run alsamixer (to unmute)
And then I have sound again. Any suggestions to avoid having to go through
this process?
Cheers,
-Cisc
On Fri, 5 Jan 2007 17:19:55 +0100 (CET)
Ferry Toth <[EMAIL PROTECTED]> wrote:
>
> I have the same problem (Debian Etch 2.6.18).
>
> I have traced it back to /etc/init.d/alsa-utils not being called.
> See: /etc/alsa/modprobe-post-install.d/alsa-utils
>
> In my confiration ALSA should be configu
On Wed, Dec 27, 2006 at 12:15:37PM +, Brad Rogers wrote:
> Simply ignore the hi-ASCII chars to end up with alsactl
> store. Bill used quote chars that don't appear in
> whatever char encoding you use. Unfortunately, they did
> render to "something".
They're UTF-8, and the message was indicat
On Wed, 27 Dec 2006 10:07:00 +0100
Fritz Wettstein <[EMAIL PROTECTED]> wrote:
Hello Fritz,
> I'm sorry but I can't interpret your answer to Bill
Simply ignore the hi-ASCII chars to end up with alsactl store. Bill
used quote chars that don't appear in whatever char encoding you use.
Unfortunatel
Hello Mathias,
I'm sorry but I can't interpret your answer to Bill
Bill wrote:
snipp...
Try „alsactl store“.
snipp...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, 2006-18-12 at 23:32 +0100, Mathias Brodala wrote:
> Hello Bill.
>
> Bill, 18.12.2006 23:21:
> > I have alsa installed and working properly.
> >
> > I configure it with alsaconf.
> >
> > Everytime I reboot, I have to reconfigure it again with alsaconf.
>
> Try „alsactl store“.
>
This w
On Thu, 2006-21-12 at 19:05 +0100, Nigel Henry wrote:
> Can you post a bit of info. Which Debian version, and kernel are you using?
> For the kernel type uname -r. Which desktop? I ask because I'm using KDE.
> Does typing as user, cat /proc/asound/cards show only one soundcard as card0?
> Wh
On Thursday 21 December 2006 12:24, Bill wrote:
> > On Mon, Dec 18, 2006 at 02:21:05PM -0800, Bill wrote:
> > > Hi folks,
> > >
> > > I have alsa installed and working properly.
> > >
> > > I configure it with alsaconf.
> > >
> > > Everytime I reboot, I have to reconfigure it again with alsaconf.
> On Mon, Dec 18, 2006 at 02:21:05PM -0800, Bill wrote:
> > Hi folks,
> >
> > I have alsa installed and working properly.
> >
> > I configure it with alsaconf.
> >
> > Everytime I reboot, I have to reconfigure it again with alsaconf.
> >
> > It's only a few keypresses but annoying.
> >
> > Is
On Mon, Dec 18, 2006 at 02:21:05PM -0800, Bill wrote:
> Hi folks,
>
> I have alsa installed and working properly.
>
> I configure it with alsaconf.
>
> Everytime I reboot, I have to reconfigure it again with alsaconf.
>
> It's only a few keypresses but annoying.
>
> Is this a known issue?
>
>
On Tue, Dec 19, 2006 at 09:20:08PM -0500, Kevin Mark wrote:
> On Tue, Dec 19, 2006 at 01:17:42PM -0500, [EMAIL PROTECTED] wrote:
> >
> > How strange. I can't log in to anything other than Gnome. icewm is
> > installed,m is my default window manager, but I get Gnome.
> >
> Hi hendrik,
> what do
On Tue, Dec 19, 2006 at 01:17:42PM -0500, [EMAIL PROTECTED] wrote:
> On Tue, Dec 19, 2006 at 06:18:12PM +0100, Nigel Henry wrote:
> > On Tuesday 19 December 2006 17:19, [EMAIL PROTECTED] wrote:
> > > I've just found the reason (at least on my laptop): the problem is with
> > > esound package -
> >
[EMAIL PROTECTED] wrote:
Thanks, this did the trick - installing of libesd-alsa0 instead of libesd
solved the problem.
Now the question is - shouldn't libesd-alsa0 be automatically installed
with alsa instead of libesd?
Kind regards,
Vladimir.
I would say; but I'm not sure that the user list
On Tuesday 19 December 2006 19:17, [EMAIL PROTECTED] wrote:
> On Tue, Dec 19, 2006 at 06:18:12PM +0100, Nigel Henry wrote:
> > On Tuesday 19 December 2006 17:19, [EMAIL PROTECTED] wrote:
> > > I've just found the reason (at least on my laptop): the problem is with
> > > esound package -
> > >
> > >
> Also, on my system, with 'libesd-alsa0' installed (instead of 'libesd'),
> sound playing is not blocked by esd. I think this can also fix problem.
HTH.
Thanks, this did the trick - installing of libesd-alsa0 instead of libesd
solved the problem.
Now the question is - shouldn't libesd-alsa0 be au
On Tue, Dec 19, 2006 at 06:18:12PM +0100, Nigel Henry wrote:
> On Tuesday 19 December 2006 17:19, [EMAIL PROTECTED] wrote:
> > I've just found the reason (at least on my laptop): the problem is with
> > esound package -
> >
> > rover:/home/rover# ps aux | grep esd
> > rover 2655 0.0 0.4 204
On 12/19/2006 10:19 AM, [EMAIL PROTECTED] wrote:
I've just found the reason (at least on my laptop): the problem is with
esound package -
rover:/home/rover# ps aux | grep esd
rover 2655 0.0 0.4 2048 580 ?S18:39 0:00
/usr/bin/esd -nobeeps
prevents alsa from working. After
Nigel Henry wrote:
Esd should not be being started at bootup, as it's a Gnome thing, but will
probably be started when you login to Gnome. I can't login to Gnome on Etch
for some reason. It's probably annoyed that I use KDE. Anyway I booted up
Sarge, and logged into Gnome, there under "Applicat
Bill wrote:
> On Mon, 2006-18-12 at 20:06 -0500, Colin wrote:
>> Bill wrote:
>> > I configure it with alsaconf.
>> >
>> > Everytime I reboot, I have to reconfigure it again with alsaconf.
>>
>> It's not alsactl store like the other posters have said. You need to
>> load the sound modules that a
On Tuesday 19 December 2006 17:19, [EMAIL PROTECTED] wrote:
> I've just found the reason (at least on my laptop): the problem is with
> esound package -
>
> rover:/home/rover# ps aux | grep esd
> rover 2655 0.0 0.4 2048 580 ?S18:39 0:00
> /usr/bin/esd -nobeeps
>
> prevents a
I've just found the reason (at least on my laptop): the problem is with
esound package -
rover:/home/rover# ps aux | grep esd
rover 2655 0.0 0.4 2048 580 ?S18:39 0:00
/usr/bin/esd -nobeeps
prevents alsa from working. After alsaconf there is no esd running, but
after reboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Before alsaconf:
[EMAIL PROTECTED]:~$ cat /proc/asound/cards
0 [SI7012 ]: ICH - SiS SI7012
SiS SI7012 with CS4299 at 0x1c00, irq 11
after alsaconf:
[EMAIL PROTECTED]:~$ cat /proc/asound/cards
0 [SI7012 ]: ICH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh, I forgot: I'm using etch.
I've already reinstalled alsa-base and alsa-utils. The most interesting
thing is that after the etch install alsa worked just fine.
Unfortunately I could not recall when the problem arise - chances are
that the problem ari
On Tuesday 19 December 2006 14:12, Vladimir Kozlov wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have absolutely the same problem, and I'm totally lost...
>
> The loaded modules before alsaconf:
>
> [EMAIL PROTECTED]:~$ lsmod | grep snd
> snd_intel8x0 30332 2
> snd_ac97_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have absolutely the same problem, and I'm totally lost...
The loaded modules before alsaconf:
[EMAIL PROTECTED]:~$ lsmod | grep snd
snd_intel8x0 30332 2
snd_ac97_codec 83104 1 snd_intel8x0
snd_ac97_bus2400 1 snd_ac9
On Mon, Dec 18, 2006 at 11:52:00PM -0800, Bill wrote:
> On Mon, 2006-18-12 at 20:06 -0500, Colin wrote:
> > It's not alsactl store like the other posters have said.
> > You need to load the sound modules that alsaconf loads
> > after it has run.
>
> How to do that?
In days gone by you could stick
On Mon, 2006-18-12 at 20:06 -0500, Colin wrote:
> Bill wrote:
> > I configure it with alsaconf.
> >
> > Everytime I reboot, I have to reconfigure it again with alsaconf.
>
> It's not alsactl store like the other posters have said. You need to
> load the sound modules that alsaconf loads after it
Bill wrote:
> I configure it with alsaconf.
>
> Everytime I reboot, I have to reconfigure it again with alsaconf.
It's not alsactl store like the other posters have said. You need to
load the sound modules that alsaconf loads after it has run.
And no, I don't know what those modules are because
On Mon December 18 2006 14:21, Bill wrote:
> Hi folks,
>
> I have alsa installed and working properly.
>
> I configure it with alsaconf.
>
> Everytime I reboot, I have to reconfigure it again with alsaconf.
>
> It's only a few keypresses but annoying.
>
> Is this a known issue?
>
> What can I do to
Hello Bill.
Bill, 18.12.2006 23:21:
> I have alsa installed and working properly.
>
> I configure it with alsaconf.
>
> Everytime I reboot, I have to reconfigure it again with alsaconf.
Try „alsactl store“.
Regards, Mathias
--
debian/rules
signature.asc
Description: OpenPGP digital signa
33 matches
Mail list logo
