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

Bug#268352: marked as done (2.6.* radeonfb regression)



Your message dated Sat, 5 Feb 2005 23:50:04 +0100
with message-id <20050205225004.GA6123@frankie.is-a-geek.org>
and subject line [jpl@lucas.homelinux.org: Re: radeonfb blanking problem not present in 2.6.10]
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 27 Aug 2004 09:38:02 +0000
>From iesifl01@area.ba.cnr.it Fri Aug 27 02:38:00 2004
Return-path: <iesifl01@area.ba.cnr.it>
Received: from muffin.area.ba.cnr.it [150.145.80.101] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C0dBH-00055c-00; Fri, 27 Aug 2004 02:38:00 -0700
Received: from area.ba.cnr.it (localhost [127.0.0.1])
	by muffin.area.ba.cnr.it (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id i7R9j7EK027337
	for <submit@bugs.debian.org>; Fri, 27 Aug 2004 11:45:07 +0200
Received: (from iesifl01@localhost)
	by area.ba.cnr.it (8.12.10/8.12.10/Submit) id i7R9j73J027336
	for submit@bugs.debian.org; Fri, 27 Aug 2004 11:45:07 +0200
Date: Fri, 27 Aug 2004 11:45:07 +0200
From: "Francesco P. Lovergine" <frankie@debian.org>
To: submit@bugs.debian.org
Subject: 2.6.* radeonfb regression
Message-ID: <20040827094506.GD18386@ba.issia.cnr.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-GPG-key: finger frankie@db.debian.org
X-GPG-fingerprint: 92E4 2D44 336F DF91 5508  23D5 A453 5199 E9F2 C747
X-Spot: Who uses non-free software empoisons you, too. Say him to stop.
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

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. 


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro


-- 
Francesco P. Lovergine

---------------------------------------
Received: (at 268352-done) by bugs.debian.org; 5 Feb 2005 22:53:51 +0000
>From frankie@debian.org Sat Feb 05 14:53:51 2005
Return-path: <frankie@debian.org>
Received: from egg.area.ba.cnr.it [150.145.80.53] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CxYoJ-0003es-00; Sat, 05 Feb 2005 14:53:51 -0800
Received: from localhost (localhost [127.0.0.1])
	by egg.area.ba.cnr.it (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id j15MrkCH021741;
	Sat, 5 Feb 2005 23:53:46 +0100
Received: from klecker (klecker.ba.issia.cnr.it [150.145.84.32])
	by egg.area.ba.cnr.it (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id j15MrJjl021713;
	Sat, 5 Feb 2005 23:53:19 +0100
Received: from adsl-22-213.37-151.net24.it ([151.37.213.22] helo=localhost)
	by klecker with asmtp (Exim 4.34)
	id 1CxYnl-00059U-IP; Sat, 05 Feb 2005 23:53:17 +0100
Received: from frankie by localhost with local (Exim 4.44)
	id 1CxYko-0001cE-Tx; Sat, 05 Feb 2005 23:50:15 +0100
Date: Sat, 5 Feb 2005 23:50:04 +0100
From: Francesco Paolo Lovergine <frankie@debian.org>
To: 290775-done@bugs.debian.org, 268352-done@bugs.debian.org,
        benh@kernel.crashing.org, sven.luther@wanadoo.fr
Subject: [jpl@lucas.homelinux.org: Re: radeonfb blanking problem not present in 2.6.10]
Message-ID: <20050205225004.GA6123@frankie.is-a-geek.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Fingerprint: 92E4 2D44 336F DF91 5508  23D5 A453 5199 E9F2 C747
X-GPG-Info: finger frankie@db.debian.org
X-Advocacy: Who uses non-free software empoisons you too. Say him to stop.
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new-20041102+Sophos at egg.area.ba.cnr.it
Delivered-To: 268352-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Indeed, I also tried and verified. It is ok with latest 2.6.9 and current 2.6.10.
So closing.


----- Forwarded message from Jonathan Lucas <jpl@lucas.homelinux.org> -----

Subject: Re: radeonfb blanking problem not present in 2.6.10
From: Jonathan Lucas <jpl@lucas.homelinux.org>
To: Francesco Paolo Lovergine <frankie@debian.org>

I no longer have this problem. I thought the bug was closed months
ago...

cheers,

Jonathan

On Sat, 2005-02-05 at 09:06 +0100, Francesco Paolo Lovergine wrote:
> On Fri, Feb 04, 2005 at 08:07:27PM -0500, Jay Berkenbilt wrote:
> > 
> > For what it's worth, I recently upgraded my kernel to 2.6.10, and I no
> > longer see this problem (screen blank after loading radeonfb with a
> > Radeon 9600 -- original report mentioned 9200 SE).  I never ran 2.6.9,
> > so I can't say whether the problem was there.
> > 
> 
> Uh, nice I'll have a try ASAP. I just noticed that some problems with
> ACPI on this box disappeared too...
> 
-- 
Jonathan Lucas <jpl@lucas.homelinux.org>



----- End forwarded message -----

-- 
Francesco P. Lovergine



Reply to: