Re: Trouble with lpr and Brother wireless printer
On Fri, 5 Aug 2022 00:05:29 -0700 Ryan Freeman wrote: > Did you happen to try CUPS with the brlaser package installed? > I have a Brother HL-L2390DW, and once I found brlaser it just worked. You, sir, are a saint. It works!! I can't believe I didn't manage to find that package (((facepalm))). So I'll amend my report: Brother HL-L2350DW works fine with cups and brlaser Thanks all for the kind help. - Ben
Re: Trouble with lpr and Brother wireless printer
I'm sorry the filter didn't work for you. I'm not using OpenBSD as a desktop right now, but I abused my router a bit to test, and can confirm that with an HL-L2370DW, the following printcap entry works, along with the filter. I know you've basically already moved on, but if you feel like giving it a try again, here's at least something. I can't remember if I mentioned it, but the filter does require ghostscript to be installed. I'm not sure exactly how you're trying to print or from what, but this printed a standard PDF file using `lpr file.pdf' without issue. /etc/printcap: lp|HLL2370DW:\ :lp=:rm=printer.localdomain:rp=BINARY_P1:sd=/var/spool/output/lpd:\ :lf=/var/log/lpd-errs:of=/usr/bin/pclfilter /usr/bin/pclfilter: #!/bin/sh gs -sPAPERSIZE=letter -sDEVICE=pxlmono -sOutputFile=- -dBATCH -dNOPAUSE -dQUIET -
Missing usbd_alloc_xfer and usbd_alloc_buffer man pages
Hi all! Can someone please explain to me what usbd_alloc_xfer and usbd_alloc_buffer do? I do not believe there are manual pages for either of them. I read the code on bxr.su, but I want to make sure I understand the intention of it. Thank, - Farhan
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Fri, 5 Aug 2022, Alexander Hall wrote: > > > On August 5, 2022 8:32:25 AM GMT+02:00, Brian Durant > wrote: > > > > > >On Thu, 4 Aug 2022, Alexander Hall wrote: > > > >> > >> > >> On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant > >> wrote: > >> > > >> > > >> >On Thu, 4 Aug 2022, Lucas wrote: > >> > > >> >> Brian Durant wrote: > >> >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am > >> >> > experiencing a > >> >> > couple of issues. The first is related to the following addition that > >> >> > I > >> >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 > >> >> > installs, > >> >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: > >> >> > XTerm*VT100.Translations: #override\ > >> >> > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > >> >> > Ctrl Shift V: insert-selection(CLIPBOARD) > >> >> > Any ideas how to get copy and paste working in Xterm with an i386 > >> >> > install? > >> >> > >> >> I don't know if it's relevant, but my Xdefaults looks like this > >> >> > >> >> XTerm.VT100.translations: #override \n\ > >> >> Ctrl Alt C:copy-selection(CLIPBOARD) \n\ > >> >> Ctrl Alt V:insert-selection(CLIPBOARD) \n\ > >> >> [...other stuff...] > >> >> > >> >> In particular, do note the "\n" after #override, which isn't present in > >> >> your snippet. This works fine for me. > >> >> > >> >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know > >> >> if it's product of your MUA or if it's actually part of the file (it's > >> >> a non-breaking space, aka in XML/HTML), do double-check the > >> >> whitespaces in there. > >> >> > >> >> -Lucas > >> > > >> >Thanks for the reply. Trying a different MUA. Not sure where the extra > >> >characters that you mention crept in, however they weren't in the > >> >.Xdefaults file as far as I could see. I added the extra "\n\" in the > >> >last > >> >line as suggested, but weirdly this had no effect. Still no copy-paste in > >> >i386. > >> > >> It wasn't the last line that potentially lacked "\n\", it was the first > >> one, "#override\n\". > >> > >> I suspect paste actually might already work. Did you try copying from, > >> say, Firefox, and then paste into an xterm? > >> > >> I strongly believe this has nothing to do with the platform. > >> > >> /Alexander > > > >Hmm. Thanks for the inspiration, but no, paste wasn't already working. I > >have however, now got copy to work. Unfortunately, nothing I do seems to > >sort paste out. Currently my snippet looks like this: > >xterm.VT100.translations:#override \ > > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > > Ctrl Shift V: insert-selection(CLIPBOARD) > > > >The "n\" that you have in he first line shouldn't make a difference as it > >is a comment "#", isn't it? What causes me some concern, is the apparent > >lack of consistent behavior between architectures on this minor, but > >irritating issue. > > Every example from the xterm man page uses sth like: > > *VT100*translations: #override \n\ > > , and it makes sense, as # is not a comment in the resource file itself. So > your resource value above effectively becomes > > "#override Ctrl Shift C: copy-selection(CLIPBOARD) > Ctrl Shift V: insert-selection(CLIPBOARD)" > > instead of > > "#override > Ctrl Shift C: copy-selection(CLIPBOARD) > Ctrl Shift V: insert-selection(CLIPBOARD)" > > Also, while being at the edge of my confidence level here, generally > > XTerm*VT100*translations: > > With all them asterisks, usually kicks in better. YMMV though. > > Also, I assume the proper xrdb commands are issued to set these resource > values. > > /Alexander OK. I tried your suggestions with the "*" and "\n\" now everything is working fine. I corrected my .Xdefaults list on my amd64 install to match, and that works fine as well. Many thanks. Brian
Re: Trouble with lpr and Brother wireless printer
On 2022-08-05, Sean Kamath wrote: > What I still believe: Get a printer that does one thing: Print. No > gizmofrobs or wingdings. And get a laser printer. Ink is a nightmare. OTOH I'm very happy with my Brother MFC-J4335DW inkjet. I haven't got scanning to work from OpenBSD but that works from my phone and non-OpenBSD boxes (and I mostly wanted that for making quick copies anyway). Printing via CUPS works great, ink is not ridiculously priced, duplexing works properly, doesn't take up too much space, etc.
Re: Trouble with lpr and Brother wireless printer
On Thu, Aug 04, 2022 at 09:27:09PM -0700, Ben Hancock wrote: > Boy, I went down the rabbit hole on this one. I'll spare the list > all the gory details, but for the sake of posterity I figured I'll > try to close the loop on this thread. > > To make a long story short: After failing to get the printer working > with just regular lpr, I tried CUPS to no avail. Along the way, Did you happen to try CUPS with the brlaser package installed? I have a Brother HL-L2390DW, and once I found brlaser it just worked. -Ryan > however, I discovered a Perl script in a Linux package available > on Brother's website that ostensibly could have served as an input > filter for lpr (called, somewhat obviously, `lpdfilter`). After a > bit of searching, I found a related thread [1] on a FreeBSD list > and made some edits to this script, hoping that it would be the trick. > > Where I hit a wall was with a binary (also included in the package) > called `rawtobr3`, that the Perl script expected. It appears to be > proprietary Brother stuff and kept throwing an error, probably > because it was built for Linux and not BSD. I did find a GitHub > repo via a FreeBSD forum thread [2] that seemed to include _some_ > version of this program, but it threw another error and the filter > did not work. > > So, to wrap up: I do not recommend the Brother HLL2350DW for your > OpenBSD printing needs. I may end up heeding the suggestions to > simply buy a printer that speaks PostScript. Recommendations welcome. > > - Ben > > [1] > https://lists.freebsd.org/pipermail/freebsd-questions/2017-July/277994.html > > [2] https://forums.freebsd.org/threads/port-for-brother-printer-drivers.78393/ >
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On August 5, 2022 8:32:25 AM GMT+02:00, Brian Durant wrote: > > >On Thu, 4 Aug 2022, Alexander Hall wrote: > >> >> >> On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant >> wrote: >> > >> > >> >On Thu, 4 Aug 2022, Lucas wrote: >> > >> >> Brian Durant wrote: >> >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing >> >> > a >> >> > couple of issues. The first is related to the following addition that I >> >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 >> >> > installs, >> >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: >> >> > XTerm*VT100.Translations: #override\ >> >> > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ >> >> > Ctrl Shift V: insert-selection(CLIPBOARD) >> >> > Any ideas how to get copy and paste working in Xterm with an i386 >> >> > install? >> >> >> >> I don't know if it's relevant, but my Xdefaults looks like this >> >> >> >> XTerm.VT100.translations: #override \n\ >> >> Ctrl Alt C:copy-selection(CLIPBOARD) \n\ >> >> Ctrl Alt V:insert-selection(CLIPBOARD) \n\ >> >> [...other stuff...] >> >> >> >> In particular, do note the "\n" after #override, which isn't present in >> >> your snippet. This works fine for me. >> >> >> >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know >> >> if it's product of your MUA or if it's actually part of the file (it's >> >> a non-breaking space, aka in XML/HTML), do double-check the >> >> whitespaces in there. >> >> >> >> -Lucas >> > >> >Thanks for the reply. Trying a different MUA. Not sure where the extra >> >characters that you mention crept in, however they weren't in the >> >.Xdefaults file as far as I could see. I added the extra "\n\" in the last >> >line as suggested, but weirdly this had no effect. Still no copy-paste in >> >i386. >> >> It wasn't the last line that potentially lacked "\n\", it was the first one, >> "#override\n\". >> >> I suspect paste actually might already work. Did you try copying from, say, >> Firefox, and then paste into an xterm? >> >> I strongly believe this has nothing to do with the platform. >> >> /Alexander > >Hmm. Thanks for the inspiration, but no, paste wasn't already working. I >have however, now got copy to work. Unfortunately, nothing I do seems to >sort paste out. Currently my snippet looks like this: >xterm.VT100.translations: #override \ > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > Ctrl Shift V: insert-selection(CLIPBOARD) > >The "n\" that you have in he first line shouldn't make a difference as it >is a comment "#", isn't it? What causes me some concern, is the apparent >lack of consistent behavior between architectures on this minor, but >irritating issue. Every example from the xterm man page uses sth like: *VT100*translations: #override \n\ , and it makes sense, as # is not a comment in the resource file itself. So your resource value above effectively becomes "#override Ctrl Shift C: copy-selection(CLIPBOARD) Ctrl Shift V: insert-selection(CLIPBOARD)" instead of "#override Ctrl Shift C:copy-selection(CLIPBOARD) Ctrl Shift V: insert-selection(CLIPBOARD)" Also, while being at the edge of my confidence level here, generally XTerm*VT100*translations: With all them asterisks, usually kicks in better. YMMV though. Also, I assume the proper xrdb commands are issued to set these resource values. /Alexander
Re: Trouble with lpr and Brother wireless printer
> On Aug 4, 2022, at 21:27, Ben Hancock wrote: > > So, to wrap up: I do not recommend the Brother HLL2350DW for your > OpenBSD printing needs. I may end up heeding the suggestions to > simply buy a printer that speaks PostScript. Recommendations welcome. HP used to make freakin’ tanks, and I had a LasterJet 4MV or 4M+for something close to 15 years. Bought it rebuilt (AFTER they stopped manufacturing it). :-). I can’t speak to anything they produced after 2005, though. I’ve been extremely happy with my Canon — but I don’t use it from OpenBSD (though someday I will get around to it). They make engines that a lot of other companies use. I used to subscribe to the idea that buying a used “enterprise” printer was ideal (hence the used HPs — I had two, they both were awesome), but I’ve been seduced by short click-to-clack times. What I still believe: Get a printer that does one thing: Print. No gizmofrobs or wingdings. And get a laser printer. Ink is a nightmare. Sean PS I used to work at a printer company (actually two). I used to know a LOT about printers (particularly PostScript printers). I don’t anymore (I’ve been out of that space for . . . wow. 18 years now. . .). It wasn’t HP.
Re: Trouble with lpr and Brother wireless printer
On Aug 04 21:27:09, b...@benghancock.com wrote: > So, to wrap up: I do not recommend the Brother HLL2350DW for your > OpenBSD printing needs. I may end up heeding the suggestions to > simply buy a printer that speaks PostScript. Recommendations welcome. I bought an HP LaserJet M608 for peanuts, works without any fuss as lp::lp=:rm=pr.stare.cz:rp=lp:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh: Jan
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Thu, 4 Aug 2022, Alexander Hall wrote: > > > On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant > wrote: > > > > > >On Thu, 4 Aug 2022, Lucas wrote: > > > >> Brian Durant wrote: > >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing a > >> > couple of issues. The first is related to the following addition that I > >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 installs, > >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: > >> > XTerm*VT100.Translations: #override\ > >> > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > >> > Ctrl Shift V: insert-selection(CLIPBOARD) > >> > Any ideas how to get copy and paste working in Xterm with an i386 > >> > install? > >> > >> I don't know if it's relevant, but my Xdefaults looks like this > >> > >> XTerm.VT100.translations: #override \n\ > >> Ctrl Alt C:copy-selection(CLIPBOARD) \n\ > >> Ctrl Alt V:insert-selection(CLIPBOARD) \n\ > >> [...other stuff...] > >> > >> In particular, do note the "\n" after #override, which isn't present in > >> your snippet. This works fine for me. > >> > >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know > >> if it's product of your MUA or if it's actually part of the file (it's > >> a non-breaking space, aka in XML/HTML), do double-check the > >> whitespaces in there. > >> > >> -Lucas > > > >Thanks for the reply. Trying a different MUA. Not sure where the extra > >characters that you mention crept in, however they weren't in the > >.Xdefaults file as far as I could see. I added the extra "\n\" in the last > >line as suggested, but weirdly this had no effect. Still no copy-paste in > >i386. > > It wasn't the last line that potentially lacked "\n\", it was the first one, > "#override\n\". > > I suspect paste actually might already work. Did you try copying from, say, > Firefox, and then paste into an xterm? > > I strongly believe this has nothing to do with the platform. > > /Alexander Hmm. Thanks for the inspiration, but no, paste wasn't already working. I have however, now got copy to work. Unfortunately, nothing I do seems to sort paste out. Currently my snippet looks like this: xterm.VT100.translations: #override \ Ctrl Shift C: copy-selection(CLIPBOARD) \n\ Ctrl Shift V: insert-selection(CLIPBOARD) The "n\" that you have in he first line shouldn't make a difference as it is a comment "#", isn't it? What causes me some concern, is the apparent lack of consistent behavior between architectures on this minor, but irritating issue.
