Re: 2.6.18-rc4-mm3 -- intel8x0 audio busted

["Miles Lane" <miles.lane@gmail.com>]

On 8/29/06, Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 29 Aug 2006 01:57:11 -0700,
> Miles Lane wrote:
> >
> > On 8/28/06, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Mon, 28 Aug 2006 11:49:39 -0700,
> > > Andrew Morton wrote:
> > > >
> > > > On Mon, 28 Aug 2006 17:11:52 +0200
> > > > Takashi Iwai <tiwai@suse.de> wrote:
> > > >
> > > > > At Sat, 26 Aug 2006 23:55:32 -0700,
> > > > > Miles Lane wrote:
> > > > > >
> > > > > > I haven't had working audio in 2.6.18-rc4-mm series (1,2,3).
> > > > > > I haven't been able to track down the cause yet.  The modules
> > > > > > all load, and there seems to be the expected enties in /proc,
> > > > > > but my sound preferences panel shows no available audio card.
> > > > > (snip)
> > > > > > Aug 26 23:16:56 localhost kernel: warning: process `alsactl' used the
> > > > > > obsolete sysctl system call
> > > > > > Aug 26 23:16:56 localhost kernel: warning: process `ls' used the
> > > > > > obsolete sysctl system call
> > > > > > Aug 26 23:16:56 localhost kernel: warning: process `alsactl' used the
> > > > > > obsolete sysctl system call
> > > > > > Aug 26 23:16:56 localhost kernel: warning: process `amixer' used the
> > > > > > obsolete sysctl system call
> > > > > > Aug 26 23:16:56 localhost kernel: warning: process `amixer' used the
> > > > > > obsolete sysctl system call
> > > > >
> > > > > Are these messages relavant?  Even "ls" fails there...
> > > > >
> > > >
> > > > No, they're just a little warning we put in there to find out how
> > > > removeable sys_sysctl() is.  (Answer: not very.  I'll drop that patch).
> > > >
> > > > It isn't relevant to this problem.
> > >
> > > OK.
> > >
> > > Then it must be something in the driver communication.
> > > Miles, do you have proper /dev/snd/* entries?
> >
> > Hello,
> >
> > I have no /dev/snd directory.
>
> That's odd.  Any udev errors?
> Do you have /sys/class/sound/* directories?

I don't know how to track down udev errors, unfortunately.
I now suspect that the problems I am having with network
device names getting messed up and this problem with
the sound drivers spring from the same cause (some
failure in device setup in udev).

Any suggestions on how to track down udev issues are
most appreciated!  I am curious to know whether this
is a bug in udev or in the kernel code.

Thanks,
       Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/