Iulian L Dragomir wrote:
On Sun, Apr 10, 2011 at 8:45 PM, Rob Kampen rkampen@kampensonline.com wrote:
Check the order of driver loading. This affected me a few kernels ago. Found that one needs to force the order of driver loading in modprobe.conf HTH
The modprobe.conf is looking like this:
alias eth0 e1000e alias scsi_hostadapter ata_piix alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel alias wlan0 iwl3945
=======================
The same configuration is used for both old (functional) and new (nonfunctional) kernels
What are your suggestions regarding the order of drivers loading ?
I found that there was another module loading before the snd-hda-intel thus I added index=0 to the one I needed and index=1 to the other module that seemed to get in the way. the clue was looking under System>Administration>Sound Card Detection and seeing the Audio configuration dialog > Settings tab - it showed my desired sound card as number 1 rather than 0 with another item as number 0 (one I did not even know was on the computer). Took me a recompiled kernel and hours of wasted time. Old kernels all worked fine - thus I thought it was a kernel patch problem - removed all the related patches and still no joy. I do not know what they are doing to the kernel but over time the loading of modules, order of disk detection etc is becoming much more of an issue. HTH YMMV
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos