On 2018-10-10, Michael Lange wrote:
>
> snd-pcm-oss *is* an alsa module, you won't get anywhere with that without
> loading the proper alsa drivers for your sound card too.
>
>>
>> https://wiki.debian.org/ALSA#ALSA_and_OSS
>>
>> If you don't unload all OSS modules then ALSA modules will not be
On Wed, 10 Oct 2018 12:00:20 + (UTC)
Curt wrote:
(...)
> > /dev/dsp surely exists in case the snd-pcm-oss driver module is
> > loaded.
>
> In this very case, in fact, according to the OP's lsmod list, so, right.
>
> Of course, at the same time we are obliged to note gandering at his
> modul
Michael Lange writes:
> Hi,
>
> > Actually that would be '/dev/snd*' not '/dev/dsp' (the latter being the
> > old, obsolete oss sound device from way back when, which I doubt would
> > exist on Stretch at all).
>
> /dev/dsp surely exists in case the snd-pcm-oss driver module is loaded.
>
> Reg
On 2018-10-10, Michael Lange wrote:
> Hi,
>
> On Tue, 9 Oct 2018 12:33:11 + (UTC)
> Curt wrote:
>
> (...)
>> Actually that would be '/dev/snd*' not '/dev/dsp' (the latter being the
>> old, obsolete oss sound device from way back when, which I doubt would
>> exist on Stretch at all).
>
> /dev/
Hi,
On Tue, 9 Oct 2018 12:33:11 + (UTC)
Curt wrote:
(...)
> Actually that would be '/dev/snd*' not '/dev/dsp' (the latter being the
> old, obsolete oss sound device from way back when, which I doubt would
> exist on Stretch at all).
/dev/dsp surely exists in case the snd-pcm-oss driver modu
dot...@gmail.com wrote:
> Conclusion: I consider the problem solved (or better, a "non-problem").
> Because I spent too much time on it, I'll give it up andl use the newly
> installed and working debian/sid, transferring configuration step by step
> and verify that sound continue working.
>
What
On 2018-10-09, dot...@gmail.com wrote:
>
> On Tue, Oct 9, 2018 at 2:02 PM Curt wrote:
>
>> On the archlinux sound troubleshooting wiki ("The only device
>> shown is 'dummy output'..." section), they suggest
>> executing
>>
>> fuser -v /dev/snd/*
>>
>>
> Thank you for the hint. I never came acro
On Tue, Oct 9, 2018 at 2:02 PM Curt wrote:
> On the archlinux sound troubleshooting wiki ("The only device
> shown is 'dummy output'..." section), they suggest
> executing
>
> fuser -v /dev/snd/*
>
>
Thank you for the hint. I never came across that link.
Unfortunately, I tried and it seems that
On 2018-10-08, dot...@gmail.com wrote:
>
> The problem in short: no sound card available to pulsaudio, while ALSA
> seems to correctly detect HDA Intel PCH.
> To make the problem more puzzling, in the same laptop with an ubuntu live
> (with kernel 4.15) audio works correctly.
>
On the archlinux s
On Mon, Oct 8, 2018 at 7:08 PM wrote:
> Sorry for the subject not-so-specific but I hope this message can start a
> first iteration to better focus my problem.
>
> The problem in short: no sound card available to pulsaudio, while ALSA
> seems to correctly detect HDA Intel PCH.
> To make the probl
On Mon, Oct 8, 2018 at 9:35 PM Kent West wrote:
>
> Sounds roughly similar to a problem I've been having. I tracked it down to
> Timidity grabbing the sound card. I don't know enough to make it fixed
> permanently, but as a temporary fix after a reboot when the problem
> manifests, I do a
>
> ps
On Monday 08 October 2018 15:52:08 David Wright wrote:
> On Mon 08 Oct 2018 at 20:52:28 (+0200), dot...@gmail.com wrote:
> > On Mon, Oct 8, 2018 at 8:48 PM Gene Heskett
wrote:
> > > But, does dmesg report its successful use at the last boot?
> > >
> > > (dmesg | grep -i microcode)
> >
> > [0
On Mon 08 Oct 2018 at 14:34:26 (-0500), Kent West wrote:
> On Mon, Oct 8, 2018 at 12:09 PM wrote:
>
> > Sorry for the subject not-so-specific but I hope this message can start a
> > first iteration to better focus my problem.
> >
> >
> Sounds roughly similar to a problem I've been having. I track
On Mon 08 Oct 2018 at 20:52:28 (+0200), dot...@gmail.com wrote:
> On Mon, Oct 8, 2018 at 8:48 PM Gene Heskett wrote:
>
> >
> > But, does dmesg report its successful use at the last boot?
> >
> > (dmesg | grep -i microcode)
> [0.00] microcode: microcode updated early to revision 0x8e, date
On Mon, Oct 8, 2018 at 12:09 PM wrote:
> Sorry for the subject not-so-specific but I hope this message can start a
> first iteration to better focus my problem.
>
>
Sounds roughly similar to a problem I've been having. I tracked it down to
Timidity grabbing the sound card. I don't know enough to
On Monday 08 October 2018 14:52:28 dot...@gmail.com wrote:
> On Mon, Oct 8, 2018 at 8:48 PM Gene Heskett
wrote:
> > But, does dmesg report its successful use at the last boot?
> >
> > (dmesg | grep -i microcode)
>
> [0.00] microcode: microcode updated early to revision 0x8e,
> date = 201
On Mon, Oct 8, 2018 at 8:48 PM Gene Heskett wrote:
>
> But, does dmesg report its successful use at the last boot?
>
> (dmesg | grep -i microcode)
[0.00] microcode: microcode updated early to revision 0x8e, date =
2018-03-24
[1.472209] microcode: sig=0x806e9, pf=0x80, revision=0x8e
[
On Mon, Oct 8, 2018 at 8:27 PM deloptes wrote:
> removing the .pulse or .config/pulse directory followed by reboot, could
> also help in similar cases
>
>
So sad! It didn't work. :(
Thank you anyway
a.
On Monday 08 October 2018 14:42:19 dot...@gmail.com wrote:
> On Mon, Oct 8, 2018 at 7:16 PM Jude DaShiell
wrote:
> > Did you install the intel microcode package yet? This may solve the
> > problem or may not. Failing that, try an install of the debian
> > firmware
>
> Jude, it is very sad (for
On Mon, Oct 8, 2018 at 7:16 PM Jude DaShiell wrote:
> Did you install the intel microcode package yet? This may solve the
> problem or may not. Failing that, try an install of the debian firmware
>
>
Jude, it is very sad (for me, of course) to tell you that the intel
microcode was already insta
On Mon, Oct 8, 2018 at 7:16 PM steve wrote:
>
> You did verify that your sound is NOT muted in some gui or alsamixer,
> didn't you ?
>
>
Thank you Steve fr your quick reply.
As I tried to explain (maybe not clearly enough, I'm sorry), pulse just
doesn't see any card at all.
In any case, followin
steve wrote:
> Hi,
>
> You did verify that your sound is NOT muted in some gui or alsamixer,
> didn't you ?
removing the .pulse or .config/pulse directory followed by reboot, could
also help in similar cases
regards
Hi,
You did verify that your sound is NOT muted in some gui or alsamixer,
didn't you ?
Steve
23 matches
Mail list logo
