Sorry I report wrong version of the driver. It should be
iwm-firmware-20220111.tgz of course.
Checked on actual hardware it seems to work fine. So I report it also to
Qubes and Xen Project, but marmarek (head of qubes development team)
suggest that it can be a problem with driver itself:
"I'm not sure if that's relevant, but a common cause is incorrect MSI /
MSI-X detection/support by the d
It appears that a small amount of the output was lost coming across
the serial console. Hopefully that has what you need. if not I can
try booting bsd.rd and getting dmesg that way. ACPU dumps are
attached.
James
>> OpenBSD/amd64 BOOT 3.55
boot> bsd.70
booting hd0a:bsd.70: 14841112|594/]=0x15
On 9/15/22, Alton Shaw wrote:
> Completely new user "test01", fired up fresh installation of Firefox,
> new blank tab, closed all other Mozilla's initial tabs, cleared
> cookies/history/cache/etc, browsed to my bank's login page. Attempted
> login but received the same result: We’re currently havi
Completely new user "test01", fired up fresh installation of Firefox,
new blank tab, closed all other Mozilla's initial tabs, cleared
cookies/history/cache/etc, browsed to my bank's login page. Attempted
login but received the same result: We’re currently having technical
issue Please try again
On Tue Sep 13, 2022 at 2:52 AM UTC, James Cook wrote:
> On Sun Sep 11, 2022 at 3:50 AM UTC, Jonathan Gray wrote:
> > On Sun, Sep 11, 2022 at 03:18:47AM +, James Cook wrote:
> > > >Synopsis:X11 keeps showing images from a few seconds ago
> > > >Category:kernel
> > > >Environment:
Le Thu, Sep 15, 2022 at 05:40:47AM -0700, Alton Shaw a écrit :
> So I completely removed Firefox, Firefox-ESR, & Chromium and then reinstall
> Firefox. Started Firefox, without changing any settings went straight to my
> banking site, tried to login and received exactly the same result: "/We’re
>
So I completely removed Firefox, Firefox-ESR, & Chromium and then
reinstall Firefox. Started Firefox, without changing any settings went
straight to my banking site, tried to login and received exactly the
same result: "/We’re currently having technical issue Please try again
later./"
At thi
