USB scanner unrecognized on 1.11-DEVELOPMENT

[Francois Tigeot]

On Tue, Jan 15, 2008 at 11:06:21AM +0100, Matthias Schmidt wrote:
> 
> * Francois Tigeot wrote:
> > 
> > I recently upgraded a machine from Dragonfly 1.10.1 to a recent
> > 1.11.0-DEVELOPMENT (as of today).
> > 
> > An Epson Perfection 1240U USB scanner which worked fine with 1.10.1 is now
> > unrecognized. Pluging and unpluging the USB cord doesn't result in any
> > kernel message visible in dmesg.
> 
> According to the sources we have an entry for your model:
> 
>  {{ USB_DEVICE(0x04b8, 0x010b) }, 0 }, /* Perfection 1240U/1240Photo */
> 
> I'm currently preparing a mass update of USB quirks and it seems like
> the vendor ID of Epson has changed.  The new entry from FreeBSD device
> ID list looks like this:
> 
>  {{ USB_DEVICE(0x03f8, 0x010b) }, 0 }, /* Epson Perfection 1240U / */
> 
> Note the difference between 0x04b8 and 0x03f8.  To check that I'm not
> wrong, you could change the ID in the uscanner source, recompile the
> module, reload it and check again if the scanner is detected:

I tried it and it didn't change anything: no kernel messages either.

However, I found out there's was a difference between a standalone
uscanner module and one compiled in the kernel.

Standalone module:
	- original -> nothing
	- patched -> nothing

Uscanner in kernel:
	- original -> some kernel messages appear at startup

	# dmesg | grep uscanner
	uscanner0: <EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr 2> on uhub0
	uscanner0: at uhub0 port 2 (addr 2) disconnected
	uscanner0: detached

	- patched -> some messages about ugen0
	ugen0: at uhub0 port 2 (addr 2) disconnected
	ugen0: detached

There's definitely something fishy going there.

-- 
Francois Tigeot