Bug 113529 - Mitsubishi Diamond Pro 2045u - Not Officially Supported
Summary: Mitsubishi Diamond Pro 2045u - Not Officially Supported
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Beta 3
Hardware: i686 SUSE Other
: P3 - Medium : Enhancement
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-27 09:37 UTC by Alex Radu
Modified: 2008-06-25 09:52 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Radu 2005-08-27 09:37:56 UTC
I have a c and it was not in the monitor list presented by SaX2. However, 
selecting the 2040u model worked adequately.  
 
If SUSE cannot officially support this monitor, like some other distros (Vida 
Linux 1.2), I suggest that a Mitsubishi Diamond Pro 2045u setting still be 
made and the settings from the 2040u used for it. This would mean that 
confused users wouldn't just quit with SUSE thinking their hardware is not 
supported.
Comment 1 Marcus Schaefer 2005-08-28 16:16:50 UTC
please provide additional information to this monitor. The output 
of  
 
  hwinfo --monitor 
 
for example 
 
Thanks 
 
Comment 2 Alex Radu 2005-08-28 16:57:07 UTC
OK, here it is: 
 
"linux:/home/exigentsky # hwinfo --monitor 
bash: hwinfo: command not found 
linux:/home/exigentsky #" 
 
I know that's not too helpful, but I really don't know how to help anymore. 
Comment 3 Marcus Schaefer 2005-08-29 05:38:50 UTC
hwinfo is located in /usr/sbin which isn't in your PATH so you need  
to specify the complete path to the command:  
  
    /usr/sbin/hwinfo --monitor 
 
thanks  
Comment 4 Alex Radu 2005-08-29 06:21:51 UTC
Alright, here's what it says: 
 
" 
linux:~ # /usr/sbin/hwinfo --monitor 
35: None 00.0: 10000 Monitor 
  [Created at fb.70] 
  Unique ID: rdCR.EY_qmtb9YY0 
  Hardware Class: monitor 
  Model: "Generic Monitor" 
  Vendor: "Generic" 
  Device: "Monitor" 
  Resolution: 1024x768@76Hz 
  Driver Info #0: 
    Max. Resolution: 1024x768 
    Vert. Sync Range: 50-90 Hz 
    Hor. Sync Range: 31-61 kHz 
  Config Status: cfg=no, avail=yes, need=no, active=unknown 
" 
Comment 5 Marcus Schaefer 2005-08-29 12:58:20 UTC
Hmm, yes thanks for this information but unfortunately as you can see  
the monitor is only detected as  Model: "Generic Monitor" which means 
it couldn't be detected completely 
 
According to this information I cannot include an entry to  
support the model. If you can give more technical details 
 
 - vendor and name 
 - hsync and vsync range 
 
I can add the model to the database but it will not be selected 
automatically 
Comment 6 Alex Radu 2005-08-29 17:07:11 UTC
Vendor: Mitsubishi 
Name: Diamond Pro 2045u

I know you need the hsync and vsync range, but I needa  few minutes to find that.
Comment 7 Alex Radu 2005-08-29 17:35:21 UTC
Here's everything for the Mitsubishi Diamond Pro 2045u (NSH1157):

Horizontal sync: 30.0-121.0 kHz
Vertical sync: 50.0-160.0 Hz

I hope that helps.
Comment 8 Stephan Kulow 2008-06-25 09:32:50 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 9 Stephan Kulow 2008-06-25 09:34:13 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 10 Stephan Kulow 2008-06-25 09:40:42 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 11 Stephan Kulow 2008-06-25 09:52:28 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(