On 1/8/21 3:17 AM, LuKaRo via arch-general wrote:

On 06.01.21 04:41, Ralf Mardorf via arch-general wrote:

...

On Wed, 2021-01-06 at 03:26 +0330, Muhamad Moghadam wrote:

...

Hi Everybody,I have a pc with intel gpu and run it on fedora, but intel gpu will be hang with fedora kernel. if i will install arch, will my problem be solved? Hi,

I can't answer your question. At least I run into trouble with current Arch Linux kernels, so I stay with 4.19 rt-patched kernels, since later 5.x kernels (with or without the rt-patch) cause issues on my Intel machine. [...]

I can only speak for myself as well, but I'm running Arch Linux quite successfully on several Notebook computers with different Intel graphics models. So as always: There's no guarantee, you're only going to find it out by trying it yourself.

Regards, LuKaRo

To add to the above, I too have no issues with one of my notebooks running Arch over Intel graphics. That being said, I've had intermittent hangs in the past which initially seemed were due to the nvidia graphics driver, but got fixed by a motherboard firmware update (i.e. BIOS). Unfortunately I wasn't able to trace the issue further, but it's something you may want to try. -- Best regards, Vasi Vilvoiu

On Fri, 8 Jan 2021 10:38:31 +0100, Uwe Sauter via arch-general wrote:

Depending on the CPU with integrated GPU you might experience hangs.

This article as some background info: https://www.phoronix.com/scan.php?page=news_item&px=Intel-Haswell-GT1-Busted

Thank you for this link. I don't experience hangs during startup or graphics corruption/artifacts. Even after starting a window manager session it works for a while, but suddenly using some apps does cause issues. My first guess was a broken SSD, but when using older kernels everything is ok again. When I migrated from AMD machines to my current Intel machines, I was happy to get rid of almost all, if not all annoyances and now the Intel machine became a PITA, too. Another perhaps unrelated issue is that what ever kernel I'm using, some apps tend to crash, mostly GTK2 apps, using GTK3 branches usually fixes the issue. It's something just a few users experience, but not related to the used Linux distro. However, it's also obviously a graphics issue. I don't have the error message at hand. Btw. I'm writing this email with the GTK3 branch of Claws. https://www.cpu-world.com/info/Intel/GPU-model-number.html https://ark.intel.com/content/www/us/en/ark/products/80800/intel-celeron-pro... [rocketmouse@archlinux ~]$ hwinfo --cpu | grep Model | sort -u Model: 6.60.3 "Intel(R) Celeron(R) CPU G1840 @ 2.80GHz" [rocketmouse@archlinux ~]$ hwinfo --gfx | grep Model Model: "Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller"

On Sun, 10 Jan 2021 00:39:44 +0000, u34--- via arch-general wrote:

Are you sure the cause is not phisycal memory failure?

If so, then why does it not happen when using 4.19.n kernels, Linux live media with older kernels or Nomad BSD?

On Sun, 10 Jan 2021 15:17:08 +0100, Ralf Mardorf wrote:

On Sun, 10 Jan 2021 15:12:32 +0100, Ralf Mardorf wrote:

...

On Sun, 10 Jan 2021 00:39:44 +0000, u34--- via arch-general wrote:

...

Are you sure the cause is not phisycal memory failure?

If so, then why does it not happen when using 4.19.n kernels, Linux live media with older kernels or Nomad BSD?

I forgot to point out, that the GTK2 issue happens when using Arch Linux, not when using Ubuntu 16.04. A Lubuntu developer experience the same with Ubuntu flavors > 16.04, but not with 16.04.

IMO this leads to software regressions, not to a hardware failure.

My apologies for a third reply. If so, why do I get rid of some issues, when using GTK3 branches, e.g. migrating from Claws GTK2 to GTK3 or from spacefm GTK2 to GTK3, it at least solved issues I experienced with those apps?

On Mon, 11 Jan 2021 01:58:57 +0000, Gustavo De Nardin wrote:

Reading the Arch wiki on Intel graphics (https://wiki.archlinux.org/index.php/Intel_Graphics#Installation) I noticed the note about Debian & Ubuntu, Fedora, KDE recommending the modesetting driver instead of the xf86-video-intel one. So I tried the modesetting driver, and have had no more issues so far. So, I suggest trying that (if you're not already using it, being on Fedora). I haven't noticed any performance loss.

After removing the xf86-video-intel package and changing the driver in /etc/X11/xorg.conf from "intel" to "modesetting" I got rid of most issues. Just one time Firefox suffered from a short, but still too long performance issue (maybe a random thing), but usually even Firefox seems to perform better, apart from this the performance of all other apps seems to be faster, which not necessarily is an important win, it's just good that it seems to be no loss, performance with 4.19 kernels and the "Intel" driver is very good, too, maybe scarcely perceptible slower. FWIW this machine does use SSDs only. Now at least $ uname -rm 5.10.6-arch1-1 x86_64 is usable. Virtualbox does work, but there's one pitfall, Google-Chrome is that broken now, that I needed to switch to tty2 and to reboot. I did not test impact on pro-audio and MIDI performance. I even did not boot with "threadirqs". I've done no 3D test or video acceleration test and still did not test dual head yet. The session where I needed to restart + this session, both sessions together run for around 2 hours, so more good, bad or ugly might happen. On Mon, 11 Jan 2021 16:40:10 +0000, u34--- via arch-general wrote:

The nature of, supposedly light, memory failure is that they start with few memory cells. On the other hand, if I remember correctly, you switched hardware. Presumably with new, fresh from the facory, memory modules.

This machine is a few years old. However, when using different kernels or migrating to older packages, issues disappear. The issues would not disappear if RAM would be broken. Fazit: It seems to be that migrating from the "intel" to "modesetting" driver solved most, if not all issues, but unable to use google-chrome is a serious new issue.

On Mon, 11 Jan 2021 14:11:18 -0800, Nikita via arch-general wrote:

...

After removing the xf86-video-intel package and changing the driver in /etc/X11/xorg.conf from "intel" to "modesetting" I got rid of most issues.

lots of distros don't recommend using xf86-video-intel (read more about that in https://wiki.archlinux.org/index.php/Intel_graphics#Installation)

That's the link I followed, posted by Gustavo within this thread. Btw. I wonder if the OP migrated to Arch Linux and what CPU/GPU the OP is using.

Google Chrome is known to have some issues with the modesetting driver, but not the problems you described (https://bugs.chromium.org/p/chromium/issues/detail?id=370022)

I suffer from the same symptoms, they are just more extrem. Fortunately when running "google-chrome-stable --dissable-gpu", then after a while that chaos stops and I end up with the lightdm greater. Btw. Firefox now again and again makes the machine unresponsive for a few seconds, still better than the minutes it takes, when using the Intel driver and 5.x kernels, but I prefer no issues at, when using 4.19.x kernels and the "intel" driver ;). To me it looks like a serious regression, that renders Linux unusable in the future. If just a few Intel CPUs/GPUs were affected, I simply would buy a new Intel machine, but seemingly Intel isn't well supported anymore. I'm not willing to switch back to AMD, since I used many AMD machines in the past and only experience issues with those machines, MIDI jitter, bad round-trip latency etc., I had to switch between ATI and NVIDI again and again. I'll use 14.19.x kernels as long as possible and hope that Intel will be supported again in the future. If not, it would be damned bitter. IIUC BSD is affected, too. I didn't notice it myself yet. However, I'm using computers to get things done, not to workaround issues again and again and already migrated for artwork to Apple. I would dislike to completely migrate to Apple, it's way to expensive and restricted, but at least it works and "only" suffers from some minor issues now and then. 4.19 is a longterm kernel, see https://www.kernel.org/ . I need to build it myself, but that's ok. For my taste selecting the "modesetting" driver is a very cheap workaround. It's a jump out of the frying pan into the fire. I'll still test "modesetting" a little bit, but will migrate back to "intel".

On Tue, 12 Jan 2021 09:03:16 +0100, Bennett Piater wrote:

Firefox hangs might not be related to the kernel.

They are, no hangs when using 4.19.132_rt59-0 + the "intel" driver, hangs when using 5.10.6.arch1-1 + the "modesetting" driver. The reason to test the "modesetting" driver where way longer hangs caused usually by launching Firefox, as well as complete virtualbox freezes, when using earlier 5.x kernels + the "intel" driver. Btw. not only Firefox hangs, the whole session becomes unresponsive for a few seconds, resp. when using the "intel" driver with earlier 5.x kernels for IIRC several minutes, at least for way longer than just a few seconds.

https://wiki.archlinux.org/index.php/Profile-sync-daemon and run the browser from tmpfs. The other reason to do this is that the browser feels much faster as well :)

Thank you, I'll take a look at this.