"Jason Seidel" wrote:
> > On Sunday 31 July 2011 02:30:11 Jason Seidel wrote:
> > > xhci0: Driver does not support 64-byte contexts.xhci0: XHCI
> > > halt/start/probe failed err=18
> >
> > This is fixed in 8-stable.
> >
> > --HPS
>
> Is it going into RELEASE?
Being in 8-stable ensures that it
Lev Serebryakov wrote:
> Last changes, committed to 8-STABLE ... breaks some API/ABI ...
AFAIK, changes that break API/ABI are not supposed to be MFCd.
Perhaps that one needs to be backed out of 8-STABLE?
___
freebsd-usb@freebsd.org mailing list
http
"General@support.checksunlimited" wrote:
> I am currently going crazy trying to figure out how to fix the
> problem with my keyboard not typing in what I type. It is like it
> has a mind of it???s own. When typing it will leave out leave out
> letters or not do a space what ever.
Last time I saw
Jerahmy Pocott wrote:
> I have a USB Drive that was working fine under 7.3, but since
> updating to 8.1 no longer has the correct /dev entries. Under
> 7.3 it was da0s1, in 8.1 there is now only da0 and da0a, which
> shouldn't exist...
>
> Any ideas on how to correct this problem?
No, but you're
Bruce Cran wrote:
> I've been having problems with a card reader
> (http://www.frontier-electronics.co.za/stor_sdr012.htm)
> and an 8GB SD card
...
> (da0:umass-sim0:0:0:0): AutoSense failed
> g_vfs_done():da0s1[READ(offset=6782976, length=36864)]error = 5
> vnode_pager_getpages: I/O read error
Matthias Apitz wrote:
> El d?a Friday, November 19, 2010 a las 08:51:38PM +0200,
> Alexander Motin escribi?:
> > > Could it be that unwritten/unformatted blocks are read as
> > > random data from that USB key? Should I overwrite the full
> > > USB key from /dev/zero?
> >
> > It is allowed behavio
Marcin Cieslak wrote:
> Dnia 14.09.2010 Alexander Best napisa??/a:
> >> > http://www.mail-archive.com/freebsd-curr...@freebsd.org/msg124948.html).
> >>
> >> If we don't have to GPL the resulting .h and .c files.
> >
> > "The contents of the database and the generated files can be
> > distribute
Rem P Roberti wrote:
> Brother! Muttprint is now working fine. The problem: the printer
> was offline! Now, before you go accusing me of being a complete
> dufus, let me say that I had no way of knowing that that condition
> existed. The printer itself indicated that it was online---no
> prob
Jim Bryant wrote:
> well, i can't speak for K&R 1978, as i can't currently find my copy,
> but, for a quick brush up, you might want to read pages 80 and 81
> from K&R 2nd Ed. 1988.
>
> your idea that the preprocessor will evaluate
>
> #define thirtytwok (1<<15)
>
> into 0x8000
>
> at compile ti
Jim Bryant wrote:
> what kind of idiot defines a constant assignment for a 32k buffer as a
> 15 bit left shift of 1?
>
> clever, yes. but in production, stupid.
>
> a constant should be just that, a constant, and thus require no
> computation at runtime.
Er, did you bother to look at the gene
The following reply was made to PR usb/149039; it has been noted by GNATS.
From: per...@pluto.rain.com
To: f...@shapeshifter.se
Cc: pilzablei...@web.de, bug-follo...@freebsd.org, freebsd-...@freebsd.org,
freebsd-usb@freebsd.org
Subject: Re: usb/149039: [uhso] Binding problem with uhso
Date
> The following reply was made to PR usb/149039; it has been noted
> by GNATS.
>
> From: Fredrik Lindberg
> To: bug-follo...@freebsd.org, pilzablei...@web.de
> Cc: Hans Petter Selasky
> Subject: Re: usb/149039: [uhso] Binding problem with uhso
> Date: Sat, 31 Jul 2010 15:00:07 +0200
>
> I appare
Torfinn Ingolfsen wrote:
> Many new machines / motherboards today comes with only one
> ps/2 port. Well, the kvm switches I use still has ps/2 ports.
> Therefore I use adapters that plug into a usb port and gives
> me two ps/2 ports ... I generally only use one port on these
> - for a mouse.
Th
The following reply was made to PR usb/144414; it has been noted by GNATS.
From: per...@pluto.rain.com
To: ste...@uplinklabs.net
Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Wed, 03 Mar 2010 22:36:00 -0800
Steve
Steven Noonan wrote:
> Interestingly, my tilde key doesn't work either (though the key
> press is detected, no character shows when the key is pressed).
Any chance it is configured as a "dead" key? If you press
tilde followed by n do you get an n with a tilde over it?
___
When I plug in the reader, I get (on the console):
umass0: SDMMC M121 USB 2.0 SD/MMC READER, rev 2.00/2.01, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: Removable Direct Access SCSI-0
device
da0: 1.000MB/s transfers
da0: 1962MB (4019200 512 byte sectors: 255H 63S/T 250C)
So far, so good
> > Does 6.1 have some fundamental problem with USB serial devices?
>
> No (but you ought to update to 6.3).
Someday, maybe, but at this point I may just wait til 7.0 comes out :)
> > I'm trying a USB-serial converter after getting nowhere with
> > connecting a USB modem directly -- the modem als
Does 6.1 have some fundamental problem with USB serial devices?
I'm trying a USB-serial converter after getting nowhere with
connecting a USB modem directly -- the modem also has a DB9 --
and getting the same unexpected behavior from the converter as
from the modem.
When connected, the console re
> > Either the device doesn't like this sort of thing,
> > or I did something wrong:
> >
> > # ls -l /dev/ugen*
> > crw-r--r-- 1 root operator1, 15 Nov 24 21:17 /dev/ugen0
> > crw-r--r-- 1 root operator1, 16 Nov 24 21:17 /dev/ugen0.1
> > crw-r--r-- 1 root operator1, 17 Nov 24 2
> > > To me it looks like they are using some kind of propritary
> > > protocol. You could try and see if any of the endpoints,
> > > which appear like /dev/ugen0.x files respond with "OK" when
> > > you send "AT\r\n" to the endpoint ...
> >
> > How would I go about doing that?
>
> I think the best
> To me it looks like they are using some kind of propritary
> protocol. You could try and see if any of the endpoints,
> which appear like /dev/ugen0.x files respond with "OK" when
> you send "AT\r\n" to the endpoint ...
How would I go about doing that? tip(1), or something else?
(In case it is
Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
> On Tuesday 01 January 2008, [EMAIL PROTECTED] wrote:
> > Has anyone tried, either successfully or not, to
> > use a ZyXEL Omni 56K Plus modem with recent FreeBSD?
> > ...
>
> We need a dump of the USB descriptors to say for sure.
> See "/usr/ports/
Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
> On Tuesday 01 January 2008, [EMAIL PROTECTED] wrote:
> > Has anyone tried, either successfully or not, to
> > use a ZyXEL Omni 56K Plus modem with recent FreeBSD?
> > ...
> We need a dump of the USB descriptors to say for sure.
> See "/usr/ports/s
Has anyone tried, either successfully or not, to
use a ZyXEL Omni 56K Plus modem with recent FreeBSD?
It's listed in /usr/src/sys/dev/usb/usbdevs, and
thus in usbdevs.h and usbdevs_data.h, but I found
no other mentions of ZyXEL in the kernel source
and none at all in the handbook. (The comments in
What-all would be involved in arranging to load quirks from
a file, instead of having to build them into the kernel?
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PR
> > umass0: vendor 0x0784 product 0x4300, rev 1.10/3.00, addr 2
> > umass0: Get Max Lun not supported (SHORT_XFER)
> > umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
...
> > so I guess I need to set CAM_QUIRK_NOLUNS and something to adjust
> > the sig. This is on a Dell Optiplex GX
I think I need to add a quirk entry to get umass(4) to handle my
camera, but I haven't found any coverage of this in the handbook.
Is there a "how to" somewhere (or is there something else I should
be doing)?
Upon connecting the camera, I get:
umass0: vendor 0x0784 product 0x4300, rev 1.10/3.00
27 matches
Mail list logo
