ECP means, both irq and dma access. maybe you don't have enough dmas on the machine 
for it(because its old) or the irq is conflicting with the sound blaster or modem (or 
ethernet, though its rare). maybe you
didn't compile the parport correctly at the kernel, plus it has been known to have 
many bugs in the past.
try to use the commercial ones (redhat, etc). anyway, do:
dmesg |grep parport and see what is the nature of the error, or dmesg|grep irq7 or 
something similar.
in any case, go over the entire dmesg and search for other problems, maybe its 
something else, like a conflicting mode or something:
do dmesg|more, and go over it line by line.
if you find an error, copy past it to www.dejanews.com, now groups.google.com and 
search old postings
about it, and then return here more edjucated and with more details about the problem.
enjoy! ;)

p.s: if i remember correctly from the past, s3 video cards conflicts sometimes with 
memory address of the coms and maybe LPTs.

* - * - *
Tzahi Fadida
[EMAIL PROTECTED]
Fax (+1 Outside the US) 240-597-3213
* - * - * - * - * - *


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of 
guy keren
Sent: Wednesday, January 09, 2002 2:46 PM
To: Efraim Yawitz
Cc: linux-il list
Subject: Re: parport



On Wed, 9 Jan 2002, Efraim Yawitz wrote:

> The parallel port doesn't seem to work, meaning that if I send something
> to the printer, nothing happens at all.However, the kernel seems to
> detect it, as shown in the output of dmesg:
>
> parport0: PC-style at 0x378, irq 7 [SPP,ECP,ECPPS2]
> lp0: using parport0 (interrupt-driven).

did you verify these irq and IO address in the BIOS? did you also verify
how your parallel port is configured? linux, as i understand, uses 'ECP'
(don't ask me what that is - i've no idea). as i saw in some bioses, this
could be configured to one of 4 different settings - check how its defined
in yours.

> When I try, as root to do tunelp /dev/lp0, I get:
>
> /dev/lp0 Device or resource busy

most likely because 'lpd' is running and holding the define busy. try to
kill lpd and check again, but not before you checked the bios settings
with regards to the message above.

> I have Windows NT 4.0 on the same machine, and it doesn't seem to detect
> the parport at all.

could be the same settings problem. or a hardware problem.

--
guy

"For world domination - press 1,
 or dial 0, and please hold, for the creator." -- nob o. dy


=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]


================================================================To unsubscribe, send 
mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to