Re: [PARPORT] probs printing w/ 2.2.18

From: Harry Mangalam (mangalam@home.com)
Date: Mon Feb 19 2001 - 19:07:29 EST

  • Next message: Harry Mangalam: "Re: [PARPORT] probs printing w/ 2.2.18"

    Thanks for the rapid response, Tim,

    I had done this but forgotten what exactly the result was. No problem in doing so - I have both kernel trees still on-disk.

    The result is that NEITHER now results in printing real print jobs. The 2.2.14 kernel doesn't allow the autoprobe to work either. Despite the lack of a correct autoprobe, things DO work the same
    otherwise - print jobs result in a piece of paper being elected that says "No spool file found".

    It Definitely was working with 2.2.14, so I may have buggered up something else in the transition.. However, it is still the case that with the parport modules UNLOADED, the sppol files don't go
    anywhere, so it seems to be related to their loadedness

    I also just noticed that in /var/log/messages, I'm seeing (running 2.2.18):

    Feb 19 15:57:38 cx408397-a modprobe: can't locate module parport_lowlevel
    Feb 19 15:57:38 cx408397-a kernel: lp: no devices found
    Feb 19 15:57:38 cx408397-a insmod: /lib/modules/2.2.18/misc/lp.o: init_module: Device or resource busy

    which seems to prevent it from loading the rest of the modules automatically..

    This despite the fact that my /etc/conf.modules says:

    alias scsi_hostadapter aic7xxx
    alias eth0 eepro100
    alias scsi_hostadapter1 BusLogic
    alias eth1 smc-ultra
    #alias /dev/printers lp # only for devfs?
    #alias /dev/lp* lp # only for devfs?
    alias parport_lowlevel parport_pc # missing in Red Hat 6.0-6.1

    I did notice that I had loaded my sound modules before the parport modules, but unloading everything and then loading the parport modules didn;t correct anything.

    hjm

    Tim Waugh wrote:
    >
    > On Mon, Feb 19, 2001 at 01:51:31PM -0800, Harry Mangalam wrote:
    >
    > > This sounds a bit like the problem that Eythan Weg had last year, but
    > > in his case it looked like his cable was just buggered. I have
    > > tested my cable on other machines and it's communicating on this
    > > machine as well (and was printing fine under 2.2.14)..
    >
    > Is installing 2.2.14 and quickly testing to see if that does indeed
    > make the problem go away an option? If so, I would suggestion trying
    > to find out exactly which kernel revision it stops working at.
    >
    > Tim.
    > */
    >
    > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    > Part 1.2Type: application/pgp-signature 

    -- 
Cheers,
Harry

    Harry J Mangalam -- (949) 856 2847 (v&f) -- hjm@ncgr.org || mangalam@home.com

    --  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 Feb 19 2001 - 19:09:06 EST