Very Computer

The problem I am having is that the printer port is not being detected.
I have made sure the interface isn't disabled in the bios, and read
through the printer how-to's, and don't see anything that could be
causing my problem.

When I run the print RedHat Print manager nothing is detected on lp0,
lp1, or lp2 (when you add a local printer it tries to detect the port).

After doing a little reading it seems that the actual port is lp0, etc..
is assigned based on the address range being used.  I haven't tried
forcing the printer port to a specific address in the Bios.  Other than
that I can't seem to find any hints.

Thanks in advance,

Brent Edwards

Was the parallel port detected during the boot sequence.  Maybe try
dmesg | grep par and see if a port was detected.  Mine returns
something like this

gateway:~> dmesg | grep par
parport0: PC-style at 0x378 [SPP,PS2]
lp0: using parport0 (polling).
gateway:~>

You might then want to check to see if the parallel ports are
writable by you.  Try ls -l /dev/lp* and see what happens.
Mine does this.

gateway:~> ls -l /dev/lp*
crw-rw----   1 root     daemon     6,   0 Apr 27  1995 /dev/lp0
crw-rw----   1 root     daemon     6,   1 Apr 27  1995 /dev/lp1
crw-rw----   1 root     daemon     6,   2 Apr 27  1995 /dev/lp2
gateway:~>

Then you might want to see if you can write to the printer (I assume that
is the device connected to the printer).

cat >> /dev/lp0
hello there
^l
^d

If that works, then you may have to figuire up how to set up the printer.

You may just have a problem with a cable that is not bi-directional or
something like that.

--
Best regards,

Stephen Jenuth

Quidquid latine dictum sit, altum viditur.

I've edited my conf.modules with the following lines:
alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=7

When I run dmesg | grep par I get:
parport0: PC-style at 0x378, irq 7 [SPP,PS2,EPP]
parport0: no IEEE-1284 device present.

When I try cat >> /dev/lp0, it returns a no such device error.  

If I boot to DOS, I can use dir >lpt1 and a directory will print so it
looks like the port is working.  What am I missing in Linux?
I'm running SUSE 6.2 with kernel 2.2.12 (2.2.10 had same problem) on
an Abit BP6 motherboard.  

When I type in lpq it says:
Warning: queue is not active (no server present).
  printing disabled                            

When I type in lpc start all, I get:
lpc: connect: Connection refused
        couldn't start daemon

Any ideas out there?  It look like Linux isn't find lpt1 on boot up
and thus not mapping /dev/lp0.  Printing worked for me about a month
ago and then all of a sudden stopped.  I've been struggling with this
problem for a long time and haven't been able to get anywhere.  Any
gurus out there have an answer?  Please send me e-mail or post here.

Thanks,
Alex

Lucid description of brain wracking and befuddling "missing /dev/lp*"
problem deleted.

Quote:>Any ideas out there?  It look like Linux isn't find lpt1 on boot up
>and thus not mapping /dev/lp0.  Printing worked for me about a month
>ago and then all of a sudden stopped.  I've been struggling with this
>problem for a long time and haven't been able to get anywhere.  Any
>gurus out there have an answer?  Please send me e-mail or post here.

>Thanks,
>Alex

Anybody brave and bold enough to solve it?
Thanks!
Adam
--
Adam J. Finkelstein

http://metalab.unc.edu/bees/adamf

I have compiled parallel printer support into the kernel.  I've tried
loading it up as a module also.  This problem occurs with version 2.2.10
and 2.2.12 of the kernel.  I don't know exactly when everything died but
it was during the time I was trying to resolve a problem with IPchains and
FTP timeouts.  I was all e*d about resolving that one until this
problem showed up.

Alex

Quote:

> Yes,

> I have compiled parallel printer support into the kernel.  I've tried
> loading it up as a module also.  This problem occurs with version 2.2.10
> and 2.2.12 of the kernel.

--

   Musique renaissance : http://listen.to/renmusic
   --> Several pages now available in English! <--

alias parport_lowlevel parport_pc

and reboot

Quote:> add the following to /etc/conf.modules

> alias parport_lowlevel parport_pc

> and reboot

Adam
--
Adam J. Finkelstein

http://metalab.unc.edu/bees/adamf

Quote:>I have the same problem. I upgraded my kernel to 2.2.13 and now at
>startup I get a message no devices for lp. I have  alias
>parport_lowlevel parport_pc in conf.modules but I still get this
>message. I have parallel port and parallel printer support builtin to
>the kernel. Any other suggestions?

after you made the kernel, (with parport and parport_pc hardware enabled) ,
did you do a "make modules" and then a "make module_install"(or
modules_install .. ) ? If not, then it won't make them and won't find them
either. It kind of sounds as if you've told the kernel you've got the
hardware but haven't made the modules for it to load. You can also compile
them right into the kernel but I'm not sure about what you've done.

            hope it works,

                  Mick

(oh--  you might want to re-resolve any symbolic links in /boot , like
/modules-info -> /modules-info-2.2.13, System.map -> System.map-2.2.13 and
of course vmlinuz -> vmlinuz-2.2.13. get System.map from /usr/src/linux,
modules-info from the one that's in /boot but rename it for the new kernel
and vmlinux from bzImage or whatever the output of the make kernel produced
in ./arch/i386/boot)(

request_module[parport_lowlevel]: Root fs not mounted
request_module[parport_probe]: Root fs not mounted
lp: driver loaded but no devices found

I am using Mandrake 6.0 with kernel 2.2.13. I have EPP enabled in the
BIOS. Any other suggestions? It feels like I've tried everything.

Quote:> One that worked for me a while ago:
> go to BIOS at startup and select EPP parallel port type. I had ECP and
it
> doesn't seem to work for kernel 2.2.10, at least. Also make sure you
have a
> symlink : /dev/lp -> /dev/lp0

Quote:> after you made the kernel, (with parport and parport_pc hardware
enabled) ,
> did you do a "make modules" and then a "make module_install"(or
> modules_install .. ) ? If not, then it won't make them and won't find
them
> either. It kind of sounds as if you've told the kernel you've got the
> hardware but haven't made the modules for it to load. You can also
compile
> them right into the kernel but I'm not sure about what you've done.

>             hope it works,

>                   Mick

> (oh--  you might want to re-resolve any symbolic links in /boot , like
> /modules-info -> /modules-info-2.2.13, System.map -> System.map-2.2.13
and
> of course vmlinuz -> vmlinuz-2.2.13. get System.map from
/usr/src/linux,
> modules-info from the one that's in /boot but rename it for the new
kernel
> and vmlinux from bzImage or whatever the output of the make kernel
produced
> in ./arch/i386/boot)(