Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Nov 2006 10:39:41 -0800
From:      Doug Barton <dougb@FreeBSD.org>
To:        freebsd-current@freebsd.org
Subject:   EHCI problem on -current, and unknown devs
Message-ID:  <4564996D.50808@FreeBSD.org>

next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9A35C555D2E066A40ED641D2
Content-Type: multipart/mixed; boundary="------------040001030900060505090703"

This is a multi-part message in MIME format.
--------------040001030900060505090703
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

[ No response from the -usb list, so I'll try here. ]

Howdy,

I have a new Dell Latitude D620, and using recent -current I get this:

ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem
0xffa80000-0xffa803ff irq 20 at device 29.7 on pci0
ehci0: Could not map memory
device_attach: ehci0 attach returned 6

FWIW, I also saw a user on the -stable list report this same problem.
I'm assuming this is bad, but what to do about it?


I'm also getting some unknown devices:

uhub4: <vendor 0x413c product 0xa005, class 9/0, rev 2.00/50.18, addr
2> on uhub0
uhub5: <vendor 0x0b97 product 0x7761, class 9/0, rev 1.10/1.10, addr
3> on uhub4
ugen2: <vendor 0x413c product 0x8103, class 224/1, rev 2.00/24.22,
addr 6> on uhub4
uhub6: <vendor 0x413c product 0x0058, class 9/0, rev 2.00/0.00, addr
2> on uhub3

Vendor ID 0x413c is Dell, and is already in the usbdevs file. The
other vendor is O2, and I got their ID for the attached patch from the
list at http://www.usb.org/developers/tools. The 0x0058 device is
already in our usbdevs file, it's the port replicator (docking
station) that the laptop is plugged into currently. I added the 0x8103
device in the attached patch based on an entry in the NetBSD usbdevs
file. (The entry makes sense to me as well, since I have one of those.)

So I have two questions ... for the devices (and vendors) that are
already in my local usbdevs file, why are they still showing up by ID?
And how do I find the device IDs for the two unknown devices? I
imagine that the O2 device is related to my built in smart card
reader, not sure about the other one.


Thanks,

Doug

--=20

    This .signature sanitized for your protection


--------------040001030900060505090703
Content-Type: text/plain;
 name="usbdevs-v"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline;
 filename="usbdevs-v"

Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(=
0x0000), rev 1.00
 port 1 powered
 port 2 addr 2: full speed, self powered, config 1, product 0xa005(0xa005=
), vendor 0x413c(0x413c), rev 50.18
  port 1 powered
  port 2 powered
  port 3 addr 3: full speed, power 200 mA, config 1, product 0x7761(0x776=
1), vendor 0x0b97(0x0b97), rev 1.10
   port 1 addr 4: full speed, power 100 mA, config 1, Biometric Coprocess=
or(0x2016), STMicroelectronics(0x0483), rev 0.01
   port 2 addr 5: full speed, self powered, config 1, O2Micro CCID SC Rea=
der(0x7762), O2(0x0b97), rev 1.10
   port 3 powered
  port 4 addr 6: full speed, self powered, config 1, product 0x8103(0x810=
3), vendor 0x413c(0x413c), rev 24.22
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(=
0x0000), rev 1.00
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(=
0x0000), rev 1.00
 port 1 powered
 port 2 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(=
0x0000), rev 1.00
 port 1 powered
 port 2 addr 2: full speed, self powered, config 1, product 0x0058(0x0058=
), vendor 0x413c(0x413c), rev 0.00
  port 1 addr 3: full speed, self powered, config 1, USB2.0 Hub Controlle=
r(0x0058), NEC Corporation(0x0409), rev 1.00
   port 1 powered
   port 2 powered
   port 3 powered
   port 4 powered
  port 2 powered
  port 3 addr 4: low speed, power 100 mA, config 1, Trackball(0xc404), Lo=
gitech(0x046d), rev 2.20
  port 4 powered


--------------040001030900060505090703
Content-Type: text/plain;
 name="usbdevs.diff"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline;
 filename="usbdevs.diff"

Index: usbdevs
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /usr/local/ncvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.278
diff -u -u -r1.278 usbdevs
--- usbdevs	15 Nov 2006 09:13:24 -0000	1.278
+++ usbdevs	22 Nov 2006 00:10:13 -0000
@@ -465,6 +465,7 @@
 vendor ZEEVO		0x0b7a	Zeevo
 vendor KURUSUGAWA	0x0b7e	Kurusugawa
 vendor ASIX		0x0b95	ASIX
+vendor O2Micro		0x0b97	O2 Micro, Inc.
 vendor USR		0x0baf	U.S. Robotics
 vendor REALTEK		0x0bda	RealTek
 vendor ADDONICS2	0x0bf6	Addonics
@@ -821,6 +822,8 @@
 /* Dell products */
 product DELL PORT		0x0058	Port Replicator
 product DELL BC02		0x8000	BC02 Bluetooth USB Adapter
+product DELL TM350		0x8103	TrueMobile 350 Bluetooth USB Adapter
+
=20
 /* Delorme Paublishing products */
 product DELORME EARTHMATE	0x0100	Earthmate GPS


--------------040001030900060505090703--

--------------enig9A35C555D2E066A40ED641D2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.0 (FreeBSD)

iD8DBQFFZJlxyIakK9Wy8PsRArNfAKCxR5D1BQvw68ShzF0+nA02O+nPmQCdHjLp
Dej9tlDX4wySASP2+fRCkyI=
=K8vz
-----END PGP SIGNATURE-----

--------------enig9A35C555D2E066A40ED641D2--



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