Printer does not work with newer kernel versions

[Kam Leo]

On Thu, 3 Feb 2005 08:43:02 +0100 (CET), Sven Borkert <sven at borkert.net> wrote:
> Hi,
> 
> I'm using Fedora Core 3 on a Compaq Deskpro EN and a HP Laserjet 4000.
> With kernel 2.6.9-1.667 printing works fine. As I updated to
> 2.6.10-1.741_FC3, system-config-printer tells me that the printer is
> always disconnected. Updating to 2.6.10-1.760_FC3 still did not fix the
> problem. When i boot 2.6.9-1.667 again, printing works without problems
> again. So, atm I'm stuck on the old kernel version because I need the
> printer.
> 
> dmesg with the newer kernel says:
> 
> parport: PnPBIOS parport detected.
> parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
> parport0: faking semi-colon
> parport0: Printer, Hewlett-Packard HP LaserJet 4000 Series
> Trying to free free DMA3
> pnp: Device 00:06 disabled.
> ieee1394: Initialized config rom entry `ip1394'
> ip_tables: (C) 2000-2002 Netfilter core team
> ip_tables: (C) 2000-2002 Netfilter core team
> e100: eth0: e100_watchdog: link up, 100Mbps, half-duplex
> i2c /dev entries driver
> pnp: Device 00:06 activated.
> parport: PnPBIOS parport detected.
> pnp: Device 00:06 disabled.
> lp: driver loaded but no devices found
> 
> With the older kernel "lp" reports the printer correctly.
> 
> Hope anyone can help me.
> 
> Sven Borkert
> 

The thread "printer stopped working - in 2.6.10 kernels" in the
January list archives suggested the following work-around:

  For the record, adding

  alias parport_lowlevel parport_pc
  options parport_pc io=0x378,0x278 irq=7,auto

  to the end of /etc/modprobe.conf fixed the problem (as suggested at
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145151).


Change the options line to fit your particular hardware configuration.
If you need more information than is provided in bugzilla use Google
to find the linux-parport mailing list (July 2000, 2.2 kernel era)
thread about the parallel port driver not being able to properly
identify some ports and the necessity to add the modprobe.conf data.

Hope that helps.

--Kam