Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Dec 2008 09:14:15 -0200
From:      "Renato Botelho" <rbgarga@gmail.com>
To:        "Hans Petter Selasky" <hselasky@c2i.net>
Cc:        freebsd-current@freebsd.org, current@freebsd.org, Alfred Perlstein <alfred@freebsd.org>
Subject:   Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks.
Message-ID:  <747dc8f30812260314u7b2a3c17t8faf3fe09808aea3@mail.gmail.com>
In-Reply-To: <747dc8f30812241058md9f782j64e192dc735dbaff@mail.gmail.com>
References:  <20081222214010.GA18389@elvis.mu.org> <747dc8f30812240236q13be1abdo58ced0f4faab8d29@mail.gmail.com> <200812241212.02913.hselasky@c2i.net> <747dc8f30812241058md9f782j64e192dc735dbaff@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 24, 2008 at 4:58 PM, Renato Botelho <rbgarga@gmail.com> wrote:
> On Wed, Dec 24, 2008 at 9:12 AM, Hans Petter Selasky <hselasky@c2i.net> wrote:
>> On Wednesday 24 December 2008, Renato Botelho wrote:
>>> On Mon, Dec 22, 2008 at 7:40 PM, Alfred Perlstein <alfred@freebsd.org>
>> wrote:
>>> > We're going to usher in the New Year with a new usb stack.
>>> >
>>> > Now is the time to test, test, test.
>>> >
>>> > It is also the time to point out anything missing from usb2 that
>>> > is in usb1.
>>> >
>>> > In two weeks, on Jan 3rd I will switch the GENERIC kernel to use
>>> > usb2.
>>> >
>>> > The old usb code will remain in case there is any fallout.
>>> >
>>> > Depending on how this trial goes we will hopefully move to the new
>>> > stack entirely within a few weeks after bug reports start dying
>>> > down.
>>>
>>> Alfred,
>>>
>>> I tried a build yesterday with a fresh -current (Revision: 186431),
>>> after boot I couldn't have my usb keyboard (Sun Type 7 Unix) working.
>>>
>>> I've collected these lines from messages, and i would like to know
>>> what i can do to give you necessary information to fix this.
>>>
>>> Dec 23 14:48:35 botelhor kernel: Trying to mount root from ufs:/dev/ad4s1a
>>> Dec 23 14:48:35 botelhor kernel: usb2_alloc_device:1417: set address 2
>>> failed (ignored)
>>> Dec 23 14:48:35 botelhor kernel: usb2_alloc_device:1452: getting
>>> device descriptor at addr 2 failed!
>>> Dec 23 14:48:35 botelhor kernel: uhub_reattach_port:401: could not
>>> allocate new device!
>>> Dec 23 14:48:39 botelhor lpd[1090]: lpd startup: logging=0
>>> Dec 23 14:48:40 botelhor kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
>>> Dec 23 14:48:40 botelhor kernel: fuse4bsd: compiled against kernel
>>> config /usr/obj/usr/src/sys/GARGA
>>> Dec 23 14:49:05 botelhor kernel: usb2_alloc_device:1417: set address 2
>>> failed (ignored)
>>> Dec 23 14:49:05 botelhor kernel: usb2_alloc_device:1452: getting
>>> device descriptor at addr 2 failed!
>>> Dec 23 14:49:05 botelhor kernel: uhub_reattach_port:401: could not
>>> allocate new device!
>>>
>>> Here is the same lines with current usb stack:
>>>
>>> Dec 23 14:52:23 botelhor kernel: uhub5: <vendor 0x0430 product 0x100e,
>>> class 9/0, rev 2.00/1.04, addr 2> on uhub3
>>> Dec 23 14:52:23 botelhor kernel: uhub5: 4 ports with 3 removable, bus
>>> powered Dec 23 14:52:23 botelhor kernel: ums0: <vendor 0x0566 USB Mouse,
>>> class 0/0, rev 1.10/51.27, addr 3> on uhub5
>>> Dec 23 14:52:23 botelhor kernel: ums0: 3 buttons and Z dir.
>>> Dec 23 14:52:23 botelhor kernel: ukbd0: <vendor 0x0430 Sun USB
>>> Keyboard, class 0/0, rev 2.00/1.04, addr 4> on uhub5
>>> Dec 23 14:52:23 botelhor kernel: kbd2 at ukbd0
>>>
>>> Thanks
>>
>>
>> Hi,
>>
>> I have made some patches for this kind of issues which are not yet
>> in -current.
>>
>> You can try to fetch the latest from:
>>
>> svn --username anonsvn --password anonsvn \
>>      checkout svn://svn.turbocat.net/i4b
>>
>> cd i4b/trunk/i4b/src/sys/dev
>> cp -r usb2 /sys/dev/
>> make -C /sys/modules/usb2 clean all install
>
> I still had problems, I'll collect more details on Friday and
> send you.

Here are my /var/log/messages:

http://pastebin.com/f6c28d7ca

I still have problems with my keyboard.

BTW, I added a #include of usb2_ioctl.h to fix lack of
USB_SHORT_XFER_OK definition, could it cause any
problems?

Thanks
-- 
Renato Botelho



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?747dc8f30812260314u7b2a3c17t8faf3fe09808aea3>