On Thu, 2023-04-06 at 11:59 +, Gerhard Roth wrote:
> On Thu, 2023-04-06 at 11:51 +, Mikolaj Kucharski wrote:
> > On Thu, Apr 06, 2023 at 11:40:06AM +, Gerhard Roth wrote:
> > > On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote:
> > > >
On Thu, 2023-04-06 at 11:51 +, Mikolaj Kucharski wrote:
> On Thu, Apr 06, 2023 at 11:40:06AM +0000, Gerhard Roth wrote:
> > On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote:
> > >
> > > So, I am not sure do I understand the output right, but is this mod
On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote:
> On Thu, Apr 06, 2023 at 09:13:27AM +0000, Gerhard Roth wrote:
> >
> > The Sierra Wireless documentation is available. Alas, switching the
> > mode seems far too complex and error prone to perform this inside
> &
On Thu, 2023-04-06 at 18:49 +1000, David Gwynne wrote:
> On Wed, Apr 05, 2023 at 11:22:34PM +, Mikolaj Kucharski wrote:
> > On Wed, Apr 05, 2023 at 11:16:55PM +, miko...@kucharski.name wrote:
> > > > Synopsis: Sierra Wireless MC7750 attaches as ugen(4)
> > > > Category: kernel
>
On Mon, 28 Mar 2022 09:25:32 +0200 Gerhard Roth wrote:
> Hi Stephan,
>
> although the newer AX88179A chip set (note the "A" at the end) uses the
> same product ID as the older AX88179, it is quite different.
>
> I will work on support for AX88179A, but that
Hi Stephan,
although the newer AX88179A chip set (note the "A" at the end) uses the
same product ID as the older AX88179, it is quite different.
I will work on support for AX88179A, but that'll take some time.
Regards,
Gerhard
On 3/26/22 22:05, Stephan Mending wrote:
Hi *,
I am currently in
On Thu, 28 Oct 2021 10:10:23 + Klemens Nanni wrote:
> On Tue, Sep 14, 2021 at 05:52:08PM -0400, James Hastings wrote:
> > >Synopsis: run(4): connecting to WEP network. panic: null node
> > >Category: kernel
> > >Environment:
> > System : OpenBSD 7.0
> > Details : OpenBSD 7
On 2/3/21 12:51 PM, Marcus Glocker wrote:
On Wed, 3 Feb 2021 11:41:17 +
Edd Barrett wrote:
On Wed, Feb 03, 2021 at 11:17:01AM +, Stuart Henderson wrote:
btw the problem was seen with umb, it's not just ugen.
From mglocker@'s explanation, I understood that it is the ugen driver
tryi
On 2020-08-18 00:03, Christoph R. Winter wrote:
Hello, thanks for your fast answer.
Am 17.08.2020 11:29, schrieb Gerhard Roth:
The "not on queue" error sounds more like a bug in xhci(4). Could you
please try to disable USB3 in the BIOS an see if the problem resolves
then.
I disabl
On 2020-08-15 14:47, Christoph R. Winter wrote:
Update :
During a CVS checkout I got disconnected because of a loop something
(sorry, did not kept the message) and saw a new message in
/var/log/messages. This time the device disaapeared in ifconfig.
Aug 15 07:21:35 t440p /bsd: usb_insert_tra
Hi Stuart,
what happens here is that the timeout kicks in and xhci_command_submit()
resets sc_cmd_trb to NULL. But that doesn't retire the TRB that is still
active in the controller and when it is done later, the KASSERT() in
xhci_event_command() is bound to fail.
My proposed fix would be:
1) xh
So, just waiting for… nothing or kernel panic. I’ll let you
know.
On 8 Jun 2020, at 19:13, Patrick Wildt <mailto:patr...@blueri.se>> wrote:
On Mon, Jun 08, 2020 at 05:31:44PM +0200, Gerhard Roth wrote:
On 2020-05-25 13:19, Martin Pieuchot wrote:
On 25/05/20(Mon) 12:56, Gerhard Roth wrote
Hi Matthias,
I just committed if_cdcef.c, rev 1.77. That should fix the panic.
However, the cdce(4) interface will still stop sending. But that
may be due to some problem with the USB network adapter.
Gerhard
On 2020-06-07 14:57, Matthias wrote:
Synopsis: 6.7-stable USB3 panic: assertwa
On 2020-05-25 13:19, Martin Pieuchot wrote:
On 25/05/20(Mon) 12:56, Gerhard Roth wrote:
On 5/22/20 9:05 PM, Mark Kettenis wrote:
From: Łukasz Lejtkowski
Date: Fri, 22 May 2020 20:51:57 +0200
Probably power supply 12 V is broken. Showing 16,87 V(Fluke 179) -
too high. Should be 12,25-12,50 V
On 5/22/20 9:05 PM, Mark Kettenis wrote:
From: Łukasz Lejtkowski
Date: Fri, 22 May 2020 20:51:57 +0200
Probably power supply 12 V is broken. Showing 16,87 V(Fluke 179) -
too high. Should be 12,25-12,50 V. I replaced to the new one.
That might be why the device stops responding. The fact that
;t be actively using mine until I can finish off
> the
> umb authentication patches). The one on Yahoo might need unlocking though -
> it
> seems to be a bit hit-and-miss as to whether they're locked or not.
>
> Let me know what you want to do.
>
> Lee.
>
> On Wed
here
and never probes config #2 (like it did before).
It would be interesting if config #2 offers an AT-interfac (umsm), too.
In that case umsm and umb could coexist.
Gerhard
> The alternative is that the device cannot attach at all.
>
> How does this get resolved? I can dig it u
On Wed, 5 Feb 2020 19:54:01 +0900 leeb wrote:
> >Synopsis:umb device no longer detected
> >Category:kernel
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6-current (GENERIC.MP) #8: Tue Jan 14 20:23:40
> JST 2020
>
> lee@x230.tan
18 matches
Mail list logo
