Re: lpt0 always busy
> > > > 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
> > > > 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
> > 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
> > 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
> > 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
> > 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]"
lpt0 always busy
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Eterm
> > > hi, > > when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with > > Eterm ... transparancy still works but "--tint" option does not > > produce usable results: my Eterm is alway blue - no matter which > > color i specify :( > > > i did several cvsups and rebuilds of the base system and the ports > > but with no luck so far > > > anybody else seeing this behaviour? anybody using eterm with --trans > > --tint--shape successfully on 5.4 / -STABLE ? > > Had this happen several months ago (February). Try recompiling Eterm > with "-DWITH_MMX". today i tried -DWITH_MMX on my box with the eterm prob - et voila :) ... everything works fine now :) open question: why is this option necessary at all now (after updating from 5.2.1)? before this update eterm worked on this box as expected ... wired ... thx regards, stan -- "Perfection is achieved, not when there is nothing left to add, but when there is nothing left to take away." --- Antoine de St. Exupery, Wind, Sand, and Stars, 1939 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Eterm
hi, when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with Eterm ... transparancy still works but "--tint" option does not produce usable results: my Eterm is alway blue - no matter which color i specify :( i did several cvsups and rebuilds of the base system and the ports but with no luck so far anybody else seeing this behaviour? anybody using eterm with --trans --tint --shape successfully on 5.4 / -STABLE ? 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]"
