On Sat, Jul 17, 1999 at 05:44:27PM -0400, Steve Fox wrote:
>
> I also have the problem of "Device Not Configured"
>
> Can you explain what you mean by your suggestions below?
> I don't know how to "configure correctly"
> I don't know how to determine if other modules are claiming resources.
>
Well, this depends on the kind of drive you have. We still do not know this.
So I talk about my ditto max external (parallel port):
I have under redhat 5.2 / kernel 2.2.10 the following /etc/conf.modules:
######### ftape f�r Ditto max ##########################
alias char-major-27 zftape
options ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
# options bpck-fdc ft_fdc_irq=7 ft_fdc_base=0x378
pre-install zftape modprobe -r lp ppa parport_pc parport_probe parport
These entries will enable the kernel (a thread of it, name kmod) to load
all the needed modules automatically, when I type in e. g. ftmt -f /dev/qft0 status.
Alternatively I could load the modules manually:
rmmod lp
rmmod ppa
rmmod parport_pc
rmmod parport_probe
rmmod parport
insmod ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
insmod zftape
insmod bpck-fdc
As you can see, I commented out options bpck-fdc: In former times I seemed
to need those options, but since I upgraded to ftape-4.x-1999_06_02
I had to leave them out.
And you can see as well, that I have connected to my parallel port
not only my ditto, but also a printer and a zip drive. Their modules
claim the same resources ftape needs, so before trying to load
ftape I have to unload lp, ppa and so on.
Ok, as I said: All of this applies to my external ditto max.
If you have a different drive, you have to change the settings above.
So you will have to find out if you need bpck-fdc, or ftape-internal instead
or something else. You will have to read some of the docs shipped with
ftape or that can be found on Claus' homepage.
And to find out if a strange module claims valuable resources, I would
recommend:
First have a look into /var/log/messages, if there is a line like
...grabs io or grabs irq or something similar.
Second: Type in
cat /proc/ioports
to see, if another module uses the same ioports, your drive does.
But to be honest: This collision problem should only occur in case you
have a parallel port drive. If not, you should presumably not run into
such a problem (but who knows...)
Let me repeat: There is no way to avoid reading at least a bit of
the docs, because you have to find out which special settings
your own drive needs. Maybe it doesn't need any options at all:
As far as I know there are some automatic mechanisms, but
I would assume that stating some options explicitly should
be a good idea.
Good luck,
Juergen.
--
*****************************************************************
* Juergen Leising, E-Mail: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
*****************************************************************
