Hello,
Recently I wanted to resurrect and old AMD Bobcat (14h) for use with
kgdb over dconschat. The system booted a
FreeBSD-13.0-ALPHA2-amd64-20210122 without a problem. I noticed the BIOS
was ~9 years old, so I updated the to most recent version, which is ~5
years old. After the BIOS update, Any
Sorry, please ignore previous reply, the modified sysctl is still
running,
the output earlier, was from the stock binary.
On 2021-02-09 14:25, Alastair Hogge wrote:
> On 2021-02-08 21:01, Hans Petter Selasky wrote:
>> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>>> Boot to multi-user; login (getty):
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
> Hi,
>
> Maybe you could do a hack and edit the sysc
The following happened while doing: chflags -R noschg /
It has not been repeatable. I've never gotten such before.
The offset values look odd to me.
chflags: g_vfs_done():gpt/FBSDmacchroot[READ(offset=-4154898212347031552,
length=32768)]error = 5
/usr/fbsd/main-sg_vfs_done():gpt/FBSDmacchroot[REA
On 7 Feb 2021, at 23:53, Steve Kargl wrote:
>
> See the last few comments here:
>
> https://github.com/JuliaMath/openlibm/issues/211
Thanks Steve. Committed here:
https://cgit.freebsd.org/src/commit/?id=93fc67896550548f91b307dbe3053f11db5d4a8a
-Dimitry
signature.asc
Description: Message si
On Mon, 08 Feb 2021 21:05:24 +0300
Greg V wrote:
>
>
> On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
> > On 2021-02-04 17:50, Emmanuel Vadot wrote:
> >
> > [...]
> >
> >> Only happens with drm when you do what ?
> >
> > Boot to multi-user; login (getty):
> > $ doas kldload /boot/mod
On Mon, Feb 8, 2021 at 10:10 AM joe mcguckin wrote:
> I was just playing around with a test ZFS system and was running through
> replacing a bad drive and I forgot to issue a ‘zpool offline’ command.
> Everything seemed to go ok anyway. The system started resilvering, etc.
> When is ‘zpool requir
I was just playing around with a test ZFS system and was running through
replacing a bad drive and I forgot to issue a ‘zpool offline’ command.
Everything seemed to go ok anyway. The system started resilvering, etc. When is
‘zpool required’? Under what conditions can I omit it?
Is there a dedic
On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
https:/
Hi there,
I wonder if it's too late to ask if it's possible to bump openssh in base
to
version 8.4 for 13.0, which enables nist-p256-capable keys and fido/u2f
support.
Despite the fido/u2f capabilities requires libfido2, iirc it is possible to
compile openssh without libfido2 but to enable it in
On 2/8/21 1:53 PM, Alastair Hogge wrote:
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
Hi,
Maybe you could do a hack and edit the sysctl source code:
1) print the sysctl before it is queried.
2) sleep 1 se
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
> Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
___
freebsd-current@freeb
12 matches
Mail list logo
