be missing a udev or systemd rule (not sure which Ubuntu uses) to
make the device accessible to the console user.
Of course, this is all assuming it's the actual problem... or the only one.
What are the permissions of /dev/bus/usb/002/006? And what are the
user's groups set to?
Monty
eg, Fedora,
will be an exercise in reading the Fedora package's spec files
carefully.
Most of the install documentation shipped with the current sane
backends is out of date, incorrect for a given distribution, or both.
It still talks about the 2.6 kernel series as if it were new...
Monty
ely forgotten
about it in fact. :-|
Monty
-- next part --
A non-text attachment was scrubbed...
Name: sane-backends-1.0.23-avision-fb6280e.patch
Type: application/octet-stream
Size: 5086 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/sane-de
preciate info on how you made it work.
Regards,
Monty
it. If you had quality problems with
> 1.0.14 or 1.0.15 Debian packages, you should have reported that back
> then.
Fine, I'll shut up then. It's my time and I'm uninterested in waving
dicks. I wrote the code and that original code still works great for
me. The rest of you can figure it out on your own. My scanner works.
Terribly sorry for the offense.
Monty
rent
models across a family of ten related chips is unworkable when changes
to any one model break ten others that can't even be tested because
the author doesn't own the hardware to do the testing.
I'll put up the last LiDE20 driver (which works: I'm still using it) I
contributed as soon as the machine it's on is on the Net again (just
moved to a new house, IT there is in disarray).
Monty
one direction or the other so that it
suddenly becomes noticable.
Monty
(sorry, I missed the third scanner; I know the LiDE 20 and 30 are well
supported)
Monty
ted by 1.0.13, and you do want at least that version.
> I also noted in the spec of my local supplier that the USB port is USB 2.0
> compatible, does this mean it doesn't work with USB 1.1? I ask because my
> Linux system is an old Dell Latitude.
It will work with USB 1.1.
Monty
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Sep 11, 2003 at 01:08:37PM +0200, Till Kamppeter wrote:
> Monty wrote:
> >LiDE20 and liDE30 never worked well; the autocal code was broken. I
> >know, I have them. I spent several
run all my devices off a hub;
connecting directly to the machine gets 'I/O error', but connecting
through a hub always works. It's not's SANE's fault; this happens
with 3/4 of my USB devices, the fourth (a flash card reader)
mysteriously always works]
Monty
o weeks.
LiDE20 and liDE30 never worked well; the autocal code was broken. I
know, I have them. I spent several days debugging the plustek backend
for exactly these scanners last month; see CVS (gerhard integrated my
patches I believe), or contact me for a Canoscan LiDE patch against
vanilla 1.0.12.
Monty
s with your files
> (e.g. symlink attack). Further more in /tmp, the file might be deleted
> on the next boot.
I would hope that you're calibrating more often than every boot. My
machines only boot a few times a year...
Monty
tion, but the better one will be to save the
> calibration data on on the disc...
> Any comments?
I was wondering about this too when working on the CanoScan LiDE
calibration. I noticed several backend drivers stash the data in a
file in /tmp and reread it on each scan...
Monty
'make things work' would certainly cause some Linux users a
heart attack, I did intend this to read 'make things break'.
Monty
ere scanned at 100dpi with identical settings and no
plustek.conf settings beyond [usb] and device.
Given that the LiDEs are decent [if very vanilla], well behaved
scanners currently selling for $35 [!] new, I hope this will benefit
quite a few users. The patch has already sold three new scanners in
the #sane channel in two days :-)
Monty
16 matches
Mail list logo
