From owner-freebsd-questions@FreeBSD.ORG Tue Jul 22 05:28:27 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EF4E0D11 for ; Tue, 22 Jul 2014 05:28:27 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B03492C0F for ; Tue, 22 Jul 2014 05:28:27 +0000 (UTC) Received: from r56.edvax.de (port-92-195-69-249.dynamic.qsc.de [92.195.69.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id E7100250AE; Tue, 22 Jul 2014 07:28:24 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s6M5SN3h002837; Tue, 22 Jul 2014 07:28:24 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 22 Jul 2014 07:28:23 +0200 From: Polytropon To: David Benfell Subject: Re: SOLVED: Re: All of a sudden, problems with X Message-Id: <20140722072823.5c6eeb4c.freebsd@edvax.de> In-Reply-To: <20140722052137.3FF3A12C10D0@mail.parts-unknown.org> References: <20140722024643.GA29536@munich.parts-unknown.org> <20140722051423.0cf369b9.freebsd@edvax.de> <20140722040440.GA16353@munich.parts-unknown.org> <20140722061900.008b35db.freebsd@edvax.de> <20140722052137.3FF3A12C10D0@mail.parts-unknown.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2014 05:28:28 -0000 On Mon, 21 Jul 2014 22:21:36 -0700, David Benfell wrote: > Polytropon writes: > > > > The easiest thing now would be to remove X and > > > > a) install it _and_ its dependencies from ports, > > ports tree updated of course > > I think this is what I did. The command I used was: > > portmaster -w -r xorg-server > > The problem reported here now seems to be solved. I have a mouse again. After a ports tree update, this would be the clean solution. All dependencies (like xf86-input-keyboard and xf86-input-mouse) will then be "in sync" again with the other X components. > I > haven't tried Xorg -configure, but I've got fluxbox working from startx > again. If your X works without a xorg.conf, you can omit this step. > And I haven't tried gdm to see if all this latest has fixed whatever > was wrong there. You could try xdm as a graphical login manager (I use it myself on my home desktop - it's fast and free of bloat). > It does seem there are some gotchas with this latest version of Xorg. One > is that it attempts to respond to my mismatched dual-head setup. It didn't > get screen dimensions right at all and fell back to an ugly common > denominator. It happens the big beautiful screen is destined for a server > that should be arriving in a couple days anyway, so I'm just disconnecting > it a bit early. The small notebook screen will suffice until then. For settings like dual-screen, having a _partial_ xorg.conf might be a usable solution, i. e., you only define those parts like screen location and dimensions as needed, and have X and HAL recognize automatically all the other parts for the setup. I'm going with a HAL-less X myself at home, with xorg.conf and two 21" CRTs so old that no autodetection magic will ever work, so "the old way" is still possible if technically required. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...