So, maybe this is a boneheadedly obvious thing, but having just spoken with Daniel about this, I'll just summarise my findings.
I, for one, was always using alsa-driver for my new Dell laptop. As it turns out, Dan has the identical laptop, but he's always been using the in-kernel driver. I always just chalked it up to "well, Dan's just leeter than me in matters of kernel things anyway, so yeah." Then one day, I walked over and I asked him what I was doing wrong in my kernel config. You know what it was for me? I saw that I had intel audio hardware, so I kept configuring intel8x0. As soon as I activated hda-intel, it was all good. Now, obviously that was just me being stupid and ignorant, but there are possibly a couple more issues. One is that if you've emerged alsa-driver for your kernel, and then recompile that kernel, you're possibly mixing two types of alsa drivers in the /lib/modules directory which would definitely lead to brokenness. So my challenge to those having problems: try it out on a fresh kernel and report your bug. And, please let's dispense with this "forcing" people to do anything. There's no such ultimatum at work here, please don't jump to erroneous conclusions. thanks, Seemant
signature.asc
Description: This is a digitally signed message part
