Trying to get sound working

johnjohn said:
but if a patch is necessary, then you would have to compile the source files that you linked to in a previous post or find a pre-compiled patch. I d not know if a patch is necessary for this system or not.
Click to expand...
jb1277976 said:
Also they added it already.. i don't know if its in this kernel or i have to compile a new kernel to add it
Click to expand...
Patching the hdac source code is not necessary. The added support for Tiger Lake-H you linked to consists of device identification for the audio driver to attach.

If you execute pciconf -vl | grep -B3 multimedia, the audio controller should be listed as "Tiger Lake-H HD Audio Controller", " as in this PR 272682 (Comment 1), from which the patch commit has derived. A attached driver can be recognized by it's device name (hdac1 in the PR, hdac0 on your system).

The issue (most likely) is the nid configuration. If there is audio on the headphones, then there should be audio on the speakers as well, with the proper configuration.

That said, just to make sure,
Code: 
hint.hdda.0.nid23.config=“as=1 seq=0 device=speakers”
hint.hdda.0.nid33.config="as=1 seq=15 device=Headphones”
didn't work? Double-check the values are properly quoted.
 
T-Daemon said:
Patching the hdac source code is not necessary. The added support for Tiger Lake-H you linked to consists of device identification for the audio driver to attach.

If you execute pciconf -vl | grep -B3 multimedia, the audio controller should be listed as "Tiger Lake-H HD Audio Controller", " as in this PR 272682 (Comment 1), from which the patch commit has derived. A attached driver can be recognized by it's device name (hdac1 in the PR, hdac0 on your system).

The issue (most likely) is the nid configuration. If there is audio on the headphones, then there should be audio on the speakers as well, with the proper configuration.

That said, just to make sure,
Code: 
hint.hdda.0.nid23.config=“as=1 seq=0 device=speakers”
hint.hdda.0.nid33.config="as=1 seq=15 device=Headphones”
didn't work? Double-check the values are properly quoted.
Click to expand...
Tried but still not working.. I triple checked.. instead of using hint.hdaa.0 i used

hint.hdac.0.cad0.nid23.config="as=1 seq=0 device=speakers"
hint.hdac.0.cad0.nid33.config="as=1 seq=15 device="Headphones"

Also if you look at this screenshot Analog is playing but just no sound..

https://0x0.st/8IZH.png
 
I’m reading the man page and I see this.. maybe I can start over and erase the bins from the manufactor

Code: 
dev.hdaa.%d.reconfig     Setting  this    to  a  non-zero     value
                     makes    driver to destroy existing pcm
                     devices and process new pins configu-
                     ration           set           via
dev.hdaa.%d.nid%d_config.


This looks interesting also

Code: 
dev.hdaa.%d.nid%d_original     Original pin configuration written by
                     BIOS.

What do you guys think?

I’ve even tried to switch seq but the headphones just play like nothing changed..

Any other ideas ?
 
jb1277976 said:
hint.hdac.0.cad0.nid23.config="as=1 seq=0 device=speakers"
hint.hdac.0.cad0.nid33.config="as=1 seq=15 device="Headphones"
Click to expand...
Hi jb1277976 i am just trying to go back to basics and in doing so, i notice that you keep reposting device hint with extra quotes. I usually chalk it up as forum post errors but i am beginnibg to wonder if you are really entering the hints with extra quotes.

your hint: hint.hdac.0.cad0.nid33.config="as=1 seq=15 device="Headphones"
should be hint.hdac.0.cad0.nid33.config="as=1 seq=15 device=Headphones"

if the patch is in-fact included in the 14.3 kernel, then why are we supposed to fiddle with device hints? shouldn't the patch be doing it for us? a patch is supposed to patch faulty, erroneous or otherwise insufficient code. Something is not right here.

to clarify: you are not getting sound from your speakers. do you get sound from your headphones?

as = association number and seq = sequence number.
"Associations are used to group individual pins to form a complex multi-pin device."
"Sequence number is a unique, per-association number used to order pins inside the particular association. 0-15"

so we should associate speaker and headphones or speaker, headphones and mic?
then we should assign sequence numbers to order the pins in the association?

hint.hdac.0.cad0.nid23.config="as=1 seq=1 device=Speakers conn=Fixed"
hint.hdac.0.cad0.nid33.config="as=1 seq=15 device=Headphones misc=0"
hint.hdac.0.cad0.nid25.config="as=2 seq=15 device=Mic conn=Jack"

I am new to this concept and i do not have a system that i can play with for learning purposes. I imagine that someone here can tell us if we are on the right path or not. Meantime, wait for an answer from someone with more experience.

I hope that you can get it working...
 
I’ve tried everything under the sun.. nothing works.. I have another laptop running FreeBSD I’m good.. thanks all
 
It's very unfortunate that we couldn't find a solution in this thread. I still think the problem is related to the Speaker device being detected with HP capabilities. As it seems, this can't be changed with pin reconfigurations. Have you tried playing around with GPIO pin configuration?
From snd_hda(4):
Code: 
	     hint.hdaa.%d.gpio_config
				  Overrides audio function GPIO	pins  configu-
				  ration  set  by BIOS.	 May be	specified as a
				  set of  space-separated  "num=value"	pairs,
				  where	 num is	GPIO line number, and value is
				  one of: "keep",  "set",  "clear",  "disable"
				  and "input".

				  "GPIOs"  are	a  codec's General Purpose I/O
				  pins which system integrators	sometimes  use
				  to  control  external	muters,	amplifiers and
				  so on.  If you have no sound,	or sound  vol-
				  ume is not adequate, you may have to experi-
				  ment	a  bit with the	GPIO setup to find the
				  optimal setup	for your system.
From your dmesg:
Code: 
hdaa0: NumGPIO=5 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1
hdaa0:  GPIO0: disabled
hdaa0:  GPIO1: disabled
hdaa0:  GPIO2: disabled
hdaa0:  GPIO3: disabled
hdaa0:  GPIO4: disabled
Does the following in /boot/device.hints with rebooting make a difference? You can try different values, keep, set, clear and input:
Code: 
hint.hdaa.0.gpio_config="0=set 1=set 2=set 3=set 4=set"

Ultimately, you can create a bug report on https://bugs.freebsd.org. There is a higher chance for an actual FreeBSD developer to come up with a solution for this problem than on this forum.
 
jb1277976 said:
Didn't work.. Thanks for keeping up with this thread.. i feel we are close!

Also they added it already.. i don't know if its in this kernel or i have to compile a new kernel to add it

src - FreeBSD source tree

cgit.freebsd.org cgit.freebsd.org
Click to expand...
Have you tested the pin configuration from the related PR ?
Additionally, I redirected the pin output using "hints devices" during boot with specific configurations:

hint.hdaa.0.nid20.config="as=1 seq=1 device=Line-out"
hint.hdaa.0.nid27.config="as=1 seq=2 device=Line-out"

These changes successfully fixed the bug, and audio output now works flawlessly without the need for manual adjustments during boot.
Click to expand...
 
bsdcode said:
Code: hdaa0: NumGPIO=5 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1<br>hdaa0: GPIO0: disabled<br>hdaa0: GPIO1: disabled<br>hdaa0: GPIO2: disabled<br>hdaa0: GPIO3: disabled<br>hdaa0: GPIO4: disabled
Click to expand...
I never really understood how the gpio pins worked.. I will reinstall FreeBSD today and test.. I put gentoo back on and sound works flawlessly..
bsdcode said:
Code hint.hdaa.0.gpio_config="0=set 1=set 2=set 3=set 4=set"
Click to expand...
Will do.. Thanks not giving up.. I’m going to unmark this as closed.. I still have hope.

How do you mark those snippets of code (quote) I tried and failed miserably!
 
monwarez said:
Have you tested the pin configuration from the related PR ?
Click to expand...
Not yet.. need to remove gentoo and try again.. not going to put a full system yet but will test with the minimum base system.

Also he said this
Code: 
none5@pci0:0:31:3:    class=0x040100 rev=0x11 hdr=0x00 vendor=0x8086 device=0x43c8 subvendor=0x17aa subdevice=0x22e5
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-H HD Audio Controller'
    class      = multimedia
    subclass   = audio

Becomes:

hdac1@pci0:0:31:3:    class=0x040100 rev=0x11 hdr=0x00 vendor=0x8086 device=0x43c8 subvendor=0x17aa subdevice=0x22e5
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-H HD Audio Controller'
    class      = multimedia
    subclass   = audio

Mine already looks like that. I will test though what everyone is recommending.. I really like FreeBSD

Thanks
 
jb1277976 said:
I never really understood how the gpio pins worked..
Click to expand...
Honestly, I don't really know much about GPIO pins myself. There are reports on this forum that setting GPIO pins helped to fix audio problems, so I think it's worth a try.

jb1277976 said:
How do you mark those snippets of code (quote) I tried and failed miserably!
Click to expand...
I typically just click on the "Quote" button in the bottom-right corner of the message I want to quote, and insert it into my edit section with the "Insert quotes..." button. Then I delete parts from the quote which are irrelevant for my reply. This should keep [code]...[/code] constructs from the original message intact.
 
monwarez said:
Have you tested the pin configuration from the related PR ?
Click to expand...
I’ve tested this hint I. The pr and that was a no go.. I don’t know why I would do 20 and 27 on mine when they are disabled..

Do you know anything about gpio pins ?

bsdcode said:
hint.hdaa.0.gpio_config="0=set 1=set 2=set 3=set 4=set"
Click to expand...
Tried these by they didn’t work.. I should open up a PR that we tried this on but is now closed..

I know we are close..

Also I’m using beep at the console to test sound if I should install a window manager and test with Firefox or pavucontrol I can
 
jb1277976 said:
Tried these by they didn’t work.. I should open up a PR that we tried this on but is now closed..
Click to expand...

I seem to have missed the GPIOx disabled in dmesg. From your original post, pcm0 should be the default device.

Code: 
pcm0: <Realtek (0x0287) (Analog 2.0+HP/2.0)> at nid 23,33 and 25 on hdaa0

Tinkering with GPIO settings, then we should try the following:
dev.hdaa.0.gpio_config="0=set 1=set" in /boot/device.hints
# sysctl hw.snd.default_unit=0

jb1277976 said:
I really like FreeBSD
Click to expand...
me too :)
 
I’m thinking something.. does it matter now since I reinstalled FreeBSD that I just boot to the console and running beep to test ? Should I install a full desktop/window manager then test with pavucontrol or it the same since mixertui does the same thing ? I’m still on the base
 
jb1277976 said:
I’m thinking something.. does it matter now since I reinstalled FreeBSD that I just boot to the console and running beep to test ? Should I install a full desktop/window manager then test with pavucontrol or it the same since mixertui does the same thing ? I’m still on the base
Click to expand...
It shouldn't make a difference if you use beep(1) in the console or inside a graphical session. It just writes audio samples to the /dev/dsp audio device.
 
While the devs look at the pr i submitted i had a question.. when i do a verbose boot and i see the pin configuartions i see this

Original:

hdaa0: 29 40471a6d 6 13 SPDIF-out None Analog 0x00 Black 10

Config:


hdaa0: 30 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA


I know orginal means thats what the bios/freebsd see at boot.. and user config is what i did.. if i didn't do anything why isn't it showing that ?

Also will SPDIF-out help us at all.. looking at AI just says something but i don't understand it.
 
Sheesh the last post was 6/24 and no progress I know they are working on it but in the tech industry things move fast.. I’ve installed another distro and will reinstall once the pr is updated
 
oxbar said:
Sheesh the last post was 6/24 and no progress I know they are working on it but in the tech industry things move fast.. I’ve installed another distro and will reinstall once the pr is updated
Click to expand...
Still Nothing..

Asked on discord to see if somebody can look into it..

Anyone else know somebody or can look up the PR 287754

Thanks
 
Hi, I just got audio working on a very similar machine. Sorry if I missed stuff with my ADD, but what exactly is and isn't working? I see a lot of talk about pins and stuff and almost definitely there are much simpler, more basic steps you have missed that will get things working.

I saw you posted the FreeBSD foundaiton audio guide. I went thorugh that too, it is missing some detail. I recommend instead going first through the steps in the Multimedia section of the handbook. It is not that much longer, but is more complete.

Once you have some concrete problems, post here and I will try to advice as per what I was able to determine works on my side.

Huh, apparently there is more than one handbook! This is by far the best entry I have found. It goes in detail through every basic step.
 
You must log in or register to reply here.
Back
Top