[PARPORT] Why is there no pda?

From: D. Olson (scapegoats@sympatico.ca)
Date: Mon Aug 05 2002 - 23:12:08 EDT

  • Next message: Frank Mikkelsen (QIS): "RE: [PARPORT] Why is there no pda?"

    I did this:

    rmmod lp
    modprobe paride
    modprobe epat
    modprobe pd

    The output of dmesg is this:

    pd: pd version 1.05, major 45, cluster 64, nice 0
    epat_init_protopda: 0x378 is parport0
    pda: epat: port 0x378, mode 0, ccr 0, test=(0,0,0)
    pda: epat: port 0x378, mode 1, ccr 0, test=(0,0,0)
    pda: epat: port 0x378, mode 2, ccr 0, test=(0,0,0)
    pda: epat: port 0x378, mode 3, ccr 0, test=(0,0,0)
    pda: epat: port 0x378, mode 4, ccr 0, test=(0,0,0)
    pda: epat: port 0x378, mode 5, ccr 0, test=(0,0,0)
    pda: Sharing parport0 at 0x378
    pda: epat 1.02, Shuttle EPAT chip c7 at 0x378, mode 5 (EPP-32), delay 1
    pda: LEXAR ATA FLAS, master, 16064 blocks [7M], (251/2/32), removable media
     pda: p1
    devfs_mk_dir(pd/disc0): using old entry in dir: daeae840 "pd"
    devfs_register(disc): could not append to parent, err: -17

    /dev has no pda, pda1, or any other pd* files. It does have a folder, pd/,
    and in there is disc0/, and in there is disc and part1.

    I tried running fdisk on disc in there, and it works... So I am wondering,
    why is there no pda1 file in /dev?

    Thanks! 

    -- 
D. Olson

    WinXP - the best thing since induced vomitting.

    --  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 : Mon Aug 05 2002 - 23:21:23 EDT