Contribute
Register

No audio on Dell 3471 with Realtek 3820

Yeah, I just thought maybe the Linux data could shape your response. Nevermind. Hackintool attached.
 

Attachments

  • pcidevices.txt
    3.4 KB · Views: 5
  • pcidevices.plist
    5.3 KB · Views: 1
Yeah, I just thought maybe the Linux data could shape your response. Nevermind. Hackintool attached.
It's puzzling why macOS is unable to detect the Realtek codec.

Possible cause:
  • When initializing the A2F0 controller, macOS is not configuring the PCI bus properly.
Some controllers can be quirky and require special treatment, which Linux provides in its ALSA drivers (ALSA = Advanced Linux Sound Architecture).

Possible remedy:
  • We can try spoofing A2F0 to other devices, which is a brute-force approach
    • We already tried spoofing it to A1F0 without success
 
I hate taking up your neurons on this. It is a pure hobby for me. But as long as you are willing - I am too. Yes, brute force makes sense to me!
 
I hate taking up your neurons on this. It is a pure hobby for me. But as long as you are willing - I am too. Yes, brute force makes sense to me!
Alright, let's establish a baseline with the AppleALC kext in this post:


This version limits retries to 50. I just want to make sure it works before we continue, otherwise all of those retry messages will interfere with other log messages.
 
Seems OK. AppleALC created 10:02 AM (Eastern). That is an hour ago.
ioreg:
1708358281566.jpeg


But Lilu Log still shows >100,000 attempts.
 

Attachments

  • Lilu_1.6.7_23.3.txt.zip
    313.3 KB · Views: 1
Let's replace Lilu.kext with the attached version, which also imposes a limit of 50 retries. Then reboot and grab the Lilu log file after waiting 120 seconds or checking for an updated timestamp on the log file.
 

Attachments

  • Lilu.kext.zip
    249 KB · Views: 3
Got the Lilu. ioReg:
1708361963488.jpeg


Getting Lilu Log. Timestamped 11:56 am (eastern, a few minutes ago)
But STILL the identical number of attempts. Almost too precise to be true. I tried power cycling - even unplugging. Did not reset NVRAM but I can't think of another way there could be previous version ghost.

Wait! There is another log file (different version number). Smaller! Sheesh.
 

Attachments

  • Lilu_1.6.8_23.3.txt
    56.3 KB · Views: 4
Ran it two more times. Got the same (truncated) Lilu log. Not sure whether it is timing out or really ending where it appears.
 
...

Wait! There is another log file (different version number). Smaller! Sheesh.
We can type ls -alt to list the files in order from most recent to least recent. This will distinguish between multiple versions of the log.
Screenshot 2024-02-19 at 9.15.12 AM.png
 
Ran it two more times. Got the same (truncated) Lilu log. Not sure whether it is timing out or really ending where it appears.
Please type ls -alt in the /var/log directory and post a screenshot. Let's see if there are multiple Lilu log files, though I think there should only be one.
 
Back
Top