On Sunday 30 March 2008 18:52, Paul Thompson wrote: > Nigel Henry wrote: > > On Saturday 29 March 2008 20:20, you wrote: > >> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > >> <html> > >> <head> > >> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> > >> <title></title> > >> </head> > >> <body bgcolor="#ffffff" text="#000000"> > >> Nigel Henry wrote: > >> <blockquote cite="mid:200803291809.18227.cave.dnb2m97pp@xxxxxxxxxxxx" > >> type="cite"> > >> <pre wrap="">On Saturday 29 March 2008 15:08, Paul Thompson wrote: > >> </pre> > >> <blockquote type="cite"> > >> <pre wrap="">Greetings > >> > >> Sound has worked fine with my Gateway 9550 notebook using earlier SuSE > >> versions, but the sound doesn't work with 10.3. > >> Yast-Hardware-Sound-Config fails with a Port or IRQ error. However after > >> failing, sound does work, but not after the next boot. > >> > >> Running "alsaconf" also succeeds in getting sound to work properly. > >> Again I have to do it after each boot. Is there any way to make > >> "alsaconf" part of the boot process? Perhaps running "alsaconf" using > >> KDE's Autostart, and specifying a config file? If so, what would the > >> config file look like? > >> > >> Thanks > >> Paul > >> </pre> > >> </blockquote> > >> <pre wrap=""><!----> > >> Hi Paul. While googling for sound related problems on Ubuntu's Gutsy > >> Gibbon, I'm sure I saw quite a few sound problems with 10.3. I dont't > >> use Suse, but would you post the following info please, after rebooting, > >> and before running alsaconf. > >> > >> cat /proc/asound/cards > >> /sbin/lsmod | grep snd > >> > >> Do you have anything plugged into the USB, webcam with mike, usb midi > >> keyboard, etc. These often cause problems resulting in the soundcard not > >> working, as the USB devices are being set as card0, rather than the > >> actual soundcard. > >> > >> You could also download the alsa-info.sh script from: > >> <a class="moz-txt-link-freetext" > >> href="http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh";>http:// > >>hg. alsa-project.org/alsa/raw-file/tip/alsa-info.sh</a> > >> > >> Make it executable, then run it before you run alsaconf, and paste the > >> pastebin link into your reply, marking it "with no sound", or something > >> like that. Then run alsaconf, and run the script again, this time > >> marking the pastebin link as "sound working". > >> > >> This script will provide a lot of info about sound on your machine. > >> > >> All the best. > >> > >> Nigel. > >> > >> > >> > >> ------------------------------------------------------------------------ > >>- Check out the new SourceForge.net Marketplace. > >> It's the best place to buy or sell services for > >> just about anything Open Source. > >> <a class="moz-txt-link-freetext" > >> href="http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/m > >>ark > >> etplace">http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.ne > >>t/ma rketplace</a> _______________________________________________ > >> Alsa-user mailing list > >> <a class="moz-txt-link-abbreviated" > >> href="mailto:Alsa-user@xxxxxxxxxxxxxxxxxxxxx";>Alsa-user@xxxxxxxxxxxxxxxx > >>e.n et</a> <a class="moz-txt-link-freetext" > >> href="https://lists.sourceforge.net/lists/listinfo/alsa-user";>https://li > >>sts .sourceforge.net/lists/listinfo/alsa-user</a> > >> > >> . > >> > >> </pre> > >> </blockquote> > >> Nigel <br> > >> <br> > >> Here are the files. There is nothing plugged into USB or PCMCIA.<br> > >> <br> > >> Thanks<br> > >> Paul<br> > >> <br> > >> </body> > >> </html> > > > > Hi Paul. Would you resend this post to the alsa-user list, but no HTML > > please. > > > > Takashi Iwai (alsa developer) is based at Suse, and is no doubt more > > clued up than me regarding sound problems with 10.3, so the info you sent > > to me may me more helpfull to him if sent to the list. > > > > The first pastebin file "No-sound" shows no alsa driver found. The driver > > is obviously available in the kernel, as alsaconf finds the card, and > > configures it. > > > > That aside, how about trying this after rebooting, and before running > > alsaconf. su to root on the CLI, and do a: > > modprobe snd_maestro3 > > > > I'm sort of clutching at straws, but does cat /proc/asound/cards now show > > your soundcard? Does /sbin/lsmod | grep snd show the same modules loaded > > as when you ran alsaconf after a reboot. See http://pastebin.ca/962404 > > > > If it does, does alsamixer open on the CLI, and more importantly, do you > > have sound? > > > > You may also have to run: > > /usr/sbin/alsactl restore > > > > Post back before I go any further. No HTML please, and CC the alsa-user > > list. > > > > All the best. > > > > Nigel. > > Nigel > > "modprobe snd_maestro3" worked:-) Now to make it part of the boot process. > > I tried using a shell script with SETUID set and called it from KDE > Autostart, but that failed. Perhaps I should put something in > modprobe.conf.local? > > Thanks for your help > Paul Hi Paul. Nice to see that's working. if you've got an /etc/rc.local file, just add the following line to it as root. modprobe snd_maestro3 Post back if you don't have the /etc/rc.local file, and I'll look for other places to set the command. Nigel. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
