FS#15251 - Problem with module-init-tools

Attached to Project: Arch Linux
Opened by André Fettouhi (A.Fettouhi) - Wednesday, 24 June 2009, 18:06 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 24 June 2009, 20:45 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Since the update of module-init-tools a few days ago I'm having issues with alsa. Now when I boot alsa fails and complains about not being able to detect my sound card and also I'm getting warnings from framebuffer_blacklist.conf. In order to get my sound working on my machine, which uses the snd-hda-intel module,

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller

I added the following line to modprobe.conf

options snd-hda-intel probe_mask=1

and I am using modprobe.conf in /etc/modprobe.d/ as mentioned in the news section. Now comes the strange thing, my sound works actually fine but I don't understand why alsa fails then??? There is more output at boot but I don't know how to save it, help please?

Additional info:
* package version(s)
* config and/or log files etc.

module-init-tools-3.8-1

Steps to reproduce:

Unknown
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 24 June 2009, 20:45 GMT
Reason for closing:  Not a bug
Comment by Greg (dolby) - Wednesday, 24 June 2009, 18:20 GMT
Did you move /etc/modprobe.d/sound to /etc/modprobe.d/sound.conf?
Also it might be useful to remove that file completely and generate a new one with alsamixer.
Mine changed its filename that way to /etc/modprobe.d/50-sound.conf
Comment by Greg (dolby) - Wednesday, 24 June 2009, 18:21 GMT
s/alsamixer/alsaconf
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 24 June 2009, 18:37 GMT
sound.conf??? I just placed the

options snd-hda-intel probe_mask=1

in the modprobe.conf like it was before the update except that modprobe.conf was placed in /etc/. I have never used a sound or sound.conf file before with machine and installation.
Comment by Roman Kyrylych (Romashka) - Wednesday, 24 June 2009, 19:41 GMT
@ André: I had warnings from ALSA too, the solution is to just run 'alsactl store'. Please confirm if this eliminates warnings.
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 24 June 2009, 20:13 GMT
OK, alsa runs now at boot after I ran alsaconf. It generated the 50-sound.conf and now alsa starts correctly. The other warnings I got were when the modules were loaded. I got a bunch of warnings from framebuffer_blacklist.conf.pacsave saying it will be ignored in a future release because it doesn't have the.conf suffix. I removed it simply and now those warnings are gone :D. Many thanks!!!

Regards

André

PS. Where in Arch Linux is the boot info stored when Arch boots and loads the different modules? Would be great to know because I run SPLASHY.

Loading...