Curtis Rey wrote:
Ok, I'm not sure how this happened but I think that when I tried to install the SBLive drivers form the creative opensource site may modules.conf went bye bye.
Now I did a cloneconf and make dep, then make modules and the mod install. Then mk_initrd and lilo. When I run lsmod It actually shows the right mods now. This happened this morning when I first booted my sys. The nvidia kernel drivers wouldn't load. I solved this, after figuring out that they actually worked correctly, by the line /sbin/modprobe -k NVdriver in the init.d/boot.local file.
What follows is all that's left of my mod conf file (and this includes the backups).
# --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF verion 0.5.10 --- alias char-major-116 snd alias snd-card-0 snd-card-emu10k1 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_cards_limit=1 snd_major=116 options snd-card-emu10k1 snd_index=0 # --- END: Generated by ALSACONF, do not edit. ---
# # YaST2: Network card # alias eth0 ne2k-pci
So, my question is this. A) how do a generate a new and "complete" modules.conf file?
Reinstall the aaa-base package. I know of no method of generating one. This file comes packed full and only gets modified by YAST/YAST2. You'll probably have to redo some configuring after you get the new one installed.
And less important - how does this happen??
The creative stuff must have barfed in the middle of changing this file. Or they have a broken install script. -- Mark Hounschell dmarkh@cfl.rr.com