Created attachment 48704 [details]
bug115151.tar.bz2

the monitor is unknown to hwinfo 

"can only be used with 1024x768" 
 
an important information, first you complained about that it does 
not work in "1280x854" than I changed that and now you are complaining 
about your crappy chip only supporting "1024x768", great ! 
 
I will change that now again to 1024x768 
 
Index: Monitors 
=================================================================== 
--- Monitors    (revision 850) 
+++ Monitors    (working copy) 
@@ -1,7 +1,7 @@ 
 # /.../ 
 # Copyright (c) 2001 SuSE GmbH Nuernberg, Germany.  All rights reserved. 
 # 
-# Author: Marcus Schaefer <sax@suse.de>, Thu Sep  1 10:44:40 2005 
+# Author: Marcus Schaefer <sax@suse.de>, Mon Sep  5 10:53:26 2005 
 # 
 # Template for monitor data 
 # -------------------------- 
@@ -3231,7 +3231,7 @@ 
  DDC=APP9C21 
  Option=DPMS 
  Hsync=32-60 
- Resolution=1280x854 
+ Resolution=1024x768 
  Vsync=50-70 
 } 
 

Marcus, note that this is a *different* monitor. 

hallt hallo hallo,

thats clearly not the display chip but the lcd, no?

so we just have to check the exact powerbook/ibook. the info in
/proc/device-tree/model tells you exactly this.
Or look for 'display' device_type files in the tree and use the width/height
properties. hwinfo has already code to walk the device-tree.

What was the DisplaySize of the other Powerbook?

I don't know what you guys are talking about *again* and this is really 
an annoying situation. I can make a correct CDB entry only with valid 
information: 
 
 Please provide information for model [ DDC=APP9C21 ] 
 
 (1) correct hsync ranges 
 (2) correct model (vendor and name) 
 (3) correct resolution 
 (4) correct display size in mm 
 
currently I use: 
 
  Hsync=32-60 
  Vsync=50-70 
  Resolution=1024x768 
  DisplaySize=No information (used from libhd if available) 
 
 
 

would it help if hwinfo reports everything, does sax or whoever look at the
hwinfo data?
if yes, we will just provide a hardcoded list.

sax is linked against libhd since years ! it uses data like  
  
  DDC_ID  
  resolution  
  hsync/vsync  
  displaysize  
  
and because of the fact that this data is sometimes wrong or missing  
the CDB entry may add/overwrite that data as well. For this monitor  
we have a unique DDC ID:  
  
   APP9C21 
 
so I'm able to set everything in the CDB but you need to provide 
correct data of course 

do you have the hwinfo data from the 1280x854 bugreport?

Marcus, note we are talking about APP9C19 (see comment 0). And Olaf, you 
probably should say what lcd _this_ is. 

my own report is a 12" ibook with 1024x768

of course: 
 
 16: None 00.0: 10000 Monitor 
  [Created at monitor.373] 
  Unique ID: rdCR.W+VqikgpQEC 
  Old Unique ID: pY3q.1g0+cJOHtfE 
  Hardware Class: monitor 
  HW Class List: monitor 
  Model: "Apple Color LCD" 
  Vendor: APP "Apple" 
  Device: eisa 0x9c21 "Color LCD" 
  Size: 32x22 cm 
  Config Status: cfg=new, avail=yes, need=no, active=unknown 
 
according to this information I created a CDB entry and fixed bug #113795 
As you can see hwinfo doesn't provide a resolution, this setting will 
come from the CDB and is currently 1024x768 
 
what is going on here ?????? 
 

hwinfo 11.18 knows about comment 12. 

ok we are talking about two monitors *argl*. The CDB provides now the 
following models. Please have a look: 
 
#============================================== 
# COLOR LCD 9C19 
#---------------------------------------------- 
APPLE:COLOR LCD 9C19  { 
 DDC=APP9C19 
 Option=DPMS 
 Hsync=32-60 
 Resolution=1024x768 
 Vsync=50-70 
} 
 
#============================================== 
# Color LCD 9C21 
#---------------------------------------------- 
APPLE:COLOR LCD 9C21  { 
 DDC=APP9C21 
 Option=DPMS 
 Hsync=32-60 
 Resolution=1280x854 
 Vsync=50-70 
} 
 
Is this ok now ? 

hopefully.

cool :-)