Re: [Sheflug] Parallel IDE CD-ROM frustrations

[James Wallbank <nospam [at] lowtech.org>]

Hi All (but particularly Alex),

Okay, I've checked modules.dep and basically (if I understand what 
it's telling me) it confirms what I thought.

epat needs paride
pcd needs paride
paride needs parport

The reason I'm using 'insmod' is because the Linux Parallel Port IDE 
HOWTO said that that's easiest - once you've got that sussed then you 
can think about recompiling the kernel to include all of the stuff 
you need if you really want - but I don't! I'll only want to access a 
parallel CD-ROM occasionally, and it doesn't have to be fast - it 
just has to work!

depmod -an > ~/tmp.tmp throws up no errors - it just creates a temp 
file that's identical to modules.dep - so nothing strange is going on 
there.

In answer to your kernel query, no. We're talking about a virgin 
Debian 2.1 kernel, with absolutely no shenanigans having taken place 
(I know - I was there all night, officer). I really haven't messed 
with the config on this machine. It doesn't have lp support on boot, 
but that's because I didn't select it when I installed. If I lsmod, I 
get all of the modules I expect, but not the ones I need, to whit (in 
order):

parport
paride
epat
pcd

I can insmod the first three no problem (lsmod tells me they're ther 
and happy) - it's pcd that throws up the error - and that's the one I 
need to get the parallel port IDE device /dev/pcd0 working. (the nub 
of the error is 'Device or resource busy - hint: this error can be 
caused by incorrect module parameters, including invalid IO or IRQ 
parameters'.)

The catch is, I don't know exactly how to phrase the parameters for pcd.

I've tried...

insmod pcd io=0x378, irq=7
insmod pcd 0378,7
insmod pcd 0378-037a

.. and many, many other combinations of irq= (many different 
numbers) io= (many different numbers, in hex, in decimal, however the 
sam-hell-I-feel-like) and in other combinations too. Isn't there a 
man page about this somewhere? (No.)

As you've read, it seems as if the parallel port isn't getting 
registered in /proc/ioports (Will's /proc/ioport has the lines 
'0378-037a : parport0' and '037b-037f : parport0' but mine doesn't!) 
In fact, I checked my Debian 2.2 box as well, and that doesn't 
mention parport0 in its /proc/ioports either.

Surely I need to make the parallel port known to the system somehow - 
presumably by passing the right parameters to parport, or perhaps to 
pcd... Or do I just need to get brutal and push text saying 
'0378-037a : parport0' into /proc/ioports? (I'm clutching at straws 
now - surely, as Will also suspects, correct use of insmod should do 
this for me...)

There *must* be some simple step I'm missing, or some definitive 
source of info on the correct way to pass parameters to parport, pcd, 
or whichever module will actually make the parallel port active. Any 
thoughts?

Cheers,

James
=====
>
>  > > ## Do I need to 'insmod parport_pc' as well, perhaps with parameters?
>>  > Presumably after insmod parport...
>>
>>  Might be it. What version of kernel are you running? (You probably said,
>  > but I can't find it :)
>
>Just in case.. I've kind of lost some of this thread I think... why are
>we using insmod? What does 'depmod -a' say? Any errors? What happens
>when you modprobe instead? I assume there hasn't been any kernel
>recompilation shenanigans going on behind closed doors???!
-- 
who: James Wallbank
org: Redundant Technology Initiative
tel: +44 114 2495522
fax: +44 114 2495533
eml: rti [at] lowtech.org
web: www.lowtech.org
loc: Access Space
      1 Sidney Street
      Sheffield
      S1 4RG
      UK
---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.