Re: Screen brightness
$ dmesg OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST 2017 rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8474267648 (8081MB) avail mem = 8212754432 (7832MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6dc0 (71 entries) bios0: vendor LENOVO version "0XCN42WW" date 04/21/2017 bios0: LENOVO 80SR acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA UEFI UEFI SSDT SSDT TPM2 MSDM SSDT DBGP DBG2 ASF! ASPT BOOT DBGP HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT DMAR FPDT acpi0: wakeup devices GLAN(S3) XHC_(S3) XDCI(S4) HDAS(S3) PXSX(S3) RP01(S3) PXSX(S3) RP02(S3) PXSX(S3) RP03(S3) PXSX(S3) RP04(S3) PXSX(S3) RP05(S3) PXSX(S3) RP06(S3) [...] 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-6500U CPU @ 2.50GHz, 2592.00 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 259200 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz, 2592.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT 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, 2592.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT 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, 2592.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,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, 120 pins acpimcfg0 at acpi0 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 2 (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 at acpi0: bus -1 (RP20) acpiec0 at acpi0 acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpibat0 at acpi0: BAT0 model "L15M2PB5" serial 4971 type LiP oem "SMP" "VPC2004" at acpi0 not configured "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "SYN2B59" at acpi0 not configured acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB "PNP0C14" at
Re: Minium System Requirements
> That said, while "minimum requirement" is neither useful nor > understandable, it might be interesting to document nominal > requirements - for example, size of base system on disk and memory > occupied on bootup. The landisk builds are done on a SH4 cpu running at 267 MHz, with 64MB of ram. Network is a 100mbit, the disk drive is a Hitachi CF 8GB disk drive -- yes it fits into a CF socket internally, and it has real spinning parts. That's not the bare minimum to get work done. I am certain a much slower machine would be able to get the work done. The landisk is obviously too much machine for the job, because it spits out a new snapshot every few days. It meets expectations; dare I say it exceeds them. So I encourage everyone to get a machine no faster than this, or perhaps even slower. Perhaps later we can decide who is proving which point. > But - given the undefined free variables - that sort of thing probably > belongs in blog posts rather than on openbsd.org. It's misc, everyone wants a helping hand no matter how silly. I'd like my lawn mowed.
Re: Minium System Requirements
On Sat, Jul 22, 2017 at 4:58 PM, Ingo Schwarzewrote: > Max Power wrote on Sat, Jul 22, 2017 at 10:49:05PM +0200: >> but In addition to your advice... >> possible that there is no official documentation? >> This is the questions...! > > And i already answered that: > > No, there isn't, because: > > 1. It varies from platform to platform. > 2. It varies from time to time. > > 3. It is rarely relevant because application software > usually is the bottleneck in practice, *not* the OS. > > So, 1 & 2 mean that maintaining such a list would cause considerable > work for developers, and 3 means that it would be virtually useless. It's also an ill-defined concept, as you've described fairly well. That said, while "minimum requirement" is neither useful nor understandable, it might be interesting to document nominal requirements - for example, size of base system on disk and memory occupied on bootup. But - given the undefined free variables - that sort of thing probably belongs in blog posts rather than on openbsd.org. Thanks, -- Raul
Re: Lenovo Notebook: No HDMI video output; DRM error; -current MP#115
What happens if you try jcs' intel_backlight utility? https://devhub.io/repos/jcs-intel_backlight_fbsd Take note of the machdep.allowaperture=3 change you need to make to sysctl.conf (requires a reboot). On Sat, Jul 22, 2017 at 5:09 PM, Michel Behrwrote: > Hi - I'm trying to connect my Lenovo Laptop a monitor via HDMI but I'm > getting no output (below I'm including messages regarding xrandr, dmesg, > and Xorg.0.log). > > Any pointing to the right direction would be much appreciated. > > Kind regards, > > Michel. > > > > $ uname -a > > > OpenBSD S400 6.1 GENERIC.MP#115 amd64 > $ dmesg > > > OpenBSD 6.1-current (GENERIC.MP) #96: Thu Jul 13 19:31:55 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > RTC BIOS diagnostic error 80 > real mem = 4140773376 (3948MB) > avail mem = 4009488384 (3823MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6fd0 (61 entries) > bios0: vendor LENOVO version "6DCN92WW(V8.06)" date 02/21/2013 > bios0: LENOVO VIUS3 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC UEFI ASF! HPET APIC MCFG SSDT BOOT ASPT DBGP > FPDT MSDM SSDT SSDT DMAR > acpi0: wakeup devices P0P1(S0) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S0) PXSX(S3) > PXSX(S3) PXSX(S3) PXSX(S3) PXSX(S3) RP05(S0) PXSX(S3) RP06(S0) PXSX(S3) > RP07(S0) PXSX(S3) [...] > 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-3317U CPU @ 1.70GHz, 1696.40 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,CX16, > xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES, > XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC, > FSGSBASE,SMEP,ERMS,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 1696402120 Hz > 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.1.2, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.14 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,CX16, > xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES, > XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC, > FSGSBASE,SMEP,ERMS,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-3317U CPU @ 1.70GHz, 1696.14 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,CX16, > xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES, > XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC, > FSGSBASE,SMEP,ERMS,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-3317U CPU @ 1.70GHz, 1696.14 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,CX16, > xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES, > XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC, > FSGSBASE,SMEP,ERMS,SENSOR,ARAT > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xf000, 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 -1 (RP02) > acpiprt4 at acpi0: bus -1 (RP03) > acpiprt5 at acpi0: bus -1 (RP04) > acpiprt6 at acpi0: bus -1 (RP05) > acpiprt7 at acpi0: bus -1 (RP06) > acpiprt8 at acpi0: bus -1 (RP07) > acpiprt9 at acpi0: bus -1 (RP08) > acpiprt10 at acpi0: bus -1 (PEG0) > acpiprt11 at acpi0: bus -1 (PEG1) > acpiprt12 at acpi0: bus -1 (PEG2) > acpiprt13 at acpi0: bus -1 (PEG3) > acpiec0 at acpi0 > acpicpu0 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpicpu1 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpicpu2 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpicpu3 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpitz0 at acpi0: critical temperature is 127 degC > "INT3F0D" at acpi0 not configured > acpibtn0 at acpi0: PWRB > "IDEA0100" at acpi0 not configured > "SYN2B04" at acpi0 not configured > "VPC2004" at acpi0 not configured > "AOA2011" at acpi0 not configured >
Lenovo Notebook: No HDMI video output; DRM error; -current MP#115
Hi - I'm trying to connect my Lenovo Laptop a monitor via HDMI but I'm getting no output (below I'm including messages regarding xrandr, dmesg, and Xorg.0.log). Any pointing to the right direction would be much appreciated. Kind regards, Michel. $ uname -a OpenBSD S400 6.1 GENERIC.MP#115 amd64 $ dmesg OpenBSD 6.1-current (GENERIC.MP) #96: Thu Jul 13 19:31:55 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 4140773376 (3948MB) avail mem = 4009488384 (3823MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6fd0 (61 entries) bios0: vendor LENOVO version "6DCN92WW(V8.06)" date 02/21/2013 bios0: LENOVO VIUS3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC UEFI ASF! HPET APIC MCFG SSDT BOOT ASPT DBGP FPDT MSDM SSDT SSDT DMAR acpi0: wakeup devices P0P1(S0) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S0) PXSX(S3) PXSX(S3) PXSX(S3) PXSX(S3) PXSX(S3) RP05(S0) PXSX(S3) RP06(S0) PXSX(S3) RP07(S0) PXSX(S3) [...] 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-3317U CPU @ 1.70GHz, 1696.40 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 1696402120 Hz 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.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.14 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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-3317U CPU @ 1.70GHz, 1696.14 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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-3317U CPU @ 1.70GHz, 1696.14 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf000, 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 -1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0 acpicpu0 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 127 degC "INT3F0D" at acpi0 not configured acpibtn0 at acpi0: PWRB "IDEA0100" at acpi0 not configured "SYN2B04" at acpi0 not configured "VPC2004" at acpi0 not configured "AOA2011" at acpi0 not configured acpibat0 at acpi0: BAT1 model "PABAS0241231" serial 41167 type Li-Ion oem "LENOVO " acpiac0 at acpi0: AC unit online acpibtn1 at acpi0: LID0 "INT340E" at acpi0 not configured acpivideo0 at acpi0: VGA_ acpivideo1 at acpi0: VGA_ acpivideo2 at acpi0: GFX0 acpivout0 at acpivideo2: DD02 cpu0: Enhanced SpeedStep 1696 MHz: speeds: 1701, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800, 782 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD
Re: Screen brightness
You are welcome, Mr G Just one more thing: you should share your dmesg in order to know all the hw involved in this drama :) Manuel > El 22/07/2017, a las 17:30, Gescribió: > > Yes. Didn't work. fw_update updates vmm uvideo and iwm. > > Anyway thanks for your replies! > >> On 07/23/17 01:22, Manuel Solis wrote: >> To bad, that is beyond my knowledge :s >> >> Have you tried >> #fw_update >> ??? >> >> Manuel >> >>> El 22/07/2017, a las 17:13, G escribió: >>> >>> Thanks for your replies. >>> >>> I get >>> >>> # xrandr --query >>> xrandr: Failed to get size of gamma for output default >>> Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 >>> default connected 1920x1080+0+0 0mm x 0mm >>> 1920x1080 0.00* >>> >>> I don't know if its a problem with skylake since openbsd 6.1 stable >>> doesn't support it yet. >>> >>> >>> On 07/23/17 00:53, Manuel Solis wrote: Hello again, Then you should use xrandr $xrandr --query To know which devices you have $xrandr --output LVDS1 --auto To enable the monitor (LVDS1/VGA1/HDMI1) $xrandr --output LVDS1 --set BACKLIGHT 50 to adjust the backlight try for instance 50, 99, 05 and see how it goes Manuel > El 22/07/2017, a las 16:20, G escribió: > > Thanks for the reply but it doesn't work. > >> On 07/23/17 00:11, Manuel Solis wrote: >> Hello, Mr G >> >> Try this two: >> $xbacklight -set 99 >> >> $xbacklight -set 50 >> >> If you see something different then it works!! >> >> Manuel >> >>> El 22/07/2017, a las 14:48, G escribió: >>> >>> Hello. >>> I'm trying to adjust my laptop brightness. >>> When I'm trying to use xbacklight i get >>> >>> #xbacklight >>> >>> No outputs have backlight property >>> >>> I search around and it seems that xbacklight is broken. I found this >>> email >>> https://marc.info/?l=openbsd-bugs=149919062727474 >>> >>> that suggested to use wsconsctl but it doesn't seems to work. Although >>> the value of wsconsctl display.brightness changes the screen brightness >>> doesn't change. >>> >>> # wsconsctl >>> keyboard.type=pc-xt >>> keyboard.bell.pitch=400 >>> keyboard.bell.period=100 >>> keyboard.bell.volume=50 >>> keyboard.bell.pitch.default=400 >>> keyboard.bell.period.default=100 >>> keyboard.bell.volume.default=50 >>> wsconsctl: Use explicit arg to view keyboard.map. >>> keyboard.repeat.del1=400 >>> keyboard.repeat.deln=100 >>> keyboard.repeat.del1.default=400 >>> keyboard.repeat.deln.default=100 >>> keyboard.ledstate=2 >>> keyboard.encoding=us >>> mouse.type=synaptics >>> mouse.rawmode=0 >>> mouse.scale=1472,5670,1408,4794,0,44,76 >>> mouse1.type=usb >>> mouse1.rawmode=1 >>> mouse1.scale=0,0,0,0,0,0,0 >>> display.type=vga-pci >>> display.emulations=vt100 >>> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >>> display.focus=4 >>> display.brightness=100.00% >>> display.screen_on=250 >>> display.screen_off=0 >>> display.vblank=off >>> display.kbdact=on >>> display.msact=on >>> display.outact=on >>> # wsconsctl display.brightness=20 >>> display.brightness -> 20.00% >>> # wsconsctl >>> keyboard.type=pc-xt >>> keyboard.bell.pitch=400 >>> keyboard.bell.period=100 >>> keyboard.bell.volume=50 >>> keyboard.bell.pitch.default=400 >>> keyboard.bell.period.default=100 >>> keyboard.bell.volume.default=50 >>> wsconsctl: Use explicit arg to view keyboard.map. >>> keyboard.repeat.del1=400 >>> keyboard.repeat.deln=100 >>> keyboard.repeat.del1.default=400 >>> keyboard.repeat.deln.default=100 >>> keyboard.ledstate=2 >>> keyboard.encoding=us >>> mouse.type=synaptics >>> mouse.rawmode=0 >>> mouse.scale=1472,5670,1408,4794,0,44,76 >>> mouse1.type=usb >>> mouse1.rawmode=1 >>> mouse1.scale=0,0,0,0,0,0,0 >>> display.type=vga-pci >>> display.emulations=vt100 >>> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >>> display.focus=4 >>> display.brightness=20.00% >>> display.screen_on=250 >>> display.screen_off=0 >>> display.vblank=off >>> display.kbdact=on >>> display.msact=on >>> display.outact=on >>> > >>> >
Re: Screen brightness
Yes. Didn't work. fw_update updates vmm uvideo and iwm. Anyway thanks for your replies! On 07/23/17 01:22, Manuel Solis wrote: > To bad, that is beyond my knowledge :s > > Have you tried > #fw_update > ??? > > Manuel > >> El 22/07/2017, a las 17:13, Gescribió: >> >> Thanks for your replies. >> >> I get >> >> # xrandr --query >> xrandr: Failed to get size of gamma for output default >> Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 >> default connected 1920x1080+0+0 0mm x 0mm >> 1920x1080 0.00* >> >> I don't know if its a problem with skylake since openbsd 6.1 stable >> doesn't support it yet. >> >> >> >>> On 07/23/17 00:53, Manuel Solis wrote: >>> Hello again, >>> >>> Then you should use xrandr >>> >>> $xrandr --query >>> To know which devices you have >>> >>> $xrandr --output LVDS1 --auto >>> To enable the monitor (LVDS1/VGA1/HDMI1) >>> >>> $xrandr --output LVDS1 --set BACKLIGHT 50 >>> to adjust the backlight >>> >>> try for instance 50, 99, 05 and see how it goes >>> >>> >>> Manuel >>> El 22/07/2017, a las 16:20, G escribió: Thanks for the reply but it doesn't work. > On 07/23/17 00:11, Manuel Solis wrote: > Hello, Mr G > > Try this two: > $xbacklight -set 99 > > $xbacklight -set 50 > > If you see something different then it works!! > > Manuel > >> El 22/07/2017, a las 14:48, G escribió: >> >> Hello. >> I'm trying to adjust my laptop brightness. >> When I'm trying to use xbacklight i get >> >> #xbacklight >> >> No outputs have backlight property >> >> I search around and it seems that xbacklight is broken. I found this >> email >> https://marc.info/?l=openbsd-bugs=149919062727474 >> >> that suggested to use wsconsctl but it doesn't seems to work. Although >> the value of wsconsctl display.brightness changes the screen brightness >> doesn't change. >> >> # wsconsctl >> keyboard.type=pc-xt >> keyboard.bell.pitch=400 >> keyboard.bell.period=100 >> keyboard.bell.volume=50 >> keyboard.bell.pitch.default=400 >> keyboard.bell.period.default=100 >> keyboard.bell.volume.default=50 >> wsconsctl: Use explicit arg to view keyboard.map. >> keyboard.repeat.del1=400 >> keyboard.repeat.deln=100 >> keyboard.repeat.del1.default=400 >> keyboard.repeat.deln.default=100 >> keyboard.ledstate=2 >> keyboard.encoding=us >> mouse.type=synaptics >> mouse.rawmode=0 >> mouse.scale=1472,5670,1408,4794,0,44,76 >> mouse1.type=usb >> mouse1.rawmode=1 >> mouse1.scale=0,0,0,0,0,0,0 >> display.type=vga-pci >> display.emulations=vt100 >> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >> display.focus=4 >> display.brightness=100.00% >> display.screen_on=250 >> display.screen_off=0 >> display.vblank=off >> display.kbdact=on >> display.msact=on >> display.outact=on >> # wsconsctl display.brightness=20 >> display.brightness -> 20.00% >> # wsconsctl >> keyboard.type=pc-xt >> keyboard.bell.pitch=400 >> keyboard.bell.period=100 >> keyboard.bell.volume=50 >> keyboard.bell.pitch.default=400 >> keyboard.bell.period.default=100 >> keyboard.bell.volume.default=50 >> wsconsctl: Use explicit arg to view keyboard.map. >> keyboard.repeat.del1=400 >> keyboard.repeat.deln=100 >> keyboard.repeat.del1.default=400 >> keyboard.repeat.deln.default=100 >> keyboard.ledstate=2 >> keyboard.encoding=us >> mouse.type=synaptics >> mouse.rawmode=0 >> mouse.scale=1472,5670,1408,4794,0,44,76 >> mouse1.type=usb >> mouse1.rawmode=1 >> mouse1.scale=0,0,0,0,0,0,0 >> display.type=vga-pci >> display.emulations=vt100 >> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >> display.focus=4 >> display.brightness=20.00% >> display.screen_on=250 >> display.screen_off=0 >> display.vblank=off >> display.kbdact=on >> display.msact=on >> display.outact=on >> >>
Re: Screen brightness
To bad, that is beyond my knowledge :s Have you tried #fw_update ??? Manuel > El 22/07/2017, a las 17:13, Gescribió: > > Thanks for your replies. > > I get > > # xrandr --query > xrandr: Failed to get size of gamma for output default > Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 > default connected 1920x1080+0+0 0mm x 0mm > 1920x1080 0.00* > > I don't know if its a problem with skylake since openbsd 6.1 stable > doesn't support it yet. > > > >> On 07/23/17 00:53, Manuel Solis wrote: >> Hello again, >> >> Then you should use xrandr >> >> $xrandr --query >> To know which devices you have >> >> $xrandr --output LVDS1 --auto >> To enable the monitor (LVDS1/VGA1/HDMI1) >> >> $xrandr --output LVDS1 --set BACKLIGHT 50 >> to adjust the backlight >> >> try for instance 50, 99, 05 and see how it goes >> >> >> Manuel >> >>> El 22/07/2017, a las 16:20, G escribió: >>> >>> Thanks for the reply but it doesn't work. >>> On 07/23/17 00:11, Manuel Solis wrote: Hello, Mr G Try this two: $xbacklight -set 99 $xbacklight -set 50 If you see something different then it works!! Manuel > El 22/07/2017, a las 14:48, G escribió: > > Hello. > I'm trying to adjust my laptop brightness. > When I'm trying to use xbacklight i get > > #xbacklight > > No outputs have backlight property > > I search around and it seems that xbacklight is broken. I found this email > https://marc.info/?l=openbsd-bugs=149919062727474 > > that suggested to use wsconsctl but it doesn't seems to work. Although > the value of wsconsctl display.brightness changes the screen brightness > doesn't change. > > # wsconsctl > keyboard.type=pc-xt > keyboard.bell.pitch=400 > keyboard.bell.period=100 > keyboard.bell.volume=50 > keyboard.bell.pitch.default=400 > keyboard.bell.period.default=100 > keyboard.bell.volume.default=50 > wsconsctl: Use explicit arg to view keyboard.map. > keyboard.repeat.del1=400 > keyboard.repeat.deln=100 > keyboard.repeat.del1.default=400 > keyboard.repeat.deln.default=100 > keyboard.ledstate=2 > keyboard.encoding=us > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5670,1408,4794,0,44,76 > mouse1.type=usb > mouse1.rawmode=1 > mouse1.scale=0,0,0,0,0,0,0 > display.type=vga-pci > display.emulations=vt100 > display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf > display.focus=4 > display.brightness=100.00% > display.screen_on=250 > display.screen_off=0 > display.vblank=off > display.kbdact=on > display.msact=on > display.outact=on > # wsconsctl display.brightness=20 > display.brightness -> 20.00% > # wsconsctl > keyboard.type=pc-xt > keyboard.bell.pitch=400 > keyboard.bell.period=100 > keyboard.bell.volume=50 > keyboard.bell.pitch.default=400 > keyboard.bell.period.default=100 > keyboard.bell.volume.default=50 > wsconsctl: Use explicit arg to view keyboard.map. > keyboard.repeat.del1=400 > keyboard.repeat.deln=100 > keyboard.repeat.del1.default=400 > keyboard.repeat.deln.default=100 > keyboard.ledstate=2 > keyboard.encoding=us > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5670,1408,4794,0,44,76 > mouse1.type=usb > mouse1.rawmode=1 > mouse1.scale=0,0,0,0,0,0,0 > display.type=vga-pci > display.emulations=vt100 > display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf > display.focus=4 > display.brightness=20.00% > display.screen_on=250 > display.screen_off=0 > display.vblank=off > display.kbdact=on > display.msact=on > display.outact=on > >>> >
Re: Screen brightness
Thanks for your replies. I get # xrandr --query xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 0.00* I don't know if its a problem with skylake since openbsd 6.1 stable doesn't support it yet. On 07/23/17 00:53, Manuel Solis wrote: > Hello again, > > Then you should use xrandr > > $xrandr --query > To know which devices you have > > $xrandr --output LVDS1 --auto > To enable the monitor (LVDS1/VGA1/HDMI1) > > $xrandr --output LVDS1 --set BACKLIGHT 50 > to adjust the backlight > > try for instance 50, 99, 05 and see how it goes > > > Manuel > >> El 22/07/2017, a las 16:20, Gescribió: >> >> Thanks for the reply but it doesn't work. >> >>> On 07/23/17 00:11, Manuel Solis wrote: >>> Hello, Mr G >>> >>> Try this two: >>> $xbacklight -set 99 >>> >>> $xbacklight -set 50 >>> >>> If you see something different then it works!! >>> >>> Manuel >>> El 22/07/2017, a las 14:48, G escribió: Hello. I'm trying to adjust my laptop brightness. When I'm trying to use xbacklight i get #xbacklight No outputs have backlight property I search around and it seems that xbacklight is broken. I found this email https://marc.info/?l=openbsd-bugs=149919062727474 that suggested to use wsconsctl but it doesn't seems to work. Although the value of wsconsctl display.brightness changes the screen brightness doesn't change. # wsconsctl keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard.map. keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=2 keyboard.encoding=us mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5670,1408,4794,0,44,76 mouse1.type=usb mouse1.rawmode=1 mouse1.scale=0,0,0,0,0,0,0 display.type=vga-pci display.emulations=vt100 display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf display.focus=4 display.brightness=100.00% display.screen_on=250 display.screen_off=0 display.vblank=off display.kbdact=on display.msact=on display.outact=on # wsconsctl display.brightness=20 display.brightness -> 20.00% # wsconsctl keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard.map. keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=2 keyboard.encoding=us mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5670,1408,4794,0,44,76 mouse1.type=usb mouse1.rawmode=1 mouse1.scale=0,0,0,0,0,0,0 display.type=vga-pci display.emulations=vt100 display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf display.focus=4 display.brightness=20.00% display.screen_on=250 display.screen_off=0 display.vblank=off display.kbdact=on display.msact=on display.outact=on >>
Re: Screen brightness
Hello again, Then you should use xrandr $xrandr --query To know which devices you have $xrandr --output LVDS1 --auto To enable the monitor (LVDS1/VGA1/HDMI1) $xrandr --output LVDS1 --set BACKLIGHT 50 to adjust the backlight try for instance 50, 99, 05 and see how it goes Manuel > El 22/07/2017, a las 16:20, Gescribió: > > Thanks for the reply but it doesn't work. > >> On 07/23/17 00:11, Manuel Solis wrote: >> Hello, Mr G >> >> Try this two: >> $xbacklight -set 99 >> >> $xbacklight -set 50 >> >> If you see something different then it works!! >> >> Manuel >> >>> El 22/07/2017, a las 14:48, G escribió: >>> >>> Hello. >>> I'm trying to adjust my laptop brightness. >>> When I'm trying to use xbacklight i get >>> >>> #xbacklight >>> >>> No outputs have backlight property >>> >>> I search around and it seems that xbacklight is broken. I found this email >>> https://marc.info/?l=openbsd-bugs=149919062727474 >>> >>> that suggested to use wsconsctl but it doesn't seems to work. Although >>> the value of wsconsctl display.brightness changes the screen brightness >>> doesn't change. >>> >>> # wsconsctl >>> keyboard.type=pc-xt >>> keyboard.bell.pitch=400 >>> keyboard.bell.period=100 >>> keyboard.bell.volume=50 >>> keyboard.bell.pitch.default=400 >>> keyboard.bell.period.default=100 >>> keyboard.bell.volume.default=50 >>> wsconsctl: Use explicit arg to view keyboard.map. >>> keyboard.repeat.del1=400 >>> keyboard.repeat.deln=100 >>> keyboard.repeat.del1.default=400 >>> keyboard.repeat.deln.default=100 >>> keyboard.ledstate=2 >>> keyboard.encoding=us >>> mouse.type=synaptics >>> mouse.rawmode=0 >>> mouse.scale=1472,5670,1408,4794,0,44,76 >>> mouse1.type=usb >>> mouse1.rawmode=1 >>> mouse1.scale=0,0,0,0,0,0,0 >>> display.type=vga-pci >>> display.emulations=vt100 >>> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >>> display.focus=4 >>> display.brightness=100.00% >>> display.screen_on=250 >>> display.screen_off=0 >>> display.vblank=off >>> display.kbdact=on >>> display.msact=on >>> display.outact=on >>> # wsconsctl display.brightness=20 >>> display.brightness -> 20.00% >>> # wsconsctl >>> keyboard.type=pc-xt >>> keyboard.bell.pitch=400 >>> keyboard.bell.period=100 >>> keyboard.bell.volume=50 >>> keyboard.bell.pitch.default=400 >>> keyboard.bell.period.default=100 >>> keyboard.bell.volume.default=50 >>> wsconsctl: Use explicit arg to view keyboard.map. >>> keyboard.repeat.del1=400 >>> keyboard.repeat.deln=100 >>> keyboard.repeat.del1.default=400 >>> keyboard.repeat.deln.default=100 >>> keyboard.ledstate=2 >>> keyboard.encoding=us >>> mouse.type=synaptics >>> mouse.rawmode=0 >>> mouse.scale=1472,5670,1408,4794,0,44,76 >>> mouse1.type=usb >>> mouse1.rawmode=1 >>> mouse1.scale=0,0,0,0,0,0,0 >>> display.type=vga-pci >>> display.emulations=vt100 >>> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >>> display.focus=4 >>> display.brightness=20.00% >>> display.screen_on=250 >>> display.screen_off=0 >>> display.vblank=off >>> display.kbdact=on >>> display.msact=on >>> display.outact=on >>> >
Re: Screen brightness
Thanks for the reply but it doesn't work. On 07/23/17 00:11, Manuel Solis wrote: > Hello, Mr G > > Try this two: > $xbacklight -set 99 > > $xbacklight -set 50 > > If you see something different then it works!! > > Manuel > >> El 22/07/2017, a las 14:48, Gescribió: >> >> Hello. >> I'm trying to adjust my laptop brightness. >> When I'm trying to use xbacklight i get >> >> #xbacklight >> >> No outputs have backlight property >> >> I search around and it seems that xbacklight is broken. I found this email >> https://marc.info/?l=openbsd-bugs=149919062727474 >> >> that suggested to use wsconsctl but it doesn't seems to work. Although >> the value of wsconsctl display.brightness changes the screen brightness >> doesn't change. >> >> # wsconsctl >> keyboard.type=pc-xt >> keyboard.bell.pitch=400 >> keyboard.bell.period=100 >> keyboard.bell.volume=50 >> keyboard.bell.pitch.default=400 >> keyboard.bell.period.default=100 >> keyboard.bell.volume.default=50 >> wsconsctl: Use explicit arg to view keyboard.map. >> keyboard.repeat.del1=400 >> keyboard.repeat.deln=100 >> keyboard.repeat.del1.default=400 >> keyboard.repeat.deln.default=100 >> keyboard.ledstate=2 >> keyboard.encoding=us >> mouse.type=synaptics >> mouse.rawmode=0 >> mouse.scale=1472,5670,1408,4794,0,44,76 >> mouse1.type=usb >> mouse1.rawmode=1 >> mouse1.scale=0,0,0,0,0,0,0 >> display.type=vga-pci >> display.emulations=vt100 >> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >> display.focus=4 >> display.brightness=100.00% >> display.screen_on=250 >> display.screen_off=0 >> display.vblank=off >> display.kbdact=on >> display.msact=on >> display.outact=on >> # wsconsctl display.brightness=20 >> display.brightness -> 20.00% >> # wsconsctl >> keyboard.type=pc-xt >> keyboard.bell.pitch=400 >> keyboard.bell.period=100 >> keyboard.bell.volume=50 >> keyboard.bell.pitch.default=400 >> keyboard.bell.period.default=100 >> keyboard.bell.volume.default=50 >> wsconsctl: Use explicit arg to view keyboard.map. >> keyboard.repeat.del1=400 >> keyboard.repeat.deln=100 >> keyboard.repeat.del1.default=400 >> keyboard.repeat.deln.default=100 >> keyboard.ledstate=2 >> keyboard.encoding=us >> mouse.type=synaptics >> mouse.rawmode=0 >> mouse.scale=1472,5670,1408,4794,0,44,76 >> mouse1.type=usb >> mouse1.rawmode=1 >> mouse1.scale=0,0,0,0,0,0,0 >> display.type=vga-pci >> display.emulations=vt100 >> display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf >> display.focus=4 >> display.brightness=20.00% >> display.screen_on=250 >> display.screen_off=0 >> display.vblank=off >> display.kbdact=on >> display.msact=on >> display.outact=on >>
Re: Screen brightness
Hello, Mr G Try this two: $xbacklight -set 99 $xbacklight -set 50 If you see something different then it works!! Manuel > El 22/07/2017, a las 14:48, Gescribió: > > Hello. > I'm trying to adjust my laptop brightness. > When I'm trying to use xbacklight i get > > #xbacklight > > No outputs have backlight property > > I search around and it seems that xbacklight is broken. I found this email > https://marc.info/?l=openbsd-bugs=149919062727474 > > that suggested to use wsconsctl but it doesn't seems to work. Although > the value of wsconsctl display.brightness changes the screen brightness > doesn't change. > > # wsconsctl > keyboard.type=pc-xt > keyboard.bell.pitch=400 > keyboard.bell.period=100 > keyboard.bell.volume=50 > keyboard.bell.pitch.default=400 > keyboard.bell.period.default=100 > keyboard.bell.volume.default=50 > wsconsctl: Use explicit arg to view keyboard.map. > keyboard.repeat.del1=400 > keyboard.repeat.deln=100 > keyboard.repeat.del1.default=400 > keyboard.repeat.deln.default=100 > keyboard.ledstate=2 > keyboard.encoding=us > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5670,1408,4794,0,44,76 > mouse1.type=usb > mouse1.rawmode=1 > mouse1.scale=0,0,0,0,0,0,0 > display.type=vga-pci > display.emulations=vt100 > display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf > display.focus=4 > display.brightness=100.00% > display.screen_on=250 > display.screen_off=0 > display.vblank=off > display.kbdact=on > display.msact=on > display.outact=on > # wsconsctl display.brightness=20 > display.brightness -> 20.00% > # wsconsctl > keyboard.type=pc-xt > keyboard.bell.pitch=400 > keyboard.bell.period=100 > keyboard.bell.volume=50 > keyboard.bell.pitch.default=400 > keyboard.bell.period.default=100 > keyboard.bell.volume.default=50 > wsconsctl: Use explicit arg to view keyboard.map. > keyboard.repeat.del1=400 > keyboard.repeat.deln=100 > keyboard.repeat.del1.default=400 > keyboard.repeat.deln.default=100 > keyboard.ledstate=2 > keyboard.encoding=us > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5670,1408,4794,0,44,76 > mouse1.type=usb > mouse1.rawmode=1 > mouse1.scale=0,0,0,0,0,0,0 > display.type=vga-pci > display.emulations=vt100 > display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf > display.focus=4 > display.brightness=20.00% > display.screen_on=250 > display.screen_off=0 > display.vblank=off > display.kbdact=on > display.msact=on > display.outact=on >
Re: Minium System Requirements
Max Power wrote on Sat, Jul 22, 2017 at 10:49:05PM +0200: > but In addition to your advice... > possible that there is no official documentation? > This is the questions...! And i already answered that: No, there isn't, because: 1. It varies from platform to platform. 2. It varies from time to time. 3. It is rarely relevant because application software usually is the bottleneck in practice, *not* the OS. So, 1 & 2 mean that maintaining such a list would cause considerable work for developers, and 3 means that it would be virtually useless. That's why we don't do it. Yours, Ingo
Re: Minium System Requirements
Thank guys, but In addition to your advice... possible that there is no official documentation? This is the questions...!
Screen brightness
Hello. I'm trying to adjust my laptop brightness. When I'm trying to use xbacklight i get #xbacklight No outputs have backlight property I search around and it seems that xbacklight is broken. I found this email https://marc.info/?l=openbsd-bugs=149919062727474 that suggested to use wsconsctl but it doesn't seems to work. Although the value of wsconsctl display.brightness changes the screen brightness doesn't change. # wsconsctl keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard.map. keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=2 keyboard.encoding=us mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5670,1408,4794,0,44,76 mouse1.type=usb mouse1.rawmode=1 mouse1.scale=0,0,0,0,0,0,0 display.type=vga-pci display.emulations=vt100 display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf display.focus=4 display.brightness=100.00% display.screen_on=250 display.screen_off=0 display.vblank=off display.kbdact=on display.msact=on display.outact=on # wsconsctl display.brightness=20 display.brightness -> 20.00% # wsconsctl keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard.map. keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=2 keyboard.encoding=us mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5670,1408,4794,0,44,76 mouse1.type=usb mouse1.rawmode=1 mouse1.scale=0,0,0,0,0,0,0 display.type=vga-pci display.emulations=vt100 display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf display.focus=4 display.brightness=20.00% display.screen_on=250 display.screen_off=0 display.vblank=off display.kbdact=on display.msact=on display.outact=on
Re: Minium System Requirements
On 07/22/17 13:45, Max Power wrote: > Hi guys, > I'm looking for on http://www.openbsd.org but... > Where Can I find the official documentation about the 'minimum system > requirements' about OpenBSD? > > Thanks. "less than your application needs". Really. You will have trouble finding an example machine of any platform that runs OpenBSD that won't work. Stupidly low-end limitations: * 80386 and before won't work (this was killed probably 15 years ago. No one noticed) * 486SX won't work (needs hw FPU) (This was plus or minus a release from the 80386 termination. Few people noticed). * 16M will probably not work anymore. Last I tried, it was in swap before the login prompt. * 32M will probably let you log in before swapping. But there will be swapping. * 64M is useful for SSH tunnels and simple firewall use. Now, if you are a new user to OpenBSD, if you are wanting to make a firewall for your home, I'd say a Pentium II or P3, 256M RAM, 40G disk, and a couple decent PCI NICs would be a good starting point. COULD you do it with a Pentium 1 system? yeah, but it will try your patience, and that's generally a bad idea for new users. You really want to say, "What happens if I do *THIS* wrong", totally hose the system, and rebuild it a few times to get comfortable with an OS, and that's hard to do if a reload takes half an hour or an hour or more. If you are looking to run a GUI and a browser, um...well, I'd say at least a dual core system with 2G RAM to start with...and I recently gave up on a three core 4G system, because Firefox, Chrome, and Thunderbird would drive it into swap after a few days up-time. But this is purely an application issue; I've got a PII system with 256M RAM that's quite useful with a gui as a terminal server. Bottom end "useful" systems I've found current use for: first generation Soekris systems with 64M RAM, 486-133mhz, 2G CF storage. They make nice OpenBSD protectors for things like Dell DRAC cards on systems in data centers. SSH to the box with ssh tunnels set up, now have full DRAC access to the machines, without exposing the very soft DRAC directly to the network. HOWEVER, be aware, OpenBSD is loaded with modern (i.e., CPU intensive) cryptography. It will WORK with very old processors, but you won't enjoy it. Nick.
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
thanks! it worked! On 07/22/17 20:54, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 08:38:56PM +0300, G wrote: >> I get the following messages >> >> # vmd -vd >> vmd: /dev/vmm: Operation not supported by device > > The vmm(4) driver requires hardware virtualization features, and if you > have the right hardware, may require you to enable them in your BIOS. > Your dmesg(8) will note if the kernel can load the vmm() driver. For > example, mine shows: > > vmm0 at mainbus0: VMX/EPT >
usb RTC, was Re: octeon port, ubiquity edgerouter
On 07/22/17 12:10, Theo de Raadt wrote: I'd really like if someone could find a USB RTC clock, which is a viable affordable product which we can then create good support for. I've searched and found a few prototypes and 'licence key' products, but nothing readily available which we could support & encourage as a solution for the RTC problem. What kind of packaging, fit & finish, and price would be acceptable? For example: A commodity microcontroller on a tiny PCB, a Dallas Semi RTC on another tiny commodity PCB and a lithium coin cell in a 4cm x 6cm x 2cm commodity box could be professionally assembled and sold in unit quantities in a month for $50. Accuracy limit is the 32Khz crystal. Temperature compensation to match the standard quartz curves in the ucode. Burn-in and trimming to a few PPM would add maybe $5. The same parts on a single PCB in a slightly smaller box might take three months, an expected sale quantity of 50, and sell for $30. USB stick size, etc. - I'm sure you can extrapolate from there. Geoff Steckel
Re: Minium System Requirements
Hi, Max Power wrote on Sat, Jul 22, 2017 at 07:45:15PM +0200: > I'm looking for on http://www.openbsd.org but... > Where Can I find the official documentation about > the 'minimum system requirements' about OpenBSD? That varies from architecture to architecture and from time to time, so there is no official statement. To provide an example for i386, i ran OpenBSD in production on 486-SX25 with 16 MB of RAM and 200 MB of HD disk space several years ago, and less than 100 MB of the disk space were actually used. Nowadays, you would probably need at least 486DX, about 64 MB of RAM, and about 1 GB of HD disk space. For other architectures, your mileage may vary. In any case, you need an FPU and an RTC. That said, your question rarely matters in practice. For almost any practical application, what matters is the resource hunger of the application programs you want to run, not the minimum requirements of OpenBSD. You want to run a graphical web browser? Well, don't try that with 64 MB of RAM and 1 GB of disk. Yours, Ingo
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
On Sat, Jul 22, 2017 at 08:38:56PM +0300, G wrote: > I get the following messages > > # vmd -vd > vmd: /dev/vmm: Operation not supported by device The vmm(4) driver requires hardware virtualization features, and if you have the right hardware, may require you to enable them in your BIOS. Your dmesg(8) will note if the kernel can load the vmm() driver. For example, mine shows: vmm0 at mainbus0: VMX/EPT
Minium System Requirements
Hi guys, I'm looking for on http://www.openbsd.org but... Where Can I find the official documentation about the 'minimum system requirements' about OpenBSD? Thanks.
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
I get the following messages # vmd -vd vmd: /dev/vmm: Operation not supported by device On 07/22/17 20:24, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 01:21:33PM -0400, I wrote: > >> # vmd -v > > I'd like to correct this. Add -d to prevent running in the background, > and log output to stderr. > > # vmd -dv >
Re: octeon port, ubiquity edgerouter
W dniu 2017-07-22 o 17:55, Sean Murphy pisze: On Sat, Jul 22, 2017 at 5:46 AM, Peter J. Philippwrote: Hi, Someone has offered me a deal on a somewhat used Ubiquiti Edgerouter, https://www.ubnt.com/edgemax/edgerouter/ <-- this one. Is it supported by OpenBSD/octeon and if not what needs to be done to make it work? Has anyone experience with this hardware? Regards, -peter Hi Peter, This is a solid machine, if you can get it, do so. OpenBSD 6.1 works very well on this hardware, I have used mine variously as a gateway router with PF, DHCP server, DNS server with unbound, and local name server with nsd. Currently it's acting as local name server while standing as backup router/nameserver/dhcp if needed. You will have to have valid time servers as the ERL doesn't have an internal clock. Have fun! Here's a dmesg: [...] Judging by your dmesg, Sean, you are describing EdgeRouter Lite (https://www.ubnt.com/edgemax/edgerouter-lite/), while Peter was asking about EdgeRouter (https://www.ubnt.com/edgemax/edgerouter/). BTW, it's really great to see now we have not 2, but 4 models of Ubiquiti routers supported! (https://www.openbsd.org/octeon.html) -- Cheers, Pawel Waga
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
On Sat, Jul 22, 2017 at 01:21:33PM -0400, I wrote: > # vmd -v I'd like to correct this. Add -d to prevent running in the background, and log output to stderr. # vmd -dv
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
On Sat, Jul 22, 2017 at 08:13:03PM +0300, G wrote: > I already enable vmd. I though enable vmd was enough > I haven't run rcctl start vmd but when I tried it I get > # rcctl start vmd > vmd(failed) Pick an option: 1. Re-run rcctl with debugging output: # rcctl -d start vmd 2. Run vmd manually. Per the vmd(8) man page, you may add -v one or more times for additional information. # vmd -v > On 07/22/17 20:03, Josh Grosse wrote: > > On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: > >> Hello. > >> Im following vmctl manual and i get. > >> > >> # vmctl create disk.img -s 4.5G > >> vmctl: imagefile created > >> # vmctl start "myvm" -m 1G -i 1 -b /bsd -d disk.img > >> vmctl: connect: /var/run/vmd.sock: No such file or directory > >> > >> Any ideas? > > > > You must start the vmd(8) daemon. > > > > # rcctl enable vmd > > # rcctl start vmd > > >
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
I already enable vmd. I though enable vmd was enough I haven't run rcctl start vmd but when I tried it I get # rcctl start vmd vmd(failed) On 07/22/17 20:03, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: >> Hello. >> Im following vmctl manual and i get. >> >> # vmctl create disk.img -s 4.5G >> vmctl: imagefile created >> # vmctl start "myvm" -m 1G -i 1 -b /bsd -d disk.img >> vmctl: connect: /var/run/vmd.sock: No such file or directory >> >> Any ideas? > > You must start the vmd(8) daemon. > > # rcctl enable vmd > # rcctl start vmd >
Re: vmctl: connect: /var/run/vmd.sock: No such file or directory
On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: > Hello. > Im following vmctl manual and i get. > > # vmctl create disk.img -s 4.5G > vmctl: imagefile created > # vmctl start "myvm" -m 1G -i 1 -b /bsd -d disk.img > vmctl: connect: /var/run/vmd.sock: No such file or directory > > Any ideas? You must start the vmd(8) daemon. # rcctl enable vmd # rcctl start vmd
vmctl: connect: /var/run/vmd.sock: No such file or directory
Hello. Im following vmctl manual and i get. # vmctl create disk.img -s 4.5G vmctl: imagefile created # vmctl start "myvm" -m 1G -i 1 -b /bsd -d disk.img vmctl: connect: /var/run/vmd.sock: No such file or directory Any ideas? Thanks in advance for your help. ps. Im running openbsd 6.1 stable
Re: octeon port, ubiquity edgerouter
> > This is a solid machine, if you can get it, do so. OpenBSD 6.1 works > > very well on this hardware, I have used mine variously as a gateway > > router with PF, DHCP server, DNS server with unbound, and local name > > server with nsd. Currently it's acting as local name server while > > standing as backup router/nameserver/dhcp if needed. You will have to > > have valid time servers as the ERL doesn't have an internal clock. > > Have fun! I'd really like if someone could find a USB RTC clock, which is a viable affordable product which we can then create good support for. I've searched and found a few prototypes and 'licence key' products, but nothing readily available which we could support & encourage as a solution for the RTC problem.
Re: octeon port, ubiquity edgerouter
On Sat, Jul 22, 2017 at 11:55:17AM -0400, Sean Murphy wrote: > Hi Peter, > > This is a solid machine, if you can get it, do so. OpenBSD 6.1 works > very well on this hardware, I have used mine variously as a gateway > router with PF, DHCP server, DNS server with unbound, and local name > server with nsd. Currently it's acting as local name server while > standing as backup router/nameserver/dhcp if needed. You will have to > have valid time servers as the ERL doesn't have an internal clock. > Have fun! > > Here's a dmesg: Thanks! I decided to buy this, after the words of confidence from everyone who replied. Thanks, -peter
Re: octeon port, ubiquity edgerouter
On Sat, Jul 22, 2017 at 5:46 AM, Peter J. Philippwrote: > Hi, > > Someone has offered me a deal on a somewhat used Ubiquiti Edgerouter, > https://www.ubnt.com/edgemax/edgerouter/ <-- this one. > > Is it supported by OpenBSD/octeon and if not what needs to be done to make it > work? Has anyone experience with this hardware? > > Regards, > -peter > Hi Peter, This is a solid machine, if you can get it, do so. OpenBSD 6.1 works very well on this hardware, I have used mine variously as a gateway router with PF, DHCP server, DNS server with unbound, and local name server with nsd. Currently it's acting as local name server while standing as backup router/nameserver/dhcp if needed. You will have to have valid time servers as the ERL doesn't have an internal clock. Have fun! Here's a dmesg: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2017 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.1 (GENERIC) #0: Mon Apr 3 07:47:02 UTC 2017 visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC real mem = 536870912 (512MB) avail mem = 524255232 (499MB) warning: no entropy supplied by boot loader mainbus0 at root cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 iobus0 at mainbus0 dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 cn30xxgmx0 at iobus0 base 0x118000800 cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c8 atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c9 atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:ca atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 uartbus0 at mainbus0 com0 at uartbus0 base 0x118000800 irq 34: ns16550a, 64 byte fifo com0: console com1 at uartbus0 base 0x118000c00 irq 35: ns16550a, 64 byte fifo /dev/ksyms: Symbol table not valid. umass0 at uhub0 port 1 configuration 1 interface 0 "Lexar USB Flash Drive" rev 2.10/11.00 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct removable serial.05dca83aZB0L2W63LA4P sd0: 30526MB, 512 bytes/sector, 62517248 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets boot device: sd0 root on sd0a (fb74a192b03ee90f.a) swap on sd0b dump on sd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE!
Re: octeon port, ubiquity edgerouter
On Sat, Jul 22, 2017 at 11:46:02AM +0200, Peter J. Philipp wrote: > Someone has offered me a deal on a somewhat used Ubiquiti Edgerouter, > https://www.ubnt.com/edgemax/edgerouter/ <-- this one. > > Is it supported by OpenBSD/octeon and if not what needs to be done to make it > work? The hardware works with OpenBSD 6.1.
Re: DUMP: Invalid argument: [block -60912738518]
On Fri, 21 Jul 2017 14:45:01 +0200 Jan Stary wrote: > If nothing is happening on the filesystem, it dumps OK; Cool. That is probably your answer Jan. > it does not matter that it's mounted. True. Unmounting massively reduces the chance of unexpected modifications during dumping. Such as cron/at/batch jobs, etc When a machine is shutdown(8) to single user mode, even /var/log, /var and /usr can be unmounted for a clean dump, newfs & (partial) restore. /home and many other parts of /var can be umnounted once the relevant daemons are stopped, and isn't too troublesome to script & cron. > At any rate, the negative block numbers seem wrong. Perhaps that's something for the tech@ people to investigate? Cheers, -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
Re: octeon port, ubiquity edgerouter
Hi, if noone chimes in then maybe you can get a dmesg or lshw output from the linux-based EdgeOS to get some more details on the hardware. I would guess it's quite a bit beefier than the ERL3 and for embedded platforms this can mean more differences than just more cores and more RAM. Regards, Florian Am 22. Juli 2017 11:46:02 MESZ schrieb "Peter J. Philipp": >Hi, > >Someone has offered me a deal on a somewhat used Ubiquiti Edgerouter, >https://www.ubnt.com/edgemax/edgerouter/ <-- this one. > >Is it supported by OpenBSD/octeon and if not what needs to be done to >make it >work? Has anyone experience with this hardware? > >Regards, >-peter
octeon port, ubiquity edgerouter
Hi, Someone has offered me a deal on a somewhat used Ubiquiti Edgerouter, https://www.ubnt.com/edgemax/edgerouter/ <-- this one. Is it supported by OpenBSD/octeon and if not what needs to be done to make it work? Has anyone experience with this hardware? Regards, -peter