Re: [Sheflug] Parallel IDE CD-ROM frustrations

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

Hi All, (especially Will)

Now look. Activating the parallel port isn't some kind of weird, 
unusual activity that Linux users don't usually do. It's a regular, 
normal sort of thing. Are we just thinking too deeply about the 
situation?

At the moment I'm loading every module that I reckon's relevant to 
the parallel port via insmod...

So I'm typing:

insmod parport
insmod paride
insmod epat                # Returns 'paride: epat registered as protocol 0'
insmod pcd drive0=0x378,0  # This fails as I described!

And after I've done all that parport0 still doesn't get mentioned in 
/proc/ioports, and neither /proc/sys/dev/parallel/* nor 
/proc/sys/dev/parallel exist.

## Do I need to pass some parameters to 'insmod parport' in order to 
establish parport0? If so, what parameters? (I guess that 0x378 will 
be there somewhere, and probably '0' but what exactly is the format 
of the line?)

## Do I need to 'insmod parport_pc' as well, perhaps with parameters? 
Presumably after insmod parport...

Surely... surely (!) you don't need to push files into /proc. (Though 
the message 'parport0: detected irq 7; use procfs to enable 
interrupt-driven operation' suggests otherwise.)

But *surely* it must be possible to activate the parallel port with 
'insmod' (which presumably will create the appropriate flag files in 
/proc)???

Calling this thread 'Parallel IDE CD-ROM frustrations' was kind of prescient!

Cheers,

James
=====

What came before...

James: (after 'insmod pcd drive0=0x378,0' failed)

>  > Then that pesky error message comes up again! Do I have to pass some
>>  parameters to the parport module? When the error message says 'use
>>  procfs to enable interrupt-driven operation', does that literally
>>  mean getting a script to splice some text (I'd guess something along
>  > the lines of '0378-037a : parport0') into /proc/ioports? Or is there
>  > something else that I have to do?

Will: (in response)

>More likely cat something to /proc/sys/dev/parport/parport0/modes.
>Dunno what.
>
>But anyway, to load the modules for parport0 then check /proc/ioports to
>see if parport is listed then. It should be listed along with an io port
>address.


That 'pesky error message':

>Using /lib/modules/2.2.17/misc/pcd.o
>pcd: pcd version 1.07, major 46, nice 0
>parport0: detected irq 7; use procfs to enable interrupt-driven operation
>pcd0: Adapter not found
>pcd: No CD-ROM drive found
>Using /lib/modules/2.2.17/misc/pcd.o: init_module: device or resource busy
>Hint: this error may be caused by incorrect module parameters,
>including invalid IO or IRQ parameters
-- 
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.