-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am not so sure that yast can help you yet. We need to figure out if the correct kernel module has been loaded before we can get anywhere. Everything done at the command line here should not interfere with yast.
what does the output of lsmod |grep snd look like? For me it looks something like this: $ lsmod |grep snd snd_atiixp_modem 16036 0 snd_atiixp 19424 3 snd_ac97_codec 73212 2 snd_atiixp_modem,snd_atiixp snd_pcm_oss 47008 0 snd_mixer_oss 17280 1 snd_pcm_oss snd_pcm 81928 5 snd_atiixp_modem,snd_atiixp,snd_ac97_codec,snd_pcm_oss snd_timer 23428 2 snd_pcm snd 51460 11 snd_atiixp_modem,snd_atiixp,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 9696 1 snd snd_page_alloc 10120 3 snd_atiixp_modem,snd_atiixp,snd_pcm also the output from lspci is useful, look for multimedia audio controller. 0000:00:14.5 Multimedia audio controller: ATI Technologies Inc: Unknown device 4370 (rev 02) If everything looks good so far, check to make sure that the device is not being used or is locked by a program: $ fuser /dev/snd/pcmC0D0* /dev/snd/pcmC0D0p: 8550m 8552m $ ps axf |grep 8550 17659 pts/3 S+ 0:00 | | \_ grep 8550 8550 ? SL 0:45 /usr/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -c drkonqi -l 3 -f $ ps axf |grep 8552 17679 pts/3 S+ 0:00 | | \_ grep 8552 8552 ? Ss 0:00 /usr/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -c drkonqi -l 3 -f Hmmm, it looks like I need to kill artsd (an audio daemon that is not even liked by the original developer). You may see something similar. So, post the output from lsmod |grep snd, lspci and we will go from there. Also what happens when you run alsamixer from the command line? Shawn wrote: > For the sound, try using Yast to tweak settings. SuSe is one of the > distributions that works best when you use their tools, rather than doing > command line edits. You CAN do the command line approach, but you have to > work within the system Suse has set up (i.e. most config settings should be > made in the /etc/sysconfig directory, and once you change this manually, you > should never use Yast again as may overwrite your changes....) > > But, keep in mind the last time I worked with Suse in this manner was with > 9.2, so things could be different now.... > > I'm not sure what to do about the USB problem... Maybe check the output of > dmesg (from the command line), and lsusb - maybe there's something there that > might help... Perhaps the kernel is only recognizing the USB system as > version 1.0? Hopefully you won't need to tweak the kernel... Last time I saw > this done on Suse, it resulted in a kernel panic on boot, and had modified > the environment enough that using the original kernel crapped out as well... > > Hope I at least pointed you in a direction that helps.... > > Shawn > > On Thursday 13 October 2005 19:49, Alex wrote: > >>hey guys.. im having ALOT of problems with suse10... i got now sound any >>more after running >>1) alsaconf >>2) flash has no audio >>3) my usb transfer rate is EXTREAMLY slow >> >>im running gnome and running into soo many problems im really thinking of >>switching distro's if i can't find a solution >> >>any help would be greatly apreciated. >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>clug-talk mailing list >>[email protected] >>http://clug.ca/mailman/listinfo/clug-talk_clug.ca >>Mailing List Guidelines (http://clug.ca/ml_guidelines.php) >>**Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDT+HqwRXgH3rKGfMRArIFAJ9TApsIOZW66wOSrQmVa1kT3+AC1QCdE9Z0 6WGRyxXT29JlDaEBOQdnwvw= =ZVNj -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
