You are not logged in.
Pages: 1
After upgrading to kernel 4.10, HDMI does not work anymore. I have an Intel graphics card.
Does someone else have this problem? And what information do you need to know what is happening? Dmesg? Let me know, so I'll try upgrading again.
Offline
It could be a bug/regression - have you tried linux-lts ( https://www.archlinux.org/packages/core … /linux-lts ) which is currently 4.9.14
Offline
I have glitching HDMI audio with kernel 4.10 and higher.
Did you find out anything more about this?
I'm currently investigating the 'snd_hda_intel' module.
Offline
HDMI does not work anymore is quite different from glitching HDMI Audio...though ironically, even the latter is mostly due to a bug/regression in the kms driver, not snd_hda_intel...
Offline
I have 4.10.13-Arch, 4.10.13-Zen, 4.10.15-Zen-custom-apparmor, 4.11.1-linux-hardened, and 4.11.1-linux-hardened-custom-apparmor installed, and have not had problems with any of them.
For the record I use gvfs, (1.32.1-1) to manage the virtual file system, along with hot plugging and the like. I have no complaints.
Irvine
Et voilà, elle arrive. La pièce, le sous, peut-être qu'il arrive avec vous!
Offline
I have 4.10.13-Arch, 4.10.13-Zen, 4.10.15-Zen-custom-apparmor, 4.11.1-linux-hardened, and 4.11.1-linux-hardened-custom-apparmor installed, and have not had problems with any of them.
For the record I use gvfs, (1.32.1-1) to manage the virtual file system, along with hot plugging and the like. I have no complaints.
Irvine
Hmm I am intrigued. Why did you even mention you use gvfs (in this thread)? Is it in any case relevant?
Offline
I think so, yes. Gvfs handles all my hot-plug devices, like USBs, external drives.... HDMI, etc, etc.
After quitting Microsoft with the introduction of Windows-10, I experimented with Ubuntu. As you can see from my thread on the subject, hot-plugging my Tv caused me no end of grief.
A few weeks after I posted that thread, I migrated to Arch, and, after installing gvfs, was overjoyed to find hot-plugging, (including my Tv,) worked out of the box.
Initially, because I only really use VLC, (which has its own system for switching audio devices,) I saw no need to install pulse-audio. However, a recent update of my Bluetooth manager had pulse-audio as a dependency. Since pulse audio is now installed, VLC wishes to use it. As a consequence, it lost its native ability to switch audio devices. This necessitated writing a small bash and launcher to to switch between the Tv and laptop speakers. However, it was no big deal, and not even remotely comparable to the struggles I had getting HDMI output to work with Ubuntu.
Hope this helps,
Irvine
Et voilà, elle arrive. La pièce, le sous, peut-être qu'il arrive avec vous!
Offline
I don't think gvfs is anything you said...
Whether your monitor get configured (as in the states can be produced with `xrandr --output BLAH --auto` and `xrandr --output BLAH --off`) automatically depends on your DE. That could be the same case for external drives and thumb stick automounting as well (which mostly with the help of udisks2, a _dependency of_ gvfs, instead of _something depends on gvfs_).
Something deps on pulseaudio does not mean you have to use pulseaudio. Arch (sort of) has it enabled by default for all users though. You can do:
systemctl --global disable pulseaudio.socket
to avoid that.
P.S. Sorry for stealing the thread
Offline
I do not disagree with the details of what you are saying, however I think you are looking at this from the wrong angle: I never explicitly installed udisks2, I installed Gvfs. Furthermore, as the Wikipedia entry on gvfs hot plugging makes clear, you can't easily separate out either Udev, Udisk, or Gvfs, and say: "Oh it's this, not that." The three systems work to together to provide a harmonious whole.
If you read the thread I linked to, I originally solved the "hot plugging" problem solely with Udev and Xrandr, neither Udisks2 nor Gvfs were required. So, if I really wished to be pedantic, I would argue that Udev was the first link of the dependency chain.
For me though, the bottom line is that, as a direct result of installing Gvfs, there was no requirement to write custom Udev rules, and that is all that matters.
Anyway, to bring the thread back on topic, as far as "glitching HDMI audio", I would be more inclined to suspect a dodgy HDMI cable/connection than a kernel bug.
Irvine
Edit
correction
Last edited by IrvineHimself (2017-05-15 19:47:02)
Et voilà, elle arrive. La pièce, le sous, peut-être qu'il arrive avec vous!
Offline
Anyway, to bring the thread back on topic, as far as "glitching HDMI audio", I would be more inclined to suspect a dodgy HDMI cable/connection than a kernel bug.
I wish it was as simple as a cable.
I've tried 2 distros and even 2 different monitors, and when the kernel is 4.9, HDMI audio works fine, when updated to the latest 4.10.x the glitching starts.
Next I'll try some more distros and report back.
Offline
Kernel 4.11.0 has the same issue
Offline
@IrvineHimself, well gvfs does play a role in automounting for DE like gnome or file managers like thunar / pcmanfm (you are probably using either of them, coz they are the ones that have gvfs as _optional_ dependency). But it's not like a "standalone" / "general" solution like udiskie. For example, if I use i3-wm and nautilus (yeah the GNOME file manager that even _pulls_ gvfs), I will not have automounting working, because automounting is not implemented in nautilus but gnome-desktop (IIRC) -> gvfs -> udisks2.
And certainly I don't see how gvfs can be relevant in manipulating X...
Offline
Pages: 1