Date: Tue, 30 May 2023 08:34:47 +0200 From: Guido Falsi <mad@madpilot.net> To: Ivan Quitschal <tezeka@hotmail.com>, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: freebsd-current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Message-ID: <6b524926-d736-f17e-701a-c2e982cb960c@madpilot.net> In-Reply-To: <CP6P284MB1900AE2D4B39EB316C3079BBCB4A9@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> 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> <CANCZdfpSnaTpNq2yX2c_qcGTaSsjVWtRyd3V3ZALfCXK57WgkA@mail.gmail.com> <a33748eb-3334-8776-46f6-07303afd705d@madpilot.net> <CANCZdfqL46mQ5dhm8WWL%2ByE8DUOwCgVqRdLWA1dBoAMA2mxqtw@mail.gmail.com> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> <CP6P284MB1900AE2D4B39EB316C3079BBCB4A9@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mad@madpilot.net> 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 <mad@madpilot.net>
>>
>> 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 <junchoon@dec.sakura.ne.jp>
>>
>>
>
>
> 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 <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6b524926-d736-f17e-701a-c2e982cb960c>