Re: possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-24 Thread Matthew Graybosch

On 7/23/19 2:41 PM, Stefan Sperling wrote:

Not at all! You've shown that this isn't a recent regression.


Well, this is what I get for using a machine manufactured in 2007. I 
suppose this bug went unnoticed for so long because development moved 
onto machines with other wifi chipsets.



If I had hardware to work with I could try to get it working.
But I don't have any AR5418 devices.


I understand. It's old hardware, and not exactly common nowadays, so I'm 
glad you didn't simply brush me off by suggesting I buy a newer laptop.



This commit make it look like problems with AR5418 were known
a decade ago already and never quite fixed:


Glad I was able to help a little. How should I go about helping test a 
fix? I've switched my T60 to Debian because I need working wifi, but I 
still have a ThinkCentre M92P running -current. Should I try finding a 
USB wifi adapter that uses the AR5418 chipset?


--
Matthew Graybosch



Re: possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-23 Thread Matthew Graybosch

On 7/11/19 5:57 AM, Stefan Sperling wrote:


Testing just bsd.rd is enough. If the bsd.rd environment is too limiting
you could also install to a USB stick and boot from it for testing purposes.

Either approach should suffice to test a wifi connection.


Hi, Stefan. Sorry it took so long to get back to you, but I tried the 
following releases by installing to USB over the last couple of weeks:


* 6.4
* 6.3
* 6.2
* 6.1
* 6.0
* 5.9
* 5.8

Unfortunately, I didn't get better results with any of these. athn0 
would sporadically work when explicitly set up in 11g mode, but would 
usually just balk with "athn0: Device Timeout".


Sorry to have wasted your time on this.

--
Matthew Graybosch



Re: possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-10 Thread Matthew Graybosch
On Wed, 10 Jul 2019 18:32:37 +0200
Stefan Sperling  wrote:

> So 11g works, and only 11n mode is broken?
> Your AP probably doesn't support 11a mode.

Sorry, Stefan, but I didn't think to try 11n mode. I must have taken
your instructions too literally.

However, I tried 11n at home after work, and that didn't work. Neither
did 11a or 11g. Worse, when I tried connecting to my phone's access
point using 11g, that didn't work either. Nor did rebooting help.

I *was* able to make wifi work using a MX Linux LiveUSB, so I don't
think it's the hardware (and I really don't want to go back to Linux).

> 11n mode should work with your device. I will see if I can figure out
> why it does not work, but I don't yet have much information to go on
> and I don't have access to this hardware.

Thanks for giving it a shot anyway and helping me make this old laptop
a little more useful. Aside from the wifi it still works fine with
OpenBSD.

> If you could test kernels of older releases and check whether 11n mode
> was working at some point, that would help me.

Would pulling the bsd.rd for 6.4 and temporarily reverting to that
release help? Naturally I'll take a full backup first, but I think
that might be safer than simply downloading the bsd.mp for 6.4 while
leaving the userland at -current.

Otherwise, since I'm doing a full backup anyway, I could just wipe and
do a clean install of 6.4.

Thanks again for your assistance.

-- 
Matthew Graybosch



Re: When will OpenBSD become a friendly place for bug reporters?

2019-07-10 Thread Matthew Graybosch
On Thu, 11 Jul 2019 00:41:45 +0200
ropers  wrote:

> Any hints on how to even start with that hardest part, or what to read
> or where to look would be MORE than welcome.

Hi, ropers. I've been reading this thread about altnumd and using
alt+000 to enter arbitrary Unicode characters like people did on DOS
and Windows. I noticed that nobody mentioned that X11 already has a
method for entering arbitrary Unicode characters using pre-defined key
sequences. It's called the "Compose" key (aka the Multi_Key in X11
header files).

https://en.wikipedia.org/wiki/Compose_key

PC and Mac keyboards don't provide a physical compose key, but you can
remap a key you don't usually use (like Caps Lock or the right-hand ALT
or CTRL keys) using setxkbmap(1).

Here's the command I use in my ~/.xsession file:

setxkbmap -option compose:caps &

Hopefully this helps somebody.

-- 
Matthew Graybosch
https://matthewgraybosch.com | gopher://asgartech.com:70
xmpp: starbrea...@matthewgraybosch.com
"'Out of order'? Even in the future nothing works!"



Re: lenovo thinkpoad with nvidia and intel graphics?

2019-07-10 Thread Matthew Graybosch
On Wed, 10 Jul 2019 09:41:51 -0400
paul wisehart  wrote:

> Hi,
> I have been windowshopping for a T440p or t540p thinkpad.
> I try to find a version that uses the intel graphics chipset, 
> but it seems most have nividia and intel. 

I have a T430s with both Intel integrated graphics and discrete NVidia
graphics. I disabled the latter at the BIOS level since Xenocara
doesn't support it, and the system worked fine with just the integrated
Intel graphics.

You might be able to do the same with most of the T440p and T540p
units, but check the specs to be sure.

-- 
Matthew Graybosch



Re: (SOLVED!) possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-10 Thread Matthew Graybosch
On Wed, 10 Jul 2019 16:59:46 +0200
Juan Francisco Cantero Hurtado  wrote:

> Forget my previous mail. Stefan is the right guy for your bug.

Thanks, Juan, but Stefan had already given me the hint I needed. I
needed a line in /etc/hostname.athn0 to explicitly set my device to use
802.11g.

!ifconfig athn0 mode 11g
join "foonet" wpakey 
dhcp
inet6 autoconf
up powersave

-- 
Matthew Graybosch



Re: possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-10 Thread Matthew Graybosch
On Wed, 10 Jul 2019 10:13:48 +0200
Stefan Sperling  wrote:

> What's interesting is that this is another device with unequal amount
> of Tx and Rx chains; so your problem looks similar to this bug which
> has already been fixed: https://marc.info/?t=15569501472=1=2

Thanks for pointing this out, Stefan. It hadn't occurred to me to
search for problems with other chipsets supported by athn(4). Let's
chalk it up to brain damage on my part from years of Linux usage. :)

> To start narrowing things down a bit, can you try 'ifconfig athn0
> mode 11g' and 'ifconfig athn0 mode 11a' to see if those modes still
> work?

11a didn't work, but 11g did. Here's the shell script I used.

BOF
#!/usr/bin/env ksh

echo "shutting down athn0"
ifconfig athn0 down
sleep 15
echo "starting up athn0 in 11g mode"
ifconfig athn0 mode 11g join "Portable Hotspot" wpakey 
up dhclient athn0
EOF

Thanks for the suggestion. I hadn't thought about manually setting the
mode; I had assumed from reading the man page that athn would select
the appropriate mode, but I guess I was wrong.

Now I just need to RTFM again and figure out how to get the mode
setting into /etc/hostname.athn0.

Thanks again!

-- 
Matthew Graybosch
https://matthewgraybosch.com | gopher://asgartech.com:70
xmpp: starbrea...@matthewgraybosch.com
"'Out of order'? Even in the future nothing works!"



possible athn(4) bug in 6.5-current involving AR5418 chipset on used ThinkPad T60

2019-07-09 Thread Matthew Graybosch
Hello. I'm having a bit of trouble getting wifi to work on a used
ThinkPad T60 with an AR5418 chipset, and gathered as much info as
possible by running sendbug as root. I can post the following to bugs@
if anybody thinks that would be more appropriate, but I had read
 and thought it best to post here
first since I'm having trouble with -current.

I'm currently managing without wifi on this machine, so I'll understand
if my particular setup is too old and busted to be worth much effort,
but in the meantime I'll be watching misc@ in case it's my fault for
not understanding the man pages.

>Synopsis:  constant athn0 "device timeout" errors on 6.5-current
>Category:  amd64 kernel system
>Environment:
System  : OpenBSD 6.5
Details : OpenBSD 6.5-current (GENERIC.MP) #101: Fri Jul 5 08:19:55 
MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
>Description:
After buying a refurbished Lenovo ThinkPad T60 and installing
OpenBSD 6.5 I attempted to set up wifi using the athn(4) driver
using the instructions in the man page and the OpenBSD FAQ at
.I tried
switching to -current in case the issue had already been fixed,
but no dice.

I've reproduced the contents of my hostname.athn0 file below,
with the SSIDs and passwords changed.

#BEGIN /etc/hostname.athn0
join "FBI Surveillance Van" wpakey 
join "I have loud neighbors" wpakey 
join "Smartphone Hotspot" wpakey 
dhcp
inet6 autoconf
up powersave
#END /etc/hostname.athn0
>How-To-Repeat:
This issue happens automatically when I reboot, unless I
disable wifi using the hardware switch. This issue also occurs
if I attempt to manually connect using ifconfig and dhclient.
>Fix:
Wired ethernet works, as does Android phone tethering using
urndis(4).

dmesg:
OpenBSD 6.5-current (GENERIC.MP) #101: Fri Jul  5 08:19:55 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3203203072 (3054MB)
avail mem = 3096092672 (2952MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version "7IET30WW (1.11 )" date 07/13/2007
bios0: LENOVO 87445BU
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4)
EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3)
HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.38 MHz, 06-0f-06
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.01 MHz, 06-0f-06
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(250@17
mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at
acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical
temperature is 100 degC acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpicmos0 at acpi0
"IBM0071" at acpi0 not configured
tpm0 at acpi0: TPM_ addr 0xfed4/0x1000, Atmel 97SC3203 rev 0x5
acpibat0 at acpi0: BAT0 model "COMPATIBLE" serial 13920 type LION oem
"SANYO" acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpidock0 at acpi0: GDCK not docked (0)

Re: 6.5 PowerPC Packages

2019-05-09 Thread Matthew Graybosch
On Thu, May 9, 2019, at 9:28 AM, Henry Bonath wrote:
> I'm not sure how many folks out there are PowerPC users, but I was
> just curious if anyone had an idea on if or when we might see those
> out in the mirrors.

I've got a 2003 lamp-style iMac that runs the macppc port of OpenBSD
-CURRENT. It runs fine but could use a RAM upgrade and a new SSD.
Pre-built package support for macppc isn't as extensive as on amd64;
NetSurf is the best graphical web browser I've found in macppc
packages, and I haven't dared try compiling from ports using only
256MB of RAM and the original 60GB HDD -- but at least I've got Emacs.

-- 
Matthew Graybosch
https://www.matthewgraybosch.com
"Out of order? Even in the future nothing works."



Re: When will be created a great desktop experience for OpenBSD?

2019-05-08 Thread Matthew Graybosch
On Wed, May 8, 2019, at 5:18 PM, Roderick wrote:
> 
> On Wed, 8 May 2019, noah pugsley wrote:
> 
> > Updated FVWM or a different default config?
> 
> I hope, no one comes to the idea to change the configuration.

I'm not really fussed about the default FVWM config; it's easy enough to pull a 
copy into $HOME and start tinkering with it once you've read fvwmrc(5), or to 
switch to cwm (1) (my favorite). Hell, it wasn't that hard to install OpenBSD 
with MATE and LibreOffice on a neighbor's old Intel NUC so her kids had a 
machine to do homework on without getting distracted by Fortnite (but wait 
until they discover hack(6)).

I'm happy with OpenBSD as a desktop machine, even though the OS wasn't made 
with me in mind, and I appreciate all of the work the developers have put into 
it for their own purposes. Thanks!

-- 
Matthew Graybosch
"'Out of order'?! Even in the future nothing works."



Re: dhclient vio0 -> Segmentation fault

2019-04-05 Thread Matthew Graybosch
On Thu, Apr 4, 2019, at 1:19 AM, Greg Steuck wrote:
> April 2 snapshot misbehaves badly on Google Compute Engine.
> 
> # dmesg | head
> OpenBSD 6.5 (GENERIC.MP) #839: Tue Apr  2 20:38:19 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> # dhclient -v -d vio0
> vio0: DHCPDISCOVER - interval 1
> vio0: DHCPOFFER from 169.254.169.254 (42:01:0a:80:00:01)
> Segmentation fault
> # ls -l /sbin/dhclient

I don't think this is confined to Google Compute Engine. I just upgraded my 
ThinkPad T430s to the April 2 snapshot, and I have a similar experience when 
setting up both wired and wireless connections (em0 and iwn0) using DHCP. My 
dhclient also segfaults after receiving DHCPOFFER from the local Verizon FIOS 
router. 

Sorry for the lack of dmesg, but I'm typing this from my phone. 

-- 
Matthew Graybosch
https://www.matthewgraybosch.com
"Out of order? Even in the future nothing works."



Re: Missing libraries.

2019-02-10 Thread Matthew Graybosch
On Mon, 11 Feb 2019 08:13:16 +0300
Kihaguru Gathura  wrote:

> Hi,
> 
> Any ideas on how to fix the missing libraries,
> 
> www# pkg_add -v mini_sendmail-chroot
> Update candidates: quirks-3.91 -> quirks-3.91
> quirks-3.91 signed on 2019-02-10T22:07:56Z
> Can't install mini_sendmail-chroot-1.3.9 because of libraries
> |library c.95.0 not found
> | /usr/lib/libc.so.92.6 (system): bad major
> Couldn't install mini_sendmail-chroot-1.3.9
> www#

The following assumes you're running -current on bare metal. If you're
running -current on a virtual machine, I don't know how to help you.
Sorry.

1. Reboot.
2. Type "bsd.rd" at the boot prompt.
3. Upgrade your system.
4. Once you're done, restart and run "pkg_add -Dsnap -Uu"
   to upgrade your existing packages.

If you're running -current and you can't install a package because of
"versions" or a "bad major", it's because new snapshots just hit the
server and your installation is out of date.

-- 
Matthew Graybosch
https://matthewgraybosch.com
https://mastodon.sdf.org/@starbreaker
xmpp: starbrea...@matthewgraybosch.com



Re: Some highlights: Emacs 21.4 and 25.3

2018-10-02 Thread Matthew Graybosch
On Tue, Oct 2, 2018, at 11:48 AM, Solene Rapenne wrote:

> emacs 25 has a X11 flavour -athena which do not use gtk, but you need to build
> it from ports, there is no package for it.
 
Thanks for the correction. I've just been going by what's available as a 
package.

-- 
Matthew Graybosch
https://www.matthewgraybosch.com
"Out of order? Even in the future nothing works."



Re: Some highlights: Emacs 21.4 and 25.3

2018-10-02 Thread Matthew Graybosch
On Tue, Oct 2, 2018, at 9:02 AM, Roderick wrote:
> 
> I see, openbsd 6.3 offers Emacs 21.4 as port. May I ask, what is special
> in this old version of Emacs?

Hi, Rodrigo. I think the maintainers are keeping GNU Emacs 21.4 around because 
its graphical version isn't built against GTK, unlike the more recent releases.

-- 
Matthew Graybosch
https://www.matthewgraybosch.com
"Out of order? Even in the future nothing works."



Re: Guess what today is

2017-10-18 Thread Matthew Graybosch
On Wed, 18 Oct 2017 09:01:15 -0200
"x9p" <m...@x9p.org> wrote:

> Happy birthday and good f*cking amazing work.

Damn right. I might be a johnny-come-lately desktop OpenBSD user, but I
won't go back to Linux except under duress.

Even my wife likes it; she just doesn't know it's OpenBSD. =^.^=

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."



Re: About WPA2 compromised protocol

2017-10-17 Thread Matthew Graybosch
On Tue, 17 Oct 2017 19:09:29 +0200
"Stephane HUC \"PengouinBSD\"" <b...@stephane-huc.net> wrote:

> Just for the fun:
> http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/

I saw somebody share that on Mastodon this morning. :)

On a more serious note; am I correct in assuming that the patch is
already in 6.2?

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."



Re: Console resolution change since upgrade to 6.2

2017-10-17 Thread Matthew Graybosch
On Tue, 17 Oct 2017 18:49:14 +0200
Jan Lambertz <jd.arb...@googlemail.com> wrote:

> that were my first ideas. never had a wsconcsctl.conf, so nothing so
> post. I already created one  yesterday trying to solve the problem.
> 
> $ cat /etc/wsconsctl.conf
> display.height=800
> display.width=1200
> 
> System says "Value is read only".
> 

Setting just those two values in /etc/wsconsctl.conf should be OK. The
man page doesn't suggest otherwise. 

Not sure why you're getting "Value is read only", though. Not sure I
can do more to help. I'm sorry; I'm still new to OpenBSD.

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."



Re: Console resolution change since upgrade to 6.2

2017-10-17 Thread Matthew Graybosch
On Tue, 17 Oct 2017 17:53:22 +0200
Jan Lambertz <jd.arb...@googlemail.com> wrote:

> Hi,
> after upgrading one of my notebooks to 6.2 release my console
> resolution is only # wsconsctl
> display.type=inteldrm
> display.width=848
> display.height=480
> display.depth=32

Have you had a look at your dmesg output? I should have taken a closer
look at that myself. Sorry about that.

inteldrm0: msi
inteldrm0: 848x480, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured

The Intel DRM driver itself is reporting a max resolution of 848x480 at
boot time. Did you take any notes on what changes you made while
upgrading this laptop to 6.2-RELEASE? They might prove interesting.

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."



Re: Console resolution change since upgrade to 6.2

2017-10-17 Thread Matthew Graybosch
On Tue, 17 Oct 2017 17:53:22 +0200
Jan Lambertz <jd.arb...@googlemail.com> wrote:

> Only the left upper of the display is active.
> Screen is capable of 1280x800. That was the mode it worked in 6.1 i
> think. At least it was fullscreen.
> I didn't found a way to change the resolution. ideas to get back to
> full resolution and fullscreen ?

Hi, Jan. Have you had a look at the "/etc/wsconsctl.conf" file?
According to wsconsctl(8), that file contains parameters that rc(8)
sets for the system at startup.

If not, can you please reply with the contents of your copy of
"/etc/wsconsctl.conf"? Thanks.

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."