Bug 86458 - Epson Stylus C 60 on usb
Epson Stylus C 60 on usb
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Zaitcev
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-22 15:11 EST by Beppe di Bolzano
Modified: 2013-05-06 13:15 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-05 14:55:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Beppe di Bolzano 2003-03-22 15:11:53 EST
Description of problem:
I have my printer on an usb port (and it works perfectly under Windows).Under
Linux 8.0A (Second Edition) it does not work at all. I have set it as "Local
printer" and "/dev/usb/lp0", then I've sent a file to the printer in two
different ways (# cp upgrade.log /dev/usb/lp0; then # lpr -p upgrade.log;), but
it does not go.
With the "cp" command I have tried to send the file also to
/dev/usb/lp1,.../lp2,.../lp3 and ..../lp4: nothing to do.
Can somebody help me?
Thanks,
Beppe 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
    
Actual results:
It does not work at all under Linux

Expected results:


Additional info:
Comment 1 Pete Zaitcev 2003-04-14 14:52:09 EDT
This has to go through some sort of support loop. I cannot guarantee
any response time for direct track Bugzilla reports. Sorry.

Having said that, please attach output of dmesg and /proc/bus/usb/devices,
taken AFTER the printer was attached. Please, DO NOT drop them into
the comment box! Use "Create a New Attachement" link instead.
Comment 2 Pete Zaitcev 2003-06-02 23:05:44 EDT
Interest lost? Still waiting for those dmesgs and /proc/bus/usb/devices.


Note You need to log in before you can comment on or make changes to this bug.