Bug#439072: snd-intel8x0 line-in not working in later 2.6.x kernels
On Wed, Aug 22, 2007 at 04:13:19AM +0200, Josip Rodin wrote:
> On Wed, Aug 22, 2007 at 02:52:59AM +0200, Josip Rodin wrote:
> > I'm reporting this bug that I have been seeing for a while and which is
> > a regression from a few months/years ago - the line-in input simply doesn't
> > work right. arecord(1) just doesn't record anything with it, it doesn't show
> > any errors, it records silence. The recording from the same external source
> > works just fine with the microphone input.
>
> > This works just fine with the same hardware in MS Windows (ugh), and it also
> > worked fine with an earlier 2.6.x kernel version that I had been using when
> > I was still running sarge on this machine. But, I removed it in the meantime
> > so I don't know which one it was. I think it was 2.6.16 or so, but I'm not
> > sure. It's definitely not working with >= 2.6.18 (I still have one of those
> > and it behaves the same as 2.6.21).
>
> Oh, I might have been too vague there. I can't exactly reproduce the old
> state because I changed much of my other hardware in this machine since and
> my old kernel images won't boot; and then I also noticed that there was once
> an old OSS driver and then I switched to alsa, but I don't have backups of
> my ancient /etc/modules file so I don't know when that was.
>
> I re-selected the old-style i810_audio driver in 2.6.21 and compiled it,
> unloaded the ALSA driver, loaded the old driver, and voila, everything went
> back to normal, I can hear the TV sound just fine. So, it might be that this
> is an OSS->ALSA regression that slipped through the cracks?
After an upstream developer helped debug it, it seems that it works if I use
alsamixer to change the mixer from the 4 channel mode to the 2 channel mode.
The 2ch mode is supposed to be the default; I have no idea why my alsamixer
setup used the 4ch mode, at least I certainly don't remember ever fiddling
with that setting (because I have no idea what it really means :).
Can someone tell me the proper steps to test the default value to see if
the bug was really just some local mishap? Move away
/var/lib/alsa/asound.state and reload the modules?
--
2. That which causes joy or happiness.
Reply to: