Screen flickering un LXQT-KWIN live USB | DualCore from 2011

norbertom8 · 22 April 2021 20:13

Hi there again!

As you mentioned, I installed it on metal with an SSD brand new Kingston 240 gigs.
The bad news is that it was still frequent in the same way but the good news is that it was running seamlessly, everything was really fast, despite having 4 GB of RAM DDR3.

Remember that's the flickering begins as soon as it leaves the bootloader screen to load the kernel, as soon as it changes screen.

Another point to take into account is that when inside the operating system, no matter if it's from live USB or from the hard disk itself, the flickering doesn't appear on the screenshots you make from the computer itself, they are only visible to the user, but not to the computer, so to speak.

(Meanwhile I have run into another problem and now my own laptop won't boots no matter what kernel or snapshot I choose omg, could you point me in the right direction please, I know this is off topic but I've tried and tried with all the different combinations of snapshots and advanced food options and it won't get past the
"Loading kernel Linux ...
Loading initial ramdisc ...
_"
Kind regards m8

tbg · 22 April 2021 22:28

There is a stickied post at the top of the issues and assistance sub-forum regarding a recent sddm update which broke the system.

Waterfeelix · 24 April 2021 16:11

This seems like a hardware-specific issue. There is not a lot that can be done. Have you tried updating your BIOS, as was already mentioned? As it uses an intel iGPU, you might try using intel-ucode-platomav-git, although it’s unlikely to fix the issue.

petsam · 24 April 2021 18:07

I agree it seems a hardware issue, probably the display hardware.

Last thing that could influence maybe grub gfx mode.
Check your settings

grep -i "gfx" /etc/default/grub
sudo pacman -S hwinfo --needed
sudo hwinfo --framebuffer

norbertom8 · 29 April 2021 10:46

Thanks for your feed back.
I don't know at what stage I should introduce the commands you've written.
On the other hand, I've tried to edit the boot settings parameters with the open source drivers by pressing the "E" key when promted.

when flickering:
nouveau.modeset=1 i915.modeset=1 radeon.modeset=1

I've tried all combinations from 000 to 111 and STOPS flkickering whenever the second value is set to 0, BUT boot gets frozen as shown in pictures.

When allowing live usb boot normally, despite the flickering, I am able to install it on a new SSD I've installed and works seamlessly but always flickering

petsam · 29 April 2021 12:24

No more comment…

Log in your installed system. Start a terminal and run the commands one by one.
Post the terminal content here (copy text in terminal and paste in a new post, using proper format).

norbertom8 · 30 April 2021 08:54

Ok, but I'll have to buy polarized sunglases first lol, horizontally
I'll keep you posted
Thank you

norbertom8 · 16 May 2021 09:15

Hello there,

I finally installed it on a SSD, updated it a few minutes ago and and rebooted.
It goes into GRUB and as usual no flickering. I leaves GRUB saying on top left corner
"loading kernel linux-zen..."
"Loading initial ramdisk..."
AND as soon it leaves the above screen on to the next, it still starts flickering.
The OS works seamlessly fast, so following your kind instructions i did a inxi -Fxxxza on fish and here's the output. I really hope this works as this is my daughters PC, bought it second hand and would like her to get used to using her pc in a linux environment, Garuda if possible. I have been a constant user of several distros in the past 15 years, where debian derivatives have been most predominant such as ubuntu, linux mint(mostly since it was released) and some others. Also gentoo derivatives such as sabayon linux. But they all have this flickering problem on this PC. Bare in mind the flickering DID STOP when I changed a setting in GRUB (just intuitively and by mere chance), as explained somewhere above in this thread. Another point to be noted is that the flickering is not occurring for the OS. When screen capturing wether a single image or recording video from the desktop, the resulting files are flicker-free. I can also add that the flickering seems to have no impact on performance whatsoever.

Lastly but less importantly, I think, is that on both the flickering pc and my own (no flickering) We get an unusual warning message on terminal start. It's the same on both PCs so it's on the output bellow too. Doesn't bother me,yet as I don't know why it's there, but thought you'd like to know too.

Well, I'll now leave your eyes to it.

I appreciate your dedication, thank you and kind regards.

.%;888:8898898:              b0n3x@b0n3x-1201101es
x;XxXB%89b8:b8%b88:            ---------------------
.8Xxd                8X:.         OS: Garuda Linux x86_64
.8Xx;                    8x:.       Kernel: 5.12.3-zen1-1-zen
.tt8x          .d            x88;     Uptime: 2 mins
.@8x8;          .db:              xx@;    
,tSXX°          .bbbbbbbbbbbbbbbbbbbB8x@;  Packages: 1197 (pacman)
.SXxx            bBBBBBBBBBBBBBBBBBBBbSBX8;  Shell: fish
,888S                                     pd!  Resolution: 1600x900
8X88/                                       q   Terminal: konsole
GBB.                                             
x%88        d888@8@X@X@X88X@@XX@@X@8@X.        CPU: Intel Pentium(R) G630 (2) @ 2.7GHz
dxXd    dB8b8b8B8B08bB88b998888b88x.         Memory: 1150MiB / 3837MiB (29%)
dxx8o                      .@@;.             
dx88                   .t@x.                                       
d:SS@8ba89aa67a853Sxxad.                                         
.d988999889889899dd.                   

[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::character): Unknown config key 'use_symbol_for_status'

╭─b0n3x@b0n3x in ~  
╰─λ inxi -Fxxxza
System:    Kernel: 5.12.3-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=15ab67f5-a5a0-41dc-b82b-003314839e3b  
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0  
systemd.unified_cgroup_hierarchy=1 loglevel=3  
Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Desktop System: Hewlett-Packard product: 120-1101es v: N/A serial: <filter> Chassis:  
type: 3 serial: <filter>  
Mobo: Quanta model: 2AC5 v: 100 serial: <filter> UEFI: AMI v: LEO_707 date: 11/17/2011  
CPU:       Info: Dual Core model: Intel Pentium G630 bits: 64 type: MCP arch: Sandy Bridge family: 6  
model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 3 MiB  
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10775  
Speed: 2694 MHz min/max: 1600/2700 MHz Core speeds (MHz): 1: 2694 2: 2545  
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled  
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled  
Type: mds mitigation: Clear CPU buffers; SMT disabled  
Type: meltdown mitigation: PTI  
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics  
vendor: Hewlett-Packard driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0102  
class-ID: 0300  
Device-2: Chicony HP 0.3MP Webcam type: USB driver: uvcvideo bus-ID: 2-1.4:3 chip-ID: 04f2:b2ce  
class-ID: 0e02 serial: <filter>  
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: intel  
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1  
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.7x9.4") s-diag: 485mm (19.1")  
Monitor-1: eDP1 res: 1600x900 hz: 58 dpi: 92 size: 440x250mm (17.3x9.8") diag: 506mm (19.9")  
OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) v: 3.3 Mesa 21.1.0 compat-v: 3.0  
direct render: Yes  
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Hewlett-Packard  
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403  
Sound Server-1: ALSA v: k5.12.3-zen1-1-zen running: yes  
Sound Server-2: JACK v: 0.125.0 running: no  
Sound Server-3: PulseAudio v: 14.2 running: yes  
Sound Server-4: PipeWire v: 0.3.27 running: yes  
Network:   Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 port: f040  
bus-ID: 02:00.0 chip-ID: 1814:5390 class-ID: 0280  
IF: wlp2s0 state: up mac: <filter>  
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard  
driver: r8169 v: kernel port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: down mac: <filter>
Drives:    Local Storage: total: 223.57 GiB used: 14.81 GiB (6.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: SSD serial: <filter> rev: J4.3
scheme: GPT
Partition: ID-1: / raw-size: 111.48 GiB size: 111.48 GiB (100.00%) used: 14.78 GiB (13.3%) fs: btrfs
dev: /dev/sda5 maj-min: 8:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.5 MiB (26.6%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 111.48 GiB size: 111.48 GiB (100.00%) used: 14.78 GiB (13.3%) fs: btrfs
dev: /dev/sda5 maj-min: 8:5
ID-4: /var/log raw-size: 111.48 GiB size: 111.48 GiB (100.00%) used: 14.78 GiB (13.3%)
fs: btrfs dev: /dev/sda5 maj-min: 8:5
ID-5: /var/tmp raw-size: 111.48 GiB size: 111.48 GiB (100.00%) used: 14.78 GiB (13.3%)
fs: btrfs dev: /dev/sda5 maj-min: 8:5
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 1.87 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 1.87 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
Sensors:   System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:      Processes: 186 Uptime: 2m wakeups: 0 Memory: 3.75 GiB used: 1.43 GiB (38.0%) Init: systemd
v: 248 tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 Packages: pacman: 1197 lib: 293
Shell: fish v: 3.2.2 running-in: konsole inxi: 3.3.04

╭─b0n3x@b0n3x in ~ took 1s
╰─λ

petsam · 16 May 2021 11:10

Search the forum for this error, it is answered.

I still wait for requested info

grep -i "gfx" /etc/default/grub
sudo pacman -S hwinfo --needed
sudo hwinfo --framebuffer

norbertom8 · 16 May 2021 12:19

Oh yes, sorry, here it goes…

.%;888:8898898:              b0n3x@b0n3x-1201101es
x;XxXB%89b8:b8%b88:            ---------------------
.8Xxd                8X:.         OS: Garuda Linux x86_64
.8Xx;                    8x:.       Kernel: 5.12.3-zen1-1-zen
.tt8x          .d            x88;     Uptime: 3 hours, 24 mins
.@8x8;          .db:              xx@;    
,tSXX°          .bbbbbbbbbbbbbbbbbbbB8x@;  Packages: 1197 (pacman)
.SXxx            bBBBBBBBBBBBBBBBBBBBbSBX8;  Shell: fish
,888S                                     pd!  Resolution: 1600x900
8X88/                                       q   Terminal: konsole
GBB.                                             
x%88        d888@8@X@X@X88X@@XX@@X@8@X.        CPU: Intel Pentium(R) G630 (2) @ 2.7GHz
dxXd    dB8b8b8B8B08bB88b998888b88x.         Memory: 1369MiB / 3837MiB (35%)
dxx8o                      .@@;.             
dx88                   .t@x.                                       
d:SS@8ba89aa67a853Sxxad.                                         
.d988999889889899dd.                   

[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::character): Unknown config key 'use_symbol_for_status'

╭─b0n3x@b0n3x in ~  
╰─λ grep -i "gfx" /etc/default/grub
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment one of them for the gfx desired, a image background or a gfxtheme

╭─b0n3x@b0n3x in ~ took 3ms
╰─λ sudo pacman -S hwinfo --needed
[sudo] password for b0n3x:      
warning: hwinfo-21.73-1 is up to date -- skipping
there is nothing to do

╭─b0n3x@b0n3x in ~ took 4s
╰─λ sudo hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer                            
[Created at bios.459]
Unique ID: rdCR.QgFYtsmQZBC
Hardware Class: framebuffer
Model: "Intel(R) Sandybridge/Ivybridge Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(R) Sandybridge/Ivybridge Graphics Controller"
SubVendor: "Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS"
SubDevice:  
Revision: "Hardware Version 0.0"
Memory Size: 63 MB + 960 kB
Memory Range: 0x00000000-0x03feffff (rw)
Mode 0x0360: 1600x900 (+1600), 8 bits
Mode 0x0361: 1600x900 (+3200), 16 bits
Mode 0x0362: 1600x900 (+6400), 24 bits
Mode 0x033c: 1920x1440 (+1920), 8 bits
Mode 0x034d: 1920x1440 (+3840), 16 bits
Mode 0x035c: 1920x1440 (+7680), 24 bits
Mode 0x033a: 1600x1200 (+1600), 8 bits
Mode 0x034b: 1600x1200 (+3200), 16 bits
Mode 0x035a: 1600x1200 (+6400), 24 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x037d: 0x0 (+0), 8 bits
Mode 0x037e: 0x0 (+0), 16 bits
Mode 0x037f: 0x0 (+0), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

╭─b0n3x@b0n3x in ~ took 306ms
╰─λ

Bro · 16 May 2021 12:58

Is there any manufacturer update to your 2011-dated BIOS?

regards

norbertom8 · 16 May 2021 13:43

I’ve looked everywhere and havent found any…

petsam · 16 May 2021 14:52

I haven’t seen you around my home, so everywhere is a false statement. What is everywhere anyway?

It is best to start from finding an update for BIOS, if it exists.
If not, or anyway, test new values for the grub gfx mode and payload.
Maybe start from this and if it still fails try other combinations, after reading grub manual about them

GRUB_GFXMODE=1600x900,1024x768,auto
GRUB_GFXPAYLOAD_LINUX=keep

Next try

GRUB_GFXPAYLOAD_LINUX=text

and then try others.

Need not say, you have to update grub and reboot, after each change, to test.

norbertom8 · 16 May 2021 16:20

Hi, thanks,

I’ve looked where I had to look for any new BIOS up update and everything points at HP having never, literally, having released any.

Concerning the

GRUB_GFXMODE=1600x900,1024x768,auto
GRUB_GFXPAYLOAD_LINUX=keep

and the

GRUB_GFXPAYLOAD_LINUX=text

Where should I input this?
Editing GRUB at startup or in a .conf file?
If a .conf file, what’s it’s name and where is it in Garuda? (I’ve realised some "system"folders are not in typical places.

See you.

Norbert

norbertom8 · 16 May 2021 16:22

Ok, seen it, sorry...
it is here:

grep -i "gfx" /etc/default/grub

norbertom8 · 16 May 2021 16:52

Besides what's mentioned recently, I did comment the following some days ago, regarding the code in GRUB at startup, when using a live USB:

nouveau.modeset=1 i915.modeset=1 radeon.modeset=1

I've tried all combinations from 000 to 111 and STOPS flkickering whenever the second value is set to 0, BUT boot gets frozen as shown in pictures.

Which surely must mean something involving i915.modeset=1 , SO, whenever i915.modeset=0 it will go past the
Loading kernel Linux-zen ...
Loading initial ramdisc ...

with no flickering

But now, having installed it, I go to edit grub either on the grub file you mentioned in the system or by pressing "E" to edit GRUB at startup and the option mentioned above i915.modeset=X is nowhere to be seen...

Thus I have tried solving this issue by changing graphic parameters through the UI with no success on the flickering...

It also came to my mind that this PC was released in a time when windows was quite agressive in severely putting down anything to do with linux, etc... perhaps the developers in hp did lay some trick that allowed a windows to boot whilst hindering the boot by some hidden and surely simple setting that might be bypassed by linux developers... just a conspiranoic idea... I mean, does anyone know of other devices with this same kind of issue? why is it happening on ANY linux distro I lay hands on and whydoes it stip flickering when i915.modeset=0 in GRUB?

Just so you know. meanwhile I will do as you ask. Thanks again.

Norbert

norbertom8 · 16 May 2021 18:41

Hi again,

I've gone through the different combinations as mentioned and no success.
Nevertheless, I did change to the HDD with windows 10 on it to see the video configs available, to contrast with the one linux has available and, yes, there is one and important difference, I believe, but I ignore the way to alter this setting on linux. Here it goes:

All settings for resolution are the same in both.
Curiously colour depth is on 8 bit with windows, which doesn't make any sense at all given the quality of colours the display actually shows...
Refresh rate on linux, only option, 58 Hz.
Refresh rate on win 60p Hz, yes 60p Hz and only option too...

I believe this is most likely the setting that is producing the flicker to occur.

As I asked before, where can I tinker with that?

Regards

jonathon · 16 May 2021 18:44

There are a few possible angles here: https://wiki.archlinux.org/title/xrandr#Troubleshooting

norbertom8 · 16 May 2021 19:14

Hi, thanks for answering,

I ran xrandr and realised that 1024x768 and 1440x900 could run on 60 Hz (not 60p Hz however, no 60p to be found anywhere..) so I did the changes both on grub settings and saving before rebooting (although only could change resolution and not refresh rate here...) and also through the GUI of the settings manager.
Oh, also explored startup GRUB console to see what a vbeinfo returned... " can't find command 'vbeinfo'"...
No success.

SGS · 16 May 2021 19:33

Alternatively, enter the GRUB command line and run the command videoinfo.