primax: Thread: More on primax problem on Mandrake 9

All right, I've come to the conclusion that there are 2 different 
problems.

1) If saned-primaxd is activated, the scanner light comes on during the
init process. This happens both with the primaxd 0.5 and 1.- versions,
both on Mandrake 8.2 and 9.0. However, on Mandrake 8.2 scanning is
possible both with primaxd and with the standalone driver (although the 
standalone driver works a lot better).

2) On Mandrake 9.0 both saned - primaxd and the standalone program
apparently work and recognize the scanner except that at the moment of
scanning both fail declaring it impossible to access the resource or to
unlock IO ports, and suidi'ing or working as root does not change
anything: however, apparently access to the parallel port IS available,
because it is undoubtedly saned to switch the light on during init and
because libieee124_test does have access to the port if run as root.
Running lsof doesn't show anything running on /dev/printers/0 /dev/lp0 or
whatever (device entries are identical in 8.2 and 9.0 mandrake).

Modprobe shows that both parport and parport_pc are correctly loaded.

Question: the first problem is apparently a (minor) bug (which could be
something to do with interaction between initscripts, devfs or xinetd and
the program); could the SECOND problem be a question of different
implementation of parport access in the 2.4.19 kernel ?

-- 
Michele Alzetta

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 November 2002 10:16, ####@####.#### wrote:
> All right, I've come to the conclusion that there are 2 different
> problems.
>
> 1) If saned-primaxd is activated, the scanner light comes on during the
> init process. This happens both with the primaxd 0.5 and 1.- versions,
> both on Mandrake 8.2 and 9.0. However, on Mandrake 8.2 scanning is
> possible both with primaxd and with the standalone driver (although the
> standalone driver works a lot better).

HUUU! - I forget to mention: Don't use primaxd. You don't need it anymore.
The driver uses the native saned. It loads the libsane-primax.so and uses it.
Therefore you had to add the "primax"-entry in dll.conf.
Please  remove primaxd and configure saned. Maybe Mandrake did this already 
for you.

> 2) On Mandrake 9.0 both saned - primaxd and the standalone program
> apparently work and recognize the scanner except that at the moment of
> scanning both fail declaring it impossible to access the resource or to
> unlock IO ports, and suidi'ing or working as root does not change
> anything: however, apparently access to the parallel port IS available,
> because it is undoubtedly saned to switch the light on during init and
> because libieee124_test does have access to the port if run as root.
> Running lsof doesn't show anything running on /dev/printers/0 /dev/lp0 or
> whatever (device entries are identical in 8.2 and 9.0 mandrake).

Seems as primaxd is locking the io-ports. Remove it.

> Modprobe shows that both parport and parport_pc are correctly loaded.

The used kernel module is calles ppdev. This provides a device: 
/dev/parport/0.
Maybe this is not loaded, as some distributions have no configured the devfsd 
correctly. So you have to load it manually with: modprobe ppdev.

> Question: the first problem is apparently a (minor) bug (which could be
> something to do with interaction between initscripts, devfs or xinetd and
> the program); could the SECOND problem be a question of different
> implementation of parport access in the 2.4.19 kernel ?

There was a problem in the implementation of the 2.4.19 kernel.  But this 
schould be fixed in the latest version. Did you use the latest cvs version? 
Maybe you have to update it again.

Hope some of the hints help. 

Andre

- -- 
Andre Herms                   ####@####.####
                              http://www.cs.uni-magdeburg.de/~aherms
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE903USK/HaDUFBducRAqpnAJ47P6Xt2yEqXTlTW+P76css/G2bagCeIY8C
IgbBpQQ2hcO19ZK3okQn63c=
=WBph
-----END PGP SIGNATURE-----

On Thu, 14 Nov 2002, Andre Herms wrote:

> HUUU! - I forget to mention: Don't use primaxd. You don't need it anymore.
> The driver uses the native saned. It loads the libsane-primax.so and uses it.
> Therefore you had to add the "primax"-entry in dll.conf.
> Please  remove primaxd and configure saned. Maybe Mandrake did this already 
> for you.

Sorry, my mistake ... in the hectic attempts at getting the scanner to 
work I tried the original standalone program, and afterwards the native 
saned which loads libsane-primax.so. So when I say 'primaxd' on mandrake 
9.0 I am actually referring to saned + libsane-primax.so.

I still have a mandrake 8.2 partition and on that one both the standalone 
program and primaxd work ok, EXCEPT that primaxd switches the lamp on at 
init.

> Seems as primaxd is locking the io-ports. Remove it.

No, I don't have primaxd. Even if I remove the whole 'saned' configuration
entries and libsane-primax.so and try to install the primax_scan
standalone binary and nothing else the standalone binary won't work.

> The used kernel module is calles ppdev. This provides a device: 
> /dev/parport/0.
> Maybe this is not loaded, as some distributions have no configured the devfsd 
> correctly. So you have to load it manually with: modprobe ppdev.

Ha ! Excellent ! So if I do modprobe ppdev the various /dev/parport/ 
entries finally appear. Unfortunately, if as root user at this point I do:

primax_scan -l on

I get: 

Could not unlock IO ports. Are you superuser ?

And, as I said, I have removed all priamxd and saned stuff from my system.

> There was a problem in the implementation of the 2.4.19 kernel.  But this 
> schould be fixed in the latest version. Did you use the latest cvs version? 
> Maybe you have to update it again.

You mean the standalone program will surely NOT work because of this 
problem ??
All right, so I will try to reinstall the saned stuff and see if it works 
with modprobe ppdev (sigh ...).

-- 
Michele Alzetta

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



> You mean the standalone program will surely NOT work because of this
> problem ??
> All right, so I will try to reinstall the saned stuff and see if it works
> with modprobe ppdev (sigh ...).

The libieee1284 seems to have problems with the devfs. If I use the devfs, it 
cannot access the parport. It seemd that the different names are the problem. 
The raw parport device is expecte to be /dev/parport0. DevFS uses different 
names like /dev/parports/0. So libieee1284 cannot find it. It also doesn't 
fall back to the classical way. Normally a devfsd should fix this, but seems 
not so.

Okay enough blames.
Try to link /dev/parports/0 to /dev/parport0.
This worked for me.

Hope for you, too.

Andre


- -- 
Andre Herms                   ####@####.####
                              http://www.cs.uni-magdeburg.de/~aherms
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE91C+8K/HaDUFBducRAqFiAJ9UMaaI/gc+BYa+n9l1MwcAweXFoQCfeylH
uz+Kj9bqwCSIml0t23WyolU=
=Ol0z
-----END PGP SIGNATURE-----