From: Raphael L. <rap...@gm...> - 2004-11-14 09:49:16
|
On Saturday 23 October 2004 13:27, Raphael Langerhorst wrote: > On Thursday 21 October 2004 09:43, Volker Stolz wrote: > > * Raphael Langerhorst <rap...@gm...>: > > >> No special code is required -- just a minimal addition to the > > >> ptal-init-script where 'moreWildcards' is defined. I didn't > > >> get a concrete patch out of him and lack the hardware to test > > >> this myself (luckily only JetDirect here :). > > >> If you use the FreeBSD port, it should take of finding libusb > > >> etc, so the above should be the only change required. > > > > > > OK, found it, thanks a lot! > > > > Jeff pointed out you might have to unload the USB-modules umass > > and ulpt, though, since those will capture the device -- ugen is > > only available if the device is not assigned to one of the above. > > Also, this won't work if you have them compiled into the kernel. > > Ah, yes, I just noticed that the device gets attached as ulpt0. I > think I have the devices in the kernel... will remove them and > rebuild kernel. > > Thanks, > Raphael > > PS: I just tried it (with ulpt0) out with a fresh 5.3-RC1 and it > didn't work... When I have removed the devices and rebuilt the > kernel I'll report back. > > > [Jeff, are you lurking here?] I am now at FreeBSD 5.3 Release, built the kernel WITHOUT ulpt, umass (and also without uscanner). The PSC 1210 gets attached to ugen0. Also I used _latest_ CVS version of hpoj and he recognizes the device but can't open it. HPOJ output is: Probing "%/dev/usb2%/dev/ugen0"... *** Found "psc 1200 series" but failed to communicate with it! *** Elapsed time for this attempt was 1 second(s). *** Check syslog file for ptal-mlcd error messages. *** See hpoj documentation for troubleshooting information. syslog output is: Nov 14 10:45:18 guardian ptal-mlcd: ERROR at ExMgr.cpp:3752, dev=<mlc:usb:probe@%/dev/usb2%/dev/ugen0>, pid=654, e=16, t=1100425518 usb_open failed! Nov 14 10:45:18 guardian ptal-mlcd: ERROR at ExMgr.cpp:2572, dev=<mlc:usb:probe@ %/dev/usb2%/dev/ugen0>, pid=654, e=25, t=1100425518 Couldn't set up print interface! Note that I think elapsed time for this attempt was 1 second(s) is more likely 0 seconds - at least I get the above message quite "immediately". Any suggestions? Raphael -- G System, The Evolving Universe - http://www.g-system.at |