I'm running 12.4-RELEASE and a startx just failed with
error messages with the MESA-LOADER complaining that it
could not find /usr/local/lib/dri/radeon_dri.so
(followup error messages "failed to load driver: radeon"
and "kmsro: driver missing").

That directory actually has a radeonsi_dri.so in it,
I was able to find a radeon_dri.so in an older backup
directory and copied it in alongside,but that only
changes the error messages from "failed to load driver: radeon"
to "unknown chip id 0x683d, can't guess." wuth the
"kmsro: driver missing" and
"MESA-LOADER: failed to retrieve device information" unchanged.

I know X was launching since the last time I upgraded mesa*,
I did just change xorg-server and a few others (pciids,
gpgme,re2...?) but what's happening?

Why would an older driver suddenly be sought and a chip
become unknown?

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> I'm running 12.4-RELEASE and a startx just failed with
> error messages with the MESA-LOADER complaining that it
> could not find /usr/local/lib/dri/radeon_dri.so
> (followup error messages "failed to load driver: radeon"
> and "kmsro: driver missing").
>
> That directory actually has a radeonsi_dri.so in it,
> I was able to find a radeon_dri.so in an older backup
> directory and copied it in alongside,but that only
> changes the error messages from "failed to load driver: radeon"
> to "unknown chip id 0x683d, can't guess." wuth the
> "kmsro: driver missing" and
> "MESA-LOADER: failed to retrieve device information" unchanged.
>
> I know X was launching since the last time I upgraded mesa*,
> I did just change xorg-server and a few others (pciids,

(yes)

> gpgme,re2...?)

correcting myself,I TRIED to upgrade these from my Synth
repository but they failed to happen because I wasn't
doing a batch job including removing qt5-webengine which
I think some other things need.

> but what's happening?
>
> Why would an older driver suddenly be sought and a chip
> become unknown?
>
> -=-=-
> The World Trade Center towers MUST rise again,
> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> I'm running 12.4-RELEASE and a startx just failed with
>> error messages with the MESA-LOADER complaining that it
>> could not find /usr/local/lib/dri/radeon_dri.so
>> (followup error messages "failed to load driver: radeon"
>> and "kmsro: driver missing").
>>
>> That directory actually has a radeonsi_dri.so in it,
>> I was able to find a radeon_dri.so in an older backup
>> directory and copied it in alongside,but that only
>> changes the error messages from "failed to load driver: radeon"
>> to "unknown chip id 0x683d, can't guess." wuth the
>> "kmsro: driver missing" and
>> "MESA-LOADER: failed to retrieve device information" unchanged.

If I make radeon_dri.so a symbolic link to radeonsi_dri.so
one of the MESA-LOADER error messages (in 2 repeated sets)
changes to
MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>> I know X was launching since the last time I upgraded mesa*,
>> I did just change xorg-server and a few others (pciids,
>
> (yes)
>
>> gpgme,re2...?)
>
> correcting myself,I TRIED to upgrade these from my Synth
> repository but they failed to happen because I wasn't
> doing a batch job including removing qt5-webengine which
> I think some other things need.
>
>> but what's happening?
>>
>> Why would an older driver suddenly be sought and a chip
>> become unknown?
>>
>> -=-=-
>> The World Trade Center towers MUST rise again,
>> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> Louis Epstein <le@main.lekno.ws> wrote:
>>> I'm running 12.4-RELEASE and a startx just failed with
>>> error messages with the MESA-LOADER complaining that it
>>> could not find /usr/local/lib/dri/radeon_dri.so
>>> (followup error messages "failed to load driver: radeon"
>>> and "kmsro: driver missing").
>>>
>>> That directory actually has a radeonsi_dri.so in it,
>>> I was able to find a radeon_dri.so in an older backup
>>> directory and copied it in alongside,but that only
>>> changes the error messages from "failed to load driver: radeon"
>>> to "unknown chip id 0x683d, can't guess." wuth the
>>> "kmsro: driver missing" and
>>> "MESA-LOADER: failed to retrieve device information" unchanged.
>
> If I make radeon_dri.so a symbolic link to radeonsi_dri.so
> one of the MESA-LOADER error messages (in 2 repeated sets)
> changes to
> MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>
>>> I know X was launching since the last time I upgraded mesa*,
>>> I did just change xorg-server and a few others (pciids,
>>
>> (yes)
>>
>>> gpgme,re2...?)
>>
>> correcting myself,I TRIED to upgrade these from my Synth
>> repository but they failed to happen because I wasn't
>> doing a batch job including removing qt5-webengine which
>> I think some other things need.

Just did a no-removals upgrade of latest synth update of
my repository and the X problem persists.

>>> but what's happening?
>>>
>>> Why would an older driver suddenly be sought and a chip
>>> become unknown?
>>>
>>> -=-=-
>>> The World Trade Center towers MUST rise again,
>>> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> Louis Epstein <le@main.lekno.ws> wrote:
>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>> I'm running 12.4-RELEASE and a startx just failed with
>>>> error messages with the MESA-LOADER complaining that it
>>>> could not find /usr/local/lib/dri/radeon_dri.so
>>>> (followup error messages "failed to load driver: radeon"
>>>> and "kmsro: driver missing").
>>>>
>>>> That directory actually has a radeonsi_dri.so in it,
>>>> I was able to find a radeon_dri.so in an older backup
>>>> directory and copied it in alongside,but that only
>>>> changes the error messages from "failed to load driver: radeon"
>>>> to "unknown chip id 0x683d, can't guess." wuth the
>>>> "kmsro: driver missing" and
>>>> "MESA-LOADER: failed to retrieve device information" unchanged.
>>
>> If I make radeon_dri.so a symbolic link to radeonsi_dri.so
>> one of the MESA-LOADER error messages (in 2 repeated sets)
>> changes to
>> MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>>
>>>> I know X was launching since the last time I upgraded mesa*,
>>>> I did just change xorg-server and a few others (pciids,
>>>
>>> (yes)
>>>
>>>> gpgme,re2...?)
>>>
>>> correcting myself,I TRIED to upgrade these from my Synth
>>> repository but they failed to happen because I wasn't
>>> doing a batch job including removing qt5-webengine which
>>> I think some other things need.
>
> Just did a no-removals upgrade of latest synth update of
> my repository and the X problem persists.
>
>>>> but what's happening?

FWIW the window manager does launch in single user mode?!

>>>> Why would an older driver suddenly be sought and a chip
>>>> become unknown?
>>>>
>>>> -=-=-
>>>> The World Trade Center towers MUST rise again,
>>>> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> Louis Epstein <le@main.lekno.ws> wrote:
>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>> I'm running 12.4-RELEASE and a startx just failed with
>>>>> error messages with the MESA-LOADER complaining that it
>>>>> could not find /usr/local/lib/dri/radeon_dri.so
>>>>> (followup error messages "failed to load driver: radeon"
>>>>> and "kmsro: driver missing").
>>>>>
>>>>> That directory actually has a radeonsi_dri.so in it,
>>>>> I was able to find a radeon_dri.so in an older backup
>>>>> directory and copied it in alongside,but that only
>>>>> changes the error messages from "failed to load driver: radeon"
>>>>> to "unknown chip id 0x683d, can't guess." wuth the
>>>>> "kmsro: driver missing" and
>>>>> "MESA-LOADER: failed to retrieve device information" unchanged.
>>>
>>> If I make radeon_dri.so a symbolic link to radeonsi_dri.so
>>> one of the MESA-LOADER error messages (in 2 repeated sets)
>>> changes to
>>> MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>>>
>>>>> I know X was launching since the last time I upgraded mesa*,
>>>>> I did just change xorg-server and a few others (pciids,
>>>>
>>>> (yes)
>>>>
>>>>> gpgme,re2...?)
>>>>
>>>> correcting myself,I TRIED to upgrade these from my Synth
>>>> repository but they failed to happen because I wasn't
>>>> doing a batch job including removing qt5-webengine which
>>>> I think some other things need.
>>
>> Just did a no-removals upgrade of latest synth update of
>> my repository and the X problem persists.
>>
>>>>> but what's happening?
>
> FWIW the window manager does launch in single user mode?!

....but only once,and now it generates xauth errors if I try.
>>>>> Why would an older driver suddenly be sought and a chip
>>>>> become unknown?
>>>>>
>>>>> -=-=-
>>>>> The World Trade Center towers MUST rise again,
>>>>> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> Louis Epstein <le@main.lekno.ws> wrote:
>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>>> I'm running 12.4-RELEASE and a startx just failed with
>>>>>> error messages with the MESA-LOADER complaining that it
>>>>>> could not find /usr/local/lib/dri/radeon_dri.so
>>>>>> (followup error messages "failed to load driver: radeon"
>>>>>> and "kmsro: driver missing").
>>>>>>
>>>>>> That directory actually has a radeonsi_dri.so in it,
>>>>>> I was able to find a radeon_dri.so in an older backup
>>>>>> directory and copied it in alongside,but that only
>>>>>> changes the error messages from "failed to load driver: radeon"
>>>>>> to "unknown chip id 0x683d, can't guess." wuth the
>>>>>> "kmsro: driver missing" and
>>>>>> "MESA-LOADER: failed to retrieve device information" unchanged.
>>>>
>>>> If I make radeon_dri.so a symbolic link to radeonsi_dri.so
>>>> one of the MESA-LOADER error messages (in 2 repeated sets)
>>>> changes to
>>>> MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>>>>
>>>>>> I know X was launching since the last time I upgraded mesa*,
>>>>>> I did just change xorg-server and a few others (pciids,
>>>>>
>>>>> (yes)
>>>>>
>>>>>> gpgme,re2...?)
>>>>>
>>>>> correcting myself,I TRIED to upgrade these from my Synth
>>>>> repository but they failed to happen because I wasn't
>>>>> doing a batch job including removing qt5-webengine which
>>>>> I think some other things need.
>>>
>>> Just did a no-removals upgrade of latest synth update of
>>> my repository and the X problem persists.
>>>
>>>>>> but what's happening?
>>
>> FWIW the window manager does launch in single user mode?!
>
> ...but only once,and now it generates xauth errors if I try.

The fix for this whole problem has turned out to be
deleting and reinstalling xorg.

But why,all of a sudden?

>>>>>> Why would an older driver suddenly be sought and a chip
>>>>>> become unknown?
>>>>>>
>>>>>> -=-=-
>>>>>> The World Trade Center towers MUST rise again,
>>>>>> at least as tall as before...or terror has triumphed.

Louis Epstein <le@main.lekno.ws> wrote:
> Louis Epstein <le@main.lekno.ws> wrote:
>> Louis Epstein <le@main.lekno.ws> wrote:
>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>>> Louis Epstein <le@main.lekno.ws> wrote:
>>>>>>> I'm running 12.4-RELEASE and a startx just failed with
>>>>>>> error messages with the MESA-LOADER complaining that it
>>>>>>> could not find /usr/local/lib/dri/radeon_dri.so
>>>>>>> (followup error messages "failed to load driver: radeon"
>>>>>>> and "kmsro: driver missing").
>>>>>>>
>>>>>>> That directory actually has a radeonsi_dri.so in it,
>>>>>>> I was able to find a radeon_dri.so in an older backup
>>>>>>> directory and copied it in alongside,but that only
>>>>>>> changes the error messages from "failed to load driver: radeon"
>>>>>>> to "unknown chip id 0x683d, can't guess." wuth the
>>>>>>> "kmsro: driver missing" and
>>>>>>> "MESA-LOADER: failed to retrieve device information" unchanged.
>>>>>
>>>>> If I make radeon_dri.so a symbolic link to radeonsi_dri.so
>>>>> one of the MESA-LOADER error messages (in 2 repeated sets)
>>>>> changes to
>>>>> MESA-LOADER: driver exports no extensions (Undefined symbol "__driDriverExtensions")
>>>>>
>>>>>>> I know X was launching since the last time I upgraded mesa*,
>>>>>>> I did just change xorg-server and a few others (pciids,
>>>>>>
>>>>>> (yes)
>>>>>>
>>>>>>> gpgme,re2...?)
>>>>>>
>>>>>> correcting myself,I TRIED to upgrade these from my Synth
>>>>>> repository but they failed to happen because I wasn't
>>>>>> doing a batch job including removing qt5-webengine which
>>>>>> I think some other things need.
>>>>
>>>> Just did a no-removals upgrade of latest synth update of
>>>> my repository and the X problem persists.
>>>>
>>>>>>> but what's happening?
>>>
>>> FWIW the window manager does launch in single user mode?!
>>
>> ...but only once,and now it generates xauth errors if I try.
>
> The fix for this whole problem has turned out to be
> deleting and reinstalling xorg.
>
> But why,all of a sudden?

THE PROBLEM PERSISTS...if the new xorg-server is upgraded
X stops launching and must be deleted,then a new xorg install
(which picks up the 2.1.7.1 xorg-server from the FreeBSD repository and
not the 2.1.8x upgrade from the local repository that causes
the problems) makes the issue go away.
(A half dozen driver apps go along for the install and delete rides).

>>>>>>> Why would an older driver suddenly be sought and a chip
>>>>>>> become unknown?
>>>>>>>
>>>>>>> -=-=-
>>>>>>> The World Trade Center towers MUST rise again,
>>>>>>> at least as tall as before...or terror has triumphed.