* HELP: Problem with radeonfb setting wrong resolution @ 2006-02-14 20:33 Timothy Miller 2006-02-14 22:20 ` Benjamin Herrenschmidt 0 siblings, 1 reply; 7+ messages in thread From: Timothy Miller @ 2006-02-14 20:33 UTC (permalink / raw) To: linux-kernel I humbly apologize if it is inappropriate for me to post this question here. I'm not subscribed, and I haven't been in a while. I've googled around for answers to this, but I don't find anything that directly addresses the issue I'm seeing. Please cc me. I'm installing a new Gentoo box, and I have configured the 2.6.12-gentoo-r6 kernel. Here's what I have enabled: + Support for framebuffer devices + ATI Radeon display support + DDC/I2C for ATI Radeon support + Lots of debug output from Radeon drive + VGA text console + Framebuffer Console support In the grub.conf file, I have this at the end of the kernel line: video=radeonfb:1024x768 When booting up, radeonfb finds the device (A Radeon 7000 PCI card), the monitor flickers for a second, and then what I get is a 640x480 screen, but the kernel seems to think it's 1024x768, because text goes off the screen. I've googled for this, but what I find is old stuff where people are complaining about seeing a higher resolution than the one they asked for. I'm getting a LOWER resolution. I can't figure out what I'm doing wrong, but there are no kernel error messages that tell me anything has gone wrong. Can anyone help me figure out what I'm doing wrong here? BTW, the monitor is a 19" NEC. No chance that the monitor reports via DDC that it can't do 1024x768. Thanks. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-14 20:33 HELP: Problem with radeonfb setting wrong resolution Timothy Miller @ 2006-02-14 22:20 ` Benjamin Herrenschmidt 2006-02-15 2:17 ` Timothy Miller 0 siblings, 1 reply; 7+ messages in thread From: Benjamin Herrenschmidt @ 2006-02-14 22:20 UTC (permalink / raw) To: Timothy Miller; +Cc: linux-kernel On Tue, 2006-02-14 at 15:33 -0500, Timothy Miller wrote: > I humbly apologize if it is inappropriate for me to post this question > here. I'm not subscribed, and I haven't been in a while. I've > googled around for answers to this, but I don't find anything that > directly addresses the issue I'm seeing. Please cc me. > > I'm installing a new Gentoo box, and I have configured the > 2.6.12-gentoo-r6 kernel. > > Here's what I have enabled: > > + Support for framebuffer devices > + ATI Radeon display support > + DDC/I2C for ATI Radeon support > + Lots of debug output from Radeon drive > + VGA text console > + Framebuffer Console support > > In the grub.conf file, I have this at the end of the kernel line: > > video=radeonfb:1024x768 > > When booting up, radeonfb finds the device (A Radeon 7000 PCI card), > the monitor flickers for a second, and then what I get is a 640x480 > screen, but the kernel seems to think it's 1024x768, because text goes > off the screen. > > I've googled for this, but what I find is old stuff where people are > complaining about seeing a higher resolution than the one they asked > for. I'm getting a LOWER resolution. > > I can't figure out what I'm doing wrong, but there are no kernel error > messages that tell me anything has gone wrong. > > Can anyone help me figure out what I'm doing wrong here? BTW, the > monitor is a 19" NEC. No chance that the monitor reports via DDC that > it can't do 1024x768. Can you send me the debug output ? (dmesg) Ben. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-14 22:20 ` Benjamin Herrenschmidt @ 2006-02-15 2:17 ` Timothy Miller 2006-02-15 5:32 ` Antonino A. Daplas 0 siblings, 1 reply; 7+ messages in thread From: Timothy Miller @ 2006-02-15 2:17 UTC (permalink / raw) To: Benjamin Herrenschmidt; +Cc: linux-kernel On 2/14/06, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > On Tue, 2006-02-14 at 15:33 -0500, Timothy Miller wrote: > > I humbly apologize if it is inappropriate for me to post this question > > here. I'm not subscribed, and I haven't been in a while. I've > > googled around for answers to this, but I don't find anything that > > directly addresses the issue I'm seeing. Please cc me. > > > > I'm installing a new Gentoo box, and I have configured the > > 2.6.12-gentoo-r6 kernel. > > > > Here's what I have enabled: > > > > + Support for framebuffer devices > > + ATI Radeon display support > > + DDC/I2C for ATI Radeon support > > + Lots of debug output from Radeon drive > > + VGA text console > > + Framebuffer Console support > > > > In the grub.conf file, I have this at the end of the kernel line: > > > > video=radeonfb:1024x768 > > > > When booting up, radeonfb finds the device (A Radeon 7000 PCI card), > > the monitor flickers for a second, and then what I get is a 640x480 > > screen, but the kernel seems to think it's 1024x768, because text goes > > off the screen. > > > > I've googled for this, but what I find is old stuff where people are > > complaining about seeing a higher resolution than the one they asked > > for. I'm getting a LOWER resolution. > > > > I can't figure out what I'm doing wrong, but there are no kernel error > > messages that tell me anything has gone wrong. > > > > Can anyone help me figure out what I'm doing wrong here? BTW, the > > monitor is a 19" NEC. No chance that the monitor reports via DDC that > > it can't do 1024x768. > > Can you send me the debug output ? (dmesg) > I just installed 2.6.15-gentoo-5, so I have a much more recent kernel. This strange behavior still happens. I forgot to mention that I'm using this on an P4, and the kernel is compiled 64-bit. I sent Ben a copy of the whole dmesg output. Here's the portion that everyone else might be interested in: radeonfb_pci_register BEGIN ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 21 (level, low) -> IRQ 193 radeonfb (0000:02:05.0): Found 65536k of DDR 64 bits wide videoram radeonfb (0000:02:05.0): mapped 16384k videoram radeonfb: Found Intel x86 BIOS ROM Image radeonfb: Retreived PLL infos from BIOS radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=150.00 Mhz, System=150.00 MHz radeonfb: PLL min 12000 max 35000 1 chips in connector info - chip 1 has 2 connectors * connector 0 of type 2 (CRT) : 2300 * connector 1 of type 3 (DVI-I) : 3201 Starting monitor auto detection... radeonfb: I2C (port 1) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 3) ... found TMDS panel radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 3) ... found TMDS panel radeonfb: Monitor 1 type DFP found radeonfb: EDID probed radeonfb: Monitor 2 type no found Parsing EDID data for panel info Guessing panel info... radeonfb: Assuming panel size 8x1 hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf Console: switching to colour frame buffer device 128x48 radeonfb (0000:02:05.0): ATI Radeon QY radeonfb_pci_register END ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-15 2:17 ` Timothy Miller @ 2006-02-15 5:32 ` Antonino A. Daplas 2006-02-15 12:44 ` Timothy Miller 2006-02-15 12:48 ` Timothy Miller 0 siblings, 2 replies; 7+ messages in thread From: Antonino A. Daplas @ 2006-02-15 5:32 UTC (permalink / raw) To: Timothy Miller; +Cc: Benjamin Herrenschmidt, linux-kernel Timothy Miller wrote: > On 2/14/06, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: >> On Tue, 2006-02-14 at 15:33 -0500, Timothy Miller wrote: >>> I humbly apologize if it is inappropriate for me to post this question >>> here. I'm not subscribed, and I haven't been in a while. I've >>> googled around for answers to this, but I don't find anything that >>> directly addresses the issue I'm seeing. Please cc me. >>> >>> I'm installing a new Gentoo box, and I have configured the >>> 2.6.12-gentoo-r6 kernel. >>> >>> Here's what I have enabled: >>> >>> + Support for framebuffer devices >>> + ATI Radeon display support >>> + DDC/I2C for ATI Radeon support >>> + Lots of debug output from Radeon drive >>> + VGA text console >>> + Framebuffer Console support >>> >>> In the grub.conf file, I have this at the end of the kernel line: >>> >>> video=radeonfb:1024x768 >>> >>> When booting up, radeonfb finds the device (A Radeon 7000 PCI card), >>> the monitor flickers for a second, and then what I get is a 640x480 >>> screen, but the kernel seems to think it's 1024x768, because text goes >>> off the screen. >>> >>> I've googled for this, but what I find is old stuff where people are >>> complaining about seeing a higher resolution than the one they asked >>> for. I'm getting a LOWER resolution. >>> >>> I can't figure out what I'm doing wrong, but there are no kernel error >>> messages that tell me anything has gone wrong. >>> >>> Can anyone help me figure out what I'm doing wrong here? BTW, the >>> monitor is a 19" NEC. No chance that the monitor reports via DDC that >>> it can't do 1024x768. >> Can you send me the debug output ? (dmesg) >> > > I just installed 2.6.15-gentoo-5, so I have a much more recent kernel. > This strange behavior still happens. I forgot to mention that I'm > using this on an P4, and the kernel is compiled 64-bit. > > I sent Ben a copy of the whole dmesg output. Here's the portion that > everyone else might be interested in: > > radeonfb_pci_register BEGIN > ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 21 (level, low) -> IRQ 193 > radeonfb (0000:02:05.0): Found 65536k of DDR 64 bits wide videoram > radeonfb (0000:02:05.0): mapped 16384k videoram > radeonfb: Found Intel x86 BIOS ROM Image > radeonfb: Retreived PLL infos from BIOS > radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=150.00 Mhz, System=150.00 MHz > radeonfb: PLL min 12000 max 35000 > 1 chips in connector info > - chip 1 has 2 connectors > * connector 0 of type 2 (CRT) : 2300 > * connector 1 of type 3 (DVI-I) : 3201 > Starting monitor auto detection... > radeonfb: I2C (port 1) ... not found > radeonfb: I2C (port 2) ... not found > radeonfb: I2C (port 3) ... found TMDS panel > radeonfb: I2C (port 4) ... not found > radeonfb: I2C (port 2) ... not found > radeonfb: I2C (port 4) ... not found > radeonfb: I2C (port 3) ... found TMDS panel > radeonfb: Monitor 1 type DFP found > radeonfb: EDID probed > radeonfb: Monitor 2 type no found > Parsing EDID data for panel info > Guessing panel info... > radeonfb: Assuming panel size 8x1 ^^^ Looks like an EDID problem. Can you change #undef DEBUG to #define DEBUG in drivers/video/fbmon.c and post your dmesg again? Tony ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-15 5:32 ` Antonino A. Daplas @ 2006-02-15 12:44 ` Timothy Miller 2006-02-15 12:48 ` Timothy Miller 1 sibling, 0 replies; 7+ messages in thread From: Timothy Miller @ 2006-02-15 12:44 UTC (permalink / raw) To: Antonino A. Daplas; +Cc: Benjamin Herrenschmidt, linux-kernel On 2/15/06, Antonino A. Daplas <adaplas@gmail.com> wrote: > > Looks like an EDID problem. Can you change #undef DEBUG to #define DEBUG > in drivers/video/fbmon.c and post your dmesg again? > Well, I did what you asked. I modified the file, recompiled the kernel (fbmon.o did get rebuilt), and copied over the kernel. I don't see any extra messages in here, however. I looked through dmesg elsewhere, and didn't find anything that seemed to relate. I double-checked what I did, but no change. Here's the only stuff I can find in dmesg that seems to relate to video: radeonfb_pci_register BEGIN GSI 17 sharing vector 0xC1 and IRQ 17 ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 21 (level, low) -> IRQ 193 radeonfb (0000:02:05.0): Found 65536k of DDR 64 bits wide videoram radeonfb (0000:02:05.0): mapped 16384k videoram radeonfb: Found Intel x86 BIOS ROM Image radeonfb: Retreived PLL infos from BIOS radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=150.00 Mhz, System=150.00 MHz radeonfb: PLL min 12000 max 35000 1 chips in connector info - chip 1 has 2 connectors * connector 0 of type 2 (CRT) : 2300 * connector 1 of type 3 (DVI-I) : 3201 Starting monitor auto detection... radeonfb: I2C (port 1) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 3) ... found TMDS panel radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 2) ... not found radeonfb: I2C (port 4) ... not found radeonfb: I2C (port 3) ... found TMDS panel radeonfb: Monitor 1 type DFP found radeonfb: EDID probed radeonfb: Monitor 2 type no found Parsing EDID data for panel info Guessing panel info... radeonfb: Assuming panel size 8x1 hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf hStart = 664, hEnd = 760, hTotal = 800 vStart = 409, vEnd = 411, vTotal = 450 h_total_disp = 0x4f0063 hsync_strt_wid = 0x8c0292 v_total_disp = 0x18f01c1 vsync_strt_wid = 0x820198 pixclock = 39729 freq = 2517 freq = 2517, PLL min = 12000, PLL max = 35000 ref_div = 60, ref_clk = 2700, output_freq = 20136 ref_div = 60, ref_clk = 2700, output_freq = 20136 post div = 0x3 fb_div = 0x1bf ppll_div_3 = 0x301bf Console: switching to colour frame buffer device 128x48 radeonfb (0000:02:05.0): ATI Radeon QY radeonfb_pci_register END Thanks. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-15 5:32 ` Antonino A. Daplas 2006-02-15 12:44 ` Timothy Miller @ 2006-02-15 12:48 ` Timothy Miller 2006-02-15 20:41 ` Antonino A. Daplas 1 sibling, 1 reply; 7+ messages in thread From: Timothy Miller @ 2006-02-15 12:48 UTC (permalink / raw) To: Antonino A. Daplas; +Cc: Benjamin Herrenschmidt, linux-kernel On 2/15/06, Antonino A. Daplas <adaplas@gmail.com> wrote: > > Looks like an EDID problem. Can you change #undef DEBUG to #define DEBUG > in drivers/video/fbmon.c and post your dmesg again? You were right. It's an edid problem. I disabled DDC/I2C for Radeon, and the problem cleared right up. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: HELP: Problem with radeonfb setting wrong resolution 2006-02-15 12:48 ` Timothy Miller @ 2006-02-15 20:41 ` Antonino A. Daplas 0 siblings, 0 replies; 7+ messages in thread From: Antonino A. Daplas @ 2006-02-15 20:41 UTC (permalink / raw) To: Timothy Miller; +Cc: Benjamin Herrenschmidt, linux-kernel Timothy Miller wrote: > On 2/15/06, Antonino A. Daplas <adaplas@gmail.com> wrote: > >> Looks like an EDID problem. Can you change #undef DEBUG to #define DEBUG >> in drivers/video/fbmon.c and post your dmesg again? > > You were right. It's an edid problem. I disabled DDC/I2C for Radeon, > and the problem cleared right up. > Something did come out from the DDC bus (as per radeonfb messages) but it probably failed the checksum/header test so no extra messages were seen. Unless the EDID is totally bogus, this can be a fixable problem. Can you send me the EDID dump? You can use the utility read-edid for this. Tony ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-02-15 20:41 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-02-14 20:33 HELP: Problem with radeonfb setting wrong resolution Timothy Miller 2006-02-14 22:20 ` Benjamin Herrenschmidt 2006-02-15 2:17 ` Timothy Miller 2006-02-15 5:32 ` Antonino A. Daplas 2006-02-15 12:44 ` Timothy Miller 2006-02-15 12:48 ` Timothy Miller 2006-02-15 20:41 ` Antonino A. Daplas
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox