From owner-freebsd-i386@FreeBSD.ORG Sun Aug 16 07:20:03 2009 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 128BA10656A7 for ; Sun, 16 Aug 2009 07:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E2F048FC43 for ; Sun, 16 Aug 2009 07:20:02 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7G7K2QG014785 for ; Sun, 16 Aug 2009 07:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7G7K2Ac014784; Sun, 16 Aug 2009 07:20:02 GMT (envelope-from gnats) Resent-Date: Sun, 16 Aug 2009 07:20:02 GMT Resent-Message-Id: <200908160720.n7G7K2Ac014784@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Peter L. Belew" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6185106568C for ; Sun, 16 Aug 2009 07:10:15 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id C4B4C8FC4B for ; Sun, 16 Aug 2009 07:10:15 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n7G7AFuW066284 for ; Sun, 16 Aug 2009 07:10:15 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n7G7AFZD066271; Sun, 16 Aug 2009 07:10:15 GMT (envelope-from nobody) Message-Id: <200908160710.n7G7AFZD066271@www.freebsd.org> Date: Sun, 16 Aug 2009 07:10:15 GMT From: "Peter L. Belew" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: i386/137822: System crashes leaving X when running vesa driver for S3 Inc. VT8375 [ProSavage8 KM266/KL266] X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2009 07:20:03 -0000 >Number: 137822 >Category: i386 >Synopsis: System crashes leaving X when running vesa driver for S3 Inc. VT8375 [ProSavage8 KM266/KL266] >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Aug 16 07:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Peter L. Belew >Release: 7.1 >Organization: >Environment: FreeBSD willy.belew 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: This gBox computer runs Windows XP, Ubuntu Linux, and FreeBSD. I just configured X and Gnome on this system. Xorg -configure produced an xorg.conf file, to which I added some screen resolution information from the same file on the Ubuntu OS. The vesa driver was used. Before I added the xorg.conf file, the system was unable to find an appropriate screen mode. This is possibly because the Samsung SyncMaster 570S tft monitor I use does not provide sufficient information to the system regarding its possible sweep modes. I started X as root by entering gdm. This seemed to function all right, but on logging out or trying to shut down or reboot from Gnome, the system froze up. I had a similar experience earlier running Ubuntu, also using the vesa driver. In that case the problem was corrected by explicitly using a savage driver. The Ubuntu bug was filed as bug # 404330 ... https://bugs.launchpad.net/bugs/414330 >How-To-Repeat: Described above ... will provide more details if needed. The FreeBSD steps were essentially the same as for Ubuntu. >Fix: Possibly there is a driver specifically for this display card, rather than vesa. That was the solution on Linux. Because probing for the display fails, it's necessary to provide an explicit xorg.conf. >Release-Note: >Audit-Trail: >Unformatted: