Re: Is Pip Available On OpenBSD?

2023-12-02 Thread Dominic Reich

* Jay F. Shachter  [Sun, Dec  3 2023 01:38 -0600]:


I am trying to build some software which claims that it needs glad2.
Glad2 does not seem to exist as an OpenBSD package but it claims that
it can be installed with pip.   There does not seem to be an OpenBSD
package named py310-pip or anything similar.  Is it possible to
install pip on OpenBSD (other than thru the dubious means of compiling


Not sure if this is the right way, but I recently installed Thonny
on current via

$ python3 -m pip install --user --upgrade thonny

HTH
dominic

--
Life is really simple, but we insist on making it complicated.
- Confucius



Re: Is Pip Available On OpenBSD?

2023-12-02 Thread Otto Moerbeek
On Sun, Dec 03, 2023 at 01:38:07AM -0600, Jay F. Shachter wrote:

> 
> Esteemed Colleagues:
> 
> I am trying to build some software which claims that it needs glad2.
> Glad2 does not seem to exist as an OpenBSD package but it claims that
> it can be installed with pip.   There does not seem to be an OpenBSD
> package named py310-pip or anything similar.  Is it possible to
> install pip on OpenBSD (other than thru the dubious means of compiling
> python from source)?  Alternately, is it possible to install glad2
> without installing pip?  Or, as an alternative to the alternative, is
> it possible to install the current version of libplacebo (the OpenBSD
> package is at version 4.208.0, whereas I need at least version 6.292.0)
> without building it from source?
> 
> I haven't upgraded to OpenBSD 7.4 yet and am still running 7.3, if
> that makes a difference.
> 
> Thank you in advance for any and all replies.
> 
> 
>   Jay F. Shachter
>   6424 North Whipple Street
>   Chicago IL  60645-4111
>   (1-773)7613784   landline
>   (1-410)9964737   GoogleVoice
> http://m5.chicago.il.us
>   j...@m5.chicago.il.us
> 
>   "But when she traced the killer's IP address ... it was in the 
> 192.168/16 block!"
> 

The name of the pip package for python3 is is py3-pip.

-Otto



Is Pip Available On OpenBSD?

2023-12-02 Thread Jay F. Shachter


Esteemed Colleagues:

I am trying to build some software which claims that it needs glad2.
Glad2 does not seem to exist as an OpenBSD package but it claims that
it can be installed with pip.   There does not seem to be an OpenBSD
package named py310-pip or anything similar.  Is it possible to
install pip on OpenBSD (other than thru the dubious means of compiling
python from source)?  Alternately, is it possible to install glad2
without installing pip?  Or, as an alternative to the alternative, is
it possible to install the current version of libplacebo (the OpenBSD
package is at version 4.208.0, whereas I need at least version 6.292.0)
without building it from source?

I haven't upgraded to OpenBSD 7.4 yet and am still running 7.3, if
that makes a difference.

Thank you in advance for any and all replies.


Jay F. Shachter
6424 North Whipple Street
Chicago IL  60645-4111
(1-773)7613784   landline
(1-410)9964737   GoogleVoice
http://m5.chicago.il.us
j...@m5.chicago.il.us

"But when she traced the killer's IP address ... it was in the 
192.168/16 block!"



re(4) timeouts

2023-12-02 Thread Capitan Cloud
Here the same driver on a laptop gives no problem on stable.
But it is about an other nic model..
I'm not new to this watchdog string, it could be
something missconfigured. How they look liie your
.re0 file and your resolv.conf? Are you using unbund?

bring you any clue the following?
https://marc.info/?l=openbsd-misc=164980790919513=2

-- Nowarez Market

Dec 2, 2023 22:11:43 Jan Stary :

> re0: watchdog timeout
> re0: stopping TXQ timed out!



re(4) timeouts

2023-12-02 Thread Jan Stary
This is current/amd64 on a HP 260 (a mini PC, dmesg below).
Everything seems to work, with two exceptions:

1. The re0 keeps complaining about

re0: watchdog timeout
re0: stopping TXQ timed out!

and never initializes enough to get an address.
Is anyone seeing this with re(4)?
Is that a driver issue?

The machine boots windows (yet) from the internal disk
where the NIC seems to work just fine, so I don't think
it is a HW error.


2. The pckbc occasionaly complains abut

pckbc: command timeout

but the keyboards seems to be working just fine.


Jan


OpenBSD 7.4-current (GENERIC.MP) #1471: Thu Nov 30 07:57:45 MST 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8454909952 (8063MB)
avail mem = 8179015680 (7800MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed1e0 (37 entries)
bios0: vendor AMI version "02.25" date 03/10/2022
bios0: HP Pippin2
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT SSDT 
DBGP DBG2 SSDT SSDT UEFI SSDT DMAR DBGP
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) 
RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) 
RP13(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, 2194.89 MHz, 06-4e-03, patch 
00f0
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 3MB 64b/line 12-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, 2194.89 MHz, 06-4e-03, patch 
00f0
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 3MB 64b/line 12-way L3 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, 2194.89 MHz, 06-4e-03, patch 
00f0
cpu2: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 3MB 64b/line 12-way L3 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, 2194.89 MHz, 06-4e-03, patch 
00f0
cpu3: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 3MB 64b/line 12-way L3 cache
cpu3: smt 1, core 1, 

Re: Thinkpad x260 not connecting to network

2023-12-02 Thread Mike Evron
Thanks for the advice all, but I've resolved the issue, and I'm quite
embarrassed:  I made absolutely sure to type the password in correctly, but
mistyped the ssid 

Thanks again.

On Sat, Dec 2, 2023 at 9:29 AM Stuart Henderson 
wrote:

> On 2023-12-02, Mike Evron  wrote:
> >
> > Thanks for taking the time to look into this.  If there is any more info
> > needed or if this should be formatted differently, please let me know.
>
> Run "ifconfig iwm0 debug", try to connect, and send the full dmesg.
>
>
> --
> Please keep replies on the mailing list.
>
>


Re: Thinkpad x260 not connecting to network

2023-12-02 Thread Stuart Henderson
On 2023-12-02, Mike Evron  wrote:
>
> Thanks for taking the time to look into this.  If there is any more info
> needed or if this should be formatted differently, please let me know.

Run "ifconfig iwm0 debug", try to connect, and send the full dmesg.


-- 
Please keep replies on the mailing list.



Re: Thinkpad x260 not connecting to network

2023-12-02 Thread Mikhail
On Fri, Dec 01, 2023 at 11:32:05PM -0800, Mike Evron wrote:
> Ifconfig output for iwm0:
> 
> iwm0: flags=808847
> mtu 1500
> lladdr 44:85:00:14:a4:06
> index 1 priority 4 llprio 3
> groups: wlan
> media: IEEE802.11 autoselect
> status: no network
> ieee80211: nwid sharynmikealbie wpakey wpaprotos wpa2 wpaakms psk
> wpaciphers ccmp wpagroupcipher ccmp
> 
> contents of hostname.iwm0:
> 
> join sharynmikealbie wpakey i-triple-checked-the-pw-i-swear
> inet autoconf
> 
> I've run fw_update and done many searches and can't figure out why this
> doesn't work.
> 
> Any help would be greatly appreciated.
> 
> Thanks in advance.

doas ifconfig iwm0 -joinlist (btw, your ifconfig says nwid, but in
hostname.iwm0 you use join)
doas tcpdump -y IEEE802_11_RADIO -ni iwm0 wlan host 44:85:00:14:a4:06

in neighboring terminal:
doas sh /etc/netstart

and bring output of tcpdump here, if there is some traffic frames
"authentication request/response" and further - use -w flag to tcpdump
to write pcap file and also send it to the list



Re: Thinkpad x260 not connecting to network

2023-12-02 Thread Mike Evron
Hi Corey,


> 1) Try quotation marks around the SSID and password.
>

Have done.  Still not working.

>
> 2) Make sure that you have run
>
> ifconfig iwm0 up
> sh /etc/netstart
>

I have.


>
> 3) If you are still confused, you can check
>
> a) man pages for hostname.if(5) or iwn(4)
>
> b) FAQ entry for Wireless
> https://www.openbsd.org/faq/faq6.html#Wireless
>
>
I went through this stuff several times before posting to the list.

To be clear, scanning works fine.  For some reason, it just won't connect
to the network.  It's the only thing I haven't been able to get working on
OpenBSD, but it is a showstopper for obvious reasons.

Thanks for taking the time to look into this.  If there is any more info
needed or if this should be formatted differently, please let me know.

Thanks again.


Re: Thinkpad x260 not connecting to network

2023-12-02 Thread Stephan, Corey J
Mike,

1) Try quotation marks around the SSID and password.

2) Make sure that you have run

ifconfig iwm0 up
sh /etc/netstart

3) If you are still confused, you can check

a) man pages for hostname.if(5) or iwn(4)

b) FAQ entry for Wireless
https://www.openbsd.org/faq/faq6.html#Wireless

or, unofficially,

c) my blog post on configuring the X270, subsection #wifi:
https://www.coreystephan.com/openbsd-thinkpad/#wifi

Cheers,
Corey

-- 
Corey Stephan, Ph.D.
coreystephan.com