gpg: failed to create temporary file '/var/lib/lurker/.#lk0x57e30100.hantslug.org.uk.27092': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Fri Mar 23 12:37:46 2007 GMT
gpg: using DSA key B15F69BD3454B217
gpg: Can't check signature: No public key
Mike Burrows wrote:
>> At the risk of sounding a bit "you don't want to start from here", if you'd
>> disabled the onboard card in the BIOS before you installed the OS, it would
>> (should) have detected and used the PCI one.
>>
> Thanks Tony. here's a radical thought. What about booting using the
> 2.4 kernel and then upgrading again to 2.6, this time with the onboard
> sound disabled?
>
Or, blacklist the onboard soundcard modules and tell ALSA which card is
the primary.
First, work out which modules are related to your onboard sound. I have
seen bugs raised that even though the onboard sound is disabled in the
BIOS, it's still (somehow?) seen.
Use lsmod to see which drivers are loaded and work out if any of them
are being used to drive the onboard sound. Then edit
/etc/modprobe.d/alsa-base-blacklist and add the module names. i.e.
blacklist snd_via82xx
Now edit /etc/modprobe.d/alsa-base and at the bottom you can tell ALSA
which module is the primary card by setting its index to 0. i.e. I have
a Soundblaster Live! so I would use:
options snd_emu10k1 index=0
After doing this, run "update-modules" and reboot, keeping your fingers
crossed. All of the above is done as root or using sudo.
After the reboot, before doing anything, run "alsamixer" as you. Make
sure the Master and PCM channels are not muted, denoted by "MM" instead
of "00" which means unmuted. alsamixer will also tell you what card and
chip is being used in the top left corner. Pressing Escape will quit
alsamixer. I'm not sure if it's still needed, but to be on the safe side
run, as root, "alsactl store".
Regards,
David.
--
.''`. David Ramsden
: :' : http://0wned.it/
`. `'` PGP key ID: 3454B217 on wwwkeys.eu.pgp.net
`- Debian - Because it works (tm).
