Lenovo T590 ACPI issues with current + Thunderbolt 3 support?
Hi all, error related to ACPI follows after dmesg. I can provide pcidump, usbdevs or acpidump too if needed. In general machine seems to be working fine (booted from USB flash in USB 3.1 port). WiFi and LAN works great in trunk setup, 3D on Intel VGA and X11 works. dmesg and sensors send as well to dmesg@ I am expecting that some of the devices will not work (like Bluetooth obviously) or may not be needed at all like Intel MEI I have spare NVMe disk Intel SSDPEKKF512G8L , 2280 and was thinking to put it in some supported USB 3.1 external box, install OpenBSD on it and use it as sort of dualboot (Windows must stay for now however :-)). BUT reading xhci(4) and looking via misc@ archives it seems like USB 3.1 Gen1/Gen2 is not yet supported and thus I will not be able to use Thunderbolt 3 port with 40Gb/s speed. As power is available only via those 2 it may be then related to that ACPI issue with AC adapter. ( just wild guess now ) OpenBSD 6.8-current (GENERIC.MP) #202: Mon Nov 30 13:05:12 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33465077760 (31914MB) avail mem = 32435552256 (30932MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0x600f6000 (67 entries) bios0: vendor LENOVO version "N2IET92W (1.70 )" date 09/21/2020 bios0: LENOVO 20N5S4DA01 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 UEFI SSDT HPET APIC MCFG ECDT SSDT SSDT BOOT SLIC SSDT LPIT WSMT SSDT DBGP DBG2 MSDM BATB DMAR NHLT ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) P XSX(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-8665U CPU @ 1.90GHz, 1794.44 MHz, 06-8e-0c 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,V MX,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,3DNOW P,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,AR AT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES 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-8665U CPU @ 1.90GHz, 1794.87 MHz, 06-8e-0c 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,V MX,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,3DNOW P,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,AR AT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 1795.82 MHz, 06-8e-0c 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,V MX,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,3DNOW P,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,AR AT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 1795.82 MHz, 06-8e-0c 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,V MX,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,3DNOW P,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,AR AT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 1795.82 M
Re: USB ports xhci not detected in Dell Precision 7820 Tower
Hi, fixed in OpenBSD 6.8. Thanks. On 10/5/19 11:09 PM, Adrian Ali wrote: Hello, I am Newbie in OpenBSD, I have been using it for 1 year. I am an advanced user in Linux and Unix, I have been using it for 25 years. My last installation of OpenBSD was on a Dell Precision 7820 Tower workstation. I have problems with the detection of USB ports. The last test was performed with snapshots from October 3, 2019. Also update the Workstation BIOS. Perform tests with different keyboards, mouse and pen drive without any positive results. USB ports are not detected, commands: nain ~ # usbdevs -v usbdevs: no USB controllers found nain ~ # lsusb -v nain ~ # dmesg | grep -i xhci acpi0: wakeup devices XHCI(S4) RP17(S4) PXSX(S4) RP18(S4) PXSX(S4) RP19(S4) PXSX(S4) RP20(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) [...] xhci0 at pci0 dev 20 function 0 "Intel C620 xHCI" rev 0x09: msi, xHCI ff.ff xhci0: reset timeout xhci0: init failed, error=5 nain ~ # nain ~ # dmidecode -t system # dmidecode 3.1 Scanning /dev/mem for entry point. SMBIOS 3.2.1 present. # SMBIOS implementations newer than version 3.1.1 are not # fully supported by this version of dmidecode. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: Precision 7820 Tower Version: Not Specified Serial Number: 1XNPZV2 UUID: 4C4C4544-0058-4E10-8050-B1C04F5A5632 Wake-up Type: Power Switch SKU Number: 0739 Family: Precision Handle 0x0005, DMI type 12, 5 bytes System Configuration Options Option 1: Default string Handle 0x0006, DMI type 15, 35 bytes System Event Log Area Length: 4 bytes Header Start Offset: 0x Header Length: 2 bytes Data Start Offset: 0x0002 Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port Access Address: Index 0x046A, Data 0x046C Status: Invalid, Not Full Change Token: 0x Header Format: No Header Supported Log Type Descriptors: 6 Descriptor 1: End of log Data Format 1: OEM-specific Descriptor 2: End of log Data Format 2: OEM-specific Descriptor 3: End of log Data Format 3: OEM-specific Descriptor 4: End of log Data Format 4: OEM-specific Descriptor 5: End of log Data Format 5: OEM-specific Descriptor 6: End of log Data Format 6: OEM-specific Handle 0x0008, DMI type 32, 20 bytes System Boot Information Status: No errors detected nain ~ # nain ~ # dmidecode -t bios # dmidecode 3.1 Scanning /dev/mem for entry point. SMBIOS 3.2.1 present. # SMBIOS implementations newer than version 3.1.1 are not # fully supported by this version of dmidecode. Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: Dell Inc. Version: 2.3.1 Release Date: 09/01/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.3 Handle 0xF047, DMI type 13, 22 bytes BIOS Language Information Language Description Format: Long Installable Languages: 2 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1 nain ~ # nain ~ # dmidecode -t baseboard # dmidecode 3.1 Scanning /dev/mem for entry point. SMBIOS 3.2.1 present. # SMBIOS implementations newer than version 3.1.1 are not # fully supported by this version of dmidecode. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0G7W4R Version: A00 Serial Number: /1XNPZV2/CNFCW008CV00D7/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle
Installer suggestion
Would it make sense to move the timezone question to before the fetching and extraction of the install sets starts? -- chs
Re: Installer suggestion
Why would you want that? I’m curious. On Tuesday, December 1, 2020, Christer Solskogen < christer.solsko...@gmail.com> wrote: > Would it make sense to move the timezone question to before the fetching > and extraction of the install sets starts? > > -- > chs >
Re: Installer suggestion
Christer Solskogen wrote: > Would it make sense to move the timezone question to before the fetching > and extraction of the install sets starts? No, because the timezone files are in the sets, because they don't fit on all the media.
Re: OpenSMTPD and ldap+tls
On 12/1/20 1:31 AM, Martijn van Duren wrote:
> Hello,
>
> There is table_ldap in the opensmtpd-extras package, but I've never used
> it, it's undocumented and I've heard that the author sees it as a proof
> of concept only at this point. So no idea how far this will take you,
> but it's your best shot. :-)
>
> A quick look through the source shows me the following snippet of the
> config parser:
>
> else if (!strcmp(key, "username"))
> read_value(&username, key, value);
> else if (!strcmp(key, "password"))
> read_value(&password, key, value);
> else if (!strcmp(key, "basedn"))
> read_value(&basedn, key, value);
> else if (!strcmp(key, "alias_filter"))
> read_value(&queries[LDAP_ALIAS].filter, key, value);
> else if (!strcmp(key, "alias_attributes")) {
> ldap_parse_attributes(&queries[LDAP_ALIAS],
> key, value, 1);
> } else if (!strcmp(key, "credentials_filter"))
> read_value(&queries[LDAP_CREDENTIALS].filter, key,
> value);
> else if (!strcmp(key, "credentials_attributes")) {
> ldap_parse_attributes(&queries[LDAP_CREDENTIALS],
> key, value, 2);
> } else if (!strcmp(key, "domain_filter"))
> read_value(&queries[LDAP_DOMAIN].filter, key, value);
> else if (!strcmp(key, "domain_attributes")) {
> ldap_parse_attributes(&queries[LDAP_DOMAIN],
> key, value, 1);
> } else if (!strcmp(key, "userinfo_filter"))
> read_value(&queries[LDAP_USERINFO].filter, key,
> value);
> else if (!strcmp(key, "userinfo_attributes")) {
> ldap_parse_attributes(&queries[LDAP_USERINFO],
> key, value, 3);
> } else if (!strcmp(key, "mailaddr_filter"))
> read_value(&queries[LDAP_MAILADDR].filter, key,
> value);
> else if (!strcmp(key, "mailaddr_attributes")) {
>
> Hope this works for you.
>
> martijn@
>
> On Tue, 2020-12-01 at 09:02 +0300, Родин Максим wrote:
>> Hello
>> Is there a way to make opensmtpd work
>> with ldap aliases over a secure connection?
>>
>> I do not know where to find working examples of this
>> My current /etc/mail/ldap.conf look like this:
>> 1 url>>--->---ldap://ldap1.mydomain.ru
>> 2 basedn>->--->---dc=mydomain,dc=ru
>> 3 username>--->---cn=service,dc=mydomain,dc=ru
>> 4 password>--->---passpasspass
>> 5
>> 6 domain_filter>-->---(&(objectClass=domain)(dc=%s))
>> 7 domain_attributes>--dc
>> 8
>> 9 credentials_filter>-(&(objectClass=posixAccount)(uid=%s))
>> 10 credentials_attributes>-uid,userPassword
>> 11
>> 12 userinfo_filter>>---(&(objectClass=posixAccount)(uid=%s))
>> 13 userinfo_attributes>uid,uidNumber,gidNumber,homeDirectory
>> 14
>> 15 alias_filter>--->---(&(objectClass=nisMailAlias)(cn=%s))
>> 16 alias_attributes>---rfc822MailMember
>>
>> ldapd daemon is set up on another host to work over tls and ssl and
>> working correctly.
>>
>> If I change url to ldaps://ldap1.mydomain.ru
>> or to ldap+tls://ldap1.mydomain.ru
>> then smtpd -dv shows:
>> """
>> _
>> vdomains[50952]: warn: ldap_parse_url fail
>> vdomains[50952]: warn: ldap_connect error
>> vdomains[50952]: fatal: failed to connect
>> """
>> _
>>
>
Is the table-procexec a viable alternative?
You can create shell wrappers to call ldap functions
and then call the shell wrappers from procexec with
the correct parameters.
This seems very possible, assuming table-procexec is usable.
Last time I checked, procexec didn't have a lot of documentation.
Best,
Aisha
Re: OpenSMTPD and ldap+tls
December 1, 2020 1:30 PM, "Aisha Tammy" wrote: > On 12/1/20 1:31 AM, Martijn van Duren wrote: > >> Hello, >> >> There is table_ldap in the opensmtpd-extras package, but I've never used >> it, it's undocumented and I've heard that the author sees it as a proof >> of concept only at this point. So no idea how far this will take you, >> but it's your best shot. :-) >> This is based on the aldap.[ch] OpenBSD client, unfortunately the author is missing in action and the code lacks support for several features that have been requested over and over. The backend as is works for common use-cases ... on a local LDAP server, no TLS and no leaf referencing a remote LDAP server. To add support for these, I'd have to actually add support in the aldap client which is not something I want to do as it's unpleasant and I don't even use LDAP to start with :-) > Is the table-procexec a viable alternative? > You can create shell wrappers to call ldap functions > and then call the shell wrappers from procexec with > the correct parameters. > This seems very possible, assuming table-procexec is usable. > Last time I checked, procexec didn't have a lot of documentation. > The table-procexec is just a proof-of-concept to show that table API would be better if it went the procexec way. It does work but it's not polished, can't pass a configuration down to a procexec table backend and requires a table-procexec instance for each procexec backend which is not elegant. Switching table API to procexec in OpenSMTPD would require help upstream.
Re: Installer suggestion
On Tue, Dec 1, 2020 at 4:43 PM Christopher Turkel < turkel.christop...@gmail.com> wrote: > Why would you want that? I’m curious. Just to place it together with the rest of the questions. Bulk them together so to speak. Now the installation waits for input about the timezone, before it continues with relinking the kernel and fills /dev etc. But it doesn't matter. Theo just explained why.
Re: Installer suggestion
Christer Solskogen wrote: > On Tue, Dec 1, 2020 at 4:43 PM Christopher Turkel < > turkel.christop...@gmail.com> wrote: > > > Why would you want that? I’m curious. > > > Just to place it together with the rest of the questions. Bulk them > together so to speak. > Now the installation waits for input about the timezone, before it > continues with relinking the kernel and fills /dev etc. > > But it doesn't matter. Theo just explained why. There have also been proposals that IF we the files are present in the ramdisk, we use them. But then the questions are not in the same order for all install methods. Another proposal was for upgrades if the files exist in the base, we use those. But sometimes new files show up, or old files go away. So again, the order of the questions could vary depending on install or upgrade method. That feels like too much of a surprise, so I have no intention of changing it.
Re: Installer suggestion
On Tue, Dec 1, 2020 at 6:36 PM Theo de Raadt wrote: > > There have also been proposals that IF we the files are present in the > ramdisk, we use them. But then the questions are not in the same order > for all install methods. Another proposal was for upgrades if the files > exist in the base, we use those. But sometimes new files show up, or old > files go away. So again, the order of the questions could vary depending > on install or upgrade method. That feels like too much of a surprise, > so I have no intention of changing it. > And it would probably be too error prone to just accept the input regardless if the timezone exists or not.
Re: OpenSMTPD and ldap+tls
Родин Максим writes: > If I change url to ldaps://ldap1.mydomain.ru > or to ldap+tls://ldap1.mydomain.ru > then smtpd -dv shows: > """ > _ > vdomains[50952]: warn: ldap_parse_url fail > vdomains[50952]: warn: ldap_connect error > vdomains[50952]: fatal: failed to connect > """ > _ > This doesn't directly address your question but might be an alternate way to achieve what you are wanting. I've used spiped from packages when I needed a secure pipe between hosts and could not use TLS for some reason. It's similar in concept to setting up an SSH tunnel but uses a pre-shared symmetric key. In my experience it is more reliable than an long-running SSH connection. Allan
Bridging multiple WAN via VLAN
Hello, I was wondering if and how I could bridge 2 WAN interfaces into single cable over vlan. Sounds cryptic, so let's start with the diagram of what I'd like to achieve: lte wifi \|/ \|/ I have 2 WAN interfaces, LTE and WIFI | |Both are connected to OBSD1 box via | |USB cable, installation is on a rooftop +---+ | OBSD1 | OBSD1 is a raspberry pi 4 network thingy +---+ | From the roof, to my server goes single | CAT5E ethernet cable +---+ | OBSD2 | OBSD2 is a firewall/router +---+ | | | The rest are various computers, I got that | | | part covered | | | LAN DMZ IOT Now, both LTE and WIFI are USB devices that can give OBSD1 direct IP address - like modem. I know I could simply operate OBSD1 like router - install dhcpd to give IP to OBSD2 and forward traffic with pf. But that seems like unnecessary overhead and I'd like to setup packet priority/queueing on OBSD2 and treat OBSD1 like a stupid device. So I was wondering, is it possible to bridge network so that: (it's easier with another diagram) IPIP 1.2.3.4 4.3.2.1 \|/ \|/ | | +-o-*-+ o - lte usb modem; * - wifi usb card | | | | | vlan1 vlan2 | OBSD1 packs raw layer2 frames into | `+' | separate vlans | | | +--o--+ o - em0 interface | | Data goes through single cable | +--o--+ o - em0 interface | | | |.-+-.| OBSD2 unpacks vlan1 and 2 into separate | vlan1 vlan2 | virtual interfaces. | 1.2.3.4 4.3.2.1 | +-+ Now I'd like for vlan1 and vlan2 on OBSD2 to have 1.2.3.4 and 4.3.2.1 IPs, so that I can perform redundancy/load balancing/queueing/whatever directly on OBSD2 device, and treat OBSD1 like some kind of stupid switch/hub. Hope it's clear what I'd like to do. Is it possible? Or am I imaging things and it's better to do it with dhcp/pf routing? If it's possible to do with vlans on layer2, then what am I suppose to look for? I can read man pages, but honestly I don't really know how to approach that problem, so some keywords, programs, rfcs would be nice to have:) Or just tell me I'm stupid and overengineering things and I should go with routing way:) Thanks in advance for any help with this. -- .-.---.-.--. | Michal Lyszczek | Embedded C, Linux | Company Address | .-. open source | | +48 727 564 419 | Software Engineer | Leszczynskiego 4/29 | oo| supporter | | https://bofc.pl `.--: 50-078 Wroclaw, Pol | /`'\ & | | GPG FF1EBFE7E3A974B1 | Bits of Code | NIP: 813 349 58 78 |(\_;/) programer | `--^--^-^--' signature.asc Description: PGP signature
