| Author |
Message |
ghstryder
|
|
Post subject: Re: RE: Printer not Working
 Posted: 01.09.2011, 18:11
|
|
Joined: 2010-09-12
Posts: 88
Location: Detroit
Status: Offline
|
|
|
saxxonian wrote:
so, is my above mentioned problem then, one of USB-parallel adapter not being "transparent" anymore to CUPS? what should I look into?
saxxonian; it sure looks that way. I count at least 2 instances like yours, where the Parallel/USB adapter setup isn't working. Something happened, since many of us had to do as hubi said and remove/recreate our printers. It leads me to wonder if support for the adapter didn't survive. I wish I had suggestions for you. |
|
|
| |
|
|
|
 |
|
saxxonian
|
|
|
Post subject: RE: Re: RE: Printer not Working
Posted: 02.09.2011, 14:35
|
|
Joined: 2010-09-11
Posts: 27
Location: Brasov, Romania
Status: Offline
|
|
| thanx ghstryder for your post, I just don't know where to start looking... |
|
|
| |
|
|
|
|
|
saxxonian
|
|
|
Post subject:
Posted: 02.09.2011, 15:00
|
|
Joined: 2010-09-11
Posts: 27
Location: Brasov, Romania
Status: Offline
|
|
dmesg | tail after trying to print a test page says:
Code:
[ 9744.602153] usb 1-2: New USB device found, idVendor=067b, idProduct=2305
[ 9744.602158] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9744.602162] usb 1-2: Product: IEEE-1284 Controller
[ 9744.602164] usb 1-2: Manufacturer: Prolific Technology Inc.
[ 9759.972727] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
[ 9765.072879] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
[ 9770.173057] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
[ 9775.273211] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
[ 9780.372379] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
[ 9785.471550] usb 1-2: usbfs: process 5541 (usb) did not claim interface 1 before use
does this hint to something? |
|
|
| |
|
|
|
|
|
hy
|
|
|
Post subject: sorry for pushing the topic
Posted: 31.10.2011, 13:32
|
|
Joined: 2010-09-14
Posts: 139
Status: Offline
|
|
| I will have to do more printing than usual in the next weeks. Unfortunately the problem persists and I am really sick of saving to pdf, restarting the machine, booting into win, print the pdf, restart, boot up aptosid, reopen all applications, go on with the work... it sucks |
|
|
| |
|
|
|
|
|
dieres
|
|
|
Post subject:
Posted: 01.11.2011, 12:52
|
|
Joined: 2010-09-12
Posts: 30
Status: Offline
|
|
| if it works only in win, install win in virtualbox, let windows announce the printer in network and configure linux to use the winprinter. Might be a workaround to avoid this nasty pdf printing and booting. |
|
|
| |
|
|
|
|
|
hy
|
|
|
Post subject: [SOLVED]
Posted: 14.11.2011, 13:53
|
|
Joined: 2010-09-14
Posts: 139
Status: Offline
|
|
Hi,
yesterdays (2011/11/13) d-u gave me new cups-s7uff, so I tried again.
Actually the printer was not recognised, as in the months before. But I found the following page:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511762
where it says:
Hint: Run "cupstestppd /etc/cups/ppd/Farblaser.ppd" and fix any errors.
I replaced Farblaser.ppd by my printer (which is)
HP-LaserJet-4050-Series-.ppd
and deleted the sections that were erroneous due to cupstestppd.
After that it worked. The printer was not recognized but I could enter it manually [with connection:
usb://HP/LaserJet%204050%20Series]
Then it worked. I hope this might help anyone else. |
|
|
| |
|
|
|
|
|
|
