snd-hda-intel does not work before reloading

Bug #199591 reported by Erik Bakker
2
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have a hardy installation on a Dell XPS M1330

The sound does not work after booting, but only starts working after a '/sbin/alsa reload' which unloads modules and reloads exacly the same modules again:

root@link:/home/eamelink# /sbin/alsa reload
Unloading ALSA sound driver modules: snd-hda-intel snd-hwdep snd-pcm-oss snd-pcm snd-page-alloc snd-mixer-oss snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device (failed: modules still loaded: snd-hda-intel snd-hwdep snd-pcm snd-page-alloc snd-timer).
Loading ALSA sound driver modules: snd-hda-intel snd-hwdep snd-pcm-oss snd-pcm snd-page-alloc snd-mixer-oss snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device.

After this, the sound works fine. Before this, there is no sound whatsoever, but also no errormessages. I can see the right channels in a mixer, but there is just no sound output. Dmesg gives nothing grepping on snd.

Tags: hardy
Revision history for this message
Erik Bakker (eamelink) wrote :

This problem has been solved by adding

options snd_hda_intel model=auto

to /etc/modprobe.d/alsa-base

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.