Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17256 - [kernel26] Unable to print.

Attached to Project: Arch Linux
Opened by Chris Bannister (Zariel) - Monday, 23 November 2009, 16:22 GMT
Last edited by Dan Griffiths (Ghost1227) - Monday, 01 March 2010, 19:40 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have cups setup working fine, but I cant print, it goes through cups without issue but nothing happens with dmesg spitting this out.

parport0: BUSY timeout (-4) in compat_write_block_pio

To fix this I recompiled the kernel with

CONFIG_PARPORT_PC_FIFO=n

Which fixes it. The printer is a USB Epson DX3800, cannot use escputil either which gives the same error.


Additional info:
kernel26-lst: 2.6.27.39-1


Steps to reproduce:
escputil -r /dev/lp0 -i
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Monday, 01 March 2010, 19:40 GMT
Reason for closing:  No response
Additional comments about closing:  No response in 2 months. Please reopen if necessary.
Comment by Tobias Powalowski (tpowa) - Monday, 23 November 2009, 16:46 GMT
A usb printer should never use /dev/lp0, this is only for parport printers.
Comment by Chris Bannister (Zariel) - Monday, 23 November 2009, 19:02 GMT
I get this in dmesg,

parport_pc 00:02: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (interrupt-driven).
Comment by Tobias Powalowski (tpowa) - Thursday, 26 November 2009, 17:54 GMT
Are you using a usb cable or a parport cable?
Have you blacklisted usblp module?
Comment by Andreas Radke (AndyRTR) - Thursday, 26 November 2009, 18:04 GMT
what's the device permissions? for the LTS kernel you may need a custom udev rule until we upgrade to udev 147. see the tons of forums threads. does the printer work with the kernel26 pkg (2.6.31.x)?
Comment by Chris Bannister (Zariel) - Thursday, 26 November 2009, 20:58 GMT
Its a USB cable, I have the udev rules in. Cups sees the printer fine.

crw-rw---- 1 root lp 6, 0 2009-11-23 16:31 lp0

lsmod|grep lp

lp 11108 0
parport 33260 3 ppdev,lp,parport_pc

Comment by Tobias Powalowski (tpowa) - Thursday, 26 November 2009, 21:08 GMT
A usb printer does not use parport or lp at all. It uses usb host controller modules and the rest is done by libusb and /dev/bus/usb.
Check if usblp module is loaded, if yes blacklist it and unload it.
Comment by Chris Bannister (Zariel) - Thursday, 26 November 2009, 21:53 GMT
usblp is not loaded.
Comment by Chris Bannister (Zariel) - Thursday, 17 December 2009, 18:19 GMT
Its connected VIA usb but it has an optional parport. This is the dmesg output when plugging it in,

ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: registered pardevice
ppdev0: unregistered pardevice
usb 5-2: USB disconnect, address 4
usb 5-2: new full speed USB device using uhci_hcd and address 5
usb 5-2: configuration #1 chosen from 1 choice
Comment by Andreas Radke (AndyRTR) - Monday, 28 December 2009, 18:57 GMT
Please try with udev and new udev-compat from testing. Additional compat rules may be needed for your device.

How does udev from core and testing set permissions for your device?
Comment by Chris Bannister (Zariel) - Monday, 04 January 2010, 17:16 GMT
I havnt tested thoroughly but blacklisting parport module helps alsp, stopping ppdev output in dmesg. Ill try new kernels when I can.
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 30 January 2010, 22:37 GMT
any news on this?

Loading...