Re: x260 hang at halt/reboot

[Base Pr1me]

OK. Then, I guess my only other suggestion would be to disable everything
that you can that looks suspect and see if the reboot hangs. If it does,
then that would rule out BIOS problems. If it doesn't, re-enable things one
at a time until it hangs.
By the way, that's a terrible pain-in-ass idea! LOL

On Tue, Aug 14, 2018 at 3:57 PM Stuart Henderson 
wrote:

> On 2018/08/14 15:53, Base Pr1me wrote:
> > Shooting from the hip: BIOS need upgraded?
>
> Thanks, but this is the newest public one already.
>
>

Re: x260 hang at halt/reboot

[Base Pr1me]

Shooting from the hip: BIOS need upgraded?

On Tue, Aug 14, 2018 at 3:33 PM Stuart Henderson 
wrote:

> I have a new (to me) X260 which hangs at halt/reboot. I've already
> disabled the TPM as I have some recollection of that causing problems in
> some cases but that hasn't helped. Any other suggestions? Thanks.
>
> OpenBSD 6.4-beta (GENERIC.MP) #209: Mon Aug 13 19:22:47 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8438833152 (8047MB)
> avail mem = 8173891584 (7795MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xd705d000 (63 entries)
> bios0: vendor LENOVO version "R02ET66W (1.39 )" date 06/12/2018
> bios0: LENOVO 20F6006YUK
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT SSDT DBGP
> DBG2 BOOT BATB SLIC SSDT SSDT MSDM DMAR ASF! FPDT UEFI
> acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP8(S4) XHCI(S3)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpihpet0 at acpi0: 2399 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2195.47 MHz
> 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,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 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) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
> 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,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
> 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,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 1, core 0, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
> 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,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (PEG0)
> acpiprt2 at acpi0: bus -1 (PEG1)
> acpiprt3 at acpi0: bus -1 (PEG2)
> acpiprt4 at acpi0: bus 2 (EXP1)
> acpiprt5 at acpi0: bus 4 (EXP3)
> acpiprt6 at acpi0: bus -1 (EXP4)
> acpiprt7 at acpi0: bus -1 (EXP5)
> acpiprt8 at acpi0: bus -1 (EXP8)
> acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
> C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
> C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: PUBS, resource for XHCI
> acpipwrres1 at acpi0: PG00, resource for PEG0
> acpipwrres2 at acpi0: PG01, resource for PEG1
> acpipwrres3 at acpi0: PG02, resource for PEG2
> 

Web store

[Base Pr1me]

Who runs https://www.openbsdstore.com? I went to buy a couple of shirts
last Friday, but cert returns errors and paypal linking stuff is quite
broken. Also, no one is responding to the ord...@openbsdstore.com address.

Any info available? I'm in the US, so that might be the difference.

Re: OpenBSD logo on my private hompage. It is allowed?

[Base Pr1me]

Hahahahahaha, I dare you!

On Thu, Jun 7, 2018, 21:42 Johannes Krottmayer  wrote:

> But i haven't a animated GIF with "under construction" on my site. :)
> Like the sites from the good old geocities. :)
>
> On Fri, Jun 08, 2018 At 05:37:08 +0200, Johannes Krottmayer wrote:
> > On Thu, Jun 07, 2018 At 21:32:55 -0600, Base Pr1me wrote:
> >> Not to be a Debbie Downer, but wasn't "under construction" banned from
> >> the internet a couple of decades a go? ;)
> >
> > LOL :)
> >
>

Re: OpenBSD logo on my private hompage. It is allowed?

[Base Pr1me]

Not to be a Debbie Downer, but wasn't "under construction" banned from the
internet a couple of decades a go? ;)

On Thu, Jun 7, 2018, 21:26 Johannes Krottmayer  wrote:

> Okay,
>
> My homepage is for non-profit purpose. I want create a little blog
> where I can present my open-source projects.
>
> So i can use the logo? Is this correct?
> Or should I ask deRaadt for this plan?
>
> Thanks in advance!
>
> Best regards,
> Johannes
>
> On Thu, Jun 007, 2018 At 22:39:36 -0400, Eric Furman wrote:
> > On Thu, Jun 7, 2018, at 10:10 PM, justina colmena wrote:
> >> On June 7, 2018 4:44:21 PM AKDT, Edgar Pettijohn III  >> web.com> wrote:
> >>>
> >>>
> >>> On 06/07/18 18:51, justina colmena wrote:
>  On June 7, 2018 3:27:30 PM AKDT, Johannes Krottmayer
> >>>  wrote:
> > Hallo,
> >
> > Thanks! I have read over that.
> >
> > Best regards,
> > Johannes Krottmayer
> >
> > On Thu, Jun 07, 2018 At 18:23:31 -0500, Constantine A. Murenin
> >>> wrote:
> >> On 7 June 2018 at 17:36, Johannes Krottmayer 
> > wrote:
> >>> Can I use the OpenBSD logo on my homepage? It is allowed?
> >>> I can't find any information about this plan.
> >> http://www.openbsd.org/art1.html has all the details.
> >>
> >> C.
> >>
>  " ... it is our intent that anyone be able to use these images to
> >>> represent OpenBSD in a positive light -- but do not make profit from
> >>> them"
> 
>  The no-profit clause is new. Sounds like I'd better dump OpenBSD
> >>> entirely if I want to make a profit at any sort of business or keep any
> >>> of my private information private or retain any of MY intellectual
> >>> property for my own use. There's a giant hole in my pocket that needs
> >>> to be sewn up. Not sure where to go. The lawyers are coming out like
> >>> alligators from the Florida swamps. This is as bad as SCO and groklaw.
> 
>  OpenBSD is for non-profit use only. Thank you for bringing that to my
> >>> attention.
>  --
>  https://www.colmena.biz/~justina/contacto.php
> 
> >>> I hope your joking. Obviously they don't want rogue people selling
> >>> merchandise with these images since it would detract from legitimate
> >>> sales that support the project. The operating system's license info is
> >>> here:
> >>> https://www.openbsd.org/policy.html
> >>
> >> Straw that broke the camel's back. There are a few other issues, namely
> >> people getting foreign psych degrees and prescribing "benzedrine" and
> >> such. I don't do drugs, and no, I am most certainly not joking. I am
> not
> >> happy with that kind of stuff, and  I personally do not want to support
> >> it on MY web page.
> >
> > Just the image itself is copyright deRaadt.
> > He just doesn't want you selling stickers or t-shirts or mugs or or or...
> > You can make and sell any product you want using OBSD.
> > No fee or questions asked. Even Baby-Mulching Machines.
> > If you want to include the OBSD logo in/on your product just write
> > and ask Theo's permission. Depending on what it is I'm pretty certain
> > he will give you permission.
> > Of course if you did make a profit from something you developed using
> > OBSD a donation would be greatly appreciated, but not required.
> > Many Big Corporations do it all the time.
> > (Use OBSD developed software and not give anything back, that is)
> > Your tinfoil hat is on too tight.
> >
>
>

Re: OT: Temperature sensors suggestions?

[Base Pr1me]

If you want, i'd be happy to discuss my setup offline. I've got lots of
code in GitHub already, that you could modify. There are other temp only
i2c sensors that would work too.

On May 18, 2018 16:38, "Daniel Ouellet" <dan...@presscom.net> wrote:

Thanks,

That look interesting. I wonder how the wifi works on this ESP8266 module.

It's so cheap that it's nothing lost to try. (;

Will see if I get other suggestions, but that's interesting and may well
be fun to program a driver for the SHT31-D too. (;

Daniel.




On 5/18/18 5:53 PM, Base Pr1me wrote:
> I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming
> involved.
> Good hardware though, if that's what you're looking for.
>
> On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet <dan...@presscom.net>
wrote:
>
>> Does anyone have a decent temperature sensors that can connect to an
>> OpenBSD server and be reliable and give any decent reading via either
>> USB or Serial port or even stand alone via Ethernet?
>>
>> I asked because yes I can use the sensors on some servers, but I got a
>> pretty expensive router blowing up because an AC unit stop working and
>> in a few hours the router was history and I need something reliable so I
>> can graph the changes in temperature to keep track of things.
>>
>> I got lucky this time as that using was providing 192 VoIP channels and
>> I had just moved them from PRI to full SIP like a month earlier. If I
>> haven't done that it would have been a disaster for me!
>>
>> So, I need more then just servers sensors so I can place these at
>> various location to get a better idea of what's going on.
>>
>> I don't understand why it is so difficult to have decent AC technician
>> keep AC units working properly. It's not like brain surgery, but that's
>> always a problem.
>>
>> Anything you know or use that is reliable that you can recommend would
>> be very much appreciated.
>>
>> I am trying to keep it simple, so using base tools in OpenBSD is a must,
>> no proprietary shit or Windows crap like I found tonnes of them. I have
>> NO Windows systems for 20+ years already and I am sure hell not going to
>> install any either. I try to keep it simple. Even snmp reading is find.
>> Simpler the better. I can grab the reading and save to a database to
>> graph later and what not. I got two self standing units in the pass,
>> nice but they get hacked and not useful obviously, so add-on to OpenBSD
>> is better to me. I trust that way more then all the self standing units,
>> records proving it...
>>
>> If that's no interest for the list fell free to reply off line as well,
>> but I guess some might like to know too.
>>
>> Thanks in advance for any suggestions...
>>
>> Daniel
>>
>>

Re: OT: Temperature sensors suggestions?

[Base Pr1me]

I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming
involved.
Good hardware though, if that's what you're looking for.

On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet  wrote:

> Does anyone have a decent temperature sensors that can connect to an
> OpenBSD server and be reliable and give any decent reading via either
> USB or Serial port or even stand alone via Ethernet?
>
> I asked because yes I can use the sensors on some servers, but I got a
> pretty expensive router blowing up because an AC unit stop working and
> in a few hours the router was history and I need something reliable so I
> can graph the changes in temperature to keep track of things.
>
> I got lucky this time as that using was providing 192 VoIP channels and
> I had just moved them from PRI to full SIP like a month earlier. If I
> haven't done that it would have been a disaster for me!
>
> So, I need more then just servers sensors so I can place these at
> various location to get a better idea of what's going on.
>
> I don't understand why it is so difficult to have decent AC technician
> keep AC units working properly. It's not like brain surgery, but that's
> always a problem.
>
> Anything you know or use that is reliable that you can recommend would
> be very much appreciated.
>
> I am trying to keep it simple, so using base tools in OpenBSD is a must,
> no proprietary shit or Windows crap like I found tonnes of them. I have
> NO Windows systems for 20+ years already and I am sure hell not going to
> install any either. I try to keep it simple. Even snmp reading is find.
> Simpler the better. I can grab the reading and save to a database to
> graph later and what not. I got two self standing units in the pass,
> nice but they get hacked and not useful obviously, so add-on to OpenBSD
> is better to me. I trust that way more then all the self standing units,
> records proving it...
>
> If that's no interest for the list fell free to reply off line as well,
> but I guess some might like to know too.
>
> Thanks in advance for any suggestions...
>
> Daniel
>
>

Re: Viewport for man.openbsd.org -- readability on phones

[Base Pr1me]

Also great for when you need reading material in the restroom.

On Tue, May 15, 2018 at 4:34 PM, Marc Espie  wrote:

> On Wed, May 16, 2018 at 12:26:10AM +0200, Solene Rapenne wrote:
> >
> > x...@dr.com writes:
> >
> > > The "viewport" meta tag significantly improves readability and
> > > usability on my phone when I add it to http://man.openbsd.org pages:
> >
> > See no offence here, I wonder what is the context leading to read man
> > pages on a phone?
>
> Happened just monday, got students checking some stuff about some system
> functions and showing the documentation to me on their phone during recess.
>
> In that specific case, it was more practical for them than lugging the
> laptop
> outside.
>
>

Re: Buying new laptop, looking for feedback

[Base Pr1me]

OpenBSD is brilliant on the T470s. No issues here.

OpenBSD 6.3-current (GENERIC.MP) #0: Mon May 14 14:29:23 MDT 2018
basepr...@stef.traceyemery.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 25491316736 (24310MB)
avail mem = 24710721536 (23565MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6f096000 (62 entries)
bios0: vendor LENOVO version "N1WET42W (1.21 )" date 12/14/2017
bios0: LENOVO 20HFCTO1WW
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT BOOT 
BATB SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) 
RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) RP09(S4) RP10(S4) RP11(S4) RP12(S4) 
RP13(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2694.92 MHz
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,SMX,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 23MHz
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) i7-7600U CPU @ 2.80GHz, 2693.72 MHz
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,SMX,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2693.72 MHz
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,SMX,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2693.72 MHz
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,SMX,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 58 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiprt5 at acpi0: bus -1 (RP05)
acpiprt6 at acpi0: bus -1 (RP06)
acpiprt7 at acpi0: bus -1 (RP07)
acpiprt8 at acpi0: bus -1 (RP08)
acpiprt9 at acpi0: bus 60 (RP09)
acpiprt10 at acpi0: bus -1 (RP10)
acpiprt11 at acpi0: bus -1 (RP11)
acpiprt12 at acpi0: bus -1 (RP12)
acpiprt13 at acpi0: bus -1 (RP13)
acpiprt14 at acpi0: bus -1 (RP14)
acpiprt15 at acpi0: bus -1 (RP15)
acpiprt16 at acpi0: bus -1 (RP16)
acpiprt17 at acpi0: bus -1 (RP17)
acpiprt18 at acpi0: bus -1 (RP18)
acpiprt19 at acpi0: bus -1 (RP19)
acpiprt20 at acpi0: bus -1 (RP20)
acpiprt21 at acpi0: bus -1 (RP21)
acpiprt22 at acpi0: bus -1 (RP22)
acpiprt23 at acpi0: bus -1 (RP23)
acpiprt24 at acpi0: bus -1 (RP24)
acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), 

Re: PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Thanks for the input! I greatly appreciate your time.

However, in a last ditch effort -- as you were typing and sending your
email --, I solved the problem. I was completely barking up the wrong tree
... sigh.

The issue was an old BIOS in the server. Once I updated the server BIOS,
the softraid hang went away!

You've given me fun things to look in to in the future, however! The more
you know, right?

Regards,
Tracey

On Tue, Apr 24, 2018 at 4:24 PM, IL Ka  wrote:

> >>  Or, is there a gdb method of booting the kernel?
>
> Short answer:
> http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-
> debugging-td335833.html
>
> Long answer:
> /dev/kmem (kmem(4)) could be used to access kernel memory.
> gdb has special target (kvm) that uses it to debug bsd kernels   (
> https://sourceware.org/gdb//onlinedocs/gdb/BSD-libkvm-Interface.html)
>
> so, we need 2 things here:
> 1) Access to /dev/kmem is disabled by default (due to securelevel(7)).
> We need to enable it with "kern.allowkmem=1" in /etc/sysctl.conf
> Or we can switch to insecure level (echo "sysctl kernl.securelevel=-1 >
> /etc/rc.securelevel")
> Make sure to reboot before it.
>
> Never set these values for production system!!
>
> 2) Kernel with debug symbols
> You can build your kernel (man config).
> As last step in "compile" folder you will have /bsd (stripped) and
> /bsd.gdb (symbolized)
>
> Then, copy /bsd.gdb to root, reboot and boot it:
> boot> boot hd0a:/bsd.gdb
>
> I think we should have article about it in FAQ:)
>
>

Re: PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Well I was able to get SR_DEBUG working with the attached diff.

I have tracked the hang down to the open device call on line 1038 `error =
VOP_OPEN(vn, FREAD, NOCRED, curproc);` in the sr_meta_native_bootprobe
function of /usr/src/sys/dev/softraid.c.

Now that I'm completely out of my depth, can anyone suggest a method for
getting the kernel to panic to ddb to get a trace or something, instead of
just freezing? Or, is there a gdb method of booting the kernel?

I'm running of trails to follow.

Thanks for any suggestions.

On Fri, Apr 20, 2018 at 2:37 PM, Base Pr1me <tlemery5...@gmail.com> wrote:

> Sorry, I put the hang position in the wrong place on the first email:
>
> scsibus6 at vscsi0: 256 targets <--- not here! sorry
> softraid0 at root
> scsibus7 at softraid0: 256 targets <- here is where the system hangs
> when virtual drives are present
>
> On Fri, Apr 20, 2018 at 2:33 PM, Base Pr1me <tlemery5...@gmail.com> wrote:
>
>> Hello all,
>>
>> I'm having virtual drive problems on a Dell 2900. When no virtual drives
>> are set up in the PERC 6/i controller, the server will not hang. However,
>> when there are virtual drives available on the system, it appears the
>> system is hanging at the probe stage -- I'm just guessing that's what is
>> occurring. The hang occurs on a fully installed kernel and ramdisk kernels.
>> I have a full install on a SATA drive for the testing, currently.
>>
>> I've tried booting with the single processor kernel and even the i386
>> ramdisk kernel. To complete boot, I'm disabling the mfi driver so the PERC
>> 6/i is not configured, or alternatively removing configured virtual drives.
>>
>> I've tried different virtual drive configurations to see if that's the
>> issue, all the way down to a single hdd configured as RAID-0. It hangs
>> regardless of configuration. The hang position in dmesg would be "scsibus7
>> at softraid0: 256 targets" -- see below. That is the last message displayed
>> on the console.
>>
>> I compiled and tried a couple of different kernels with SCSIDEBUG and
>> various SCSIDEBUG options to see if it would report anything before the
>> hang, with no luck. I also tried to see if mfi or softraid would report
>> anything, but I must be missing a compile option to get these working,
>> because the compiler had errors with these options set:
>>
>> option MFI_DEBUG - wanted to see if mfi reported anything
>> option SR_DEBUG - wanted to see of softraid reported anything
>>
>> It's also VERY possible I have the wrong SCSIDEBUG options set. The two I
>> tried were:
>>
>> # i don't understand these options well enough
>> option SCSIDEBUG
>> option SCSIDEBUG_LEVEL=0x0080
>> option SCSIDEBUG_BUSES=0x8
>> option SCSIDEBUG_TARGETS=0x1
>> option SCSIDEBUG_LUN=0x1
>>
>> # hell, let's go for it
>> option SCSIDEBUG
>> option SCSIDEBUG_LEVEL=0x0080
>> option SCSIDEBUG_BUSES=0xff
>> option SCSIDEBUG_TARGETS=0xff
>> option SCSIDEBUG_LUN=0xff
>>
>> I didn't see any differences.
>>
>> Does anyone have any suggestions on further troubleshooting and/or better
>> SCSIDEBUG options? Am I digging in the wrong area? I appreciate any
>> thoughts or suggestions. I'm attaching 3 dmesg's. The first has mfi enabled
>> and no virtual drives configured, the second has mfi disabled, and the
>> third has SCSIDEBUG enabled with mfi disabled, to capture the dmesg.
>>
>> Thanks,
>>
>> Tracey
>>
>> No virtual drives
>> 
>> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 12863209472 (12267MB)
>> avail mem = 12466286592 (11888MB)
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xcfb9c000 (64 entries)
>> bios0: vendor Dell Inc. version "2.0.1" date 10/27/2007
>> bios0: Dell Inc. PowerEdge 2900
>> acpi0 at bios0: rev 2
>> acpi0: sleep states S0 S4 S5
>> acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT EINJ
>> TCPA
>> acpi0: wakeup devices PCI0(S5)
>> 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) Xeon(R) CPU E5410 @ 2.33GHz, 2327.86 MHz
>> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,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,
>> DCA

Re: PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Sorry, I put the hang position in the wrong place on the first email:

scsibus6 at vscsi0: 256 targets <--- not here! sorry
softraid0 at root
scsibus7 at softraid0: 256 targets <- here is where the system hangs
when virtual drives are present

On Fri, Apr 20, 2018 at 2:33 PM, Base Pr1me <tlemery5...@gmail.com> wrote:

> Hello all,
>
> I'm having virtual drive problems on a Dell 2900. When no virtual drives
> are set up in the PERC 6/i controller, the server will not hang. However,
> when there are virtual drives available on the system, it appears the
> system is hanging at the probe stage -- I'm just guessing that's what is
> occurring. The hang occurs on a fully installed kernel and ramdisk kernels.
> I have a full install on a SATA drive for the testing, currently.
>
> I've tried booting with the single processor kernel and even the i386
> ramdisk kernel. To complete boot, I'm disabling the mfi driver so the PERC
> 6/i is not configured, or alternatively removing configured virtual drives.
>
> I've tried different virtual drive configurations to see if that's the
> issue, all the way down to a single hdd configured as RAID-0. It hangs
> regardless of configuration. The hang position in dmesg would be "scsibus7
> at softraid0: 256 targets" -- see below. That is the last message displayed
> on the console.
>
> I compiled and tried a couple of different kernels with SCSIDEBUG and
> various SCSIDEBUG options to see if it would report anything before the
> hang, with no luck. I also tried to see if mfi or softraid would report
> anything, but I must be missing a compile option to get these working,
> because the compiler had errors with these options set:
>
> option MFI_DEBUG - wanted to see if mfi reported anything
> option SR_DEBUG - wanted to see of softraid reported anything
>
> It's also VERY possible I have the wrong SCSIDEBUG options set. The two I
> tried were:
>
> # i don't understand these options well enough
> option SCSIDEBUG
> option SCSIDEBUG_LEVEL=0x0080
> option SCSIDEBUG_BUSES=0x8
> option SCSIDEBUG_TARGETS=0x1
> option SCSIDEBUG_LUN=0x1
>
> # hell, let's go for it
> option SCSIDEBUG
> option SCSIDEBUG_LEVEL=0x0080
> option SCSIDEBUG_BUSES=0xff
> option SCSIDEBUG_TARGETS=0xff
> option SCSIDEBUG_LUN=0xff
>
> I didn't see any differences.
>
> Does anyone have any suggestions on further troubleshooting and/or better
> SCSIDEBUG options? Am I digging in the wrong area? I appreciate any
> thoughts or suggestions. I'm attaching 3 dmesg's. The first has mfi enabled
> and no virtual drives configured, the second has mfi disabled, and the
> third has SCSIDEBUG enabled with mfi disabled, to capture the dmesg.
>
> Thanks,
>
> Tracey
>
> No virtual drives
> 
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 12863209472 (12267MB)
> avail mem = 12466286592 (11888MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xcfb9c000 (64 entries)
> bios0: vendor Dell Inc. version "2.0.1" date 10/27/2007
> bios0: Dell Inc. PowerEdge 2900
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S4 S5
> acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT EINJ
> TCPA
> acpi0: wakeup devices PCI0(S5)
> 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) Xeon(R) CPU E5410 @ 2.33GHz, 2327.86 MHz
> 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,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
> cpu0: 6MB 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 332MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.51 MHz
> 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,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
> cpu1: 6MB 64b/line 16-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.53 MHz
> 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,
> 

PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Hello all,

I'm having virtual drive problems on a Dell 2900. When no virtual drives
are set up in the PERC 6/i controller, the server will not hang. However,
when there are virtual drives available on the system, it appears the
system is hanging at the probe stage -- I'm just guessing that's what is
occurring. The hang occurs on a fully installed kernel and ramdisk kernels.
I have a full install on a SATA drive for the testing, currently.

I've tried booting with the single processor kernel and even the i386
ramdisk kernel. To complete boot, I'm disabling the mfi driver so the PERC
6/i is not configured, or alternatively removing configured virtual drives.

I've tried different virtual drive configurations to see if that's the
issue, all the way down to a single hdd configured as RAID-0. It hangs
regardless of configuration. The hang position in dmesg would be "scsibus7
at softraid0: 256 targets" -- see below. That is the last message displayed
on the console.

I compiled and tried a couple of different kernels with SCSIDEBUG and
various SCSIDEBUG options to see if it would report anything before the
hang, with no luck. I also tried to see if mfi or softraid would report
anything, but I must be missing a compile option to get these working,
because the compiler had errors with these options set:

option MFI_DEBUG - wanted to see if mfi reported anything
option SR_DEBUG - wanted to see of softraid reported anything

It's also VERY possible I have the wrong SCSIDEBUG options set. The two I
tried were:

# i don't understand these options well enough
option SCSIDEBUG
option SCSIDEBUG_LEVEL=0x0080
option SCSIDEBUG_BUSES=0x8
option SCSIDEBUG_TARGETS=0x1
option SCSIDEBUG_LUN=0x1

# hell, let's go for it
option SCSIDEBUG
option SCSIDEBUG_LEVEL=0x0080
option SCSIDEBUG_BUSES=0xff
option SCSIDEBUG_TARGETS=0xff
option SCSIDEBUG_LUN=0xff

I didn't see any differences.

Does anyone have any suggestions on further troubleshooting and/or better
SCSIDEBUG options? Am I digging in the wrong area? I appreciate any
thoughts or suggestions. I'm attaching 3 dmesg's. The first has mfi enabled
and no virtual drives configured, the second has mfi disabled, and the
third has SCSIDEBUG enabled with mfi disabled, to capture the dmesg.

Thanks,

Tracey

No virtual drives

OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 12863209472 (12267MB)
avail mem = 12466286592 (11888MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xcfb9c000 (64 entries)
bios0: vendor Dell Inc. version "2.0.1" date 10/27/2007
bios0: Dell Inc. PowerEdge 2900
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT EINJ
TCPA
acpi0: wakeup devices PCI0(S5)
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) Xeon(R) CPU E5410 @ 2.33GHz, 2327.86 MHz
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,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 6MB 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 332MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.51 MHz
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,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 6MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.53 MHz
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu2: 6MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.51 MHz
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu3: 6MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
, remapped to apid 4
ioapic1 at mainbus0: apid 5 pa 0xfec8, version 20, 24 pins
, remapped to apid 5
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)

Re: Beg for Atheros wifi driver

[Base Pr1me]

/0x0020
>   0x0018: BAR empty ()
>   0x001c: BAR empty ()
>   0x0020: BAR empty ()
>   0x0024: BAR empty ()
>   0x0028: Cardbus CIS: 
>   0x002c: Subsystem Vendor ID: 11ad Product ID: 0807
>   0x0030: Expansion ROM Base Address: 
>   0x0038: 
>   0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
>   0x0040: Capability 0x01: Power Management
>   State: D0
>   0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
>   0x0070: Capability 0x10: PCI Express
>   Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
>   0x0100: Enhanced Capability 0x01: Advanced Error Reporting
>   0x0148: Enhanced Capability 0x02: Virtual Channel Capability
>   0x0168: Enhanced Capability 0x03: Device Serial Number
>   0x0178: Enhanced Capability 0x18: Latency Tolerance Reporting
>   0x0180: Enhanced Capability 0x1e: L1 PM
>  3:0:0: ATI unknown
>   0x: Vendor ID: 1002 Product ID: 699f
>   0x0004: Command: 0007 Status: 0010
>   0x0008: Class: 03 Subclass: 80 Interface: 00 Revision: c0
>   0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
>   0x0010: BAR mem prefetchable 64bit addr: 0xc000/0x1000
>   0x0018: BAR mem prefetchable 64bit addr: 0xd000/0x0020
>   0x0020: BAR io addr: 0x2000/0x0100
>   0x0024: BAR mem 32bit addr: 0xd140/0x0004
>   0x0028: Cardbus CIS: 
>   0x002c: Subsystem Vendor ID: 1025 Product ID: 1211
>   0x0030: Expansion ROM Base Address: 
>   0x0038: 
>   0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
>   0x0048: Capability 0x09: Vendor Specific
>   0x0050: Capability 0x01: Power Management
>   State: D0
>   0x0058: Capability 0x10: PCI Express
>   Link Speed: 2.5 / 8.0 GT/s Link Width: x8 / x8
>   0x0100: Enhanced Capability 0x0b: Vendor-Specific
>   0x0270: Enhanced Capability 0x19: Secondary PCIe Capability
>   0x0320: Enhanced Capability 0x18: Latency Tolerance Reporting
>   0x00a0: Capability 0x05: Message Signalled Interrupts (MSI)
>
>
>
> 2018-04-17 11:03 GMT-05:00 Base Pr1me <tlemery5...@gmail.com>:
>
>> Verbose output with pcidump -v would give you the vendor and product ids,
>> which would give you more information about the "unknown" device.
>>
>> On Tue, Apr 17, 2018 at 9:40 AM, Manuel Solis <lossoli...@gmail.com>
>> wrote:
>>
>>> Thank you again,
>>>
>>> As i said, i am ordering the wifi usb adapters that you suggested,
>>> but for the record, this are the outputs from lspci and pcidump
>>>
>>> pcidump
>>> Domain /dev/pci0:
>>>  0:0:0: AMD AMD64 15h Root Complex
>>>  0:1:0: ATI Carrizo
>>>  0:1:1: ATI Radeon HD Audio
>>>  0:2:0: AMD AMD64 15h Host
>>>  0:2:2: AMD AMD64 15h PCIE
>>>  0:2:3: AMD AMD64 15h PCIE
>>>  0:3:0: AMD AMD64 15h Host
>>>  0:3:1: AMD AMD64 15h PCIE
>>>  0:8:0: AMD AMD64 15h PSP 2.0
>>>  0:9:0: AMD AMD64 15h Host
>>>  0:9:2: AMD AMD64 15h HD Audio
>>>  0:16:0: AMD Carrizo xHCI
>>>  0:17:0: AMD Carrizo AHCI
>>>  0:18:0: AMD Carrizo USB2
>>>  0:20:0: AMD Carrizo SMBus
>>>  0:20:3: AMD Carrizo LPC
>>>  0:24:0: AMD AMD64 15h Link Cfg
>>>  0:24:1: AMD AMD64 15h Address Map
>>>  0:24:2: AMD AMD64 15h DRAM Cfg
>>>  0:24:3: AMD AMD64 15h Misc Cfg
>>>  0:24:4: AMD AMD64 15h CPU Power
>>>  0:24:5: AMD AMD64 15h Misc Cfg
>>>  1:0:0: Realtek RTL8411B Card Reader
>>>  1:0:1: Realtek 8168
>>>  2:0:0: Atheros unknown
>>>  3:0:0: ATI unknown
>>>
>>>
>>> lspci from pciutils
>>>
>>> 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1576
>>> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> Carrizo (rev cc)
>>> 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini
>>> HDMI/DP
>>> Audio
>>> 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
>>> 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
>>> 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
>>> 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
>>> 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
>>> 00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device
>>> 1578
>>> 00:09.0 Host bridge: Advanc

Re: Beg for Atheros wifi driver

[Base Pr1me]

Verbose output with pcidump -v would give you the vendor and product ids,
which would give you more information about the "unknown" device.

On Tue, Apr 17, 2018 at 9:40 AM, Manuel Solis  wrote:

> Thank you again,
>
> As i said, i am ordering the wifi usb adapters that you suggested,
> but for the record, this are the outputs from lspci and pcidump
>
> pcidump
> Domain /dev/pci0:
>  0:0:0: AMD AMD64 15h Root Complex
>  0:1:0: ATI Carrizo
>  0:1:1: ATI Radeon HD Audio
>  0:2:0: AMD AMD64 15h Host
>  0:2:2: AMD AMD64 15h PCIE
>  0:2:3: AMD AMD64 15h PCIE
>  0:3:0: AMD AMD64 15h Host
>  0:3:1: AMD AMD64 15h PCIE
>  0:8:0: AMD AMD64 15h PSP 2.0
>  0:9:0: AMD AMD64 15h Host
>  0:9:2: AMD AMD64 15h HD Audio
>  0:16:0: AMD Carrizo xHCI
>  0:17:0: AMD Carrizo AHCI
>  0:18:0: AMD Carrizo USB2
>  0:20:0: AMD Carrizo SMBus
>  0:20:3: AMD Carrizo LPC
>  0:24:0: AMD AMD64 15h Link Cfg
>  0:24:1: AMD AMD64 15h Address Map
>  0:24:2: AMD AMD64 15h DRAM Cfg
>  0:24:3: AMD AMD64 15h Misc Cfg
>  0:24:4: AMD AMD64 15h CPU Power
>  0:24:5: AMD AMD64 15h Misc Cfg
>  1:0:0: Realtek RTL8411B Card Reader
>  1:0:1: Realtek 8168
>  2:0:0: Atheros unknown
>  3:0:0: ATI unknown
>
>
> lspci from pciutils
>
> 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1576
> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Carrizo (rev cc)
> 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP
> Audio
> 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
> 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
> 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
> 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
> 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
> 00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device
> 1578
> 00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157d
> 00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Device 157a
> 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI
> Controller (rev 20)
> 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA
> Controller [AHCI mode] (rev 49)
> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
> Controller (rev 49)
> 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev
> 4a)
> 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev
> 11)
> 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1570
> 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1571
> 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1572
> 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1573
> 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1574
> 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1575
> 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B
> PCI Express Card Reader (rev 01)
> 01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 32)
> 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO
> [Radeon RX 550] (rev c0)
>
>
>
> Have a great day,
>
>
>
>
> 2018-04-16 7:27 GMT-05:00 Paul de Weerd :
>
> > On Mon, Apr 16, 2018 at 01:05:37PM +1000, Stuart Longland wrote:
> > | On 16/04/18 08:08, Manuel Solis wrote:
> > | > Sorry for that, i havent figure it out, maybe i should reinstall
> > windows to
> > | > get the info
> > | >  My bad.
> > |
> > | Does `lspci` work on OpenBSD?  Failing that, boot a Linux LiveCD and
> run
> > | `lspci` there, it'll tell you the chipset; `dmesg` might give you some
> > | more clues.
> >
> > No need to run Linux to run lspci, it's available through the pciutils
> > packages (doas pkg_add pciutils).  But base OpenBSD has pcidump(8),
> > which gives quite similar info.
> >
> > | `lsusb` if it's a USB wifi chip.
> >
> > Or try usbdevs(8), also in base OpenBSD.
> >
> > Your operating system of choice comes with a pretty complete toolset.
> >
> > Paul 'WEiRD' de Weerd
> >
> > --
> > >[<++>-]<+++.>+++[<-->-]<.>+++[<+
> > +++>-]<.>++[<>-]<+.--.[-]
> >  http://www.weirdnet.nl/
> >
> >
>
>
> --
> Lic. Manuel Solís Vázquez
>

Re: door opening sensor HW for OpenBSD?

[Base Pr1me]

Robert, I'm a huge fan of over engineering. Thanks for the chuckle!!

On Sat, Mar 24, 2018, 15:52 Robert  wrote:

> On Sat, 24 Mar 2018 22:32:02 +0100
> "Hess THR"  wrote:
> > Can you please recommend any hardware, that I could plug in to the
> notebook and though I could send a warning mail when the door was moved
> (open/closed).
>
> I can think of so many ways to do this, from boring to insane :)
>
> * Mount a switch on top of the door that gets unpressed when the door
>   opens, and connect to the serial port. Then read the pin status.
> * The same, but mount the switch behind the door so that it gets
>   pressed when the door opens.
> * Use a magnetic switch instead, and read it through the serial port.
> * Put a keyboard behind the door, so that the door presses against a
>   key when it opens. Map the key to a script.
> * Attach a mouse to the door and react on the mouse movement.
> * Attach a GPS sensor to the door and measure movements.
> * Attach a USB barometer and detect the air pressure diff when the door
>   opens.
> * Attach a USB gyroscope to the door. Detect movement.
> * Attach a USB light sensor (Arduino?) and detect movement.
> * Put an RFID tag on the door, and attach an RFID reader, to detect
>   when the tag approaches the reader.
> * Attach the laptop to the door and use the built-in gyroscope (if
>   available).
> * Same, but use the gyroscope from the HD. Might require firmware
>   hacking.
> * Don't oil the door and evaluate the microphone input.
> * Attach any USB device, but route the 5V line through a switch
>   attached to the door. Detect when the device attaches.
> * Mount the laptop behind the door so that the door opens/closes the
>   laptop lid. Detect wake/sleep state.
> * Fix your credit card to the door and have it move through a card
>   reader when the door opens. Check account balance through script.
>
> Send pix!
>
> regards,
> Robert
>
>

Re: ESP8266 Non-OS SDK

[Base Pr1me]

Thanks for the info. I haven't dove into the 32 world, yet. Glad to hear
someone is working in that direction.
Take care.

On Fri, Mar 23, 2018 at 6:56 AM, Eric Huiban <gro...@grompf.net> wrote:

> Base Pr1me wrote:
>
>> Has anyone played around with compiling the Espressif SDK for their chips?
>> Just curious.
>>
>> Thanks,
>> Tracey
>>
>>
> I'm beginning to modify the SDK for Espressif ESP32 step by step when time
> allows. It's full of linuxism and very gnuish, but if i can do some mod in
> their stuff everybody can. I'm a very small player in this kind of arena. ;)
>
> I'm know at the step where the SDK is looking for python and does not find
> it on BSD (all versions are here because of pkg dependancies management...).
>
> So... it is slow (on my  x230 laptop each compilation of the toolchain now
> lasts 50mn before ending with a new error) and quite boring. However it
> apparently can be done up to now. But i'm not finished with this stuff and
> cannot say it is definitively OK.
>
> Regards
>

ESP8266 Non-OS SDK

[Base Pr1me]

Has anyone played around with compiling the Espressif SDK for their chips?
Just curious.

Thanks,
Tracey

Re: httpd howto redirect port 80 to 443 in vm

[Base Pr1me]

Crap, naturally, don't forget "tls" in front of "port 443". Apologies.

On Fri, Mar 2, 2018 at 7:54 AM, Base Pr1me <tlemery5...@gmail.com> wrote:

> I should mention for clarification there are two server sections. The
> second listens on 443 and does the tls and location heavy lifting.
> So, there are two:
>
> server "example.com" {
> listen on $ext_if port 80
> alias "www.example.com"
> block return 301 "https://example.com/;
> }
> server "example.com" {
> listen on $ext_if port 443
> alias "www.example.com"
>#rest of stuff
> }
>
> On Fri, Mar 2, 2018 at 7:51 AM, Base Pr1me <tlemery5...@gmail.com> wrote:
>
>> I simply have a block in my httpd.conf for my redirects:
>>
>> server "example.com" {
>> listen on $ext_if port 80
>> alias "www.example.com"
>> block return 301 "https://example.com/;
>> }
>>
>> On Fri, Mar 2, 2018 at 7:40 AM, Solène Rapenne <sol...@perso.pw> wrote:
>>
>>> Le 2018-03-02 15:33, Matt M a écrit :
>>>
>>>> Why not use a .htaccess redirect?
>>>>
>>>> https://www.sslshopper.com/apache-redirect-http-to-https.html
>>>>
>>>
>>> .htaccess file is a feature of Apache web server while we are
>>> talking about httpd.
>>>
>>>
>>
>

Re: httpd howto redirect port 80 to 443 in vm

[Base Pr1me]

I should mention for clarification there are two server sections. The
second listens on 443 and does the tls and location heavy lifting.
So, there are two:

server "example.com" {
listen on $ext_if port 80
alias "www.example.com"
block return 301 "https://example.com/;
}
server "example.com" {
listen on $ext_if port 443
alias "www.example.com"
   #rest of stuff
}

On Fri, Mar 2, 2018 at 7:51 AM, Base Pr1me <tlemery5...@gmail.com> wrote:

> I simply have a block in my httpd.conf for my redirects:
>
> server "example.com" {
> listen on $ext_if port 80
> alias "www.example.com"
> block return 301 "https://example.com/;
> }
>
> On Fri, Mar 2, 2018 at 7:40 AM, Solène Rapenne <sol...@perso.pw> wrote:
>
>> Le 2018-03-02 15:33, Matt M a écrit :
>>
>>> Why not use a .htaccess redirect?
>>>
>>> https://www.sslshopper.com/apache-redirect-http-to-https.html
>>>
>>
>> .htaccess file is a feature of Apache web server while we are
>> talking about httpd.
>>
>>
>

Re: httpd howto redirect port 80 to 443 in vm

[Base Pr1me]

I simply have a block in my httpd.conf for my redirects:

server "example.com" {
listen on $ext_if port 80
alias "www.example.com"
block return 301 "https://example.com/;
}

On Fri, Mar 2, 2018 at 7:40 AM, Solène Rapenne  wrote:

> Le 2018-03-02 15:33, Matt M a écrit :
>
>> Why not use a .htaccess redirect?
>>
>> https://www.sslshopper.com/apache-redirect-http-to-https.html
>>
>
> .htaccess file is a feature of Apache web server while we are
> talking about httpd.
>
>

Re: Help questions

[Base Pr1me]

No flame from here, but, you did receive a very valuable reply from Michael
Hekeler regarding your emails. The history of the reply is located here:

https://marc.info/?l=openbsd-misc=151575921608315=2

On Thu, Feb 22, 2018 at 2:36 PM, leroy jordan 
wrote:

> I'm new to oBSD. However, I do wont to learn so i can contribute. The
> skills; that I have so far has came from the books that are suggested from
> the Open website. Which are useful in getting me started. but  they don't
> have all the answers and when I post o misc no one seems to reply I know
> this is not kindergarten. you're not going to hold my hand however how will
> I ever learn.
> If no one reaches out I use the emails as a teaching tool so you can bash
> me all you want but I'm not going to give up I'm all in.
>  maybe I'm just ranting.
>
> Thanks Leroy Jordan
>

Re: Jan 20 snapshot

[Base Pr1me]

.0bda0307201006010301
umass1 at uhub13 port 3 configuration 1 interface 0 "Seagate Expansion
Desk" rev 3.00/1.00 addr 9
umass1: using SCSI over Bulk-Only
scsibus3 at umass1: 2 targets, initiator 0
sd7 at scsibus3 targ 1 lun 0: <Seagate, Expansion Desk, 9401> SCSI4
0/direct fixed
sd7: 3815447MB, 512 bytes/sector, 7814037167 sectors
uhub14 at uhub0 port 3 configuration 1 interface 0 "GenesysLogic USB3.0
Hub" rev 3.00/92.16 addr 10
umass2 at uhub14 port 1 configuration 1 interface 0 "Realtek USB3.0 Card
Reader" rev 3.00/1.63 addr 11
umass2: using SCSI over Bulk-Only
scsibus4 at umass2: 2 targets, initiator 0
sd8 at scsibus4 targ 1 lun 0: <Generic-, SD/MMC/MS/MSPRO, 1.00> SCSI4
0/direct removable serial.0bda0307201006010301
uhub15 at uhub1 port 1 configuration 1 interface 0 "Standard Microsystems
Hub" rev 2.00/0.01 addr 2
uftdi0 at uhub15 port 1 configuration 1 interface 0 "FTDI FT232R USB UART"
rev 2.00/6.00 addr 3
ucom0 at uftdi0 portno 1
uvideo0 at uhub15 port 2 configuration 1 interface 0 "Logitech Webcam C310"
rev 2.00/0.10 addr 4
video0 at uvideo0
uaudio0 at uhub15 port 2 configuration 1 interface 2 "Logitech Webcam C310"
rev 2.00/0.10 addr 4
uaudio0: audio descriptors make no sense, error=4
ugen0 at uhub15 port 2 configuration 1 "Logitech Webcam C310" rev 2.00/0.10
addr 4
ugen1 at uhub15 port 3 "Broadcom Corp BCM20702A0" rev 2.00/1.12 addr 5
uhidev0 at uhub15 port 4 configuration 1 interface 0 "Logitech USB
Receiver" rev 2.00/12.01 addr 6
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
uhidev1 at uhub15 port 4 configuration 1 interface 1 "Logitech USB
Receiver" rev 2.00/12.01 addr 6
uhidev1: iclass 3/1, 8 report ids
ums0 at uhidev1 reportid 2: 16 buttons, Z and W dir
wsmouse0 at ums0 mux 0
uhid0 at uhidev1 reportid 3: input=4, output=0, feature=0
uhid1 at uhidev1 reportid 4: input=1, output=0, feature=0
uhid2 at uhidev1 reportid 8: input=1, output=0, feature=0
uhidev2 at uhub15 port 4 configuration 1 interface 2 "Logitech USB
Receiver" rev 2.00/12.01 addr 6
uhidev2: iclass 3/0, 33 report ids
uhid3 at uhidev2 reportid 16: input=6, output=6, feature=0
uhid4 at uhidev2 reportid 17: input=19, output=19, feature=0
uhid5 at uhidev2 reportid 32: input=14, output=14, feature=0
uhid6 at uhidev2 reportid 33: input=31, output=31, feature=0
ugen2 at uhub1 port 2 "Brother HL-2240 series" rev 2.00/1.00 addr 7
uhub16 at uhub1 port 5 configuration 1 interface 0 "Genesys Logic USB2.0
Hub" rev 2.00/9.01 addr 8
umidi0 at uhub7 port 1 configuration 1 interface 1 "M-Audio MIDISPORT 2x2
Anniv" rev 1.10/1.04 addr 2
umidi0: (genuine USB-MIDI)
umidi0: out=2, in=2
midi0 at umidi0: 
midi1 at umidi0: 
ugen3 at uhub7 port 1 configuration 1 "M-Audio MIDISPORT 2x2 Anniv" rev
1.10/1.04 addr 2
ugen4 at uhub7 port 3 "iLok iLok" rev 1.10/0.10 addr 3
vscsi0 at root
scsibus5 at vscsi0: 256 targets
softraid0 at root
scsibus6 at softraid0: 256 targets
sd9 at scsibus6 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
sd9: 228935MB, 512 bytes/sector, 468860513 sectors
root on sd9a (0036a72db8823cbe.a) swap on sd9b dump on sd9b
radeondrm0: 1024x768, 32bpp
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0
wskbd1: connecting to wsdisplay0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
sd10 at scsibus6 targ 2 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct
fixed
sd10: 810818MB, 512 bytes/sector, 1660556159 sectors

On Sun, Jan 21, 2018 at 5:12 AM, Base Pr1me <tlemery5...@gmail.com> wrote:

> Running on this 20180108 kernel now. Here's the dmesg. Seems to be running
> stable now. Normally, I'd be completely hung at this point. Hopefully, I
> haven't screwed all of this up with my intoxication, but, I'm too stubborn
> to not keep a system running! ;)
>
>
> On 1/21/18 4:10 PM, Stuart Henderson wrote:
>
>> On 2018-01-21, Base Pr1me <tlemery5...@gmail.com> wrote:
>>
>>> I'll try. Not sure I can keep it running long enough to get dmesg lol.
>>> Last
>>> upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
>>> and get dmesg this week, when I have more time ... Or wait until newer
>>> snaps and try again.
>>>
>>> On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote:
>>>
>>> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
>>>>
>>>>> Anyone else's system hanging randomly after upgrading to yesterday's
>>>>> snapshot? This isn't a panic that drops to ddb. It's just freezing with
>>>>>
>>>> no
>>>>
>>>>> response to anything.
>>>>>
>>>> A full dmesg would be welcome, and having the date of your previous
>>>> version too.
>>>>
>>>> thanks.
>>>> --
>>>> Sebastien Marie
>>>>
>>>> Moving back to a slightly older kernel and getting dmesg would be
>> useful.
>>
>> If you have an working bsd.rd on the disk you can drop to a shell and
>> mount the filesystems, save a copy of /var/run/dmesg.boot (interested
>> to see any microcode-update related lines from the newer one).
>>
>> Here's a saved snapshot from a couple of weeks ago you could try:
>> https://junkpile.org/bsd.mp.20180108.gz
>>
>> Hopefully that will be stable and you can then send a dmesg showing what's
>> in the system.
>>
>>
>>

Re: Jan 20 snapshot

[Base Pr1me]

Running on this 20180108 kernel now. Here's the dmesg. Seems to be running 
stable now. Normally, I'd be completely hung at this point. Hopefully, I haven't 
screwed all of this up with my intoxication, but, I'm too stubborn to not keep a 
system running! ;)



On 1/21/18 4:10 PM, Stuart Henderson wrote:

On 2018-01-21, Base Pr1me <tlemery5...@gmail.com> wrote:

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote:


On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with

no

response to anything.

A full dmesg would be welcome, and having the date of your previous
version too.

thanks.
--
Sebastien Marie


Moving back to a slightly older kernel and getting dmesg would be useful.

If you have an working bsd.rd on the disk you can drop to a shell and
mount the filesystems, save a copy of /var/run/dmesg.boot (interested
to see any microcode-update related lines from the newer one).

Here's a saved snapshot from a couple of weeks ago you could try:
https://junkpile.org/bsd.mp.20180108.gz

Hopefully that will be stable and you can then send a dmesg showing what's
in the system.


OpenBSD 6.2-current (GENERIC.MP) #333: Sun Jan  7 09:13:00 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16951357440 (16166MB)
avail mem = 16430698496 (15669MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries)
bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014
bios0: Gigabyte Technology Co., Ltd. 970A-DS3P
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS
acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) 
USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) 
PE23(S4) PC02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.57 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
acpitimer0: recalibrated TSC frequency 3516153538 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.14 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 19 (application processor)
cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE

Re: Jan 20 snapshot

[Base Pr1me]

Got it ... I hope ... "Gin"ny and all

On 1/21/18 4:10 PM, Stuart Henderson wrote:

On 2018-01-21, Base Pr1me <tlemery5...@gmail.com> wrote:

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote:


On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with

no

response to anything.

A full dmesg would be welcome, and having the date of your previous
version too.

thanks.
--
Sebastien Marie


Moving back to a slightly older kernel and getting dmesg would be useful.

If you have an working bsd.rd on the disk you can drop to a shell and
mount the filesystems, save a copy of /var/run/dmesg.boot (interested
to see any microcode-update related lines from the newer one).

Here's a saved snapshot from a couple of weeks ago you could try:
https://junkpile.org/bsd.mp.20180108.gz

Hopefully that will be stable and you can then send a dmesg showing what's
in the system.


OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16951357440 (16166MB)
avail mem = 16430669824 (15669MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries)
bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014
bios0: Gigabyte Technology Co., Ltd. 970A-DS3P
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS
acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) 
USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) 
PE23(S4) PC02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.53 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
acpitimer0: recalibrated TSC frequency 3516127432 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 19 (application processor)
cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu3: 64KB 64b

Re: Jan 20 snapshot

[Base Pr1me]

Cool, thanks. I'll check this out this week. Much gratitude. I'm far too
'ginned' up at the moment. ;)

On Jan 21, 2018 16:13, "Stuart Henderson" <s...@spacehopper.org> wrote:

> On 2018-01-21, Base Pr1me <tlemery5...@gmail.com> wrote:
> > I'll try. Not sure I can keep it running long enough to get dmesg lol.
> Last
> > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
> > and get dmesg this week, when I have more time ... Or wait until newer
> > snaps and try again.
> >
> > On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote:
> >
> >> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> >> > Anyone else's system hanging randomly after upgrading to yesterday's
> >> > snapshot? This isn't a panic that drops to ddb. It's just freezing
> with
> >> no
> >> > response to anything.
> >>
> >> A full dmesg would be welcome, and having the date of your previous
> >> version too.
> >>
> >> thanks.
> >> --
> >> Sebastien Marie
> >>
> >
>
> Moving back to a slightly older kernel and getting dmesg would be useful.
>
> If you have an working bsd.rd on the disk you can drop to a shell and
> mount the filesystems, save a copy of /var/run/dmesg.boot (interested
> to see any microcode-update related lines from the newer one).
>
> Here's a saved snapshot from a couple of weeks ago you could try:
> https://junkpile.org/bsd.mp.20180108.gz
>
> Hopefully that will be stable and you can then send a dmesg showing what's
> in the system.
>
>
>

Re: Jan 20 snapshot

[Base Pr1me]

Ok, thanks.

On Jan 21, 2018 11:02, "Sebastien Marie" <sema...@online.fr> wrote:

> On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote:
> > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > > Anyone else's system hanging randomly after upgrading to yesterday's
> > > snapshot? This isn't a panic that drops to ddb. It's just freezing
> with no
> > > response to anything.
> >
> > I haven't notice any problems with:
> > kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55
> MST 2018
>
> I reported a problem (unexpected reboots) with recent snapshots (and not
> reproductible with rebuilt kernel).
>
> I quickly check with binary diffing for changes and snapshots have
> uncommited changes.
>
> It is why I asked for dmesg and previous working snap.
> --
> Sebastien Marie
>

Re: Jan 20 snapshot

[Base Pr1me]

Ty.

On Jan 21, 2018 10:45, "Adam Wolk" <adam.w...@tintagel.pl> wrote:

> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezing with
> no
> > response to anything.
>
> I haven't notice any problems with:
> kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55
> MST 2018
>
> Regards,
> Adam
>

Re: Jan 20 snapshot

[Base Pr1me]

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote:

> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezing with
> no
> > response to anything.
>
> A full dmesg would be welcome, and having the date of your previous
> version too.
>
> thanks.
> --
> Sebastien Marie
>

Jan 20 snapshot

[Base Pr1me]

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with no
response to anything.

Re: Flatbed scanner that works well with OpenBSD?

[Base Pr1me]

Did you give your userland user/group permissions to use the uhub/ugen
device?

On Fri, Jan 19, 2018 at 9:59 AM, Anthony J. Bentley 
wrote:

> Bryan Linton writes:
> > Hello misc@
> >
> > I'm currently looking to purchase a scanner that works well with OpenBSD.
> >
> > I'm aware of the list provided at:
> >
> >   http://www.sane-project.org/sane-mfgs.html
> >
> > but I recently purchased (and returned) a scanner that was listed as
> being
> > fully supported on that list because no matter what I did, I couldn't
> > get it to work right with xsane or scanimage.  Though I purchased it
> used,
> > so it's possible it may have simply been broken from the get-go.
> >
> > Does anyone happen to know of a scanner that is *known* to work well
> > with OpenBSD?
>
> Well, I just bought a CanoScan 9000F MkII specifically because it was
> marked as fully supported on that list, and I can say it does NOT work
> on OpenBSD; scanimage -L detects it just fine but attempting to scan
> gives an I/O error. As a workaround I plugged it into a Linux laptop,
> started saned, and scan seamlessly from OpenBSD with scanimage's network
> support, until I find the time to make a proper bug report.
>
> In the past I used a CanoScan LiDE 20 quite regularly from OpenBSD, but
> that was several years ago.
>
>

Re: Re-compute bsd checksum

[Base Pr1me]

Don't think you can use config to disable ulpt and KARL. Someone will correct me 
if I'm wrong.


On 1/16/18 1:08 PM, Thuban wrote:

I disabled `ulpt` in the kernel using `config` to use an USB-printer.

Now, at reboot, I see "kernel relinking failed" message.
How to recreate the new checksum? I can't igure out where to find this
information.

Any advice?

Regards.

Re: Writing "ones" instead of "zeroes" when wiping disk

[Base Pr1me]

You can adapt my linux bash script for such pointlessly "paranoid"
purposes. I use it to prove to HIPAA auditors just how paranoid I can be,
and it's above NIST requirements in the US.

https://github.com/spoollord/shredder

Would require you to pkg_add pv base64. Or, just adapt the script without
those.

On Thu, Jan 11, 2018 at 8:26 AM, Ingo Schwarze  wrote:

> Hi Andreas,
>
> Andreas Thulin wrote on Thu, Jan 11, 2018 at 02:45:21PM +:
>
> > Again, an ignorant question (as usual):
> > How might I do something similar to
> > # dd if=/dev/one of=/dev/sd0 bs=1M
>
>   jot -cs '' 512 255 255
>
> writes 512 bytes with all bits set.  Feel free to use larger numbers
> than 512.  For large numbers, this is certainly slower than dd
> because it uses an explicit loop with some conditionals and one
> printf(3) for each byte.
>
>   perl -e 'print "\xff"x512'
>
> may be faster.  If i needed maximum speed, i'd probably write a two-line
> C program.
>
>   while true; do echo -n "\0377"; done
>
> works for the purist, but will hardly be fast.
>
> Btw., you are asking for "Hello World!", kind of.
> It may be hard to find a program that can't solve your task...  ;)
>
> > as a complement to the usual and well-described
> > # dd if=/dev/zero of=/dev/sd0 bs=1M
> > followed by
> > # dd if=/dev/urandom of=/dev/sd0 bs=1M
> > in order to achieve paranoid disk-wiping?
>
> I have no idea whether or not such paranoia makes sense.
> Maybe, maybe not.
>
> Yours,
>   Ingo
>
>

Re: Community-driven OpenBSD tutorials wiki?

[Base Pr1me]

The Pledge of the Network Admin, from one of those book authors:
http://bsdly.blogspot.com/2011/01/i-will-not-mindlessly-paste-from-howtos.html
:D

On Thu, Jan 4, 2018 at 9:02 AM, Marko Cupać  wrote:

> On Thu, 4 Jan 2018 10:41:19 -0500
> Bryan Harris  wrote:
>
> > My preference is to purchase a book. I have had a good experience with
> > Absolute OpenBSD, Httpd & Relayd, the tarsnap book, and the Book of
> > PF.
> >
> > I would buy a book about OpenSMTPD and also ikev2 but I didn't see
> > any.
> >
> > Just my $0.02, I like books better than online tutorials.
>
> Couldn't agree more. Those are good books.
>
> However, back in a day when I was completely fresh to OpenBSD, I
> preferred to copy/paste someone's working solution, and then discover
> which config line does what, how, and why. That's because I had no
> clue about anything. It was valuable to read how people designed
> solutions to their needs, what combination of software they used etc.
> Only at the later stage I was able to dive into documentation.
>
> I was particularly fond of this set of howtos:
> http://www.kernel-panic.it/openbsd.html
> --
> Before enlightenment - chop wood, draw water.
> After  enlightenment - chop wood, draw water.
>
> Marko Cupać
> https://www.mimar.rs/
>
>

Re: openbsd code coverage

[Base Pr1me]

I only say this because I am extremely intoxicated. Will you please shut
the fuck up?

On Dec 9, 2017 17:08, "Rupert Gallagher"  wrote:

> Fuck you x9p anonymous coward.
>
> Sent from ProtonMail Mobile
>
> On Sat, Dec 9, 2017 at 23:02, x9p  wrote:
>
> > On Sat, December 9, 2017 3:33 pm, Anders Andersson wrote: > On Sat, Dec
> 9, 2017 at 12:46 PM, Rupert Gallagher  > wrote: >> Code Coverage? > > Type
> that into google instead, maybe you will get a better answer. > > Indeed
> redirecting @protonmail.com to /dev/null provides a much more pleasant
> misc@- reading experience, as suggested before. Just saw this email bcz
> of citation. cheers. x9p @protonmail.com>

Re: New default setup for touchpads in X

[Base Pr1me]

Honestly, my issues are minimal in regards to the tap-to-click activating during 
typing. If I'm typing in bed or at a awkward angle exacerbates it, but it's not 
a huge issue. "Edge Zones" might be just the ticket. I always found the 
syndaemon a bit odd, anyway, and had to play with the timing to make it feel 
like it worked correctly.


I'll keep an eye out for your future posts and report any (and then when I went 
to type anomalies, the tap-to-click got me, even though I'm not at an odd angle) 
anomalies. So, parenthetically, edge zones might be the ticket! :D


On 12/5/17 5:23 PM, Ulf Brosziewski wrote:

Up to now, I have only vaguely considered that, and there are
some other things pending.  However, if many users will be
missing that option, my priorities might change ;-)  Would
"edge areas" be an alternative for you?  synaptics(4) has an
option for defining edge zones.  A touch that starts there does
not trigger pointer movement, tapping, and scrolling as long as
it hasn't left the area.  The input driver in wsmouse(4) has a
similar mechanism, what's missing up to now is a decent way to
configure it, but it can be done, and it might be a way to mitigate
the effects of accidental touches.  Of course, whether it could
help in your case depends on your habits.

On 12/06/2017 12:17 AM, Base Pr1me wrote:

Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.

On Tue, Dec 5, 2017 at 3:59 PM, Ulf Brosziewski <ulf.brosziew...@t-online.de

wrote:
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.

X will select ws(4) instead of synaptics(4) as default driver.  In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4).  Touchpad configuration parameters are made available in
wsconsctl(4), see
 https://marc.info/?l=openbsd-misc=150153498920367=2
for some hints (the wsmouse man page is not up to date yet).

Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file.  If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.

Re: New default setup for touchpads in X

[Base Pr1me]

Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.

On Tue, Dec 5, 2017 at 3:59 PM, Ulf Brosziewski  wrote:

> If you're following -current, or if you upgrade your system with the
> next or a future snapshot, please note that the default setup for
> touchpads in X will change.
>
> X will select ws(4) instead of synaptics(4) as default driver.  In a
> configuration with ws, touchpad-specific input processing is done by
> wsmouse(4).  Touchpad configuration parameters are made available in
> wsconsctl(4), see
> https://marc.info/?l=openbsd-misc=150153498920367=2
> for some hints (the wsmouse man page is not up to date yet).
>
> Using synaptics(4) as input driver is still possible, it will require
> a custom xorg.conf file.  If you already have such a file - which
> overrides the default -, please consider giving ws a try, and help
> us by reporting problems if it doesn't work for you.
>
>

Re: pcengines apu boards

[Base Pr1me]

I run 5 apu2 devices with no problems. I don't have any apu3 devices ... yet.

On 11/30/17 3:00 PM, Paul B. Henson wrote:

I was wondering if anybody is successfully running openbsd on pcengines apu
boards? I have one of their APU3 series, specifically a apu3b4 with OpenBSD
6.2 on it but I can't get the USB2 EHCI ports functioning correctly (for one
thing, they don't detect a hot plugged device), I'm not sure if it's an
issue with the ehci driver and the amd ehci chipset or possibly something in
the bios acpi tables. But just as a data point, it would be interesting to
know if the problem is specific to my board or endemic to the design, so if
anyone has an APU series board with fully functional USB2 ports on the ehci
controller, I would much appreciate hearing which board it is, which
specific AMD chipset is driving the controller, and what bios version you
are running (and what OpenBSD version too).

Thanks much.

Re: Hellos from the Lands of Norway.

[Base Pr1me]

second that ...

On Tue, Nov 7, 2017 at 9:47 AM, Christer Solskogen <
christer.solsko...@gmail.com> wrote:

> On Tue, Nov 7, 2017 at 3:55 PM, Ywe Cærlyn  wrote:
>
> > Well I have introduced myself then.
> >
> > Maybe I will write some more posts at a later time.
> >
> >
> I have a suggestion. Don't.
>
> --
> chs
>