Re: lpt0 always busy

2005-09-27 Thread stanley jobson
> 
> > > You could try printing to /dev/lpt0.ctl since that will ignore
> > > BUSY for the  open.
> >
> > one can print using lpt0.ctl? - thx 4 the hint - i'll check this ...
> 
> Well, I'm pretty sure you can.
> AFAIK the only difference is that lpt0.ctl ignores BUSY on open so
> lptcontrol  can use it.
> 

unfort. qemu is not able to open lpt0.ctl too (no perm prob) but i will
do some more testing in this direction ...

thx
regards,
stan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-27 Thread stanley jobson
> > 
> > its a canon lbp 460 - ugly gdi printer :)
> 
> Aha, that explains wy it will not work. see this:
> http://linuxprinting.org/show_printer.cgi?recnum=Canon-LBP-460
> 
> the printer can print ascii text at all, it is a raster-only win* gdi
> printer. It is the driver who does all the work.

i know that this printer will never work with fbsd or even linux so i
hoped i could setup a qemu with win98 and just passing lpt0 throu ...
but unfort. this does not work :(

what i need is a possibility to give qemu/vmware access to lpt0 without
any checking done by fbsd 

thx,
regards,
stan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-27 Thread Torfinn Ingolfsen
On Tue, 27 Sep 2005 10:26:36 +0200
stanley jobson <[EMAIL PROTECTED]> wrote:

> > 
> > It seriously looks like the printer, cable or port are broken, or
> > the printer  is very very special..
> > 
> > What sort of printer is it?
> 
> its a canon lbp 460 - ugly gdi printer :)

Aha, that explains wy it will not work. see this:
http://linuxprinting.org/show_printer.cgi?recnum=Canon-LBP-460

the printer can print ascii text at all, it is a raster-only win* gdi
printer. It is the driver who does all the work.

Always, always check LinuxPrinting.org before starting with an unknown
printer.
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-27 Thread Daniel O'Connor
On Tuesday 27 September 2005 17:56, stanley jobson wrote:
> > It seriously looks like the printer, cable or port are broken, or the
> > printer  is very very special..
> >
> > What sort of printer is it?
>
> its a canon lbp 460 - ugly gdi printer :)

Hmm, well lots of printers these days are raster only..
I'd  recommend buying an Epson since they are usually more functional than 
Canon in !Win32.

> > You could try printing to /dev/lpt0.ctl since that will ignore BUSY
> > for the  open.
>
> one can print using lpt0.ctl? - thx 4 the hint - i'll check this ...

Well, I'm pretty sure you can.
AFAIK the only difference is that lpt0.ctl ignores BUSY on open so lptcontrol 
can use it.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpHOteqYASe8.pgp
Description: PGP signature


Re: lpt0 always busy

2005-09-27 Thread stanley jobson
> 
> It seriously looks like the printer, cable or port are broken, or the
> printer  is very very special..
> 
> What sort of printer is it?

its a canon lbp 460 - ugly gdi printer :)

> 
> You could try printing to /dev/lpt0.ctl since that will ignore BUSY
> for the  open.

one can print using lpt0.ctl? - thx 4 the hint - i'll check this ...

thx
regards,
stan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-25 Thread Daniel O'Connor
On Monday 26 September 2005 01:42, Stanley Jobson wrote:
> > > i have a separate box running win98. from this box i am able to use the
> > > printer with the orig vendor driver without any problem ...
> >
> > Hmm, well it's possible the serial port is broken..
>
> maybe ...

Err parallel port :)

> > Have you tried using lptcontrol to put it into simple mode?
>
> [EMAIL PROTECTED] seb $ lptcontrol -s -d /dev/lpt0.ctl
> [EMAIL PROTECTED] seb $
>
> > What do you see in dmesg?
>
> lpt0: switched to interrupt-driven standard mode
>
> looks that everything is ok - not ?
> but open(/dev/lpt0) still complains about "device busy" ...

It seriously looks like the printer, cable or port are broken, or the printer 
is very very special..

What sort of printer is it?

You could try printing to /dev/lpt0.ctl since that will ignore BUSY for the 
open.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpbzbQ9ql2e8.pgp
Description: PGP signature


Re: lpt0 always busy

2005-09-25 Thread Stanley Jobson
> > i have a separate box running win98. from this box i am able to use the
> > printer with the orig vendor driver without any problem ...
> 
> Hmm, well it's possible the serial port is broken..

maybe ...

> 
> > > Are you sure nothing else is using the port? (lpd, cups, etc)
> >
> > i think so: lpd is not running and lsof | grep lpt doesnt show anything
> > either : (
> 
> fstat /dev/lpt0
> and
> fstat /dev/lpt0.ctl
> 
> ?

[EMAIL PROTECTED] seb $ fstat /dev/lpt0.ctl 
USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W NAME
[EMAIL PROTECTED] seb $ fstat /dev/lpt0
USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W NAME
[EMAIL PROTECTED] seb $ 

> 
> > so i guess there could be a prob with the ready/status checking
> > procedure
> 
> This consists of checking the BUSY pin on the port..
> Parallel ports are (sans ECP/EPP extras) very very simple.
> 
> Have you tried using lptcontrol to put it into simple mode?

[EMAIL PROTECTED] seb $ lptcontrol -s -d /dev/lpt0.ctl 
[EMAIL PROTECTED] seb $

> What do you see in dmesg?

lpt0: switched to interrupt-driven standard mode

looks that everything is ok - not ?
but open(/dev/lpt0) still complains about "device busy" ...

thx
regards,
stan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-25 Thread Daniel O'Connor
On Sunday 25 September 2005 23:03, stanley jobson wrote:
> i have a separate box running win98. from this box i am able to use the
> printer with the orig vendor driver without any problem ...

Hmm, well it's possible the serial port is broken..

> > Are you sure nothing else is using the port? (lpd, cups, etc)
>
> i think so: lpd is not running and lsof | grep lpt doesnt show anything
> either : (

fstat /dev/lpt0
and
fstat /dev/lpt0.ctl

?

> so i guess there could be a prob with the ready/status checking
> procedure

This consists of checking the BUSY pin on the port..
Parallel ports are (sans ECP/EPP extras) very very simple.

Have you tried using lptcontrol to put it into simple mode?
What do you see in dmesg?

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpFofGqksr7d.pgp
Description: PGP signature


Re: lpt0 always busy

2005-09-25 Thread stanley jobson

> > so it seems that fbsd expects some kind of status reply from the
> > printer - correct?
> >
> > if so: how could i by-pass this? (cause my ugly gdi printer is
> > probably not able to answer correctly) i just wonna have access to
> > my parallel port ...
> 
> It expects that your printer will toggle the BUSY line as it should..
> I don't believe you'd be able to print on any OS if this was broken.

i have a separate box running win98. from this box i am able to use the
printer with the orig vendor driver without any problem ...

> 
> Are you sure nothing else is using the port? (lpd, cups, etc)
> 

i think so: lpd is not running and lsof | grep lpt doesnt show anything
either : (

so i guess there could be a prob with the ready/status checking
procedure

any other ideas? any idea how to by pass this check so other programs
(like qemu) could simple use the port?

maybe it s necessary to hack the lpt driver - but because i am not a
kernel hacker (maybe a good c hacker :)) - some help with this would be
really nice ...

thx
regards,
stan
 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-25 Thread Daniel O'Connor
On Sunday 25 September 2005 17:21, stanley jobson wrote:
> > Usually, if you get "device busy," it means that the printer is simply
> > not on or connected properly. Check your parallel cable.
>
> unfort. my printer is connected properly and it is on while simply
> trying to open it with open(/dev/lpt0) - lptest > /dev/lpt0 fails too
> ...
>
> so it seems that fbsd expects some kind of status reply from the printer
> - correct?
>
> if so: how could i by-pass this? (cause my ugly gdi printer is probably
> not able to answer correctly) i just wonna have access to my parallel
> port ...

It expects that your printer will toggle the BUSY line as it should..
I don't believe you'd be able to print on any OS if this was broken.

Are you sure nothing else is using the port? (lpd, cups, etc)


-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgppkJbk5bPGm.pgp
Description: PGP signature


Re: lpt0 always busy

2005-09-25 Thread stanley jobson
> > hi,
> > i am now trying for weeks to get my lpt0 working without any success
> > :(
> > 
> > i always get "device busy" (running lptcontrol, lptest,
> > open(/dev/lpt0)).  i found a lot of questions about this via google
> > and some hints too (e.g. excluding device ppi from kernel) but all
> > this didnt help :(
> > 
> > i should mention that my printer connected to lpt0 is a funny gdi
> > printer which only works under win98. so my idea was to use qemu to
> > run a emulated win98 to get my printer working - but therefore qemu
> > needs to be able to open /dev/lpt0 ...
> > 
> > finally i wrote a simple c prog which just calls open(/dev/lpt0) but
> > it also always fails with device busy :(
> > 
> > what are the requirements to successfully open lpt0 port (apart from
> > having connected a printer to it) ?
> > 
> > does fbsd expects a response from the printer (e.g. ready status)?
> > maybe my printer is not able to do this ... if so: what are possible
> > workarounds? could i convice the kernel that lpt0 is ready?
> > 
> > thx
> > regards,
> > stan
> > 
> > ps: i am running fbsd 5.4
> > 
> Usually, if you get "device busy," it means that the printer is simply
> not on or connected properly. Check your parallel cable.

unfort. my printer is connected properly and it is on while simply
trying to open it with open(/dev/lpt0) - lptest > /dev/lpt0 fails too
...

so it seems that fbsd expects some kind of status reply from the printer
- correct?
if so: how could i by-pass this? (cause my ugly gdi printer is probably
not able to answer correctly) i just wonna have access to my parallel
port ...

thx
regards,
stan


 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: lpt0 always busy

2005-09-24 Thread Dan Ponte
On Sat, Sep 24, 2005 at 06:09:09PM +0200, stanley jobson <[EMAIL PROTECTED]> 
was witnessed plotting the following conspiracy:
> hi,
> i am now trying for weeks to get my lpt0 working without any success :(
> 
> i always get "device busy" (running lptcontrol, lptest,
> open(/dev/lpt0)).  i found a lot of questions about this via google and
> some hints too (e.g. excluding device ppi from kernel) but all this
> didnt help :(
> 
> i should mention that my printer connected to lpt0 is a funny gdi
> printer which only works under win98. so my idea was to use qemu to run
> a emulated win98 to get my printer working - but therefore qemu needs to
> be able to open /dev/lpt0 ...
> 
> finally i wrote a simple c prog which just calls open(/dev/lpt0) but it
> also always fails with device busy :(
> 
> what are the requirements to successfully open lpt0 port (apart from
> having connected a printer to it) ?
> 
> does fbsd expects a response from the printer (e.g. ready status)? maybe
> my printer is not able to do this ... if so: what are possible
> workarounds? could i convice the kernel that lpt0 is ready?
> 
> thx
> regards,
> stan
> 
> ps: i am running fbsd 5.4
> 
Usually, if you get "device busy," it means that the printer is simply
not on or connected properly. Check your parallel cable.
-Dan
-- 
Dan Ponte
http://www.theamigan.net/
A great many people think they are thinking when they are merely
rearranging their prejudices.
-- William James
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"