From owner-freebsd-current@FreeBSD.ORG Fri May 9 00:13:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 429CC37B401; Fri, 9 May 2003 00:13:46 -0700 (PDT) Received: from vineyard.net (k1.vineyard.net [204.17.195.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F7B14400D; Fri, 9 May 2003 00:13:45 -0700 (PDT) (envelope-from joshe@jade.elsasser.org) Received: from localhost (loopback [127.0.0.1]) by vineyard.net (Postfix) with ESMTP id 42DB59157D; Fri, 9 May 2003 03:13:44 -0400 (EDT) Received: from vineyard.net ([127.0.0.1]) by localhost (king1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67795-07; Fri, 9 May 2003 03:13:44 -0400 (EDT) Received: from jade.elsasser.org (adsl-141-154-85-190.ba-dsg.net [141.154.85.190]) by vineyard.net (Postfix) with ESMTP id C247091511; Fri, 9 May 2003 03:13:43 -0400 (EDT) Received: by jade.elsasser.org (Postfix, from userid 1000) id 7A250147792; Fri, 9 May 2003 02:57:29 -0400 (EDT) Date: Fri, 9 May 2003 02:57:29 -0400 From: Josh Elsasser To: Daniel Eischen Message-ID: <20030509065729.GA5877@jade.nat.elsasser.org> References: <20030504.200453.99587468.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-PGP-Key-URL: http://www.elsasser.org/pubkey.asc X-PGP-Key-Fingerprint: 8F39 9F2B 3738 54D9 3E40 4604 CFD5 EA3F B833 FD50 X-Virus-Scanned: by AMaViS at Vineyard.NET cc: anholt@freebsd.org cc: mb@imp.ch cc: current@freebsd.org cc: "M. Warner Losh" Subject: Re: ACPI-Sleep broken for radeon mobility chips ? (on Current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 07:13:46 -0000 On Mon, May 05, 2003 at 12:23:04AM -0400, Daniel Eischen wrote: > On Sun, 4 May 2003, M. Warner Losh wrote: > > > In message: <20030504123034.O33100@cvs.imp.ch> > > Martin Blapp writes: > > : > > : Hi all, > > : > > : I have these two problems: > > : > > : - Black screen in the console after wakeup. Console is dead. > > : - Shaded screen in X which turns white after a while with nice patterns on it > > : after wakeup. > > : > > : OS is still alive. One can login over the network and reboot. > > : > > : Looks like other people got the same problem: > > : > > : http://groups.google.com/groups?q=vga0+radeon+freebsd&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=20030217230308.GA594_lenny.anarcat.ath.cx%40ns.sol.net&rnum=9 > > : > > : Does anyone of you know what the problem is exactly ? > > : > > : Here are the dmesg parts: > > : > > : VESA: v2.0, 65536k memory, flags:0x1, mode table:0xc04bdc82 (1000022) > > : VESA: ATI MOBILITY RADEON 9000 > > : > > : vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > : > > : drm0: port 0xa000-0xa0ff mem > > : 0xec100000-0xec10ffff,0 > > : xf0000000-0xf7ffffff irq 11 at device 0.0 on pci1 > > : info: [drm] AGP at 0xe8000000 64MB > > : info: [drm] Initialized radeon 1.8.0 20020828 on minor 0 > > : > > : I tried tried to turn of dri, agp and vesa modules, but with out without > > : makes zero difference. > > > > I have the same problem with my machine as well: > > > > drm0: port 0xcc00-0xccff mem 0xfcffc000-0xfcffffff,0xe8000000-0xebffffff irq 11 at device 0.0 on pci1 > > info: [drm] AGP at 0xe4000000 64MB > > info: [drm] Initialized r128 2.3.0 20021029 on minor 0 > > > > It is one reason that suspend/resume for cardbus breaks sometimes > > mysteriously... > > Same for my Inspiron 4150 (also ATI Rage 128 Mobility MF). > > One other note, the screen does go blank in Windows XP also. Even if > I set the BIOS (rev A05) to disable it when plugged in. It sometimes > takes a day or two for it to get in this mode, but once there, it > always blanks after a few minutes. Moving the mouse, pressing keys, > etc do nothing to refresh the screen. I can login remotely, and > key presses are responded to (I can reboot the machine as long as > was in an xterm), but I just can't see what I'm doing. When it's > real bad, the screen will blank while I'm using it and sometimes > every minute or so. The only way to get it back is Fn + F5 then > Escape out of the menu. > > I do get the white screen every now and then also, when > suspending and resuming. But I think the blank screen is > a BIOS bug. I have this same problem, on a Sony Vaio with i815 graphics. Aside from the display, the machine appears to resume fine. I can halt or reboot the machine by typing blind or logging in remotely. -jre