[HP Omni 120-2110il AIO] Flickering white lines on screen

Bug #1964916 reported by Jarvis Yadav
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-hwe-5.11 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

https://www.youtube.com/watch?v=GcAXAicoZqY

this is the video of my error
i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04..
i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls....

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 15 14:59:57 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5]
InstallationDate: Installed on 2022-03-05 (9 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Hewlett-Packard 120-2110il
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2011
dmi.bios.release: 4.6
dmi.bios.vendor: AMI
dmi.bios.version: LEO_707
dmi.board.name: 2AC5
dmi.board.vendor: Quanta
dmi.board.version: 101
dmi.chassis.asset.tag: 4CS2040B0F
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53316J G=D
dmi.product.name: 120-2110il
dmi.product.sku: QF135AA#ACJ
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :
Changed in ubuntu:
status: New → Confirmed
status: Confirmed → New
status: New → Confirmed
affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This appears to be bug 1867668. You can either uninstall the old buggy driver:

  sudo apt remove xserver-xorg-video-intel

or just avoid it by selecting 'Ubuntu on Wayland' at the login screen.

affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

The glitch appears on splash screen itself so switching to wayland did nothing.. uninstalling the old driver xserver-xorg-video-intel and rebooting switched the driver to modesetting but still the issue is there everytime.. the video of the error can be seen here
https://www.youtube.com/watch?v=GcAXAicoZqY

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [Sandy Bridge] Flickering white lines on screen

If the problem occurs in Wayland and also after uninstalling the old driver, then it sounds like either a kernel bug or a hardware connection problem.

It looks like this is a desktop but with a laptop screen. Is that right?

affects: xserver-xorg-video-intel (Ubuntu) → linux-hwe-5.11 (Ubuntu)
summary: - I am having a wierd display glitch
+ [Sandy Bridge] Flickering white lines on screen
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please:

1. Reboot.

2. Log into a Wayland session and ensure the bug is happening.

3. While the bug is happening run:

   journalctl -b0 > journal.txt

4. Attach the resulting text file here.

Changed in linux-hwe-5.11 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

Attached the journal.txt

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

Thanks for your reply...
Yes my device is an HP omni 120 all in one series desktop..

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

This is the output of "inxi -Gxx"

Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Hewlett-Packard driver: i915 v: kernel ports: active: eDP-1
    empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0102
  Device-2: Chicony type: USB driver: uvcvideo bus-ID: 2-1.4:3
    chip-ID: 04f2:b296
  Display: wayland server: X.org v: 1.20.11 with: Xwayland
    compositor: gnome-shell v: 3.36.9 driver: X: loaded: fbdev
    unloaded: modesetting,vesa gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: HP Omni / Pro res: 1600x900 dpi: 92
    diag: 506mm (19.9")
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1)
    v: 3.3 Mesa 21.0.3 compat-v: 3.0 direct render: Yes

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In the past when people had trouble with HP all-in-one screens, the solution was:

 1. Beware! Backup you data! You will likely need to reinstall Ubuntu after this.
 2. Go into the BIOS and toggle the legacy mode/secure boot settings.
 3. Reinstall Ubuntu.

summary: - [Sandy Bridge] Flickering white lines on screen
+ [HP Omni 120-2110il AIO] Flickering white lines on screen
Changed in linux-hwe-5.11 (Ubuntu):
status: Incomplete → New
Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

Ok I will try this just now and check the results.. Thanks for your time..

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

So here's an update,
It seems like I don't have the 'Secure Boot' Option in my bios so I couldn't test it.
I disabled UEFI devices from my bios and that forced it to use legacy boot devices only (Sandisk Cruzer Blade in the above video is my bootable pendrive from which I am installing ubuntu)
Then reinstalled Ubuntu, but still the issues are same..
Here is a video of bug during the installation process- https://www.youtube.com/watch?v=1VMa3WcwaYQ
And here is a video of the startup process- https://www.youtube.com/watch?v=lIZj-oHXCHs

My BIOS doesn't have a direct option to switch to legacy or UEFI mode, so I disabled UEFI devices to force it to use legacy mode (and that's why there are not UEFI boot sources in the video above)
In short- Nothing Changed, Everything is the same
Also since Windows 10 works fine on the device I don't think that there is any damage or fault in the hardware

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try adding kernel parameter:

  i915.enable_psr=0

which you can do in /etc/default/grub as part of the GRUB_CMDLINE_LINUX_DEFAULT line. Then run:

  sudo update-grub

and reboot.

Changed in linux-hwe-5.11 (Ubuntu):
status: New → Incomplete
Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

Here is a screenshot of the grub file
Added parameter, updated the grub and rebooted but nothing has changed... The flickering lines are still there

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

To be sure it applied properly, what is the contents of /proc/cmdline ?

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=6ee9af7d-b744-419e-91ba-9ccff120f42b ro quiet splash i915.enable_psr=0 vt.handoff=7

content of /proc/cmdline

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

My only remaining suggestions are:

 * Try a newer kernel, or more simply try Ubuntu 22.04 which contains a newer kernel: http://cdimage.ubuntu.com/daily-live/current/ ; or

 * Use the nomodeset kernel parameter :(

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote (last edit ):

If i use the nomodeset parameter what things would get disabled?
Will I get slow performance with nomodeset parameter?

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

I would like to ask one more thing, Should I try some other liunx distribution such as fedora or linux mint or something else that you can suggest? Will changing the distro fix this issue? :(

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

Btw I am trying to install kernel 5.15.32.. Will let you know if things change..

Changed in linux-hwe-5.11 (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I don't think changing distro will fix it.

The final thing to try is the latest 'drmtip' kernel:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/

If the bug still isn't fixed in that latest kernel then you should report it to the kernel graphics developers at:

  https://gitlab.freedesktop.org/drm/intel/-/issues

Additional info:

  https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

Ok I will try 'drmtip' kernel, and report it as well in case it's not fixed.. But I would like to ask what if I use the "nomodeset" parameter.. What compromises would be there in using nomodeset?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

nomodeset really is a temporary workaround. It disables the GPU hardware acceleration, and in some cases might prevent you from even getting the correct screen resolution.

Revision history for this message
Jarvis Yadav (jarvisydv0069) wrote :

Can you help me out in installing the latest drmtip kernel.. Whenever I try to install drmtip kernel it shows error like,
"linux-headers-***-generic depends on libc6(>= 2.34) however Version of libc6 on system is 2.31
Package libssl3 is not installed"
I think I will have to compile the latest drmtip kernel to overcome these dependency issues.. I don't know how to compile the drmtip kernel.. Help would be appreciated.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's a little too complex to explain here.

Instead please try booting Ubuntu 22.04 from USB to see if it has the same bug:
http://cdimage.ubuntu.com/daily-live/current/

If you are willing to also install 22.04, and the bug still isn't fixed there, then the drm-tip kernel should install more easily on that.

Changed in linux-hwe-5.11 (Ubuntu):
status: Confirmed → New
status: New → Invalid
Changed in linux-hwe-5.11 (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Camilo QS (vxcamiloxv) wrote :

I have the same issue, I just tested last daily ubuntu iso lunar-desktop-amd64.iso (2023-02-16 08:22) and same issue

HP Omni 120
Intel Core i5-2400S
Intel graphics 2000 - Mesa Intel® HD Graphics 2000 (SNB GT1)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Camilo, can you attach a video of your issue?

tags: added: panel-artifact
Revision history for this message
Richard Marwitz (rhmarw) wrote :

I also have the same issue. It is the same as described in the the original post. My screen looks exactly like the video attached above. I am running Ubuntu 22.04.1 on an HP All in One 120-1031.

If I use NOMODSET the lines do not appear but the screen is too large to use.

Also if I use VNC to view the desktop remotely Everything looks good.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try the workaround in comment #13.

Revision history for this message
Richard Marwitz (rhmarw) wrote :

I tried the workaround in comment #13. The screen still has the lines.

Revision history for this message
Saija Tuiskula (saikkuli) wrote (last edit ):

I installed Ubuntu 22.04.2 LTS (Jammy Jellyfish) with Legacy safe graphics mode.

 After installation open terminal
and do the following (able to do despite the flikering):

Sudo nano /etc/defaul/grub

add nomodeset to GRUB_CMDLINE_LINUX_DEFAULT:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""

Then save by hitting Ctrl+O enter, exit nano whit Ctrl+X

Then run:

sudo update-grub

sudo reboot. (Rebooting doesn't work. Needs to shut down and restart?)

Now lines do not appear but the screen is large

Next still whit terminal.
xrandr_____ to see which Display is in use. (My was default)

$cvt 1600 900 (At this point there were several bug reports, I didn't care)

$cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync

$xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync

$xrandr --addmode default "1600x900_60.00"

$ xgamma
-> Red 1.000, Green 1.000, Blue 1.000 (For some strange reason this had to be done, otherwise it didn't work)

then

$sudo nano /etc/default/grub

find the line exsample:

#GRUB_GFXMODE=1024x768 (maybe something else)

edit 1024x786 to your resolution: 1600x900, remove the #

example:

GRUB_GFXMODE=1600x900

update by the command

$sudo update-grub

Then reboot your computer

$sudo reboot

This is what I done whit my HP Omni 120-1100eo Desktop PC

Revision history for this message
Camilo QS (vxcamiloxv) wrote :

Attached video of HP Omni 120 Flickering, I tested with kernel 6.0, 6.1, 6.2 (compiled by my self using drm-tip branch), and 6.2 from 23.04, now testing 6.3, same issue, the only workaround is "nomodeset i915.modeset=0"

Revision history for this message
Camilo QS (vxcamiloxv) wrote (last edit ):

I reported the issue to intel/freedesktop and was fixed https://gitlab.freedesktop.org/drm/intel/-/issues/8895#note_2005508, I guess it will be included in the next kernel version.

Revision history for this message
Leon Le (iamleon) wrote :

@Camilo QS, Could you please show me how to fix? I'm suffering from the same problem?

Revision history for this message
Leon Le (iamleon) wrote :

Solution: Build a kernel for HP Omni 120 based on Linux kernel 6.4.13

Step 1: Download Linux kernel 6.4.13 and extract:
"wget https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.4.13.tar.xz"
"tar xvf linux-6.4.13.tar.xz"

Step 2: Install additional packages for building a kernel
"sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc flex libelf-dev bison"

Step 3: Configure Kernel
Navigate to the linux-6.4.13 : "cd inux-6.4.13"
Copy the existing Linux config file: "cp -v /boot/config-$(uname -r) .config"
Make a default configuration file: "make menuconfig" -> Save -> Exit

Step 4: Edit drivers/gpu/drm/drm_edid.c in folder linux-6.4.13 (Visit https://gitlab.freedesktop.org/nouvelles/kernel/-/commit/2682768bde745b10ae126a322cdcaf532cf88851 for more details)
Remove
 /* Some EDIDs have bogus h/vtotal values */
 if (mode->hsync_end > mode->htotal)
  mode->htotal = mode->hsync_end + 1;
 if (mode->vsync_end > mode->vtotal)
  mode->vtotal = mode->vsync_end + 1;
Add
 /* Some EDIDs have bogus h/vsync_end values */
 if (mode->hsync_end > mode->htotal) {
  drm_dbg_kms(dev, "[CONNECTOR:%d:%s] reducing hsync_end %d->%d\n",
       connector->base.id, connector->name,
       mode->hsync_end, mode->htotal);
  mode->hsync_end = mode->htotal;
 }
 if (mode->vsync_end > mode->vtotal) {
  drm_dbg_kms(dev, "[CONNECTOR:%d:%s] reducing vsync_end %d->%d\n",
       connector->base.id, connector->name,
       mode->vsync_end, mode->vtotal);
  mode->vsync_end = mode->vtotal;
 }

Step 5: Start building the kernel. Note: It may take hours to complete.
"scripts/config --disable SYSTEM_TRUSTED_KEYS"
"scripts/config --disable SYSTEM_REVOCATION_KEYS"
"sudo make -j$(nproc)"
Press Enter 2 times to confirm the default options for the generation of new certificates.

Step 6: Install the compiled kernel
"sudo make modules_install"
then
"sudo make install"

Reboot and the flickering disappear. This issue has been existing for over a decade, so I hope anyone suffering from this issue can now fix it.

Revision history for this message
Camilo QS (vxcamiloxv) wrote :

FYI this is available in kernel version 6.7-rc7 and will be included in final release of linux kernel 6.7

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.