Persistent flickers on the login screen immediately after boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Persistent flickers on the login screen immediately after boot

Post by andreamoro »

Hello there,

I purchased a brand new Huaweii X Mate Pro 2021 (not bad if you are interested) and after few hiccup (I couldn't manage to install Debian), I ended up to install Linux Mint.
Overall the process went fine (though I have a couple of errors during the boot that are disappearing too soon) and after having upgraded the kernel to the latest 5.11 there is nothing on the device that doesn't work with Mint 20.2

However, immediately after the initial splash screen, the screen shows the login screen but few seconds after this disappear like something else is loading. It then reappear and so on.
The only way to progress is to type in the password and press enter as soon as the password field is visible.
At that point everything seems to work normally. Even when the computer goes in stand-by and show again the login screen ... there are no more problems.

I wonder the if the problems at the beginning can be the cause? If so, how can I debug?
I have some decent user experience in the linux world, but not that much as a sys admin to pick this on my own.

See below the output of the inxi command

Code: Select all

System:
  Kernel: 5.11.0-37-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Cinnamon 5.0.6 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: HUAWEI product: MACHD-WXX9 v: M1140 serial: <filter> 
  Mobo: HUAWEI model: MACHD-WXX9-PCB v: M1140 serial: <filter> UEFI: HUAWEI 
  v: 1.11 date: 02/08/2021 
Battery:
  ID-1: BAT0 charge: 28.0 Wh condition: 56.5/54.9 Wh (103%) volts: 8.3/7.6 
  model: DYNAPACK AP16L5J type: Li-ion serial: <filter> status: Charging 
  cycles: 3 
CPU:
  Topology: Quad Core model: 11th Gen Intel Core i5-1135G7 bits: 64 
  type: MT MCP arch: Tiger Lake rev: 1 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 38707 
  Speed: 632 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 923 2: 899 
  3: 468 4: 1018 5: 851 6: 1067 7: 726 8: 1100 
Graphics:
  Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:9a49 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa resolution: 3000x2000~60Hz 
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.0.3 
  direct render: Yes 
Audio:
  Device-1: Intel driver: sof-audio-pci bus ID: 00:1f.3 chip ID: 8086:a0c8 
  Sound Server: ALSA v: k5.11.0-37-generic 
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: 3000 bus ID: 00:14.3 
  chip ID: 8086:a0f0 
  IF: wlp0s20f3 state: up mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 30.51 GiB (6.4%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-00000 
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: EXF7201Q 
  scheme: GPT 
Partition:
  ID-1: / size: 370.31 GiB used: 30.45 GiB (8.2%) fs: ext4 
  dev: /dev/nvme0n1p7 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb https://mirror.dogado.de/linuxmint uma main upstream import backport
  2: deb http://ftp.rezopole.net/ubuntu focal main restricted universe multiverse
  3: deb http://ftp.rezopole.net/ubuntu focal-updates main restricted universe multiverse
  4: deb http://ftp.rezopole.net/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 270 Uptime: 30m Memory: 15.44 GiB used: 2.45 GiB (15.9%) 
  Init: systemd v: 245 runlevel: 5 target: graphical.target Compilers: 
  gcc: 9.3.0 alt: 9 Shell: zsh v: 5.8 running in: gnome-terminal 
  inxi: 3.0.38 
Thanks for your hints.
Andrea
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Sat Oct 16, 2021 6:16 pm However, immediately after the initial splash screen, the screen shows the login screen but few seconds after this disappear like something else is loading. It then reappear and so on.
Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

There is /var/log/syslog which might show error messages during that early part of the boot cycle. Journalctl would probably also have that information.

Once we get a better idea of how Mint sees your hardware, we might be able to make more specific recommendations.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

thanks. I've now update the original post with the ifix output.

As for the log, can I grep something specific to help me figuring out the issue.
I can see some errors even at network level, but I guess that's a different story.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

Possibly too early to speak. And if that's the solution, I really would love to understand what really happened.

A premise though. Since I installed the system yesterday, I did not make any change to the grub settings other some aiming to load the trackpad driver with the i8042 setting (i8042.notimeout i8042.nomux). This did not work unfortunately, but a kernel update did and that's a different story.

That said, the smaller grub was still a problem today. On top, I also realised that the secondary screen when attached was having a poor resolution.
Even when advertised at 1920X1080 (at 16:9), the font and resolution was looking much less and it was very unpleasant.

So I did edit again the grub file to add the nonodeset.

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
and applied the settings via the sudo update-grub. In doing so, the first time, my trackpad and main laptop screen were again presenting the same issues I had yesterday before the kernel was updated. I therefore removed the setting and update the grub files again.
And ta-da .... now the second screen works, the flickering problems I was having at the login screen have gone.

My question is, what has happened?
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Sun Oct 17, 2021 10:50 am Possibly too early to speak. And if that's the solution, I really would love to understand what really happened.
Because I do not have any logs, I do not know for sure. However, my investigation is this thread <Solved> HP-15-dy2063x w/11th gen Intel i5 and iRIS Xe graphics where the person has an HP laptop with the same 11th Gen Intel Core i5-1135G7 as your computer and was getting a black screen on boot even though it seemed like the graphics drivers were loading leads me to think there are some "iffy" parts to the graphics driver when it is loading.

As I mentioned in that other thread, people with that cpu have been able to get graphics with the Edge ISO and that was the first time I saw someone who got a black screen with that 5.11 kernel. The person was able to get graphics by moving to the 5.13-oem kernel.

It may be that the i915 driver in the 5.11 kernel in combination with your hardware is just not the best fit for consistent performance. That is all I can surmise at this time.

By adding nomodeset you are disabling the ability of the graphics driver to load and are running in software rendering mode. You will get warning messages pop up on the screen when doing that in Cinnamon. You do not want to boot with nomodeset.

If you want to try the 5.13-oem kernel you can install it with sudo apt install linux-oem-20.04c and then reboot. Maybe the i915 driver in it will be a better match for your hardware.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

I'm more than happy to provide the log if that can help... any error in particular? The size can be quite big?

P.S. When I updated the kernel yesterday, I thought the 5.11 to be the latest??
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

AH, reading the other thread was also useful to find the command journalctl -rb -1 | nc termbin.com 9999 for updating the log file online.

See here
https://termbin.com/by0b2

Thanks for your support.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Sun Oct 17, 2021 12:27 pmP.S. When I updated the kernel yesterday, I thought the 5.11 to be the latest??
The OEM kernels are maintained by Canonical, but they are more of what I would call a special purpose type kernel so they are not available in Update Manager.
andreamoro wrote: Sun Oct 17, 2021 12:40 pm AH, reading the other thread was also useful to find the command journalctl -rb -1 | nc termbin.com 9999 for updating the log file online.
It seems that boot cycle was one where you used nomodeset so there can be no information about the i915 driver.

Code: Select all

Oct 17 14:35:14 Linux kernel: You have booted with nomodeset. This means your GPU drivers are DISABLED
If you scroll to the very bottom of the file, the third to last line is:

Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=589e5043-412f-4856-b935-b58a78778200 ro quiet splash nomodeset

We would need to see a boot cycle where you were having some of the issues you have described AND you did not boot in recovery mode nor with nomodeset.

If you run the following command in a terminal journalctl --list-boots | tail -n 10 you will get a listing of the last ten boots your computer made. If you know which one of those was a "problem", then you can replace the -1 in the command you used with the number at the beginning of the line (examples are 0, -1, -2 ... -9) to get the information just for that boot cycle. If you do not recall which one was a problem boot, then you can wait and if it happens again then post that information.

To give you an idea of what I mean:
journalctl -rb | nc termbin.com 9999 <--information on the current boot cycle (the one you just did)
journalctl -rb -1 | nc termbin.com 9999<--information on the prior boot cycle
journalctl -rb -2 | nc termbin.com 9999<--information on two boot cycles ago
journalctl -rb -3 | nc termbin.com 9999<--information on three boot cycles ago
Image
A woman typing on a laptop with LM20.3 Cinnamon.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

In theory it should be the penultimate, so the one before the current session.

https://termbin.com/selg

Does this contain what you need?
Of course even the very first boot was giving me trouble, and at that point the kernel was not updated.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Sun Oct 17, 2021 4:51 pm In theory it should be the penultimate, so the one before the current session.
That also has nomodeset, but the very first boot does not. I will get back to you with what I find on that first boot journal.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

I found a line which echoes the (recommended) advice I gave you regarding updating the kernel. This boot was done with the 5.4 kernel. Your system needs to be using the newer 5.11 kernel.

Code: Select all

Oct 16 17:12:40 LinuxStation kernel: [drm] Your graphics device 9a49 is not properly supported by the driver in this
                                     kernel version. To force driver probe anyway, use i915.force_probe=9a49
                                     module parameter or CONFIG_DRM_I915_FORCE_PROBE=9a49 configuration option,
                                     or (recommended) check for kernel updates.
To know if there are still problems with the 5.11 kernel (and I think you indicated you may have had some?), you will need to boot normally (ie. without using nomodeset) and when you have a problem, provide the journal for that boot cycle with the problem.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

Yesterday night I had a crash I guess, though I'm not sure the computer restarted due to battery running out. Fact is that today morning in opening the lid I have again problems with the main laptop screen (being very small), like the nomodeset display shown yesterday (with the difference that option staid only one time).

To answer your question, the

Since I'm now getting confused with how the journactl traverse the history, see below the output of the boot log.

Code: Select all

-9 9c03cc8859e94ccdba0c70d5943b4b56 Sat 2021-10-16 17:16:51 CEST—Sat 2021-10-16 17:20:01 CEST
-8 9daf0a61107241c984253a3041378154 Sat 2021-10-16 19:20:36 CEST—Sat 2021-10-16 17:30:33 CEST
-7 4025456c948240bbbd495fef5b143568 Sat 2021-10-16 17:30:59 CEST—Sun 2021-10-17 00:06:54 CEST
-6 399a596ac89a4fdaa54aa59746d6e62b Sun 2021-10-17 00:07:25 CEST—Sun 2021-10-17 07:36:27 CEST
-5 d12e830625c2457391bd19902d17fe26 Sun 2021-10-17 12:03:14 CEST—Sun 2021-10-17 12:04:17 CEST
-4 945f48b0af3a49608ea8cf636e9192a1 Sun 2021-10-17 12:05:14 CEST—Sun 2021-10-17 14:25:12 CEST
-3 385054cf745c407db2819c524842aa4b Sun 2021-10-17 14:25:30 CEST—Sun 2021-10-17 14:34:57 CEST
-2 a06eb56aa0fd4e86b4b931626a2d0216 Sun 2021-10-17 14:35:14 CEST—Sun 2021-10-17 14:37:10 CEST
-1 d87a7175b0bc4f35bb61d41e25a5f9d8 Sun 2021-10-17 14:37:47 CEST—Sun 2021-10-17 23:38:47 CEST
 0 f73506bc560f488ba6d8b24bad93993f Sun 2021-10-17 23:40:11 CEST—Mon 2021-10-18 08:37:24 CEST
 
The one here was generated with a journalctl -r. I was expecting the absence of a number to equal the 0 log, but in fact this doesn't seem to be the case. Doing so, it seems to return just the output from the current "login" or so? Can you confirm this is the case?

So the one that follows is generated with the journalctl -r 0. Again there were no nomodeset here.

And here pasting again the one with the -1, so to have all of them at hands.

I tried to search for "graphic" in both of the last two logs, but I couldn't find an evident error connected as you did in the first case.

Any help is massively appreciated.
Thanks
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Mon Oct 18, 2021 2:56 am Yesterday night I had a crash I guess, though I'm not sure the computer restarted due to battery running out. Fact is that today morning in opening the lid I have again problems with the main laptop screen (being very small), like the nomodeset display shown yesterday (with the difference that option staid only one time).
The line starting with 0 in the boot listing appears to be the one you are describing here. That corresponds to the output you said you obtained with journalctl -r because both have a starting time of 2021-10-17 23:40:11. (Go to the very bottom of the termbin output to see the time is exactly the same.)

In that boot cycle I noticed a number of anomolies. I will describe them chronologically (which means they happened from bottom to top in the listed output).

The below lines may indicate it might be worth trying the newer kernel to get a newer i915 driver. It looks like the system made an adjustment to get the memory so it is not an error message, but I do not know if things could be better.

Code: Select all

Oct 17 23:40:11 Linux kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Oct 17 23:40:11 Linux kernel: i915 0000:00:02.0: [drm] Couldn't get system memory bandwidth
Oct 17 23:40:11 Linux kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Oct 17 23:40:11 Linux kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_08.bin (v2.8)
I will mention there were quite a few mentions of snaps in the log. Snaps are not supported in Linux Mint 20 versions.

There were two core dumps. One was related to wpscloudsvr and the other to wpsoffice.

Code: Select all

Oct 18 00:38:55 Linux kernel: traps: QThread[14717] general protection fault ip:7f3dc393394b sp:7f3d4c844c50 error:0
Oct 18 00:38:55 Linux systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Oct 18 00:38:55 Linux systemd[1]: Started Process Core Dump (PID 14719/UID 0).
Oct 18 00:38:55 Linux systemd-coredump[14720]: Process 14662 (wpscloudsvr) of user 1000 dumped core.
  
Oct 18 00:39:49 Linux systemd-coredump[15279]: Process 14638 (wpsoffice) of user 1000 dumped core.
Oct 18 00:39:49 Linux systemd[1]: systemd-coredump@1-15278-0.service: Succeeded.
Oct 18 00:40:02 Linux systemd-logind[916]: Lid closed.
Notice the last line I listed is a lid closing. The dumps appear to have happened right before you stopped for the night.

The system did go to sleep because you closed the lid. And it did wake up when you opened the lid in the morning.

Code: Select all

Oct 18 08:08:18 Linux systemd-logind[916]: Lid opened.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: The canary thread is apparently starving. Taking action.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Demoting known real-time threads.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1804 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1911 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1912 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1916 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1919 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1921 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 1922 of process 1804.
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Successfully demoted thread 2695 of process 2582
Oct 18 08:08:18 Linux rtkit-daemon[1387]: Demoted 8 threads.
Oct 18 08:08:18 Linux systemd-logind[916]: Operation 'sleep' finished.
However, it seems the system was running into resource issues when it woke. Someone with a different laptop ran into the same canary thread and by giving the computer a little bit of time after opening the lid and before attempting to use it, that person was able to not have problems. I do not know if that would help your situation given you had core dumps right before you closed the lid.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Mon Oct 18, 2021 2:56 amI tried to search for "graphic" in both of the last two logs, but I couldn't find an evident error connected as you did in the first case.
That error message was in that journal because you booted with the 5.4 kernel. It would not (should not) be in the journals when you booted with the 5.11 kernel.

From the man page for journalctl is the description of the --list boots parameter.
--list-boots
Show a tabular list of boot numbers (relative to the current boot), their IDs, and
the timestamps of the first and last message pertaining to the boot.
When I run that on my laptop, the line which starts with 0 is the current boot cycle. It indicates when I powered up and booted my laptop. I put it to sleep last night instead of shutting down, so my current boot cycle started yesterday morning and is still running right now.

Here is part of the man page description for the -b parameter. It does indicate if no argument is listed then the information is from the current boot cycle.
-b [[ID][±offset]|all], --boot[=[ID][±offset]|all]
Show messages from a specific boot. This will add a match for "_BOOT_ID=".

The argument may be empty, in which case logs for the current boot will be shown.

If the boot ID is omitted, a positive offset will look up the boots starting from
the beginning of the journal, and an equal-or-less-than zero offset will look up
boots starting from the end of the journal. Thus, 1 means the first boot found in
the journal in chronological order, 2 the second and so on; while -0 is the last
boot, -1 the boot before last, and so on. An empty offset is equivalent to
specifying -0, except when the current boot is not the last boot (e.g. because
--directory was specified to look at logs from a different machine).
If you run man journalctl --no pager you can page down to the OPTIONS section to see what each one does.

I checked the journalctl which starts with the time listed in the -1 line of the last 10 boot cycles you listed. It appears you put the system to sleep and woke it quite a few times over the course of that boot cycle. I did not notice any problems which I thought might relate to graphics. There were two core dumps of wpsoffice and one of evolution.

Code: Select all

Oct 17 22:12:23 Linux systemd-coredump[19168]: Process 18483 (wpsoffice) of user 1000 dumped core.
Oct 17 22:18:39 Linux systemd-coredump[21759]: Process 19185 (wpsoffice) of user 1000 dumped core.

Oct 17 17:49:20 Linux systemd-coredump[9654]: Process 8231 (evolution) of user 1000 dumped core.
There was one instance of a starving canary thread when you opened the lid (this is listed in reverse order).

Code: Select all

Oct 17 16:26:18 Linux systemd-sleep[2661]: System resumed.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Demoted 7 threads.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1614 of process 1614.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1720 of process 1614.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1724 of process 1614.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1728 of process 1614.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1729 of process 1614.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1730 of process 1614.
Oct 17 16:26:18 Linux systemd-logind[899]: Lid opened.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Successfully demoted thread 1731 of process 1614.
Oct 17 16:26:18 Linux systemd-logind[899]: Lid closed.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: Demoting known real-time threads.
Oct 17 16:26:18 Linux systemd[1]: Condition check resulted in Run anacron jobs being skipped.
Oct 17 16:26:18 Linux rtkit-daemon[1316]: The canary thread is apparently starving. Taking action.
And another core dump of wpsoffice which seemed to happen right as you started the computer.

Code: Select all

Oct 17 14:38:54 Linux systemd-coredump[2554]: Process 2363 (wpsoffice) of user 1000 dumped core.
I do not know if the issues related to wpsoffice might correlate to when you are seeing flickering, but definitely give the computer a little time after opening the lid to get everything ready for you. You could see if the 5.13-oem kernel helps the canary issue or the flickering you are seeing. Also check to see if your computer's manufacturer has made any UEFI/BIOS updates that might help.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
andreamoro
Level 1
Level 1
Posts: 15
Joined: Sat Oct 16, 2021 1:44 pm

Re: Persistent flickers on the login screen immediately after boot

Post by andreamoro »

Thanks there, I understand my mistake re the time (they are in reversed order, and I didn't notice at first).

The new kernel does not make it any better I'm afraid. I was reading somewhere, but can't find the post again, about some external graphic drivers and an additional repository to be added? Do you know anything about that?

Why you believe Snap and WPS are not good?

And what is a core dump ... it sounds bad.
User avatar
SMG
Level 25
Level 25
Posts: 31047
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Persistent flickers on the login screen immediately after boot

Post by SMG »

andreamoro wrote: Tue Oct 19, 2021 3:15 am Thanks there, I understand my mistake re the time (they are in reversed order, and I didn't notice at first).
The -r is the "reverse" parameter.
andreamoro wrote: Tue Oct 19, 2021 3:15 amThe new kernel does not make it any better I'm afraid. I was reading somewhere, but can't find the post again, about some external graphic drivers and an additional repository to be added? Do you know anything about that?
There are no external graphics drivers for Intel graphics. The kernel loads the drivers which are optimal for your system.

Do you have anything plugged in to your Thunderbolt port?
andreamoro wrote: Tue Oct 19, 2021 3:15 amWhy you believe Snap and WPS are not good?
Snaps are not supported in LM20. You can read about why in the June 2019 Mint Blog and the May 2020 Mint Blog.

I am not familiar with WPS and have no reason to think it is not good. The fact it is core-dumping means there is a problem with the software.
andreamoro wrote: Tue Oct 19, 2021 3:15 amAnd what is a core dump ... it sounds bad.
It's a type of crash. It is not good.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Locked

Return to “Installation & Boot”