Remember vaguely that it was discussed on the list but was unable to find it back. Googled and also no usable results. I changed recently from 9.3 to 10.0 and I am really pleased with the speed of 10.0 The only main problem which remains after making 10.0 my default program is that Skype does not work anymore. This happened also sometimes with 9.3 but a rerunning of the Skype was in most cases enough to get a connection. In 10.0 the message is without change "problem with sound device". Has somebody a workaround? Read in Google that the problem is mainly Skype (not open source ;) ) which seems to use Open Sound System. I use Alsamixergui (only because I like that GUI) and and in the Control Center I have it set the select audio device to Selfdetect. I have tried to set it to OSS and to Treaded OSS (whatever that is) to no avail. Any help is more than welcome.
rerunning of the Skype was in most cases enough to get a connection. In 10.0 the message is without change "problem with sound device". Has somebody a workaround?
You're not the only one with that problem in 10.0. I've struggled to find a solution. The Skype developers/customer support is zero for the Linux version. They've stopped all work on the Linux version as of what... 1.2.x... and the Windows version is 2.something now with all sorts of nice features. :-( Anyway, I did find a way to "work around" the problem... I bought a Logitech USB headset, and set it as the default device for Skype. A couple notable changes... the sound quality improved 1000x, and I don't get the "problem with sound device" error anymore. So, I am not running Skype through my Soundblaster of my AC/97 onboard sound cards anymore... the USB headset (which works in SUSE10.0 by simply plugging it in... no configuration needed) seems to have solved whatever problem Skype was having with using the sound cards. Not a software solution... but... it worked for me to change my way of using Skype. C.
On Wednesday 10 May 2006 10:13, Clayton wrote:
Not a software solution... but... it worked for me to change my way of using Skype.
Hi Clayton, Care to share a model number, since the one you bought is known to work? I haven't had the problems that you two have experienced, but I've switched to wireless headphones (no mic) and my desktop mic is broken. I gave my wired headset (with mic) to my daughter but it worked flawlessly with Skype on this system. If I can, I'd like to avoid rearranging plugs every time I use Skype. Thanks & regards, Carl Also, Constant, you wrote:
In 10.0 the message is without change "problem with sound device".
As a quick test, move your ~/.Skype directory to .oldskype and see if the "fresh" install clears this up. It could be the 9.3 sound configuration isn't compatible with 10.0 Carl
On Wednesday 10 May 2006 21:29, Carl Hartung wrote:
On Wednesday 10 May 2006 10:13, Clayton wrote:
Not a software solution... but... it worked for me to change my way of using Skype.
Hi Clayton,
Care to share a model number, since the one you bought is known to work? I haven't had the problems that you two have experienced, but I've switched to wireless headphones (no mic) and my desktop mic is broken. I gave my wired headset (with mic) to my daughter but it worked flawlessly with Skype on this system. If I can, I'd like to avoid rearranging plugs every time I use Skype.
Thanks & regards,
Carl
Also, Constant, you wrote:
In 10.0 the message is without change "problem with sound device".
As a quick test, move your ~/.Skype directory to .oldskype and see if the "fresh" install clears this up. It could be the 9.3 sound configuration isn't compatible with 10.0
Dear Carl, Will do a reinstall. Started in the meantime Skype in console and got the info ioctl set fragment: Invalid argument /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy After the first line ioctl set fragment the following lines are repeated for every try to connect. Can you do something with this info?
On Wednesday 10 May 2006 10:48, Constant Brouerius van Nidek wrote:
Dear Carl, Will do a reinstall. Started in the meantime Skype in console and got the info
ioctl set fragment: Invalid argument /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy
After the first line ioctl set fragment the following lines are repeated for every try to connect. Can you do something with this info?
This is just telling you Skype can't connect to /dev/dsp-1 Have you been here: http://forum.skype.com/viewforum.php?f=18 Carl
Addendum: This is an excellent resource if you have to tweak/debug Skype: Unofficial Skype + Linux Sound FAQ: http://forum.skype.com/viewtopic.php?t=4489 Carl
On Wednesday 10 May 2006 15:48, Constant Brouerius van Nidek wrote:
On Wednesday 10 May 2006 21:29, Carl Hartung wrote:
On Wednesday 10 May 2006 10:13, Clayton wrote:
Not a software solution... but... it worked for me to change my way of using Skype.
Hi Clayton,
Care to share a model number, since the one you bought is known to work? I haven't had the problems that you two have experienced, but I've switched to wireless headphones (no mic) and my desktop mic is broken. I gave my wired headset (with mic) to my daughter but it worked flawlessly with Skype on this system. If I can, I'd like to avoid rearranging plugs every time I use Skype.
Thanks & regards,
Carl
Also, Constant, you wrote:
In 10.0 the message is without change "problem with sound device".
As a quick test, move your ~/.Skype directory to .oldskype and see if the "fresh" install clears this up. It could be the 9.3 sound configuration isn't compatible with 10.0
Dear Carl, Will do a reinstall. Started in the meantime Skype in console and got the info
ioctl set fragment: Invalid argument /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy /dev/dsp-1: Device or resource busy
After the first line ioctl set fragment the following lines are repeated for every try to connect. Can you do something with this info?
May be you have a lot o9f a typo there /dev/dsp-1 thats should be /dev/dsp1 .. Having checked on three systems 9.2 10.0 32bit 10.0 64bit .. All /dev/dsp try correcting the typo i have no problems at all with Skype on all 3 systems also a laptop with AMD turion 64 running suse 10.1 beta something 32bit .. All work perfectly with speakers and microphone the only time i get any problems is from cable systems (DSL) as opposed to my BT (ADSL) system ADSL to ADSL is fine . Pete . -- The Labour party has changed their emblem from a rose to a condom as it more accurately reflects the government's political stance. A condom allows for inflation, halts production, destroys the next generation, protects a bunch of pricks, and gives you a sense of security while you are actually being fucked. from GSM
On Wednesday 10 May 2006 15:56, Peter Nikolic wrote:
May be you have a lot o9f a typo there /dev/dsp-1 thats should be /dev/dsp1 ..
Nice catch, Peter! I don't know if that setting is entered manually or selected from a drop-down list... we'll have to wait for Constant to check in, I guess. Carl
On Thursday 11 May 2006 04:06, Carl Hartung wrote:
On Wednesday 10 May 2006 15:56, Peter Nikolic wrote:
May be you have a lot o9f a typo there /dev/dsp-1 thats should be /dev/dsp1 ..
Nice catch, Peter!
I don't know if that setting is entered manually or selected from a drop-down list... we'll have to wait for Constant to check in, I guess.
Could be the solution. Must be a bug because I did not do any manual "labor" and to be honest, I cannot remember to have chosen anything at a drop-down list. Still do not exactly know what dsp means ;). And the result as shown in my last post was copied as is from a console. Where do I start changing dsp-1 into dsp1?
On Thursday 11 May 2006 07:33, Constant Brouerius van Nidek wrote:
Could be the solution. Must be a bug because I did not do any manual "labor" and to be honest, I cannot remember to have chosen anything at a drop-down list. Still do not exactly know what dsp means ;). And the result as shown in my last post was copied as is from a console.
Where do I start changing dsp-1 into dsp1?
Constant, Did you visit the Skype on Linux forum /and/ the Unofficial Skype/Sound on Linux link I posted yesterday? Carl
On Thursday 11 May 2006 18:42, Carl Hartung wrote:
On Thursday 11 May 2006 07:33, Constant Brouerius van Nidek wrote:
Could be the solution. Must be a bug because I did not do any manual "labor" and to be honest, I cannot remember to have chosen anything at a drop-down list. Still do not exactly know what dsp means ;). And the result as shown in my last post was copied as is from a console.
Where do I start changing dsp-1 into dsp1?
Constant,
Did you visit the Skype on Linux forum /and/ the Unofficial Skype/Sound on Linux link I posted yesterday?
Dear Carl, Not yet. Just had my dinner and are now at my computer to start the night (19.00 hr local time). The sites are on top of my list for today. Have the feeling that my soundcard setup is somewhere broken. In Yast I see two soundcards (only one on board) from what I can remember are using the same driver. The installed card in Yast is the "Ensoniq Audio PCI" and the not installed is the "Creative Sound Blaster Audio PCI128" . Cannot remember what the card itself says and I am to lazy for now (dinner you know) to open up my box ;). The strange thing is that the Ensoniq setup informs me that the card is "Configured as sound card number " with the "Driver snd-ens1371" Deleting the card does not do anything and trying to install the creative card is trying fruitless to use the same snd-ens1371 driver. How to fresh install the soundcard?
On Thursday 11 May 2006 04:06, Carl Hartung wrote:
On Wednesday 10 May 2006 15:56, Peter Nikolic wrote:
May be you have a lot o9f a typo there /dev/dsp-1 thats should be /dev/dsp1 ..
Nice catch, Peter!
I don't know if that setting is entered manually or selected from a drop-down list... we'll have to wait for Constant to check in, I guess.
Could be the solution. Must be a bug because I did not do any manual "labor" and to be honest, I cannot remember to have chosen anything at a drop-down list. Still do not exactly know what dsp means ;). And the result as shown in my last post was copied as is from a console.
Where do I start changing dsp-1 into dsp1? Just to add some more info for completness sake. I read somewhere that downgrading Skype could/should do the job. I even found a download site for
On Thursday 11 May 2006 18:33, Constant Brouerius van Nidek wrote: the 1.1xx version but that did not help either. A new install from the latest version is also not (yet) functioning.
On Thursday 11 May 2006 07:45, Constant Brouerius van Nidek wrote: <snipped> Constant, You will be wasting time if you install or configure Skype while your sound system configuration is broken. YaST showing two cards where there is only one on-board sound chip is a dead giveaway... you need to clear this problem up before trying to configure software. First things first! Carl
On Thursday 11 May 2006 19:32, Carl Hartung wrote:
On Thursday 11 May 2006 07:45, Constant Brouerius van Nidek wrote: <snipped>
Constant,
You will be wasting time if you install or configure Skype while your sound system configuration is broken. YaST showing two cards where there is only one on-board sound chip is a dead giveaway... you need to clear this problem up before trying to configure software.
First things first!
Carl, Your so right ;). That my sound setup was somewhere not right is something I never knew before. It works for those things that I am working with so why look at the setup. I now want to clean the setup but via Yast it is a no go. I can not delete any card (it just ignores the command). So I now want to go console and do some deleting. But what? I have no idea.
On Thursday 11 May 2006 20:40, Carl Hartung wrote:
On Thursday 11 May 2006 09:04, Constant Brouerius van Nidek wrote:
... But what? I have no idea.
First, try deleting the file /etc/modprobe.d/sound and running YaST to configure your sound chip/card again.
Done and now to the Skype pages for the finetuning. Will report. But running Skype in the console I still get /dev/dsp-1
On Thursday 11 May 2006 10:33, Constant Brouerius van Nidek wrote:
Done and now to the Skype pages for the finetuning. Will report. But running Skype in the console I still get /dev/dsp-1
Did the card seem to be configured correctly? Are your sounds working as you expect them to? Is YaST showing only one 'card' installed and is it the correct one? Have you moved ~/.Skype to ~/.oldskype and launched Skype again? Carl
On Thursday 11 May 2006 21:42, Carl Hartung wrote:
On Thursday 11 May 2006 10:33, Constant Brouerius van Nidek wrote:
Done and now to the Skype pages for the finetuning. Will report. But running Skype in the console I still get /dev/dsp-1
Did the card seem to be configured correctly? Are your sounds working as you expect them to? Is YaST showing only one 'card' installed and is it the correct one? Have you moved ~/.Skype to ~/.oldskype and launched Skype again?
Carl, The card was configured correctly. My sounds are working as expected. The card is correctlt shown in Yast. I have moved the old /.skype to a temp direvtory. Seemed a better solution as renaming them. I have deleted in Yast Skype and installed a fresh, new Skype again. Ran Skype in console and get the same info as before. Still /dev/dsp-1 Think it is now the time to symlink dsp-1 to dsp. Could you give me the command line for that. Can do it in midnight commander but never seem to be able to get it right there.
On Thursday 11 May 2006 11:57, Constant Brouerius van Nidek wrote:
The card was configured correctly. My sounds are working as expected. The card is correctlt shown in Yast. I have moved the old /.skype to a temp direvtory. Seemed a better solution as renaming them. I have deleted in Yast Skype and installed a fresh, new Skype again. Ran Skype in console and get the same info as before. Still /dev/dsp-1 Think it is now the time to symlink dsp-1 to dsp. Could you give me the command line for that. Can do it in midnight commander but never seem to be able to get it right there.
I'll bet the anomalous /dev/dsp-1 is a leftover, non-working device created by a YaST script when it was 'configuring' the second, "phantom" card. Try this as normal user, please, before attempting to create a link: cd /dev l ds* (that's a lowercase L, for list) If you find that /dev/dsp *and* /dev/dsp-1 exist, open Skype and, somewhere under 'Tools' > 'Options' is a drop-down list for selecting the correct (working) Digital Signal Processing device (DSP)... I only have one and it's called "/dev/dsp" like everybody else. That's all I see in the drop-down list. If, however, both exist under /dev, the correct one (/dev/dsp) should be available in the drop-down list and you can just select it. If, on the other hand, you do the 'l ds*' and see *only* /dev/dsp-1 I'd say you haven't really fixed the underlying problem... you might want to think about discovering why the standard /dev/dsp has not been created. If there is only a /dev/dsp-1 and you don't want to chase down why, then 'su -' to root while in /dev and do 'ln -s dsp-1 dsp' That's it. Please let me know what you find... I am very curious now. Good luck! Carl
On Thursday 11 May 2006 23:47, Carl Hartung wrote:
On Thursday 11 May 2006 11:57, Constant Brouerius van Nidek wrote:
The card was configured correctly. My sounds are working as expected. The card is correctlt shown in Yast. I have moved the old /.skype to a temp direvtory. Seemed a better solution as renaming them. I have deleted in Yast Skype and installed a fresh, new Skype again. Ran Skype in console and get the same info as before. Still /dev/dsp-1 Think it is now the time to symlink dsp-1 to dsp. Could you give me the command line for that. Can do it in midnight commander but never seem to be able to get it right there.
I'll bet the anomalous /dev/dsp-1 is a leftover, non-working device created by a YaST script when it was 'configuring' the second, "phantom" card. Try this as normal user, please, before attempting to create a link:
cd /dev l ds* (that's a lowercase L, for list)
If you find that /dev/dsp *and* /dev/dsp-1 exist, open Skype and, somewhere under 'Tools' > 'Options' is a drop-down list for selecting the correct (working) Digital Signal Processing device (DSP)... I only have one and it's called "/dev/dsp" like everybody else. That's all I see in the drop-down list. If, however, both exist under /dev, the correct one (/dev/dsp) should be available in the drop-down list and you can just select it.
If, on the other hand, you do the 'l ds*' and see *only* /dev/dsp-1 I'd say you haven't really fixed the underlying problem... you might want to think about discovering why the standard /dev/dsp has not been created.
If there is only a /dev/dsp-1 and you don't want to chase down why, then 'su -' to root while in /dev and do 'ln -s dsp-1 dsp'
That's it. Please let me know what you find... I am very curious now.
Good luck!
Well, here is the result of l ds* gives following :/dev> l ds* crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1 No dsp-1 so I really do not know where that comes from. The Skype instalation is total fresh after deleting in Yast from the the last install and the soundcard is newly configured. Just found out that my email notification is not working ;(. In console the skype command is calling the local skype setup so I assume dsp-1 must be found somewhere there. Or could that be hiding somewhere in the etc local config?
On Thursday 11 May 2006 13:16, Constant Brouerius van Nidek wrote:
Well, here is the result of l ds* gives following
:/dev> l ds*
crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1
No dsp-1 so I really do not know where that comes from.
OK, I've done a little searching on Google and I'm starting to believe that 'dsp-1' is actually a label used by Skype to point to the first /dev/ds* in the list of available/prospective devices it populates during setup (i.e. dsp-1 is Skype's internal label for the first ds* it finds under /dev) Here's what mine looks like: crw-rw----+ 1 carl audio 14, 3 2006-05-06 20:11 dsp You haven't said whether or not you've looked under 'Tools' > 'Options' in Skype to try changing the selected device. Have you done that? What devices do you see listed there? Carl
On Friday 12 May 2006 01:05, Carl Hartung wrote:
On Thursday 11 May 2006 13:16, Constant Brouerius van Nidek wrote:
Well, here is the result of l ds* gives following
:/dev> l ds*
crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1
No dsp-1 so I really do not know where that comes from.
OK, I've done a little searching on Google and I'm starting to believe that 'dsp-1' is actually a label used by Skype to point to the first /dev/ds* in the list of available/prospective devices it populates during setup (i.e. dsp-1 is Skype's internal label for the first ds* it finds under /dev)
Here's what mine looks like: crw-rw----+ 1 carl audio 14, 3 2006-05-06 20:11 dsp
You haven't said whether or not you've looked under 'Tools' > 'Options' in Skype to try changing the selected device. Have you done that? What devices do you see listed there?
I did look there and changed the setting from /dev/dsp to /dev/dsp1 and back. After running in console I found that Skype uses /dev/dsp-1 for what shows inunder the tools as /dev/dsp and it uses /dev/dsp1 for /dev/dsp1 Go figure. Whatever I choose, the information is still the same. Problem with sound device. I can of course always go back to the functioning 9.3 but I think that would not be the Suse way ;). By the way after a reboot I got my email notification back, still in a shortened form.
On Thursday 11 May 2006 14:43, Constant Brouerius van Nidek wrote:
I did look there and changed the setting from /dev/dsp to /dev/dsp1 and back. After running in console I found that Skype uses /dev/dsp-1 for what shows inunder the tools as /dev/dsp and it uses /dev/dsp1 for /dev/dsp1 Go figure. Whatever I choose, the information is still the same. Problem with sound device.
I have to run out for a bit. Can you, in the interim, head over to the Skype forum links that I provided and do some reading and testing? It seems from a trend in the Google hits I'm seeing that a change in SUSE between 9.2/9.3 and 10.0 broke Skype on many people's systems. The problem seems to be at least partly hardware-driven in that the hardware you've got determines which modules are loaded automatically and this, in turn, seems to affect which approach works. The "solutions" are all over the board, too... I'll look at this more after I get back this evening. If you can keep some basic notes as you're exploring and trying things out, I'd like to know what you've found. cu Carl
On Thursday 11 May 2006 14:43, Constant Brouerius van Nidek wrote:
Well, here is the result of l ds* gives following crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1
Hi Constant, I have an idea... I'd like to see if we can't convince your system to configure and behave more like mine and other people's that only have one /dev/dsp (you *did* say you're running on-board only, no separate sound card, right?) Please try the following: * uninstall your sound chip/card with YaST * log out of KDE (close session only) * Ctl+Alt+F1 at the greeter to switch to tty1 console * log in as root * drop to run level 3 ('init 3' to shut down KDE and X) * delete the file /etc/modprobe.d/sound again * delete /dev/dsp1 and /dev/dsp * run the following commands: rpm -e kdemultimedia3-mixer (removes the mixer, can be reinstalled) ldconfig init 5 && exit * log into KDE * open a shell, 'su -' to root * run the following commands: rcalsasound stop rm /etc/asound.state rcalsasound start alsactl store then run: alsaconf -L /home/cbvn/Documents/alsaconf.log * configure your sound card * exit from root and from the shell alsaconf will log your sound card configuration session while using alsaconf, which is what you're trying this time instead of YaST. What you want to see is a plain vanilla /dev/dsp with permissions matching mine (posted previously.) If this procedure cleans up that anomaly, I'd be inclined to remove every trace of Skype, download the latest rpm and install it again from scratch before testing it. Good luck! Carl
On Friday 12 May 2006 05:36, Carl Hartung wrote:
On Thursday 11 May 2006 14:43, Constant Brouerius van Nidek wrote:
Well, here is the result of l ds* gives following crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1
Hi Constant,
I have an idea... I'd like to see if we can't convince your system to configure and behave more like mine and other people's that only have one /dev/dsp (you *did* say you're running on-board only, no separate sound card, right?)
Please try the following:
What you want to see is a plain vanilla /dev/dsp with permissions matching mine (posted previously.) If this procedure cleans up that anomaly, I'd be inclined to remove every trace of Skype, download the latest rpm and install it again from scratch before testing it.
Good luck!
Carl, Back again and in the startblocks for a new attack on my system. Did exactly as you proposed to do and end up with the usual info. The content from the alsa configuration is as follows: Starting alsaconf: Fri May 12 21:35:00 WIT 2006 sb16 isapnp=0 sb8 dma8=1 irq=5 sb8 dma8=3 irq=5 Starting alsaconf: Fri May 12 21:36:05 WIT 2006 Again /dev/dsp and dsp1. In order to uninstall the sound card I had to remove it. In my Yast deleting of a card does not work. A fresh install of Skype after rpm -e skype and removing ny trace of skype from my home directory was done with the latest download. No result. Really wonder after reading trough a lot of the reactions on the Skype list if it is not time to just get another voip product. That is for the moment something which is widely discussed on the Skype list. I am close to giving up. Any experience with others such as Openwengo, Ekiga,Twinkle, SIPphone and Gizmo?
On Friday 12 May 2006 13:21, Constant Brouerius van Nidek wrote:
Carl, Back again and in the startblocks for a new attack on my system. Did exactly as you proposed to do and end up with the usual info.
The content from the alsa configuration is as follows: Starting alsaconf: Fri May 12 21:35:00 WIT 2006 sb16 isapnp=0 sb8 dma8=1 irq=5 sb8 dma8=3 irq=5 Starting alsaconf: Fri May 12 21:36:05 WIT 2006
Again /dev/dsp and dsp1.
Constant, Did I screw up and confuse your system with another system I'm 'troubleshooting'? I don't recall picking up on a second sound card/chip. If the motherboard has built-in sound that isn't disabled in the BIOS, the installer will pick up both digital signal processors and generate a dsp and dsp1 :-/ Are you using the on-board sound? Can you send me a .pdf of the mainboard manual... or a link? Carl
On Saturday 13 May 2006 01:34, Carl Hartung wrote:
On Friday 12 May 2006 13:21, Constant Brouerius van Nidek wrote:
Carl, Back again and in the startblocks for a new attack on my system. Did exactly as you proposed to do and end up with the usual info.
The content from the alsa configuration is as follows: Starting alsaconf: Fri May 12 21:35:00 WIT 2006 sb16 isapnp=0 sb8 dma8=1 irq=5 sb8 dma8=3 irq=5 Starting alsaconf: Fri May 12 21:36:05 WIT 2006
Again /dev/dsp and dsp1.
Constant,
Did I screw up and confuse your system with another system I'm 'troubleshooting'? I don't recall picking up on a second sound card/chip. If the motherboard has built-in sound that isn't disabled in the BIOS, the installer will pick up both digital signal processors and generate a dsp and dsp1 :-/
Are you using the on-board sound?
Can you send me a .pdf of the mainboard manual... or a link?
Dear Carl, No screw up on your side. I have a soundcardles board and a PCI sound card. It was not possible to delete the card(s) that where found on the system so I took the sound card out and got a fresh possibility to setup my card. Did it with alsa as you proposed after rm several files. and stopping starting rcalsasound etc. Was a good idea but it did not help any. Think that I return to my full functioning but slower 9.3 where by the way I have dsp dsp1 dsp2 and dsp3 Do not ask me why. They are just there ;) Think I wait for 10.1 or 10.3. Thanks for the help. Was a plesure.
On Saturday 13 May 2006 10:44, Constant Brouerius van Nidek wrote:
No screw up on your side. I have a soundcardles board and a PCI sound card.
What's your mainboard make/model?
It was not possible to delete the card(s) that where found on the system so I took the sound card out and got a fresh possibility to setup my card. Did it with alsa as you proposed after rm several files. and stopping starting rcalsasound etc. Was a good idea but it did not help any.
Did YaST ID the card correctly? My notes show: Creative Sound Blaster Audio PCI128 Is this the correct model number? Do you have a revision number?
Think that I return to my full functioning but slower 9.3 where by the way I have dsp dsp1 dsp2 and dsp3 Do not ask me why. They are just there ;)
I'm beginning to think in 10.0 dsp is trying to act as 'record' and 'play' for left channel and dsp1 for the right channel when it should be dsp is 'record' for both left and right with dsp1 as 'play' for left and right. Confused yet? ;-) As you've described, above, in your working 9.3 setup the card's functional input/output pairs are being represented by four discreet /dev/ds* entries. I don't know the age of this card, but we might need to review the drivers/parameters in more detail. That's why I'm hoping you can verify the card model *and* revision number for me.
Think I wait for 10.1 or 10.3.
If you can run 9.3 while keeping 10.0 installed to debug it, that would be the ideal scenario. Also, I think finding and fixing (or working around) the problem in 10.0 will carry over into 10.1, meaning it should make 'tweaking' Skype to work in 10.1 easier. Carl
On Saturday 13 May 2006 23:24, Carl Hartung wrote:
On Saturday 13 May 2006 10:44, Constant Brouerius van Nidek wrote:
No screw up on your side. I have a soundcardles board and a PCI sound card.
What's your mainboard make/model?
It was not possible to delete the card(s) that where found on the system so I took the sound card out and got a fresh possibility to setup my card. Did it with alsa as you proposed after rm several files. and stopping starting rcalsasound etc. Was a good idea but it did not help any.
Did YaST ID the card correctly? My notes show: Creative Sound Blaster Audio PCI128 Is this the correct model number? Do you have a revision number?
Think that I return to my full functioning but slower 9.3 where by the way I have dsp dsp1 dsp2 and dsp3 Do not ask me why. They are just there ;)
I'm beginning to think in 10.0 dsp is trying to act as 'record' and 'play' for left channel and dsp1 for the right channel when it should be dsp is 'record' for both left and right with dsp1 as 'play' for left and right. Confused yet? ;-)
As you've described, above, in your working 9.3 setup the card's functional input/output pairs are being represented by four discreet /dev/ds* entries.
I don't know the age of this card, but we might need to review the drivers/parameters in more detail. That's why I'm hoping you can verify the card model *and* revision number for me.
Think I wait for 10.1 or 10.3.
If you can run 9.3 while keeping 10.0 installed to debug it, that would be the ideal scenario. Also, I think finding and fixing (or working around) the problem in 10.0 will carry over into 10.1, meaning it should make 'tweaking' Skype to work in 10.1 easier.
You are right.That was the whole idea of having 10.0 on the other half of my hard disk. As I said, in my 9.3 setup I had 4 dsp from 0 to 3. Thought it may be not as invented and after my first information with Skype was the "problem with sound" I have redone my sound system as you proposed for the 10.0. Yast 9.3 let me delete the sound card (10.0 did not do that- could you check if you could delete the sound card with Yast in 10.0?) and the rest was just a walkover. I have now just one dsp but for the moment no email notification. Not such a problem. Everything else at the sound side works in 9.3. During daylight, tomorrow I will open up my box and have a look at the card in order to find the version number. But after the fine reinstall of the sound card I wonder whether a reinstall of the Yast modules could bring improvement. Will keep you informed.
On Thursday 11 May 2006 18:16, Constant Brouerius van Nidek wrote:
On Thursday 11 May 2006 23:47, Carl Hartung wrote
Well, here is the result of l ds* gives following
:/dev> l ds*
crw-rw-rw- 1 cbvn audio 14, 3 2006-05-11 21:02 dsp crw------- 1 cbvn audio 14, 19 2006-05-11 21:02 dsp1
No dsp-1 so I really do not know where that comes from. The Skype instalation is total fresh after deleting in Yast from the the last install and the soundcard is newly configured. Just found out that my email notification is not working ;(. In console the skype command is calling the local skype setup so I assume dsp-1 must be found somewhere there. Or could that be hiding somewhere in the etc local config?
I have just looked in the latest version of Skype whic is the one i run on all my machines and can see no trace of "/dev/dsp-1" at all there has got to be some corruption creaping in from some old config somewhere that is causing all this . This could be a bumpy ride trying to find it ..check in "/root/.Skype/yourusername" make sure it is not in there somewhere HTH Pete . -- The Labour party has changed their emblem from a rose to a condom as it more accurately reflects the government's political stance. A condom allows for inflation, halts production, destroys the next generation, protects a bunch of pricks, and gives you a sense of security while you are actually being fucked. from GSM
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-05-11 at 18:33 +0700, Constant Brouerius van Nidek wrote:
Where do I start changing dsp-1 into dsp1?
At worst, symlink it. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEYyQCtTMYHG2NR9URAgw4AJ0f9sKu/ck+BIiLngXPCqobi3c2oQCfVBW6 ZZ56I2SMv1XLjGgmYm5dB50= =2Iqf -----END PGP SIGNATURE-----
On Thursday 11 May 2006 12:33, Constant Brouerius van Nidek wrote:
On Thursday 11 May 2006 04:06, Carl Hartung wrote:
On Wednesday 10 May 2006 15:56, Peter Nikolic wrote:
May be you have a lot o9f a typo there /dev/dsp-1 thats should be /dev/dsp1 ..
Nice catch, Peter!
I don't know if that setting is entered manually or selected from a drop-down list... we'll have to wait for Constant to check in, I guess.
Could be the solution. Must be a bug because I did not do any manual "labor" and to be honest, I cannot remember to have chosen anything at a drop-down list. Still do not exactly know what dsp means ;). And the result as shown in my last post was copied as is from a console.
Where do I start changing dsp-1 into dsp1?
I would have thought "cd /dev "l dsp-1 if dsp-1 is the device itself then as you say there must be a bug i have not got the same problem here . I hope that dsp-1 is a link to dsp if it is then "rm dsp-1 "ln-s dsp1 dsp I think that is the correct way round can never remember see "man ln" for more info .. Pete . -- The Labour party has changed their emblem from a rose to a condom as it more accurately reflects the government's political stance. A condom allows for inflation, halts production, destroys the next generation, protects a bunch of pricks, and gives you a sense of security while you are actually being fucked. from GSM
Care to share a model number, since the one you bought is known to work?
It's the "Logitech USB Headset 250" It works perfectly. I have to admit I was pleasantly surprised when I plugged it into the USB port and idscovered it worked immediately. I didn't have to start YAST and add it as a new device or anything... simply worked as soon as I plugged it in. As a caveat... controlling the volume is a challenge I've yet to solve to my satisfaction. The default settings are acceptable...
If I can, I'd like to avoid rearranging plugs every time I use Skype.
That's been my biggest beef with using Skype as my main phone :-) Once I got teh USB headset though... problems solved :-) No more futzing around with scrambling to swap over the speakers with the headset. C.
On Wed, 2006-05-10 at 16:13 +0200, Clayton wrote:
Anyway, I did find a way to "work around" the problem... I bought a Logitech USB headset, and set it as the default device for Skype. A couple notable changes... the sound quality improved 1000x, and I don't get the "problem with sound device" error anymore. Fantastic - I got mine today - very happy!
Thanks! Hans
On Saturday 20 May 2006 02:34, Hans du Plooy wrote:
On Wed, 2006-05-10 at 16:13 +0200, Clayton wrote:
Anyway, I did find a way to "work around" the problem... I bought a Logitech USB headset, and set it as the default device for Skype. A couple notable changes... the sound quality improved 1000x, and I don't get the "problem with sound device" error anymore.
Fantastic - I got mine today - very happy!
Am close to going for this hardware solution if it works with you Hans. Could you report the results. In the meantime I have taken two steps to improve my Skype. They seem to work. Found them on the Skype list. I changed the hangup.wav from a 16 bit into a 8 bit. It is the only 16 bit of the Skype wav and it is said to help with the general problem. The second change is to start Skype with "artsdsp -m Skype" . I did this in the Skype desktop icon. This worked up to now in my 9.3. Will now try it out in the 10.0 and next week in the 10.1 The general mood on the Skype list is down and nobody expects any improvement soon. More then six months without any change/improvement although the source of the problem is known to be the use of OSS in Skype instead of alsa.
On Sat, 2006-05-20 at 16:37 +0700, C. Brouerius van Nidek wrote:
On Saturday 20 May 2006 02:34, Hans du Plooy wrote:
On Wed, 2006-05-10 at 16:13 +0200, Clayton wrote:
Anyway, I did find a way to "work around" the problem... I bought a Logitech USB headset, and set it as the default device for Skype. A couple notable changes... the sound quality improved 1000x, and I don't get the "problem with sound device" error anymore.
Fantastic - I got mine today - very happy!
Am close to going for this hardware solution if it works with you Hans. Could you report the results. In the meantime I have taken two steps to improve my Skype. They seem to work. Found them on the Skype list. I changed the hangup.wav from a 16 bit into a 8 bit. It is the only 16 bit of the Skype wav and it is said to help with the general problem. The second change is to start Skype with "artsdsp -m Skype" . I did this in the Skype desktop icon. This worked up to now in my 9.3. Will now try it out in the 10.0 and next week in the 10.1 The general mood on the Skype list is down and nobody expects any improvement soon. More then six months without any change/improvement although the source of the problem is known to be the use of OSS in Skype instead of alsa.
Wasn't it about six months ago that the sale of Skype was completed? How amazingly coincidental. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (8)
-
C. Brouerius van Nidek -
Carl Hartung -
Carlos E. R. -
Clayton -
Constant Brouerius van Nidek
-
Hans du Plooy -
Ken Schneider -
Peter Nikolic