> > >
> > > $ls -l /dev/pcd*
> > > brw-rw---- 1 marc cdwriter 46, 0 Feb 10 13:59 /dev/pcd0
> > > brw-rw---- 1 marc cdwriter 46, 1 Feb 10 13:59 /dev/pcd1
> > > brw-rw---- 1 marc cdwriter 46, 2 Feb 10 13:59 /dev/pcd2
> > > brw-rw---- 1 marc cdwriter 46, 3 Feb 10 13:59 /dev/pcd3
> >
> > 1. what version of Mandrake are you running?
>
> I run currently 8.1 on this machine (laptop).
>
> > 2. Do you use devfs? Do you mount devfs?
>
> Yes I use devfs and I pass devfs=mount as a kernel parameter at boot
time
> (as
> Mandrake set it up).
>
> > 3. who created these files? They must not exist with mounted devfs
>
> I don't remember having created these files.
> I surely used this script taken from this howto :
> http://www.torque.net/parport/paride.html
>
> #!/bin/bash
> #
Oh :(
Well, Marc, the bad news are it is not going to work out-of-the-box. My
question - would you help in testing it? You will have to update to
current cooker (or at least beta4 - I have heard it is out) because
testing on 8.1 is pretty useless, devfs support there is largely broken
and I do not have time to test old versions anyway. You also have to
apply patch to kernel and compile it. I'll tell you what to do so here
is no problem.
O.K. several points:
- currently pcd has very poor devfs support. It registers only vanilla
/dev/cdroms/ entry; it does not register anything else. It means with
devfs no /dev/pcd* are created that violates devices.txt :-)
- everything else in paride (pg = generic, pd = disk, pt = tape) seems
to register corresponding /dev/{pg,pd,pt}/* entries and devfsd knows how
to create compatibility links for them
So to (fully) support paride with devfs we need
- patch kernel pcd.c to create correct device entries; in which case
"correct" means /dev/pcd/pcd* IMHO and /dev/cdroms/ links
- patch devfsd to create compatibility links
- think about modules.devfs configuration. We have to deal with both
interface+device here much like for SCSI.
Pixel is it possible to autodetect paride devices (assuming, they are
connected on install) like for SCSI ppa/imm?
My concern is, loading more than one parport driver may not be
transparent. I.e. adding paride to standard modules.devfs may
accidentally trigger loading of paride that may break other modules (lp
or ppa/imm). Anybody knows about it?
-andrej
|