From owner-freebsd-stable@FreeBSD.ORG Thu Jan 29 14:20:08 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D0201065672; Thu, 29 Jan 2009 14:20:08 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by mx1.freebsd.org (Postfix) with ESMTP id AA3868FC1F; Thu, 29 Jan 2009 14:20:07 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=d1KX9u3KBSJbiMrdhMsY+NJYG+tk2grhm97742U8iBcUpQH60YANbRP5rCzDrNv5; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.246] (helo=joker.seclark.com) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1LSWkW-0003oU-Ky; Thu, 29 Jan 2009 08:16:04 -0500 Message-ID: <4981AC13.2040300@earthlink.net> Date: Thu, 29 Jan 2009 08:16:03 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Alex Goncharov References: <6B7ABE80-35AB-4C44-B5A4-200E10DCC3AC@airwired.net> <49819BD5.5040709@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec790b6138ff94354d05a45997a2c494d9cd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.246 Cc: freebsd-stable@freebsd.org, danallen46@airwired.net, "Bruce M. Simpson" , freebsd-ports@freebsd.org Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 14:20:08 -0000 Alex Goncharov wrote: > ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +0000) ----* > | One theory is that somehow the mouse driver ioctls which are passed > | to ums, are somehow hosing USB, although why that would be, I don't > | understand. ums currently doesn't have driver instrumentation in that path. > | > | I pulled a fairly detailed IRC log of my collaborative debugging > | session with Robert, please ping me if you need details of this. > `----------------------------------------------------* > > Thank you for the detailed write up! No help to me, though -- on my > Latitude laptop, there was no problem with any mouse: USB or the > built-in "pointing device". It was the keyboard -- and, trust me, I > did try many variations of the machine configuration, and I did do a > lot of reading on various relevant topics (writing, too, as you have > seen :-() > > As I mentioned elsewhere, my way of resolving the problem after a > one-and-a-half day's of struggle was to revert to the old X (on that > laptop). > > On the topic of how this upgrade was introduced, I can't help but > refer to my recent experience helping to fix TWM: > > ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) ----* > | > I have used the new version of TWM for five days, using it less > | > intensively than usual. No problems in seen during my (light) use. > | > | Hello Alex, no problem at all! Improved solutions have priority over > | promised deadlines. > | > | Thank you for your time helping to improve TWM, :-) > | > `----------------------------------------------------* > > Eeri Kask and I worked together all past September on fixing TWM > crashes: I was willingly trying his multiple versions of the code, but > I knew what I was risking, could choose convenient times for building > and trying every new version (we tried about 30 of them) -- and I > could always go back to the previous version (or the original TWM from > ports). > > I would be happy to try a new X on my machines, if it were labeled as > experimental, with an easy way to revert to the old X (while being in > the testing stage). As it is, this upgrade brought a lot of problems > to unsuspecting people, at the time they don't quite choose, with > potential dangers not disclosed. > > In honesty, this upgrade should have been presented this way, way > before the code was placed in the ports source tree: > > * We'll have a new X in ports soon -- there are multiple reports of > problems with it on Linux. > > * We want to try it on FreeBSD -- but nobody is forcing you to do the > upgrade. > > * If you, of your own free will, choose to upgrade, you may have > hours and days of problems -- but heck, it was your choice. > > * If your problems cannot be fixed, you'll have to figure out > something yourself. > > * If you choose not to upgrade, you are frozen with the pre-existing > ports collection: there may be no automated ways to upgrade your > packages, with the old X in place. Of course, you can somehow get > pieces on new ports, unrelated to X. > > * The choice is totally yours. > > -- Alex -- alex-goncharov@comcast.net -- > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > On my system the matrox driver quit working, when I tried using the built in via the via driver wouldn't compile so when I tried X -configure it generated a config using vesa, but when I tried to start X with the xorg.conf.new with the vesa driver X said it couldn't find any screens. I finally had to revert back to an older version. This should not happen on a stable system. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson)