Re: Happy Hacking keyboard not working anymore
On Wed Feb 17 2021 18:39, Norman Golisz wrote: > On Tue Feb 16 2021 11:10, Masato Asou wrote: > > I am useing Happy Hacking keyboard model:PD-KB400B and upgraded > > OpenBSD current by > > http://ftp.riken.jp/pub/OpenBSD/snapshots/amd64/bsd.rd a few minutes > > ago. > > > > Now, my OpenBSD box works fine and I can use Happy Hacking keyboard. > > > > Is your keyboard or USB port broken? > > No, it worked just fine on another computer with -RELEASE. > > But with the latest snapshot the keyboard is working properly again! I suspect this is due to mglocker's backout of changes in ukbd(4). I'd like to share my keyboard model and dmesg in case it helps: HHKB Professional Classic PD-KB401W OpenBSD 6.9-beta (GENERIC) #329: Tue Feb 16 09:49:35 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 16957259776 (16171MB) avail mem = 16428077056 (15667MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x8a996000 (107 entries) bios0: vendor American Megatrends Inc. version "2811" date 05/27/2020 bios0: Wortmann_AG 1009703;2110128 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG MSDM SSDT SSDT HPET SSDT SSDT UEFI LPIT SSDT SSDT DBGP DBG2 SSDT TPM2 ASF! WSMT acpi0: wakeup devices SIO1(S3) UAR1(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) i5-9500 CPU @ 3.00GHz, 2994.96 MHz, 06-9e-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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,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 cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured 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 2 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus -1 (RP03) acpiprt7 at acpi0: bus -1 (RP04) acpiprt8 at acpi0: bus -1 (RP05) acpiprt9 at acpi0: bus 3 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiprt12 at acpi0: bus 5 (RP09) acpiprt13 at acpi0: bus -1 (RP10) acpiprt14 at acpi0: bus -1 (RP11) acpiprt15 at acpi0: bus -1 (RP12) acpiprt16 at acpi0: bus -1 (RP13) acpiprt17 at acpi0: bus -1 (RP14) acpiprt18 at acpi0: bus -1 (RP15) acpiprt19 at acpi0: bus -1 (RP16) acpiprt20 at acpi0: bus 1 (RP17) acpiprt21 at acpi0: bus -1 (RP18) acpiprt22 at acpi0: bus -1 (RP19) acpiprt23 at acpi0: bus -1 (RP20) acpiprt24 at acpi0: bus -1 (RP21) acpiprt25 at acpi0: bus -1 (RP22) acpiprt26 at acpi0: bus -1 (RP23) acpiprt27 at acpi0: bus -1 (RP24) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x "ACPI000E" at acpi0 not configured acpibtn0 at acpi0: SLPB "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT33A1" at acpi0 not configured acpibtn1 at acpi0: PWRB "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C14" at acpi0 not configured acpipwrres0 at acpi0: USBC, resource for XDCI acpipwrres1 at acpi0: V0PR acpipwrres2 at acpi0: V1PR acpipwrres3 at acpi0: V2PR acpipwrres4 at acpi0: WRST acpicpu0 at acpi0: C2(500@79 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres5 at acpi0: FN00, resource for FAN0 acpipwrres6 at acpi0: FN01, resource for FAN1 acpipwrres7 at acpi0: FN02, resource for FAN2 acpipwrres8 at acpi0: FN03, resource for FAN3 acpipwrres9 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 119 degC acpipwrres10 at acpi0: PIN_ acpivideo0 at acpi0: GFX0 cpu0: u
Re: Happy Hacking keyboard not working anymore
On Tue Feb 16 2021 11:10, Masato Asou wrote: > I am useing Happy Hacking keyboard model:PD-KB400B and upgraded > OpenBSD current by > http://ftp.riken.jp/pub/OpenBSD/snapshots/amd64/bsd.rd a few minutes > ago. > > Now, my OpenBSD box works fine and I can use Happy Hacking keyboard. > > Is your keyboard or USB port broken? No, it worked just fine on another computer with -RELEASE. But with the latest snapshot the keyboard is working properly again! Thanks for your help, though! Norman
Re: relayd: Binding to port range
On Thu Oct 10 2019 20:27, Klemens Nanni wrote: > On Thu, Oct 10, 2019 at 04:45:37PM +0200, Norman Golisz wrote: > > it seems relayd's configuration syntax does not allow specifying port > > ranges, like 9740:10200. Am I correct? > Depends on where; search for "range" in relayd.conf(5). Thanks! Unfortunately, it does not support ranges in relay mode. I'd have loved to replace haproxy. ;-)
relayd: Binding to port range
Hi, it seems relayd's configuration syntax does not allow specifying port ranges, like 9740:10200. Am I correct? Thanks! Norman
Re: Xorg blanks until I switch to a TTY and back on 6.5
On Wed May 1 2019 14:53, Daniel Bolgheroni wrote: > On Wed, May 01, 2019 at 04:43:09PM +, Jonathan Gray wrote: > > On Wed, May 01, 2019 at 12:34:12PM -0300, Daniel Bolgheroni wrote: > > > On Mon, Apr 29, 2019 at 07:05:25AM +, Jonathan Gray wrote: > > > > Does this help? > > > > > > It was already commited but fixed the problem here. > > > > > > However, I still can't see the correct modes set for LVDS-1 and for the > > > external monitor on HDMI-1. An ultrawide 2560x1080 monitor can see at most > > > 1920x1080, but worked fine with the previous drm. > > > > There is a change queued for the next 4.19 release which concerns the > > modesetting xorg driver, I'm not sure if it is relevant: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/plain/queue-4.19/revert-drm-i915-fbdev-actually-configure-untiled-displays.patch > > It's not, I'm sorry. I will try the next iteractions. > > Thank you for your work. Someone opened a bug on freedesktop's bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110629
Using USB headsets
Hi,
I'm trying to figure out how to get my USB headset (Plantronics C310)
to work.
I can't hear anything, nor does the microphone work. I fiddled with
different mixerctl settings to no avail, and I'm not even sure my
headset had been detected at all, as the available options to set
don't change, while I plug or unplug the device[1].
dmesg[2] happily reports it detected and configured the device:
uaudio0 at uhub0 port 1 configuration 1 interface 0 "Plantronics Plantronics
C310" rev 2.00/1.35 addr 2
uaudio0: audio rev 1.00, 7 mixer controls
audio1 at uaudio0
uhidev1 at uhub0 port 1 configuration 1 interface 3 "Plantronics Plantronics
C310" rev 2.00/1.35 addr 2
uhidev1: iclass 3/0, 42 report ids
uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 2: input=2, output=0, feature=0
uhid2 at uhidev1 reportid 3: input=32, output=32, feature=0
uhid3 at uhidev1 reportid 4: input=0, output=36, feature=0
uhid4 at uhidev1 reportid 5: input=32, output=0, feature=0
uhid5 at uhidev1 reportid 6: input=0, output=36, feature=0
uhid6 at uhidev1 reportid 7: input=32, output=0, feature=0
uhid7 at uhidev1 reportid 8: input=1, output=0, feature=0
uhid8 at uhidev1 reportid 9: input=0, output=1, feature=0
uhid9 at uhidev1 reportid 20: input=1, output=0, feature=0
uhid10 at uhidev1 reportid 21: input=2, output=0, feature=0
uhid11 at uhidev1 reportid 23: input=0, output=1, feature=0
uhid12 at uhidev1 reportid 24: input=0, output=1, feature=0
uhid13 at uhidev1 reportid 25: input=0, output=1, feature=0
uhid14 at uhidev1 reportid 26: input=0, output=1, feature=0
uhid15 at uhidev1 reportid 27: input=0, output=0, feature=2
uhid16 at uhidev1 reportid 30: input=0, output=1, feature=0
uhid17 at uhidev1 reportid 31: input=1, output=0, feature=0
uhid18 at uhidev1 reportid 32: input=0, output=1, feature=0
uhid19 at uhidev1 reportid 42: input=0, output=1, feature=0
Do you have an idea what else to try? Do you have experience with
similar hardware?
Best wishes,
Norman
[1] mixerctl -v
inputs.dac-0:1=126,126
inputs.dac-2:3=126,126
record.adc-2:3_mute=off [ off on ]
record.adc-2:3=124,124
record.adc-0:1_mute=off [ off on ]
record.adc-0:1=124,124
inputs.mix_source=mic2,spkr2,spkr3,beep { mic2 spkr2 spkr3 beep }
inputs.mix_mic2=120,120
inputs.mix_spkr2=120,120
inputs.mix_spkr3=120,120
inputs.mix_beep=120,120
inputs.mix2_source=dac-0:1,mix { dac-0:1 mix }
inputs.mix3_source=dac-2:3,mix { dac-2:3 mix }
inputs.mic=85,85
outputs.spkr_source=mix3 [ mix2 mix3 ]
outputs.spkr_mute=off [ off on ]
outputs.spkr_eapd=on [ off on ]
outputs.hp_source=mix2 [ mix2 mix3 ]
outputs.hp_mute=off [ off on ]
outputs.hp_boost=off [ off on ]
outputs.hp_eapd=on [ off on ]
outputs.mic2_source=mix2 [ mix2 mix3 ]
outputs.mic2_mute=off [ off on ]
inputs.mic2=85,85
outputs.mic2_dir=input-vr80 [ none output input input-vr0 input-vr50
input-vr80 input-vr100 ]
outputs.spkr2_source=mix2 [ mix2 mix3 ]
outputs.spkr2_mute=off [ off on ]
inputs.spkr2=85,85
outputs.spkr2_dir=output [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
outputs.spkr3_source=mix2 [ mix2 mix3 ]
outputs.spkr3_mute=off [ off on ]
inputs.spkr3=85,85
outputs.spkr3_dir=output [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
record.adc-0:1_source=mic2,spkr2,spkr3,beep,mix,mic { mic2 spkr2 spkr3 beep
mix mic }
record.adc-2:3_source=mic2,spkr2,spkr3,beep,mix { mic2 spkr2 spkr3 beep mix }
outputs.hp_sense=unplugged [ unplugged plugged ]
outputs.mic2_sense=unplugged [ unplugged plugged ]
outputs.spkr_muters=hp,mic2 { hp mic2 }
outputs.master=126,126
outputs.master.mute=off [ off on ]
outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp,spkr2,spkr3 { dac-0:1 dac-2:3
spkr hp mic2 spkr2 spkr3 }
record.volume=124,124
record.volume.mute=off [ off on ]
record.volume.slaves=adc-2:3,adc-0:1 { adc-2:3 adc-0:1 mic mic2 spkr2 spkr3 }
[2] dmesg
OpenBSD 6.1-current (GENERIC.MP) #93: Thu Jul 6 15:41:21 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16846462976 (16066MB)
avail mem = 16330108928 (15573MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (70 entries)
bios0: vendor LENOVO version "G1ET73WW (2.09 )" date 10/19/2012
bios0: LENOVO 2349S1P
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF!
UEFI UEFI POAT SSDT SSDT DMAR UEFI DBG2
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3)
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz, 2794.07 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,
Re: Laptop not waking from suspend on opening lid
On Thu May 5 2016 08:10, Anthony Campbell wrote: > On 04 May 2016, Mike Larkin wrote: > > > > This is probably the same problem that kettenis fixed in a recent post. > > > > I'd try applying that diff first. > > > > -ml > > After an upgrade to a new snapshot on 3 May things have now reverted to > normal and waking occurs correctly. Yes, I can confirm that. Thank you all!
Re: Laptop not waking from suspend on opening lid
I just checked it and I can reproduce it on my T400 (dmesg below). On Tue May 3 2016 08:28, Anthony Campbell wrote: > On 03 May 2016, Anthony Campbell wrote: > > On 02 May 2016, Mike Larkin wrote: > > > On Sun, May 01, 2016 at 04:08:28PM +0100, Anthony Campbell wrote: > > > > This is on a Thinkpad Z61m running amd64. Suspend on lid closure has > > > > worked without problems for many months with numerous snapshots. After > > > > upgrading on 30 April the machine no longer wakes on lid opening. The > > > > sleep symbol below the screen blinks repeatedly but nothing else > > > > happens. > > > > > > > > If I suspend it with Fn+F4 the same thing happens; it is impossible to > > > > wake the machine. > > > > > > > > Another Thinkpad running i386 is not affected. > > > > > > > > > > When did it last work? Eg, when before "30 April"? Unfortunately, I didn't upgrade frequently - I made a jump from Apr 7. to Apr 29., but the kernel from Apr 7. works. I'll try to bisect. OpenBSD 5.9-current (GENERIC.MP) #2000: Fri Apr 29 17:01:24 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4166717440 (3973MB) avail mem = 4035842048 (3848MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012 bios0: LENOVO 6475BE3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.36 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 265MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "IBM0057" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0400" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "IBM0079" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK docked (15) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: msi inteldrm0: 1440x900 wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:95:39:e7 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22
Re: 5.9 discs in the wild. Europe/Germany
On Thu Apr 21 2016 15:27, Stefan Wollny wrote: > Arrived today in Germany :-) > > Thx to everybody who made this possible. Absolutely. Received mine yesterday (also Germany). Thank you!
Re: vmmctl and vmd problem
> run vmmctl and vmd: > vmmctl enable > vmmctl: connect: /var/run/vmd.sock: No such file or directory > > vmd -v > fatal in vmd: can't open vmm device node /dev/vmm: Device not configured This is expected. vmm(4) is not yet enabled in the default kernel configuration.
Re: SIM card in a Thinkpad T400
> Attached below is a perl script I crafted to quickly connect/disconnect > and query for status (network name, signal strength, HSDPA/GPRS, etc). > It is a bit flawed, and maybe could use some improvement from someone > who actually knows what he's doing, but hey "it works for me". Thanks for providing this convenient script, Ze`! Works for me on my T400 as well. cdce0 at uhub1 port 4 configuration 1 interface 7 "Ericsson Ericsson F3507g Mobile Broadband Minicard Composite Device" rev 2.00/0.00 addr 2
Re: debugging vio issue?
On Wed May 28 2014 11:37, Philip Guenther wrote: > On Wed, May 28, 2014 at 11:26 AM, Adam Thompson wrote: > > > Don't have a good answer for you, but I have similar problems with vio(4). > > Switching to e1000 on the KVM side solved my random hangs completely. Same behaviour with RHEV 3.3. > The vio(4) manpage mentions > Setting flags to 0x02 disables the RingEventIndex feature. This can be > tried as a workaround for possible bugs in host implementations or vio > at > the cost of slightly reduced performance. > > Have any of you tested that to see whether it improves the situation? Thank you, Philip. I'll try that out. Norman
Re: Intel HD Graphics 4000, only one monitor detected
Hi Jonathan, On Tue May 20 2014 20:56, Jonathan Gray wrote: > On Tue, May 20, 2014 at 10:05:07AM +0200, mar...@familjenbergkvist.net wrote: > > >Synopsis: Intel HD Graphics 4000, only one monitor detected > > >Category: > > >Environment: > > System : OpenBSD 5.5 > > Details : OpenBSD 5.5-current (GENERIC.MP) #136: Mon May 19 > > 09:40:42 MDT 2014 > > > > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > I have two identical monitors connected to my Intel HD Graphics 4000 > > on DisplayPort and HDMI respectively. Usually there was no problem > > detecting them both and split my desktop across both monitors. But > > somewhere between > > OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 > > and > > OpenBSD 5.5-beta (GENERIC.MP) #287: Fri Feb 7 11:45:09 MST 2014 > > something happened. The monitor on HDMI is mirroring the DisplayPort > > and it is not detected properly by xrand. > > > > After doing xrandr --auto the monitor on HDMI turns black and is not > > detected at all by xrand. > > That is around the timeframe of the xf86-video-intel update to > 2.99.909 from 2.20.19. Currently we have 2.99.910. > > I don't see any likely commits in the kernel around that timeframe. > > 2.99.911 has since been released > http://lists.freedesktop.org/archives/xorg/2014-March/056491.html > > When I get a chance I'll test it here and send you a patch to see > if that changes anything. I'd be happy to provide feedback as well! ;-) Norman
Re: smtpd stops immediately after starting in -current
Hi Gilles,
On Sun May 18 2014 13:45, Gilles Chehade wrote:
> can you share your configuration file ?
>
> i'm unable to reproduce no matter what i try :-/
I'm also able to reproduce this crash:
$ echo test | mail norman && sudo smtpd -dv
debug: init ssl-tree
info: OpenSMTPD 5.4.3 starting
debug: bounce warning after 4h
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
info: startup [debug mode]
debug: init ssl-tree
debug: parent_send_config_ruleset: reloading
debug: parent_send_config: configuring pony process
debug: parent_send_config: configuring ca process
debug: init private ssl-tree
debug: queue: done loading queue into scheduler
debug: ca_engine_init: using RSAX engine support
debug: smtp: listen on 127.0.0.1 port 25 flags 0x0 pki ""
debug: smtp: listen on IPv6:fe80::1%lo0 port 25 flags 0x0 pki ""
debug: smtp: listen on IPv6:::1 port 25 flags 0x0 pki ""
debug: smtp: will accept at most 501 clients
debug: smtpd: scanning offline queue...
debug: smtpd: enqueueing offline message
/var/spool/smtpd/offline/1400440122.uj4xYO8YaC
debug: smtpd: offline scanning done
debug: smtp: new client on listener: 0x14804c2680c0
smtp-in: New session 80dc422d384e8c2d from host 1000@localhost [local]
warn: parent -> pony: pipe closed
warn: queue -> pony: pipe closed
warn: ca -> pony: pipe closed
warn: control -> pony: pipe closed
warn: scheduler -> queue: pipe closed
warn: lka -> pony: pipe closed
smtpd.conf:
listen on lo0
table aliases db:/etc/mail/aliases.db
table secrets { me => me.local:whoohoo}
accept for local alias deliver to maildir
accept for any relay via tls+auth://m...@smtp.me.local:587 auth
dmesg:
OpenBSD 5.5-current (GENERIC.MP) #132: Fri May 16 10:26:11 MDT 2014
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4166717440 (3973MB)
avail mem = 4047036416 (3859MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries)
bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012
bios0: LENOVO 6475BE3
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4)
EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3)
EHC1(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.31 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 266MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus -1 (EXP2)
acpiprt5 at acpi0: bus 5 (EXP3)
acpiprt6 at acpi0: bus 13 (EXP4)
acpiprt7 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic"
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK docked (15)
cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1440x900
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
"Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured
em0 at pci0 dev
Re: Thinkpad T400 does not resume
Hello Jan, On Sat Feb 8 2014 17:59, Jan Stary wrote: [...] > Are the T400 generally known to suspend/resume? I'm not seeing any issues on my T400. Although mine is running amd64. Would you mind sharing your dmesg for comparison? OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4166717440 (3973MB) avail mem = 4047581184 (3860MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012 bios0: LENOVO 6475BE3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.38 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK docked (15) cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1440x900 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:95:39:e7 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi azalia0: codecs: Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO 3T3R, MoW, address 00:16:ea:b3:62:e8 ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: msi pci3 at ppb2 bus 5 ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x03: msi pci4 at ppb3 bus 13 uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 16 uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 17 uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x03: apic 1 int 19 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x93 pci5 at ppb
Re: sysmerge complains about not valid etcXX.tgz set
On Sat Jan 25 2014 18:18, Markus Lude wrote: > Hello, > > today I updated to the latest snapshot on sparc64 (from 22nd january). > When I run sysmerge after that I got > > $ sudo sysmerge -s etc55.tgz -x xetc55.tgz > *** ERROR: /var/tmp/sysmerge.Hwq1ImlHSs/etc55.tgz is not a valid > etcXX.tgz set > > Any ideas what might go wrong here? try specifying the full (absolute) path to the sets. It's a regression, where sysmerge doesn't handle implicit paths correctly. ajacout@ has already fixed it in -current after Jan, 22.
Re: X11 graphics corruption on intel card
On Wed Jan 15 2014 18:06, frantisek holop wrote: > nobody seeing this on i915? No, everything fine on my Thinkpad T400. You already tried -current, right? Though I didn't had this error with the snapshot from Dec, 28. either. dmesg and Xorg.log attached. OpenBSD 5.5-beta (GENERIC.MP) #267: Sun Jan 12 22:33:47 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4166717440 (3973MB) avail mem = 4047605760 (3860MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012 bios0: LENOVO 6475BE3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.34 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK docked (15) cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1440x900 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:95:39:e7 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi azalia0: codecs: Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO 3T3R, MoW, address 00:16:ea:b3:62:e8 ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: msi pci3 at ppb2 bus 5 ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x03: msi pci4 at ppb3 bus 13 uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 16 uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 17 uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x03: apic 1 int 19 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to
Re: queueing/hfsc question
On Tue Dec 3 2013 20:40, Gabor Berczi wrote: > On Dec 3, 2013, at 7:15 PM, Andy wrote: > > >Including http://www.openbsd.org/faq/pf/queueing.html > > This page doesn't even mention neither HFSC nor any new scheduler... Please watch the video record of Henning's talk on the new queueing subsystem. And yes, the new queueing subsystem is not yet included in one of the releases. This will be the case with 5.5. It's in -current, though.
Re: queueing/hfsc question
On Tue Dec 3 2013 20:32, Gabor Berczi wrote: > On Dec 3, 2013, at 8:03 PM, josh Grosse wrote: > > >On 2013-12-03 13:46, Gabor Berczi wrote: > >>On Dec 3, 2013, at 7:15 PM, Andy wrote: > >>> queue ack on $extinterface bandwidth 10% priority 6 hfsc ( realtime > >>>10% ) > >>> queue ack on $intinterface bandwidth 10% priority 6 hfsc ( realtime > >>>10% ) > >>One queue can't be on two interfaces. > >>"queue XYZ already exists on interface pppoe0" > > > >Child queues are able to use the same name. Here's an example, using the > >new queuing syntax, where the "std" and "pig" queue names are assigned to > >queues on different interfaces with different settings: > > /etc/pf.conf.test:4: unknown unit M > /etc/pf.conf.test:5: queue pig has no parent > /etc/pf.conf.test:5: errors in queue definition > /etc/pf.conf.test:6: queue std has no parent > /etc/pf.conf.test:6: errors in queue definition > /etc/pf.conf.test:8: unknown unit M > /etc/pf.conf.test:9: queue local has no parent > /etc/pf.conf.test:9: errors in queue definition > /etc/pf.conf.test:10: queue down has no parent > /etc/pf.conf.test:10: errors in queue definition > /etc/pf.conf.test:11: queue pig has no parent > /etc/pf.conf.test:11: errors in queue definition > /etc/pf.conf.test:12: queue std has no parent > /etc/pf.conf.test:12: errors in queue definition You need to run -current for this.
Re: is zeroing CRYPT needed?
On Mon Nov 25 2013 10:08, obsd, cgi wrote: > according to: > http://www.openbsd.org/cgi-bin/man.cgi?query=bioctl > > dd if=/dev/zero of=/dev/rsd3c bs=1m count=1 > > is needed. but Why? since it's likely to contain garbage. If this area has been in use before, there's a good chance it exposes "random" data, which could, and most probably will, confuse fdisk. That's why you have to "wipe" the area in advance.
Re: new queueing subsystem
On Wed Oct 16 2013 08:54, Johan Beisser wrote: > Or cam I still just do very basic priority queueing in 5.5? See pf.conf(5), 'set prio'. This doesn't even require you to define queues, etc.
Re: Limit downloading using the new queueing subsystem (OpenBSD 5.4-current)
On Tue Oct 15 2013 16:32, Wesley MOUEDINE ASSABY wrote:
> Le 2013-10-15 16:18, Norman Golisz a écrit :
> >On Tue Oct 15 2013 14:08, Norman Golisz wrote:
> >>On Tue Oct 15 2013 15:48, Wesley MOUEDINE ASSABY wrote:
> >>> When i download a file using the host 192.168.1.1
> >>> and do at the same time :
> >>>
> >>> # pfctl -vvs queue
> >>>
> >>> queue restriction on axe0 bandwidth 800K qlimit 50
> >>> [ pkts: 0 bytes: 0 dropped pkts: 0
> >>bytes:
> >>> 0 ]
> >>> [ qlength: 0/ 50 ]
> >>> [ measured: 0.0 packets/s, 0 b/s ]
> >>> queue employee parent restriction on axe0 bandwidth 10K qlimit 50
> >>> [ pkts: 21119 bytes: 30624777 dropped pkts: 0
> >>bytes:
> >>> 0 ]
> >>> [ qlength: 0/ 50 ]
> >>> [ measured: 115.8 packets/s, 1.35Mb/s ]
> >>
> >>yap, bandwidth restrictions apply on upload, only. So, you're
> >>effectively using 10K for TCP ACK packets.
> >
> >you might want to restrict bandwidth on the LAN interface, though.
> >You'd
> >configure the queues as above on the LAN interface and apply packets
> >going "out"/upload.
>
> Actually, queue is defined on axe0 ("IN"); it is the lan interface.
> It doesn't work (downloading limited).
>
> I already tried this:
> block all
> pass in log quick on lan from $employee set queue employee tag policy1
> pass in on lan
> pass log quick tagged policy1
> pass out on egress
> # Downloading still not limited.
>
> Any idea ?
Yes, I remember you need to explicitly set a "maximum" bandwidth to the
queue definition:
queue employee parent restriction bandwidth 10K max 10K
Does this work for you?
Re: Limit downloading using the new queueing subsystem (OpenBSD 5.4-current)
On Tue Oct 15 2013 14:08, Norman Golisz wrote: > On Tue Oct 15 2013 15:48, Wesley MOUEDINE ASSABY wrote: > > When i download a file using the host 192.168.1.1 > > and do at the same time : > > > > # pfctl -vvs queue > > > > queue restriction on axe0 bandwidth 800K qlimit 50 > > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: > > 0 ] > > [ qlength: 0/ 50 ] > > [ measured: 0.0 packets/s, 0 b/s ] > > queue employee parent restriction on axe0 bandwidth 10K qlimit 50 > > [ pkts: 21119 bytes: 30624777 dropped pkts: 0 bytes: > > 0 ] > > [ qlength: 0/ 50 ] > > [ measured: 115.8 packets/s, 1.35Mb/s ] > > yap, bandwidth restrictions apply on upload, only. So, you're > effectively using 10K for TCP ACK packets. you might want to restrict bandwidth on the LAN interface, though. You'd configure the queues as above on the LAN interface and apply packets going "out"/upload.
Re: Limit downloading using the new queueing subsystem (OpenBSD 5.4-current)
On Tue Oct 15 2013 15:48, Wesley MOUEDINE ASSABY wrote: > When i download a file using the host 192.168.1.1 > and do at the same time : > > # pfctl -vvs queue > > queue restriction on axe0 bandwidth 800K qlimit 50 > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: > 0 ] > [ qlength: 0/ 50 ] > [ measured: 0.0 packets/s, 0 b/s ] > queue employee parent restriction on axe0 bandwidth 10K qlimit 50 > [ pkts: 21119 bytes: 30624777 dropped pkts: 0 bytes: > 0 ] > [ qlength: 0/ 50 ] > [ measured: 115.8 packets/s, 1.35Mb/s ] yap, bandwidth restrictions apply on upload, only. So, you're effectively using 10K for TCP ACK packets.
Re: Installing Openbsd 5.2 as KVM guest
On Thu Feb 14 2013 08:54, Xavier Naveira wrote: > Hi everyone, > > I'm trying to install OpenBSD 5.2 as KVM guest but I can't get passed the > installation process because the disk and the network are not being > detected correctly. [...] > Is it possible at all to install OpenBSD in such a machine? Yes, try -current.
Re: openbsd and vmware
On Thu Feb 7 2013 17:50, Jan Lambertz wrote: > I also tried the socket trick in different setups but couldn't make it > work. You *do* boot bsd.mp, right? Because bsd.rd never recognised a such configured VM as being SMP-capable in my case, and installed bsd.sp by default, instead. > I tried a smp 4,threads 1 cores 1 sockets 4. Sysctl tells cpus are > found but not used. Did you pass any special cpu information to qemu ? Sorry, I can't tell. I used RHEV 3.1 and by increasing the number of sockets, it linearly increased the number of cores, too. So, did you try 4 cores and 4 sockets, then?
Re: openbsd and vmware
On Thu Feb 7 2013 05:33, Jan Lambertz wrote: > problems i found using kvm and openbsd: > SMP not working as it should. I usually increase the number of virtual sockets to get those extra cores recognised by OpenBSD. This seems to make the hypervisor produce better ACPI routing information ... > No virto drivers for openbsd(disk i miss the most) Hm? On -current: virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00: Virtio Block Device vioblk0 at virtio2 scsibus1 at vioblk0: 2 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed sd0: 8192MB, 512 bytes/sector, 16777216 sectors virtio2: apic 1 int 10 ... and these ... virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00: Virtio Network Device vio0 at virtio0: address 00:1a:4a:15:00:1f virtio0: apic 1 int 11 virtio6 at pci0 dev 9 function 0 "Qumranet Virtio Memory" rev 0x00: Virtio Memory Balloon Device viomb0 at virtio6 virtio6: apic 1 int 10
Re: bsd.sp and bsd.mp kernels, how to compile?
On Sun Dec 9 2012 11:59, John Long wrote: > On Sun, Dec 09, 2012 at 12:21:34PM +0100, Paul de Weerd wrote: > > Alternatively, you can `make` GENERIC and `make install` GENERIC.MP. > > Or just skip making the SP kernel, you don't need to have it around > > per se ;) > > I didn't know if make generic would leave a finished bsd.sp kernel in / > Not sure what the kernel make install target does, since I wasn't paying > attention after building the kernel a bunch of times on my Fuloong box. In both cases, whether it's GENERIC or GENERIC.MP, `make install` installs the kernel to /bsd: rm -f /obsd ln /bsd /obsd cp bsd /nbsd mv /nbsd /bsd > If make builds a kernel and leaves it in / and just doesn't point the > bootloader at it that will be enough and I'll just make install the mp > kernel like I think you are saying. The bootloader loads /bsd by default. So, if you're about to provide both versions, and you generally want GENERIC.MP to be loaded, you'd `make install` GENERIC.MP, and than manually copy the binary from GENERIC to /bsd.sp. At the boot prompt, you may choose the SP kernel by typing `boot bsd.sp`.
Re: a pf ruleset 5.2
Hi,
On Tue Nov 6 2012 10:49, Wesley wrote:
> I just built a small firewall using OpenBSD 5.2
> Advices are welcome... ;-)
>
> Thank you very much.
>
> So, 2 interfaces, with the following rules :
>
> -Traffic only Ipv4
> -Allow pings in/out
> -Allow our lan to only have ftp/http and https
> -Allow an access from anywhere to our RDP server
> -Prioritizing Acks
>
> *
> lan=rl0
> allow="{www,ftp,https}"
^^^
I'd change the last line to:
allowed_tcp = "{ ftp, www, https, domain }"
allowed_udp = "{ domain }"
> rdphost="10.0.0.10"
>
> set skip on lo
> set block-policy return
>
> match in all scrub (no-df max-mss 1440)
> match out on egress inet from $lan:network to any nat-to egress
>
> block log all
>
> anchor "ftp-proxy/*"
> pass in quick inet proto tcp to port ftp divert-to 127.0.0.1 port 8021
Really? You want this rule apply on egress, too?
> pass out on egress inet proto tcp set prio (1,7)
I'd convert this to a "match" rule, which affects traffic in both
directions, and is decision-agnostic:
match on egress inet proto tcp set prio(1, 7)
> pass out on egress inet proto udp
> pass out on $lan inet
This could be crammed into one line:
pass out inet all
> pass in on $lan proto udp from $lan:network to port domain
> pass in on $lan proto tcp from $lan:network to port $allow
Is it on purpose you don't want tcp dns to pass?
If not, you'd change these lines to:
pass in on $lan inet proto udp from $lan:network to port $allowed_udp
pass in on $lan inet proto tcp from $lan:network to port $allowed_tcp
> pass inet proto icmp all icmp-type echoreq
Are you missing unreach?
> pass in on egress inet proto tcp from any to any port 3389 \
> rdr-to $rdphost tag rdp set prio (1,7)
No need to set priority here anymore.
> pass out on $lan tagged rdp
Superfluous.
Re: OpenBSD 5.2 Tos / AckPri
On Mon Nov 5 2012 12:15, Wesley wrote:
> Hi,
>
> In OpenBSD 5.2, does this line : "pass all tos lowdelay" do the same
> job that using altq/priq (see below)?
No.
> ext_if="kue0"
> altq on $ext_if priq bandwidth 100Kb queue { q_pri, q_def }
> queue q_pri priority 7
> queue q_def priority 1 priq(default)
> pass out on $ext_if proto tcp from $ext_if to any flags S/SA \
> keep state queue (q_def, q_pri)
The above pass rule says "pass all packets with lowdelay TOS flag set",
the other says "pass packets leaving the interface and put them into
queue q_def, and if they have the lowdelay TOS flag set, put them into
queue q_pri, instead".
Re: no output from /etc/daily
Hello Robert, On Sat Sep 22 2012 15:16, Robert Connolly wrote: > My local mail is not working, and I don't know how to diagnose it. I'm > using OpenSMTP. please check your /var/log/maillog. And, what version are you running?
Re: power button halt vs reboot(8) and halt(8)
On Fri Jul 13 2012 23:58, frantisek holop wrote: > hi there, > > how different is the code path between reboot(8), halt(8) > and when i press the power button? > > the reason i ask is, that fairly often, reboot(8) and halt(8) > "hangs" (X disappears, but there is only black screen, > and the console never appears, no "syncing disks" message), > but pressing the power button turns off the machine > without fail every time. another one of those mysteries.. > > happened on multiple notebooks for me, but here is the dmesg > for the one i use daily nowadays. I can confirm this happens on my Thinkpad T400, too. I did not yet dig further into this, so I provide at least some system info; dmesg, pcidump, Xorg.0.log. $ dmesg OpenBSD 5.2-beta (GENERIC.MP) #6: Wed Jul 11 21:11:53 CEST 2012 nor...@theos.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4182446080 (3988MB) avail mem = 404878 (3861MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET93WW (3.23 )" date 12/15/2011 bios0: LENOVO 6475BE3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.39 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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 273MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2328.83 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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK docked (15) cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 drm0 at inteldrm0 "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured puc0 at pci0 dev 3 function 3 "Intel GM45 KT" rev 0x07: ports: 1 com com2 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com2: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:95:39:e7 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi azalia0: codecs: Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO 3T3R, MoW, address 00:16:ea:b3:62:e8 ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: msi pci3 at ppb2 bus 5 ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x03: msi pci4 at ppb3 bus
Re: dwm in base
On Tue Jul 10 2012 20:52, z...@sdf.org wrote: > Hello, > > there are a lot of nice window managers in OpenBSD base (fvwm, cwm, ...). > > I am a big fan of dwm and I think it shares the philosophy of minimalism > which is important to a lot of BSD lovers. Also, it has a good code > quality and is rock solid... > > Is there a reason why dwm isnt in OpenBSD base installation? Is there a reason why dwm should be included into base? dwm is extremely small, easy to compile and install (it doesn't even need gnu make crap, everything necessary to build comes with base). And, last but not least, its configuration is modified by editing its config.h by hand. So, everyone seriously using it compiles it from source, anyway.
Re: partitioning with more mount points on obsd51
> I tend to get old computers from folks that upgrade and actually > have a DNS Server running on an Intel built for windows95. :) Yeah, BSDs deal fine with old computers and limited resources. I love that, too. :) > And for the sake of comparison, I have a FreeBSD machine with ZFS > filesystem mostly backup up video and it looks like this: > > (70) @ 23:39:38> zfs list > NAME USED AVAIL REFER MOUNTPOINT > bigD32.8G 37.6G 672M / > bigD/swap 4.13G 41.7G 57.1M - > bigD/tmp 44K 37.6G44K /tmp > bigD/usr27.8G 37.6G 312M /usr > bigD/usr/distfiles31K 37.6G31K /usr/distfiles > bigD/usr/home 23.9G 37.6G 23.9G /usr/home > bigD/usr/local 421M 37.6G 421M /usr/local > bigD/usr/obj2.44G 37.6G 2.44G /usr/obj > bigD/usr/packages 31K 37.6G31K /usr/packages > bigD/usr/ports 435M 37.6G 435M /usr/ports > bigD/usr/src 351M 37.6G 351M /usr/src > bigD/var 156M 37.6G 1.28M /var > bigD/var/backups1.04M 37.6G 1.04M /var/backups > bigD/var/crash 31.5K 37.6G 31.5K /var/crash > bigD/var/db 153M 37.6G 152M /var/db > bigD/var/db/pkg 1.30M 37.6G 1.30M /var/db/pkg > bigD/var/empty31K 37.6G31K /var/empty > bigD/var/mail 31K 37.6G31K /var/mail > bigD/var/run 55K 37.6G55K /var/run > bigD/var/tmp 32K 37.6G32K /var/tmp Interesting. Depending on purpose, I also dedicate /var/www, /var/named, and everything chroot'ed. And, *if* useful, you can also optimise their filesystem parameters according to the expected utilisation (many small files, fast seek times, big chunks of data, high throughput?). Note, however, most of the time the defaults are just fine, since reasonable metrics are applied to them anyway. And, if you're going to build your own releases on OpenBSD, you might want to plan another 2 GBs for the destination paths /usr/dest, /usr/rel, each. Norman
Re: partitioning with more mount points on obsd51
Hi Darrel, On Tue Jun 26 2012 14:58, Darrel wrote: > We have less limitation on partitioning these days, so /usr/obj > was obvious- actually had that one before. I chose /usr/src and > /usr/local as well, and expect that this was unimportant unless > moving into NFS or some special circumstance. no, this isn't necessarily true. Think of FFS' block alignment feature, using different mount options, file system optimisations, etc. > I have looked at some of the things that folks are doing with /var > on ZFS. I understand that ZFS is not within the scope of this > list; however, does anyone have some neat ideas about partitions > under /var? > > Particularly, I am interested in /var/crash, /var/tmp, and /tmp. > I would not personally have any use for a crashdump, unless it > would be to pass it along to someone who could make use of it. I > basically want the partitions to be set up logically. > > Typically etc, usr, tmp, var, home, and / have been enough. /usr/obj > is an excellent addition and so does someone have recommendations > of further refining my scheme for OpenBSD51? > > I used /altroot for the first time on OpenBSD50, but had to modify > fstab like this: > #bb128e900f20094a.d /altroot ffs xx 0 0 > /dev/wd0d /altroot ffs xx 0 0 > > I guess that /var/crash should be crafted to memory and that Hmm. No. Be aware that the kernel dumps the entire physical memory to swap. When rebooting, savecore(8) copies the dump to /var/crash. Therefore, it needs to be at least as big as available system RAM + a few bits more. You see why mfs is not suited for this. > /var/tmp as well as /tmp can actually be very small? Yes, they can. But it depends on your setup. See, /tmp can become scarce when your web browser stores its temporary data there, e.g. video data. And, one further hint, you should place /var/tmp on non-volatile storage, as it is supposed to hold temporary data between reboots, whereas /tmp can safely be an mfs. My imperfect configuration looks like this: ~ $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd2a 509M 64.0M420M13%/ /dev/sd2p 44.8G 29.1G 13.5G68%/home /dev/sd2d 1001M793M158M83%/usr /dev/sd2e 502M196M281M41%/usr/X11R6 /dev/sd2f 6.9G2.7G3.8G42%/usr/local /dev/sd2i 2.0G1.1G812M58%/usr/obj /dev/sd2k 4.9G384M4.3G 8%/usr/ports /dev/sd2l 3.9G 87.4M3.7G 2%/usr/ports/pobj /dev/sd2g 2.9G890M1.9G31%/usr/src /dev/sd2h 2.0G552M1.3G29%/usr/xenocara /dev/sd2j 2.0G495M1.4G26%/usr/xobj /dev/sd2m 123M 17.4M 99.8M15%/var /dev/sd2o 246M5.1M229M 2%/var/log /dev/sd2n 123M 96.0K117M 0%/var/tmp mfs:4517 495M109K470M 0%/tmp Yours, Norman.
Re: Large (3TB) HDD support
On Mon Jun 4 2012 11:46, Peter Laufenberg wrote: > >On Mon Jun 4 2012 08:16, Peter Laufenberg wrote: > >> UEFI has gotten more press, and given RH an opportunity to present > >> itself as defender of freedom > > I meant that sarcastically Sure you did. I just wanted to highlight this point even more.
Re: Large (3TB) HDD support
On Mon Jun 4 2012 08:16, Peter Laufenberg wrote: > UEFI has gotten more press, and given RH an opportunity to present > itself as defender of freedom, but it's really an evolution of PCs > running black-box code when and where it can do most harm. In fact, RH betrayed the OSS community by not trying to exert at least some pressure on the big players in the mainboard industry, willing to implement UEFI with Secure Boot adhering to MS's constraints. RH was probably the only big OSS vendor with powers to fight against that pervert situation in that every boot code out there needs to be signed by MS. They probably say, it's only 99 dollars, so what? It's isn't worth the hassle, let's take the most convenient option, which works for us. We don't care for you, outlandish operating system (OSS) vendors ... very sad. Norman.
Re: is it possible to set up IMAP with OpenSMTPD
On Sun Jun 3 2012 20:43, Tomasz Marszal wrote: > Hi > I wonder is it possible to run imap and squirrelmail with OpenSMTPD + SpamD > > i run OpenSMTPD on freebsd 8.3 and it works fine for me i haven't > configured spamd yet because i dont have domain but i will buy one soon. > Tell me guys pleas is imap conf possible with this two. Yes, as with every other smtp server delivering to mbox or maildir. Point your imap server to the mbox or maildir path, and configure OpenSMTPD to deliver to either mbox or maildir. Note that you should use the maildir format for this setup, as mbox could be problematic when it comes to locking and data integrity [1]. You may want to read at least smtpd(8), smtpd.conf(5), spamd(8), spamd.conf(5) and probably pf.conf(5), to learn more about the relevant components. It also gives you examples how to set up pf to work with spamd. [1] http://wiki.dovecot.org/MailboxFormat/mbox
Re: unbound
On Sun May 20 2012 12:08, bofh wrote: > Ooo! If you have time, for the great unwashed masses, if you could > tell us what are the things we need to do in 5.1 to get this going, > that'd be greatly appreciated. # pkg_add -vi unbound Edit your rc.conf.local's $pkg_scripts to add "unbound". # /etc/rc.d/unbound start
Re: vmmap speed increase diff
On Tue Mar 27 2012 17:08, patrick keshishian wrote: > FF11 was dog-slow, at least on my netbook. This patch makes FF11 more > tolerable. same here with libreoffice and xxxterm. I'm extensively using my Thinkpad T400 since Saturday with this patch without apparent problems.
Re: MySQL connection error after upgrade 4.9->5.0
Hi Uwe, On Wed Mar 14 2012 22:47, Uwe Dippel wrote: > On Wed, Mar 14, 2012 at 10:22 PM, Uwe Dippel wrote: > > > I had read those. And yet, I don't understand that line. It doesn't > > look like it should be written into rc.conf / rc.conf.local, does it? > > Correct me if I'm wrong. It looks like a shell variable that has > > 'postfix' appended. > > Ooops, I think I got it finally. The shell variable is defined in > rc.conf, and actually has 'postfix' appended when rc.conf.local is > being run. > Personally, I would not have expected the variable to be created in > rc.conf, because since 4. something it is being considered 'clean' of > user entries at upgrade. > Would it not be better to add package start strings in rc.conf.local only? of course it is declared in rc.conf. This file is used by rc(8) to define and control its variables. rc.conf.local is sourced by rc.conf.local near at the end to overwrite the defaults with user-defined values. Hence, it is still true, you put your local modifications into rc.conf.local, to prevent the upgrade script from overwriting them. So, to let rc(8) start daemons installed by pkg_add, you configure $pkg_scripts in /etc/rc.conf.local, accordingly: pkg_scripts="postfix mpd etc" Note that rc(8) starts them in the order you provide with $pkg_scripts. Yours, Norman
Re: xenocara fails to build on -current with radeonold
On Tue Mar 13 2012 16:57, Kenneth R Westerback wrote: > On Tue, Mar 13, 2012 at 08:45:14PM +0100, Norman Golisz wrote: > > On Tue Mar 13 2012 17:11, Mattieu Baptiste wrote: > > > Hi all, > > > > > > Is it just me? radeonold fails to build on -current (amd64): > > > > no, I can confirm that on i386, too. Went fine before the update of > > radeon(4) and the renaming of the old radeon driver to radeonold(4). > > > > Yours, > > Norman > > > > Need to get newer tree. Was just fixed, at least for me. confirmed. Just compiled xenocara successfully on i386.
Re: MySQL connection error after upgrade 4.9->5.0
On Wed Mar 14 2012 11:59, Norman Golisz wrote: > Hi Uwe, > > On Wed Mar 14 2012 17:53, Uwe Dippel wrote: > > I have this unfortunate occurrence on one of my production machines: > > "Database Error: Unable to connect to the database:Could not connect to > > MySQL" > > I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but > > can't find what went wrong. I just did the upgrade, and made the links > > as proposed (so I hope) > > > > # pwd > > /etc/php-5.2 > > # ls -l > > total 0 > > lrwxr-xr-x 1 root wheel 26 Mar 14 17:26 gd.ini -> > > /etc/php-5.2.sample/gd.ini > > lrwxr-xr-x 1 root wheel 29 Mar 14 17:25 mysql.ini -> > > /etc/php-5.2.sample/mysql.ini > > > > # ls -l /var/www/conf/modules > > total 0 > > lrwxr-xr-x 1 root daemon 41 Mar 14 16:26 php.conf -> > > /var/www/conf/modules.sample/php-5.2.conf > > > > I also tried to copy the modified php.ini from /var/www/conf to > > /etc/php-5.2.ini > > Then the result is: > > "Database Error: Unable to connect to the database:The MySQL adapter > > "mysql" is not available." > > you need to create the directory /etc/php-5.2 and place equivalent symbolic > links > to modules in /etc/php-5.2.sample as in /var/www/conf/php5. sorry, I failed to read your post properly. I'm ashamed. You did follow these steps, obviously. However, did you change any values in php.ini from default?
Re: MySQL connection error after upgrade 4.9->5.0
Hi Uwe, On Wed Mar 14 2012 17:53, Uwe Dippel wrote: > I have this unfortunate occurrence on one of my production machines: > "Database Error: Unable to connect to the database:Could not connect to MySQL" > I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but > can't find what went wrong. I just did the upgrade, and made the links > as proposed (so I hope) > > # pwd > /etc/php-5.2 > # ls -l > total 0 > lrwxr-xr-x 1 root wheel 26 Mar 14 17:26 gd.ini -> > /etc/php-5.2.sample/gd.ini > lrwxr-xr-x 1 root wheel 29 Mar 14 17:25 mysql.ini -> > /etc/php-5.2.sample/mysql.ini > > # ls -l /var/www/conf/modules > total 0 > lrwxr-xr-x 1 root daemon 41 Mar 14 16:26 php.conf -> > /var/www/conf/modules.sample/php-5.2.conf > > I also tried to copy the modified php.ini from /var/www/conf to > /etc/php-5.2.ini > Then the result is: > "Database Error: Unable to connect to the database:The MySQL adapter > "mysql" is not available." you need to create the directory /etc/php-5.2 and place equivalent symbolic links to modules in /etc/php-5.2.sample as in /var/www/conf/php5. >From upgrade50.html: > php module changes > The various PHP modules (for example gd, mysql, postgresql, xcache, and > various > other modules which are part of PHP or from PECL) had their configuration > files > in /var/www/conf/php5.sample; symbolic links for active modules were placed in > /var/www/conf/php5. These have moved to /etc/php-5.2.sample and /etc/php-5.2 > respectively. You will need to check for existing links in /var/www/conf/php5 > and create equivalent links in /etc/php-5.2. Note that mbstring is now part of > the main php-5.2 package so an existing mbstring.ini symbolic link can be > ignored. Yours, Norman
Re: xenocara fails to build on -current with radeonold
On Tue Mar 13 2012 17:11, Mattieu Baptiste wrote: > Hi all, > > Is it just me? radeonold fails to build on -current (amd64): no, I can confirm that on i386, too. Went fine before the update of radeon(4) and the renaming of the old radeon driver to radeonold(4). Yours, Norman
Re: [SOLVED] Re: should 'make -j8 build' work?
Hi Joe, On Wed Feb 8 2012 11:27, Joe Gidi wrote: > On Wed, February 8, 2012 3:25 am, Stuart Henderson wrote: > > On 2012-02-07, Joe Gidi wrote: > >> In every case, when the box hangs, I'm unable to break into ddb. > > > > How long do you leave it when it hangs? There have been occasions > > where a box appears to hang but then recovers. > > > > Are you using softdep? > > I actually resolved this by pulling and reseating all the DIMMs. > > Oddly enough, prior to that, the box went through 3 complete runs of > memtest86+ without error, but continued to hang at random spots during > 'make -j8 build'. > > I pulled and reseated all the memory and then did 5 'make -j8 build' runs > successfully, no more hangs. > > Very strange, but this is why I like to stress-test new builds... actually, it's the most reliable way to detect faulty hardware. Memory testers, if at all, only find specific issues (mostly by writing and reading bit patterns to RAM). They can't stimulate and stress the hardware as a build process (e.g. of an operating system) does. Memtest and such only have limited use. Yours, Norman
Re: Static or dynamic code analysis software
Hi Chris, On Mon Jan 16 2012 12:21, Chris Smith wrote: > Are there any dynamic or static C code analysis tools available for > OpenBSD? there has been a thread around here [1]. Examples include lint, cppcheck, clang's static analyser and parfait. Yours, Norman [1] http://comments.gmane.org/gmane.os.openbsd.misc/192303
Re: Blank virtual consoles in OpenBSD 5.0 with Intel graphics
On Thu Jan 12 2012 21:00, Norman Golisz wrote: > Hi Joe, > > On Thu Jan 12 2012 12:36, Joe Gidi wrote: > > Running OpenBSD/amd64 5.0-RELEASE on a ThinkPad T410 with Intel > > graphics, > > I have blank virtual consoles after starting X. > > these new Thinkpad models come with Sandybridge graphic chips. As I realise, I probably confused ambigous marketing names [1]. This model seems to have no sandybridge chipset. You may try -current, though. Yours, Norman [1] http://en.wikipedia.org/wiki/Intel_HD_Graphics
Re: Blank virtual consoles in OpenBSD 5.0 with Intel graphics
Hi Joe, On Thu Jan 12 2012 12:36, Joe Gidi wrote: > Running OpenBSD/amd64 5.0-RELEASE on a ThinkPad T410 with Intel graphics, > I have blank virtual consoles after starting X. these new Thinkpad models come with Sandybridge graphic chips. Basic Sandybridge support has been added recently to the kernel and Xenocara, and should provide you with 2D graphics and working suspend/resume functionality. To try it, just upgrade to -current. Yours, Norman
Re: system crashed recently: uvm_fault ( 0xe33d7ea0,0x0,0,3) ->e
On Thu Dec 15 2011 11:31, co...@tetrachina.com wrote: > Hi, > > OpenBSD 4.1 as firewall crashed sometimes recently everyday ,and the > debug messages are like that: > > uvm_fault ( 0xe33d7ea0,0x0,0,3) -> e > kernel:page fault trap,code=0 > stopped at pipe_create+ 0x16: Mov1 $0,0x10(%ebx) > ddb> > > anyone could tell me how to solve it .thanks in advance. Looks like faulty memory hardware. You can validate this assumption by installing memtest86+, reboot and execute it at the boot prompt: boot /stand/memtest If it throws errors to you, your memory hardware is most probably defective. Yours, Norman
Re: cdio burning images
Hi John, On Fri Nov 11 2011 16:44, Norman Golisz wrote: > On Fri Nov 11 2011 23:07, John Tate wrote: > > # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso > > cdio: The media can't be written in TAO mode > > > > What am I doing wrong? > > You don't read manuals. > > cdio(1): > > > -f device > > Specifies the name of the CD device, such as /dev/rcd0c. Both > > absolute and relative paths to /dev filenames are possible; the > > raw partition name is added if needed. > > Meaning that when you specify "-f cd0" it internally converts it to > "-f /dev/rcd0c". > > Also, you probably want to explore disklabel(8) and the difference > between raw-level and block-level access of block devices. Read a UNIX > book of your choice, or stick with Google hunting for an explanation. even though this information is not principally wrong, it was unrelated, incomplete and written inadequately rude. Sorry for that. However, did you compare the ISO's checksum after downloading it? Norman.
Re: Partition size
Hi Leonardo, On Fri Nov 11 2011 15:47, Leonardo M. Rami wrote: > Hi, I have an 4.4OpenBSD server running on a VMWare ESXi server as a > virtual machine. On the server, I configured a 21GB disk for this > virtual machine, but it doesn't shows all that space, but this: > > [root@openbsd44:~] # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/sd0a 1008M794M164M83%/ > /dev/sd0d 5.9G5.2G380M93%/var > > > [root@openbsd44:~] # fdisk sd0 > Disk: sd0 geometry: 1174/255/63 [18874368 Sectors] > Offset: 0 Signature: 0xAA55 > Starting Ending LBA Info: > #: id C H S - C H S [ start:size ] > --- > 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused > > 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused > > 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused > > *3: A6 0 1 1 - 1043 254 63 [ 63:16771797 ] OpenBSD > > How can I let the operating system see the whole disk?. as you can see, fdisk(8) only shows 9216 MB in total for this disc. Are these 21 GBs the original virtual disc's capacity, or did you enlarge it afterwards? In the latter, you would have to extend the OpenBSD partition to the new sector boundary, effectively enlarging it, repartition your disklabel(8) and possibly growfs(8) your filesystems. Norman. PS: Your OBSD installation is antiquated. Consider upgrading.
Re: cdio burning images
On Fri Nov 11 2011 23:07, John Tate wrote: > # cdio -f cd0c tao /home/john/ubuntu-11.10-desktop-i386.iso > cdio: The media can't be written in TAO mode > > What am I doing wrong? You don't read manuals. cdio(1): > -f device > Specifies the name of the CD device, such as /dev/rcd0c. Both > absolute and relative paths to /dev filenames are possible; the > raw partition name is added if needed. Meaning that when you specify "-f cd0" it internally converts it to "-f /dev/rcd0c". Also, you probably want to explore disklabel(8) and the difference between raw-level and block-level access of block devices. Read a UNIX book of your choice, or stick with Google hunting for an explanation. Norman.
Re: how to disable fsck when power failure
On Tue Nov 8 2011 12:03, Matteo Leccardi wrote: > > Disabling or skipping fsck(8)s is generally a very bad idea. > > > > Norman. > > > > @Norman: is it! BTW... > @Cosmo Wu > man 5 fstab is your friend. > Quick and dirt: Edit /etc/fstab and change the last digit of the > corrispondent mount point line form [1|2] to 0 > Ex. > default > 515f3560ef6f35f5.a / ffs rw 1 1 > to > 515f3560ef6f35f5.a / ffs rw 1 0 It must be said again, it is absolutely risky and unsafe to skip fsck(8)s for root filesystems in particular. If you have not taken any precaution to prevent or to detect a filesystem corruption, then chances are, you render your system non-operational very easily. You have the choice.
Re: how to disable fsck when power failure
On Tue Nov 8 2011 17:41, co...@tetrachina.com wrote: > misc#,Dz:C#! > > > > when the box with OpenBSD had a power failure and the system did not > unmount properly. > > it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. > > as a gateway ,so i can't go to fix it manually everytime.How do I advoid > this? Disabling or skipping fsck(8)s is generally a very bad idea. However, you could install a UPS. Further, partition your discs properly and mount filesystems, if possible, read-only. This greatly minimises the risk of filesystem inconsistencies/corruption. Norman.
Re: 5.0 vmt0 kernel panic in Linux KVM
On Mon Nov 7 2011 11:10, Walter Haidinger wrote: > Hi! > > Trying to upgrade to 5.0 fails with a kernel panic > (vmt0, see dmesg below). Previous 4.9 worked fine, > also 5.0 bsd.rd boots (dmesg below too). > > The VMware Tools driver seems to miss something - > "vmt0: failed to open backdoor RPC channel (TCLO protocol)" - > which is correct, as OpenBSD is _not_ run inside a VMware > virtual machine but in a Linux KVM (Kernel 3.0.4, > qemu-kvm 0.15.1). > > Is this a known problem? Searching for vmt on misc@ > did not show anything. I don't know either. But, you could try to disable the vmt(4) driver at boot. At the boot prompt, type "boot -c" to trigger the UKC. At the UKC prompt, type "disable vmt". Then type "quit". If your system boots up without errors, you can preserve this setting by using config(8): sudo /usr/sbin/config -e -f /bsd and typing "disable vmt" again. Save this by typing "quit". Good luck, Norman.
Re: The keyboard doesn't work in X after the most recent update
Hi Andreas, On Sat Nov 5 2011 18:45, Andreas Bartelt wrote: > On 11/05/11 15:39, tkdchen wrote: > >Hi all, > > > >My keyboard does not work in fvwm, GNOME or KDE after the most recent > >update. No key response except the Fn+brightness-up and down. > >I run 5.0-current on Thinkpad x201i. Thanks a lot for your help. > > I've noticed that the keyboard of an Asus EEE 701 also doesn't work > with Xorg on current (I followed the steps from current.html). > However, I didn't test any older versions of OpenBSD on this > netbook. > > Does anybody know if this a known or a new problem with this model? since 5.0, xenocara uses xkeyboard-config instead of the old /etc/X11/xkb. In the last couple of days, some code has been changed in xkeyboard-config, however, and made keyboards in X non-functional, when the /usr/X11R6/share/X11/xkb/symbols/srvr_ctrl directory was present. This directory was removed and replaced by a bare file [1]. So, chances are, older versions are not affected on your netbook. Best regards, Norman.
Re: The keyboard doesn't work in X after the most recent update
On Sat Nov 5 2011 22:39, tkdchen wrote: > Hi all, > > My keyboard does not work in fvwm, GNOME or KDE after the most recent > update. No key response except the Fn+brightness-up and down. > I run 5.0-current on Thinkpad x201i. Thanks a lot for your help. Remember to read http://www.openbsd.org/faq/current.html, before applying snapshots or updating your local cvs checkout and compiling from it. Norman.
Re: The keyboard doesn't work in X after the most recent update
On Sat Nov 5 2011 22:39, tkdchen wrote:
> Hi all,
>
> My keyboard does not work in fvwm, GNOME or KDE after the most recent
> update. No key response except the Fn+brightness-up and down.
> I run 5.0-current on Thinkpad x201i. Thanks a lot for your help.
This is a known bug in xkb. As suggested on tech@:
_symbols_dir=/usr/X11R6/share/X11/xkb/symbols/srvr_ctrl/srvr_ctrl
mv ${_symbols_dir}/srvr_ctrl ${_symbols_dir}/_srvr_ctrl
mv ${_symbols_dir}/_srvr_ctrl/srvr_ctrl ${_symbols_dir}
rmdir ${_symbols_dir}/_srvr_ctrl
Norman.
Re: kernel panic on openbsd i386 snapshot 20111103
On Sat Nov 5 2011 15:07, David Vasek wrote: > On Sat, 5 Nov 2011, Norman Golisz wrote: > > >On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote: > >>Am I barking up the wrong tree trying to deduce if I really do have a > >>hardware problem? I am open to accepting diffs and compiling from source if > >>other developers think there might be a bug to fix here. > > > >It seems to be a hardware fault. To trap memory issues, you could try > >memtest86+ [1]. > > >[1] http://www.memtest.org/ > > Or ports/sysutils/memtest86+, which is the same and as a package it > is easier to deal with - it can be loaded by boot(8) directly from > /stand on your root filesystem. No CDs, floppies etc. are needed. Thanks for the pointer. I was thinking of burning the ISO, but that's indeed better.
Re: kernel panic on openbsd i386 snapshot 20111103
On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote: > Am I barking up the wrong tree trying to deduce if I really do have a > hardware problem? I am open to accepting diffs and compiling from source if > other developers think there might be a bug to fix here. It seems to be a hardware fault. To trap memory issues, you could try memtest86+ [1]. Good luck, Norman [1] http://www.memtest.org/
Re: kernel panic on openbsd i386 snapshot 20111103
Hi Jeffrey,
On Sat Nov 5 2011 07:49, Forman, Jeffrey wrote:
> I am in the process of building a new OpenBSD i386 5.0-release Intel Atom
> D510-based fw/router. I was editing some config files on the box in emacs
> when the process threw a core dump. Thinking perhaps it was just emacs, I
> went to do something else, 'sudo pkg_add -v mutt', and received a coredump
> again.
>
> I went looking for stress testing apps, thinking I might have a bad CPU or
> RAM module and came upon 'stress'. After several iterations of stress
> seeming to cause kernel panics, and then upgrading to a 5.0 snapshot from
> November 13, 2011[1], I was still seeing panics. I provide the below detail
> to help those more knowledgeable in debugging.
>
> Thanks in advance,
> Jeff
>
> [1] http://openbsd.mirrors.tds.net/pub/OpenBSD/snapshots/i386/
>
> Full stress command line:
> # stress --cpu 8 --io 4 --vm 2 -m 5 --vm-bytes 128M --timeout 30s -v
I did this on my machine as well, it's a i386 single core processor
running a single processor kernel. I ran this stress test several times,
no panic. Your panic trace also indicates complications with uvm's page
fault handler and an MP locking mechanism involved.
Therefore, could you try bsd.sp and do the stress testing again? Is it
running well now?
Norman.
OpenBSD 5.0-current (GENERIC) #85: Wed Nov 2 22:27:31 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1.70GHz ("GenuineIntel" 686-class) 1.70
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2
real mem = 2146299904 (2046MB)
avail mem = 2101112832 (2003MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @ 0xfd750, SMBIOS
rev. 2.33 @ 0xe0010 (61 entries)
bios0: vendor IBM version "1RETDRWW (3.23 )" date 06/18/2007
bios0: IBM 2374VDL
apm0 at bios0: Power Management spec V1.2
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xfd6e0/0x920
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdea0/272 (15 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #6 is the last bus
bios0: ROM list: 0xc/0x1 0xdc000/0x4000! 0xe/0x1!
cpu0 at mainbus0: (uniprocessor)
cpu0: Enhanced SpeedStep 1695 MHz: speeds: 1700, 1400, 1200, 1000, 800, 600 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x5800/0x8
io address conflict 0x5808/0x4
io address conflict 0x5810/0x8
io address conflict 0x580c/0x4
pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xd000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: irq 11
drm0 at radeondrm0
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x81
pci2 at ppb1 bus 2
mem address conflict 0xb000/0x1000
mem address conflict 0xb100/0x1000
cbb0 at pci2 dev 0 function 0 "TI PCI4520 CardBus" rev 0x01: irq 11
cbb1 at pci2 dev 0 function 1 "TI PCI4520 CardBus" rev 0x01: irq 11
em0 at pci2 dev 1 function 0 "Intel PRO/1000MT (82540EP)" rev 0x03: irq 11,
address 00:11:25:32:45:72
iwi0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2200BG" rev 0x05: irq 11,
address 00:0e:35:bc:03:c1
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 6 device 0 cacheline 0x8, lattimer 0xb0
pcmcia1 at cardslot1
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x01: 24-bit timer
at 3579545Hz
pciide0 at pci0 dev 31 function 1 "Intel 82801DBM IDE" rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: irq 11
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM non-parity PC2700CL2.5
spdmem1 at iic0 addr 0x51: 1GB DDR SDRAM non-parity PC2700CL2.5
auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x01: irq 11, ICH4
AC97
ac97: codec id 0x41
Re: Copy root partition to another machine
On Fri Nov 4 2011 17:43, Bambero wrote: > Hello > > I want to copy my root partition to another with dd without ssh. Is > this correct: > > 1. On first machine: > dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror > > 2. On second machine: > dd if=root.img of=/dev/rwd0a bs=16b seek=1 > > May/should I ommit seek, skip, conv, bs parameters ? I'd recommend the use of dump(8) and restore(8). This has the advantage of only copying occupied bytes of your filesystem, which can drastically reduce the output's size and time required. Further, you don't run into issues when restoring your fs into a freshly created partition on a different machine, with a possibly different hard drive model and different geometry layout. You can even decide to change fs parameters before restoring your dump. Much more robust than dd'ing in this case. Finally, as others pointed out already, installboot(8) the boot blocks for your machine. Norman.
Re: Help setting up a PF NAT gateway
Hi Stefan, On Wed Oct 12 2011 14:59, Stefan Midjich wrote: > I must say that thanks to your help on this list I've finally managed > to get it working. I have bought FreeBSD CD sets in the past as a > means to donate and I intend to buy 5.0 sets now because I believe > strongly in open source software. really fine! > The only thing I have yet to solve is the ftp-proxy redirection. Here > is my current ruleset. Well, you defined this match for outgoing packets of vic2: > match out on vic2 inet from 10.221.181.10 to any nat-to (vic2) round-robin but allow the ftp-proxy to send packets from 127.0.0.1: > pass out inet proto tcp from 127.0.0.1 to any port = ftp flags S/SA keep state Hence, change the match rule to: > match out on vic2 inet all nat-to (vic2) round-robin Good luck, Norman
Re: cd and run app from rc.local
On Thu Oct 6 2011 06:17, Steve wrote: > Hi, > Can someone please point me in the right direction. [...] > I > understand this is probably unix 101 but I cant find it. Please read and understand rc.local(8) and [1]. In general you have two options: - add your script to rc.local(8), - create a rc.d(8) script which has a path to your script in the variable "daemon" and add its name to rc_scripts in rc.conf.local. See rc.d(8) and rc.subr(8). [1] http://openbsd.org/faq/faq10.html#rc
