The kernle module snd-hda-intel could not be loaaded

Kocha · June 8, 2015, 11:36pm

Hello everyone,

I’m trying to get sound over HDMI with no results as of yet. I tried different things. In the KDE settings, the point for Sound over HDMI is greyed-out. Last thing I tried was over YaST. The first of my Intel soundcards (the normal one, not sound over HDMI) configured perfectly. The second one gave the error message “Kernel module snd-hda-intel could not be loaded. A possible reason could be wrong modul paramenters or wrong IO- or IRQ-parameters.” Since I have no clue how to set kernel parameters, I thouhgt I’d ask you guys.

Hardware is a brandnew Intel NUC with i7 and Intel HD 6100.

Greetings,
Kocha

hcvv · June 9, 2015, 9:49am

And the openSUSE version is???

deano_ferrari · June 9, 2015, 10:16am

Did you try configuring via YaST > Hardware > Sound yet? If you get stuck, you might want to share more details about your sound system with us.

Along with the openSUSE version, post these details as a start

cat /etc/modprobe.d/50-sound.conf

/usr/sbin/hwinfo --sound

Kocha · June 9, 2015, 11:56am

openSUSE version is 13.2 with all updates made.

I’ve tried installing it with YaST. I have two Intel soundcards showing up there. I assume the first one is for the audio outs and the second one for sound over hdmi. The first one was no problem. It installed just fine. The second one gave me the error message above.

/etc/modprobbe.d/50-sound.conf has this output:

options snd slots=snd-hda-intel# 3hqH.9axPssPrj9A:Intel Corporation
alias snd-card-0 snd-hda-intel

hwinfo --sound this:

09: PCI 03.0: 0403 Audio device                                   [Created at pci.328]
  Unique ID: 3hqH.9axPssPrj9A
  SysFS ID: /devices/pci0000:00/0000:00:03.0
  SysFS BusID: 0000:00:03.0
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x160c 
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x2057 
  Revision: 0x09
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xf7134000-0xf7137fff (rw,non-prefetchable)
  IRQ: 16 (no events)
  Module Alias: "pci:v00008086d0000160Csv00008086sd00002057bc04sc03i00"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=yes, avail=yes, need=no, active=unknown


13: PCI 1b.0: 0403 Audio device
  [Created at pci.328]
  Unique ID: u1Nb.DZPPTv1n3yC
  SysFS ID: /devices/pci0000:00/0000:00:1b.0
  SysFS BusID: 0000:00:1b.0
  Hardware Class: sound
  Device Name: "CIR Device"
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x9ca0 
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x2057 
  Revision: 0x03
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xf7130000-0xf7133fff (rw,non-prefetchable)
  IRQ: 63 (326 events)
  Module Alias: "pci:v00008086d00009CA0sv00008086sd00002057bc04sc03i00"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

deano_ferrari · June 9, 2015, 12:21pm

Let’s see how the cards are reported

cat /proc/asound/cards

aplay -l

Kocha · June 9, 2015, 12:57pm

 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7130000 irq 62

**** Liste der Hardware-Geräte (PLAYBACK) ****Karte 1: PCH [HDA Intel PCH], Gerät 0: ALC283 Analog [ALC283 Analog]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0

deano_ferrari · June 10, 2015, 12:38am

Hmmm…it’s not clear to me why two cards are detected by hwinfo and snd_hda_intel shown as loaded for both, but only one card reported by ‘aplay -l’. Run the ALSA diagnostic

sudo /usr/sbin/alsa-info.sh

It will upload the result to a server, and you can post the link that it generates here. Someone should be able to advise further following that information.

Kocha · June 10, 2015, 1:29am

Here’s the result:

http://www.alsa-project.org/db/?f=7497be2f29719e53428e4c243fc23f38d3b8f07a

Might be a problem with the drivers? The graphic driver also is pretty **** slow. I tried running games on it that run on my old laptop with Core2Duo and Intel HD graphicscard, got about 5fps.

deano_ferrari · June 10, 2015, 1:45am

Two devices are reported

!!PCI Soundcards installed in the system
!!--------------------------------------

00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------

00:03.0 0403: 8086:160c (rev 09)
    Subsystem: 8086:2057
--
00:1b.0 0403: 8086:9ca0 (rev 03)
    Subsystem: 8086:2057

The first thing that jumps out at me is with the kernel output

snd_hda_intel 0000:00:03.0: Cannot turn on display power on i915

This appears repeatedly in the kernel messaging.

Might be a problem with the drivers? The graphic driver also is pretty **** slow. I tried running games on it that run on my old laptop with Core2Duo and Intel HD graphicscard, got about 5fps.

Yes, it’s a driver issue, but I’m not sure if/how it relates to the graphics driver as well. I’m not familiar with this hardware, and a bug report is likely required.

deano_ferrari · June 10, 2015, 1:48am

BTW, I just wanted to check - Is your monitor attached via an HDMI cable?

Kocha · June 10, 2015, 3:52am

Yes, well it’s mini hdmi on the NUC and hdmi on the TV, so I have a mini hdmi to hdmi cable.

I just upgraded the kernel to version 4.0.5.1 (I didn’t even know that this exists yet) and upgraded xf86-video-intel to the newest version according to this site:

http://lslezak.blogspot.ch/2011/04/installing-latest-intel-graphics-driver.html

Didn’t help with the sound, but KDE runs a bit smoother. The games still don’t really run, though.

Might be that Intel hasn’t released any drivers for this model yet? Well, there are some for Windows on its page, but none for Linux.

I’ll try upgrading the BIOS tomorrow, see if that helps.

baskitcaise · June 10, 2015, 4:45pm

deano ferrari donned his tin foil hat and penned:

>
>
> Did you try configuring via YaST > Hardware > Sound yet? If you get
> stuck, you might want to share more details about your sound system with
> us.
>
> Along with the openSUSE version, post these details as a start
>
> Code:
> --------------------
> cat /etc/modprobe.d/50-sound.conf
> --------------------
>
>
> Code:
> --------------------
> /usr/sbin/hwinfo --sound
> --------------------
>
>

Deano and all.

I have found in 13.2 that you do not touch Yast to config sound. use the
desktop settings to do that I have more or less the same set up and all I
did was adjust to where the sound was piped.

At first I disabled the HDMI ( because it was not connected )

Then go from there and tell System settings where you want individual
streams to go.

HTH

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

deano_ferrari · June 10, 2015, 8:42pm

@baskitcaise: The issue is that the OP’s sound hardware is not completely recognised, although two devices are detected. The OP also mentioned “In the KDE settings, the point for Sound over HDMI is greyed-out.”

Did you check the OP’s diagnostic (alsa-info.sh) output (refer post#25)?

Kocha · June 10, 2015, 10:38pm

Just plugged in some headphones and on them, the sound works perfectly.

What I forgot to mention: My TV has HDMI 2.0 plugs, while the NUC only has 1.4 plugs. This usually shouldn’t be a problem, but I thought, I’d mention it.

baskitcaise · June 10, 2015, 10:39pm

deano ferrari donned his tin foil hat and penned:

>
>
> @baskitcaise: The issue is that the OP’s sound hardware is not
> completely recognised, although two devices are detected. The OP also
> mentioned “In the KDE settings, the point for Sound over HDMI is
> greyed-out.”
>
> Did you check the OP’s diagnostic (alsa-info.sh) output (refer post#25)?
>
>

Hi Deano,

Sorry, no I did not check, that post does not appear on nntp so no link,
suppose I will have to use the web side ( tut! )

Cheers

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

baskitcaise · June 10, 2015, 10:52pm

deano ferrari donned his tin foil hat and penned:

>
>
> @baskitcaise: The issue is that the OP’s sound hardware is not
> completely recognised, although two devices are detected. The OP also
> mentioned “In the KDE settings, the point for Sound over HDMI is
> greyed-out.”
>
> Did you check the OP’s diagnostic (alsa-info.sh) output (refer post#25)?
>
>

Addendum to my last, it appears that the corporate firewall I am going
through at the moment does not like any addy with “forum” et al in it so web
interface is out at the moment ( but I may be able to get there in a long
winded way )

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

deano_ferrari · June 10, 2015, 11:54pm

Yes, well that corroborates the with the part of your sound system that is reported as working.

What I forgot to mention: My TV has HDMI 2.0 plugs, while the NUC only has 1.4 plugs. This usually shouldn’t be a problem, but I thought, I’d mention it.

I think that it may be worth trying a newer kernel perhaps. A search of ‘snd_hda_intel 0000:00:03.0: Cannot turn on display power on i915’ does generate a number of hits that might be worth researching further.

Kocha · June 11, 2015, 9:32pm

I’ve upgraded the Kernel to 4.0.5.1, which is the newest version, I suppose? I also updated to the newest alsa version. Latter let to nothing but problems. Think, I’ll make a new partition and install Arch on it, to see if things work there.

oldcpu · June 11, 2015, 9:56pm

If you are willing to experiment a bit you could try a suggestion from this thread: http://askubuntu.com/questions/613056/no-audio-in-dell-xps-13-ubuntu-15-04 and this bug reoprt.

Their hardware is similar - but not identical - so I can’t say if their work around will work for you. They speculate that it is not an snd-hda-intel module to load … The bug report notes a workaround is to pass acpi_os="!Windows 2013" as a kernel parameter, but this is non-optimal since the mode of the touchpad is affected. I don’t know if the acpi setting will work for openSUSE also.

On the off chance it is an rt286 that needs to be loaded (based on that bug report an not on the information you provided) you could try with root permissions:


modprobe snd-soc-rt286

and then test / try to configure your audio. If that does not work, there is no harm.

Note the above is pretty big speculation on my part.

deano_ferrari · June 11, 2015, 10:24pm

I did stumble across that thread and the bug report myself.

I also note the following kernel reference
http://cateee.net/lkddb/web-lkddb/SND.html
mentions

vendor: 8086 ("Intel Corporation"), device: 160c ("Broadwell-U Audio Controller"

lkddb pci 8086 160c .... .... ...... : CONFIG_SND CONFIG_SND_HDA_INTEL : sound/pci/hda/hda_intel.c # in 3.16–3.19, 4.0, 4.1-rc+HEAD

and there is also an entry

lkddb acpi "INT343A" : CONFIG_SND CONFIG_SND_SOC CONFIG_SND_SOC_RT286 : sound/soc/codecs/rt286.c # in 3.17–3.19, 4.0, 4.1-rc+HEAD

I’m assuming a kernel upgrade is necessary first. Maybe both modules are required to be loaded?