Re: Surprise null root password

2023-05-29 Thread Alexander Leidinger


Quoting bob prohaska  (from Fri, 26 May 2023  
16:26:06 -0700):



On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:


The question is how you update the configuration files,
mergemaster/etcupdate/something else?



Via etcupdate after installworld. In the event the system
requests manual intervention I accept "theirs all". It seems
odd if that can null a root password.

Still, it does seem an outside possibility. I could see it adding
system users, but messing with root's existing password seems a
bit unexpected.


As you are posting to -current@, I expect you to report this issue  
about 14-current systems. As such: there was a "recent" change  
(2021-10-20) to the root entry to change the shell.
 
https://cgit.freebsd.org/src/commit/etc/master.passwd?id=d410b585b6f00a26c2de7724d6576a3ea7d548b7


By blindly accepting all changes, this has reset the PW to the default  
setting (empty).


I suggest to review changes ("df" instead of "tf" in etcupdate) to at  
least those files which you know you have modified, including the  
password/group stuff. After that you can decide if the diff which is  
shown with "df" can be applied ("tf"), or if you want to keep the old  
version ("mf"), or if you want to modify the current file ("e", with  
both versions present in the file so that you can copy/paste between  
the different versions and keep what you need).


Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF


pgpGEjDP92h3s.pgp
Description: Digitale PGP-Signatur


Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head

2023-05-29 Thread Guido Falsi

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 




Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head

2023-05-29 Thread Guido Falsi

On 30/05/23 00:18, 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.


Poudriere did not rebuild the kmod ports since there was no 
__FreeBSD_version change. I usually force it being rebuild by hand, but 
this time I forgot!


I did force pkg reinstall for it by hand, but this just reinstalled the 
same previous package.


In the end I forced rebuilding it and reinstalling everything and the 
issue disappeared.


--
Guido Falsi 




Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head

2023-05-29 Thread Ivan Quitschal




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

--tzk



Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head

2023-05-29 Thread Tomoaki AOKI
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



Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head

2023-05-29 Thread Guido Falsi

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 




Re: WITH_BEARSSL: -8112 bytes available

2023-05-29 Thread Gordon Bergling
Hi,

On Mon, May 29, 2023 at 10:58:27AM +0200, FreeBSD User wrote:
> on CURRENT, enabling in /etc/src.conf
> 
> WITH_BEARSSL=
> 
> seems to result in a slightly enlarged loader binary, which seems to have a 
> fixed size
> supposed on the error I get. See below.
> 
> The system is amd64 (64 bit), for the record.
> 
> Somewhere in the past developers mentioned this upcoming problem and provided 
> a knob to adjust
> the used size - I forgot about that knob and I couldn't find it even in the 
> loader docs - or
> looked at the wrong places.
> 
> Can someone help me out here?
> 
> The first error stops compileing world/kernel, but taking a second run, the 
> error goes away.
> 
> Kind regards and thanks in advance,
> 
> oh
> 
> 
> 
> [...]
> --- all_subdir_stand/efi ---
> SOURCE_DATE_EPOCH=1451606400  objcopy -j .peheader -j .text -j .sdata -j 
> .data  -j .dynamic -j
> .dynsym -j .rel.dyn  -j .rela.dyn -j .reloc -j .eh_frame -j set_Xcommand_set  
> -j
> set_Xficl_compile_set  --output-target=efi-app-x86_64 loader_4th.sym 
> loader_4th.efi ---
> all_subdir_stand/i386 --- 
> 
> -8112 bytes available 7.71 real12.86 user 3.08 sys
> 
> make[1]: stopped in /usr/src
> [...]

I often face a similiar error, not sure if it is BEARSSL related since I build
it since a few month per default, but it often helps just to restart the build.

--Gordon


signature.asc
Description: PGP signature


Re: PinePhone Pro Boots On CURRENT

2023-05-29 Thread Mathias Picker
Am 29. Mai 2023 15:15:29 MESZ schrieb Mathias Picker 
:
>Am 29. Mai 2023 05:24:02 MESZ schrieb Pete Wright :
>>i've had this pinephone pro for a few months now and finally got around to 
>>attempting to boot FreeBSD on it.  Here's the phone:
>>https://wiki.pine64.org/wiki/PinePhone_Pro
>>
>>I needed to get this serial console adapter which works flawlessly with "cu"
>>(USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo Jack Cable):
>>https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details
>>
>>then i just downloaded the latest CURRENT snapshot and put it on a microsd 
>>card and it booted into multi-user mode.  here's the dmesg:
>>https://www.nomadlogic.org/ppro-dmesg.txt
>>
>>i am working on building a new image now to include the pinephone pro DTB 
>>file from Linux to see if that improves some of the hardware detection.  
>>certainly a long way to go before this could be a useful mobile device, but 
>>i'm very encouraged that i can actually boot the thing.
>>
>>i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and 
>>bluetooth card working...
>>
>>But, once i get the linux DTB for this guy into a disk image i'm going to see 
>>if i can get the display up next, but would love to hear any input or 
>>pointers from folks with more ARM porting experience than me.
>>
>>thanks!
>>-pete
>>
>>
>>
>>-- 
>>Pete Wright
>>p...@nomadlogic.org
>>@nomadlogicLA
>
>Gesehen?
>
>Leider bin ich inzwischen Fold-Abhängig.
>Trotzdem cool!
>Mathias Picker
>Geschäftsführer
>virtual earth Gesellschaft für Wissens re/prä sentation mbH
>Westendstr. 142
>80339 München
>+4915256178344
Sorrry,that shoud have been a forward. 
Too much sun burned my brain out I guess…

And that's great news!
Mathias Picker
Geschäftsführer
virtual earth Gesellschaft für Wissens re/prä sentation mbH
Westendstr. 142
80339 München
+4915256178344

Re: PinePhone Pro Boots On CURRENT

2023-05-29 Thread Mathias Picker
Am 29. Mai 2023 05:24:02 MESZ schrieb Pete Wright :
>i've had this pinephone pro for a few months now and finally got around to 
>attempting to boot FreeBSD on it.  Here's the phone:
>https://wiki.pine64.org/wiki/PinePhone_Pro
>
>I needed to get this serial console adapter which works flawlessly with "cu"
>(USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo Jack Cable):
>https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details
>
>then i just downloaded the latest CURRENT snapshot and put it on a microsd 
>card and it booted into multi-user mode.  here's the dmesg:
>https://www.nomadlogic.org/ppro-dmesg.txt
>
>i am working on building a new image now to include the pinephone pro DTB file 
>from Linux to see if that improves some of the hardware detection.  certainly 
>a long way to go before this could be a useful mobile device, but i'm very 
>encouraged that i can actually boot the thing.
>
>i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and 
>bluetooth card working...
>
>But, once i get the linux DTB for this guy into a disk image i'm going to see 
>if i can get the display up next, but would love to hear any input or pointers 
>from folks with more ARM porting experience than me.
>
>thanks!
>-pete
>
>
>
>-- 
>Pete Wright
>p...@nomadlogic.org
>@nomadlogicLA

Gesehen?

Leider bin ich inzwischen Fold-Abhängig.
Trotzdem cool!
Mathias Picker
Geschäftsführer
virtual earth Gesellschaft für Wissens re/prä sentation mbH
Westendstr. 142
80339 München
+4915256178344