On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote> On 03/08/15 22:15, Chris H wrote: > > On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote > > > >> On 03/07/15 01:55, Chris H wrote: > >>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote > >>> > >>>> I've got MSI X99 motherboard and am using it with UEFI installation of----8<---BIG-SNIP---> >>> > >> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: > >> http://pastebin.com/pP0KXp4v > > Out of the 4 MSI boards I that I have; 3 run the same > > Realtek ALC893 HDA CODEC that yours does. The other, the > > Realtek ALC1200 HDA CODEC. All four of them work. But I > > notice 1 notable difference; that yours reports 2 > > HDA interfaces: > > hdac0: <NVIDIA (0x0fbb) HDA Controller> > > and > > hdac1: <Intel Wellsburg HDA Controller> > > I see hdac0 is disregarded (unused) whereas > > hdac1 is enabled, and functioning. I think your problems > > quite possibly lies in your (sound) system attempting to > > use the first HDA device in the list, which is effectively > > disabled. If you can determine a way to tell KDE, and friends > > to use the 2nd HDA. Things may well go as intended. > > None of the 4 MSI boards I have display 2 HDA's, as yours > > does. > > If you have any additional questions, you may well find > > the FreeBSD forums already have answers to your issue. This > > is where I originally found answers to my issues, when I > > first started using these boards. > > > > HTH > >> > >> KDE is definitely using OSS as chosen in its settings (I also use its > >> own mixer which can do the same as Xfce's). I also use VLC's Phonon > >> backend because Gstreamer is said to cause problems, but that also works > >> on 3 other computers. > > > I don't think it's KDE's fault, as it also happens when I kill KDE > (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have > vol and pcm maxed out.If your speakers are amplified, you should hear them "pop", when the kernel finds, and creates/attaches the driver(s) to it. Same would be true, if you were wearing your headphones when bouncing your box. I'm quite sure that the sound system is defaulting the the first HDA presented. Which, in your case, is the one that is disabled/ non-operational. It's not KDE per se; but how the software decides, by default, to hook sound up. If you had a sound control panel available in KDE. You *should* be able to *choose* which sound device to use. In your case, provided it's even seen, it would be the *2nd* HDA. The sound control panel should also present the *status* of the sound device that it's using. Which, in your case, would indicate everything as being "muted", and/or "unavailable". On the box I'm writing this from, the HDA/CODEC is the Realtek ALC893, as yours is. I have it hooked up to a 700 watt external amplifier that I use as sound for my entire house. With the amplifier turned on, if I bounce the box (reboot) I hear a "pop" when the kernel detects/attaches to the sound chip. These are the relevant, and only "sound" related devices, created/listed in /dev: cd0 dsp0.0 dsp1.0 dsp2.0 dsp4.0 midistat mixer0 mixer1 mixer2 mixer4 sndstat If I'm not mistaken, you're probably running GENERIC, which has *also* loaded snd_hda, and possibly/probably, others. Which accounts for the additional HDA listing in dmesg(8). What I would do, if I were you, is build/install a custom kernel, stripped of any device not available on your MB. This is the first thing I do, after a fresh install, and, as you're discovering, for good reason. :) You should also find, by doing so, that your system performs much better, as a result. The *only* sound related listings I have in my KERNCONF file, is: speaker # PC beeper sound # geneic sound snd_hda # Realtec CODEC HDA Last, and only because I have to say it; you *are* sure that you have your headphones/speakers plugged into the *correct* jack, right? ;-) Hey! It happens. :) --Chris --
I havent really followed this thread in great detail, but I just remembered that I also have an MSI motjherboard with onboard sound, pyus a graphics card with sound on it. I have to ouyht this in sysctl.conf hw.snd.default_unit=1 to make sure sound comes out of the onboard port not the graphics card, as the kernel finds them in the opposite order. Could something this work for you maybe ? -pete.
On 03/11/15 02:12, Chris H wrote:> On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote > >> On 03/08/15 22:15, Chris H wrote: >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote >>> >>>> On 03/07/15 01:55, Chris H wrote: >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote >>>>> >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > ----8<---BIG-SNIP--- >>>>> >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: >>>> http://pastebin.com/pP0KXp4v >>> Out of the 4 MSI boards I that I have; 3 run the same >>> Realtek ALC893 HDA CODEC that yours does. The other, the >>> Realtek ALC1200 HDA CODEC. All four of them work. But I >>> notice 1 notable difference; that yours reports 2 >>> HDA interfaces: >>> hdac0: <NVIDIA (0x0fbb) HDA Controller> >>> and >>> hdac1: <Intel Wellsburg HDA Controller> >>> I see hdac0 is disregarded (unused) whereas >>> hdac1 is enabled, and functioning. I think your problems >>> quite possibly lies in your (sound) system attempting to >>> use the first HDA device in the list, which is effectively >>> disabled. If you can determine a way to tell KDE, and friends >>> to use the 2nd HDA. Things may well go as intended. >>> None of the 4 MSI boards I have display 2 HDA's, as yours >>> does. >>> If you have any additional questions, you may well find >>> the FreeBSD forums already have answers to your issue. This >>> is where I originally found answers to my issues, when I >>> first started using these boards. >>> >>> HTH >>>> >>>> KDE is definitely using OSS as chosen in its settings (I also use its >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon >>>> backend because Gstreamer is said to cause problems, but that also works >>>> on 3 other computers. >>> >> I don't think it's KDE's fault, as it also happens when I kill KDE >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have >> vol and pcm maxed out. > If your speakers are amplified, you should hear them "pop", > when the kernel finds, and creates/attaches the driver(s) to > it. Same would be true, if you were wearing your headphones > when bouncing your box. > I'm quite sure that the sound system is defaulting the the first > HDA presented. Which, in your case, is the one that is disabled/ > non-operational. It's not KDE per se; but how the software > decides, by default, to hook sound up. If you had a sound > control panel available in KDE. You *should* be able to > *choose* which sound device to use. In your case, provided > it's even seen, it would be the *2nd* HDA. The sound control > panel should also present the *status* of the sound device > that it's using. Which, in your case, would indicate everything > as being "muted", and/or "unavailable". > On the box I'm writing this from, the HDA/CODEC is the > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > external amplifier that I use as sound for my entire house. > With the amplifier turned on, if I bounce the box (reboot) > I hear a "pop" when the kernel detects/attaches to the > sound chip. These are the relevant, and only "sound" related > devices, created/listed in /dev: > > cd0 > > dsp0.0 > dsp1.0 > dsp2.0 > dsp4.0 > > midistat > mixer0 > mixer1 > mixer2 > mixer4 > > sndstat > > If I'm not mistaken, you're probably running GENERIC, which > has *also* loaded snd_hda, and possibly/probably, others. > Which accounts for the additional HDA listing in dmesg(8). > What I would do, if I were you, is build/install a > custom kernel, stripped of any device not available > on your MB. This is the first thing I do, after a fresh > install, and, as you're discovering, for good reason. :) > You should also find, by doing so, that your system performs > much better, as a result. > The *only* sound related listings I have in my KERNCONF file, > is: > speaker # PC beeper > sound # geneic sound > snd_hda # Realtec CODEC HDA > Last, and only because I have to say it; > you *are* sure that you have your headphones/speakers > plugged into the *correct* jack, right? ;-) > Hey! It happens. :) > > --Chris > > -- > >I've deleted all other drivers except for snd_hda and sound but NVIDIA interfaces also use snd_hda driver. Also, I have already set up hw.snd.default_unit=4, which is the analog Intel interface (included in my 1st mail). I'm not sure how I should choose the default device in KDE, since it's chosen in hw.snd.default_unit. I'm not sure how you are able to hear a "pop" when sound devices are detected because it doesn't work that way on any of my other PC's (6 in total).
On 03/11/15 02:12, Chris H wrote:> On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote > >> On 03/08/15 22:15, Chris H wrote: >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote >>> >>>> On 03/07/15 01:55, Chris H wrote: >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj <pkubaj at riseup.net> wrote >>>>> >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > ----8<---BIG-SNIP--- >>>>> >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: >>>> http://pastebin.com/pP0KXp4v >>> Out of the 4 MSI boards I that I have; 3 run the same >>> Realtek ALC893 HDA CODEC that yours does. The other, the >>> Realtek ALC1200 HDA CODEC. All four of them work. But I >>> notice 1 notable difference; that yours reports 2 >>> HDA interfaces: >>> hdac0: <NVIDIA (0x0fbb) HDA Controller> >>> and >>> hdac1: <Intel Wellsburg HDA Controller> >>> I see hdac0 is disregarded (unused) whereas >>> hdac1 is enabled, and functioning. I think your problems >>> quite possibly lies in your (sound) system attempting to >>> use the first HDA device in the list, which is effectively >>> disabled. If you can determine a way to tell KDE, and friends >>> to use the 2nd HDA. Things may well go as intended. >>> None of the 4 MSI boards I have display 2 HDA's, as yours >>> does. >>> If you have any additional questions, you may well find >>> the FreeBSD forums already have answers to your issue. This >>> is where I originally found answers to my issues, when I >>> first started using these boards. >>> >>> HTH >>>> >>>> KDE is definitely using OSS as chosen in its settings (I also use its >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon >>>> backend because Gstreamer is said to cause problems, but that also works >>>> on 3 other computers. >>> >> I don't think it's KDE's fault, as it also happens when I kill KDE >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have >> vol and pcm maxed out. > If your speakers are amplified, you should hear them "pop", > when the kernel finds, and creates/attaches the driver(s) to > it. Same would be true, if you were wearing your headphones > when bouncing your box. > I'm quite sure that the sound system is defaulting the the first > HDA presented. Which, in your case, is the one that is disabled/ > non-operational. It's not KDE per se; but how the software > decides, by default, to hook sound up. If you had a sound > control panel available in KDE. You *should* be able to > *choose* which sound device to use. In your case, provided > it's even seen, it would be the *2nd* HDA. The sound control > panel should also present the *status* of the sound device > that it's using. Which, in your case, would indicate everything > as being "muted", and/or "unavailable". > On the box I'm writing this from, the HDA/CODEC is the > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > external amplifier that I use as sound for my entire house. > With the amplifier turned on, if I bounce the box (reboot) > I hear a "pop" when the kernel detects/attaches to the > sound chip. These are the relevant, and only "sound" related > devices, created/listed in /dev: > > cd0 > > dsp0.0 > dsp1.0 > dsp2.0 > dsp4.0 > > midistat > mixer0 > mixer1 > mixer2 > mixer4 > > sndstat > > If I'm not mistaken, you're probably running GENERIC, which > has *also* loaded snd_hda, and possibly/probably, others. > Which accounts for the additional HDA listing in dmesg(8). > What I would do, if I were you, is build/install a > custom kernel, stripped of any device not available > on your MB. This is the first thing I do, after a fresh > install, and, as you're discovering, for good reason. :) > You should also find, by doing so, that your system performs > much better, as a result. > The *only* sound related listings I have in my KERNCONF file, > is: > speaker # PC beeper > sound # geneic sound > snd_hda # Realtec CODEC HDA > Last, and only because I have to say it; > you *are* sure that you have your headphones/speakers > plugged into the *correct* jack, right? ;-) > Hey! It happens. :) > > --Chris > > -- > >A small update: I can set hw.snd.default_unit=5 and sound works through the front panel, but not so through the back panel. I have tried any other value from 0 to 7 and the sound works with the back panel on Windows so it's connected properly.