zlacker

[parent] [thread] 21 comments
1. vladva+(OP)[view] [source] 2022-09-24 18:04:43
This seems to me as a more generic problem with newer hardware, not specific to Linux. Likely devices rushed out the door to meet some idiotic deadline, badly specced and with incompletely implemented drivers.

At the end of 2021 I got an EliteBook 845 g8 (Zen 3) that worked completely fine out of the box on Linux (Arch with up-to-date kernel). Every last bit of kit worked perfectly. Bluetooth, IR webcam, fingerprint sensor, light sensor, mute LEDs, etc. On Windows, to this day, the webcam isn't recognized because of some USB chip along the line. There's also a lot of lag when adjusting the display backlight, for some reason.

I also have its cousin, an EB 840 g8 (intel 11th gen). A few days ago I installed Win11 22h2 on it. I was lucky to have had an external mouse, since neither the touchpad nor the track point could be used for setup. And it absolutely needs the latest Intel GPU drivers to correctly output 4k@60 through its HP dock (DP pass-thtough, not DisplayLink). On Linux, the same display setup has worked well since day one. But the mute LEDs are still broken.

Both laptops don't come with integrated wired network, so I have an HP USB dongle (Realtek chip). This works quite well on Linux. On Windows, it initially works well, but then, for some reason, Windows figures it needs to update the driver. Then it gains some interesting failure modes, where from the terminal I can do whatever I want, but Edge keeps thinking the connection is lost.

replies(5): >>uluyol+H >>spadro+O >>kitsun+k4 >>Andrex+Wz >>mycall+iq2
2. uluyol+H[view] [source] 2022-09-24 18:10:38
>>vladva+(OP)
Arch is a rolling release distro. So it gets hardware support faster than other distros that stick to older kernels and userspace. Most users are not on rolling releases.

I personally like the rolling approach, but that doesn't reflect everyone's experience.

replies(2): >>yjftsj+Bc >>sillys+SP
3. spadro+O[view] [source] 2022-09-24 18:11:29
>>vladva+(OP)
In all my years I have yet to see HDMI output from a laptop to a monitor work on the first try in Ubuntu. Always need to install the proprietary drivers for that to work at all. If it can't even do that without a headache, after 10+ years of Linux use, I would call that a Linux problem, not a hardware problem. My colleagues seem to run into the same issue frequently as well. This article seems kind of ignorant. I'm glad it worked on the first try on his ancient ThinkPad. That doesn't mean Linux is stable enough for most normal use cases on most hardware for me to recommend it to any of my non-tech proficient family.
replies(7): >>vladva+s1 >>marcod+72 >>cycoma+C6 >>adrian+Le >>nijave+qf >>encryp+lh >>vanvie+yy
◧◩
4. vladva+s1[view] [source] [discussion] 2022-09-24 18:14:59
>>spadro+O
I've never had any issue with HDMI or DP output. But it's true that my only laptop with a dedicated GPU was an MBP, all the others have or had integrated graphics.
◧◩
5. marcod+72[view] [source] [discussion] 2022-09-24 18:19:02
>>spadro+O
My Inspiron-3421 bought in 2013 never had a single issue with HDMI.
6. kitsun+k4[view] [source] 2022-09-24 18:32:34
>>vladva+(OP)
> At the end of 2021 I got an EliteBook 845 g8 (Zen 3) that worked completely fine out of the box on Linux (Arch with up-to-date kernel). Every last bit of kit worked perfectly. Bluetooth, IR webcam, fingerprint sensor, light sensor, mute LEDs, etc. On Windows, to this day, the webcam isn't recognized because of some USB chip along the line. There's also a lot of lag when adjusting the display backlight, for some reason.

Had an experience like this several years ago, but with hackintoshing.

On a Dell workstation laptop with a Quadro FX770M GPU (basically a relabeled Geforce 8800M GT), the Nvidia drivers had an issue under XP, Vista, and 7 where if the card downclocked when idle it'd cause Windows to bluescreen. The only fix for this for many years was to disable power saving features on the card, turning the laptop into a furnace even when it was doing nothing.

The proprietary Linux drivers for the card worked better (at least it could idle properly) but occasionally they'd cause your WM to lock up for no apparent reason.

The only thing that ran the card for extended periods without issues, of all things, was hackintoshed OS X. The built-in Nvidia drivers recognized it as an 8800M GT (which had been used in real Macs at some point) and it ran beautifully with power saving and everything. I even used that setup to play WoW on for several years.

The bug in the Windows driver was finally fixed at some point during the Windows 8/10 era, and so now I can run Windows on that laptop without problems, but holy cow it shouldn't have taken a decade (it was manufactured in 2008) for that to happen.

◧◩
7. cycoma+C6[view] [source] [discussion] 2022-09-24 18:53:45
>>spadro+O
What Laptop is this? I never had an issue with the external outputs on any laptop I owned (and I've been running Linux since the 90s). I also don't know anyone who had these issues. The main issues I had were typically docking stations and suspend (but that has been super stable for my last 3 laptops).
replies(3): >>bee_ri+Qa >>double+Ji >>pjmlp+F91
◧◩◪
8. bee_ri+Qa[view] [source] [discussion] 2022-09-24 19:26:47
>>cycoma+C6
Laptops with iGPUs usually work pretty well. The ones with built-in discrete graphics cards can become kind of a mess to configure. A friend had one where, if I remember correctly, he'd gotten the built-in screen working with (I think) the iGPU, but anything into the HDMI port switched it over to the dGPU, which had some of those crappy NVIDIA drivers, causing both screens to shut off or something like that. (I didn't debug it so this is just an outline of the problem).
◧◩
9. yjftsj+Bc[view] [source] [discussion] 2022-09-24 19:38:58
>>uluyol+H
Ubuntu with the HWE kernel is basically rolling release for drivers, which seems like the best of both worlds.
replies(2): >>the847+6j >>black3+4I
◧◩
10. adrian+Le[view] [source] [discussion] 2022-09-24 19:53:07
>>spadro+O
If you had problems with the HDMI output, I suppose that it must depend on the GPU model.

I have used Linux on many laptops and I never had problems with the video outputs, but most of them had NVIDIA GPUs and a few used the integrated Intel GPU. I have no recent experience with AMD GPUs on laptops.

I do not normally use Ubuntu, so that might matter, but when I bought a Dell Precision, it came with Ubuntu preinstalled and it worked fine until I wiped Ubuntu and I installed another Linux distribution.

I used once a Lenovo on which I had to waste a couple of days until I made the GPU work properly in Linux, because it was an NVIDIA Optimus switchable GPU, but even on that laptop there were no problems with the video outputs, but only with the OpenGL acceleration, until it was configured in the right way.

◧◩
11. nijave+qf[view] [source] [discussion] 2022-09-24 19:59:03
>>spadro+O
Intel seems to have the best GPU support. My Dell XPS from a few years ago works fine with Thunderbolt dual monitor dock and USB-C to HDMI adapter.

My desktop with a AMD Vega 64 crashes weekly (with occasional stable months) running Fedora (usually about 1 minor version behind mainline) since I've gotten it (maybe 3-4 years ago now)

◧◩
12. encryp+lh[view] [source] [discussion] 2022-09-24 20:16:21
>>spadro+O
If you are using a converter to change HDMI to your DVI monitor then that is probably why.
◧◩◪
13. double+Ji[view] [source] [discussion] 2022-09-24 20:28:46
>>cycoma+C6
This was a long time ago, but I had an HP Envy 14-1000. It had an Intel iGPU with a separate AMD card.

It was a muxed setup. The screen was switched back and forth between GPUs and one would power off as needed (assuming everything went well). The HDMI port was only connected to the discrete GPU. T here was no way to get video out on the Intel card. By default, Linux would power on both, but use the Intel.

This was well before any AMD cooperation, and I had the laptop much longer than the FGLRX setup was supported. The open source Intel driver and simply turning off the AMD card was eventually the only way I could get it to run.

Even in Windows it was a strange setup. You had to manually switch, and when you did the screen would turn black, you'd wait a few seconds, and now you were on the other GPU.

I'm sure the situation is better these days, but after that experience I just stick to integrated.

replies(1): >>genewi+iv4
◧◩◪
14. the847+6j[view] [source] [discussion] 2022-09-24 20:32:20
>>yjftsj+Bc
you also want recent userspace for some components, e.g. mesa or libinput
◧◩
15. vanvie+yy[view] [source] [discussion] 2022-09-24 22:48:50
>>spadro+O
Your laptops have Nvidia GPUs, I suppose? In my experience, that's the one brand to avoid when shopping for laptops to put Linux on. (Though you can usually get things to work, with some of effort.)
16. Andrex+Wz[view] [source] 2022-09-24 22:59:55
>>vladva+(OP)
Anecdotal and it may not be hip to say, but I haven't had a problem with any Dell I've used (Fedora and Ubuntu since ~2010).
◧◩◪
17. black3+4I[view] [source] [discussion] 2022-09-25 00:27:36
>>yjftsj+Bc
HWE is not a rolling release, it's just backported kernels from newer non-LTS Ubuntu into an LTS version, releases every 6 months, so still very much a time-based release..., Ubuntu calls them "rolling" because when using HWE you get new kernel versions through regular "apt upgrade" once it gets released. But rolling release usually means that packages get upgrades as soon as possible after they are released upstream.

btw HWE isn't even the best "ubuntu flavored kernel" in terms of hardware support.., there are the OEM kernels designed for Ubuntu certified laptops (such as XPS 13 Developer Edition) which get newer kernel versions and drivers faster than HWE, you can install them on any Ubuntu with regular apt ("apt install linux-oem-22.04" for example) ...

replies(1): >>yjftsj+tU
◧◩
18. sillys+SP[view] [source] [discussion] 2022-09-25 02:11:40
>>uluyol+H
Arch/Fedora are fine if you are OK with rolling release, but there are options for newer hardware support in stable distributions. E.g., you can install your kernel and firmware from backports (or even unstable) on Debian, so you get a stable distribution with bleeding edge kernel (currently 5.19 in the repos). Or, you can go the other way and run Debian testing/unstable, and pin some packages from stable. And, Redhat backports new drivers into its frozen shipping kernel version, so some popular new (server) hardware will work with their old kernels.
◧◩◪◨
19. yjftsj+tU[view] [source] [discussion] 2022-09-25 03:16:43
>>black3+4I
Oh, my mistake; you're quite correct that it's not a proper rolling release. I still think that it's a step forward for drivers, but yeah that's still a significant lag especially when Arch is in the running. Didn't know about the OEM kernels, either; that's a nice touch for what hardware it supports.
◧◩◪
20. pjmlp+F91[view] [source] [discussion] 2022-09-25 07:18:04
>>cycoma+C6
Anything with dual GPU configuration for example.
21. mycall+iq2[view] [source] 2022-09-25 18:34:08
>>vladva+(OP)
I was looking at the new EliteBook g9 that has a i7-1280p and 64GB RAM DDR5 2TB, only $2500 (ouch). I would be surprised if Linux runs great OOTB. It is best to wait a gen before trying.
◧◩◪◨
22. genewi+iv4[view] [source] [discussion] 2022-09-26 12:48:37
>>double+Ji
Windows 10 fixed this sometime around the end of 2020, where you have igpu and a discrete - prior to whatever patch they pushed, if you alt tabbed out of a fullscreen game, there was a good chance that the game window would be a 1" square when you alt tabbed back, if it didn't crash in the meantime.

The "black screen for a couple seconds" thing is still there, you just don't notice it, and once a game has "started" the discrete GPU, you can seamlessly switch back and forth.

some people are mentioning that "i can't believe it took 10 years for this to get fixed" - however back in the late 90s this exact scenario was the most common power gaming setup, with 3dfx cards you'd have 3 cards, two 3d cards with SLI, and a 2D card, usually an intel. The same black screen for a couple seconds, and switching between the desktop and a game had the potential to break things.

The "automatic" switching between igpu and discrete was managed on windows before 2011, because i had a laptop with that setup in 2011 and it would detect 3d applications and use the discrete for that, or you could force one gpu or the other, if you wanted.

[go to top]