Re: [PARPORT] Backpack CDRW Problems

From: Duane Drake (duane.drake@e-ci.com)
Date: Tue Jun 11 2002 - 16:17:10 EDT

  • Next message: Al Crowley: "Re: [PARPORT] Backpack CDRW Problems"

    I would agree, but that is not what is happening.

    I get the same results with modprobe as with insmod.

    The bpck6 module is not being acknowledged at all:

    6. I get the following results:
    insmod paride
    Using /lib/modules/2.4.18/kernel/drivers/block/paride/paride.o
    insmod bpck6
    Using /lib/modules/2.4.18/kernel/drivers/block/paride/bpck6.o
    insmod pg
    Using /lib/modules/2.4.18/kernel/drivers/block/paride/pg.o
    /lib/modules/2.4.18/kernel/drivers/block/paride/pg.o: init_module:
    Operation not permitted
    Hint: insmod errors can be caused by incorrect module parameters,
    including invalid IO or IRQ parameters

    7. Here is what dmesg says: (Strangely, There is no mention at all of
    the bpck6 module)
    paride: version 1.06 installed (parport)
    pg: pg version 1.02, major 97
    pg0: Autoprobe failed
    pg: No ATAPI device detected

    Duane

    Al Crowley wrote:

    >Upon boot, you should simply be able to issue the following commands:
    >
    >modprobe bpck6
    >modprobe pcd (for read-only access or modprobe pg for writing)
    >
    >
    >-AL
    >
    >
    >At 03:44 PM 6/11/2002 -0400, you wrote:
    >
    >
    >>Thanks for your quick response.
    >>
    >>My serial number is: 21602843
    >>I am running RH 7.3
    >>
    >>Duane
    >>
    >>
    >>
    >>

    -- To unsubscribe, send mail to: linux-parport-request@torque.net --
    -- with the single word "unsubscribe" in the body of the message. --

    This archive was generated by hypermail 2b29 : Tue Jun 11 2002 - 16:21:24 EDT