Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Parallelport support broken?

  1. #11
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    Quote Originally Posted by mse1 View Post
    Yes, but with a single port only.
    Do you actually need the other ports though? You can specify multiple addresses (to match the hardware) if need be. See the parport_pc kernel reference I linked to earlier.

  2. #12
    Join Date
    Dec 2009
    Posts
    48

    Default Re: Parallelport support broken?

    Quote Originally Posted by deano_ferrari View Post
    Do you actually need the other ports though?
    Yes.
    You can specify multiple addresses (to match the hardware) if need be. See the parport_pc kernel reference I linked to earlier.
    Yup, "options parport_pc io=0x378,0xd050,0xd030 dma=none,none,none irq=none,none,none" seems to work, thank you very much for the help!

  3. #13
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    Quote Originally Posted by mse1 View Post
    Yes.

    Yup, "options parport_pc io=0x378,0xd050,0xd030 dma=none,none,none irq=none,none,none" seems to work, thank you very much for the help!
    Well done! Glad to have been of help with this.

  4. #14
    Join Date
    Dec 2009
    Posts
    48

    Default Re: Parallelport support broken?

    Interestingly "options parport_pc io=0x378,0xd050,0xd030 dma=none,none,none irq=7,18,10" works too, "dmesg|grep parport" lists
    Code:
    [   17.250204] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [   17.333784] parport1: PC-style at 0xd050, irq 18 [PCSPP,TRISTATE,EPP]
    [   17.416860] parport2: PC-style at 0xd030, irq 10 [PCSPP,TRISTATE,EPP]
    [   17.424652] parport2: Printer, Hewlett-Packard HP LaserJet 6P
    [  105.840722] lp0: using parport0 (interrupt-driven).
    [  105.840745] lp1: using parport1 (interrupt-driven).
    [  105.840766] lp2: using parport2 (interrupt-driven).
    so maybe the problem is not interrupts but "using FIFO [PCSPP,TRISTATE,COMPAT,ECP]". Now the question is how to switch off FIFO/COMPAT so one doesn't need to fumble with IRQ's?

  5. #15
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    Quote Originally Posted by mse1 View Post
    Interestingly "options parport_pc io=0x378,0xd050,0xd030 dma=none,none,none irq=7,18,10" works too, "dmesg|grep parport" lists
    Code:
    [   17.250204] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [   17.333784] parport1: PC-style at 0xd050, irq 18 [PCSPP,TRISTATE,EPP]
    [   17.416860] parport2: PC-style at 0xd030, irq 10 [PCSPP,TRISTATE,EPP]
    [   17.424652] parport2: Printer, Hewlett-Packard HP LaserJet 6P
    [  105.840722] lp0: using parport0 (interrupt-driven).
    [  105.840745] lp1: using parport1 (interrupt-driven).
    [  105.840766] lp2: using parport2 (interrupt-driven).
    so maybe the problem is not interrupts but "using FIFO [PCSPP,TRISTATE,COMPAT,ECP]". Now the question is how to switch off FIFO/COMPAT so one doesn't need to fumble with IRQ's?
    Yes, that is good to know that polling and IRQ both work here. I could be wrong, but explicitly setting using dma=none prevents FIFO buffer being used perhaps?

  6. #16
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    For built-in devices as least, it may be possible to configure in the BIOS.

  7. #17
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    This bug discusses FIFO configuration/behaviour across a few distros and may be of interest to you

    https://bugs.launchpad.net/ubuntu/+s...752/comments/7

    The kernel configuration parameter CONFIG_PARPORT_PC_FIFO= is relevant here. Most parport builds have it enabled, but RH had it disabled according to the bug report.

  8. #18
    Join Date
    Dec 2009
    Posts
    48

    Default Re: Parallelport support broken?

    Quote Originally Posted by deano_ferrari View Post
    I could be wrong, but explicitly setting using dma=none prevents FIFO buffer being used perhaps?
    There is already "options parport_pc dma=none" in "/etc/modprobe.d/00-system.conf" (openSUSE default).
    "options parport_pc io=0x378,0xd050,0xd030 dma=none,none,none" in "/etc/modprobe.d/99-local.conf" reports as:
    Code:
    [    6.502001] parport0: PC-style at 0x378, irq 1 [PCSPP,TRISTATE]
    [    6.502006] genirq: Flags mismatch irq 1. 00000000 (parport0) vs. 00000080 (i8042)
    [    6.502817] parport0: irq 1 in use, resorting to polled operation
    [    6.585474] parport1: PC-style at 0xd050 [PCSPP,TRISTATE,EPP]
    [    6.668475] parport2: PC-style at 0xd030 [PCSPP,TRISTATE,EPP]
    [  163.712859] lp0: using parport0 (polling).
    [  163.712883] lp1: using parport1 (polling).
    [  163.712905] lp2: using parport2 (polling).

  9. #19
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: Parallelport support broken?

    Quote Originally Posted by mse1 View Post
    There is already "options parport_pc dma=none" in "/etc/modprobe.d/00-system.conf" (openSUSE default).
    Right, then maybe the act of specifying single addresses (io=...) perhaps?

  10. #20
    Join Date
    Dec 2009
    Posts
    48

    Default Re: Parallelport support broken?

    Quote Originally Posted by deano_ferrari View Post
    The kernel configuration parameter CONFIG_PARPORT_PC_FIFO= is relevant here. Most parport builds have it enabled, but RH had it disabled according to the bug report.
    It seems that FIFO handling of parport_pc is buggy. I don't know if parport_pc is still maintained, there is no reaction on the bug reports up to now.
    https://bugzilla.opensuse.org/show_bug.cgi?id=1016204
    https://bugzilla.kernel.org/show_bug.cgi?id=190541

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •