Date: Sun, 27 Jan 2013 19:15:47 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: George Mitchell <george+freebsd@m5p.com> Cc: freebsd-current@freebsd.org Subject: Re: ulpt can't attach Lexmark E120 Message-ID: <201301271915.47712.hselasky@c2i.net> In-Reply-To: <51056CAC.9070105@m5p.com> References: <5105527F.3010708@m5p.com> <201301271733.14312.hselasky@c2i.net> <51056CAC.9070105@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 27 January 2013 19:06:36 George Mitchell wrote: > On 01/27/13 11:33, Hans Petter Selasky wrote: > > On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > >> System: Raspberry Pi > >> uname: r245840M (Alie Tan's image from 25 January) > >> > >> By comparison, this Lexmark E120 printer attaches and prints with no > >> difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > >> > >> ugen0.5: <Lexmark International> at usbus0 > >> ulpt1: <Lexmark International Lexmark E120n, class 0/0, rev 2.00/1.00, > >> addr 5> on usbus0 > >> device_attach: ulpt1 attach returned 12 > >> > >> Also, an HP CM1015 attaches without a problem. What should I try next? > > > > Also try to set: > > > > sysctl hw.usb.ulpt.debug=15 > > It's a non-debug build of ulpt, so that doesn't exist: > sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory > > > before attaching. > > > > Also try to attach one printer alone. > > > > --HPS > > After unplugging the HP: > > root@pi:/home/george # usbconfig > ugen0.1: <OTG Root HUB DWCOTG> at usbus0, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen0.2: <product 0x9512 vendor 0x0424> at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=SAVE > ugen0.3: <product 0xec00 vendor 0x0424> at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > ugen0.4: <Lexmark E120n Lexmark International> at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON > > I attached the usbdump output, though there seem to be quite a few > packets not connected with ulpt burying the interesting packets in > the noise. -- George Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301271915.47712.hselasky>