From owner-freebsd-current@freebsd.org Wed Feb 3 19:28:37 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D80B9528B60 for ; Wed, 3 Feb 2021 19:28:37 +0000 (UTC) (envelope-from 01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com) Received: from a48-91.smtp-out.amazonses.com (a48-91.smtp-out.amazonses.com [54.240.48.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DWBYc6dXjz3MYG for ; Wed, 3 Feb 2021 19:28:36 +0000 (UTC) (envelope-from 01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1612380514; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=9DXehzrX6Ln+OIysJ50sx3J0S6rgugRBPsS8N1tNcU8=; b=iA/O0yGl2eNuYh0wX1jAkZD3hHHUg6AsicNAMfxvoWm2me+8f++U4txJRIifVo5Q sA2UrPG8O1aTe1h771V8pPXLuOmUJ34MgafOzQUKlGFWFBaZg5STnJ4U4sjmW+cH+AK kJZFa7+juN4fp1n7FqX4yx4NHTGkl/q3+6kNr6Jw= Subject: Re: Problem with X Server when updating to 38bfc6dee33 To: freebsd-current@freebsd.org References: <0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@email.amazonses.com> <7D8AD706-C572-46B4-BAD6-96759934BFAA@grem.de> <010001776892e9be-885ca347-91b7-411f-a20b-009cbe248a73-000000@email.amazonses.com> From: Thomas Laus Message-ID: <01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@email.amazonses.com> Date: Wed, 3 Feb 2021 19:28:34 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2021.02.03-54.240.48.91 Feedback-ID: 1.us-east-1.9pbSdi8VQuDGy3n7CRAr3/hYnLCug78GrsPo0xSgBOs=:AmazonSES X-Rspamd-Queue-Id: 4DWBYc6dXjz3MYG X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=amazonses.com header.s=224i4yxa5dv7c2xz3womw6peuasteono header.b=iA/O0yGl; dmarc=none; spf=pass (mx1.freebsd.org: domain of 01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com designates 54.240.48.91 as permitted sender) smtp.mailfrom=01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com X-Spamd-Result: default: False [-0.43 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=224i4yxa5dv7c2xz3womw6peuasteono]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[acm.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[54.240.48.91:from:127.0.2.255]; DKIM_TRACE(0.00)[amazonses.com:+]; NEURAL_HAM_SHORT(-0.73)[-0.734]; RCVD_IN_DNSWL_NONE(0.00)[54.240.48.91:from]; NEURAL_HAM_LONG(-1.00)[-1.000]; FORGED_SENDER(0.30)[lausts@acm.org,01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; RWL_MAILSPIKE_POSSIBLE(0.00)[54.240.48.91:from]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[54.240.48.91:from]; ASN(0.00)[asn:14618, ipnet:54.240.48.0/23, country:US]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,01000177695e29b4-36aa3d3b-1558-4030-ab0b-c5ea49224dc6-000000@amazonses.com]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2021 19:28:37 -0000 On 2/3/21 12:12 PM, Niclas Zeising wrote: > > I think also xf86-input-synaptics was affeced by the same issue. > In any case, kern.evdev.rcpt_mask should not need any changes on FreeBSD > 12.1 or later, the defaults have been updated there.  Unless you are > using a serial mouse. > > Can you provide an Xorg.log from the faulty system? > Regards > Looking over the Xorg.log and seeing missing drivers, I re-installed xorg-minimal from ports and everything is working correctly. Thanks everyone for the help. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF