[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#268352: 2.6.* radeonfb regression



On Sat, Sep 11, 2004 at 02:55:15PM +0200, Francesco P. Lovergine wrote:
> On Mon, Aug 30, 2004 at 11:17:36PM +0200, Francesco Paolo Lovergine wrote:
> > > > Package: kernel
> > > > Severity: normal
> > > > 
> > > > 2.4 series radeonfb (1.8-benh) works perfectly (also modular).
> > > > 2.6 series new radeonfb never worked (since 2.6.0 at least), it does not sync here (laptop XSVGA).
> > > > After loading, fbset reports 1400x1050-60, as for the 2.4 version, but screen
> > > > is blank and stay in normal text mode 80x25. I need to switch on and back to X in order to
> > > > see screen content again. That's for loading it modular of course, I have to do yet test
> > > > for static version.
> > > > 
> > > > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY
> > > > 
> > > > 0000:01:00.0 0300: 1002:4c59
> > > >         Subsystem: 0e11:b11b
> > > >         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping+ SERR+ FastB2B+
> > > >         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > > >         Interrupt: pin A routed to IRQ 9
> > > >         Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
> > > >         Region 1: I/O ports at 2000 [size=256]
> > > >         Region 2: Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
> > > >         Expansion ROM at <unassigned> [disabled] [size=128K]
> > > >         Capabilities: <available only to root>
> > > > 
> > > > In dmesg:
> > > > 
> > > > Aug 18 19:06:41 localhost kernel: radeonfb: Retreived PLL infos from BIOS
> > > > Aug 18 19:06:41 localhost kernel: radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=143.00 MHz
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 1 type LCD found
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: EDID probed
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 2 type no found
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: panel ID string: Samsung LTN150P1-L02
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: detected LVDS panel size from BIOS: 1400x1050
> > > > Aug 18 19:06:42 localhost kernel: radeondb: BIOS provided dividers will be used
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: Power Management enabled for Mobility chipsets
> > > > Aug 18 19:06:42 localhost kernel: radeonfb: ATI Radeon LY  DDR SGRAM 32 MB
> > > > 
> > > > This is with current 2.6.8 in debian, but that's true with _all_ other previous versions (2.6.0+).
> > > > 
> > > > fbset return right mode, as set in /etc/fb.modes too:
> > > > 
> > > > mode "1400x1050-60"
> > > >     # D: 108.003 MHz, H: 63.983 kHz, V: 60.191 Hz
> > > >     geometry 1400 1050 1400 1050 8
> > > >     timings 9259 136 40 10 0 112 3
> > > >     rgba 6/0,6/0,6/0,0/0
> > > >     hsync high
> > > >     vsync high
> > > >     accel true
> > > > endmode
> > > > 
> > > > I tried to fbset explicitly the mode after module loading too, but without results.
> > > > I'll return results with static compiled in module when possible. 
> > > > 
> > 
> > 
> > Ok, I tried with radeonfb statically compiled in. Same results. 
> > Display images disappeared a few messages after boot and reappeared
> > later (in 80x25) when console fonts are loaded, I think.
> > fbset again return a 1400x1050-60 mode active...
> > 
> 
> As suggested by Sveni, I'm sending full info with radeonfb debug mode on.

Just Sven will do :).

> I'm having the same problem on a HP Pavilion zt3020EA, which has an ATI
> Radeon 9000 chipset. Native res is 1280x800. Again blank screen with
> cursor moving on it, and all working fine in 2.4 or X. The problem apparently
> is the same so I'm sending a followup for that.

Mmm, Can you clarify if it works fine in 1280x800 mode or not ? I have some
doubts about the wisdom of using an LCD with bigger than native resolution.

> Sep 11 13:38:41 pavilion kernel: radeonfb_pci_register BEGIN
> Sep 11 13:38:41 pavilion kernel: ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 10 (level, low) -> IRQ 10
> Sep 11 13:38:41 pavilion kernel: radeonfb: probed DDR SGRAM 65536k videoram
> Sep 11 13:38:41 pavilion kernel: radeonfb: mapped 16384k videoram
> Sep 11 13:38:41 pavilion kernel: radeonfb: Retreived PLL infos from BIOS
> Sep 11 13:38:41 pavilion kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=250.00 Mhz, System=220.00 MHz
> Sep 11 13:38:41 pavilion kernel: 1 chips in connector info
> Sep 11 13:38:41 pavilion kernel:  - chip 1 has 1 connectors
> Sep 11 13:38:41 pavilion kernel:   * connector 0 of type 2 (CRT) : 2300
> Sep 11 13:38:41 pavilion kernel: Starting monitor auto detection...
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 1) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 2) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 3) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 4) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 2) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 4) ... not found
> Sep 11 13:38:41 pavilion kernel: Non-DDC laptop panel detected

Oh well, so the panel is not sending DDC info, and thus can't give radeonfb
info about maximum and minimum frequencies.

Benh, do you know how the monitor frequencies are detected in non-DDC mode ? 

> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 3) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: I2C (port 4) ... not found
> Sep 11 13:38:41 pavilion kernel: radeonfb: Monitor 1 type LCD found
> Sep 11 13:38:41 pavilion kernel: radeonfb: Monitor 2 type no found
> Sep 11 13:38:41 pavilion kernel: radeonfb: panel ID string: CMO Color LCD
> Sep 11 13:38:41 pavilion kernel:
> Sep 11 13:38:41 pavilion kernel: radeonfb: detected LVDS panel size from BIOS: 1280x800
> Sep 11 13:38:41 pavilion kernel: BIOS provided panel power delay: 1000
> Sep 11 13:38:41 pavilion kernel: radeondb: BIOS provided dividers will be used
> Sep 11 13:38:41 pavilion kernel: ref_divider = 6
> Sep 11 13:38:41 pavilion kernel: post_divider = 2
> Sep 11 13:38:41 pavilion kernel: fbk_divider = 3f
> Sep 11 13:38:41 pavilion kernel: Scanning BIOS table ...
> Sep 11 13:38:41 pavilion kernel:  320 x 350
> Sep 11 13:38:41 pavilion kernel:  320 x 400
> Sep 11 13:38:41 pavilion kernel:  320 x 400
> Sep 11 13:38:41 pavilion kernel:  320 x 480
> Sep 11 13:38:41 pavilion kernel:  400 x 600
> Sep 11 13:38:41 pavilion kernel:  512 x 384
> Sep 11 13:38:41 pavilion kernel:  640 x 350
> Sep 11 13:38:41 pavilion kernel:  640 x 400
> Sep 11 13:38:41 pavilion kernel:  640 x 475
> Sep 11 13:38:41 pavilion kernel:  640 x 480
> Sep 11 13:38:41 pavilion kernel:  720 x 480
> Sep 11 13:38:41 pavilion kernel:  720 x 576
> Sep 11 13:38:41 pavilion kernel:  800 x 600
> Sep 11 13:38:41 pavilion kernel:  848 x 480
> Sep 11 13:38:41 pavilion kernel:  1024 x 768
> Sep 11 13:38:41 pavilion kernel:  1280 x 800
> Sep 11 13:38:41 pavilion kernel: Found panel in BIOS table:
> Sep 11 13:38:41 pavilion kernel:   hblank: 160
> Sep 11 13:38:41 pavilion kernel:   hOver_plus: 48
> Sep 11 13:38:41 pavilion kernel:   hSync_width: 32
> Sep 11 13:38:41 pavilion kernel:   vblank: 23
> Sep 11 13:38:41 pavilion kernel:   vOver_plus: 2
> Sep 11 13:38:41 pavilion kernel:   vSync_width: 6
> Sep 11 13:38:41 pavilion kernel:   clock: 7100
> Sep 11 13:38:41 pavilion kernel: Setting up default mode based on panel info

I suppose the above info is related to the default mode. 

Friendly,

Sven Luther



Reply to: