Hello all!
After one year I was in need to use ipv6 on wireless and everything is
working ok.
I'm running 15-CURRENT:
---
wlans_iwlwifi0="wlan0"
create_args_wlan0="wlanmode sta regdomain ETSI country PT"
ifconfig_wlan0_ipv6="inet6 accept_rtadv"
ifconfig_wlan0="WPA SYNCDHCP"
rtsold_enable="YES"
I think that the problem is that admsmn has probed, but not attached (or
failed to attach for some reason), so we find the device, but it's not
initialized yet, so when we call amdsmn_read, it tries to lock a mutex
that's not yet initialized.
Not sure why this is happening, or why loading it as
providers, and can be installed by
running:
% vagrant init freebsd/FreeBSD-14.0-ALPHA4
% vagrant up
== ISO CHECKSUMS ==
o 14.0-ALPHA4 amd64 GENERIC:
SHA512 (FreeBSD-14.0-ALPHA4-amd64-20230901-4c3f144478d4-265026-bo
Following my first pkg upgrade with 15.0-CURRENT, I no longer get the
required character after input.
In applications such as Dolphin, Konsole, Firefox, and Thunderbird: the
visible input (e.g. code 2013 for an en dash) is followed by disappearance.
In Code - OSS (editors/vscode): input is
On Fri, 01 Sep 2023 17:14:02 +0200
"Herbert J. Skuhra" wrote:
> On Fri, 01 Sep 2023 16:04:41 +0200, Gary Jennejohn wrote:
> >
> > On Fri, 01 Sep 2023 14:15:20 +0200
> > "Herbert J. Skuhra" wrote:
> >
> > > On Fri, 01 Sep 2023 13:03:14 +0200, Gary Jennejohn wrote:
> > > >
> > > > I have a laptop
On Fri, 1 Sep 2023 14:43:21 +
Gary Jennejohn wrote:
> A git-bisect is probably required.
>
I did a bisect and the result was commit
9a7add6d01f3c5f7eba811e794cf860d2bce131d.
However, that can't be correct because this commit was made on
Mon Jul 17 19:29:20 2023 and my FBSD-14 kernel from
On Fri, 01 Sep 2023 16:04:41 +0200, Gary Jennejohn wrote:
>
> On Fri, 01 Sep 2023 14:15:20 +0200
> "Herbert J. Skuhra" wrote:
>
> > On Fri, 01 Sep 2023 13:03:14 +0200, Gary Jennejohn wrote:
> > >
> > > I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
> > >
> > > These
On Fri, 1 Sep 2023 14:23:36 +
Gary Jennejohn wrote:
> Now that I look at the date of my FreeBSD-14 kernel I see that it's from
> August 13, so this commit is perhaps not the cause of my FreeBSD-15
> kernel panicking at boot time, since FBSD-14 boots OK.
>
> Nonetheless, amdtemp or maybe
On Fri, 1 Sep 2023 11:03:14 +
Gary Jennejohn wrote:
> I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
>
> These are respectively Zen 1 and Zen 2 CPUs.
>
> I built a kernel on both computers using the FreeBSD-15 source tree.
>
> If I include the amdtemp device in my
On Fri, 01 Sep 2023 14:15:20 +0200
"Herbert J. Skuhra" wrote:
> On Fri, 01 Sep 2023 13:03:14 +0200, Gary Jennejohn wrote:
> >
> > I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
> >
> > These are respectively Zen 1 and Zen 2 CPUs.
> >
> > I built a kernel on both
On Fri, Sep 1, 2023, 5:03 AM Gary Jennejohn wrote:
> I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
>
> These are respectively Zen 1 and Zen 2 CPUs.
>
> I built a kernel on both computers using the FreeBSD-15 source tree.
>
> If I include the amdtemp device in my
On Fri, 01 Sep 2023 13:03:14 +0200, Gary Jennejohn wrote:
>
> I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
>
> These are respectively Zen 1 and Zen 2 CPUs.
>
> I built a kernel on both computers using the FreeBSD-15 source tree.
>
> If I include the amdtemp device
I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X.
These are respectively Zen 1 and Zen 2 CPUs.
I built a kernel on both computers using the FreeBSD-15 source tree.
If I include the amdtemp device in my kernel file BOTH computers end up
with a kernel panic while trying to
13 matches
Mail list logo
