From owner-freebsd-x11@FreeBSD.ORG Mon Sep 22 22:47:28 2014 Return-Path: Delivered-To: freebsd-x11@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 465E26D5 for ; Mon, 22 Sep 2014 22:47:28 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FE53323 for ; Mon, 22 Sep 2014 22:47:28 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id a13so4733496igq.1 for ; Mon, 22 Sep 2014 15:47:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=75kHojH0gFHoPZyyouDnYVjZ6imJhaR08HRC+FleLMQ=; b=Px30YZXJaygxNTcfHaUYEON9f7ExkfpRHFqD+2bLz3dsQ7ISYCYYkFLmRXqXtXFMMy mbpPufkY2uIv78OmDHAlHixUhm2wY7+Fbfdu3U5/abw48s+jBETCDmk7xPj6/64K9CKY jinwe/UUgqVi4thyzjRAj0y9l2R84jq3GjBLN1mWf50q5qvyo3UhZZsKkgUV/zG61lrN kOUPEop5D/PpFU9i5Hlb8pskv/UyyzLwqTAlPPffPu18X0q9mB3j/Ibu8ZwMYyC2Naqd CNf8pIE+IOsPSQ7UCxtF6uAbviqBk3tQ0bESuY29KGa205f91UqM3SlkLcEfEANW9ot3 YPag== MIME-Version: 1.0 X-Received: by 10.42.102.9 with SMTP id g9mr8688641ico.1.1411426047111; Mon, 22 Sep 2014 15:47:27 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.163.70 with HTTP; Mon, 22 Sep 2014 15:47:27 -0700 (PDT) In-Reply-To: <542096D6.2000403@astart.com> References: <5414A4B6.5010706@UToledo.edu> <5416B1FE.1010801@dumbbell.fr> <1411306792093-5950838.post@n5.nabble.com> <1411317698961-5950873.post@n5.nabble.com> <541F2CA4.6@hiwaay.net> <1411341142791-5950945.post@n5.nabble.com> <541F64A4.3030002@hiwaay.net> <542096D6.2000403@astart.com> Date: Mon, 22 Sep 2014 15:47:27 -0700 X-Google-Sender-Auth: vSK7X9jpbKwWkxNR9ieB1PoAw20 Message-ID: Subject: Re: FreeBSD Port: x11-servers/xorg-server From: Kevin Oberman To: papowell@astart.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 22:47:28 -0000 On Mon, Sep 22, 2014 at 2:38 PM, Patrick Powell wrote: > On 09/21/14 16:52, William A. Mahaffey III wrote: > >> >> On 09/21/14 18:12, Robert_Burmeister wrote: >> >>> William A. Mahaffey III wrote >>> >>>> On 09/21/14 11:41, Robert_Burmeister wrote: >>>> >>>>> On 13.09.2014 22:10, Robert Burmeister wrote: >>>>>>>> >>>>>>>>> FreeBSD 10.1 i386 >>>>>>>>> xorg-server 1.12.4_9,1 and 1.12.4_1,1 >>>>>>>>> Still don't have mouse support after upgrade from 1.12.4_8,1 >>>>>>>>> >>>>>>>> [ 1786.822] (EE) Failed to load module "mouse" (module does not >>>>>>> exist, >>>>>>> 0) >>>>>>> >>>>>> Have you installed x11-drivers/xf86-input-mouse? >>>>>> >>>>>>> [ 1786.825] (EE) Failed to load module "kbd" (module does not exist, >>>>>>> 0) >>>>>>> >>>>>> And x11-drivers/xf86-input-keyboard? >>>>>> _______________________________________________ >>>>>> >>>>> Installing x11-drivers/xf86-input-mouse and >>>>> x11-drivers/xf86-input-keyboard >>>>> fixed the problem, however, I don't understand why upgrading >>>>> from xorg-server 1.12.4_8,1 to xorg-server 1.12.4_9,1 >>>>> would require new drivers, or lose the ones it had. >>>>> >>>>> I would think these drivers would/should be a dependency for >>>>> xorg-server >>>>> in the Ports system... >>>>> _______________________________________________ >>>>> >>>> I have had that same problem verbatim the last 2 x-server upgrades I >>>> did, & that was the fix, (re?)install the kbd & mouse drivers. I >>>> (pkg-)upgraded this A.M., no such issues .... >>>> ---------------------------------------------------------------------- >>>> >>> Even more interesting... >>> x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-keyboard >>> have xorg-server as a dependency, and so cannot be a circular dependency. >>> >>> I'm guessing that the mouse and keyboard drivers got deleted as >>> dependents >>> of >>> xorg-server during the upgrade, but there are no dependencies in my >>> desktop >>> build >>> process that require that they be put back, even through a complete >>> system >>> recompile. >>> >>> I'm thinking 'x11-drivers/xorg-drivers' and 'x11/xorg-minimal' should be >>> bumped >>> when xorg-server is upgraded. >>> >>> (When my current recompile is done, I will check that my xorg-drivers >>> didn't >>> get removed as well.) >>> >> >> >> I am using pkg, no ports, no recompiling .... FBSD 9.3, BTW .... >> >> >> Just a thought - check to make sure that the x11-drivers/xf86-input-keyboard > port on the PKGng server you are using was actually rebuilt for the new > version of xorg-server. I had this problem a couple of weeks ago and the > X log file hinted that the keyboard driver was not compatible with the > version of xorg-server. At the time I thought that this was due to a lag > in the PKGng server building the new drivers so I compiled and installed > the x11-drivers/xf86-input-keyboard. The problem went away. > > This appears to be the same sort of issue. Perhaps the driver(s) are not > getting rebuilt for the new version of xorg-server? Or perhaps this is > related to packages on the 'with_new_xorg' PKGng server versus packages on > the standard PKGng server? > > I think you just discovered the root problem with "no mouse or keyboard" issue. I just got a note from someone else I was working with on this that the problem was fixed by rebuilding those ports. It is known that they need to be rebuilt to work with NEW_XORG, but there is no version bump, so they generally don't and may not be getting into the NEW_XORG packages. Even if it does, since the version is the same, probably does not get pulled in automatically. Looks to me like there should be a note to this effect on the wiki, at the very least. It's a pretty odd situation. If this happened in the standard ports system, it would just result in a PORT_REVISION bump. Could that be done to those packages in the NEW_XORG repo? -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com