Re: Trouble with lpr and Brother wireless printer

2022-08-04 Thread Ben Hancock
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,
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.

2022-08-04 Thread Alexander Hall



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



Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.

2022-08-04 Thread Brian Durant



On Thursday, August 4, 2022, Michael Hekeler wrote:
> Am 04.08.22 15:27 schrieb Brian Durant:
> > 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 understand that you want to map these keys but just to mention: there
> is support for PRIMARY in xterm(1) and this means selected text is in
> primary without any explicit copy action taking place.
> see Inter-Client Communication Coventions Manual for X

Thank you for the information. Seen from my perspective, the override that I am 
using is more convenient on a laptop, but more importantly, expected behavior 
should be the same regardless of architecture. There shouldn't be different 
behavior on amd64 architecture compared to i386 architecture.



Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.

2022-08-04 Thread Michael Hekeler
Am 04.08.22 15:27 schrieb Brian Durant:
> 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 understand that you want to map these keys but just to mention: there
is support for PRIMARY in xterm(1) and this means selected text is in
primary without any explicit copy action taking place.
see Inter-Client Communication Coventions Manual for X



Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.

2022-08-04 Thread Brian Durant



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.



Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.

2022-08-04 Thread Lucas
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



Re: Console unnecessarily switches from 80x25 to 1920x1080

2022-08-04 Thread Stuart Henderson
On 2022-08-03, TCH  wrote:
> I have an OpenBSD 7.1 server. First i've installed only the following sets: 
> bsd, bsd.mp, bsd.rd, base71, comp71, man71.
>
> Then, when i was installing nginx, PHP and it's accessories with pkg_add, 
> php-gd refused to install because it needed xbase. I've booted into upgrade 
> mode and installed the following sets: xbase71, xfont71, xshare71.
>
> Since then, the machine switches into 1920x1080 during boot. All console 
> screens are like that. How do i tell OpenBSD to stop this and use the 80x25 
> character screen, like it did before? (I mean, literally, not via "emulation" 
> on a 1920x1080 graphical screen with the 'DOS' font.)

I think this is because of rebooting after fw_update was run, not because
of installing X sets.

> 'dmesg' is here:
> http://oscomp.hu/depot/dmesg.boot

You might be able to get it working how you want if you do
"echo disable radeondrm >> /etc/bsd.re-config", run
/usr/libexec/reorder_kernel, and reboot...


-- 
Please keep replies on the mailing list.



Re: Configuration of static ipv6 router

2022-08-04 Thread Nicolas Goy
On 2022 ven 29 jui - 14:08, Stuart Henderson wrote:
> On 2022-07-28, Nicolas Goy  wrote:
> >
> > Ok, I think I found the issue.
> >
> > The cisco is useing the address fe80:b2b:11fe:161::2  but for some
> > reason, openbsd doesn't link this.
> >
> > I cannot ping fe80:b2b:11fe:161::2%vport0 
> >
> > The system is adding fe80::%vport0/64 to the routing table.
> >
> > I am not sure, but I think that's the cause.
> >
> > I tried to add it to the routing table but it says "file exists".
> 
> I suggest you send output from the commands which show the current
> actual state of the system, i.e. netstat -rnfinet6, ifconfig -A, etc.
> And instead of e.g. "I cannot ping X", show the actual command you
> typed and what happened.
> 
> For anyone who might have an idea what's up, it's a lot easier to read
> these than it is to interpret information from english descriptions,
> and might give some clues from things which you didn't describe.
> Also it's much easier to compare this with how things look on a working
> system.
> 
> I don't think there's a dmesg in the information scattered in the
> thread either, sometimes that is useful, which is why it's always
> requested.
> 
> 


Well, yes, maybe I missed some info.

But hopefully someone figured it out, my ISP is using a link local
address that does not follow RFC 4129 which states that there must be 54
0 before the interface id.

https://www.rfc-editor.org/rfc/rfc4291.html#section-2.5.6

I asked my ISP to changeg the link local address, but no answer yet,
they are "working on it".



-- 
Nicolas Goy
Engineer & Developer

https://www.kuon.ch
https://www.goyman.com



Xterm copy-paste not happening on OpenBSD 7.1 i386.

2022-08-04 Thread Brian Durant
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?