On Sat 17 Sep 2016 at 20:10:15 -0400, Felix Miata wrote:

> Lisi Reisz composed on 2016-09-17 11:56 (UTC+0100):
> >Alan McConnell wrote:
> >>Alas for the days of wheezy, when everything _worked_!!
> >Wheezy is LTS (though admittedly more successfully for servers), so if
> >everything Just Worked, and you liked it, why did you change?  There are
> >indeed valid reasons, but what is yours?
> I sense Alan expects everyone here has read and remembers every post he has
> written. He told us his, though indirectly:
> https://lists.debian.org/debian-user/2016/09/msg00296.html
> Synopsis:
> Wheezy was on old puter, with mature hardware supported by FOSS.
> Jessie is on new (unspecified model) Dell (with Win10), with unknown
> hardware with unknown FOSS support.

Contrasting the behaviour of machine A with machine B (worked on my old
machine, works fine with Windows etc) and indulging in nostalgia is only
of passing interest when the objective is to get an aspect of machine A
to function. If is like telling a doctor you ran a marathon every week
twenty years ago when the present issue is having two broken legs.

> New puter's design date is *probably* newer than Jessie, which would mean
> problems can be *expected*, because he's not tried an OS that's newer than
> his puter, such as Stretch.
> Win10 works without problems because Dell made sure of it. Dell didn't do
> that with Jessie or any other Debian, and probably with no other Linux
> either.

Information about the audio card can be extracted from the output of
'lspci -v'. It could even be publicised here as an a aid to diagnosis.

ALSA is built into the kernel so it is fruitless expecting to find
packages to install it. However 'lsmod | grep snd' would be useful for
people to see.

> If Alan wants serious help, he needs to stop keeping his hardware info
> secret. Ordinarily I would expect he could share the copious output provided
> by alsa-info.sh, but it seems to be absent from Jessie, so he would need to
> find it elsewhere in order to run it, e.g.:
> http://www.alsa-project.org/db/?f=a59c5f2edf8a61119a94d34a5d8afc13703f0b71

Pulseaudio is sometimes thought to be the culprit in audio issues. It
can be taken out of the picture with 'apt-get purge pulseaudio'
(reinstatement is easy) and any other sound-related packages installed
in an endeavour to solve the problem also purged.

Besides the nature of the hardware a bunch of users would be interested
in its capabilities. 'aplay -L' and 'amixer' would go some way to
satisfying their curiosity.

Meanwhile, the device might spring into life and consequently the four
outputs of interest would not be needed.


Reply via email to