[vox-tech] parport troubles

Peter Jay Salzman p at dirac.org
Sun Jan 23 14:54:09 PST 2005


Hi all,

Kernel 2.6.9 has been giving me parport woes.  My printer works on all my
kernels, except 2.6.9.  Under every kernel *except* for 2.6.9:

   * IRQ7 is assigned to parport
   * The printer works.

On the 2.6.9 kernel:

   * parport is not assigned an IRQ.
   * The printer doesn't work (duh).

Here's a comparison of kernel config options related to parport:

2.6.9 config options (where           2.6.7 config options (where
parport is broken)                    parport works)
=============================         =================================
CONFIG_PARPORT=y                      CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y                   CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y              CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set    # CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y              CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y           CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PARPORT_OTHER=y                CONFIG_PARPORT_OTHER=y
CONFIG_PARPORT_1284=y                 CONFIG_PARPORT_1284=y

   
On 2.6.9, dmesg has some mysterious messages:

   pnp: the driver 'parport_pc' has been registered
   pnp: match found with the PnP device '00:0e' and the driver 'parport_pc'
   parport: PnPBIOS parport detected.
   pnp: Device 00:0e disabled.

which explains a lot without really explaining anything.  I have no idea why
the device is disabled only under 2.6.9.  The only thing I knew what to do
was to compare config options related to pnp, since that is what presumably
disabled the parport device:


2.6.7 (works)                          2.6.9 (doesn't work)
=============                          ====================
# Plug and Play support                # Plug and Play support
#                                      #
CONFIG_PNP=y                           CONFIG_PNP=y
CONFIG_PNP_DEBUG=y                     CONFIG_PNP_DEBUG=y
                                       
# Protocols                            # Protocols
#                                      #
CONFIG_ISAPNP=y                        CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y                       CONFIG_PNPBIOS=y
# CONFIG_PNPBIOS_PROC_FS is not set    # CONFIG_PNPBIOS_PROC_FS is not set


I'm stumped.  Has anybody seen this type of problem before?

Thanks,
Pete


More information about the vox-tech mailing list