Hi,
Eddy De Greef wrote:
> After he compiled everything from source, upgraded his kernel,
> and altered the parport BIOS settings, Neal's problem disappeared.
> It's impossible to say what was the real problem, unfortunately.
>From what I read on parport-devel this is a bug in the SuSE kernel
reg
On 15-06-04 17:10:24 Jochen Eisinger wrote:
> Neal Gamradt wrote:
> > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5
> > from 'parport0'
> > [...]
> > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00
> > from 'parport0'
>
> the backend gets the correct value first, but later the scanner
Hi,
Neal Gamradt wrote:
> [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5
> from 'parport0'
> [...]
> [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00
> from 'parport0'
the backend gets the correct value first, but later the scanner only
returns the wrong value 0x00. To me this looks lik
Hello All,
First off I would like to thank you all for the the
work you have put into scanner support for Linux, I
have a Mustek 600CP and historically I have never had
much trouble setting it up thanks to the great work
you have done. I recently upgraded from Suse 8.2 to
Suse 9.1. Currently I a
