Date: Thu, 29 Jan 2009 09:43:42 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: sclark46@earthlink.net Cc: "Bruce M. Simpson" <bms@freebsd.org>, danallen46@airwired.net, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org, Alex Goncharov <alex-goncharov@comcast.net> Subject: Re: Unhappy Xorg upgrade Message-ID: <1233240223.1779.49.camel@wombat.2hip.net> In-Reply-To: <4981AC13.2040300@earthlink.net> References: <6B7ABE80-35AB-4C44-B5A4-200E10DCC3AC@airwired.net> <E1LSP0B-0003Ds-H8@daland.home> <49819BD5.5040709@FreeBSD.org> <E1LSWHr-0009TS-P7@daland.home> <4981AC13.2040300@earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-dv9MjWZZzmssQTlS9Lzc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2009-01-29 at 08:16 -0500, Stephen Clark wrote: > Alex Goncharov wrote: > > ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +0000) ----* > > | One theory is that somehow the mouse driver ioctls which are pass= ed=20 > > | to ums, are somehow hosing USB, although why that would be, I don't=20 > > | understand. ums currently doesn't have driver instrumentation in that= path. > > |=20 > > | I pulled a fairly detailed IRC log of my collaborative debugging=20 > > | session with Robert, please ping me if you need details of this. > > `----------------------------------------------------* > >=20 > > 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 :-() > >=20 > > 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). > >=20 > > On the topic of how this upgrade was introduced, I can't help but > > refer to my recent experience helping to fix TWM: > >=20 > > ,--- 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. > > |=20 > > | Hello Alex, no problem at all! Improved solutions have priority over= =20 > > | promised deadlines. > > |=20 > > | Thank you for your time helping to improve TWM, :-) > > | > > `----------------------------------------------------* > >=20 > > 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). > >=20 > > 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. > >=20 > > In honesty, this upgrade should have been presented this way, way > > before the code was placed in the ports source tree: > >=20 > > * We'll have a new X in ports soon -- there are multiple reports of > > problems with it on Linux. > >=20 > > * We want to try it on FreeBSD -- but nobody is forcing you to do the > > upgrade. > >=20 > > * If you, of your own free will, choose to upgrade, you may have > > hours and days of problems -- but heck, it was your choice. > >=20 > > * If your problems cannot be fixed, you'll have to figure out > > something yourself. > >=20 > > * 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. > >=20 > > * The choice is totally yours. > >=20 > > -- Alex -- alex-goncharov@comcast.net -- > >=20 > >=20 > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" > >=20 > 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 w= ith > the vesa driver X said it couldn't find any screens. I finally had to rev= ert=20 > back to an older version. This should not happen on a stable system. for Via hardware, you should be using openchrome. robert. > --=20 >=20 > "They that give up essential liberty to obtain temporary safety, > deserve neither liberty nor safety." (Ben Franklin) >=20 > "The course of history shows that as a government grows, liberty > decreases." (Thomas Jefferson) >=20 >=20 > _______________________________________________ > 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" --=-dv9MjWZZzmssQTlS9Lzc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAkmBwJ4ACgkQM4TrQ4qfRONNmACfSo8eCUT4Tdxb7GMwwcFTyACH iVwAoInbc83w/ApcypZAHjJ/J1D/G0JN =D/yb -----END PGP SIGNATURE----- --=-dv9MjWZZzmssQTlS9Lzc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1233240223.1779.49.camel>