From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 22 22:40:18 2006 Return-Path: X-Original-To: freebsd-mobile@FreeBSD.ORG 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 E11E816A47E for ; Fri, 22 Sep 2006 22:40:18 +0000 (UTC) (envelope-from markus.hoenicka@mhoenicka.de) Received: from mx1.augustakom.net (mx1.augustakom.net [80.81.6.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2884743D53 for ; Fri, 22 Sep 2006 22:40:17 +0000 (GMT) (envelope-from markus.hoenicka@mhoenicka.de) Received: from 215.1-dial.augustakom.net ([80.81.1.215] helo=yeti.mininet) by mx1.augustakom.net with esmtp (Exim 4.62) (envelope-from ) id 1GQtgf-000139-9z for freebsd-mobile@FreeBSD.ORG; Fri, 22 Sep 2006 22:40:02 +0000 X-Mailer: emacs 21.3.1 (via feedmail 8 I); VM 7.19 under Emacs 21.3.1 From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17684.26155.124036.771316@yeti.mininet> Date: Sat, 23 Sep 2006 00:39:39 +0200 To: freebsd-mobile@FreeBSD.ORG In-Reply-To: <200609220942.k8M9gAlG079087@lurza.secnetix.de> References: <1158783978.4511a3ea1f22f@www.domainfactory-webmail.de> <200609220942.k8M9gAlG079087@lurza.secnetix.de> X-SA-Exim-Connect-IP: 80.81.1.215 X-SA-Exim-Mail-From: markus.hoenicka@mhoenicka.de X-SA-Exim-Scanned: No (on mx1.augustakom.net); SAEximRunCond expanded to false Cc: Subject: Re: Xorg (i810) freezes randomly when using hardware accel X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 22:40:19 -0000 Oliver Fromme writes: > > Section "Device" > > Identifier "truei810" > > Driver "i810" > > VideoRam 131072 > > # Insert Clocks lines here if appropriate > > EndSection > > I think you should _not_ override the VideoRam. Let it > autodetect the amount of video RAM. > I was under the impression that there is no autodetection in the case of shared video ram. In any case, using a different VideoRam setting or none at all does not change the problem. Googling for the Xorg error message gave a few hits, e.g. https://launchpad.net/distros/ubuntu/+source/xserver-xorg-video-i810/+bug/22741 which makes me think this is not a FreeBSD-specific problem. Moreover, it is likely to get fixed in a new release. So what I'd like to focus on is how I can get my console back after X got stuck. > > No. It doesn't show up in the process list, so I assume it exits with an error > > right away. > > You assume? I'm pretty sure there _must_ be something in > the logs, or an error message on stdout/stderr when you try > to start the X server. (BTW, how do you start it?) > I tried both ways you suggested: 1) run startx blindly. The login test told me that the box still listens to keypresses, so I assumed this might work 2) log in via ssh and run startx You mentioned that you run FreeBSD 6.1. Does that mean > 6.1-RELEASE? If yes, you should consider updating to > RELENG_6 ("6-stable"), which is currently in code freeze > for the 6.2 release cycle. I'm running it on my notebook, > too. > FreeBSD yeti.mininet 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Mon Aug 28 22:24:48 CEST 2006 markus@yeti.mininet:/usr/src/sys/i386/compile/YETI i386 > Did you try the VESA mode suggestion? What happened? It > should either reset the screen mode, or print an error > message (if VESA isn't supported). > I tried the vidcontrol stuff without X. Setting 80x25 or VGA_80x25 does work, whereas VESA_132x25 causes an error message saying VESA is not supported. However, if I try one of these suggestions after X froze (either blindly or through ssh) the screen is not affected except that it sometime goes from all white to all black. regards, Markus -- Markus Hoenicka markus.hoenicka@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de