mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: nick@coelacanth.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13 pcd problems?
Date: Sat, 10 Nov 2001 01:10:25 +0100 (MET)	[thread overview]
Message-ID: <200111100010.BAA27674@harpo.it.uu.se> (raw)

On 09 Nov 2001 13:38:05 -0500, Nick Papadonis wrote:
>Is anyone having similar problems with pcd using Kernel v2.4.13?  I'm trying
>to get my BackPack 6 working.  I don't think I should be passing any
>other parameters to pcd.
>
>Any insight much appreciated.
>
>- Nick
>
>$ 540 /home/nick -> modprobe paride
>$ 541 /home/nick -> modprobe bpck6
>$ 542 /home/nick -> modprobe pcd
>/lib/modules/2.4.13/kernel/drivers/block/paride/pcd.o: init_module: Operation not permitted
>Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
>/lib/modules/2.4.13/kernel/drivers/block/paride/pcd.o: insmod /lib/modules/2.4.13/kernel/drivers/block/paride/pcd.o failed
>/lib/modules/2.4.13/kernel/drivers/block/paride/pcd.o: insmod pcd failed

A dmesg log would have been appropriate here.
Two things to check/test:
1. Configure the parport as EPP or PS2 in the BIOS, not ECP.
2. Tell Linux the IO address _and_ IRQ of your parport.

I have the following in /etc/modules.conf in an old box, and
its Freecom parport CD-ROM works fine in 2.4.current.

alias parport_serial off
alias parport_lowlevel off
above parport parport_pc
options parport_pc io=0x378 irq=7
above paride frpw
alias block-major-46 pcd

             reply	other threads:[~2001-11-10  0:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-10  0:10 Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-09 18:38 Nick Papadonis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200111100010.BAA27674@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@coelacanth.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®