Date: Mon, 9 Mar 2009 14:04:34 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: "M. Warner Losh" <imp@bsdimp.com> Cc: usb@freebsd.org, thompsa@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Latest kernel breaks scanner Message-ID: <200903091404.34912.hselasky@c2i.net> In-Reply-To: <20090309.065558.-432839106.imp@bsdimp.com> References: <20090308.154353.-1350498283.imp@bsdimp.com> <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 09 March 2009, M. Warner Losh wrote: > In message: <200903091233.55089.hselasky@c2i.net> > > Hans Petter Selasky <hselasky@c2i.net> writes: > : On Sunday 08 March 2009, Andrew Thompson wrote: > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > : > > > : > > Andrew Thompson <thompsa@FreeBSD.org> writes: > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it > : > > : > doesn't work. Scanner not found by xsane. > : > > : > : > > : Are you sure its not this? > : > > : > : > > : 20090227: > : > > : The /dev handling for the new USB stack has changed, a > : > > : buildworld/installworld is required for libusb20. > : > > > : > > Yes. Been there, done that. Also have the libmap.conf changes in > : > > place for old binaries that had worked for months before that. xsane > : > > used to just work in this setup, but now fails. Looks like some kind > : > > of mismatch in the ABI: > : > > > : > > found USB scanner (UNKNOWN vendor and product) at device > : > > /dev/uscanner0 > : > > : > Not sure what would have caused that. Before you spend too much time on > : > this you may want to note that the integration patches for libusb into > : > the ports build will likely be committed tomorrow. This will bump the > : > port numbers so the affected ports rebuild, hopefully sane with DTRT > : > after that. > : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb > : backend? > > never had to do that before... Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is broken, and the fallback to libusb backend will maybe solve your problem temporarily if you rm /dev/uscanner0 . Actually that is another question: Should we remove ID's from uscanner.c which will work fine attaching through the libusb backend ? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903091404.34912.hselasky>