Re: Suspend/Hibernate doesn't work after upgrading to the latest current snapshot

[Justin Yang]

Hi,

I always follow the -current, so I use an elder snapshot before this
upgrading, though I've not upgraded my laptop for more than one week.

On Sun, Apr 14, 2019 at 1:20 AM Mike Larkin  wrote:

> On Sat, Apr 13, 2019 at 10:54:14PM +0800, Justin Yang wrote:
> > Hi, all:
> >
> > After upgrading to the latest current snapshot today, I find that the
> > suspend and hibernate functions do not work anymore on my Xiaomi Air
> > laptop. It does trigger the black screen after typing zzz/ZZZ, or closing
> > the lid, but can not resume anymore. I try to dig into the log in
> > /var/log/message, but am not able to find anything useful. So could you
> > help me figure it out, please?
> >
> > My dmesg is attached with this mail. Thanks.
> >
> >
> > --
> > Justin Yang
>
>
> What were you running before the snapshot?
>
> > OpenBSD 6.5 (GENERIC.MP) #857: Thu Apr 11 08:02:35 MDT 2019
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 4156014592 (3963MB)
> > avail mem = 4020420608 (3834MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xe6380 (64 entries)
> > bios0: vendor INSYDE Corp. version "XMAKB200P0200" date 11/02/2017
> > bios0: Timi TM1607
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP UEFI UEFI MSDM SSDT SSDT TPM2 SSDT SSDT ASF!
> ASPT BOOT DBGP HPET APIC MCFG SSDT SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP
> DBG2 SSDT SSDT DMAR FPDT
> > acpi0: wakeup devices PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4)
> HDAS(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4)
> RP08(S4) RP10(S4) RP11(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) m3-7Y30 CPU @ 1.00GHz, 5540.71 MHz, 06-8e-09
> > 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 974.81 MHz, 06-8e-09
> > 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 899.34 MHz, 06-8e-09
> > 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz, 06-8e-09
> > 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,L1DF,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
> > acpimcfg0: addr 0xe000, bus 0-255
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus -1 (RP01)
> > acpiprt2 at acpi0: bus -1 (RP02)
> > acpiprt3 at acpi0: b

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Noth]

Sorry about that, I totally messed up the names. I want to thank jcs@ 
not jostein@ and the github link is 
https://github.com/jcs/intel_backlight_fbsd . I somehow included a 
totally irrelevant youtube channel I don't even remember clicking.


My apologies,

Noth

On 14/04/2019 05:05, Alessandro De Laurenzis wrote:

Hello Noth,

Could you please double check the two links you posted? It seems that 
the first page doesn't exist and the second one is not relevant...


Thanks

--
Alessandro

Il 14 aprile 2019 00:33:14 CEST, Noth  ha 
scritto:


Thanks to jostein@ on #openbsd, I now have a working touchpad. All it
took was disabling dwiic* in the kernel, and then both the touchpad
(wsmouse0) and touchscreen (wsmouse1) work.

I was also pointed by mlarkin to the intel_backlight
(https://github.com/jostein/intel_backlight_fbsd  ) command which works
perfectly.

So with just one tweak and an extra userland command, the Dell XPS 9350
works 100% under OpenBSD:

- suspend works

- hibernation works

- sound works

- Xorg works, with brightness ajustments possible

- wifi works once you switch out the wifi chip

If you like 13" 3200x1800 screens in a 11.6" size laptop, I can only but
recommend this model.



I also tried the same fixes on the XPS 9370, and got the same succesful
result. However suspend & hibernation don't work for the time being.


Cheers,

Noth

On 13th/04/2019 17:44, Noth wrote:

It worked around 6.1 but no longer does, Xorg stopped working
with 6.2 and only just started working with the snapshot I
tried yesterday. I hadn't updated in 1-2 months, so not sure
when the fix went in for inteldrm. On 13/04/2019 17:06, joshua
stein wrote:

On 13/04/2019 16:49, Noth wrote:

Hello again,    I updated to the latest snapshot
and now Xorg works! But it has a caveat, the
pointer device detected is the touchscreen not the
touchpad. It's assigned device wsmouse0 and ums1
doesn't seem to recognize the touchpad anymore so
no wsmouse1. I've tested this on the XPS 13 9350
and my new 9370. Same results on both (do make
sure you have the latest firmware installed via
fw_update). 


Did the touchpad ever work or is this a recent regression?

dwiic0 at pci0 dev 21 function 0 "Intel 100 Series
I2C" rev 0x21: apic 2 int 16 iic0 at dwiic0 dwiic1 at
pci0 dev 21 function 1 "Intel 100 Series I2C" rev
0x21: apic 2 int 17 iic1 at dwiic1 ihidev0 at iic1
addr 0x2cdwiic1: timed out reading remaining 29 ,
failed fetching initial HID descriptor 

Re: ws

[Bryan Steele]

On Sun, Apr 14, 2019 at 11:31:33AM +0900, Jerome Pinot wrote:
> Hi,
> 
> I'm curious to know what is the origin of the "w(s)" prefix we have
> on some OpenBSD specific places, like:
> - wscons
> -wsmoused
> - wskbd
> - wsrc
> - wobj
> etc
> 
> It seems to be a quite old practice and common with other BSDs.
> Anybody has the history for this?
> 
> Thanks!
> 
> -- 
> Jerome Pinot

'workstation console' at least sounds plausible.

https://www.netbsd.org/docs/guide/en/chap-cons.html

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Alessandro De Laurenzis]

Hello Noth,

Could you please double check the two links you posted? It seems that the first 
page doesn't exist and the second one is not relevant...

Thanks

--
Alessandro

Il 14 aprile 2019 00:33:14 CEST, Noth  ha scritto:
>Thanks to jostein@ on #openbsd, I now have a working touchpad. All it 
>took was disabling dwiic* in the kernel, and then both the touchpad 
>(wsmouse0) and touchscreen (wsmouse1) work.
>
>I was also pointed by mlarkin to the intel_backlight 
>(https://github.com/jostein/intel_backlight_fbsd ) command which works 
>perfectly.
>
>So with just one tweak and an extra userland command, the Dell XPS 9350
>
>works 100% under OpenBSD:
>
>- suspend works
>
>- hibernation works
>
>- sound works
>
>- Xorg works, with brightness ajustments possible
>
>- wifi works once you switch out the wifi chip
>
>If you like 13" 3200x1800 screens in a 11.6" size laptop, I can only
>but 
>recommend this model.
>
>
>
>I also tried the same fixes on the XPS 9370, and got the same succesful
>
>result. However suspend & hibernation don't work for the time being.
>
>
>Cheers,
>
>Noth
>
>On 13th/04/2019 17:44, Noth wrote:
>> It worked around 6.1 but no longer does, Xorg stopped working with
>6.2 
>> and only just started working with the snapshot I tried yesterday. I 
>> hadn't updated in 1-2 months, so not sure when the fix went in for 
>> inteldrm.
>>
>> On 13/04/2019 17:06, joshua stein wrote:
 On 13/04/2019 16:49, Noth wrote:
> Hello again,
>
>    I updated to the latest snapshot and now Xorg works! But it has
>a
> caveat, the pointer device detected is the touchscreen not the 
> touchpad.
> It's assigned device wsmouse0 and ums1 doesn't seem to recognize
>the
> touchpad anymore so no wsmouse1. I've tested this on the XPS 13 
> 9350 and
> my new 9370. Same results on both (do make sure you have the
>latest
> firmware installed via fw_update).
>>> Did the touchpad ever work or is this a recent regression?
>>>
 dwiic0 at pci0 dev 21 function 0 "Intel 100 Series I2C" rev 0x21: 
 apic 2 int
 16
 iic0 at dwiic0
 dwiic1 at pci0 dev 21 function 1 "Intel 100 Series I2C" rev 0x21: 
 apic 2 int
 17
 iic1 at dwiic1
 ihidev0 at iic1 addr 0x2cdwiic1: timed out reading remaining 29
 , failed fetching initial HID descriptor
>>

ws

[Jerome Pinot]

Hi,

I'm curious to know what is the origin of the "w(s)" prefix we have
on some OpenBSD specific places, like:
- wscons
-wsmoused
- wskbd
- wsrc
- wobj
etc

It seems to be a quite old practice and common with other BSDs.
Anybody has the history for this?

Thanks!

-- 
Jerome Pinot

Re: What are the operating systems that ship without blobs?

[Quantum Robin]

Em sáb, 13 de abr de 2019 20:36, Leonid Bobrov 
escreveu:

> On Sat, Apr 13, 2019 at 01:12:06PM -0300, Quantum Robin wrote:
> > Em sáb, 13 de abr de 2019 04:23, Chris Bennett <
> > cpb_m...@bennettconstruction.us> escreveu:
> >
> > > On Sat, Apr 13, 2019 at 01:55:21AM -0300, Quantum Robin wrote:
> > > > Are there operating
> > > > systems that ship without blobs?
> > > >
> > > > If yes, what are the operating
> > > > systems that ship without blobs?
> > >
> > > OpenBSD does not ship with blobs. Ever.
> > > That was a major theme s number of years ago.
> > >
> > > Firmware is not considered a blob since this is strictly hardware
> > > related code. No firmware, device won't work.
> > >
> > > Nvidia is an excellent example of a company 100% hostile to Open Source
> > > code. They refuse to release anything needed to even allow someone to
> > > write the necessary firmware/software.
> > >
> > > So, anything that fully supports Nvidia is running proprietary secret
> > > blobs. Yuck. These blobs may be harmless, but who knows?
> > >
> > > So if you are shopping for an OS, you can put a checkmark for OpenBSD
> in
> > > the no blobs list.
> > >
> > > Beyond that, the list may or may not want to discuss other OS's.
> > > Probably not.
> > >
> > > Since this topic has come up and it's personally useful to me to reply
> > > elsewhere about security elsewhere right now, could someone reply to
> > > both of us off-list about this topic?
> > >
> > > Otherwise, we are getting into other OS junk that IMHO is not
> > > appropriate here.
> > >
> > > Chris Bennett
> > >
> >
> > In the past, Theo de Raadt said:
> >
> > "3. mail from Theo, 12.03.2007 03:00:
> >
> > Did you even think about the fact that there are only two operating
> systems
> > that ship without blobs?
> >
> > OpenBSD
> >
> > Debian (and derived systems)"
> >
> > Why Theo de Raadt said in past here in misc openbsd that was fact that
> > existed only two operating systems that did ship without blobs if is
> truth
> > that this is a list for OpenBSD, not op systems in general?
> >
> > >
>
> Theo missed GNU/Linux-libre distros recommended by FSF, they don't
> include blobs and non-free firmware. Also GNU/Hurd has no blobs and
> no non-free firmware, right?
>

Leonid Bobrov,

Do Theo de Raadt agree with you that he missed GNU/Linux-libre distros
recommended by FSF don't
include blobs and non-free firmware and that GNU/Hurd has no blobs and
no non-free firmware?

Theo de Raadt,

Do you agree with Leonid Bobrov that GNU/Linux-libre distros recommended by
FSF don't
include blobs and non-free firmware and that GNU/Hurd has no blobs and
no non-free firmware?

If not, why you do not agree with Leonid Bobrov that GNU/Linux-libre
distros recommended by FSF don't
include blobs and non-free firmware and that GNU/Hurd has no blobs and
no non-free firmware?

>

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Noth]

Thanks to jostein@ on #openbsd, I now have a working touchpad. All it 
took was disabling dwiic* in the kernel, and then both the touchpad 
(wsmouse0) and touchscreen (wsmouse1) work.


I was also pointed by mlarkin to the intel_backlight 
(https://github.com/jostein/intel_backlight_fbsd ) command which works 
perfectly.


So with just one tweak and an extra userland command, the Dell XPS 9350 
works 100% under OpenBSD:


- suspend works

- hibernation works

- sound works

- Xorg works, with brightness ajustments possible

- wifi works once you switch out the wifi chip

If you like 13" 3200x1800 screens in a 11.6" size laptop, I can only but 
recommend this model.




I also tried the same fixes on the XPS 9370, and got the same succesful 
result. However suspend & hibernation don't work for the time being.



Cheers,

Noth

On 13th/04/2019 17:44, Noth wrote:
It worked around 6.1 but no longer does, Xorg stopped working with 6.2 
and only just started working with the snapshot I tried yesterday. I 
hadn't updated in 1-2 months, so not sure when the fix went in for 
inteldrm.


On 13/04/2019 17:06, joshua stein wrote:

On 13/04/2019 16:49, Noth wrote:

Hello again,

   I updated to the latest snapshot and now Xorg works! But it has a
caveat, the pointer device detected is the touchscreen not the 
touchpad.

It's assigned device wsmouse0 and ums1 doesn't seem to recognize the
touchpad anymore so no wsmouse1. I've tested this on the XPS 13 
9350 and

my new 9370. Same results on both (do make sure you have the latest
firmware installed via fw_update).

Did the touchpad ever work or is this a recent regression?

dwiic0 at pci0 dev 21 function 0 "Intel 100 Series I2C" rev 0x21: 
apic 2 int

16
iic0 at dwiic0
dwiic1 at pci0 dev 21 function 1 "Intel 100 Series I2C" rev 0x21: 
apic 2 int

17
iic1 at dwiic1
ihidev0 at iic1 addr 0x2cdwiic1: timed out reading remaining 29
, failed fetching initial HID descriptor

Re: What are the operating systems that ship without blobs?

[Leonid Bobrov]

On Sat, Apr 13, 2019 at 01:12:06PM -0300, Quantum Robin wrote:
> Em sáb, 13 de abr de 2019 04:23, Chris Bennett <
> cpb_m...@bennettconstruction.us> escreveu:
> 
> > On Sat, Apr 13, 2019 at 01:55:21AM -0300, Quantum Robin wrote:
> > > Are there operating
> > > systems that ship without blobs?
> > >
> > > If yes, what are the operating
> > > systems that ship without blobs?
> >
> > OpenBSD does not ship with blobs. Ever.
> > That was a major theme s number of years ago.
> >
> > Firmware is not considered a blob since this is strictly hardware
> > related code. No firmware, device won't work.
> >
> > Nvidia is an excellent example of a company 100% hostile to Open Source
> > code. They refuse to release anything needed to even allow someone to
> > write the necessary firmware/software.
> >
> > So, anything that fully supports Nvidia is running proprietary secret
> > blobs. Yuck. These blobs may be harmless, but who knows?
> >
> > So if you are shopping for an OS, you can put a checkmark for OpenBSD in
> > the no blobs list.
> >
> > Beyond that, the list may or may not want to discuss other OS's.
> > Probably not.
> >
> > Since this topic has come up and it's personally useful to me to reply
> > elsewhere about security elsewhere right now, could someone reply to
> > both of us off-list about this topic?
> >
> > Otherwise, we are getting into other OS junk that IMHO is not
> > appropriate here.
> >
> > Chris Bennett
> >
> 
> In the past, Theo de Raadt said:
> 
> "3. mail from Theo, 12.03.2007 03:00:
> 
> Did you even think about the fact that there are only two operating systems
> that ship without blobs?
> 
> OpenBSD
> 
> Debian (and derived systems)"
> 
> Why Theo de Raadt said in past here in misc openbsd that was fact that
> existed only two operating systems that did ship without blobs if is truth
> that this is a list for OpenBSD, not op systems in general?
> 
> >

Theo missed GNU/Linux-libre distros recommended by FSF, they don't
include blobs and non-free firmware. Also GNU/Hurd has no blobs and
no non-free firmware, right?

Re: Good options for SAS HBA or SATA expansion cards?

[John Long]

On Sat, 13 Apr 2019 08:05:29 - (UTC)
Stuart Henderson  wrote:

> On 2019-04-11, John Long  wrote:
> > I have a Dell server that was advertised to support 4x3.5 + 2x2.5
> > drives but when I popped it open I found there are only 4 SATA
> > ports on the motherboard total. So of the 6 claimed drives, I can
> > actually only install 3 drives because the stock DVD drive consumes
> > a mobo port.  
> 
> You missed the important information of *which* server.

Ah sorry.

> If it's one of the usual poweredge then you're usually better off with
> whatever they normally use for RAID systems (you can usually find them
> second-hand).

Yeah T30 PowerEdge. The local shop has the card Dell recommended, but
I'm not sure I trust them since it's unlikely Dell tests anything but a
thousand variants of Windows and *maybe* RedHat.

/jl

Re: Good options for SAS HBA or SATA expansion cards?

[John Long]

Thank you Paul and Johann!

/jl

Re: Suspend/Hibernate doesn't work after upgrading to the latest current snapshot

[Theo de Raadt]

Please review kernel changes between those dates, and consider compiling
a set of kernels to pinpoint it better.

That's the best advice available right now.  (We may work on producing
some tooling that makes this easier).



Zac P  wrote:

> I have the same problem on a Dell Inspiron 5570 running snapshot #847.
> OpenBSD 6.5 (GENERIC.MP) #847: Tue Apr  9 09:12:46 MDT 2019
> 
> Suspend has actually never worked (most likely due to UEFI, I just
> haven't looked into it), but hibernate worked perfectly on the snapshot
> from 2019-03-19.
> 
> I first noticed hibernate stopped working after upgrading from the
> 2019-03-19 snapshot to the 2019-04-07 snapshot.
> 
> I will continue researching and provide more information if I can.
> 
> - Zac
> 
> My dmesg below:
> OpenBSD 6.5 (GENERIC.MP) #847: Tue Apr  9 09:12:46 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 1276160 (12170MB)
> avail mem = 12365201408 (11792MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (96 entries)
> bios0: vendor Dell Inc. version "1.1.8" date 08/15/2018
> bios0: Dell Inc. Inspiron 5570
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT BOOT SSDT HPET
> SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT SSDT MSDM
> SLIC BGRT TPM2 DMAR
> acpi0: wakeup devices PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4)
> RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4)
> PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz, 3393.45 MHz, 06-8e-0a
> 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,L1DF,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 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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
> 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,L1DF,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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
> 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,L1DF,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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
> 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,L1DF,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
> acpimcfg0: addr 0xe000, bus 0-255
> acpihpet0 at acpi0: 2399 Hz
> 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 -1 (RP09)
> acpiprt5 at acpi0: bus -1 (RP10)
> acpiprt6 at acpi0: bus -1 (RP11)
> acpiprt7 at acpi0: b

Re: Suspend/Hibernate doesn't work after upgrading to the latest current snapshot

[Zac P]

I have the same problem on a Dell Inspiron 5570 running snapshot #847.
OpenBSD 6.5 (GENERIC.MP) #847: Tue Apr  9 09:12:46 MDT 2019

Suspend has actually never worked (most likely due to UEFI, I just
haven't looked into it), but hibernate worked perfectly on the snapshot
from 2019-03-19.

I first noticed hibernate stopped working after upgrading from the
2019-03-19 snapshot to the 2019-04-07 snapshot.

I will continue researching and provide more information if I can.

- Zac

My dmesg below:
OpenBSD 6.5 (GENERIC.MP) #847: Tue Apr  9 09:12:46 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1276160 (12170MB)
avail mem = 12365201408 (11792MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (96 entries)
bios0: vendor Dell Inc. version "1.1.8" date 08/15/2018
bios0: Dell Inc. Inspiron 5570
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT BOOT SSDT HPET
SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT SSDT MSDM
SLIC BGRT TPM2 DMAR
acpi0: wakeup devices PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4)
RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4)
PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz, 3393.45 MHz, 06-8e-0a
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,L1DF,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 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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
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,L1DF,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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
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,L1DF,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) i3-8130U CPU @ 2.20GHz, 3392.09 MHz, 06-8e-0a
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,L1DF,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
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 2399 Hz
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 -1 (RP09)
acpiprt5 at acpi0: bus -1 (RP10)
acpiprt6 at acpi0: bus -1 (RP11)
acpiprt7 at acpi0: bus -1 (RP12)
acpiprt8 at acpi0: bus -1 (RP13)
acpiprt9 at acpi0: bus -1 (RP01)
acpiprt10 at acpi0: bus -1 (RP02)
acpiprt11 at acpi0: bus -1 (RP03)
acpiprt12 at acpi0: bus -1 (RP04)
acpiprt13 at acpi0: bus 1 (RP05)
acpiprt14 at acpi0: bus 2 (RP06)
acpiprt15 at acpi0: bus -1 (RP07)
acpiprt16 at acpi0: bus -1 (RP08)
acpiprt17 at acpi0: bus -1 (RP17)
acpiprt18 at acpi0: bus -1 (RP18)
acpipr

Re: Suspend/Hibernate doesn't work after upgrading to the latest current snapshot

[Mike Larkin]

On Sat, Apr 13, 2019 at 10:54:14PM +0800, Justin Yang wrote:
> Hi, all:
> 
> After upgrading to the latest current snapshot today, I find that the
> suspend and hibernate functions do not work anymore on my Xiaomi Air
> laptop. It does trigger the black screen after typing zzz/ZZZ, or closing
> the lid, but can not resume anymore. I try to dig into the log in
> /var/log/message, but am not able to find anything useful. So could you
> help me figure it out, please?
> 
> My dmesg is attached with this mail. Thanks.
> 
> 
> -- 
> Justin Yang


What were you running before the snapshot?

> OpenBSD 6.5 (GENERIC.MP) #857: Thu Apr 11 08:02:35 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4156014592 (3963MB)
> avail mem = 4020420608 (3834MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xe6380 (64 entries)
> bios0: vendor INSYDE Corp. version "XMAKB200P0200" date 11/02/2017
> bios0: Timi TM1607
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP UEFI UEFI MSDM SSDT SSDT TPM2 SSDT SSDT ASF! ASPT 
> BOOT DBGP HPET APIC MCFG SSDT SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 
> SSDT SSDT DMAR FPDT
> acpi0: wakeup devices PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) 
> RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) 
> RP10(S4) RP11(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) m3-7Y30 CPU @ 1.00GHz, 5540.71 MHz, 06-8e-09
> 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 974.81 MHz, 06-8e-09
> 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 899.34 MHz, 06-8e-09
> 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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz, 06-8e-09
> 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,L1DF,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
> acpimcfg0: addr 0xe000, bus 0-255
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (RP01)
> acpiprt2 at acpi0: bus -1 (RP02)
> acpiprt3 at acpi0: bus -1 (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 1 (RP09)
> acpiprt10 at acpi0: bus -1 (RP10)
> acpiprt11 at acpi0: bus -1 (RP11)
> acpiprt12 at acpi0

Re: What are the operating systems that ship without blobs?

[Quantum Robin]

Em sáb, 13 de abr de 2019 04:23, Chris Bennett <
cpb_m...@bennettconstruction.us> escreveu:

> On Sat, Apr 13, 2019 at 01:55:21AM -0300, Quantum Robin wrote:
> > Are there operating
> > systems that ship without blobs?
> >
> > If yes, what are the operating
> > systems that ship without blobs?
>
> OpenBSD does not ship with blobs. Ever.
> That was a major theme s number of years ago.
>
> Firmware is not considered a blob since this is strictly hardware
> related code. No firmware, device won't work.
>
> Nvidia is an excellent example of a company 100% hostile to Open Source
> code. They refuse to release anything needed to even allow someone to
> write the necessary firmware/software.
>
> So, anything that fully supports Nvidia is running proprietary secret
> blobs. Yuck. These blobs may be harmless, but who knows?
>
> So if you are shopping for an OS, you can put a checkmark for OpenBSD in
> the no blobs list.
>
> Beyond that, the list may or may not want to discuss other OS's.
> Probably not.
>
> Since this topic has come up and it's personally useful to me to reply
> elsewhere about security elsewhere right now, could someone reply to
> both of us off-list about this topic?
>
> Otherwise, we are getting into other OS junk that IMHO is not
> appropriate here.
>
> Chris Bennett
>

In the past, Theo de Raadt said:

"3. mail from Theo, 12.03.2007 03:00:

Did you even think about the fact that there are only two operating systems
that ship without blobs?

OpenBSD

Debian (and derived systems)"

Why Theo de Raadt said in past here in misc openbsd that was fact that
existed only two operating systems that did ship without blobs if is truth
that this is a list for OpenBSD, not op systems in general?

>

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Noth]

It worked around 6.1 but no longer does, Xorg stopped working with 6.2 
and only just started working with the snapshot I tried yesterday. I 
hadn't updated in 1-2 months, so not sure when the fix went in for inteldrm.


On 13/04/2019 17:06, joshua stein wrote:

On 13/04/2019 16:49, Noth wrote:

Hello again,

   I updated to the latest snapshot and now Xorg works! But it has a
caveat, the pointer device detected is the touchscreen not the touchpad.
It's assigned device wsmouse0 and ums1 doesn't seem to recognize the
touchpad anymore so no wsmouse1. I've tested this on the XPS 13 9350 and
my new 9370. Same results on both (do make sure you have the latest
firmware installed via fw_update).

Did the touchpad ever work or is this a recent regression?


dwiic0 at pci0 dev 21 function 0 "Intel 100 Series I2C" rev 0x21: apic 2 int
16
iic0 at dwiic0
dwiic1 at pci0 dev 21 function 1 "Intel 100 Series I2C" rev 0x21: apic 2 int
17
iic1 at dwiic1
ihidev0 at iic1 addr 0x2cdwiic1: timed out reading remaining 29
, failed fetching initial HID descriptor

Re: Black screen when starting Xorg with Dell XPS 13 9350

[joshua stein]

> On 13/04/2019 16:49, Noth wrote:
> > Hello again,
> > 
> >   I updated to the latest snapshot and now Xorg works! But it has a
> > caveat, the pointer device detected is the touchscreen not the touchpad.
> > It's assigned device wsmouse0 and ums1 doesn't seem to recognize the
> > touchpad anymore so no wsmouse1. I've tested this on the XPS 13 9350 and
> > my new 9370. Same results on both (do make sure you have the latest
> > firmware installed via fw_update).

Did the touchpad ever work or is this a recent regression?

> dwiic0 at pci0 dev 21 function 0 "Intel 100 Series I2C" rev 0x21: apic 2 int
> 16
> iic0 at dwiic0
> dwiic1 at pci0 dev 21 function 1 "Intel 100 Series I2C" rev 0x21: apic 2 int
> 17
> iic1 at dwiic1
> ihidev0 at iic1 addr 0x2cdwiic1: timed out reading remaining 29
> , failed fetching initial HID descriptor

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Noth]

Dmesg:

OpenBSD 6.5 (GENERIC.MP) #857: Thu Apr 11 08:02:35 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16991145984 (16204MB)
avail mem = 16466567168 (15703MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (94 entries)
bios0: vendor Dell Inc. version "1.10.1" date 01/22/2019
bios0: Dell Inc. XPS 13 9350
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT 
SSDT DBGP DBG2 SSDT BOOT SSDT UEFI SSDT MSDM SSDT SLIC DMAR BGRT TPM2 ASF!
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) 
PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) 
RP12(S4) PXSX(S4) RP13(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz, 2494.94 MHz, 06-4e-03
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,L1DF,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) i7-6500U CPU @ 2.50GHz, 2494.23 MHz, 06-4e-03
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,L1DF,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) i7-6500U CPU @ 2.50GHz, 2494.23 MHz, 06-4e-03
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,L1DF,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) i7-6500U CPU @ 2.50GHz, 2494.23 MHz, 06-4e-03
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,L1DF,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
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 2399 Hz
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 60 (RP09)
acpiprt5 at acpi0: bus -1 (RP10)
acpiprt6 at acpi0: bus -1 (RP11)
acpiprt7 at acpi0: bus -1 (RP12)
acpiprt8 at acpi0: bus -1 (RP13)
acpiprt9 at acpi0: bus 1 (RP01)
acpiprt10 at acpi0: bus -1 (RP02)
acpiprt11 at acpi0: bus -1 (RP03)
acpiprt12 at acpi0: bus -1 (RP04)
acpiprt13 at acpi0: bus 58 (RP05)
acpiprt14 at acpi0: bus 59 (RP06)
acpiprt15 at acpi0: bus -1 (RP07)
acpiprt16 at acpi0: bus -1 (RP08)
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 (RP14)
acpiprt22 at acpi0: bus -1 (RP15)
acpiprt23 at acpi0: bus -1 (RP16)
acpiec0 at acpi0
acpiec at acpi0 not configured
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),

Suspend/Hibernate doesn't work after upgrading to the latest current snapshot

[Justin Yang]

Hi, all:

After upgrading to the latest current snapshot today, I find that the
suspend and hibernate functions do not work anymore on my Xiaomi Air
laptop. It does trigger the black screen after typing zzz/ZZZ, or closing
the lid, but can not resume anymore. I try to dig into the log in
/var/log/message, but am not able to find anything useful. So could you
help me figure it out, please?

My dmesg is attached with this mail. Thanks.


-- 
Justin Yang
OpenBSD 6.5 (GENERIC.MP) #857: Thu Apr 11 08:02:35 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4156014592 (3963MB)
avail mem = 4020420608 (3834MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xe6380 (64 entries)
bios0: vendor INSYDE Corp. version "XMAKB200P0200" date 11/02/2017
bios0: Timi TM1607
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI UEFI MSDM SSDT SSDT TPM2 SSDT SSDT ASF! ASPT BOOT 
DBGP HPET APIC MCFG SSDT SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT SSDT 
DMAR FPDT
acpi0: wakeup devices PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) 
RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) 
RP10(S4) RP11(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) m3-7Y30 CPU @ 1.00GHz, 5540.71 MHz, 06-8e-09
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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 974.81 MHz, 06-8e-09
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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 899.34 MHz, 06-8e-09
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,L1DF,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) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz, 06-8e-09
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,L1DF,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
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus -1 (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 1 (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

Re: Black screen when starting Xorg with Dell XPS 13 9350

[Noth]

Hello again,

  I updated to the latest snapshot and now Xorg works! But it has a 
caveat, the pointer device detected is the touchscreen not the touchpad. 
It's assigned device wsmouse0 and ums1 doesn't seem to recognize the 
touchpad anymore so no wsmouse1. I've tested this on the XPS 13 9350 and 
my new 9370. Same results on both (do make sure you have the latest 
firmware installed via fw_update).


Cheers,

Noth

On 03/03/2019 04:31, Bryan Avery wrote:

Thanks for the help, Fred. Unfortunately, I'm still getting a black
screen. I didn't previously have a ~/.xsession, but I created one with
the following contents:

export LANG=en_US.UTF-8
export ENV=$HOME/.kshrc
xrdb -merge $HOME/.Xresources
xsetroot -solid dimgray
xidle &
LANG= xclock -strftime "%a %e %b %Y %H:%M" &
xset b off
setxkbmap -option ctrl:nocaps
exec cwm

I also removed machdep.allowaperture=1 from /etc/sysctl.conf. When I
booted with this configuration, I got a black screen and the
Xorg.0.log gave:

[13.242] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[13.242] linear framebuffer access unavailable
[13.312] (--) Using wscons driver on /dev/ttyC4
[13.370]
X.Org X Server 1.19.6
Release Date: 2017-12-20
[13.370] X Protocol Version 11, Revision 0
[13.370] Build Operating System: OpenBSD 6.4 amd64
[13.370] Current Operating System: OpenBSD c12h17n2o4p.my.domain
6.4 GENERIC.MP#7 amd64
[13.370] Build Date: 25 October 2018  11:39:05PM
[13.370]
[13.370] Current version of pixman: 0.34.0
[13.370] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[13.370] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[13.370] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar  2
19:00:38 2019
[13.372] (==) Using config directory: "/etc/X11/xorg.conf.d"
[13.373] (==) Using system config directory
"/usr/X11R6/share/X11/xorg.conf.d"
[13.374] (==) No Layout section.  Using the first Screen section.
[13.374] (==) No screen section available. Using defaults.
[13.374] (**) |-->Screen "Default Screen Section" (0)
[13.374] (**) |   |-->Monitor ""
[13.375] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[13.375] (**) |   |-->Device "drm"
[13.375] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[13.375] (==) Automatically adding devices
[13.375] (==) Automatically enabling devices
[13.375] (==) Not automatically adding GPU devices
[13.375] (==) Max clients allowed: 256, resource mask: 0x1f
[13.382] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[13.382] (==) ModulePath set to "/usr/X11R6/lib/modules"
[13.383] (II) The server relies on wscons to provide the list of
input devices.
If no devices become available, reconfigure wscons or disable AutoAddDevices.
[13.383] (II) Loader magic: 0x35f44c71000
[13.383] (II) Module ABI versions:
[13.383] X.Org ANSI C Emulation: 0.4
[13.383] X.Org Video Driver: 23.0
[13.383] X.Org XInput driver : 24.1
[13.383] X.Org Server Extension : 10.0
[13.383] (--) PCI:*(0:0:2:0) 8086:1916:1028:0704 rev 7, Mem @
0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64
[13.383] (II) LoadModule: "glx"
[13.386] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[13.400] (II) Module glx: vendor="X.Org Foundation"
[13.400] compiled for 1.19.6, module version = 1.0.0
[13.400] ABI class: X.Org Server Extension, version 10.0
[13.400] (II) LoadModule: "intel"
[13.400] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so
[13.405] (II) Module intel: vendor="X.Org Foundation"
[13.405] compiled for 1.19.6, module version = 2.99.916
[13.405] Module class: X.Org Video Driver
[13.405] ABI class: X.Org Video Driver, version 23.0
[13.405] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[13.406] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[13.406] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[13.406] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics:
5200, 6200, P6300
[13.408] (II) intel(0): Using Kernel Mode Setting driver: i915,
version 1.6.0 20151010
[

Re: What are the operating systems that ship without blobs?

[Oddmund Garvik]

Le 13/04/2019 à 09:23, Chris Bennett a écrit :
> On Sat, Apr 13, 2019 at 01:55:21AM -0300, Quantum Robin wrote:
>> Are there operating
>> systems that ship without blobs?
>>
>> If yes, what are the operating
>> systems that ship without blobs?
> OpenBSD does not ship with blobs. Ever.
> That was a major theme s number of years ago.
>
> Firmware is not considered a blob since this is strictly hardware
> related code. No firmware, device won't work.
>
> Nvidia is an excellent example of a company 100% hostile to Open Source
> code. They refuse to release anything needed to even allow someone to
> write the necessary firmware/software.
>
> So, anything that fully supports Nvidia is running proprietary secret
> blobs. Yuck. These blobs may be harmless, but who knows?
>
> So if you are shopping for an OS, you can put a checkmark for OpenBSD in
> the no blobs list.
>
> Beyond that, the list may or may not want to discuss other OS's.
> Probably not.
>
> Since this topic has come up and it's personally useful to me to reply
> elsewhere about security elsewhere right now, could someone reply to
> both of us off-list about this topic?
>
> Otherwise, we are getting into other OS junk that IMHO is not
> appropriate here.
>
> Chris Bennett
>
>
>
Another approach towards a totally free system is to choose hardware
that does not need blobs and/or non-free firmware. I am using a ThinkPad
X200 where even the bios is free (Libreboot -- a de-blobbed version of
Coreboot).  OpenBSD runs very well on this system. It is quite old
(2008), but adding up to 8 GB RAM and an SSD made it more than good
enough. I am retired now, so I don't need a super-duper system for work,
but even for that it could be usable. I am writing a lot and it is
perfect...

Cheers,

Oddmund Garvik

Re: Good options for SAS HBA or SATA expansion cards?

[Stuart Henderson]

On 2019-04-11, John Long  wrote:
> I have a Dell server that was advertised to support 4x3.5 + 2x2.5
> drives but when I popped it open I found there are only 4 SATA ports on
> the motherboard total. So of the 6 claimed drives, I can actually
> only install 3 drives because the stock DVD drive consumes a mobo port.

You missed the important information of *which* server.

If it's one of the usual poweredge then you're usually better off with
whatever they normally use for RAID systems (you can usually find them
second-hand).

Re: What are the operating systems that ship without blobs?

[Chris Bennett]

On Sat, Apr 13, 2019 at 01:55:21AM -0300, Quantum Robin wrote:
> Are there operating
> systems that ship without blobs?
> 
> If yes, what are the operating
> systems that ship without blobs?

OpenBSD does not ship with blobs. Ever.
That was a major theme s number of years ago.

Firmware is not considered a blob since this is strictly hardware
related code. No firmware, device won't work.

Nvidia is an excellent example of a company 100% hostile to Open Source
code. They refuse to release anything needed to even allow someone to
write the necessary firmware/software.

So, anything that fully supports Nvidia is running proprietary secret
blobs. Yuck. These blobs may be harmless, but who knows?

So if you are shopping for an OS, you can put a checkmark for OpenBSD in
the no blobs list.

Beyond that, the list may or may not want to discuss other OS's.
Probably not.

Since this topic has come up and it's personally useful to me to reply
elsewhere about security elsewhere right now, could someone reply to
both of us off-list about this topic?

Otherwise, we are getting into other OS junk that IMHO is not
appropriate here.

Chris Bennett