I have ubuntu 17.10 which defaults to 4.13. However, I can install a 4.15 kernel and nvidia works with it (390.48).
But I still can’t get audio over display port if I’m running hybrid graphics (modeset=1)
I can only get audio over DP if i use the BIOS setting in my thinkpad for pure discrete graphics.
Should I be expecting display port audio in hybrid graphics?
Tim, the audio device is turned on but the dmesg output looks odd, as if there’s nothing connected to it.
Does turning it off and on again make it work?
sudo tee /proc/acpi/nvhda <<<OFF
sudo tee /proc/acpi/nvhda <<<ON
the funny thing is that when I am in discrete nvidia mode, I have two Nvidia audio devices, one for the HDMI screen (which has no speakers) and one for the display port screen (the one I want).
When the system lists only one, and you see that it has nothing connected, I guess it is seeing the HDMI one only?
I have a confession to make. Today I ordered a Thinkpad t480 and I’m selling out of Optimus … Ubuntu 18.04 was the final straw, it was the best optimus solution for my use case, and now it just makes me :( Partly I use linux because it’s fun, and this has stopped being fun.
Understandable, Tim. Though your audio problems rather sounds like a design/firmware issue of that specific model. Would only be interesting to see the behaviour running Windows.
arn_epsilon, to have that stable, use the updated module from here:
[url]https://github.com/hhfeuer/nvhda[/url]
and use the dkms install method. Afterwards, run
sudo update-initramfs -u
This will keep the module recompiled on kernel updates.
I used the Maik Freudenberg Module and indeed it fixed the problem … but to add to this
I love to fool around until it is BROKE, knowing I can fix it with the aforementioned “Kernel Module” …
and used UKUU to install a bleeding edge Kernel that Ubuntu is NOT installing even with “Developer Mode” Checked … Ubuntu 18.04-1 is using 4-15 from JANUARY!!!
… so I found a tool called UKUU (needed a repository - I think … installed easy-peasy,and installed kernel 4-18 from THIS MONTHSEPTEMBER
Loving Linux for years, but could not believe my 1 week grief with a new cutting edge Omen X laptop - No HDMI / HDA / Nvidia Sound or Card as ALL on this forum know …
and this kernel SEEMS to have fixed it !! Just makes SENSE - How could they NOT! was my thinking as this problem has been around for almost a year!!!
and when I realized Ubuntu’s kernel is about that age … well the rest is history!
I also have an ASUS GL502VM with a GTX 1060 and I have a similar problem with some caveats. I’m loading the module using /etc/initramfs-tools/modules and I enable the audio output by placing “options nvhda load_state=1” at /etc/modprobe.d/nvhda.conf, but then I’m unable to get my laptop to sleep.
I’m using Kubuntu 18.10 and it will just hang with an error message that I believe has something to do with not being able to put all devices to sleep and it eventually kicks me back to the login screen. However, if I manually disable the audio output output before “sudo tee /proc/acpi/nvhda <<< OFF” I’m then able to get it to sleep. I then have to turn it on again after I resume it with “sudo tee /proc/acpi/nvhda <<< ON”. I automated this process using the a variation of the systemd units provided a few posts back and it has been working fine so far, but I still feel that it is flimsy solution.
Interestingly enough, If I manually “modprobe nvhda” after login from a terminal and if I enable the audio output with “sudo tee /proc/acpi/nvhda <<< ON” I’m able to sleep and resume. In that case, I still have the same problem as you, the HDMI audio output stops working, but by issuing “sudo tee /proc/acpi/nvhda <<< OFF” followed by “sudo tee /proc/acpi/nvhda <<< OFF” I get it to work again.
For the time being I’m just doing everything manually from the terminal with a couple of simple scripts: one that “modprobes” the nvhda module and enables the audio output, while another disables the audio output and “rmmods” the nvhda module. Sill, this is far from the perfect “ootb” experience that I would expect.
@generix
I didn’t notice that, but I developed my own custom systemd units myself.
Nevertheless, as I previously mentioned, when I load the module at “/etc/initramfs-tools/modules” I have to turn it the audio off before suspending (either manually or using the systemd unit). Otherwise, the suspend fails and I’m eventually sent to the lock screen.
If I load it later, on my own session using “sudo modprobe nvhda”, the system is able to sleep with no problem EVEN IF I don’t disable the audio before sleep.
I was just reporting this because I find it odd that loading the module at “/etc/initramfs-tools/modules” vs. “sudo modprobe nvhda” has such a different behavior and I was hoping to see if someone else had a similar experience.
BTW, instead of adding “nvhda” to “/etc/initramfs-tools/modules” and “options nvhda load_state=1” to “/etc/modprobe.d/nvhda.conf”, I tried to just run “modprobe nvhda” and “sudo tee /proc/acpi/nvhda <<< ON” on my rc.local. I was already using to set a few other things up on the up and since nvhda is a non-essential kernel module I thought, why not give it a try? It works as well as if it was built into the initramfs. So that another option if you prefer not to “pollute” your initramfs.