* radeonfb: DDC read wrong? @ 2006-06-20 14:01 Robert Siemer 2006-06-24 12:11 ` Antonino A. Daplas 0 siblings, 1 reply; 10+ messages in thread From: Robert Siemer @ 2006-06-20 14:01 UTC (permalink / raw) To: linux-fbdev-devel Hello everybody! problem: booting kernel overdrives monitor with 200Hz refresh kernel: 2.6.16 kernel which worked fine: 2.6.14 Monitor: EIZO FlexScan F563-T Graphic adapter: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (from Xorg.log) I switched to 2.6.16 and booting the kernel overdrove my monitor with 200Hz refresh rate. As I notice now I have a limit configured in X (I will try it without limitation to see what X is doing...). The only interesting line so far from X-log: (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=20000 max=40000; xclk=20000 Any comments? Robert ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-20 14:01 radeonfb: DDC read wrong? Robert Siemer @ 2006-06-24 12:11 ` Antonino A. Daplas 2006-06-24 17:47 ` Robert Siemer 0 siblings, 1 reply; 10+ messages in thread From: Antonino A. Daplas @ 2006-06-24 12:11 UTC (permalink / raw) To: linux-fbdev-devel, Robert.Siemer Robert Siemer wrote: > Hello everybody! > > problem: booting kernel overdrives monitor with 200Hz refresh > > kernel: 2.6.16 > kernel which worked fine: 2.6.14 > > Monitor: EIZO FlexScan F563-T > Graphic adapter: ATI Technologies Inc Radeon RV250 If [Radeon 9000] > (from Xorg.log) > > I switched to 2.6.16 and booting the kernel overdrove my monitor with > 200Hz refresh rate. > > As I notice now I have a limit configured in X (I will try it without > limitation to see what X is doing...). > > The only interesting line so far from X-log: > (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=20000 max=40000; > xclk=20000 > > > Any comments? Can you change #undef DEBUG to #define DEBUG in drivers/video/fbmon.c then post your dmesg? If your monitor's EDID block is faulty, we can add it to our monitor database for fixups. Tony Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-24 12:11 ` Antonino A. Daplas @ 2006-06-24 17:47 ` Robert Siemer 2006-06-24 21:33 ` Antonino A. Daplas ` (2 more replies) 0 siblings, 3 replies; 10+ messages in thread From: Robert Siemer @ 2006-06-24 17:47 UTC (permalink / raw) To: linux-fbdev-devel [-- Attachment #1: Type: text/plain, Size: 1293 bytes --] On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: > Robert Siemer wrote: > > Hello everybody! > > > > problem: booting kernel overdrives monitor with 200Hz refresh > > > > kernel: 2.6.16 > > kernel which worked fine: 2.6.14 > > > > Monitor: EIZO FlexScan F563-T > > Graphic adapter: ATI Technologies Inc Radeon RV250 If [Radeon 9000] > > (from Xorg.log) > > > > I switched to 2.6.16 and booting the kernel overdrove my monitor with > > 200Hz refresh rate. > > > > As I notice now I have a limit configured in X (I will try it without > > limitation to see what X is doing...). > > > > The only interesting line so far from X-log: > > (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=20000 max=40000; > > xclk=20000 > > > > > > Any comments? > > Can you change #undef DEBUG to #define DEBUG in drivers/video/fbmon.c > then post your dmesg? > > If your monitor's EDID block is faulty, we can add it to our > monitor database for fixups. Have you read this message from me? http://marc.theaimsgroup.com/?l=linux-fbdev-devel&m=115096319623635&w=2 The EDID block has a correct checksum as "get-edid | parse-edid" is saying... The monitor is a 17", with frequencies H: 30 - 86 kHz, V: 55 - 160 Hz. I recommand it with 1024x768@100 The dmesg is attached... Robert [-- Attachment #2: dmesg --] [-- Type: text/plain, Size: 11377 bytes --] [4294667.296000] Linux version 2.6.16 (Version: panorama.4) (siemer@panorama) (gcc version 4.1.2 20060613 (prerelease) (Debian 4.1.1-5)) #5 PREEMPT Sat Jun 24 19:19:30 CEST 2006 [4294667.296000] BIOS-provided physical RAM map: [4294667.296000] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) [4294667.296000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) [4294667.296000] BIOS-e820: 0000000000100000 - 000000007ffec000 (usable) [4294667.296000] BIOS-e820: 000000007ffec000 - 000000007ffef000 (ACPI data) [4294667.296000] BIOS-e820: 000000007ffef000 - 000000007ffff000 (reserved) [4294667.296000] BIOS-e820: 000000007ffff000 - 0000000080000000 (ACPI NVS) [4294667.296000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) [4294667.296000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) [4294667.296000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) [4294667.296000] 0MB HIGHMEM available. [4294667.296000] 2047MB LOWMEM available. [4294667.296000] On node 0 totalpages: 524268 [4294667.296000] DMA zone: 4096 pages, LIFO batch:0 [4294667.296000] DMA32 zone: 0 pages, LIFO batch:0 [4294667.296000] Normal zone: 520172 pages, LIFO batch:31 [4294667.296000] HighMem zone: 0 pages, LIFO batch:0 [4294667.296000] DMI 2.3 present. [4294667.296000] ASUS P4B266 detected: force use of acpi=ht [4294667.296000] ACPI: RSDP (v000 ASUS ) @ 0x000f7720 [4294667.296000] ACPI: RSDT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x7ffec000 [4294667.296000] ACPI: FADT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x7ffec100 [4294667.296000] ACPI: BOOT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x7ffec040 [4294667.296000] ACPI: MADT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x7ffec080 [4294667.296000] ACPI: DSDT (v001 ASUS P4B266 0x00001000 MSFT 0x0100000b) @ 0x00000000 [4294667.296000] ACPI: PM-Timer IO Port: 0xe408 [4294667.296000] ACPI: Local APIC address 0xfee00000 [4294667.296000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [4294667.296000] Processor #0 15:2 APIC version 20 [4294667.296000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [4294667.296000] Allocating PCI resources starting at 88000000 (gap: 80000000:7ec00000) [4294667.296000] Built 1 zonelists [4294667.296000] Kernel command line: BOOT_IMAGE=/vmlinuz video=radeonfb:1024x768@100 resume=/dev/hda3 [4294667.296000] Found and enabled local APIC! [4294667.296000] mapped APIC to ffffd000 (fee00000) [4294667.296000] Enabling fast FPU save and restore... done. [4294667.296000] Enabling unmasked SIMD FPU exception support... done. [4294667.296000] Initializing CPU#0 [4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes) [4294667.296000] Detected 1816.476 MHz processor. [4294667.296000] Using pmtmr for high-res timesource [4294667.296000] Console: colour VGA+ 80x25 [4294667.608000] Dentry cache hash table entries: 524288 (order: 9, 2097152 bytes) [4294667.614000] Inode-cache hash table entries: 262144 (order: 8, 1048576 bytes) [4294667.668000] Memory: 2074136k/2097072k available (1794k kernel code, 22472k reserved, 684k data, 140k init, 0k highmem) [4294667.668000] Checking if this processor honours the WP bit even in supervisor mode... Ok. [4294667.728000] Calibrating delay using timer specific routine.. 3637.28 BogoMIPS (lpj=1818644) [4294667.728000] Security Framework v1.0.0 initialized [4294667.728000] Capability LSM initialized [4294667.728000] Mount-cache hash table entries: 512 [4294667.728000] CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 [4294667.728000] CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 [4294667.728000] CPU: Trace cache: 12K uops, L1 D cache: 8K [4294667.728000] CPU: L2 cache: 512K [4294667.728000] CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 [4294667.728000] Intel machine check architecture supported. [4294667.728000] Intel machine check reporting enabled on CPU#0. [4294667.728000] CPU0: Intel P4/Xeon Extended MCE MSRs (12) available [4294667.728000] CPU0: Thermal monitoring enabled [4294667.728000] CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 [4294667.728000] Checking 'hlt' instruction... OK. [4294667.834000] NET: Registered protocol family 16 [4294667.835000] PCI: PCI BIOS revision 2.10 entry at 0xf1090, last bus=2 [4294667.835000] PCI: Using configuration type 1 [4294667.836000] ACPI: Subsystem revision 20060127 [4294667.836000] ACPI: Interpreter disabled. [4294667.836000] Linux Plug and Play Support v0.97 (c) Adam Belay [4294667.836000] pnp: PnP ACPI: disabled [4294667.836000] SCSI subsystem initialized [4294667.836000] usbcore: registered new driver usbfs [4294667.836000] usbcore: registered new driver hub [4294667.836000] PCI: Probing PCI hardware [4294667.836000] PCI: Probing PCI hardware (bus 00) [4294667.837000] PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO [4294667.837000] PCI quirk: region ec00-ec3f claimed by ICH4 GPIO [4294667.837000] Boot video device is 0000:01:00.0 [4294667.838000] PCI: Transparent bridge - 0000:00:1e.0 [4294667.839000] PCI: Using IRQ router PIIX/ICH [8086/2440] at 0000:00:1f.0 [4294667.839000] PCI: Found IRQ 5 for device 0000:02:03.0 [4294667.839000] PCI: Sharing IRQ 5 with 0000:02:04.0 [4294667.839000] PCI: Sharing IRQ 5 with 0000:02:09.0 [4294667.839000] PCI: Sharing IRQ 5 with 0000:02:0d.0 [4294667.839000] PCI: Found IRQ 9 for device 0000:02:04.2 [4294667.839000] PCI: Sharing IRQ 9 with 0000:00:1f.4 [4294667.852000] PCI: Bridge: 0000:00:01.0 [4294667.852000] IO window: d000-dfff [4294667.852000] MEM window: e9800000-ea7fffff [4294667.852000] PREFETCH window: ec000000-f7ffffff [4294667.852000] PCI: Bridge: 0000:00:1e.0 [4294667.852000] IO window: a000-bfff [4294667.852000] MEM window: e6000000-e97fffff [4294667.852000] PREFETCH window: ea800000-ebffffff [4294667.852000] PCI: Setting latency timer of device 0000:00:1e.0 to 64 [4294667.852000] Simple Boot Flag at 0x3a set to 0x80 [4294667.852000] Machine check exception polling timer started. [4294667.853000] audit: initializing netlink socket (disabled) [4294667.853000] audit(1151170193.852:1): initialized [4294667.854000] VFS: Disk quotas dquot_6.5.1 [4294667.854000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [4294667.854000] Initializing Cryptographic API [4294667.854000] io scheduler noop registered [4294667.854000] io scheduler anticipatory registered [4294667.854000] io scheduler deadline registered (default) [4294667.854000] io scheduler cfq registered [4294667.855000] radeonfb_pci_register BEGIN [4294667.855000] PCI: Found IRQ 11 for device 0000:01:00.0 [4294667.855000] radeonfb (0000:01:00.0): Found 65536k of DDR 128 bits wide videoram [4294667.855000] radeonfb (0000:01:00.0): mapped 16384k videoram [4294667.855000] radeonfb: Found Intel x86 BIOS ROM Image [4294667.855000] radeonfb: Retrieved PLL infos from BIOS [4294667.855000] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=250.00 Mhz, System=200.00 MHz [4294667.855000] radeonfb: PLL min 20000 max 40000 [4294667.855000] 1 chips in connector info [4294667.855000] - chip 1 has 2 connectors [4294667.856000] * connector 0 of type 2 (CRT) : 2300 [4294667.856000] * connector 1 of type 3 (DVI-I) : 3201 [4294667.856000] Starting monitor auto detection... [4294668.063000] radeonfb: I2C (port 1) ... not found [4294668.426000] radeonfb: I2C (port 2) ... not found [4294668.658000] radeonfb: I2C (port 3) ... found CRT display [4294669.021000] radeonfb: I2C (port 4) ... not found [4294669.384000] radeonfb: I2C (port 2) ... not found [4294669.747000] radeonfb: I2C (port 4) ... not found [4294669.979000] radeonfb: I2C (port 3) ... found CRT display [4294669.979000] radeonfb: Monitor 1 type CRT found [4294669.979000] radeonfb: EDID probed [4294669.979000] radeonfb: Monitor 2 type no found [4294669.979000] ======================================== [4294669.979000] Display Information (EDID) [4294669.979000] ======================================== [4294669.979000] EDID Version 1.1 [4294669.979000] Manufacturer: EIZ [4294669.979000] Model: 202 [4294669.979000] Serial#: 0 [4294669.979000] Year: 1996 Week 2 [4294669.979000] ASCII Block: 7 \x1eV\x01\x01\x01\x01\x01\x01\x01\x01\x01 [4294669.979000] Display Characteristics: [4294669.979000] Monitor Operating Limits: Detailed Timings [4294669.979000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.979000] [4294669.980000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.980000] [4294669.980000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.980000] [4294669.980000] Supported VESA Modes [4294669.980000] 720x400@70Hz [4294669.980000] 832x624@75Hz [4294669.980000] 1280x1024@75Hz [4294669.980000] 1152x870@75Hz [4294669.980000] Manufacturer's mask: 0 [4294669.980000] Standard Timings [4294669.980000] Extrapolated [4294669.980000] H: 0-80KHz V: 38-75Hz DCLK: 135MHz [4294669.980000] Analog Display Input: Input Voltage - 0.700V/0.300V [4294669.980000] Sync: Separate Composite Sync on Green [4294669.981000] Max H-size in cm: 31 [4294669.981000] Max V-size in cm: 23 [4294669.981000] Gamma: 1.80 [4294669.981000] DPMS: Active yes, Suspend yes, Standby yes [4294669.981000] RGB Color Display [4294669.981000] Chroma [4294669.981000] RedX: 0.625 RedY: 0.340 [4294669.981000] GreenX: 0.275 GreenY: 0.605 [4294669.981000] BlueX: 0.150 BlueY: 0.065 [4294669.981000] WhiteX: 0.283 WhiteY: 0.298 [4294669.981000] Detailed Timings [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.982000] [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.982000] [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync [4294669.982000] [4294669.982000] Supported VESA Modes [4294669.982000] 720x400@70Hz [4294669.982000] 832x624@75Hz [4294669.982000] 1280x1024@75Hz [4294669.982000] 1152x870@75Hz [4294669.982000] Manufacturer's mask: 0 [4294669.982000] Standard Timings [4294669.983000] ======================================== [4294669.986000] hStart = 1217, hEnd = 1345, hTotal = 1601 [4294669.986000] vStart = 865, vEnd = 868, vTotal = 900 [4294669.986000] h_total_disp = 0x8f00c7 hsync_strt_wid = 0x1004cb [4294669.986000] v_total_disp = 0x35f0383 vsync_strt_wid = 0x30360 [4294669.986000] pixclock = 9259 [4294669.986000] freq = 10800 [4294669.986000] freq = 10800, PLL min = 20000, PLL max = 40000 [4294669.986000] ref_div = 12, ref_clk = 2700, output_freq = 21600 [4294669.986000] ref_div = 12, ref_clk = 2700, output_freq = 21600 [4294669.986000] post div = 0x1 [4294669.986000] fb_div = 0x60 [4294669.986000] ppll_div_3 = 0x10060 [4294670.047000] Console: switching to colour frame buffer device 144x54 [4294670.050000] radeonfb (0000:01:00.0): ATI Radeon If [4294670.050000] radeonfb_pci_register END [4294670.053000] PNP: No PS/2 controller found. Probing ports directly. .... [-- Attachment #3: Type: text/plain, Size: 300 bytes --] Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 [-- Attachment #4: Type: text/plain, Size: 182 bytes --] _______________________________________________ Linux-fbdev-devel mailing list Linux-fbdev-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-24 17:47 ` Robert Siemer @ 2006-06-24 21:33 ` Antonino A. Daplas 2006-06-24 21:56 ` Robert Siemer 2006-06-24 23:27 ` Antonino A. Daplas 2006-06-25 0:00 ` Antonino A. Daplas 2 siblings, 1 reply; 10+ messages in thread From: Antonino A. Daplas @ 2006-06-24 21:33 UTC (permalink / raw) To: linux-fbdev-devel; +Cc: Robert Siemer Robert Siemer wrote: > On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: >> Robert Siemer wrote: > [4294669.980000] Analog Display Input: Input Voltage - 0.700V/0.300V > [4294669.980000] Sync: Separate Composite Sync on Green > [4294669.981000] Max H-size in cm: 31 > [4294669.981000] Max V-size in cm: 23 > [4294669.981000] Gamma: 1.80 > [4294669.981000] DPMS: Active yes, Suspend yes, Standby yes > [4294669.981000] RGB Color Display > [4294669.981000] Chroma > [4294669.981000] RedX: 0.625 RedY: 0.340 > [4294669.981000] GreenX: 0.275 GreenY: 0.605 > [4294669.981000] BlueX: 0.150 BlueY: 0.065 > [4294669.981000] WhiteX: 0.283 WhiteY: 0.298 > [4294669.981000] Detailed Timings > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > [4294669.982000] > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > [4294669.982000] > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > [4294669.982000] Yes, your monitor has a broken EDID block. It basically violated the VESA detailed timing descriptor specs. Can you send me a dump of the EDID? You can use read-edid for that. Tony Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-24 21:33 ` Antonino A. Daplas @ 2006-06-24 21:56 ` Robert Siemer 0 siblings, 0 replies; 10+ messages in thread From: Robert Siemer @ 2006-06-24 21:56 UTC (permalink / raw) To: linux-fbdev-devel [-- Attachment #1: Type: text/plain, Size: 1532 bytes --] On Sun, Jun 25, 2006 at 05:33:21AM +0800, Antonino A. Daplas wrote: > Robert Siemer wrote: > > On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: > >> Robert Siemer wrote: > > > [4294669.980000] Analog Display Input: Input Voltage - 0.700V/0.300V > > [4294669.980000] Sync: Separate Composite Sync on Green > > [4294669.981000] Max H-size in cm: 31 > > [4294669.981000] Max V-size in cm: 23 > > [4294669.981000] Gamma: 1.80 > > [4294669.981000] DPMS: Active yes, Suspend yes, Standby yes > > [4294669.981000] RGB Color Display > > [4294669.981000] Chroma > > [4294669.981000] RedX: 0.625 RedY: 0.340 > > [4294669.981000] GreenX: 0.275 GreenY: 0.605 > > [4294669.981000] BlueX: 0.150 BlueY: 0.065 > > [4294669.981000] WhiteX: 0.283 WhiteY: 0.298 > > [4294669.981000] Detailed Timings > > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > > [4294669.982000] > > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > > [4294669.982000] > > [4294669.982000] 2 MHz 1 2 3 258 1 1 18 258 -HSync -VSync > > [4294669.982000] > > Yes, your monitor has a broken EDID block. It basically violated the > VESA detailed timing descriptor specs. I noticed already. > Can you send me a dump of the EDID? You can use read-edid for that. What will the corrected behaviour look like. The edid is attached (get-edid), but tell me what the changes to the kernel will cause! Robert [-- Attachment #2: eizo.edid --] [-- Type: application/octet-stream, Size: 128 bytes --] [-- Attachment #3: Type: text/plain, Size: 300 bytes --] Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 [-- Attachment #4: Type: text/plain, Size: 182 bytes --] _______________________________________________ Linux-fbdev-devel mailing list Linux-fbdev-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-24 17:47 ` Robert Siemer 2006-06-24 21:33 ` Antonino A. Daplas @ 2006-06-24 23:27 ` Antonino A. Daplas 2006-06-25 0:00 ` Antonino A. Daplas 2 siblings, 0 replies; 10+ messages in thread From: Antonino A. Daplas @ 2006-06-24 23:27 UTC (permalink / raw) To: linux-fbdev-devel; +Cc: Robert Siemer Robert Siemer wrote: > On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: >> Robert Siemer wrote: >>> Hello everybody! >>> >>> Any comments? >> Can you change #undef DEBUG to #define DEBUG in drivers/video/fbmon.c >> then post your dmesg? >> >> If your monitor's EDID block is faulty, we can add it to our >> monitor database for fixups. > > Have you read this message from me? > http://marc.theaimsgroup.com/?l=linux-fbdev-devel&m=115096319623635&w=2 Okay, now I see it. > > The EDID block has a correct checksum as "get-edid | parse-edid" is > saying... > > The monitor is a 17", with frequencies H: 30 - 86 kHz, V: 55 - 160 Hz. I > recommand it with 1024x768@100 > BTW, I'm attaching a patch that does basic fix-ups. It just marks the invalid detailed timings descriptor blocks to "unknown". Post your dmesg again, and if it works you should see something like: fbmon: The EDID block of blah-blah is known to be broken fbmon: Trying to fix blah-blah As mentioned, this is a basic fix. We can be more fancy with the fix-ups but I will need the specifications of your monitor. Hsync and Vsync ranges, PixelClock A working and preferred modeline to replace the detailed timing: xvidtune would help A few supported VESA compatible modes, etc... Tony diff --git a/drivers/video/fbmon.c b/drivers/video/fbmon.c index fb9ed4c..31ccc35 100644 --- a/drivers/video/fbmon.c +++ b/drivers/video/fbmon.c @@ -49,8 +49,9 @@ #else #define DPRINTK(fmt, args...) #endif -#define FBMON_FIX_HEADER 1 -#define FBMON_FIX_INPUT 2 +#define FBMON_FIX_HEADER 1 +#define FBMON_FIX_INPUT 2 +#define FBMON_FIX_DETAILED 3 #ifdef CONFIG_FB_MODE_HELPERS struct broken_edid { @@ -72,6 +73,12 @@ static struct broken_edid brokendb[] = { .model = 0x5a44, .fix = FBMON_FIX_INPUT, }, + /* Eizo (202) */ + { + .manufacturer = "EIZ", + .model = 0x0202, + .fix = FBMON_FIX_DETAILED, + }, }; static const unsigned char edid_v1_header[] = { 0x00, 0xff, 0xff, 0xff, @@ -127,6 +134,17 @@ static int check_edid(unsigned char *edi if (b[4] & 0x01 && b[0] & 0x80) ret = fix; break; + case FBMON_FIX_DETAILED: + b = edid + DETAILED_TIMING_DESCRIPTIONS_START; + + for (i = 0; i < 4; i++, b+=DETAILED_TIMING_DESCRIPTION_SIZE) { + if (!(b[0] == 0 && b[1] == 0 && b[2] == 0)) { + ret = fix; + break; + } + } + + break; } return ret; @@ -135,6 +153,7 @@ static int check_edid(unsigned char *edi static void fix_edid(unsigned char *edid, int fix) { unsigned char *b; + int i; switch (fix) { case FBMON_FIX_HEADER: @@ -146,8 +165,21 @@ static void fix_edid(unsigned char *edid b = edid + EDID_STRUCT_DISPLAY; b[0] &= ~0x80; edid[127] += 0x80; + break; + case FBMON_FIX_DETAILED: + printk("fbmon: trying to fix detailed description blocks\n"); + b = edid + DETAILED_TIMING_DESCRIPTIONS_START; + + /* Use 0xf0 which is currently unused for tagging */ + for (i = 0; i < 4; i++, b+=DETAILED_TIMING_DESCRIPTION_SIZE) { + if (!(b[0] == 0 && b[1] == 0 && b[2] == 0)) { + b[3] = 0xf0; + b[0] = b[1] = b[2] = b[4] = 0; + } + } } -} +} + static int edid_checksum(unsigned char *edid) { Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-24 17:47 ` Robert Siemer 2006-06-24 21:33 ` Antonino A. Daplas 2006-06-24 23:27 ` Antonino A. Daplas @ 2006-06-25 0:00 ` Antonino A. Daplas 2006-06-26 17:01 ` Robert Siemer 2 siblings, 1 reply; 10+ messages in thread From: Antonino A. Daplas @ 2006-06-25 0:00 UTC (permalink / raw) To: linux-fbdev-devel; +Cc: Robert Siemer Robert Siemer wrote: > On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: >> Robert Siemer wrote: Disregard the previous patch, I forgot to adjust the checksum. Try this instead... Tony diff --git a/drivers/video/fbmon.c b/drivers/video/fbmon.c index fb9ed4c..42865b6 100644 --- a/drivers/video/fbmon.c +++ b/drivers/video/fbmon.c @@ -49,8 +49,9 @@ #else #define DPRINTK(fmt, args...) #endif -#define FBMON_FIX_HEADER 1 -#define FBMON_FIX_INPUT 2 +#define FBMON_FIX_HEADER 1 +#define FBMON_FIX_INPUT 2 +#define FBMON_FIX_DETAILED 3 #ifdef CONFIG_FB_MODE_HELPERS struct broken_edid { @@ -72,6 +73,12 @@ static struct broken_edid brokendb[] = { .model = 0x5a44, .fix = FBMON_FIX_INPUT, }, + /* Eizo (202) */ + { + .manufacturer = "EIZ", + .model = 0x0202, + .fix = FBMON_FIX_DETAILED, + }, }; static const unsigned char edid_v1_header[] = { 0x00, 0xff, 0xff, 0xff, @@ -127,6 +134,18 @@ static int check_edid(unsigned char *edi if (b[4] & 0x01 && b[0] & 0x80) ret = fix; break; + case FBMON_FIX_DETAILED: + b = edid + DETAILED_TIMING_DESCRIPTIONS_START; + + for (i = 0; i < 4; i++, b+=DETAILED_TIMING_DESCRIPTION_SIZE) { + if (!(b[0] == 0 && b[1] == 0 && + b[2] == 0 && b[4] == 0)) { + ret = fix; + break; + } + } + + break; } return ret; @@ -134,7 +153,8 @@ static int check_edid(unsigned char *edi static void fix_edid(unsigned char *edid, int fix) { - unsigned char *b; + unsigned char *b, csum = 0; + int i; switch (fix) { case FBMON_FIX_HEADER: @@ -146,8 +166,29 @@ static void fix_edid(unsigned char *edid b = edid + EDID_STRUCT_DISPLAY; b[0] &= ~0x80; edid[127] += 0x80; + break; + case FBMON_FIX_DETAILED: + printk("fbmon: trying to fix detailed description blocks\n"); + b = edid + DETAILED_TIMING_DESCRIPTIONS_START; + + /* Use 0xf0 which is currently unused for tagging */ + for (i = 0; i < 4; i++, b+=DETAILED_TIMING_DESCRIPTION_SIZE) { + if (!(b[0] == 0 && b[1] == 0 && + b[2] == 0 && b[4] == 0)) { + b[3] = 0xf0; + b[0] = b[1] = b[2] = b[4] = 0; + } + } + + for (i = 0; i < EDID_LENGTH - 1; i++) + csum += edid[i]; + + csum = 256 - csum; + edid[EDID_LENGTH - 1] = csum; + } -} +} + static int edid_checksum(unsigned char *edid) { Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-25 0:00 ` Antonino A. Daplas @ 2006-06-26 17:01 ` Robert Siemer 2006-06-26 20:55 ` Antonino A. Daplas 0 siblings, 1 reply; 10+ messages in thread From: Robert Siemer @ 2006-06-26 17:01 UTC (permalink / raw) To: linux-fbdev-devel On Sun, Jun 25, 2006 at 08:00:30AM +0800, Antonino A. Daplas wrote: > Robert Siemer wrote: > > On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: > >> Robert Siemer wrote: > > Disregard the previous patch, I forgot to adjust the checksum. > Try this instead... The patch works in the way that I see a console without a video= param. Please answer my questions: -Does the EDID block that reads the kernel get somehow exported or used somewhere else (in kernel maybe)? -How get the capabilities of the monitor joined with the capabilities of the graphic adapter? -Are there some (high) minimum capabilities of the radeon cards (so, is it possible to assume all can handle h: ...kHz, v: ...Hz or pxck: ...MHz) -Which mode gets choosen from the resulting set of resolutions? I mean, based on what? Thanks, Robert Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-26 17:01 ` Robert Siemer @ 2006-06-26 20:55 ` Antonino A. Daplas 2006-06-27 19:11 ` Luca 0 siblings, 1 reply; 10+ messages in thread From: Antonino A. Daplas @ 2006-06-26 20:55 UTC (permalink / raw) To: linux-fbdev-devel; +Cc: Robert Siemer Robert Siemer wrote: > On Sun, Jun 25, 2006 at 08:00:30AM +0800, Antonino A. Daplas wrote: >> Robert Siemer wrote: >>> On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: >>>> Robert Siemer wrote: >> Disregard the previous patch, I forgot to adjust the checksum. >> Try this instead... > > The patch works in the way that I see a console without a video= param. > > Please answer my questions: > -Does the EDID block that reads the kernel get somehow exported or > used somewhere else (in kernel maybe)? For drivers that use the EDID, it gets converted into struct fb_monspecs. Part of this structure is a private mode database (cat /sys/class/graphics/fb0/modes). > -How get the capabilities of the monitor joined with the capabilities > of the graphic adapter? The driver has to watch out for that. > -Are there some (high) minimum capabilities of the radeon cards (so, > is it possible to assume all can handle h: ...kHz, v: ...Hz or pxck: > ...MHz) VGA cards will always have an upper limit to the pixelclock, and the horizontal and vertical sync limits are derived from the pixelclock and the resolution of the display. > -Which mode gets choosen from the resulting set of resolutions? I mean, > based on what? Depends on the driver. A combination of the 'first detailed timing is preferred' flag and a detailed timing is the initial startup mode. As for radeonfb, I think it just grabs the first detailed timing for the initial mode. Tony Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: radeonfb: DDC read wrong? 2006-06-26 20:55 ` Antonino A. Daplas @ 2006-06-27 19:11 ` Luca 0 siblings, 0 replies; 10+ messages in thread From: Luca @ 2006-06-27 19:11 UTC (permalink / raw) To: linux-fbdev-devel; +Cc: Robert Siemer Il Tue, Jun 27, 2006 at 04:55:49AM +0800, Antonino A. Daplas ha scritto: > Robert Siemer wrote: > > On Sun, Jun 25, 2006 at 08:00:30AM +0800, Antonino A. Daplas wrote: > >> Robert Siemer wrote: > >>> On Sat, Jun 24, 2006 at 08:11:46PM +0800, Antonino A. Daplas wrote: > >>>> Robert Siemer wrote: > >> Disregard the previous patch, I forgot to adjust the checksum. > >> Try this instead... > > > > The patch works in the way that I see a console without a video= param. > > > > Please answer my questions: > > -Does the EDID block that reads the kernel get somehow exported or > > used somewhere else (in kernel maybe)? > > For drivers that use the EDID, it gets converted into struct fb_monspecs. > Part of this structure is a private mode database > (cat /sys/class/graphics/fb0/modes). With radeonfb you can also access the raw edid block(s): /sys/class/graphics/fb0/device/edid1 /sys/class/graphics/fb0/device/edid2 (for second monitor, if any). > > -Which mode gets choosen from the resulting set of resolutions? I mean, > > based on what? > > Depends on the driver. A combination of the 'first detailed timing > is preferred' flag and a detailed timing is the initial startup mode. > As for radeonfb, I think it just grabs the first detailed timing for > the initial mode. Yes, the selection goes like this: - mode option - 1st detailed block - 1st mode in the db Luca -- Home: http://kronoz.cjb.net Se alla sera, dopo una strepitosa vittoria, guardandoti allo specchio dovessi notare un secondo paio di palle, che il tuo cuore non si riempia d'orgoglio, perche` vuol dire che ti stanno inculando -- Saggio Cinese Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2006-06-27 19:11 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-06-20 14:01 radeonfb: DDC read wrong? Robert Siemer 2006-06-24 12:11 ` Antonino A. Daplas 2006-06-24 17:47 ` Robert Siemer 2006-06-24 21:33 ` Antonino A. Daplas 2006-06-24 21:56 ` Robert Siemer 2006-06-24 23:27 ` Antonino A. Daplas 2006-06-25 0:00 ` Antonino A. Daplas 2006-06-26 17:01 ` Robert Siemer 2006-06-26 20:55 ` Antonino A. Daplas 2006-06-27 19:11 ` Luca
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 NNTP newsgroup(s).