That works, thanks.
Rebecca
On February 12, 2019 at 1:24:15 AM, Hans Petter Selasky
(h...@selasky.org(mailto:h...@selasky.org)) wrote:
> The USB timeout error might indicate an IRQ issue.
>
> Can you try setting:
>
> hw.usb.xhci.use_polling=1
>
> In /boot/loader.conf and reboot.
>
> --HPS
The USB timeout error might indicate an IRQ issue.
Can you try setting:
hw.usb.xhci.use_polling=1
In /boot/loader.conf and reboot.
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
I’m having problems with USB devices on -CURRENT on my ThreadRipper system. The
controller keeps on getting reset. I thought it might be related to my iogear
KVM, but disconnecting it doesn’t help.
Feb 12 00:59:47 photon kernel: xhci0: Resetting controller
Feb 12 00:59:47 photon kernel: usb_all
- Hans Petter Selasky's Original Message -
> On Friday 11 May 2012 02:54:19 John wrote:
> > Hi Folks,
> >
> >We've been trying to bring freebsd up on a hp dl980g7 for awhile.
> > Due to usb issues, we finally installed onto a revo card and
> > installed it into the 980. The system cons
On Friday 11 May 2012 02:54:19 John wrote:
> Hi Folks,
>
>We've been trying to bring freebsd up on a hp dl980g7 for awhile.
> Due to usb issues, we finally installed onto a revo card and
> installed it into the 980. The system consistently puts out the
> following messages:
>
> usbd_ctrl_tran
Hi Folks,
We've been trying to bring freebsd up on a hp dl980g7 for awhile.
Due to usb issues, we finally installed onto a revo card and
installed it into the 980. The system consistently puts out the
following messages:
usbd_ctrl_transfer_setup: could not setup default USB transfer
usb_alloc_
On Sat, 18 Oct 2003, Greg J. wrote:
> On Sat, 18 Oct 2003 15:55:52 -0700 (PDT)
> Doug White <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 15 Oct 2003, Doug White wrote:
> >
> > > > >
> > > > > > Anyone else having these errors? Is there a way to fix it?
> > > > >
> > > > > What's attached to the ports?
On Sat, 18 Oct 2003 15:55:52 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:
> On Wed, 15 Oct 2003, Doug White wrote:
>
> > > >
> > > > > Anyone else having these errors? Is there a way to fix it?
> > > >
> > > > What's attached to the ports?
> > > Nothing.. if I plug anything in (like a mouse)
On Wed, 15 Oct 2003, Doug White wrote:
> > >
> > > > Anyone else having these errors? Is there a way to fix it?
> > >
> > > What's attached to the ports?
> > Nothing.. if I plug anything in (like a mouse) it freezes my system.
>
> Interesting .. which VIA chipset is it? I have a KT400 at home that
On Thu, 16 Oct 2003 08:50:01 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:
> On Wed, 15 Oct 2003, Greg J. wrote:
>
> > > > > What's attached to the ports?
> > > > Nothing.. if I plug anything in (like a mouse) it freezes my
> > > > system.
> > >
> > > Interesting .. which VIA chipset is it? I
On Wed, 15 Oct 2003, Greg J. wrote:
> > > > What's attached to the ports?
> > > Nothing.. if I plug anything in (like a mouse) it freezes my system.
> >
> > Interesting .. which VIA chipset is it? I have a KT400 at home that
> > hasn't built current in a while but worked as of a few weeks ago. I'l
On Wed, 15 Oct 2003, Greg J. wrote:
> On Wed, 15 Oct 2003 09:14:45 -0700 (PDT)
> Doug White <[EMAIL PROTECTED]> wrote:
>
> >
> > Don't crosspost to -questions. -current is the correct forum. Thanks!
> >
> Thanks for the info. :)
> > On Wed, 15 Oct 2003, Greg J. wrote:
> >
> > > Anyone else having
On Wed, 15 Oct 2003 09:14:45 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:
>
> Don't crosspost to -questions. -current is the correct forum. Thanks!
>
Thanks for the info. :)
> On Wed, 15 Oct 2003, Greg J. wrote:
>
> > Anyone else having these errors? Is there a way to fix it?
>
> What's a
Don't crosspost to -questions. -current is the correct forum. Thanks!
On Wed, 15 Oct 2003, Greg J. wrote:
> Anyone else having these errors? Is there a way to fix it?
What's attached to the ports?
>
> uname -a:
>
> FreeBSD localhost.bsd-unix.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Tue
> Oct 14
Anyone else having these errors? Is there a way to fix it?
uname -a:
FreeBSD localhost.bsd-unix.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Tue
Oct 14 07:18:13 MST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/CASPER i386
dmesg:
uhci0: port 0xd000-0xd01f irq 6 at device
16.0 on pci0
usb0: on u
on resume with a usbdevs -v I get ...
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, OHCI root hub(0x),
AcerLabs(0x), rev 1.00
port 1 addr 2: low speed, power 100 mA, config 1, USB Mouse(0xc00c),
Logitech(0x046d), rev 6.20
port 2 powered
port 3 powered
Regardless of
On Fri, Jan 10, 2003 at 12:22:22PM +1100, Mark Sergeant wrote:
> I'm running a toshiba portege 4000 with -CURRENT as of January 9.
> Suspending and resuming runs fine apart from USB, on resume it is unable
> to recognise my USB mouse (logitech), nothing even registers that it is
> plugged in, nor d
On 11 Jan 2003 16:20:45 +1100
Mark Sergeant <[EMAIL PROTECTED]> wrote:
> Both are turned on yes. Restarting both doesn't work, nothing works when
> plugged into the usb ports after a resume.
usbd automatically starts moused for an usb mouse. Maybe the existing
moused and the moused started from u
Both are turned on yes. Restarting both doesn't work, nothing works when
plugged into the usb ports after a resume.
Cheers,
Mark
On Sat, 2003-01-11 at 07:49, Andrew Y Ng wrote:
> are usbd and moused are turned on.
>
> /ayn
>
> On 0, Mark Sergeant <[EMAIL PROTECTED]> wrote:
> > I'm running a to
are usbd and moused are turned on.
/ayn
On 0, Mark Sergeant <[EMAIL PROTECTED]> wrote:
> I'm running a toshiba portege 4000 with -CURRENT as of January 9.
> Suspending and resuming runs fine apart from USB, on resume it is unable
> to recognise my USB mouse (logitech), nothing even registers tha
I'm running a toshiba portege 4000 with -CURRENT as of January 9.
Suspending and resuming runs fine apart from USB, on resume it is unable
to recognise my USB mouse (logitech), nothing even registers that it is
plugged in, nor does the mouse get any power yet on booting normally USB
works fine. Has
I had no problem with kernel from February 14, but failed ums probes are
happening very consistently with kernel from Feb 18. Kernels from dates
earlier than Feb 14 failed to attach USB mouse most of the time but
sometimes misteriously managed to work. No configuration was changing
between success
Hello,
with current of yesterday everything seems to be ok for me again. But I
do not see any reason for this (code has not changed inbetween).
Michael
Alexander Kabaev wrote:
>>Sorry, no hint by my side, but I can report exactly the same problem
>>on an Athlon-C System equipped with a VIA-K
>
> Sorry, no hint by my side, but I can report exactly the same problem
> on an Athlon-C System equipped with a VIA-KT133A chipset.
> (actually it has the same USB controller, so it was expectable)
>
> Riggs
I am seeing the same symptoms while using Microsoft USB mouse with
KT133A-based comp
On Sun, 17. Feb 2002, at 9:53 +0100, Michael Class wrote
according to [Recent USB problems]:
> usb1: on uhci1
> usb1: USB revision 1.0
> uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub1: 2 ports with 2 removable, self powered
>
> The system is a dual PI
Hello,
after the following patch:
joe 2002/02/15 16:51:26 PST
Modified files:
sys/dev/usb ohci.c uhci.c usb.h usb_subr.c usbdivar.h
Log:
Merge from NetBSD:
Pave the way for USB2, by replacing 'lowspeed' with 'speed', so
that it can take the values USB_SPEED_LOW,
Thorsten Greiner wrote:
> Hi,
>
> I cannot get the USB interface to work on my ASUS L7300G Laptop with
> -CURRENT. I have attached an excerpt of the message file and the section of
> the config file dealing with USB. Any hints?
>
> messages:
> Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_
Hi,
I cannot get the USB interface to work on my ASUS L7300G Laptop with
-CURRENT. I have attached an excerpt of the message file and the section of
the config file dealing with USB. Any hints?
messages:
Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci0: port 0x1c00-0x1c1f irq 11 at device 7.
If this with usb support compiled into the kernel, try the following
patch:
--- usb_subr.c.orig Wed Feb 9 23:27:31 2000
+++ usb_subr.c Wed Feb 9 21:16:54 2000
@@ -302,7 +302,7 @@
u_int ms;
{
/* Wait at least two clock ticks so we know the time has
passed. */
- if (bu
Since my new Viewsonic monitor included a USB hub and cable, I decided
to connect them. Under 3.3-STABLE (somewhere, forget when) this
worked and usbdev -v would show that the extra 4 port hub was
connected. After upgrading to 4.0-CURRENT, I got:
uhci0: port 0xcc00-0xcc1f irq 10 at device
4.
30 matches
Mail list logo