Hi, I would like to announce that after many years the last use case of yast2-sound ( finding proper kernel driver for hardware ) gone[1] and we as yast team do not see reason to still maintain it. For this reason we create delete request for this yast module[2]. If there is still someone who finds module useful and willing to maintain it, please contact us. We can give you access to github repo and also move maintainership to you. For Leap 15.X nothing changes and module is still part of it same as for SLE15 codebase. Thanks Josef [1] https://bugzilla.suse.com/show_bug.cgi?id=1206903 [2] https://build.opensuse.org/request/show/1060978
On 2023-01-25 22:37, josef Reidinger wrote:
Hi, I would like to announce that after many years the last use case of yast2-sound ( finding proper kernel driver for hardware ) gone[1] and we as yast team do not see reason to still maintain it. For this reason we create delete request for this yast module[2]. If there is still someone who finds module useful and willing to maintain it, please contact us. We can give you access to github repo and also move maintainership to you. For Leap 15.X nothing changes and module is still part of it same as for SLE15 codebase.
Thanks Josef
[1] https://bugzilla.suse.com/show_bug.cgi?id=1206903 [2] https://build.opensuse.org/request/show/1060978
I have a use case for YaST sound on this Leap 15.4 machine. On every boot, sounds fails to work. The solution is, on every boot, to automatically do: yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Thu, Jan 26, 2023 at 10:07 AM Carlos E. R. <carlos.e.r@opensuse.org> wrote:
What alternative command can we use instead to do the same job?
None, it just should work, without any intervention, please file a bug report with all the sound card information.. and also, if still fails with Kernel:HEAD Cheers.
On 2023-01-26 08:34, Cristian Rodríguez wrote:
On Thu, Jan 26, 2023 at 10:07 AM Carlos E. R. <carlos.e.r@opensuse.org> wrote:
What alternative command can we use instead to do the same job? None, it just should work, without any intervention, please file a bug report with all the sound card information.. and also, if still fails with Kernel:HEAD
Adding to Cristian's message ... Carlos, you probably know this but in case not, when I'm filing bugs, I search the bugs database[1] first. If I don't find anything, I model my bug against a similar bug. This helps me determine setting fields such as /Product/, /Component/, /Version/, etc. As I have filed audio bugs in the past, I can offer you that if you need to open a bug, you will want to include /alsa-info.sh/ output[2]. In general, gathering as much information as possible cuts down on the initial back-and-forth and helps optimize the dev's time (minimizes context switching). If you haven't yet, have a look at the /Audio Troubleshooting/ Wiki[3]. Good luck! ::: References ::: [1] - https://bugzilla.opensuse.org/show_bug.cgi [2] - https://en.opensuse.org/SDB:Audio_troubleshooting#STEP-3:_Checking_your_audi... [3] - https://en.opensuse.org/SDB:Audio_troubleshooting --- Pablo Sanchez - Blueoak Database Engineering Ph: 819.459.1926 iNum: 883.5100.0990.1054
On 2023-01-26 14:34, Cristian Rodríguez wrote:
On Thu, Jan 26, 2023 at 10:07 AM Carlos E. R. <carlos.e.r@opensuse.org> wrote:
What alternative command can we use instead to do the same job?
None, it just should work, without any intervention, please file a bug report with all the sound card information.. and also, if still fails with Kernel:HEAD Cheers.
Heisenbug. When menaced with being reported, it behaved himself and worked fine, after a full power off/on. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On 2023-01-25 22:37, josef Reidinger wrote:
Hi, I would like to announce that after many years the last use case of yast2-sound ( finding proper kernel driver for hardware ) gone[1] and we as yast team do not see reason to still maintain it. For this reason we create delete request for this yast module[2]. If there is still someone who finds module useful and willing to maintain it, please contact us. We can give you access to github repo and also move maintainership to you. For Leap 15.X nothing changes and module is still part of it same as for SLE15 codebase.
Thanks Josef
[1] https://bugzilla.suse.com/show_bug.cgi?id=1206903 [2] https://build.opensuse.org/request/show/1060978
I have a use case for YaST sound on this Leap 15.4 machine. On every boot, sounds fails to work. The solution is, on every boot, to automatically do: yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Thursday 2023-01-26 14:25, Carlos E. R. wrote:
I have a use case for YaST sound on this Leap 15.4 machine.
On every boot, sounds fails to work. The solution is, on every boot, to automatically do:
yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job?
probably `rmmod` followed by `modprobe`.
On 2023-01-26 15:32, Jan Engelhardt wrote:
On Thursday 2023-01-26 14:25, Carlos E. R. wrote:
I have a use case for YaST sound on this Leap 15.4 machine.
On every boot, sounds fails to work. The solution is, on every boot, to automatically do:
yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job?
probably `rmmod` followed by `modprobe`.
Don't know, but an equivalent command would be nice to have. Many people have been doing that, uninstall-reinstall for years and years. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
On 2023-01-26 15:32, Jan Engelhardt wrote:
On Thursday 2023-01-26 14:25, Carlos E. R. wrote:
I have a use case for YaST sound on this Leap 15.4 machine.
On every boot, sounds fails to work. The solution is, on every boot, to automatically do:
yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job?
probably `rmmod` followed by `modprobe`.
Don't know, but an equivalent command would be nice to have.
I second Jan's suggestion - it is almost certainly about bad timing of a module load, somehow. It ought to be fairly easy to diagnose, from dmesg output.
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them. -- Per Jessen, Zürich (-0.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
* Per Jessen <per@opensuse.org> [01-26-23 12:54]:
Carlos E. R. wrote:
On 2023-01-26 15:32, Jan Engelhardt wrote:
On Thursday 2023-01-26 14:25, Carlos E. R. wrote:
I have a use case for YaST sound on this Leap 15.4 machine.
On every boot, sounds fails to work. The solution is, on every boot, to automatically do:
yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job?
probably `rmmod` followed by `modprobe`.
Don't know, but an equivalent command would be nice to have.
I second Jan's suggestion - it is almost certainly about bad timing of a module load, somehow. It ought to be fairly easy to diagnose, from dmesg output.
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]:
Carlos E. R. wrote:
On 2023-01-26 15:32, Jan Engelhardt wrote:
On Thursday 2023-01-26 14:25, Carlos E. R. wrote:
I have a use case for YaST sound on this Leap 15.4 machine.
On every boot, sounds fails to work. The solution is, on every boot, to automatically do:
yast sound remove && yast2 sound add I heard of other people doing the same. The root reason is not known. What alternative command can we use instead to do the same job?
probably `rmmod` followed by `modprobe`.
Don't know, but an equivalent command would be nice to have.
I second Jan's suggestion - it is almost certainly about bad timing of a module load, somehow. It ought to be fairly easy to diagnose, from dmesg output.
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Google it. Examples: <https://www.gamedev.net/forums/topic/339562-sound-only-works-after-restarting-sound-system-with-yast-under-suse/> Sound only works after restarting sound system with YaST under SuSE <https://unix.stackexchange.com/questions/165696/restarting-all-sound-services-and-their-configure-settings> I am working on OpenSuse 12.3, to get sound in here I have to go the yast settings and reinstall the sound card interface to get the sound working. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]:
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there. -- Per Jessen, Zürich (-0.5°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-27 09:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]:
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there.
Users are not the people that can continue building YaST, or at least publish the commands calls that yast does when reinstalling. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-01-27 09:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]:
Many people have been doing that, uninstall-reinstall for years and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there.
Users are not the people that can continue building YaST, or at least publish the commands calls that yast does when reinstalling.
Actually, anyone can read the logs or the code, but I only mentioned the users list as an example of where to go look for support. -- Per Jessen, Zürich (0.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-27 12:51, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-27 09:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]:
> Many people have been doing that, uninstall-reinstall for years > and years.
Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there.
Users are not the people that can continue building YaST, or at least publish the commands calls that yast does when reinstalling.
Actually, anyone can read the logs or the code, but I only mentioned the users list as an example of where to go look for support.
But I'm not asking for support. I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add" -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am 27.01.23 um 13:03 schrieb Carlos E. R.:
But I'm not asking for support.
I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add"
But a post on the Factory mailing list with subject "Drop of yast2-sound" is probably not the right place for this. Am 25.01.23 um 22:37 schrieb josef Reidinger:
For Leap 15.X nothing changes
- Ben
On 27.01.23 13:03, Carlos E. R. wrote:
I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add"
I don't know anything about the yast sound module, but a 5 minute look at the code hints that /usr/lib/YaST2/bin/alsadrivers unload # at "sound remove" and /usr/lib/YaST2/bin/alsadrivers reload # at "sound add" might be the thing that makes things work for you. So you might try these instead of calling "yast sound remove..." next time, and if this helps also, add this additional piece of wisdom to your already existing bug report. BTW: what is the bug number for this problem? You did not yet mention it here AFAIR. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
On 2023-01-27 13:14, Stefan Seyfried wrote:
On 27.01.23 13:03, Carlos E. R. wrote:
I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add"
I don't know anything about the yast sound module, but a 5 minute look at the code hints that
/usr/lib/YaST2/bin/alsadrivers unload # at "sound remove"
and
/usr/lib/YaST2/bin/alsadrivers reload # at "sound add"
might be the thing that makes things work for you.
Thanks. Much appreciated.
So you might try these instead of calling "yast sound remove..." next time, and if this helps also, add this additional piece of wisdom to your already existing bug report.
BTW: what is the bug number for this problem? You did not yet mention it here AFAIR.
I don't remember if I posted one at the time. Now the machine has been updated to 15.4 and works again. Nobody suggested a bug report at the time AFAIR. The most insistent advice was to remove pulse and install pipewire instead. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Just made "sudo zypper ref && sudo zypper dup" on tumbleweed and found there is no sound (and no "yast2-sound"). My system is alsa-only and I used yast2-sound to switch off pulseaudio on my old-but-still-perfect pci soundcard. Trying to figure out but no success yet.
On 2023-02-09 07:31, lesco wrote:
Just made "sudo zypper ref && sudo zypper dup" on tumbleweed and found there is no sound (and no "yast2-sound"). My system is alsa-only and I used yast2-sound to switch off pulseaudio on my old-but-still-perfect pci soundcard. Trying to figure out but no success yet.
Try /usr/lib/YaST2/bin/alsadrivers unload /usr/lib/YaST2/bin/alsadrivers reload as Stefan said. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Thu, 2023-02-09 at 10:40 +0100, Carlos E. R. wrote:
On 2023-02-09 07:31, lesco wrote:
Just made "sudo zypper ref && sudo zypper dup" on tumbleweed and found there is no sound (and no "yast2-sound"). My system is alsa-only and I used yast2-sound to switch off pulseaudio on my old-but-still-perfect pci soundcard. Trying to figure out but no success yet.
Try
/usr/lib/YaST2/bin/alsadrivers unload /usr/lib/YaST2/bin/alsadrivers reload
Considering /usr/lib/YaST2/bin/alsadrivers lives/lived in yast2-sound, this tip won't hold up. The script vanished together with the package. Cheers, Dominique (script is archived as part of git of course, yast-sound lived in https://github.com/yast/yast-sound)
On 2023-02-09 16:13, Dominique Leuenberger wrote:
On Thu, 2023-02-09 at 10:40 +0100, Carlos E. R. wrote:
On 2023-02-09 07:31, lesco wrote:
Just made "sudo zypper ref && sudo zypper dup" on tumbleweed and found there is no sound (and no "yast2-sound"). My system is alsa-only and I used yast2-sound to switch off pulseaudio on my old-but-still-perfect pci soundcard. Trying to figure out but no success yet.
Try
/usr/lib/YaST2/bin/alsadrivers unload /usr/lib/YaST2/bin/alsadrivers reload
Considering /usr/lib/YaST2/bin/alsadrivers lives/lived in yast2-sound, this tip won't hold up.
The script vanished together with the package.
Oh, of course. I should have known.
(script is archived as part of git of course, yast-sound lived in https://github.com/yast/yast-sound)
Then, what can lesco do? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
Then, what can lesco do?
Debug & diagnose the issue. Or revert to Leap? -- Per Jessen, Zürich (1.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-10 19:10, lesco wrote:
Just installed pipewire. Everything seems to be working fine. Let see if I can live with that.
As long as you don't have extreme audio needs, you'll probably be fine. For me, it hasn't been a perfect fit. I sometimes use low latency kernel and record audio/music. In my studio setup, pipewire is a no-no so far. But it seems to be getting there so maybe in a year we can start using pipewire for pro audio. I know that Unfa, a prominent Linux audio user, has started using it in his installation, Arch Linux. A nice thing to have when using pipewire is qpwgraph. Maybe you already have it installed. https://gitlab.freedesktop.org/rncbc/qpwgraph zypper --no-refresh in qpwgraph -- /bengan
On Thu, 9 Feb 2023 18:27:26 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-02-09 16:13, Dominique Leuenberger wrote:
On Thu, 2023-02-09 at 10:40 +0100, Carlos E. R. wrote:
On 2023-02-09 07:31, lesco wrote:
Just made "sudo zypper ref && sudo zypper dup" on tumbleweed and found there is no sound (and no "yast2-sound"). My system is alsa-only and I used yast2-sound to switch off pulseaudio on my old-but-still-perfect pci soundcard. Trying to figure out but no success yet.
Try
/usr/lib/YaST2/bin/alsadrivers unload /usr/lib/YaST2/bin/alsadrivers reload
Considering /usr/lib/YaST2/bin/alsadrivers lives/lived in yast2-sound, this tip won't hold up.
The script vanished together with the package.
Oh, of course. I should have known.
(script is archived as part of git of course, yast-sound lived in https://github.com/yast/yast-sound)
Then, what can lesco do?
Well, if you are curious the code is at https://github.com/yast/yast-sound/blob/SLE-15-SP5/src/bin/alsadrivers But as said in original announcement issue with it is that in TW after some changes in kernel it is no longer easy 1:1 mapping of sound card and kernel drivers, so that modprobing is much more tricky and basically yast will need to mimic kernel behavior to know which drivers to use. So options in this case is 1. switch to pipewire 2. stick with old kernel in Leap 15 and use yast2-sound workaround 3. find yourself or with yast2-sound (as long as it live) which modules works in given case and then it should be easy to unload and load it in trivial shell script. 4. report a bug and hopefully get answer from sound maintainer. Josef
On 1/27/23 22:33, Carlos E. R. wrote:
On 2023-01-27 12:51, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-27 09:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote:
* Per Jessen <> [01-26-23 12:54]: >> Many people have been doing that, uninstall-reinstall for years >> and years. > > Can't say I'm one of them.
but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there.
Users are not the people that can continue building YaST, or at least publish the commands calls that yast does when reinstalling.
Actually, anyone can read the logs or the code, but I only mentioned the users list as an example of where to go look for support.
But I'm not asking for support.
I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add"
The best place to ask this would be in the bugreport where you are attempting to work through and resolve the issue rather then depending on obsolete scripts as a work around. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2023-02-09 11:31, Simon Lees wrote:
On 1/27/23 22:33, Carlos E. R. wrote:
On 2023-01-27 12:51, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-27 09:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-26 19:31, Patrick Shanahan wrote: > * Per Jessen <> [01-26-23 12:54]: >>> Many people have been doing that, uninstall-reinstall for years >>> and years. >> >> Can't say I'm one of them. > > but you have heard of many people uninstall/reinstall as a solutin?
Haha, no, it's not a very persistent rumour :-)
Google it.
We are going off-topic here, it is a plain support question. I would suggest follow-ups to the users list. See the rest of my reply over there.
Users are not the people that can continue building YaST, or at least publish the commands calls that yast does when reinstalling.
Actually, anyone can read the logs or the code, but I only mentioned the users list as an example of where to go look for support.
But I'm not asking for support.
I am asking for someone that knows the insides of yast sound module to please tell what yast does when asked to "yast sound remove && yast2 sound add"
The best place to ask this would be in the bugreport where you are attempting to work through and resolve the issue rather then depending on obsolete scripts as a work around.
Nobody at the time I had the problem suggested a bug report — which I said maybe a week ago, and currently my problem is gone. But there is another poster (lesco) who has a problem with sound and no yast available just now — can you help him? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (14)
-
Ben Greiner -
Bengt Gördén -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Dominique Leuenberger -
Jan Engelhardt -
josef Reidinger -
lesco -
Pablo Sanchez -
Patrick Shanahan -
Per Jessen -
Simon Lees -
Stefan Seyfried