[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#908464: marked as done (linux-image-amd64: Primary LCD screen refuse to work)

Your message dated Fri, 28 May 2021 12:15:08 -0700 (PDT)
with message-id <60b1413c.1c69fb81.879eb.2c51@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #908464,
regarding linux-image-amd64: Primary LCD screen refuse to work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
908464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908464
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 4.18+98
Severity: normal

Dear Maintainer,

Each time I try to boot with the new kernel (4.18.x), one of my LCD
screen works in VGA mode (as primary display) but stop to work as soon
as the graphical mode starts (it complains about "No signal").

Note that the system seems to be unaware of this because the second
screen render the graphical display as if the primary screen was working.

I am using Wayland (yes, I love the bleeding edge...).

One last specificity of my settings is that the primary display is
connected through DP (display port) and the secondary display uses HDMI.

I tried to look at the usual logs (/var/log/messages, /var/log/kern.log,
/var/log/Xorg.0.log and /var/log/Xorg.1.log), but I did not found
anything related (I may have missed it).

So, does the 4.18.x Linux kernel family introduce some new things about
the display ports or the way Xorg/Wayland is handled.

And, everything is working fine when I switch back to 4.17.x.
So, I really suspect the 4.18.x to be faulty on that.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.18.0-1-amd64  4.18.6-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: