On Fri, 15 Aug 2003, Gene Heskett wrote:
I can confirm that this does not appear to be printer related, this
nearly exact scenario just happened to me while running test3-mm2. So
I powered down the printer, in this case an Epson C82 being driven by
cups, and then rebooted to 2.4.22-rc2.
On Friday 15 August 2003 12:25, Alan Stern wrote:
On Fri, 15 Aug 2003, Gene Heskett wrote:
I can confirm that this does not appear to be printer related,
this nearly exact scenario just happened to me while running
test3-mm2. So I powered down the printer, in this case an Epson
C82 being
On Wednesday 06 August 2003 16:30, Alan Stern wrote:
On Wed, 6 Aug 2003, Peter Denison wrote:
Having just upgraded to 2.4.21, the first time I tried to print,
the following happened. The printer started to print, but gave up
after a while and spat out just about 1 of image. Needless to
say, it
Having just upgraded to 2.4.21, the first time I tried to print, the
following happened. The printer started to print, but gave up after a
while and spat out just about 1 of image. Needless to say, it all worked
fine under 2.4.20.
Intel 82801BA based MB, running stock 2.4.21 (compiled with gcc
On Wed, 6 Aug 2003, Peter Denison wrote:
Having just upgraded to 2.4.21, the first time I tried to print, the
following happened. The printer started to print, but gave up after a
while and spat out just about 1 of image. Needless to say, it all worked
fine under 2.4.20.
Intel 82801BA
On Wed, 6 Aug 2003, Alan Stern wrote:
On Wed, 6 Aug 2003, Peter Denison wrote:
kernel: 2: [d66d9060] link (0001) e3 IOC Active Length=0 MaxLen=7ff DT1
EndPt=0 Dev=2, PID=e1(OUT) (buf=)
This indicates more communications problems. Have you checked that your
USB cable is
