Bug 21732 - Monitor HP w22 not supported
Summary: Monitor HP w22 not supported
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
: 21733 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-09-18 10:05 CEST by Heiko Stark
Modified: 2020-08-23 15:56 CEST (History)
4 users (show)

See Also:
Source RPM: drakx-kbd-mouse-x11-1.23-1.mga6. ldetect-lst
CVE:
Status comment:


Attachments

Description Heiko Stark 2017-09-18 10:05:33 CEST
Theme name: Adwaita
Kernel version = 4.9.43-server-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Xeon(R) CPU           X5482  @ 3.20GHz
Comment 1 Marja Van Waes 2017-09-19 08:39:21 CEST
What _exactly_ do you mean when you say the HP w22 monitor is "not supported"? 
 Only that you cannot select it from the drop-down vendor list?
 Or also that you can't get it to work well or work at all?

Many monitors aren't in the vendor list, because nowadays most monitors support Plug'n Play

If your monitor works badly or not at all: when did you notice that:
 when *replacing* another monitor with the HP w22 monitor?
 or when *adding* the HP w22 as a second monitor?
 or.... ?

Keywords: (none) => NEEDINFO
CC: (none) => mageiatools, marja11

Comment 2 Heiko Stark 2017-09-19 09:21:30 CEST
Dear Marja van Waes,

Thanks for the answer!

Both, it's not in the drop-down vendor list and it doesn't work.
But I solved the problem as follows.

For the HP w22 monitor you could choose a similar monitor.

After that, I noticed that my Quadro NVS 295 graphics card could not handle a large screen size.
Planar Dome E5 (2560x2048) + HP w22 (1680x1050)
After I switched to a GT 630 it worked. That's why I think the graphics card was the main problem. 'NVIDIA X Server Setting' is a bit more informative than 'XFdrake' (sorry).

Additionally, is it possible to add your own monitors to the drop-down vendor list?

Best regards,
Heiko Stark
Comment 3 Marja Van Waes 2017-09-19 10:13:50 CEST
(In reply to Heiko Stark from comment #2)
> Dear Marja van Waes,
> 
> Thanks for the answer!
> 
> Both, it's not in the drop-down vendor list and it doesn't work.
> But I solved the problem as follows.
> 
> For the HP w22 monitor you could choose a similar monitor.
> 
> After that, I noticed that my Quadro NVS 295 graphics card could not handle
> a large screen size.
> Planar Dome E5 (2560x2048) + HP w22 (1680x1050)
> After I switched to a GT 630 it worked. That's why I think the graphics card
> was the main problem. 'NVIDIA X Server Setting' is a bit more informative
> than 'XFdrake' (sorry).
> 
> Additionally, is it possible to add your own monitors to the drop-down
> vendor list?

The monitor vendor list comes from

 /usr/share/ldetect-lst/MonitorsDB

I always assumed only CRT monitors need to be listed there.


@ Thierry or anyone else:

1. is that true, that the MonitorsDB is only meant for CRT monitors?
2. This bug confuses me, especially what Heiko tells about his graphic card. Is
   there anything that should be fixed in one of our packages?

Source RPM: drakx-kbd-mouse-x11-1.23-1.mga6 => drakx-kbd-mouse-x11-1.23-1.mga6. ldetect-lst

Marja Van Waes 2017-11-16 09:08:12 CET

Assignee: bugsquad => mageiatools
Keywords: NEEDINFO => (none)

Marja Van Waes 2018-11-03 09:14:23 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=21733

Comment 4 Thierry Vignaud 2018-11-05 11:27:33 CET
Nope, it's not restricted to CRT monitors

CC: (none) => thierry.vignaud

Comment 5 Thierry Vignaud 2018-11-05 11:34:18 CET
format is :

<Manufacturer>; <Monitor name>; <EISA ID (if any)>; <horiz sync in Khz>; <vert sync in Hz>; DPMS support or preferred_resolution

so here it would be sg like:
Hewlett-Packard; HP W22xxxxxxxxx; HWPxxxxxx; ...
Comment 6 Aurelien Oudelet 2020-08-16 21:21:35 CEST
*** Bug 21733 has been marked as a duplicate of this bug. ***
Comment 7 Aurelien Oudelet 2020-08-16 21:23:52 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team
Comment 8 Aurelien Oudelet 2020-08-23 15:56:03 CEST
Same above. Forget really closing.

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.