Re: pulseaudio RTP Streaming problem on X11 Desktop

[Alexandre Ratchov]

On Wed, May 04, 2016 at 06:58:01PM +0300, freeunix freeunix wrote:
> hi, I use the OpenBSD 5.9 amd64 snapshots.
> and XDM Remote Deskop using is marvelous for OpenBSD.
> 
> Now I have any problem.(I want use audio streaming for firefox.)
> I tried to use pulseaudio. but couldn't work it.
> 

Are both client and server running OpenBSD?  If so, you could use
sndiod instead of pulseaudio to forward audio.  On the system with
the sound card, setup sndiod to use the -L option, for instance
run:

rcctl set sndiod flags -L -

and on all the systems where audio programs run export
the environment variable:

AUDIODEVICE=snd@hostname/0

where hostname is the network address of the system with the sound
card.

-- Alexandre

Re: diff - FAQ5 missing info on updating current source tree

[Theo Buehler]

On Fri, May 06, 2016 at 12:58:33AM -0400, Gabriel Guzman wrote:
> FAQ5 is missing a sentence: 

fixed, thanks.

diff - FAQ5 missing info on updating current source tree

[Gabriel Guzman]

FAQ5 is missing a sentence: 

Index: faq5.html
===
RCS file: /cvs/www/faq/faq5.html,v
retrieving revision 1.267
diff -u -p -u -r1.267 faq5.html
--- faq5.html   1 May 2016 16:59:24 -   1.267
+++ faq5.html   6 May 2016 04:54:43 -
@@ -263,6 +263,8 @@ $ cvs -qd anon...@anoncvs.example.org
 Replace src with the module you want, such as xenocara
 or ports.
 
+Once you have the tree checked out, you can update it at a later time with
+
 
 $ cd /usr/src
 $ cvs -qd anon...@anoncvs.example.org:/cvs up -Pd

Re: non-wintel hardware choices

[Predrag Punosevac]

Riccardo Mottola wrote:

> Hi,
> 
> Gregory Edigarov wrote:
> > if I want to build a non-wintel system with commodity running OpenBSD 
> > without problems, what are my options?

The only live architectures besides AMD64 are ARM and MIPS64 routers. I
have also heard of RISC-V and OpenRISK but have never seen the hardware
in real life.

OpenBSD supports MIPS64 router hardware via octeon port

http://www.openbsd.org/octeon.html

Please see caveats by searching this mailing list for example for
EdgeRouter LITE.

ARM-based devices, such as BeagleBone, BeagleBoard, PandaBoard ES, SABRE
Lite, Nitrogen6x and Wandboard will be supported by armv7 port. 

http://www.openbsd.org/armv7.html

Presumably Bitrig fork of OpenBSD has somewhat better support at the
moment for ARM based devices.



> > preferably something non-apple also, which i will be able to connect 
> > display, mouse, and keyboard, and hopefully run X, etc. 

Apple uses Intel hardware for a long time :)

> 
> since we don't have Raspberry support, then your choice for reasonable 

Who are we? Raspberry PI is a pile of proprietary firmware. 

> (albeit almost all obsolete) platform restricts to ultra-sparc (old 
> sparcs are fun, but slow by any means and also the CPU support is for 
> OpenBSD hit and miss... 2 of my SparcStations are unstable), PPC (some 

Sparc (old 32-bit SUN hardware from late 80s), Sparc64, sgi, alpha,
macppc are all vintage architectures. You apparently never run OpenBSD
on Sparc64 hardware since otherwise you would know that OpenBSD support
for Sparc64 was only second to Solaris. OpenBSD is the only operating
system other than Solaris which support UltraSPARC IV/T1/T2 and Fujitsu
SPARC64-V/VI/VII chip-sets. That was the favorite hardware of OpenBSD
developers before it died circa 2004. Sun Blade 2500 gray was the last
and the greatest. I gave mine to somebody last Summer. Too much noise
and electricity. It was not worthy for a guy who doesn't make living by
writing a code (Nice Big-endian machine). 

> Amiga boards, older Macs) and... nothing else. PA-RISC is fun, but I 
> never tried X there.
> And, if you think, the only other machines that could do are Itanium and
> 
> Alpha.
> 

Amiga :) Dude we are talking some late 80s stuff here when I was young. 

> 
> For most of these, you will notice that base OpenBSD stuff works pretty 
> well (as does NetBSD and to a lesser degree Linux) but several bigger 
> application prove quite buggy! Browsers, mail clients.. everything is 
> tested on i386/amd64 only.


NetBSD Sparc64 port was in the sorry state comparing to OpenBSD. On the
top of it NetBSD has been relaying on the cross compiling for a long,
long time. At this point one has to wonder whether NetBSD can really run
on anything else than amd64. Last time I looked they didn't have native
software package builds for anything else than amd64. On the top of it
all last year during the series of interviews with OpenBSD and NetBSD
conducted by a Polish guy the most revealing thing was that not a single
NetBSD guy used NetBSD at work and even worse most guys run NetBSD only
in the virtual environment on their private hardware. In sharp contrast
all OpenBSD developers who were interviewed run large OpenBSD
deployments at work and used OpenBSD as the only OS on their private
hardware (you have to eat your own dog food).



> SPARC and PPC seem to me more crashy when bad programming happens, which
> 
> is actually a good thing and a reason to keep computing diversity alive.
> 
> But I fear it will become worse, the only thing that has a chance is ARM
> 
> which is used little-endian. Or embedded PPC, which is used also LE. Big
> 
> Endian will perhaps not even taught at school in 10+ years.
> 
> On Linux I have Firefox running on PPC, but I read that others have 
> issues with it on non-intel. Be prepared to find more bugs than usual.
> We at GNUstep take quite some care that things work on PPC, SPARC and 
> ARM, but because I love them :)
> 

With exception of ARM you are talking about vintage hardware. OP was
asking about new commodity hardware. 


Cheers,
Predrag

> Riccardo

Re: non-wintel hardware choices

[arrowscript]

Why is ARM not mentioned?
patrick@ seems to be doing a great job on this port. Bitrig is also a thing.
i.MX6 processor seem well supported and could easily run desktop stuff like HD 
videos. I think ODROID-C1 run already, no? It's just $35 last time I checked. 
Sabrelite is the standard for i.MX6, though.

Dell XPS13 9333 Touchpad doesn't work

[Gabriel Guzman]

Hello misc@

I have a Dell XPS 13 9333 that I recently installed OpenBSD on.  For the
most part everything runs great.  WiFi, suspend resume, everything.  The
laptop has both a touchscreen and a touchpad.  The touchscreen works
just fine, I can use it as a pointing device w/out problems.  The
touchpad however doesn't seem to be recognized by the system.  I'm not
sure if it's user error or some hardware that's not recognized.  dmesg
and other output included below.  Anyone have any idea what I might be
able to try to get this working?  Plugging in an external mouse also
works just fine.   

Thanks, 
gabe. 


OpenBSD 5.9-current (GENERIC.MP) #2002: Sun May  1 06:35:58 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8474284032 (8081MB)
avail mem = 8212860928 (7832MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0fc0 (69 entries)
bios0: vendor Dell Inc. version "A06" date 11/07/2014
bios0: Dell Inc. XPS13 9333
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT SSDT UEFI 
POAT BATB FPDT SLIC UEFI SSDT BGRT CSRT
acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) 
TPD4(S4) TPD7(S0) TPD8(S0) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) 
RP03(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.56 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
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 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus -1 (PEG0)
acpiprt5 at acpi0: bus -1 (PEG1)
acpiprt6 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"PNP0C14" at acpi0 not configured
"INT3F0D" at acpi0 not configured
"ACPI0008" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"SYN0608" at acpi0 not configured
dwiic0 at acpi0: I2C1 addr 0xfe105000/0x1000 irq 7
iic0 at dwiic0
ihidev0 at iic0 addr 0x2c irq 39dwiic0: timed out reading remaining 29
, failed fetching initial HID descriptor
"DLL060A" at acpi0 not configured
acpibtn0 at 

Re: non-wintel hardware choices

[Bryan Everly]

Unfortunately PA-RISC doesn't have X support at the console. You can
run X on it and have the Windows render on a SPARC, MIPS or Intel
platform though.

Thanks,
Bryan

> On May 5, 2016, at 7:37 PM, Riccardo Mottola 
wrote:
>
> Hi,
>
> Gregory Edigarov wrote:
>> if I want to build a non-wintel system with commodity running OpenBSD
without problems, what are my options?
>> preferably something non-apple also, which i will be able to connect
display, mouse, and keyboard, and hopefully run X, etc.
>
> since we don't have Raspberry support, then your choice for reasonable
(albeit almost all obsolete) platform restricts to ultra-sparc (old sparcs are
fun, but slow by any means and also the CPU support is for OpenBSD hit and
miss... 2 of my SparcStations are unstable), PPC (some Amiga boards, older
Macs) and... nothing else. PA-RISC is fun, but I never tried X there.
> And, if you think, the only other machines that could do are Itanium and
Alpha.
>
>
> For most of these, you will notice that base OpenBSD stuff works pretty well
(as does NetBSD and to a lesser degree Linux) but several bigger application
prove quite buggy! Browsers, mail clients.. everything is tested on i386/amd64
only.
> SPARC and PPC seem to me more crashy when bad programming happens, which is
actually a good thing and a reason to keep computing diversity alive. But I
fear it will become worse, the only thing that has a chance is ARM which is
used little-endian. Or embedded PPC, which is used also LE. Big Endian will
perhaps not even taught at school in 10+ years.
>
> On Linux I have Firefox running on PPC, but I read that others have issues
with it on non-intel. Be prepared to find more bugs than usual.
> We at GNUstep take quite some care that things work on PPC, SPARC and ARM,
but because I love them :)
>
> Riccardo

Re: non-wintel hardware choices

[Riccardo Mottola]

Hi,

Gregory Edigarov wrote:
if I want to build a non-wintel system with commodity running OpenBSD 
without problems, what are my options?
preferably something non-apple also, which i will be able to connect 
display, mouse, and keyboard, and hopefully run X, etc. 


since we don't have Raspberry support, then your choice for reasonable 
(albeit almost all obsolete) platform restricts to ultra-sparc (old 
sparcs are fun, but slow by any means and also the CPU support is for 
OpenBSD hit and miss... 2 of my SparcStations are unstable), PPC (some 
Amiga boards, older Macs) and... nothing else. PA-RISC is fun, but I 
never tried X there.
And, if you think, the only other machines that could do are Itanium and 
Alpha.



For most of these, you will notice that base OpenBSD stuff works pretty 
well (as does NetBSD and to a lesser degree Linux) but several bigger 
application prove quite buggy! Browsers, mail clients.. everything is 
tested on i386/amd64 only.
SPARC and PPC seem to me more crashy when bad programming happens, which 
is actually a good thing and a reason to keep computing diversity alive. 
But I fear it will become worse, the only thing that has a chance is ARM 
which is used little-endian. Or embedded PPC, which is used also LE. Big 
Endian will perhaps not even taught at school in 10+ years.


On Linux I have Firefox running on PPC, but I read that others have 
issues with it on non-intel. Be prepared to find more bugs than usual.
We at GNUstep take quite some care that things work on PPC, SPARC and 
ARM, but because I love them :)


Riccardo

SMP implementation

[Pavan Maddamsetti]

I have been reading about ongoing improvements to SMP in OpenBSD. My
understanding is that context switching from userspace to the kernel can be
hazardous if shared resources are not protected by locking. OpenBSD
currently has a "giant lock" for safe concurrent access to kernel data
structures. It will eventually be replaced by finer grained locking in
order for the kernel to execute on multiple CPUs simultaneously.

Has any thought been given to an alternative design where each CPU has its
own thread scheduler, like DragonFly BSD?

https://www.dragonflybsd.org/presentations/dragonflybsd.asiabsdcon04.pdf

Re: non-wintel hardware choices

[Christian Weisgerber]

On 2016-05-05, Gregory Edigarov  wrote:

> if I want to build a non-wintel system with commodity running OpenBSD 
> without problems, what are my options?
> preferably something non-apple also, which i will be able to connect 
> display, mouse, and keyboard, and hopefully run X, etc.

There aren't any.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gabriel Guzman]

On 05/04, Andrew Gwozdziewycz wrote:
> Hi Gabe,
> 
> I found it possible to boot and install 5.9 on an XPS 13" (9333)[0], but
> had problems getting the all important suspend to RAM (or anything which
> allowed me to close the lid and reopen to resume work) to work. Were you
> successful in getting this necessary laptop functionality working correctly?
> 
> If so, would you mind sharing your configs? I'd love to reinstall OpenBSD
> on this machine, but can't sacrifice that.

Hi Andrew -- 

Suspend just works for me.  No config necessary.  I just made sure apmd
was running and then either typing zzz, or closing the lid suspends the
machine and opening it wakes it back up. Maybe it was an issue that has
since been fixed?  My machine is also an XPS 13 9333. dmesg included for
good measuere.

gabe.


OpenBSD 5.9-current (GENERIC.MP) #2002: Sun May  1 06:35:58 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8474284032 (8081MB)
avail mem = 8212860928 (7832MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0fc0 (69 entries)
bios0: vendor Dell Inc. version "A06" date 11/07/2014
bios0: Dell Inc. XPS13 9333
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT SSDT UEFI 
POAT BATB FPDT SLIC UEFI SSDT BGRT CSRT
acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) 
TPD4(S4) TPD7(S0) TPD8(S0) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) 
RP03(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.56 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
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 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus -1 (PEG0)
acpiprt5 at acpi0: bus -1 (PEG1)
acpiprt6 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"PNP0C14" at acpi0 not configured
"INT3F0D" at acpi0 not configured
"ACPI0008" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"SYN0608" at acpi0 not configured
dwiic0 at acpi0: I2C1 addr 

Re: non-wintel hardware choices

[Christian Weisgerber]

On 2016-05-05, "Bryan C. Everly"  wrote:

> The fastest desktop that I own is a SunBlade 2500 Silver (don't let
> the name throw you, it is a tower desktop machine).

That machine is 12 years old.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

httpd apex->www redirect issues

[alex]

Hi all,

I'm trying to set up httpd to do an apex->www redirect, and it works except for 
the fact that other subdomains also get redirected. It seems as if 'server 
"pnnk.org"' matches any subdomain.

DNS:
pnnk.org. A 192.30.33.33
phoenix   A 192.30.33.33
mail  A 192.30.33.33
www   CNAME phoenix
pnnk.org. MXmail

$ cat /etc/httpd.conf
server "pnnk.org" {
listen on * port 80
listen on :: port 80
block return 301 "http://www.pnnk.org;
}

server "www.pnnk.org" {
listen on * port 80
listen on :: port 80
}

Here's an example of the problem. I expected this to fail, not redirect:

$ telnet mail.pnnk.org 80
Trying 192.30.33.33...
Connected to mail.pnnk.org.
Escape character is '^]'.
GET / HTTP/1.1
Host: mail.pnnk.org

HTTP/1.0 301 Moved Permanently
Date: Thu, 05 May 2016 13:21:19 GMT
Server: OpenBSD httpd
Connection: close
Content-Type: text/html
Content-Length: 374
Location: http://www.pnnk.org




301 Moved Permanently



301 Moved Permanently

OpenBSD httpd


Connection closed by foreign host.

Is there something I can do to get the behavior I expect? 

Thanks,
Alex

p.s. I apologize if my message shows up more than once, I had an issue with my 
mail setup but I think it's fixed now.

Re: rwhod in 5.9 ?

[Sebastian Benoit]

stan(st...@panix.com) on 2016.05.03 07:17:38 -0400:
> Building 5.9 machines to replace 5.5 ones. Looking in /usr/src on the 5.9
> machines, I do not see the code for rwhod. Has this been removed, and if
> so, why? We use this on all of our mahcines.

Because we remove code that nobody uses and maintains. The fact that you are
the first to notice after 24 months speaks for itself.

/Benno

PS: anyone still using rusers?

Re: non-wintel hardware choices

[Ted Unangst]

Gregory Edigarov wrote:
> if I want to build a non-wintel system with commodity running OpenBSD 
> without problems, what are my options?

If you install openbsd, then it won't be wintel. :)

Re: non-wintel hardware choices

[Cody Swanson]

Agreed, SPARC is your best bet for a non-x86 workstation with reasonable X 
support. I have some older SGI hardware that runs OpenBSD but the X support is 
hit and miss and certainly not as refined as the SPARC workstations I've tried. 
I think the last SPARC workstations Sun made were the ultra 25 and ultra 45. I 
have a Sunblade 2500 and even though it's 10 years old it still works fine as a 
desktop. If you are looking at these pay attention to the installed graphics 
option, not all of the cards are supported by X from what I understand.

- On May 5, 2016, at 9:00 AM, Bryan C. Everly br...@bceassociates.com wrote:

Gregory,

I'm a big fan / collector of non Wintel stuff and I run OpenBSD on it
all.  I can tell you that the 64-bit SPARC stuff seems to be the best
fit for your use case in my experience.  The downside is that a
desktop (or heaven forbid laptop) solution hasn't really been
manufactured for a while (please misc@ correct me if I'm wrong here).

The fastest desktop that I own is a SunBlade 2500 Silver (don't let
the name throw you, it is a tower desktop machine).  It has dual
1.6GHz processors and 8GB of RAM.  I put two Sun XVR-100 video cards
in it (the 100 and the 300 are about the best cards you can have with
accelerated X support that I've found).

It's pretty speedy and mostly useful.  The only downside is web
browser support.  Since Firefox and Chromium aren't available for
anything other than i386 and amd64 platforms, it's kind of hit and
miss.  If anyone on the list has a suggestion, I'd really appreciate
it.  This box is good enough to be my daily driver at work if I could
solve that wrinkle.

Thanks,
Bryan


On Thu, May 5, 2016 at 10:30 AM, Gregory Edigarov  wrote:
> Hi  everybody,
>
> if I want to build a non-wintel system with commodity running OpenBSD
> without problems, what are my options?
> preferably something non-apple also, which i will be able to connect
> display, mouse, and keyboard, and hopefully run X, etc.
>
> --
> With best regards,
>   Gregory Edigarov

Re: non-wintel hardware choices

[David Coppa]

On Thu, May 5, 2016 at 5:00 PM, Bryan C. Everly  wrote:
> Gregory,

> It's pretty speedy and mostly useful.  The only downside is web
> browser support.  Since Firefox and Chromium aren't available for
> anything other than i386 and amd64 platforms, it's kind of hit and
> miss.  If anyone on the list has a suggestion, I'd really appreciate
> it.  This box is good enough to be my daily driver at work if I could
> solve that wrinkle.

Firefox used to work on sparc64:

https://rhaalovely.net/~landry/shared/firefox-24.0a1-sparc64.png

https://rhaalovely.net/~landry/shared/firefox-24.0a1-sparc64-2.png

Ciao!
David

Re: non-wintel hardware choices

[Stefan Sperling]

On Thu, May 05, 2016 at 05:30:21PM +0300, Gregory Edigarov wrote:
> Hi  everybody,
> 
> if I want to build a non-wintel system with commodity running OpenBSD
> without problems, what are my options?
> preferably something non-apple also, which i will be able to connect
> display, mouse, and keyboard, and hopefully run X, etc.
> 
> --
> With best regards,
>   Gregory Edigarov
> 

See http://www.openbsd.org/plat.html

In particular, you might be able to find loongson or sparc64 machines
that fit your requirements.

I would not expect big modern web browsers like firefox or chromium
to run on non-intel machines, though, in case you had that in mind.

Re: non-wintel hardware choices

[Bryan C. Everly]

Gregory,

I'm a big fan / collector of non Wintel stuff and I run OpenBSD on it
all.  I can tell you that the 64-bit SPARC stuff seems to be the best
fit for your use case in my experience.  The downside is that a
desktop (or heaven forbid laptop) solution hasn't really been
manufactured for a while (please misc@ correct me if I'm wrong here).

The fastest desktop that I own is a SunBlade 2500 Silver (don't let
the name throw you, it is a tower desktop machine).  It has dual
1.6GHz processors and 8GB of RAM.  I put two Sun XVR-100 video cards
in it (the 100 and the 300 are about the best cards you can have with
accelerated X support that I've found).

It's pretty speedy and mostly useful.  The only downside is web
browser support.  Since Firefox and Chromium aren't available for
anything other than i386 and amd64 platforms, it's kind of hit and
miss.  If anyone on the list has a suggestion, I'd really appreciate
it.  This box is good enough to be my daily driver at work if I could
solve that wrinkle.

Thanks,
Bryan


On Thu, May 5, 2016 at 10:30 AM, Gregory Edigarov  wrote:
> Hi  everybody,
>
> if I want to build a non-wintel system with commodity running OpenBSD
> without problems, what are my options?
> preferably something non-apple also, which i will be able to connect
> display, mouse, and keyboard, and hopefully run X, etc.
>
> --
> With best regards,
>   Gregory Edigarov

non-wintel hardware choices

[Gregory Edigarov]

Hi  everybody,

if I want to build a non-wintel system with commodity running OpenBSD 
without problems, what are my options?
preferably something non-apple also, which i will be able to connect 
display, mouse, and keyboard, and hopefully run X, etc.


--
With best regards,
  Gregory Edigarov

Re: Laptop not waking from suspend on opening lid

[Norman Golisz]

On Thu May  5 2016 08:10, Anthony Campbell wrote:
> On 04 May 2016, Mike Larkin wrote:
> > 
> > This is probably the same problem that kettenis fixed in a recent post.
> > 
> > I'd try applying that diff first.
> > 
> > -ml
> 
> After an upgrade to a new snapshot on 3 May things have now reverted to
> normal and waking occurs correctly.

Yes, I can confirm that. Thank you all!

Re: iwi and rsu driver not working in 5.9

[Stefan Sperling]

On Thu, May 05, 2016 at 11:09:27AM +0200, Stefan Sperling wrote:
> You need this commit to fix iwi on 5.9.
> Not sure about rsu(4) but perhaps this will fix it, too.

You can now also build a kernel from the 5.9-stable branch to get this patch.

> /usr/src/sys/net80211/ieee80211_node.c
> 
> revision 1.100
> date: 2016/03/03 07:20:45;  author: gerhard;  state: Exp;  lines: +3 -1;  
> commitid: t8jeYaoxQko1CuFD;
> Restore assignment of ic_curmode that was accidentally removed when
> moving the ERP code to post-assoc phase. Fixes iwi(4) fatal firmware
> errors.
> 
> ok stsp@, sobrado@
> 
> 
> Index: ieee80211_node.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211_node.c,v
> retrieving revision 1.99
> retrieving revision 1.100
> diff -u -p -r1.99 -r1.100
> --- ieee80211_node.c  25 Jan 2016 15:14:22 -  1.99
> +++ ieee80211_node.c  3 Mar 2016 07:20:45 -   1.100
> @@ -630,6 +630,8 @@ ieee80211_end_scan(struct ifnet *ifp)
>   goto notfound;
>   (*ic->ic_node_copy)(ic, ic->ic_bss, selbs);
>   ni = ic->ic_bss;
> +
> + ic->ic_curmode = ieee80211_chan2mode(ic, ni->ni_chan);
>  
>   if (ic->ic_flags & IEEE80211_F_RSNON)
>   ieee80211_choose_rsnparams(ic);

Re: iwi and rsu driver not working in 5.9

[Stefan Sperling]

On Thu, May 05, 2016 at 08:46:26AM +0200, Boris Rieken wrote:
> I have two laptops that use the iwi driver for their Intel wireless
> interfaces and I have an usb wifi dongle that uses the rsu driver. Under 5.7
> and 5.8 these work perfectly. But under 5.9 I cannot connect to a wireless
> network. Scanning with ifconfig works fine. When using dhclient to get an ip
> address. Dhclient tells me the device is sleeping..?
> 
> I tried the usb dongle on 3 different laptop and on a virtual machine
> (virtualbox with usb pass thru). With 5.9 it never works. But as soon as I
> install 5.7 or 5.8 everything works as expected.
> 
> I always used the i386 builds.
> 

You need this commit to fix iwi on 5.9.
Not sure about rsu(4) but perhaps this will fix it, too.

/usr/src/sys/net80211/ieee80211_node.c

revision 1.100
date: 2016/03/03 07:20:45;  author: gerhard;  state: Exp;  lines: +3 -1;  
commitid: t8jeYaoxQko1CuFD;
Restore assignment of ic_curmode that was accidentally removed when
moving the ERP code to post-assoc phase. Fixes iwi(4) fatal firmware
errors.

ok stsp@, sobrado@


Index: ieee80211_node.c
===
RCS file: /cvs/src/sys/net80211/ieee80211_node.c,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -p -r1.99 -r1.100
--- ieee80211_node.c25 Jan 2016 15:14:22 -  1.99
+++ ieee80211_node.c3 Mar 2016 07:20:45 -   1.100
@@ -630,6 +630,8 @@ ieee80211_end_scan(struct ifnet *ifp)
goto notfound;
(*ic->ic_node_copy)(ic, ic->ic_bss, selbs);
ni = ic->ic_bss;
+
+   ic->ic_curmode = ieee80211_chan2mode(ic, ni->ni_chan);
 
if (ic->ic_flags & IEEE80211_F_RSNON)
ieee80211_choose_rsnparams(ic);

Re: Laptop not waking from suspend on opening lid

[Anthony Campbell]

On 04 May 2016, Mike Larkin wrote:
> 
> This is probably the same problem that kettenis fixed in a recent post.
> 
> I'd try applying that diff first.
> 
> -ml


After an upgrade to a new snapshot on 3 May things have now reverted to
normal and waking occurs correctly.

AC

-- 
Anthony Campbellhttp://www.acampbell.uk

iwi and rsu driver not working in 5.9

[Boris Rieken]

I have two laptops that use the iwi driver for their Intel wireless
interfaces and I have an usb wifi dongle that uses the rsu driver. Under 5.7
and 5.8 these work perfectly. But under 5.9 I cannot connect to a wireless
network. Scanning with ifconfig works fine. When using dhclient to get an ip
address. Dhclient tells me the device is sleeping..?

I tried the usb dongle on 3 different laptop and on a virtual machine
(virtualbox with usb pass thru). With 5.9 it never works. But as soon as I
install 5.7 or 5.8 everything works as expected.

I always used the i386 builds.