I have installed 13.2rc1 on a new Toshiba laptop, but I have no sound.
aplay runs silently. There appears to be to sound devices, Intel HCMI anf Intel PCH. I am not surprised at silence from HCMI as I have no such devices, but how do I get basic stereo? In 13.1 there wa a yast2 sound module which is missing now.
Toshiba Protege Z30-A; running fvwm2 over X11; no gnome or KDE
I do not know about the rc, but I am running factory, and the package yast2-sound exists.
On Thu, 30 Oct 2014 17:26:01 GMT
nightwishfan <nightwishfan@no-mx.forums.opensuse.org> wrote:
>
> I do not know about the rc, but I am running factory, and the package
> yast2-sound exists.
Yes, I’ve had no trouble configuring sound with YaST and kmix in RC-1 on
my three machines. Well, no more than usual.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.14.1; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
Did you try changing the order of the sound devices in yast that sometimes works
How/ There is no sound option in my yast2; that was the original point! It is not shown as a package either.
…and now oit is magically available and I have sound!
issue closed
What you have NO sound in the hardware section of yast?? How did you manage that?? LOL Or is that a new feature of 13.2???
Go to yast and see if the sound package is installed (search for yast)
I guess it is flat out not detected if the Yast-sound is installed.Might be time to look for drivers I guess.
lspci may give a clue to the hardware
I typed too soon!
I got the yast2/sound option but its actions are curious
Hardware says I have two sound devices – Intel Audio device and Lynx Point-LP HD Audio Controller
In Yast2 select sound and these two show up. Configure and in that order. select index 0 , and then other/playTestSound…
Silence, so select index 1, still silence
Select 0/edit and the reset and next; still no sound
Select 1/edit and the same, but this time there is sound
Having a silent primary card is dumb so I set the Lync Point as primary
test again, silence with 0, but 1 works
What gives?
Now aplay -l says no sound cards (it was showing lots last week)
Rather upsetting as sound is what I do
I struggle a bit to visualize your setup. Can you please, immediately after a fresh boot, with your laptop (?) connected to the Internet, in a konsole/xterm, run the following diagnostic script:
/usr/sbin/alsa-info.sh
and select the SHARE/UPLOAD option. After the script is complete, in the konsole/xterm will be the WEB/Internet address where the script uploaded the diagnostic content. Please copy the WEB/internet address here.
I will then look at that information, and do my best to provide an assessment and give some (hopefully useful) advice.
Edit: I also note there have been updates to pulse audio since RC1, so if you are using the ‘raw’ RC1 than already it is out of date.
Not sure I got this right. Ran alsa-info.sh and it said
Newer version detected:
To view te ChangeLog, please visit http://www.als-project.org/alsa-info.sh.changelog
ALSA-Info script has been updatd to v
Please re-run the script
which is now an empty file.
Fixed a routing problem and reloaded
http://www.alsa-project.org/db/?f=9da250c9d5959755f3fb113d0b44996cdc56d64b
Sound devices are just complicated now a days.
This might help you understand the differences in the interface
Essentially it is a single device with multiple interfaces.
I note this:
!!Sound Servers on this system
!!----------------------------
ESound Daemon:
Installed - Yes (/usr/bin/esd)
Running - No
ie no pulse audio installed nor running. And no other sound daemon running. That is most unusual for KDE. What desktop are you using now ? Gnome ? LXDE ? Xfce ?
I also note two instances of alsa’s intel audio driver running:
!!Loaded ALSA modules
!!-------------------
snd_hda_intel
snd_hda_inte
where I note:
!!Soundcards recognised by ALSA
!!-----------------------------
0 [HDMI ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf0630000 irq 63
1 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf0634000 irq 64
!!PCI Soundcards installed in the system
!!--------------------------------------
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
where its clear that openSUSE has identified the HDMI sound device as card-0, and has identified the analog audio as card-1.
That reversal of HDMI and analog device is easiest to solve by using pulse audio with the pavucontrol (pulse audio volume control) application, but for some reason your openSUSE does not have pulse audio. Without pulse audio, and with the same driver being used for both instances, I don’t know how to easily reverse the two.
Below is the aplay output:
!!Aplay/Arecord output
!!--------------------
APLAY
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
**card 1:** PCH [HDA Intel PCH], **device 0:** ALC283 Analog [ALC283 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
and aplay also supports this assessment where the default (card-0) is HDMI. Most likely you have no HDMI devices connected, but rather its the ALC283 analog audio that you need to use.
I took a look at the dmesg output at the end, and there is a LOT of information there, and it is clear you did not run the diagnostic script immediately after a fresh boot like I asked. That complicates this. I assume there was a reason the script could not be run immediately after a boot (like I asked) but I can not figure out that reason from looking at the dmesg output. Could you explain that to me so I can understand better ?
Also, please advise if the following gives sound:
aplay -D=hw:1,0 -vv /usr/share/sounds/alsa/test.wav
where by specifying aplay like the above should play the test.wav sound via card-1, device-0 (hw:0,1) I am trying to see if the analog sound works.
EDIT: if the above gives an error, copy and paste EXACTLY what command you sent and EXACTLY what error you obtained.
My approach, if I were you , would be to fix the pulse audio removal, install pavucontrol, and use it to ensure that audio goes to card-1.
Another approach (which I do not know the details off my head) would be to try and reverse card-0 and card-1, but given they use the same alsa intel audio driver, that will be tricky.
Also, I note this:
!!DMI Information
!!---------------
Manufacturer: TOSHIBA
Product Name: PORTEGE Z30-A
Product Version: PT241E-01H06UEN
Firmware Version: Version 3.60
I own a Toshiba Satellite Z30, which is almost the identical device, (the cheaper satellite vs the more expensive portege) and audio works great. BUT some times I need to use pavucontrol to ensure audio is output to the correct device. ie sometimes it is routed to headset instead of to speaker. I definitely did NOT de-install pavucontrol on my Toshiba as for that specific hardware , I believe that removal would make it more difficult to use.
Hence I do recommend you install your openSUSE with the nominal pulse audio setup, install pavucontrol, and do not remove pulse audio.
.
Dd not add anything that wasnews to me. I have an HDMI connector on the machine in question but no HDMI equipment at all. I want to use the stright forward stereo analogue sound, and preferably by default. If I wany high quality sound I use the setup in the studio.
Sorry this is so long…
Why would I need ESound? Never used it before. Pulseaudio is the system that stops audacity working and on the 13.1 machine I am often having to kill it to get sound. As to desktop, what? I do not think I have a desktop (except as a computer). I run X11 with fvwm as window manager. No icons, no “tray” or distractions. xterm, emacs and audacity is most of what I use. Mouse is to select which xterm…
I also note two instances of alsa’s intel audio driver running:
!!Loaded ALSA modules !!------------------- snd_hda_intel snd_hda_inte
where I note:
!!Soundcards recognised by ALSA !!----------------------------- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xf0630000 irq 63 1 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf0634000 irq 64 !!PCI Soundcards installed in the system !!-------------------------------------- 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
where its clear that openSUSE has identified the HDMI sound device as card-0, and has identified the analog audio as card-1. That reversal of HDMI and analog device is easiest to solve by using pulse audio with the pavucontrol (pulse audio volume control) application, but for some reason your openSUSE does not have pulse audio. Without pulse audio, and with the same driver being used for both instances, I don't know how to easily reverse the two.
That is indeed what I want; yast2 suggests it can do it but it does not work
Below is the aplay output:
!!Aplay/Arecord output !!-------------------- APLAY **** List of PLAYBACK Hardware Devices **** card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 **card 1:** PCH [HDA Intel PCH], **device 0:** ALC283 Analog [ALC283 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0
and aplay also supports this assessment where the default (card-0) is HDMI. Most likely you have no HDMI devices connected, but rather its the ALC283 analog audio that you need to use.
I agree; as I have no HDMI equipment I was assuming it could be ignored but apparently not.
I took a look at the dmesg output at the end, and there is a LOT of information there, and it is clear you did not run the diagnostic script immediately after a fresh boot like I asked. That complicates this. I assume there was a reason the script could not be run immediately after a boot (like I asked) but I can not figure out that reason from looking at the dmesg output. Could you explain that to me so I can understand better ?
Simply I did not see the reboot part of the message
Also, please advise if the following gives sound:
aplay -D=hw:1,0 -vv /usr/share/sounds/alsa/test.wav
where by specifying aplay like the above should play the test.wav sound via card-1, device-0 (hw:0,1) I am trying to see if the analog sound works.
After the mesage I did try aplay with -Dhw:1 and it worked.
My approach, if I were you , would be to fix the pulse audio removal, install pavucontrol, and use it to ensure that audio goes to card-1.
Another approach (which I do not know the details off my head) would be to try and reverse card-0 and card-1, but given they use the same alsa intel audio driver, that will be tricky.
What do I get from pulseaudo? The installation did not add it and I have only ever found it a nuisance on the machines that have it. Reading wikipedia it sounds like it replaces jack, for which I also have not found a need.
I have audacity on my Toshiba Z930, with pulse audio enabled, and audacity works (I use the KDE desktop). Why does it not work on your Toshiba Z930 ? Possibly its your desktop.
As for ESound, I don’t recall if I have ever used it either. The point was not to say use ESound but rather to point out you have no Sound Servers running. Surely that must cause problems with applications that use the desktop, unless the desktop and applications go straight to alsa api to obtain a sound output.
Only FVWM ? I struggle here , wrt running a laptop with only FVWM (noting: https://en.wikipedia.org/wiki/FVWM ). I know I could not do it. So you have no KDE, no Gnome, no LXDE and no XFCE !! wow. But if it works … ok … albeit I sense it does not work for audio very well.
Good - that proves sound works.
The problem here is your FVWM (?) is trying to get audio from sound card-0 by default. I do not know of any easy way to tell FVWM to go to sound-card-1 instead.
Thats because you are using FVWM. This is really fundamental. Using only FVWM and not KDE, not Gnome, not lxde, not xfde. This sort of information is very important and should be in the first post of a help request wrt audio.
What pulse provides is the means to take audio from any input audio device, and direct it to any application. And it provides the means to take audio from any audio application, and direct it to any output audio device. Ergo one can direct sound NOT to go to sound-card-0, but rather go to sound-card-1.
Will pulse audio work with FVWM ? It may not.
Honestly, I probably would not have dived into this thread had I picked up on your desktop being FVWM (I missed that).
What you need to do now, IMHO, is find a way to tell your alsa driver to configure the HDA Intel HDMI at 0xf0630000 irq 63 (which I think is the 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)) to be sound card-1 and NOT sound card-0.
And at the same time tell the alsa driver to configure the HDA Intel PCH at 0xf0634000 irq 64 (00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)) to be sound card-0 and not sound-card-1.
But I may have the Haswell-ULT HD Audio Controller mixed up with the Intel Corporation 8 Series HD Audio Controller. I don’t know. This is beyond something that I can rattle an answer off of the top of my head, and as noted had I known (1) your laptop was a Toshiba Z930 (like mine) that has 2 Intel audio devices with multiple instances of the same Intel audio driver running (making it difficult to distinguish between the 2 instances) and (2) running FVWM , then I may not have jumped in.
I’ll take a look at my Toshiba Z930 to see how it configures sound card-0 and 1, but in all honesty, given I use KDE, I may not have any hints there.
.
I pulled my Toshiba out of its storage, flashed it up , and checked it. It turns out my Toshiba Z930 (satellite) has very different hardware from your Toshiba PORTEGE Z30-A. Clearly I was very confused thinking the hardware could be even remotely similar.
My sound servers:
!!Sound Servers on this system
!!----------------------------
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
ESound Daemon:
Installed - Yes (/usr/bin/esd)
Running - No
and my laptop HDMI hardware shares the same audio driver instance, and shares the same sound card as regular analogue audio (but is a different sound device on the same card) :
!!Aplay/Arecord output
!!--------------------
APLAY
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
So no help there.
I think efforts need to focus on how to tell alsa to swap the labelling of the two sound devices between card-0 and card-1 assignments.
Here is an idea (it may not work ) … which I obtained from here: https://bbs.archlinux.org/viewtopic.php?id=180102 (post#7).
I note this from your PC:
!!Soundcards recognised by ALSA
!!-----------------------------
0 **HDMI** ]: HDA-Intel - HDA Intel **HDMI**
HDA Intel HDMI at 0xf0630000 irq 63
1 **PCH** ]: HDA-Intel - HDA Intel **PCH**
In “/etc/modprobe.d/50-sound.conf” as the first line put:
options snd-hda-intel id=PCH,HDMI index=0,1
restart and test …
I hope that works, and if that fails, try
options snd-hda-intel id=PCH,HDMI index=1,0
restart and test. But I do not believe this second one should work.
Honestly, I don’t fully understand this syntax but I think the idea is to assign to id=PCH to the card index=0.
As you can see, I am trying to force a reversal of PCH and HDMI and I am not clear how to do this.
.
and I note I’m bad. I totally missed this in your first post.
I think we will not agree. I have used fvwm and had good audio on 3 dfferent laptops and three different desktops, and most of thesr are still in use. I use my computers to compose.
The pulseaudio/audacity problem turned up about a year ago. Fix is to kill pulseaudio and then one can get sound. I have been using fvwm and its predecesors for about 20 years and it provides what I need – terminals mainly. KDE feels to like Windows to me – too much clicking.
I was not sure if it was the new laptop or 13.2 that was causing the problem. Anyway installed 13.2 today and yes I have built the music software and can play back in audacity. Just a little more to configure for realtie sound.
Than yo for the thoughts though – much appreciated
Glad to read its working now. Its strange it was not before and it is now, but possibly between RC1 and the version you are using now there was an update that fixed it.
If sound does stop working in the future, I recommend you check the order of the sound devices, and if sound cards swapped, and if necessary, try that idea to force the PCH to a specific index.
.