From owner-freebsd-mobile@FreeBSD.ORG Thu Oct 21 14:59:25 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CEB16A4CF for ; Thu, 21 Oct 2004 14:59:25 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 489B543D39 for ; Thu, 21 Oct 2004 14:59:24 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail 4539 invoked by uid 65534); 21 Oct 2004 14:59:22 -0000 Received: from p5089FDD1.dip.t-dialin.net (EHLO ms.homeip.net) (80.137.253.209) by mail.gmx.net (mp022) with SMTP; 21 Oct 2004 16:59:22 +0200 X-Authenticated: #15946415 Received: from [10.0.0.13] (helo=[10.0.0.13]) by ms.homeip.net with asmtp (TLSv1:AES256-SHA:256) id 1CKePS-0005zz-5k for freebsd-mobile@freebsd.org; Thu, 21 Oct 2004 16:59:22 +0200 Message-ID: <4177CEC3.2020904@gmx.de> Date: Thu, 21 Oct 2004 16:59:15 +0200 From: Jochen Gensch User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org References: <4176DECC.70606@gmx.de> <20041021011752.GE10871@empiric.icir.org> <41779562.8020303@gmx.de> In-Reply-To: X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Turning off screen completely X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 14:59:25 -0000 Eric Kjeldergaard wrote: > There are 2 major factors that are involved. One is a driver from X. > This driver is at the root of (almost) all display issues that people > commonly write about. The other driver is a kernel driver for > FreeBSD. This driver is used for many things often including power > management and direct access. So which one is causing the trouble here then? Because AFAIK the new X.org 6.8 provides updated drivers for radeon cards... otherwise it is an radeon.ko module problem. Jochen