The following reply was made to PR usb/139598; it has been noted by GNATS.
From: "Momchil Ivanov"
To: bug-follo...@freebsd.org,
wbl...@wonkity.com
Cc: momc...@xaxo.eu
Subject: Re: usb/139598: [umass] CAM reports "xptioctl: put "device pass"
in your kernel config file" even when already present
As I've updated to FreeBSD 8.0-STABLE #0: Sat Nov 28 12:03:22 CET
2009, the problem is gone.
Thanks for the great work!
Regards,
On Tue, Aug 25, 2009 at 7:10 PM, Ullrich Franke wrote:
> Hi Mr, Atkinson,
>
> On Tue, 25 Aug 2009 13:30:47 GMT
> ga...@freebsd.org wrote:
>> [snip]
>> New Synopsis:
2009/11/28 :
> Old Synopsis: USB mouse doesn't work under FreeBSD 8.0-RELEASE
> New Synopsis: [umouse] [usb8] USB mouse doesn't work under FreeBSD 8.0-RELEASE
>
> Responsible-Changed-From-To: freebsd-i386->freebsd-usb
> Responsible-Changed-By: gavin
> Responsible-Changed-When: Sat Nov 28 22:29:08
The following reply was made to PR usb/139598; it has been noted by GNATS.
From: Buganini
To: bug-follo...@freebsd.org, wbl...@wonkity.com
Cc:
Subject: Re: usb/139598: [umass] CAM reports "xptioctl: put "device pass" in
your kernel config file" even when already present
Date: Mon, 30 N
The following reply was made to PR usb/139598; it has been noted by GNATS.
From: Momchil Ivanov
To: bug-follo...@freebsd.org,
wbl...@wonkity.com
Cc:
Subject: Re: usb/139598: [umass] CAM reports "xptioctl: put "device pass" in
your kernel config file" even when already present
Date: Sun, 29 No
On Sun, Nov 29, 2009 at 02:50:03AM +, Brett Glass wrote:
> The following reply was made to PR usb/140883; it has been noted by GNATS.
>
> From: Brett Glass
> To: bug-follo...@freebsd.org
> Cc: sub.m...@gmail.com
> Subject: Re: usb/140883: [axe] USB gigabit ethernet hangs after short
> perio
On Sat, Nov 28, 2009 at 01:40:18PM -0700, Brett Glass wrote:
> Everyone:
>
> Just tried to plug an ASIX-based USB-to-Ethernet interface into a
> system running FreeBSD 8.0-RELEASE, and discovered that it wasn't
> recognized. It turns out that ASIX has come out with a new version
> of one of its
Hi, I've got a USB audio device that identifies itself in dmesg in 8.0-
RELEASE like so:
ugen6.2: at usbus6
uaudio0: rev 1.00/10.00, addr 2> on usbus6
uaudio0: No playback!
uaudio0: No recording!
uaudio0: No midi sequencer
pcm3: on uaudio0
uhid0: 1.00/10.00, addr 2> on usbus6
The "No playbac
At 02:23 PM 11/29/2009, Pyun YongHyeon wrote:
I think the large number of interrupts has nothing to do with
axe(4). Almost all USB ethernet controllers are poorly designed
to save cost so you can't expect reasonable performance from it and
you should have fast CPU to copy received frames in a bu
On Sun, Nov 29, 2009 at 04:51:09PM -0700, Brett Glass wrote:
> At 02:38 PM 11/29/2009, Pyun YongHyeon wrote:
>
> >I'm not sure buffer size allowed in driver is 4K. Long time ago I
> >increased Rx buffer size to 16KB from 2KB for 88178/88772. That
> >change was essential to get 220Mbps for 88178/88
On Sun, Nov 29, 2009 at 05:03:44PM -0700, Brett Glass wrote:
> At 02:23 PM 11/29/2009, Pyun YongHyeon wrote:
>
> >I think the large number of interrupts has nothing to do with
> >axe(4). Almost all USB ethernet controllers are poorly designed
> >to save cost so you can't expect reasonable performa
At 02:38 PM 11/29/2009, Pyun YongHyeon wrote:
I'm not sure buffer size allowed in driver is 4K. Long time ago I
increased Rx buffer size to 16KB from 2KB for 88178/88772. That
change was essential to get 220Mbps for 88178/88772 on Rx. The
patch was not made into 8.0-RELEASE though.
If not, it
[r...@mesa /]# devinfo -rv | grep phy
(..)
ukphy1 pnpinfo oui=0x606e model=0xc rev=0x0 at phyno=0
(..)
I understand my device may have the same name, but different PHY thus
is actually a different product.
In order to debug this problem i need physical access to change the
ether
13 matches
Mail list logo
