Bug 85067

Summary:	[uscanner] Cannot attach ScanJet 4300C to usb device
Product:	Base System	Reporter:	P. U. Kruppa <root>
Component:	usb	Assignee:	freebsd-usb (Nobody) <usb>
Status:	Open ---
Severity:	Affects Only Me
Priority:	Normal
Version:	6.0-BETA2
Hardware:	Any
OS:	Any

Description P. U. Kruppa 2005-08-18 05:30:14 UTC

When I plug my ScanJet 4300C to the USB port I get this # dmesg

uscanner1: vendor 0x03f0 product 0x0305, rev 1.00/0.00, addr 2
uscanner1: setting config no failed
device_attach: uscanner1 attach returned 6
uhub0: port 2, set config at addr 2 failed
uhub0: device problem (STALLED), disabling port 2

Fix: 

This is no vital problem, since I can boot into Windows and run my
ScanJet there.  But if there is no fix, the ScanJet 4300C should be taken
 out of the list of supported hardware.

Comment 1 Mark Linimon freebsd_committer

2008-01-29 10:06:34 UTC

State Changed
From-To: open->suspended

Mark suspended awaiting patches.

Comment 2 olli 2008-05-23 09:02:15 UTC

Just a small follow-up:  The ScanJet 4300C *still* doesn't
work with an up-to-date 7-stable.  Same dmesg messages.

Since this is a long-standing problem and it doesn't seem
to be fixed anytime soon, I *strongly* recommend that the
ScanJet 4300C entry should be removed from the uscanner(4)
manual page, or marked as "currently broken" or similar,
so people don't go buy that scanner, believing that it
will work because it's explicitely listed in the manpage,
like I did.  :-(

Best regards
   Oliver

PS:  From my reading of the code, the problem is not in
uscanner(4) but rather in the non-device-specific USB bus
code.  It seems to disable the port before it ever reaches
uscanner's attach function.  However, I'm not a USB expert,
so I can't tell for sure.

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

In my experience the term "transparent proxy" is an oxymoron (like jumbo
shrimp).  "Transparent" proxies seem to vary from the distortions of a
funhouse mirror to barely translucent.  I really, really dislike them
when trying to figure out the corrective lenses needed with each of them.
        -- R. Kevin Oberman, Network Engineer

Comment 3 Eitan Adler freebsd_committer

2018-05-28 19:48:41 UTC

batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.