No sound card detected

Varsuuk · 05-05-2017, 07:38 PM

I was replacing my many years old Linux server which was on an Intel Core2Duo and decided to get an inexpensive replacement which would run quieter.

I used to only use for running source control servers, firewalls, webserver for parents to get grandkids pics and for running Minecraft servers for my boy

I am familiar with Linux, been coding C++ in the environment for decades but not so much admining much

Ended up getting the Intel 7320, Asus ROG Strix Z270E (not what I orig ordered, long story - Amazon replaced it with much higher end MB...whatever, it's not a gaming machine)

Not much else, 16GB memory - the HDs are all the old drives from before (recent WD Gold 1TB, older Red 2TB REALLY old 750GB)

Install went fine, once fixed my UEFI issue missing the partition ;P oops...but at end no more issues.

EXCEPT:

Can't get sound to work.
Using the "built-in" sound, there is not a single card on the MB - planned on built-in video even. First time EVER for me to do that.

Not sure what to supply, the audio is said to be:
"ROG SupremeFX s1220A 8-Channel High Definition Audio CODEC"

Most likely the only times I would do any sound would be with headphones, so don't give a hoot about multichannel.

Preferences/Sound shows "Dummy Output"

Code:

sudo aplay -L

default
    Playback/recording through the PulseAudio sound server
null
    Discard all samples (playback) or generate zero samples (capture)
pulse
    PulseAudio Sound Server


sudo aplay -l
aplay: device_list:268: no soundcards found...

Code:

lspci -v

(copied audio part up top)
00:1f.3 Audio device: Intel Corporation Device a2f0
	Subsystem: ASUSTeK Computer Inc. Device 8723
	Flags: bus master, fast devsel, latency 32, IRQ 130
	Memory at df140000 (64-bit, non-prefetchable) [size=16K]
	Memory at df120000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 3
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
------------------------



00:00.0 Host bridge: Intel Corporation Device 590f (rev 06)
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:02.0 VGA compatible controller: Intel Corporation Device 5912 (rev 04) (prog-if 00 [VGA controller])
	DeviceName:  Onboard IGD
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, fast devsel, latency 0, IRQ 128
	Memory at de000000 (64-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [100] #1b
	Capabilities: [200] Address Translation Service (ATS)
	Capabilities: [300] #13
	Kernel driver in use: i915_bpo
	Kernel modules: i915_bpo

00:14.0 USB controller: Intel Corporation Device a2af (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, medium devsel, latency 0, IRQ 120
	Memory at df130000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
	Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation Device a2ba
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, fast devsel, latency 0, IRQ 129
	Memory at df14d000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
	Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Device a282 (prog-if 01 [AHCI 1.0])
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 126
	Memory at df148000 (32-bit, non-prefetchable) [size=8K]
	Memory at df14c000 (32-bit, non-prefetchable) [size=256]
	I/O ports at f090 [size=8]
	I/O ports at f080 [size=4]
	I/O ports at f060 [size=32]
	Memory at df14b000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA v1.0
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1b.0 PCI bridge: Intel Corporation Device a2e7 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: 90000000-901fffff
	Prefetchable memory behind bridge: 0000000090200000-00000000903fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 872f
	Capabilities: [a0] Power Management version 3
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.0 PCI bridge: Intel Corporation Device a290 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: 90400000-905fffff
	Prefetchable memory behind bridge: 0000000090600000-00000000907fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 872f
	Capabilities: [a0] Power Management version 3
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	Memory behind bridge: df000000-df0fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 872f
	Capabilities: [a0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Access Control Services
	Capabilities: [220] #19
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.6 PCI bridge: Intel Corporation Device a296 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 872f
	Capabilities: [a0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Access Control Services
	Capabilities: [220] #19
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: 90800000-909fffff
	Prefetchable memory behind bridge: 0000000090a00000-0000000090bfffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 872f
	Capabilities: [a0] Power Management version 3
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1f.0 ISA bridge: Intel Corporation Device a2c5
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, medium devsel, latency 0

00:1f.2 Memory controller: Intel Corporation Device a2a1
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: bus master, fast devsel, latency 0
	Memory at df144000 (32-bit, non-prefetchable) [size=16K]

00:1f.3 Audio device: Intel Corporation Device a2f0
	Subsystem: ASUSTeK Computer Inc. Device 8723
	Flags: bus master, fast devsel, latency 32, IRQ 130
	Memory at df140000 (64-bit, non-prefetchable) [size=16K]
	Memory at df120000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 3
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1f.4 SMBus: Intel Corporation Device a2a3
	Subsystem: ASUSTeK Computer Inc. Device 872f
	Flags: medium devsel, IRQ 11
	Memory at df14a000 (64-bit, non-prefetchable) [size=256]
	I/O ports at f040 [size=32]
	Kernel modules: i2c_i801

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
	Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I219-V
	Flags: bus master, fast devsel, latency 0, IRQ 127
	Memory at df100000 (32-bit, non-prefetchable) [size=128K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] PCI Advanced Features
	Kernel driver in use: e1000e
	Kernel modules: e1000e

03:00.0 USB controller: ASMedia Technology Inc. Device 2142 (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 8732
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at df000000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
	Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] #19
	Capabilities: [300] Latency Tolerance Reporting
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: xhci_hcd

seasons · 05-06-2017, 10:24 AM

You need a 4.11 kernel: https://www.phoronix.com/scan.php?pa...-Sound-Updates

Varsuuk · 05-06-2017, 12:26 PM

OH...my... that explains it... but definitely sounds like a problem

I just installed Mint 18.1 and began recreating the old environment. But it is only on 4.4.0-53 (with Update manager listing in red: 4.4.0-77.98) so it seems unlikely it will see 4.11 via the distro.

I am not any longer in the world of time or even mindset to actively manage entire systems. Once long ago, I ran my linux via Gentoo and LOVED compiling all the newest stuff - but I wasn't married, I didn't have a young boy and I didn't get home from work until after 7:30 back then...

Is there any "easy" way to update the kernel and still be able to use Mint's package/update manager or do I have to head off to fly by seat of pants time again?

I don't really care about sound, except it is next to my main PC and could be of use to allow my son to do some things on it so if there is a Linux game we can both be in same room vs him in his and us communicating with TS3 (which server is on the Linux box)

If this IS possible, could you or someone point me to a decent "howto" etc?
I'm not at all scared to compile my own etc, I code all day long - just want to have minimum trouble with later Mint updates etc if I did this.

THANKS for the heads up!
Can't believe how much googling I did with MB name and Linux sound error messages to no avail. Bah. I suck.

Varsuuk · 05-06-2017, 12:39 PM

Of course, now I want to cry because while reading the Kernel article, I came across mention of GCC7 and I was like...??

You see, I work in a Finance Exchange and getting them to switch to a newer compiler just for C++11 has been an ongoing fight still. Heaven knows C++14 is already long out and C++17 is well underway. I was pretty sure there was a GCC6 (we still use like 4.4? I forget) but no idea they were up to 7.

I just looked at my Mint and see... GCC5.4.

I really can't go back to Gentoo... but things like this make me want to

I know I have little reason to cry, it isn't like I have time for personal coding any longer - likelihood that I can fire up GCC7 and muck about much is small.

But still, know I CANNOT have it...hurts my geek brain.

Before I go full on into Mint18.1, any idea if there are other "good" easy to keep stable distros that keep more up to date with GCC/Kernels? Not sure I can convince myself to increase risk of maintenance but... I might go weak and do it anyway ;P

I hope I stay strong with pedestrian Mint it seems easier to deal with...

Varsuuk · 05-06-2017, 12:45 PM

Hmm... last poster mentions using Mint with Kernel 4.9 and works with 1220.

I guess, I should either:
1. Buy a cheap PCI (SB?) sound card (all my old SBs were old school ISA I finally tossed lol) so can "just work."
2. Read a HowTo on getting 4.9 or 4.11 etc to work on Mint 18.1 (look to see if can get howto on installing ALTERNATE gcc so can do my own coding in newer compiler but allow any system recompiles etc to use the same one the rest was compiled with for compatibility.
3. Switch to something like Fedora which goes more cutting edge - what are the big negatives there? It might be the best option because it likely updates gcc more often.

seasons · 05-06-2017, 02:42 PM

Considering that Mint is based on Ubuntu, I'm fairly sure you can just use one of Ubuntu's "mainline" kernels:
https://wiki.ubuntu.com/Kernel/MainlineBuilds
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

Shadow_7 · 05-06-2017, 03:32 PM

You might be able to compile the alsa part only on the older GCC. But it depends on how much access you have I guess. Probably not enough to swap parts in /lib/modules/$(uname -r)/ for "custom" bits. Or to modprobe / insmod from full path areas. It was easier when alsa wasn't integrated into the kernel. The problem with a lot of new hardware is that you have issues using it without a new / bleeding edge kernel. Baring a few things available on github like wifi drivers.

When the driver is in use, it should show up in /proc/asound/cards.

seasons · 05-06-2017, 04:13 PM

Quote:

Originally Posted by Shadow_7

You might be able to compile the alsa part only on the older GCC.

You don't need to compile anything to install a new kernel (unless you've got dkms modules that get rebuilt). I'm not sure how talk of compilers made its way into this thread.

Shadow_7 · 05-06-2017, 04:52 PM

Quote:

Originally Posted by seasons

You don't need to compile anything to install a new kernel (unless you've got dkms modules that get rebuilt). I'm not sure how talk of compilers made its way into this thread.

Post #4 from the OP about finance and adoption. Sounds like a work computer, but I could be wrong. In my case I was referencing using NEW alsa on an OLD kernel, the kernel that comes with whatever distro applies. Permissions to do that would be the same as those needed to do a full kernel swap. But it's less risky to fudge a few drivers than to swap out kernels. And with drivers you wouldn't technically need to reboot to use the new drivers.

Varsuuk · 05-06-2017, 06:36 PM

Nah - it is my home Linux box. I have run a linux (original Solaris back when) at home so I can use it for further education and testing code that I may want to work on for office in future. I'm a hobbyist as well as a senior c++ dev... I should be playing video games but sometimes I just want to write some new libraries instead.

I have full access. From the thermal paste to the OS... I just built it to replace my last Linux box. Usually my Linux box(es - sometimes I've had 2) are "hand me downs" of my old "secondary game machines" but now that have a 10yo boy, I don't have those for handmedowns so I bought an inexpensive setup and just xferred drives and PSU while replacing rest.

I asked about the DKMS stuff only because installing Mint it warns on the "driver" screen that you may need to recompile DKMS (whatever the initials are

) for the new kernel. So, problem thinker I am (my servers going down for a while can cost my employer easily several millions... so I tend to think defensively and it carries over to regular life, I guess too) I was just imagining if I REPLACED the GCC with a new one if some components were built with the old timey C++98 compilers and all of sudden part is rebuilt with C++17 compilers (I'd prob only use in C++14 atm) - if any heck would break loose... especially were there cross-border exceptions.

But ya, the MAIN thing (I'm sorry - I'm pathologically tangential) is asking if there was a "safe" way to install a higher stable kernel to see if it solves my sound card issue. I read via the link it's 2.11 but someone said worked for them in 2.9, so figure would try that one first IF I could do so safely/easily with Mint.

Shadow, thanks for the reply - I can see why you thought that way - I mentioned the adoption problem because it was the reason I wanted to adopt it here so I could learn and get practice. I worry that I have become too out of date with modern >C++98 USE (vs reading the books). I'm gold at my current company, but who knows if they decided to drop my part of the business - I'd be less gold

So rather keep the level of expertise I can claim in '98 for the newer ones as well. Hence practice at home if I cannot get them to update (harder still because they are primarily a Java place except for our specific Trading System team, other TS's are Java.)

Shadow_7 · 05-06-2017, 09:06 PM

I tend to copy the /boot/config from the distro's default kernel to .config of the latest stable kernel from kernel.org and make oldconfig. There's just a lot of manual steps like running update-grub to get the bootloader up to date afterwards, which the distro would have done for you if you installed a distro supplied kernel. But I've been compiling kernels since the old 2.4.x days. There are various distro ways to make a kernel too, make-kpkg, make deb-pkg, and various others. Which is probably better since it handles the initrd side of things versus trying to figure out which things need to NOT be modules so it can read itself off device. The advantage of compiling the kernel is you don't get GCC versioning issues with the other things already a part of your distro.

Varsuuk · 05-07-2017, 12:51 AM

I'm going to try to build it tomorrow, if son allows me the time

So there is no "PPA" (I'm so new to this stuff I just recall initials but not meanings) for 2.11 kernel? (or 2.9 for that matter, if can't get 2.11)

I will have to do some googling if going to build it based on Shadow's "manual steps" comment. I wouldn't know where to start without that.

273 · 05-07-2017, 07:21 AM

This guide doesn't look too difficult.
This has reminded me and I'm about to try to install the 4.11 kernel from the Debian experimental repository (I'm running Sid) to see whether it will just install.
Edit: It doesn't seem to want to play with the installed NVIDIA proprietary drivers, sadly, so likely I'd need to install them manually rather than using nvidia-kernel-dkms.

Varsuuk · 05-07-2017, 01:19 PM

I just tried this prior to reading your edit.

It was indeed easy to install.
Reboot (even cold) did not change what I saw on my lspci, aplay, etc runs.
Still no sound device should in Preferences/Sound and aplay -l "no soundcard" so it may be a different issue unless I need to get something else installed.

Not using the nvidia (at the moment anyway - in future, who knows) but I do see on my "Updates" page I have the update for Kerner 4.4 avail (still since it doesn't register the 4.11) but what made me think twice is that it also includes a "kernel firmare for 4.4" update. Did I need to get "kernel firmware for 4.11" somewhere as well?

But yea, no sound detection still.

Varsuuk · 05-07-2017, 01:34 PM

Installed.

Still only shows "Dummy Output" in devices on the control app.
Nothing shows up in pulldown for hardware devices either.