This Post is 2 Years Old!
But for other’s sake I will cut and paste the solutions and info, that worked for me. Only because I don’t see my answer anywhere in the top 3 pages.
Read at your own peril … LOL
Hp Omen X Troubleshooting
ALSA, PulseAudio, HDMI, Kent, Sound File Location, Steam, HP Computers, Launchpad, Hibernate
• Commands
• $ pacmd list-cards
• $ sudo lspci -H1 (When Dirver IS installed properly)
‣ 01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1080 Mobile] (rev a1)
‣ 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
• Solved
• No NVHDA Solution - Install a Kernel module to toggle audio function.
∘ I can confirm that kernel module, posted by
∘ Maik Freudenberg (75985 – [NVC1] HDMI audio device only visible after rescan),
• Kernel module to toggle audio function
∘ is working fine on my system. Thank you for the fix. The HDMI audio device now works as it should (now detected).
∘ The steps I did to enable HDMI audio device:
∘ 1. Download and extract the file nvhda.tar.xz. (from above link)
∘ 2. Run these commands in Terminal, in the location of the extracted folder
• $ make
• $ sudo make install
• $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules
• $ echo “options nvhda load_state=1” | sudo tee /etc/modprobe.d/nvhda.conf
‣ sudo update-initramfs -u
∘ 3. Reboot.
∘ Reason Possibly Explained
∘ PCI: Enable NVIDIA HDA controllers
‣ Many NVIDIA GPUs can be configured as either a single-function video device or a multi-function device with video at function 0 and an HDA audio controller at function 1. The HDA controller can be enabled or disabled by a bit in the function 0 config space.
‣ Some BIOSes leave the HDA disabled, which means the HDMI connector from the NVIDIA GPU may not work. Sometimes the BIOS enables the HDA if an HDMI cable is connected at boot time, but that doesn’t handle hotplug cases.
‣ Enable the HDA controller on device enumeration and resume and re-read the header type, which tells us whether the GPU is a multi-function device.
‣ This quirk is limited to NVIDIA PCI devices with the VGA Controller device class. This is expected to correspond to product configurations where the NVIDIA GPU has connectors attached. Other products where the device class is 3D Controller are expected to correspond to configurations where the NVIDIA GPU is dedicated (dGPU) and has no connectors. See original post (URL below) for more details.
‣ This commit takes inspiration from an earlier patch by Daniel Drake.
#############################################################################
Problems SOLVED! I
∘ Hibernate/Suspend - NVHDA Sound doesn’t repopulate
• However, if I manually disable the audio output output “sudo tee /proc/acpi/nvhda <<< OFF” I’m then able to get it to sleep. I then have to turn it on again on resume with "sudo tee /proc/acpi/nvhda <<< ON
• $ sudo tee /proc/acpi/nvhda <<< OFF (before Hibernation/Suspend or Sleep)
• $ sudo tee /proc/acpi/nvhda <<< ON (After Resume)
• SOLVED! I
#########################################################################################
• ACPI (Advance Configuration and Power Interface)
• ERROR “acpi int3400 unsupported event” ERRORS …
‣ Edit Grub
• sudo gedit /etc/default/grub
• add to "grub’s …
∘ GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”, … acpi=strict to look like
∘ GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash acpi=strict”
• and Change GRUB_TIMEOUT=10 see Grub to GRUB_TIMEOUT=2. This will make the Grub load time to 2 seconds.
• sudo gedit /etc/default/grub
• sudo update-grub2
• sudo update-initramfs -u (Always a good idea)
• Limit Time Sop Jobs from taking 1 minute 30 seconds to run hundreds of acpi:3400 errors
• sudo gedit /etc/systemd/system.conf
∘ DefaultTimeoutStartSec=3s
∘ DefaultTimeoutStopSec=3s
∘ sudo update-initramfs -u (Always a good idea)
• Hibernate
• 2018 GTX 1080 Problems
∘ NVidia’s display and Sound
‣ lspci
• 01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1080 Mobile] (rev a1)
• 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
• pci:0 &
• bus info: pci@0000:01:00.0
‣ In Windows: Nvidia High Definition Sound
∘ Driver Version 1.3.37.4
∘ Driver Date 6/24/2018
∘ Intel’s
• pci:0 (as well)
• bus info: pci@0000:00:01.0
∘ PCH-H High Definition Audio Controller
∘ lspci -v | grep -A7 -i “audio”
• 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80)
‣ (vendor: 8086 (“Intel Corporation”), device: a171 (“CM238 HD Audio Controller”))
‣ Subsystem: Hewlett-Packard Company CM238 HD Audio Controller
‣ Kernel modules: snd_hda_intel
• 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
‣ Subsystem: Hewlett-Packard Company GP104 High Definition Audio Controller
‣ Kernel driver in use: snd_hda_intel
‣ Kernel driver in use: snd_hda_intel
############################################################################
• The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts… This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen.
‣ Unfortunately, on some cards this doesnt work properly and you end up with a black screen.
‣ nomodeset - Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.
• Unfortunately, the kernel won’t see the audio function unless you remove the graphics function first, which temporarily breaks the console. Because of that, it works best if you write a Shell Scripts to do it so you don’t have to SSH into the system or try to type the commands into the console blind.
∘ Obviously, you have to stop the X server first so that you can unload the NVIDIA drivers.
∘ For example, on my system, the GPU is at 01:00.0 and its parent PCI bridge is 00:01.0. So the Shell Scripts I use is:
∘ mine!! NVidia’s display bus info: pci@0000:01:00.0 Sound Should and Will be 01:00.1
‣ I was able to automatically have this work upon boot by using the legacy rc.local file, which is run by systemd upon boot. This is the content of the file:
• sudo gedit /etc/rc.local
sudo gedit /etc/rc.local
paste the code:
• No Driver Installed??
∘ Install common Sound card drivers and needed packages in Ubuntu.
• sudo apt-get install build-essential linux-headers-uname -r
alsa-base alsa-firmware-loaders alsa-oss alsa-source alsa-tools alsa-tools-gui alsa-utils alsamixergui
• sudo apt install kernel-package dh-make dwz libmail-box-perl uboot-mkimage
‣ 643MBs of Stuff hmmm? Optimism?
• Other stuff
∘
• sudo gedit /etc/modprobe.d/blacklist.conf
∘ CODE: SELECT ALL
‣ # Disable the HDMI audio
‣ blacklist snd_hda_intel
• Restart sound 1
• Restart sound 2
• sudo service pulseaudio restart
• pulseaudio -k
• killall pulseaudio
∘ start pulseaudio again as a daemon :
• pulseaudio -D
∘ Check if any pulseaudio instance is running :
• pulseaudio --check
∘
• Skype
∘ Playback
‣ headset - default device (default)
‣ HDMI 0 works
‣ White Speakers - USB AUDIO Device
‣ USB Sound Card - USB AUDIO, USB Audio Default Audio Device (default:CARD=AUDIO)
∘ Mic - USB Audio, USB Audio Default Audio Device (sysdefault:CARD=AUDIO)
• Phonon Settings
∘ Playback
‣ Sound Card - built-in
• USB AUDIO, USB Audio Default Audio Device (default:CARD=AUDIO)
‣ USB Sound Card - USB AUDIO (USB audio)
• MIC, - USB AUDIO (USB audio) (Default Audio Device)
• Crackling Mic
∘ Skype Microphone not working - SOLVED
‣ $ echo “autospawn = no” > ~/.pulse/client.conf
‣ $ killall plastering
‣ restart skype
• select 1st usb audio device in skype mic options (now many options before just pulseaudio
∘ Hallelujah
• if using HDMI output
∘ set in Frontend of Myth to ALSA:plughw1,3
‣ or pulseaudio:
• PulseAudio
∘ Pulseaudio Not Loading On Startup
‣ In case anybody else has experienced this problem, I was able to resolve it by entering autospawn = yes in ~/.pulse/client.conf
∘ kill or restart pulseaudio as user (not root)
‣ pulseaudio --kill && pulseaudio --start
∘ pulseaudio -k, killall pulseaudio
∘ sudo alsa force-reload
• Sound Glitches Kubuntu
∘ PulseAudio Volume Control
∘ pulse should not be installed with KDE ??
∘ remove the $HOME/.kde/share/config/phonondevicesrc file and restart KDE
∘ Here’s what I did to get PulseAudio managing all the sound for me in Intrepid KDE4.
‣ Setting Up Pulse
• First you need to get pulseaudio installed and set up properly if it is not already. You can get all the pulseaudio packages with your package manager. You also need to get a few other items and set up alsa, xine, gstreamer, phonon and pulseaudio for maximum usability.
‣ Open System Settings/Advanced/Autostart. Select Add program, type pulseaudio -D in the box and select Run in Terminal and Do not close when command exits click OK. In permissions check Is executable. In Application/Name type Pulseaudio and check that the Command is pulseadio -D so it starts with the defaults from default.pa. click OK. To set up the padevchooser launcher it is basically the same just change pulseaudio to padevchooser.
• aplay -l
• alsamixer