From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 218785] New: HP Victus by HP Laptop 16-e0xxx. HDMI connection doesn't detect counterpart projector.
Date: Sat, 27 Apr 2024 16:43:43 +0000 [thread overview]
Message-ID: <bug-218785-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218785
Bug ID: 218785
Summary: HP Victus by HP Laptop 16-e0xxx. HDMI connection
doesn't detect counterpart projector.
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: icegood1980@gmail.com
Regression: No
As for me, it is regression.
On the same laptop and different OSes:
1) Linux fedora 6.0.17-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 4
16:00:03 UTC 2023 x86_64 GNU/Linux
everything is fine. UDEV has changes during cable plug in:
KERNEL[48.311971] change
/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card0 (drm)
UDEV [48.317955] change
/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card0 (drm)
KERNEL[49.453282] add
/devices/pci0000:00/0000:00:01.1/0000:01:00.0/graphics/fb1 (graphics)
UDEV [49.455485] add
/devices/pci0000:00/0000:00:01.1/0000:01:00.0/graphics/fb1 (graphics)
2) In both new ubuntu
Linux ice-home 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20
00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
and fedora vmlinuz-6.8.7-300.fc40.x86_64
udev is empty. No changes
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-04-27 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 16:43 bugzilla-daemon [this message]
2024-04-27 16:46 ` [Bug 218785] HP Victus by HP Laptop 16-e0xxx. HDMI connection doesn't detect counterpart projector bugzilla-daemon
2024-04-28 8:16 ` bugzilla-daemon
2024-05-01 6:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218785-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).