boblinux, as per
http://global.shuttle.com/products/productsDownload?productId=1718&panelId=1 an
update is available for your BIOS (1.04). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it
doesn't, could you please both specify what ha
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258919
Title:
printing issue with parallel-to-usb adapter
Status in “linux” package i
I meant : cups+libusb is flawed : sorry !
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258919
Title:
printing issue with parallel-to-usb adapter
Status in “linux” package in Ubuntu:
I just made another test : I stopped the cups service, loaded usblp with
modprobe, and ran :
cat lines.ps | gs -q -sDEVICE=ppmraw -r600 -sPAPERSIZE=letter -dNOPAUSE
-sOutputFile=- - | pnm2ppa --eco -v 720 -i - -o - > /dev/usb/lp0
so : lines.ps contains 56 lines to be printed, which fails with
c
I ran a last quick search : I began diving in libusb programming : and
this is what i was afraid of : they don't use the usual Unix special
files : they address the usb devices on the bus directly, as I found on
this example :
A short introduction to libusb | Roar of the Jespersaur
http://www.jesp
I am sorry I have been unclear : with the old Unix, I was able to run
low level tests such as :
cat test_file > /dev/lp0
with such a test I would have been able to test the kernel driver only;
so would have I been able to do with usblp, which generates such special
devices : I could have generate
Sorry I have been busy all week.
Before posting to the usb list, do you confirm my first guess that this
may be a kernel bug ? I saw that cups does not support usblp anymore.
Can we be sure that this is not a cups issue ? I just mentioned the
kernel because it seemed one possible thing to do. But
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
8 matches
Mail list logo
