Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

alsa with realtek alc1150

840 views
Skip to first unread message

JohnF

unread,
Sep 1, 2014, 6:38:54 AM9/1/14
to
Thanks, guys, for help with my preceding video problem.
And now, can't get sound working either.
You may want to stay away from asus Z87I-deluxe mb.
At least, in my case, I don't know enough to tweak
the 14.1x32 drivers, etc, to get all the onboard
stuff working (wireless also not quite working, though
after installing wl.ko module there's an eth1 which
iwconfig sees, and I haven't even tried bluetooth yet).

Back to sound, the simple test
mpg321 thisALC1150isaPITA.mp3
emits
[oss.c:172] error: Can't open default sound device!
[audio.c:630] error: failed to open audio device
[audio.c:180] error: Unable to find a working output module
in this list: alsa,oss
[audio.c:532] error: Failed to open audio output module
[mpg123.c:902] error: Failed to initialize output, goodbye.

I got (lots) more info running alsa-info.sh from
http://www.alsa-project.org/main/index.php/Help_To_Debug
which, among its 1768 lines of output, has near the top

!!Soundcards recognised by ALSA
!!-----------------------------
0 [MID ]: HDA-Intel - HDA Intel MID
HDA Intel MID at 0xf7c34000 irq 52
1 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7c30000 irq 53
!!PCI Soundcards installed in the system
!!--------------------------------------
00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)
00:1b.0 Audio device: Intel Corporation Lynx Point High Definition
Audio Controller (rev 05)
!!HDA-Intel Codec information
!!---------------------------
Node 0x08 [Vendor Defined Widget] wcaps 0xf00000: Mono
Codec: Realtek ALC1150
Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC1150 Analog", type="Audio", device=0
!!All Loaded Modules
!!------------------
snd_hda_codec_realtek

And various other stuff from alsa-info.sh
that looks good, though none of which I actually understand.
But right near the bottom there's some bad-looking stuff
!!ALSA/HDA dmesg
!!--------------
[ 6.174447] snd_hda_intel 0000:00:03.0: irq 52 for MSI/MSI-X
[ 6.234415] hda_codec: invalid CONNECT_LIST verb 5[1]:0
[ 6.234543] hda_codec: invalid CONNECT_LIST verb 6[1]:0
[ 6.234669] hda_codec: invalid CONNECT_LIST verb 7[1]:0
[ 6.297910] hda_codec: ALC1150: SKU not ready 0x00000000

From
http://www.alsa-project.org
I saw that 1.0.28 is alsa's current version as of 6/17/14,
whereas /var/log/packages/ shows alsa stuff some two years
older (and not updated in slackware-current).
Realtek also has a download site (sorry about breaking up url)
http://www.realtek.com.tw/Downloads/
downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&
Conn=3&DownTypeID=3&GetDown=false
and I tried installing their "Linux driver(3.0)" from the
bottom of that page.
Bottom line...hosed the system, and I had to reinstall
14.1 from dvd, and start all over.
Now, at this point I could try downloading from alsa-project,
but you can understand I'm a little reluctant to do that without
any insight about what I'm doing or why I'm doing it (though
that's never stopped me before:). Can't even google whether or not
slackware's older alsa should or shouldn't support the alc1150.
The above diagnostics suggest it's at least being recognized.

Any suggestions about how to proceed to try to get
this stuff working? Thanks,
--
John Forkosh ( mailto: j...@f.com where j=john and f=forkosh )

buck

unread,
Sep 1, 2014, 12:19:17 PM9/1/14
to
JohnF <jo...@please.see.sig.for.email.com> wrote in
news:lu1ibu$1vo$1...@reader1.panix.com:

> Any suggestions about how to proceed to try to get
> this stuff working? Thanks,

Recommended reading:
http://andthatsjazz.org/gpu-hdmi-audio.html
--
buck

JohnF

unread,
Sep 2, 2014, 12:15:13 AM9/2/14
to
Thanks, buck. Well, that's a real page turner :).
Actually, hdmi not (yet) a problem. I'm just plugging
into lime audio jack on front of case, with the usual
little headset icon. I checked out their section 10,
"Issues In Alsa", but didn't notice anything relevant,
although I may easily have missed it due to lack of
prerequisite knowledge. Also, it's apparently 2+ years
old, which is pretty long in the tooth for this kind
of stuff.

JohnF

unread,
Sep 2, 2014, 3:46:57 AM9/2/14
to
Turns out drivers may not be the problem after all.
Asus Z87I-deluxe mb has two soundcards, card#0 the
default goes to hdmi (like buck may have been suggesting),
which I wasn't using. Googled a solution: create a
/etc/asound.conf file containing
pcm.!default {
type hw
card 1
device 0
}
ctl.!default {
type hw
card 1
device 0
}
to make card#1 default. After that, mpg321 >>says<< its
playing the mp3 file, but I'm still hearing nothing.
And alsamixer -c 1 seems to show volume turned up
on jack I'm plugged into.
Tried googling slackware disable hdmi audio
which I now think is the problem, and came across
several possible solutions, some even saying "it worked!",
from blacklist'ing to "remove"ing the unwanted card in
/sys/devices/pci0000:00/ But still no joy.
Any ideas, or url's that definitively discuss it? Thanks,

JohnF

unread,
Sep 2, 2014, 5:46:26 AM9/2/14
to
Sorry for following myself up yet again,
but ... got it working!
I think...
After messing around with googled suggestions,
including some rmmod/modprobe's (and god knows what else),
I finally tried changing the above asound.conf file
to device 1 which aplay had reported as "digital",
which I didn't think I wanted, but thought I'd try.
And, indeed, mpg321 still said it was playing,
and I still heard nothing. Then, just as a check,
I re-changed to device 3 which is non-existent,
and mpg321 complained as expected.
So I changed back to original device 0 and, lo,
mpg321 said it was playing, and now I heard it.
How's that possible??? I'm kind of afraid to reboot.
Will try to redirect and save output from all these sound
utils to document current state, and then keep fingers
crossed and reboot.
But alsa stuff in 14.1 apparently works for ALC1150
if configured right. Exactly how to do that seems
a little more problematic than it probably ought to be.

JohnF

unread,
Sep 2, 2014, 7:43:01 AM9/2/14
to
JohnF <jo...@please.see.sig.for.email.com> wrote:
> <<snip>>
> Sorry for following myself up yet again,
> but ... got it working!
> I think...
> After messing around with googled suggestions,
> including some rmmod/modprobe's (and god knows what else),
> I finally tried changing the above asound.conf file
> to device 1 which aplay had reported as "digital",
> which I didn't think I wanted, but thought I'd try.
> And, indeed, mpg321 still said it was playing,
> and I still heard nothing. Then, just as a check,
> I re-changed to device 3 which is non-existent,
> and mpg321 complained as expected.
> So I changed back to original device 0 and, lo,
> mpg321 said it was playing, and now I heard it.
> How's that possible??? I'm kind of afraid to reboot.
> Will try to redirect and save output from all these sound
> utils to document current state, and then keep fingers
> crossed and reboot.

Didn't work on reboot.
Only difference I could see was in lsmod|grep -i snd :
When sound worked...
snd_hda_codec_realtek 30084 1
snd_hda_codec_hdmi 26494 1
snd_hda_intel 29700 1
snd_hda_codec 123925 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,
snd_hda_intel
snd_hwdep 4738 1 snd_hda_codec
snd_pcm 62870 4 snd_hda_codec_hdmi,snd_hda_codec,
snd_hda_intel
snd_page_alloc 6062 2 snd_pcm,snd_hda_intel
snd_timer 14870 1 snd_pcm
snd 44159 8 snd_hda_codec_realtek,snd_hwdep,snd_timer,
snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,
snd_hda_intel
soundcore 4318 1 snd
After reboot when sound no longer worked...
snd_hda_codec_realtek 30084 1
snd_hda_codec_hdmi 26494 1
snd_hda_intel 29700 0
snd_hda_codec 123925 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,
snd_hda_intel
snd_hwdep 4738 1 snd_hda_codec
snd_pcm 62870 3 snd_hda_codec_hdmi,snd_hda_codec,
snd_hda_intel
snd_page_alloc 6062 2 snd_pcm,snd_hda_intel
snd_timer 14870 1 snd_pcm
snd 44159 7 snd_hda_codec_realtek,snd_hwdep,snd_timer,
snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,
snd_hda_intel
soundcore 4318 1 snd
Note that snd_hda_intel, snd_pcm and snd modules are "Used by"
one more module in the "When sound worked" list. But that
one more module isn't listed. What's going on with that???
Also, now that sound isn't working again,
trying to rmmod snd_hda_codec_hdmi says, Error: module in use,
suggesting I'm back where I started, needing to disable hdmi audio.
Any suggestions??? Thanks,

JohnF

unread,
Sep 2, 2014, 8:30:34 AM9/2/14
to
JohnF <jo...@please.see.sig.for.email.com> wrote:
> <<snip>
> Didn't work on reboot.

Okay, finally got it working (solution was to run alsactl init 1).
Let me document the full and easy solution, just in case anybody
else has similar problem...

First step:
--------------
type at the command prompt
aplay -l
and you should get output something like (this is my mb)...
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 1: ALC1150 Digital [ALC1150 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
From this list, determine the card# and device# you want
your sound played through.
In my case, that's card#1, device#0.

Second step:
---------------
edit/create either the file
/etc/asound.conf # for the whole world
or the file
~/.asoundrc # for your login only
and in either case put in the lines
pcm.!default {
type hw
card 1
device 0
}
ctl.!default {
type hw
card 1
device 0
}
using the card and device determined in step 1.

Third and final step:
------------------------
edit
/etc/rc.d/rc.local
and add the line
/usr/sbin/alsactl init 1
and reboot.
Note: no need to reboot immediately,
just run that command at command prompt.

Gee, a monkey at a typewriter could have figured
that all out quicker than I did. I googled and googled,
and nobody put those simple steps anywhere I could find.
The asound.conf file stuff, yes, but that alsactl nowhere
to be found.
0 new messages