On Tue, Aug 4, 2015 at 12:56 PM, Bruno Schneider wrote:
> It's a notebook, no plugs or wires to test. But I did check the
> hardware by booting into an old Mandriva partition and sound works
> there.
I'm bumping up the thread with new information: sound works on
headphones, only the speakers seem
On Tuesday 04 August 2015 16:29:08 Nicolas George wrote:
> Le septidi 17 thermidor, an CCXXIII, Lisi Reisz a écrit :
> > > I assume, of course, that you re-re-checked the speakers and tried to
> > > plug them in all sockets?
> >
> > Sorry, but... And checked that they are plugged in to a turned on
On Tue, Aug 4, 2015 at 11:16 AM, Nicolas George wrote:
> You could try posting the output of amixer (with the correct -D option for
> your card), someone may spot something not correctly routed.
Output is at the bottom. Also included a screenshot of alsamixer here:
http://postimg.org/image/jf
Le septidi 17 thermidor, an CCXXIII, Lisi Reisz a écrit :
> > I assume, of course, that you re-re-checked the speakers and tried to plug
> > them in all sockets?
> Sorry, but... And checked that they are plugged in to a turned on wall
> socket
> and turned on themselves?
That is not even enough
On Tuesday 04 August 2015 15:16:39 Nicolas George wrote:
> I assume, of course, that you re-re-checked the speakers and tried to plug
> them in all sockets?
Sorry, but... And checked that they are plugged in to a turned on wall socket
and turned on themselves?
Lisi
--
To UNSUBSCRIBE, email t
Le septidi 17 thermidor, an CCXXIII, Bruno Schneider a écrit :
> I can see my card in /proc/asound/cards:
Good.
> But I can't play sound on it:
The reason is in the error message. Unlike some other systems, Linux gives
useful error messages, reading them is a good habit to take.
> aplay: set_pa
On Mon, Aug 3, 2015 at 5:18 PM, Nicolas George wrote:
>
> I gave a few hints about the tools to use for that in this message:
>
> https://lists.debian.org/debian-user/2015/07/msg00648.html
I can see my card in /proc/asound/cards:
$ cat /proc/asound/cards
0 [Generic]: HDA-Intel - HD-Audio
[Please don't top post, it makes it hard to follow and reply.]
On Mon, Aug 03, 2015 at 12:48:36PM -0700, Mike Izbicki wrote:
> The list of modules helped a bunch! I modprobed them one-by-one and
> after running `modprobe snd_hda_intel` a bunch of new devices showed
> up and sound started working
Le sextidi 16 thermidor, an CCXXIII, Bruno Schneider a écrit :
> Therefore, I'm starting to think it is an ALSA problem. But I don't
> know where to continue my search for errors.
I gave a few hints about the tools to use for that in this message:
https://lists.debian.org/debian-user/2015/07/msg0
I have a problem that is similar to Mike's, but I'm using Debian
testing (stretch).
One day, sound stopped working and I just can't make it work again.
I'm been looking mostly into pulseaudio for any misconfigurations but
everything seems ok. Running "pacmd list-sinks
On Mon, 3 Aug 2015 12:48:36 -0700
Mike Izbicki wrote:
> The list of modules helped a bunch! I modprobed them one-by-one and
> after running `modprobe snd_hda_intel` a bunch of new devices showed
> up and sound started working.
>
> Thanks!
>
outstanding!
Very glad to have been able to help.
The list of modules helped a bunch! I modprobed them one-by-one and
after running `modprobe snd_hda_intel` a bunch of new devices showed
up and sound started working.
Thanks!
On Mon, Aug 3, 2015 at 12:00 PM, wrote:
> On Mon, 3 Aug 2015 09:16:16 -0700
> Mike Izbicki wrote:
>
>>
>> I also just
On Mon, 3 Aug 2015 09:16:16 -0700
Mike Izbicki wrote:
>
> I also just ran the `alsaloop` program, which gave the following
> output not related to /dev/dsp:
> ```
> ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
> playback hw:0,0 open error: No such file or directory
> Loopback
On Sun, 2 Aug 2015 19:03:06 -0700
Mike Izbicki wrote:
> I *think* the fundamental problem is that /dev/dsp doesn't exist. For
> example, when I run mplayer, I get the following output:
My sound works and I do not have a /dev/dsp
>
> Running alsamixer shows a master channel and a capture chann
I run Debian Wheezy. About a month ago I updated some of my packages
and sound stopped working in all of my programs. I completely forget
the exact commands I ran or packages I upgraded. At the time I didn't
care that sounds didn't work, but now I want to get it working again.
I *
On 7/6/14, Weydson Lima wrote:
> On 7/5/14, B wrote:
>> Try to add a file in /etc/modprobe.d (eg: NAUGHTY_INTEL_SND.conf)
>> with a line in: options snd-hda-intel index=-2 (or whatever name
>> is your module's name, YMMV) and reboot.
>
>
> What should the file name be? These are the files I h
What should the file name be? These are the files I have under modprobe.d:
alsa-base-blacklist.conf
alsa-base.conf
dkms.conf
fbdev-blacklist.conf
fglrx-blacklists-radeon.conf
radeon-kms.conf
I checked the alsa-base.conf and it had those lines:
options bt87x index=-2
options cx88_alsa index=-2
op
On Sat, 5 Jul 2014 21:19:39 -0600
Weydson Lima wrote:
> I have just upgraded the kernel on my Debian box from 3.2 to 3.14
> for the first time and I have no sound on X anymore. How can I
> troubleshoot this issue?
>
> I do see the snd_hda_intel module being loaded, but I don't know
> what else I
I have just upgraded the kernel on my Debian box from 3.2 to 3.14 for the
first time and I have no sound on X anymore. How can I troubleshoot this
issue?
I do see the snd_hda_intel module being loaded, but I don't know what else
I can do to solve this.
Thank you
Anthony Campbell wrote:
[...]
>>
>> Have you tried running udevtrigger as user root? This is from bug no 430624
>> [1]:
>>
>> # udevtrigger --verbose
>>
>> "This should reload the modules you need. On next reboot, your system will
>> find
>> your soundcard. The module management is done by udev.
On 28 Sep 2007, Chris Lale wrote:
> Anthony Campbell wrote:
> > On 28 Sep 2007, Chris Lale wrote:
> >> Meanwhile, you could try my workaround [1] for Etch:
> >>
> >> "The problem in alsaconf is the result of the presence of the file
> >> /etc/modprobe.conf. This causes /etc/modprobe.d/ to be ignore
Anthony Campbell wrote:
> On 28 Sep 2007, Chris Lale wrote:
>> Meanwhile, you could try my workaround [1] for Etch:
>>
>> "The problem in alsaconf is the result of the presence of the file
>> /etc/modprobe.conf. This causes /etc/modprobe.d/ to be ignored by Debian
>> packages (including alsaconf) w
On 28 Sep 2007, Chris Lale wrote:
>
> Meanwhile, you could try my workaround [1] for Etch:
>
> "The problem in alsaconf is the result of the presence of the file
> /etc/modprobe.conf. This causes /etc/modprobe.d/ to be ignored by Debian
> packages (including alsaconf) which store their configurat
Anthony Campbell wrote:
> On 27 Sep 2007, Chris Lale wrote:
>> Anthony Campbell wrote (on the Debian-User list)
>> http://lists.debian.org/debian-user/2007/09/msg02165.html :
>>
>>> On 24 Sep 2007, Chris Lale wrote:
Florian Kulzer wrote:
This is probably because alsaconf is broken [1
On 27 Sep 2007, Chris Lale wrote:
> Anthony Campbell wrote (on the Debian-User list)
> http://lists.debian.org/debian-user/2007/09/msg02165.html :
>
> > On 24 Sep 2007, Chris Lale wrote:
> >> Florian Kulzer wrote:
> >>
> >> This is probably because alsaconf is broken [1]. What version are you
> >
Anthony Campbell wrote (on the Debian-User list)
http://lists.debian.org/debian-user/2007/09/msg02165.html :
> On 24 Sep 2007, Chris Lale wrote:
>> Florian Kulzer wrote:
>>
>> This is probably because alsaconf is broken [1]. What version are you using?
>> It
>> is slated to be fixed in version 1.
On 24 Sep 2007, Anthony Campbell wrote:
>
> Thanks very much; yes, that brings sound back. Presumably I should add
> this to /etc/modules to have it start automatically?
>
Following up to myself: adding this to /etc/modules does indeed make
sound work automatically after a reboot.
--
Anthony C
On 24 Sep 2007, Chris Lale wrote:
> Florian Kulzer wrote:
>
> This is probably because alsaconf is broken [1]. What version are you using?
> It
> is slated to be fixed in version 1.0.14-2 [2].
>
> [1]
> http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux#Some_applications_.28OSS_applicati
On 24 Sep 2007, Florian Kulzer wrote:
> On Mon, Sep 24, 2007 at 10:55:36 +0100, Anthony Campbell wrote:
> > I've just discovered that my sound has disappeared following a recent
> > upgrade in Sid, after working flawlessly for months/years.
> >
> > I suspected this was due to a problem with udev,
Florian Kulzer wrote:
> On Mon, Sep 24, 2007 at 10:55:36 +0100, Anthony Campbell wrote:
>> I've just discovered that my sound has disappeared following a recent
>> upgrade in Sid, after working flawlessly for months/years.
>>
>> I suspected this was due to a problem with udev, which has recently
>>
On Mon, Sep 24, 2007 at 10:55:36 +0100, Anthony Campbell wrote:
> I've just discovered that my sound has disappeared following a recent
> upgrade in Sid, after working flawlessly for months/years.
>
> I suspected this was due to a problem with udev, which has recently
> replaced hotplug here (not
I've just discovered that my sound has disappeared following a recent
upgrade in Sid, after working flawlessly for months/years.
I suspected this was due to a problem with udev, which has recently
replaced hotplug here (not necessarily an improvement, I think).
However, "lsmod | grep snd" seems t
Chris Dams wrote:
Dear Ye Fei and others,
I just ran 'alsaconf' but this does not help. Still no sound. :-(
Just a thought: perhaps your motherboard has integrated sound and you
want to use a PCI sound card? Make sure that the device you configure in
Alsaconf is the one you have your spe
Dear Ye Fei and others,
I just ran 'alsaconf' but this does not help. Still no sound. :-(
Best wishes,
Chris
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-4-amd64. After rebooting sound
> stopped working. lsmod still shows the right driver being loaded and I set
> the volume to a nonzero value using kmix. When I play (say) a wav file
> noatum looks like it is playing something, but I do not hear anything.
> Also other programs (e.g., pl
Dear all,
Recently I did an apt-get update followed by apt-get upgrade. This
included an upgrade to kernel 2.6.18-4-amd64. After rebooting sound
stopped working. lsmod still shows the right driver being loaded and I set
the volume to a nonzero value using kmix. When I play (say) a wav file
Hi everyone,
Wondering if anyone else has had sound stop working very recently
(within the past week). Yesterday I upgraded to 2.6.12 and noticed
that I had no sound. Thinking that 2.6.12 had problems, I downgraded
to 2.6.11, which has been working, with sound, for some time, but the
problem per
Another thing you might check is this.
/dev/dsp is the device-node used by the OSS system. `play' uses this
device (as does wavp and realplayer and many other sound
applications). To access hardware via /dev/dsp under Alsa, then, you
need to make sure that you have oss-emulation set up. The norm
I got bit by this too and posted here and on devel -- I was referred to
these two bugs:
http://bugs.debian.org/287483
http://bugs.debian.org/284356
If you read through them you'll find that they changed some symbol
references in the new kernel you installed and any modules compiled
a
> Just to verify - 'modprobe via82cxxx_audio' returns no errors, but does not
> affect the outcome of sound tests done afterwards?
Nope, here is a copy of the test I ran:
sarge:~# modprobe via82cxxx_audio
sarge:~# play /usr/share/sounds/pop.wav
playing /usr/share/sounds/pop.wav
sox: Can't open o
Jason Chagas wrote:
> Adam Aube wrote:
>> I notice that via82cxxx_audio isn't loaded. Have you tried loading it
>> via modprobe before testing your sound?
> Yes, I had tried running "modprobe via82cxxx_audio" before but it simply
> returned without errors. However, lsmod didn't show 'via82cxxx_au
Jason
On Fri, 2004-12-31 at 22:55 -0500, Adam Aube wrote:
> Jason Chagas wrote:
>
> > I recently updated my Sarge system with the latest packages and sound
> > stopped working.
>
> > All sound applications fails to open /dev/dsp. Here is an example:
>
> >
Jason Chagas wrote:
> I recently updated my Sarge system with the latest packages and sound
> stopped working.
> All sound applications fails to open /dev/dsp. Here is an example:
> % play /usr/share/sounds/pop.wav
> playing /usr/share/sounds/pop.wav
> sox: Can't open out
I recently updated my Sarge system with the latest packages and sound
stopped working. Apparently I'm not the only one who ran into this
problem. I've tried following the suggestions (except for statically
rebuilding sound core into the kernel) from the threaded discussions
below b
On Tue, 09 Nov 2004 16:05:36 +0530, JSS wrote:
> My system has 2.4.26-1-686 debian/unstable. All of a sudden, sound has
> stopped working.
> I am using i810_audio (not alsa) for sound. I am giving the information
> below (output of lsmod, /etc/modules.conf, /etc/modules and lspci|grep
> audi
My system has 2.4.26-1-686 debian/unstable. All of a sudden, sound has
stopped working.
I am using i810_audio (not alsa) for sound. I am giving the information
below (output of lsmod, /etc/modules.conf, /etc/modules and lspci|grep
audio). Any help to debug the problem and find the solution wi
You are not alone. I have an Audigy card which uses the same driver.
Since moving to 2.4.24 I have lost sound through both KDE and mpg123. I
can't find the cause yet.
My system works fine if I go back to 2.4.22.
Tony Middleton
Joris Huizer wrote:
Hello,
Still working on a 2.4.24 kernel, I
Hello,
Still working on a 2.4.24 kernel, I discovered there was no sound even
though a program was supposed to play sounds - and also that others play
sound, either;
These are specs from the systeminfo script that was posted here, resently:
PCI:
00:00.0 Host bri
On Tue, 3 Sep 2002 22:04:14 -0500
[EMAIL PROTECTED] (Martin A. Hansen) wrote:
> i upgraded my kernel from 2.4.17 to 2.4.19.
>
> i used to have alsa working, but now it dont anymore.
>
> i compile my own alsa package with make-kpkg.
>
> the speakers click when i start alsa. alsamixer seems to b
On Tue, 03 Sep 2002, Martin A. Hansen wrote:
> hi there
>
> i upgraded my kernel from 2.4.17 to 2.4.19.
>
> i used to have alsa working, but now it dont anymore.
>
> i compile my own alsa package with make-kpkg.
Hi,
you have to compile your alsa-packages again every-time you upgrade or
compil
On Tue, 03 Sep 2002, Martin A. Hansen wrote:
> hi there
>
> i upgraded my kernel from 2.4.17 to 2.4.19.
> i compile my own alsa package with make-kpkg.
Hi,
you have to compile your alsa-packages again every-time you upgrade or
compile a new kernel.
As root, go to the the base of the kernel sour
i am aware of the permission trap, and no, sound does not work as root
either ...
there must be something else wrong.
martin
On Wed, Sep 04, 2002 at 01:19:23AM -0400, C. Schanck wrote:
> On Tuesday 03 September 2002 11:04 pm, Martin A. Hansen wrote:
> > hi there
> >
> > i upgraded my kernel
hi there
i upgraded my kernel from 2.4.17 to 2.4.19.
i used to have alsa working, but now it dont anymore.
i compile my own alsa package with make-kpkg.
the speakers click when i start alsa. alsamixer seems to be working, but i can get no
soundprograms to make any sound. mpg123, alsaplayer, x
On Thu, 14 Dec 2000, Ron Hale-Evans wrote:
> I am running Potato with a SoundBlaster PCI64 sound card, which uses
> the es1370 kernel module. I installed the soundcore and es1370 modules
a couple of days ago, did a chmod a+rw to all /dev devices in group
'audio', and everything worked fine.
On Thu, 14 Dec 2000, Ron Hale-Evans wrote:
> Greetings, all--
>
> I am running Potato with a SoundBlaster PCI64 sound card, which uses
> the es1370 kernel module. I installed the soundcore and es1370 modules
> a couple of days ago, did a chmod a+rw to all /dev devices in group
> 'audio', and ever
Greetings, all--
I am running Potato with a SoundBlaster PCI64 sound card, which uses
the es1370 kernel module. I installed the soundcore and es1370 modules
a couple of days ago, did a chmod a+rw to all /dev devices in group
'audio', and everything worked fine.
This morning I was using the Window
56 matches
Mail list logo
