Alsa Issues [SOLVED]

NobodyCares · n00b Joined: 04 Jun 2007 Posts: 11

I am relatively new to Linux, and just recently I installed Gentoo with Gnome as my WM. I am almost positive that everything went well with my Gentoo install, but I forgot to compile Alsa support into the kernel. I tried to use alsa-drivers, to no avail. I followed the alsa guide here and everything went well until I tried to use alsaconfig, which spit out this error message:

Running modules-update...
* Updating /etc/modules.conf ... [ ok ]
* Updating /etc/modprobe.conf ... [ ok ]
* Updating modules.dep ...
FATAL: Could not open '/System.map': No such file or directory [ !! ]
Loading driver...
* Loading ALSA modules ...
* Loading: snd-card-0 ... [ ok ]
* Loading: snd-seq ... [ ok ]
* ERROR: Failed to load necessary drivers [ ok ]
* Restoring Mixer Levels ...
alsactl: unrecognized option `---'
Usage: alsactl <options> command

Available options:
-h,--help this help
-f,--file # configuration file (default /etc/asound.state or /etc/asound.names)
-F,--force try to restore the matching controls as much as possible
-d,--debug debug mode
-v,--version print version of this program

Available commands:
store <card #> save current driver setup for one or each soundcards
to configuration file
restore<card #> load current driver setup for one or each soundcards
from configuration file
* Errors while restoring defaults, ignoring [ ok ]
Setting default volumes...
amixer: Mixer attach default error: No such device
Saving the mixer setup used for this in /etc/asound.state.
/usr/sbin/alsactl: save_state:1253: No soundcards found...

I'm not sure exactly what I need to do here, as alsamixer won't even run. Any tips? I tried to recompile my kernel with alsa support, but I can't find my grub.conf file either, and slocate isn't turning up anything but the example. My kernel loads fine, but grub seems to have moved all its configuration files into the ether...

sugar · Posted: Tue Jun 05, 2007 3:01 am Post subject:

If you followed the usual install, you can mount your boot partition by

mbreith · Apprentice Joined: 09 Mar 2006 Posts: 196

NobodyCares · n00b Joined: 04 Jun 2007 Posts: 11

I tried to manually place the kernel into /boot, but it said that there wasn't enough space. I'm trying to find a way to have GRUB boot the kernel from the root file, but I am having a little trouble understanding exactly how the GRUB notation for each partition works. Right now, I have my old kernel at:
/boot/kernel-NCGentoo

and the new kernel is:

/root/kernels/kernel-NCGentoo2

I'm not sure how to tell GRUB to go to /root rather than /boot. I understand boot is (hd0,0) but wouldn't that make swap (hd2,0) or (hd0,2) and /root (hd3,0) or (hd0,3)?

I ran depmod as root with no problem, so I suppose that is one thing I don't have to worry about.

Update: I was making a stupid mistake with GRUB syntax, which was counting my partitions from 1, not 0. I got GRUB to find the new kernel no problem by telling it to look at:
(hd0,2)/kernels/kernel-NCGentoo2

I am currently booted into my new kernel, and it would appear that my sound is working fine!

mbreith · Apprentice Joined: 09 Mar 2006 Posts: 196

See, people here care

What is the size of your /boot?

Having the kernel sitting somewhere else will work just fine, as you found out, but will cause problems when updating things. Basically you will always have to manually update grub. You will likely also have to manually run depmod any time you add new modules.

Thanks for adding [solved]

_________________
I don't stat chatspeak acronyms.