On Wed, May 23, 2007 1:17 am, Christoph Maier wrote: > On Tue, 2007-05-22 at 21:16 -0700, William Santiago wrote: >> Carl, Thanks for pointing out my newbie mistake about burning ISO files >> to >> CD, when I followed your instructions, it worked like a charm. >> >> >> Latest Situation: >> >> Installed Ubuntu 6.06 (over older version) via internet connection >> tonight. >> As OS was installing, error messages pertaining to volume control >> crossed my >> screen more than once. No surprise, when I rebooted system, I have no >> sound >> but I might add, I had no sound when I installed prior version of Ubuntu >> either. Please, someone, point me in right direction taking into >> account I >> am very GREEN... >> >> All help greatly appreciated... >> Bill >> >> > Hi Bill, > > I'm also still relatively green, and most of what I know I learned at > recent installfests from the experienced guys (Carl is one of > them ...). > > Anyway, the first thing you'll need to find out is what sound hardware > your Linux distribution thinks you have (and whether it makes the right > assumptions). > > If you are running the GNOME desktop, you'll get an indication if you > run > gnome-sound-properties from a terminal (you can also get it from > System->Preferences->Sound) and look at what the alternatives to > "Autodetect" in the various menus are. > These should be the audio hardware devices that Linux thinks you have. > > That's about as much as I can help at the moment ... > > ... the experts can probably recover the error messages you got from > someplace in /var/log and draw valuable conclusions what, exactly, the > nature of the volume control errors were, and in which direction to look > to fix them. > > Christoph > (wonders which log file would be a good place to look for the messages) >
Usually /var/log/messages. I often zero it with: cat /dev/null>/var/log/messages Have to be root to do that. Also you can use tail on the file to see the latest stuff. tail -f will do a live tail so you can do stuff and see the log messages pop up. A wonderful source of info is dmesg. dmesg | less This gives the latest poop on what the kernel is seeing, similar to the boot up messages. HTH, -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
