From nobody Tue May 30 06:34:47 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QVjLt0yn2z4Xwmg for ; Tue, 30 May 2023 06:35:18 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVjLt08tVz3HqR for ; Tue, 30 May 2023 06:35:18 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QVjLH1G89z6wDN; Tue, 30 May 2023 08:34:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685428485; x= 1687242886; bh=pmNmpJNreUeENdtnhuCQRSxxNdk5hklpHya6IFhSkMQ=; b=b R6B3uHZPWk7L4HMEa8YKSgaicQECTEZj1vs2ryK/rN/NgS8xgp7d4xWNljalsMgr tFUgIqCvGwUQX8+SD4fLXzORwNDlObwDIC+tQ7BbdErnLHeUsZhi2WFfEoL+fGbl s2hCD+nZYA2dMjEgylj6xWy9J4ej4PT0z/ixq76+6xeGfrfaReph4w32Jrj3ntFq /wgSo6lxg3EZQQKcyTKcNBjUIzqh+/ZhrZEkI+K3fsx5ce2Ta/3lwTHjSxKQLVZ7 I6v2NNwgebWhd+l3UpOSaJS0QoyIC204S2iE2VSu0pnqD3jTzAMHQJwnhSPRYycz /A0wS0xFCOOUkrdQsJQIA== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id jDF8dM3LDGUn; Tue, 30 May 2023 08:34:45 +0200 (CEST) Message-ID: <6b524926-d736-f17e-701a-c2e982cb960c@madpilot.net> Date: Tue, 30 May 2023 08:34:47 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Ivan Quitschal , Tomoaki AOKI Cc: freebsd-current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QVjLt08tVz3HqR X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org On 30/05/23 00:26, Ivan Quitschal wrote: > > > On Mon, 29 May 2023, Tomoaki AOKI wrote: > >> On Mon, 29 May 2023 21:05:42 +0200 >> Guido Falsi wrote: >> >>> On 28/05/23 20:45, Guido Falsi wrote: >>> >>>>> It may well be something broke... but I'm just wanting to be double >>>>> sure it's against a consistent package set. If something broke, then I >>>>> can't help. >>>> >>>> I see, I did not understand what you meant at first. >>>> >>>> What I posted was the result of a simple "pkg upgrade", which is what I >>>> usually do to update the machine, and usually works quite fine. >>>> >>>> I have not tested forcing all packages reinstallation ("pkg upgrade -f" >>>> if I get it correctly). >>>> >>>> That is something I was already planning to do. Will report back >>>> tomorrow for that. >>>> >>> >>> Well forcing reinstallation of all ports (with rebuilt kmod ports) made >>> the issue disappear. >>> >>> SO it looks like it was really nothing. Sorry for the noise and thanks >>> for the suggestions! >>> >>> -- >>> Guido Falsi >> >> IIRC, drm*-kmod port didn't seem to be updated in the first place. >> OTOH, generic kernel seems to be updated via pkgbase. >> >> This could cause problems with incompatibilities. >> And fixed with forcibly updating all pkgs. >> poudliere built new pkg, but pkg doesn't thought it's updated , maybe. >> >> >> -- >> Tomoaki AOKI    >> >> > > > try using this drm-kmod here, instead of the ones within ports > > git clone https://github.com/freebsd/drm-kmod > > thats the only one that works for me I'm having good results with: > pkg info -o '*kmod*' drm-515-kmod-5.15.25_3 graphics/drm-515-kmod gpu-firmware-amd-kmod-picasso-20230210 graphics/gpu-firmware-amd-kmod gpu-firmware-amd-kmod-raven-20230210 graphics/gpu-firmware-amd-kmod from the official tree. -- Guido Falsi