Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Joe Gidi]

[big snip]
>> The newly installed system boots successfully, but then it seems to fail
>> to initialize video properly at the end of the boot process. My monitor
>> goes into an endless cycle of trying to sync up. I can ssh in and see
>> this
>> in /var/log/messages:
>>
>> Nov 26 11:45:55 opteron /bsd: root on sd0a (ef051b8fc18f2fbe.a) swap on
>> sd0b dump on sd0b
>> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
>> Nov 26 11:45:55 opteron /bsd: drm:pid0:evergreen_init *ERROR* disabling
>> GPU acceleration
>> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
>> 0x802922c0 unpin not necessary
>> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
>> 0x802922c0 unpin not necessary
>> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
>> Nov 26 11:45:55 opteron /bsd: error: [drm:pid0:radeonfb_create] *ERROR*
>> failed to create fbcon object -12
>> Nov 26 11:45:55 opteron ntpd[27846]: /var/db/ntpd.drift is empty
>> Nov 26 11:45:55 opteron savecore: no core dump
>>
>> My video card is:
>> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00
>> drm0 at radeondrm0
>> radeondrm0: msi
>>
>> And the radeondrm-firmware-20150927 package is installed.
>>
>> Thanks again for all your help.

I had a few more minutes to play around with this today. Disabling
radeondrm in ukc results in a usable console. Here's a dmesg:

OpenBSD 5.8-current (GENERIC.MP) #1666: Thu Nov 26 00:22:53 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8470441984 (8078MB)
avail mem = 8209608704 (7829MB)
User Kernel Config
UKC> disable radeondrm
214 radeondrm* disabled
UKC> quit
Continuing...
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbc41b018 (58 entries)
bios0: vendor American Megatrends Inc. version "2601" date 03/24/2015
bios0: ASUSTeK COMPUTER INC. M5A97 LE R2.0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT BGRT
acpi0: wakeup devices SBAZ(S4) PS2K(S3) PS2M(S3) UAR1(S4) P0PC(S4)
UHC1(S4) UHC2(S4) UHC4(S4) UHC6(S4) UHC7(S4) PC02(S4) PC03(S4) PC04(S4)
PC05(S4) PC06(S4) PC07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD Opteron(tm) Processor 3350 HE, 2809.74 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 19 (application processor)
cpu3: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR

Re: can't boot from USB3.0 flash memory

[Dragos Ruiu]

It might also be a bios setting issue.  (Many BIOS have settings for which
systems are enabled by the BIOS code)
Try enabling "Legacy USB Support" or similar.

Cheers,
--dr

-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Nick Holland
Sent: November 26, 2015 3:59 AM
To: misc@openbsd.org
Subject: Re: can't boot from USB3.0 flash memory

On 11/26/15 08:25, freeu...@ruggedinbox.com wrote:
> I have USB3.0 flash memory.(SANDISK)
> "OpenBSD 5.8 amd64/i386 on USB3.0"
> 
> 1.USB3.0 flash memory connect to USB2.0/1.0
> boot: It's fine.
> 2.USB3.0 flash memory connect to USB3.0
> boot: can't boot!
> 
> anyone don't need boot from USB3.0?

LOTS of details missing here, but if you are saying that under whatever
mysterious circumstance you can not get the USB3 device to boot it doesn't
try to boot at all, this is not an OpenBSD issue.

OpenBSD's boot process is dependent upon the system BIOS until the kernel is
loaded.  So, if there is no attempt to boot, you have a BIOS issue.  I've
certainly seen this.  The answer is a BIOS upgrade that probably doesn't
exist, because many manufacturers barely test this feature.  Nothing OpenBSD
can do to fix it if the HW won't grab and run the boot code.

Nick.

Re: vmmctl and vmd problem

[Norman Golisz]

> 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.

Wireless PCI hardware

[Alexander Salmin]

Hey friends,

I want OpenBSD in hostap mode with PCI or PCIe ath / athn driver.

I am not interested in USB Wifi which has recently been discussed
on this list, already have a good usb wifi that works well for its 
purpose (thanks!).


Instead I have been checking out the ath(4) and athn(4) driver manuals
for compatible pci or pcie cards.

I would love to go haywire and buy more cards in my local store and test
them, but once I open the seal; I can't return them. Yes, I tried, this 
is not

an option anymore, spent too much money on it. :-|

If you recently bought a PCI or PCIe wireless card with atheros chipset
that works for OpenBSD, please report which name/model/manufacturer and 
preferably ~buydate so we know if its recently or might been replaced by 
new version.


Or, if you are running a computer store or similar or have a friend that 
does,

maybe you can help with testing(?).

Cards I have not yet tested which I'm thinking of buying, any advise on 
these?

Both are quite cheap.

- TP-Link TL-WN851ND
- TP-Link TL-WDN4800


Alexander

Re: Wireless PCI hardware

[Kevin Chadwick]

> I want OpenBSD in hostap mode with PCI or PCIe ath / athn driver.
> 
> 
> If you recently bought a PCI or PCIe wireless card with atheros chipset
> that works for OpenBSD, please report which name/model/manufacturer and 
> preferably ~buydate so we know if its recently or might been replaced by 
> new version.
> 
> Cards I have not yet tested which I'm thinking of buying, any advise on 
> these?
> Both are quite cheap.
> 
> - TP-Link TL-WN851ND
> - TP-Link TL-WDN4800

Don't know about PCI but could get cardbus adaptor for d-link DWA-652
that works well for me or look up it's chip. What usb are you using as
the ones i tried a while back weren't much good though there have been
changes to the drivers since so probably worth trying again.

http://www.ebay.co.uk/itm/D-Link-DWA-652-Xtreme-N-Wireless-Notebook-Adapter-Draft-/400461073245?hash=item5d3d570b5d:g:HdsAAOxyrP9RZur0

-- 

KISSIS - Keep It Simple So It's Securable

em0 ... cannot find mem space

[Mikkel C. Simonsen]

Today I installed an Intel 82546EB dual-port NIC in a Fujitsu Siemens
Futro S400, that I plan to use as a router/firewall.

Only one of the interfaces shows up in dmesg, and it's not working after
boot. Is this a known problem, and is there a fix? Full dmesg attached.

Mikkel C. Simonsen



OpenBSD 5.8 (GENERIC) #1066: Sun Aug 16 02:33:00 MDT 2015
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2
cache) 1.01 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,MPC,MMXX,3DNOW2,3DNOW
real mem  = 251084800 (239MB)
avail mem = 233758720 (222MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 05/14/08, BIOS32 rev. 0 @ 0xfaa30, SMBIOS rev.
2.2 @ 0xf (31 entries)
bios0: vendor Phoenix Technologies, LTD version "6.00PG Rev. 4.00.0Q"
date 05/14/2008
bios0: FUJITSU SIEMENS FUTRO S400
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP SSDT
acpi0: wakeup devices USB0(S5) USB1(S5) USB2(S5) USB3(S5) AMR0(S4)
UAR1(S5) UAR2(S5) PS2M(S5) PS2K(S4) PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpitz0 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xc000 0xcc000/0x4000!
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: PowerNow! K7 1001 MHz: speeds: 1000 800 667 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
0:7:1: mem address conflict 0x100/0x10
0:7:1: mem address conflict 0x100/0x10
0:7:1: mem address conflict 0x100/0x100
pchb0 at pci0 dev 0 function 0 "SiS 741 PCI" rev 0x03
sisagp0 at pchb0
agp0 at sisagp0: aperture at 0xe800, size 0x400
ppb0 at pci0 dev 1 function 0 "SiS 86C202 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SiS 6330 VGA" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 "SiS 85C503 System" rev 0x25
pciide0 at pci0 dev 2 function 5 "SiS 5513 EIDE" rev 0x00: 741: DMA,
channel 0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 1-sector PIO, LBA48, 3815MB, 7813120 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 3 function 0 "SiS 5597/5598 USB" rev 0x0f: irq 3,
version 1.0, legacy support
ohci1 at pci0 dev 3 function 1 "SiS 5597/5598 USB" rev 0x0f: irq 5,
version 1.0, legacy support
ehci0 at pci0 dev 3 function 3 "SiS 7002 USB" rev 0x00: irq 12
ehci0: timed out waiting for BIOS
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "SiS EHCI root hub" rev 2.00z/1.00 addr 1
em0 at pci0 dev 7 function 0 "Intel 82546EB" rev 0x01: cannot find mem space
unknown vendor 0x8186 product 0x1010 (class network subclass ethernet,
rev 0x01) at pci0 dev 7 function 1 not configured
re0 at pci0 dev 9 function 0 "Realtek 8169SC" rev 0x10: RTL8169/8110SCd
(0x1800), irq 15, address 00:90:dc:a3:5e:c3
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 2
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbc0: unable to establish interrupt for irq 12pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
wbsio0 at isa0 port 0x2e/2: W83697HF rev 0x12
lm1 at wbsio0 port 0x290/8: W83697HF
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "SiS OHCI root hub" rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 "SiS OHCI root hub" rev 1.00/1.00 addr 1
umass0 at uhub1 port 2 configuration 1 interface 0 "TEAC TEAC FD-05PUB"
rev 1.10/0.00 addr 2
umass0: using UFI over CBI with CCI
scsibus1 at umass0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0:  ATAPI 0/direct
removable
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (558bcbde01142a1f.a) swap on wd0b dump on wd0b

Re: OpenBSD as a pentester PC?

[Chris Smith]

On Thu, Nov 26, 2015, at 10:23 PM, Mohammad BadieZadegan wrote:
> Hi every OpenBSD user,
> I have OpenBSD on my Notebook since 2 years ago and I don't want to
> switch
> other OS for my business pentest project.
> I need some pentest tools for my project like metasploit, fuzzers, ..etc
> but I could not find them on OpenBSD package list
> !
> By default does OpenBSD support metasploit installing (or any attack
> tools)
> or defer them for security purpose?
> I want to have one OS on my note book for all purpose(business+home).
> Is that I must switch to other OS? (That I don't like at all!)
> Regards.
> 
> -- 
> [image: ( openbsd.pro  933k.ir )] 
> 

To be honest, some security tools can be so poorly written, or perform
unusual or dangerous operations in their daily usages, that they present
a difficult challenge to properly secure and port to other OS's. You
don't really want them on your "main" system.

As a pentester myself, I usually end up with some very basic tools on my
host system (e.g. nmap, nc, hping etc...) and segregating all of the
other rubbish into a kali or debian virtual machine, which can then be
wiped or rolled back between jobs to ensure both system integrity, and
that jobs do not cross-pollinate data between them.

In my opinion, the best way to advance OpenBSD's use in this area is to
support, test and develop its virtualisation capabilities.

>  I want to have one OS on my note book for all purpose(business+home)

If you're doing this professionally, I really do not recommend this
without proper segregation. Especially if you're handling your customers
sensitive data or functionality (e.g. network connectivity).

Cheers,
Chris.

Re: Wireless PCI hardware

[Alexander Salmin]

Don't know about PCI but could get cardbus adaptor for d-link DWA-652
that works well for me or look up it's chip. What usb are you using as
the ones i tried a while back weren't much good though there have been
changes to the drivers since so probably worth trying again.

http://www.ebay.co.uk/itm/D-Link-DWA-652-Xtreme-N-Wireless-Notebook-Adapter-Draft-/400461073245?hash=item5d3d570b5d:g:HdsAAOxyrP9RZur0

For USB I am using the run(4) driver for Ralink 802.11n product 
Netsys98N but my head hurts a bit while using it. Not so good for 
long-term use. :-) Works extremely well though, very long-range. But 
still, looking for PCI/PCIe.


http://www.dx.com/p/netsys-98n-2-4ghz-4200mw-high-power-802-11b-g-n-150mbps-usb-wi-fi-wireless-network-adapter-93722#.Vled1noy30M

Re: OpenBSD as a pentester PC?

[Stuart McMurray]

On Thursday, November 26, 2015, Chris Smith  wrote:

> On Thu, Nov 26, 2015, at 10:23 PM, Mohammad BadieZadegan wrote:
> > Hi every OpenBSD user,
> > I have OpenBSD on my Notebook since 2 years ago and I don't want to
> > switch
> > other OS for my business pentest project.
> > I need some pentest tools for my project like metasploit, fuzzers, ..etc
> > but I could not find them on OpenBSD package list
> > !
> > By default does OpenBSD support metasploit installing (or any attack
> > tools)
> > or defer them for security purpose?
> > I want to have one OS on my note book for all purpose(business+home).
> > Is that I must switch to other OS? (That I don't like at all!)
> > Regards.
> >
> > --
> > [image: ( openbsd.pro  933k.ir )] 
> >
>
> To be honest, some security tools can be so poorly written, or perform
> unusual or dangerous operations in their daily usages, that they present
> a difficult challenge to properly secure and port to other OS's. You
> don't really want them on your "main" system.
>
> As a pentester myself, I usually end up with some very basic tools on my
> host system (e.g. nmap, nc, hping etc...) and segregating all of the
> other rubbish into a kali or debian virtual machine, which can then be
> wiped or rolled back between jobs to ensure both system integrity, and
> that jobs do not cross-pollinate data between them.
>
> In my opinion, the best way to advance OpenBSD's use in this area is to
> support, test and develop its virtualisation capabilities.
>
> >  I want to have one OS on my note book for all purpose(business+home)
>
> If you're doing this professionally, I really do not recommend this
> without proper segregation. Especially if you're handling your customers
> sensitive data or functionality (e.g. network connectivity).
>
> Cheers,
> Chris.
>
>
I do much the same, with two VMs, though.  I use the OpenBSD VM for
on-the-spot development more than general use.

The other thing I've found OpenBSD great for as a pentester is quickly
putting together small networks of virtual machines for either testing
things or for one-off demonstrations.


-- 
J. Stuart McMurray

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Jonathan Gray]

On Thu, Nov 26, 2015 at 11:51:03AM -0500, Joe Gidi wrote:
> The newly installed system boots successfully, but then it seems to fail
> to initialize video properly at the end of the boot process. My monitor
> goes into an endless cycle of trying to sync up. I can ssh in and see this
> in /var/log/messages:
> 
> Nov 26 11:45:55 opteron /bsd: root on sd0a (ef051b8fc18f2fbe.a) swap on
> sd0b dump on sd0b
> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
> Nov 26 11:45:55 opteron /bsd: drm:pid0:evergreen_init *ERROR* disabling
> GPU acceleration
> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
> 0x802922c0 unpin not necessary
> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
> 0x802922c0 unpin not necessary
> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
> Nov 26 11:45:55 opteron /bsd: error: [drm:pid0:radeonfb_create] *ERROR*
> failed to create fbcon object -12
> Nov 26 11:45:55 opteron ntpd[27846]: /var/db/ntpd.drift is empty
> Nov 26 11:45:55 opteron savecore: no core dump
> 
> My video card is:
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00
> drm0 at radeondrm0
> radeondrm0: msi
> 
> And the radeondrm-firmware-20150927 package is installed.

Can you include a full dmesg when booted via uefi with radeondrm
still enabled? pcidump -v output would be helpful as well.

We may have to read the video bios out of the acpi VFCT table
when booting via efi and the radeondrm code doesn't do that currently.

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Joe Gidi]

On Thu, November 26, 2015 10:13 pm, Jonathan Gray wrote:
> Can you include a full dmesg when booted via uefi with radeondrm
> still enabled? pcidump -v output would be helpful as well.
>
> We may have to read the video bios out of the acpi VFCT table
> when booting via efi and the radeondrm code doesn't do that currently.

Sure, here you go:

OpenBSD 5.8-current (GENERIC.MP) #1666: Thu Nov 26 00:22:53 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8470441984 (8078MB)
avail mem = 8209608704 (7829MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbc41b018 (58 entries)
bios0: vendor American Megatrends Inc. version "2601" date 03/24/2015
bios0: ASUSTeK COMPUTER INC. M5A97 LE R2.0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT BGRT
acpi0: wakeup devices SBAZ(S4) PS2K(S3) PS2M(S3) UAR1(S4) P0PC(S4)
UHC1(S4) UHC2(S4) UHC4(S4) UHC6(S4) UHC7(S4) PC02(S4) PC03(S4) PC04(S4)
PC05(S4) PC06(S4) PC07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD Opteron(tm) Processor 3350 HE, 2809.72 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 19 (application processor)
cpu3: AMD Opteron(tm) Processor 3350 HE, 2809.37 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCN
T,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR
8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,
BMI1
cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 6 pa 0xfec2, version 21, 32 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0PC)
acpiprt2 at acpi0: bus 1 (PC02)
acpiprt3 at acpi0: bus -1 (PC03)
acpiprt4 at acpi0: bus 2 (PC04)
acpiprt5 at acpi0: bus -1 (PC05)
acpiprt6 at acpi0: bus -1 (PC06)
acpiprt7 at acpi0: bus 3 (PC07)
acpiprt8 at acpi0: bus -1 (PC09)
acpiprt9 at acpi0: bus -1 (PC0A)
acpiprt10 at acpi0: bus -1 (PC0B)
acpiprt11 at acpi0: bus -1 (PC0C)
acpiprt12 at acpi0: bus -1 (PC0D)
acpiprt13 at acpi0: bus -1 (PE20)
acpiprt14 at acpi0: bus -1 (PE21)
acpiprt15 at acpi0: bus -1 (PE22)
acpiprt16 at acpi0: bus -1 (PE23)
acpiec0 

Relayd mail notification

[Luiz Gustavo Costa]

Hi list !

My question is simple, but i can not have a horizon !

I want to notify by email when a host of redirect or relay list goes
offline, but could not know where i have to change.

Where can i get this status change log?

there is an option "log" in relayctl command, but have not found
documentation about it.

Can anyone help me on this ?

Thanks !

---
Luiz Gustavo Costa (Powered by BSD)
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
mundoUnix - Consultoria em Software Livre
http://www.mundounix.com.br
ICQ: 2890831 / MSN: cont...@mundounix.com.br
Blog: http://www.luizgustavo.pro.br

Re: em0 ... cannot find mem space

[Jonathan Gray]

On Fri, Nov 27, 2015 at 12:56:36AM +0100, Mikkel C. Simonsen wrote:
> Today I installed an Intel 82546EB dual-port NIC in a Fujitsu Siemens
> Futro S400, that I plan to use as a router/firewall.
> 
> Only one of the interfaces shows up in dmesg, and it's not working after
> boot. Is this a known problem, and is there a fix? Full dmesg attached.
> 
> Mikkel C. Simonsen

It sounds like your system didn't setup the pci bar correctly.
pcidump -v will give more details on that.

0x8186 is unheard of for intel pci nics.

Be warned that machines with sis chipsets are horrible, I'm glad they
stopped making them a while back.

> 
> 
> 
> OpenBSD 5.8 (GENERIC) #1066: Sun Aug 16 02:33:00 MDT 2015
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2
> cache) 1.01 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,MPC,MMXX,3DNOW2,3DNOW
> real mem  = 251084800 (239MB)
> avail mem = 233758720 (222MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 05/14/08, BIOS32 rev. 0 @ 0xfaa30, SMBIOS rev.
> 2.2 @ 0xf (31 entries)
> bios0: vendor Phoenix Technologies, LTD version "6.00PG Rev. 4.00.0Q"
> date 05/14/2008
> bios0: FUJITSU SIEMENS FUTRO S400
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP SSDT
> acpi0: wakeup devices USB0(S5) USB1(S5) USB2(S5) USB3(S5) AMR0(S4)
> UAR1(S5) UAR2(S5) PS2M(S5) PS2K(S4) PCI0(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0: C1(@1 halt!), PSS
> acpitz0 at acpi0: critical temperature is 100 degC
> acpibtn0 at acpi0: PWRB
> bios0: ROM list: 0xc/0xc000 0xcc000/0x4000!
> cpu0 at mainbus0: (uniprocessor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: PowerNow! K7 1001 MHz: speeds: 1000 800 667 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> 0:7:1: mem address conflict 0x100/0x10
> 0:7:1: mem address conflict 0x100/0x10
> 0:7:1: mem address conflict 0x100/0x100
> pchb0 at pci0 dev 0 function 0 "SiS 741 PCI" rev 0x03
> sisagp0 at pchb0
> agp0 at sisagp0: aperture at 0xe800, size 0x400
> ppb0 at pci0 dev 1 function 0 "SiS 86C202 AGP" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "SiS 6330 VGA" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 2 function 0 "SiS 85C503 System" rev 0x25
> pciide0 at pci0 dev 2 function 5 "SiS 5513 EIDE" rev 0x00: 741: DMA,
> channel 0 configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 1-sector PIO, LBA48, 3815MB, 7813120 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> ohci0 at pci0 dev 3 function 0 "SiS 5597/5598 USB" rev 0x0f: irq 3,
> version 1.0, legacy support
> ohci1 at pci0 dev 3 function 1 "SiS 5597/5598 USB" rev 0x0f: irq 5,
> version 1.0, legacy support
> ehci0 at pci0 dev 3 function 3 "SiS 7002 USB" rev 0x00: irq 12
> ehci0: timed out waiting for BIOS
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "SiS EHCI root hub" rev 2.00z/1.00 addr 1
> em0 at pci0 dev 7 function 0 "Intel 82546EB" rev 0x01: cannot find mem space
> unknown vendor 0x8186 product 0x1010 (class network subclass ethernet,
> rev 0x01) at pci0 dev 7 function 1 not configured
> re0 at pci0 dev 9 function 0 "Realtek 8169SC" rev 0x10: RTL8169/8110SCd
> (0x1800), irq 15, address 00:90:dc:a3:5e:c3
> rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 2
> isa0 at pcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbc0: unable to establish interrupt for irq 12pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> wbsio0 at isa0 port 0x2e/2: W83697HF rev 0x12
> lm1 at wbsio0 port 0x290/8: W83697HF
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> usb1 at ohci0: USB revision 1.0
> uhub1 at usb1 "SiS OHCI root hub" rev 1.00/1.00 addr 1
> usb2 at ohci1: USB revision 1.0
> uhub2 at usb2 "SiS OHCI root hub" rev 1.00/1.00 addr 1
> umass0 at uhub1 port 2 configuration 1 interface 0 "TEAC TEAC FD-05PUB"
> rev 1.10/0.00 addr 2
> umass0: using UFI over CBI with CCI
> scsibus1 at umass0: 2 targets, initiator 0
> sd0 at scsibus1 targ 1 lun 0:  ATAPI 0/direct
> removable
> vscsi0 at root
> scsibus2 at vscsi0: 256 targets
> softraid0 at root
> scsibus3 at softraid0: 256 targets
> root on wd0a (558bcbde01142a1f.a) swap on wd0b dump on wd0b

Re: Relayd mail notification

[Gleydson Soares]

On Fri, Nov 27, 2015 at 12:56:22AM -0200, Luiz Gustavo Costa wrote:
> Hi list !
> 
> My question is simple, but i can not have a horizon !
> 
> I want to notify by email when a host of redirect or relay list goes
> offline, but could not know where i have to change.
> 
> Where can i get this status change log?
> 
> there is an option "log" in relayctl command, but have not found
> documentation about it.
> 
> Can anyone help me on this ?

the output of `relayctl show summary' isn't enough?

relayd supports send SNMP trap when the state of a host changes.
so it seems easy to integrate with any NMS solution.

// gsoares

Re: MacbookPro 11,1

[Joerg Jung]

> Am 26.11.2015 um 00:50 schrieb Bryan Vyhmeister :
>
>> On Thu, Nov 26, 2015 at 12:02:18AM +0100, Joerg Jung wrote:
>> The problem with the MacBook8,1 is the USB trackpad/keyboard is connected
>> via SPI internally.  No SPI driver in OpenBSD.
>> Moreover, the internal SSD is connected via NVMe, also not supported.
>>
>> Also, both seem not really working in any other open source OS yet.
>> See here http://moepi.net/?page_id=213
>>
>> Interesting is, MacBookPro12,1 seems to use same SPI Trackpad as well,
>> but (ACPI?) behaves differently and seems working using Linux, see here:
>> http://www.spinics.net/lists/linux-acpi/msg61848.html
>
> Perhaps all the "Force Touch" trackpads are SPI connected?
>
>>> His solution was a
>>> USB keyboard and a USB hub. I didn't have either handy but may try that
>>> later today. In the case of the 12-inch Retina MacBook, there is only
>>> that single USB-C port so I'm not sure if the USB hub was needed for any
>>> reason other than to provide at least two ports (one for USB flash drive
>>> and one for USB keyboard).
>>
>> No real success here, the USB 3.x hub I tried was passive (likely not
enough power)
>> and crashed the machine on attach/detach.
>
> It sounds like the MacBook8,1 does not work for now then. That's too
> bad. I wonder if the MacBookPro11,4 (2015 15-inch with integrated
> graphics) also has the same SPI trackpad? I wonder if it also has
> storage issues with OpenBSD?
>
> My goal is to document how well OpenBSD works on all the recent Apple
> hardware I can. I'm intending to purchase a MacBookPro11,1 (2014
> 13-inch) which it sounds like from the thread works pretty well. I am
> interested to find out if the SD card slot works.
>
> I'm also hoping to find out more about the storage, SD card, and
> trackpad of the MacBookPro11,4 (2015 15-inch with integrated graphics)
> and also of the MacBookPro11,2 (2014 15-inch with integrated graphics).
> Both of these machines still have Haswell chips (unlike the
> MacBookPro12,1).
>
> The MacBookAir6,1 (2013/2014 11-inch MacBook Air) I have works very well
> in all respects but since it's the 11-inch it does not have an SD card
> and my MacBookAir7,2 (2015 13-inch MacBook Air) works reasonably well
> but lacks X acceleration (due to Broadwell) and the brightness cannot be
> adjusted with xbacklight(1). The SD card slot also is not detected in
> any way.

Can you send a dmesg for this Air7,2 please?

> I'm hoping to get some feedback on the SD card slot on the
> MacBookAir6,2 if possible as well.
>
> Bryan

Re: OpenBSD 5.7-stable/OpenSMTPD 5.4.4 error: client did not present certificate

[David Dahlberg]

Am Mittwoch, den 25.11.2015, 18:51 +0100 schrieb Gianluca D.Muscelli:
> Hi, if i use verify in /etc/smtpd.conf sometimes I reciveerrors like
> this:
[..]
> Nov 25 16:33:05 server smtpd[12808]: smtp-in: Disconnecting session
> 95548f7f974b7523: client did not present certificate
> 
> Any suggestion to fix this problem?

There ain't any fix, because this behaviour is exactly the one that you
requested:

>listen on egress pki mail.example.it tls-require verify 

smtpd.conf(5)
| If tls-require verify is specified, the client must provide a valid 
| certificate to be able to establish an SMTP session.

If you don't want this, don't use it.

BTW, you have other problems as well (found out while trying to PM):

$ dig gianlucamuscelli.it MX
gianlucamuscelli.it.85780   IN  MX \
0 mail.gianlucamuscelli.it.
$ dig mail.gianlucamuscelli.it A
mail.gianlucamuscelli.it has address 192.168.1.30
$ dig mail.gianlucamuscelli.it 
;; connection timed out; no servers
could be reached

$ dig gianlucamuscelli.it NS
gianlucamuscelli.it.85923   IN  NS  ns1.gianluc
amuscelli.it.
gianlucamuscelli.it.85923   IN  NS  ns2.gianluc
amuscelli.it.
$ dig ns1.gianlucamuscelli.it A
ns1.gianlucamuscelli.it. 85923  IN  A   192.168.1.30
$ dig ns2.gianlucamuscelli.it 
;; connection timed out; no servers could be reached
$ dig ns2.gianlucamuscelli.it A
ns2.gianlucamuscelli.it. 85923  IN  A   192.168.1.30
$ dig ns2.gianlucamuscelli.it 
;; connection timed out; no servers could be reached

OpenBSD as a pentester PC?

[Mohammad BadieZadegan]

Hi every OpenBSD user,
I have OpenBSD on my Notebook since 2 years ago and I don't want to switch
other OS for my business pentest project.
I need some pentest tools for my project like metasploit, fuzzers, ..etc
but I could not find them on OpenBSD package list
!
By default does OpenBSD support metasploit installing (or any attack tools)
or defer them for security purpose?
I want to have one OS on my note book for all purpose(business+home).
Is that I must switch to other OS? (That I don't like at all!)
Regards.

-- 
[image: ( openbsd.pro  933k.ir )] 

Re: OpenBSD as a pentester PC?

[Jiri B]

On Thu, Nov 26, 2015 at 12:53:47PM +0330, Mohammad BadieZadegan wrote:
> Hi every OpenBSD user,
> I have OpenBSD on my Notebook since 2 years ago and I don't want to switch
> other OS for my business pentest project.
> I need some pentest tools for my project like metasploit, fuzzers, ..etc
> but I could not find them on OpenBSD package list
> !
> By default does OpenBSD support metasploit installing (or any attack tools)
> or defer them for security purpose?
> I want to have one OS on my note book for all purpose(business+home).
> Is that I must switch to other OS? (That I don't like at all!)
> Regards.

Hi,

see http://www.openbsd.org/faq/ports/index.html

We would be happy to help you to bring more such tools to OpenBSD
ports.

Also check this one https://github.com/jasperla/openbsd-wip, maybe
somebody has started working on some of yours wanted apps.

j.

Re: OpenBSD as a pentester PC?

[Joshua Padman]

Hi,

Its not really set up for this

However, metasploit needs postgres + ruby. Other software is mainly java or
python based..

This would take considerable effort as hackers tend to work towards getting
stuff done rather than neat and nice cross platform compatibility.


On Thu, Nov 26, 2015 at 8:23 PM, Mohammad BadieZadegan 
wrote:

> Hi every OpenBSD user,
> I have OpenBSD on my Notebook since 2 years ago and I don't want to switch
> other OS for my business pentest project.
> I need some pentest tools for my project like metasploit, fuzzers, ..etc
> but I could not find them on OpenBSD package list
> !
> By default does OpenBSD support metasploit installing (or any attack tools)
> or defer them for security purpose?
> I want to have one OS on my note book for all purpose(business+home).
> Is that I must switch to other OS? (That I don't like at all!)
> Regards.
>
> --
> [image: ( openbsd.pro  933k.ir )] 

output of pkg_check(1)

[Jan Stary]

The output of "pkg_check -x -v -D nosig"
(full log bellow) on current/amd64 confuses me.

Firstly,

  System libs NOT in locate dbs:
/usr/X11R6/lib/libEGL.so.0.0
/usr/X11R6/lib/libGL.so.15.0
/usr/X11R6/lib/libglapi.so.0.0

but

$ locate /usr/X11R6/lib/libEGL.so.0.0
/usr/X11R6/lib/libEGL.so.0.0
$ locate /usr/X11R6/lib/libGL.so.15.0
/usr/X11R6/lib/libGL.so.15.0
$ locate /usr/X11R6/lib/libglapi.so.0.0
/usr/X11R6/lib/libglapi.so.0.0

and the files themselves exist.
In fact, /var/db/locate.database is an hour old.

Does "not in locate dbs" mean something else?
Does pkg_check use the locate db instead of checking the files themselves?

Why does pkg_check care about /usr/X11R6/lib,
and why exactly these three? Is it because some
installed package mentioned them as a dependency?


Next, there is a section of files "not found":

  Not found:
/boot
/bsd
/bsd.rd
/bsd.sp
/dload
...

None of these belongs to an installed package, obviously,
but why would pkg_check even consider them? Manpage says

   Other files
  Checks that there are no other random objects under /usr/local.

but this is not /usr/local. There is /var/spool etc
- seems like the whole / is traversed.


Lastly,

  In dbus-1.10.4v0:x11/dbus,-main:
/etc/machine-id
  In libxml-2.9.2p3:textproc/libxml,-main:
/var/db/xmlcatalog

Yes, these exist, and presumably belong those packages.
What about them?

Jan


full script(1):

# pkg_check -x -v -D nosig
System libs NOT in locate dbs:
/usr/X11R6/lib/libEGL.so.0.0
/usr/X11R6/lib/libGL.so.15.0
/usr/X11R6/lib/libglapi.so.0.0

Not found:
/boot
/bsd
/bsd.rd
/bsd.sp
/dload
/etc/X11/app-defaults/GV
/etc/X11/app-defaults/Gnuplot
/etc/X11/xdm/authdir
/etc/examples/ftpchroot
/etc/examples/hosts.lpd
/etc/fonts/conf.d/10-autohint.conf
/etc/fstab
/etc/hostname.re0
/etc/hosts
/etc/iked/local.pub
/etc/iked/private/local.key
/etc/isakmpd/local.pub
/etc/isakmpd/private/local.key
/etc/man.conf
/etc/mixerctl.conf
/etc/mixerctl.conf.onboard
/etc/mk.conf
/etc/mygate
/etc/myname
/etc/pkg.conf
/etc/random.seed
/etc/rc.conf.local
/etc/resolv.conf
/etc/resolv.conf.tail
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_dsa_key.pub
/etc/ssh/ssh_host_ecdsa_key
/etc/ssh/ssh_host_ecdsa_key.pub
/etc/ssh/ssh_host_ed25519_key
/etc/ssh/ssh_host_ed25519_key.pub
/etc/ssh/ssh_host_rsa_key
/etc/ssh/ssh_host_rsa_key.pub
/etc/usermgmt.conf
/media
/obsd
/pflogd.core
/root/.aucat_cookie
/root/.config
/root/.forward
/root/.ssh
/root/.viminfo
/root/.vimrc
/root/Mail
/root/OLD
/root/TODO
/root/man.conf
/root/manpages.BekKbaACeqGG
/root/manpages.Rc8jp6G_lwXv
/root/manpages.iZk17KSJKAbP
/root/manpages.qAjqJw7JLGpZ
/root/manpages.sCWRaNUv_HkX
/root/manpages.wDzeT7NkP2jH
/root/typescript
/usr/X11R6/include/freetype2/config
/usr/X11R6/include/freetype2/freetype.h
/usr/X11R6/include/freetype2/ftadvanc.h
/usr/X11R6/include/freetype2/ftbbox.h
/usr/X11R6/include/freetype2/ftbdf.h
/usr/X11R6/include/freetype2/ftbitmap.h
/usr/X11R6/include/freetype2/ftbzip2.h
/usr/X11R6/include/freetype2/ftcache.h
/usr/X11R6/include/freetype2/ftcffdrv.h
/usr/X11R6/include/freetype2/ftchapters.h
/usr/X11R6/include/freetype2/ftcid.h
/usr/X11R6/include/freetype2/fterrdef.h
/usr/X11R6/include/freetype2/fterrors.h
/usr/X11R6/include/freetype2/ftfntfmt.h
/usr/X11R6/include/freetype2/ftgasp.h
/usr/X11R6/include/freetype2/ftglyph.h
/usr/X11R6/include/freetype2/ftgxval.h
/usr/X11R6/include/freetype2/ftgzip.h
/usr/X11R6/include/freetype2/ftimage.h
/usr/X11R6/include/freetype2/ftincrem.h
/usr/X11R6/include/freetype2/ftlcdfil.h
/usr/X11R6/include/freetype2/ftlist.h
/usr/X11R6/include/freetype2/ftlzw.h
/usr/X11R6/include/freetype2/ftmac.h
/usr/X11R6/include/freetype2/ftmm.h
/usr/X11R6/include/freetype2/ftmodapi.h
/usr/X11R6/include/freetype2/ftmoderr.h
/usr/X11R6/include/freetype2/ftotval.h
/usr/X11R6/include/freetype2/ftoutln.h
/usr/X11R6/include/freetype2/ftpfr.h
/usr/X11R6/include/freetype2/ftrender.h
/usr/X11R6/include/freetype2/ftsizes.h
/usr/X11R6/include/freetype2/ftsnames.h
/usr/X11R6/include/freetype2/ftstroke.h
/usr/X11R6/include/freetype2/ftsynth.h
/usr/X11R6/include/freetype2/ftsystem.h

5.8-release does not properly unmount / on reboot

[Marko Cupać]

Hi,

this has been reported earlier here on the list:
http://www.mail-archive.com/misc%40openbsd.org/msg141046.html

I have the same problem of unclean reboots on pcengines apu1d with
5.8-release installed on sdcard. I hoped some of the errata patches
will fix it, but up until 007 none did. halt -p is fine, reboot and
shutdown -r result in unclean unmount.

Here's dmesg:

OpenBSD 5.8 (GENERIC.MP) #2: Thu Nov 26 10:23:47 CET 2015
pac...@sarajevo.kappastar.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
ff
real mem = 2098511872 (2001MB)
avail mem = 2031079424 (1936MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e16d820 (7 entries)
bios0: vendor coreboot version "4.0" date 09/08/2014
bios0: PC Engines APU
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT
acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4)
PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3)
UOH3(S3) UOH4(S3) UOH5(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD G-T40E Processor, 1000.14 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,L
ONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully
associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD G-T40E Processor, 1000.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,L
ONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 16-way L2 cache
cpu1: 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully
associative
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
acpiprt0 at acpi0: bus -1 (AGPB)
acpiprt1 at acpi0: bus -1 (HDMI)
acpiprt2 at acpi0: bus 1 (PBR4)
acpiprt3 at acpi0: bus 2 (PBR5)
acpiprt4 at acpi0: bus 3 (PBR6)
acpiprt5 at acpi0: bus -1 (PBR7)
acpiprt6 at acpi0: bus 5 (PE20)
acpiprt7 at acpi0: bus -1 (PE21)
acpiprt8 at acpi0: bus -1 (PE22)
acpiprt9 at acpi0: bus -1 (PE23)
acpiprt10 at acpi0: bus 0 (PCI0)
acpiprt11 at acpi0: bus 4 (PIBR)
acpicpu0 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS
acpicpu1 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
cpu0: 1000 MHz: speeds: 1000 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00
ppb0 at pci0 dev 4 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E
(0x2c00), msi, address 00:0d:b9:3e:84:9c
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
ppb1 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
re1 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E
(0x2c00), msi, address 00:0d:b9:3e:84:9d
rgephy1 at re1 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
ppb2 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci3 at ppb2 bus 3
re2 at pci3 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E
(0x2c00), msi, address 00:0d:b9:3e:84:9e
rgephy2 at re2 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x40: apic 2 int
19, AHCI 1.2
scsibus1 at ahci0: 32 targets
ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int
18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "ATI EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 2 int
18, version 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "ATI EHCI root hub" rev 2.00/1.00 addr 1
piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x42: polling
iic0 at piixpm0
pcib0 at pci0 dev 20 function 3 "ATI SB700 ISA" rev 0x40
ppb3 at pci0 dev 20 function 4 "ATI SB600 PCI" rev 0x40
pci4 at ppb3 bus 4
ohci2 at pci0 dev 20 function 5 "ATI SB700 USB" rev 0x00: apic 2 int
18, version 1.0, legacy support
ppb4 at pci0 dev 21 function 0 "ATI SB800 PCIE" 

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[YASUOKA Masahiko]

On Wed, 11 Nov 2015 15:33:06 -0500
"Joe Gidi"  wrote:
> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in one
> of my systems and tried to boot the November 11th amd64 miniroot58.fs
> image to test UEFI booting. I get to the bootloader, but it appears to
> fail while loading the kernel and goes into a reboot loop. Here's
> everything I see on screen before it reboots:
> 
> probing: pc0 mem[640K 2984M 4M 48K 5103M]
> disk: hd0 hd1 hd2*
>>> OpenBSD/amd64 EFIBOOT 3.29
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238

I'd like to figure out where the efiboot is stopping.  Can you replace
the BOOTX64.EFI in the miniroot58.fs and check the output?

compiled version:

  http://yasuoka.net/~yasuoka/BOOTX64.EFI

diff:

Index: efiboot/efiboot.c
===
RCS file: /disk/cvs/openbsd/src/sys/arch/amd64/stand/efiboot/efiboot.c,v
retrieving revision 1.9
diff -u -p -r1.9 efiboot.c
--- efiboot/efiboot.c   8 Nov 2015 00:17:29 -   1.9
+++ efiboot/efiboot.c   26 Nov 2015 09:15:17 -
@@ -569,7 +569,7 @@ efi_makebootargs(void)
 void
 _rtt(void)
 {
-#ifdef EFI_DEBUG
+#if defined(EFI_DEBUG) || 1
printf("Hit any key to reboot\n");
efi_cons_getc(0);
 #endif
Index: libsa/exec_i386.c
===
RCS file: /disk/cvs/openbsd/src/sys/arch/amd64/stand/libsa/exec_i386.c,v
retrieving revision 1.15
diff -u -p -r1.15 exec_i386.c
--- libsa/exec_i386.c   5 Oct 2015 22:59:39 -   1.15
+++ libsa/exec_i386.c   26 Nov 2015 09:15:17 -
@@ -123,6 +123,7 @@ run_loadfile(u_long *marks, int howto)
 * This code may be used both for 64bit and 32bit.  Make sure the
 * bootarg is 32bit always on even on amd64.
 */
+   printf("%s() calling makebootargs32()\n", __func__);
 #ifdef __amd64__
makebootargs32(av, );
 #else
@@ -134,6 +135,10 @@ run_loadfile(u_long *marks, int howto)
printf("entry point at 0x%lx [%x, %x, %x, %x]\n", entry,
((int *)entry)[0], ((int *)entry)[1],
((int *)entry)[2], ((int *)entry)[3]);
+
+   printf("Hit any key to continue\n");
+   efi_cons_getc(0);
+
 #ifndef EFIBOOT
/* stack and the gung is ok at this point, so, no need for asm setup */
(*(startfuncp)entry)(howto, bootdev, BOOTARG_APIVER, marks[MARK_END],

random.seed question

[Marko Cupać]

Hi,

I can't seem to find an explanation what is the purpose of random.seed
from sysadmin's point of view. Any good soul out there to point me in
the right direction?

The reason why I am asking is the fact that I am preparing pcengines
apu box which needs to be read-only because of reduced sdcard wear but
also because it is going to be placed in remote environment with
frequent power outages (daily manual fscks expected if / is rw).

I am achieving this by putting ro record in fstab for (the only) /
partition and moving /dev, /var and /tmp to mfs and tmpfs mounts.

I am concerned about shutdown message about inability to dd random.seed
because of read-only file system. What would be the implications of not
writing it on shutdown?

Also does the following modification to rc look reasonable (not a
patch file, I've just put "+" sign to make change more visible)?

random_seed()
{
+   # make / read-write in order to make next lines possible
+   /sbin/mount -uw /
# push the old seed into the kernel
dd if=/var/db/host.random of=/dev/random bs=65536 count=1
status=none chmod 600 /var/db/host.random
# ... and create a future seed
dd if=/dev/random of=/var/db/host.random bs=65536 count=1
status=none # and create a seed file for the boot-loader
dd if=/dev/random of=/etc/random.seed bs=512 count=1 status=none
chmod 600 /etc/random.seed
+   # make / read-only again
+   /sbin/mount -ur /
}

Thank you in advance.
--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: OpenBSD as a pentester PC?

[Bryan Everly]

I have been slowly trying to add such tools to the ports tree. If you
can give me a list of the ones you are interested in from most
important to least I will see what I can do.

Thanks,
Bryan

> On Nov 26, 2015, at 4:50 AM, Mohammad BadieZadegan  
> wrote:
>
> Hi every OpenBSD user,
> I have OpenBSD on my Notebook since 2 years ago and I don't want to switch
> other OS for my business pentest project.
> I need some pentest tools for my project like metasploit, fuzzers, ..etc
> but I could not find them on OpenBSD package list
> !
> By default does OpenBSD support metasploit installing (or any attack tools)
> or defer them for security purpose?
> I want to have one OS on my note book for all purpose(business+home).
> Is that I must switch to other OS? (That I don't like at all!)
> Regards.
>
> --
> [image: ( openbsd.pro  933k.ir )] 

can't boot from USB3.0 flash memory

[freeunix]

I have USB3.0 flash memory.(SANDISK)
"OpenBSD 5.8 amd64/i386 on USB3.0"

1.USB3.0 flash memory connect to USB2.0/1.0
boot: It's fine.
2.USB3.0 flash memory connect to USB3.0
boot: can't boot!

anyone don't need boot from USB3.0?

Re: OpenBSD as a pentester PC?

[Michael McConville]

Mohammad BadieZadegan wrote:
> I have OpenBSD on my Notebook since 2 years ago and I don't want to
> switch other OS for my business pentest project. I need some pentest
> tools for my project like metasploit, fuzzers, ..etc but I could not
> find them on OpenBSD package list
> ! By default
> does OpenBSD support metasploit installing (or any attack tools) or
> defer them for security purpose? I want to have one OS on my note book
> for all purpose(business+home). Is that I must switch to other OS?
> (That I don't like at all!)

Here's a recent thread on this topic, started by Bryan (who already
replied here):

https://marc.info/?t=143776937300012=1=2

Re: random.seed question

[Theo de Raadt]

> I am concerned about shutdown message about inability to dd random.seed
> because of read-only file system. What would be the implications of not
> writing it on shutdown?

Huge loss of security in cryptographic situations.  This explains
the mechanism it serves:

http://www.openbsd.org/papers/hackfest2014-arc4random/index.html

Re: random.seed question

[Paul de Weerd]

On Thu, Nov 26, 2015 at 01:30:51PM +0100, Marko Cupa?? wrote:
| Hi,
| 
| I can't seem to find an explanation what is the purpose of random.seed
| from sysadmin's point of view. Any good soul out there to point me in
| the right direction?

Carry entropy from the previous run to the next.  This data is read
*before* the kernel is booted, so the kernel can use better entropy
for some of its inner workings.

For a hint why you want proper entropy at the earliest start of the
system, look at this recent story: 

https://www.raspberrypi.org/forums/viewtopic.php?f=66=126892

| The reason why I am asking is the fact that I am preparing pcengines
| apu box which needs to be read-only because of reduced sdcard wear but
| also because it is going to be placed in remote environment with
| frequent power outages (daily manual fscks expected if / is rw).
| 
| I am achieving this by putting ro record in fstab for (the only) /
| partition and moving /dev, /var and /tmp to mfs and tmpfs mounts.
| 
| I am concerned about shutdown message about inability to dd random.seed
| because of read-only file system. What would be the implications of not
| writing it on shutdown?

You'd have the same entropy data as the previous run which may make
certain attacks more feasible.

| Also does the following modification to rc look reasonable (not a
| patch file, I've just put "+" sign to make change more visible)?
| 
| random_seed()
| {
| +   # make / read-write in order to make next lines possible
| +   /sbin/mount -uw /
| # push the old seed into the kernel
| dd if=/var/db/host.random of=/dev/random bs=65536 count=1
| status=none chmod 600 /var/db/host.random
| # ... and create a future seed
| dd if=/dev/random of=/var/db/host.random bs=65536 count=1
| status=none # and create a seed file for the boot-loader
| dd if=/dev/random of=/etc/random.seed bs=512 count=1 status=none
| chmod 600 /etc/random.seed
| +   # make / read-only again
| +   /sbin/mount -ur /
| }

That's an option, but you'd need to carry that along yourself.  You're
already in unsupported territory (with a ro /) but for your own sanity
I'd recommend trying to keep such changes to a minimum: this will be
overwritten when you upgrade and it becomes a maintenance burden.

I'd recommend sticking something in rc.local or creating an @reboot
cronjob that updates the /etc/random.seed.  May not be ideal (the
entropy may not be very strong - I don't know if there is much
difference between just after boot or just before shutdown in this
regard), but at least it's easier to carry from release to release.

Paul 'WEiRD' de Weerd

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/ 

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Joe Gidi]

On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
> On Wed, 11 Nov 2015 15:33:06 -0500
> "Joe Gidi"  wrote:
>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in
>> one
>> of my systems and tried to boot the November 11th amd64 miniroot58.fs
>> image to test UEFI booting. I get to the bootloader, but it appears to
>> fail while loading the kernel and goes into a reboot loop. Here's
>> everything I see on screen before it reboots:
>>
>> probing: pc0 mem[640K 2984M 4M 48K 5103M]
>> disk: hd0 hd1 hd2*
 OpenBSD/amd64 EFIBOOT 3.29
>> boot>
>> cannot open hd0a:/etc/random.seed: No such file or directory
>> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238
>
> I'd like to figure out where the efiboot is stopping.  Can you replace
> the BOOTX64.EFI in the miniroot58.fs and check the output?

Sure, I now get these two lines after the 'booting' line:

GOP setmode failed(7)
Hit any key to reboot

Please let me know if I can do any further testing, and thank you for
looking into this.

Thanks,

--
Joe Gidi
j...@entropicblur.com

"You cannot buy skill." -- Ross Seyfried

Re: output of pkg_check(1)

[Marc Espie]

On Thu, Nov 26, 2015 at 10:47:40AM +0100, Jan Stary wrote:
> The output of "pkg_check -x -v -D nosig"
> (full log bellow) on current/amd64 confuses me.
> 
> Firstly,
> 
>   System libs NOT in locate dbs:
>   /usr/X11R6/lib/libEGL.so.0.0
>   /usr/X11R6/lib/libGL.so.15.0
>   /usr/X11R6/lib/libglapi.so.0.0
> 
> but
> 
> $ locate /usr/X11R6/lib/libEGL.so.0.0
> /usr/X11R6/lib/libEGL.so.0.0
> $ locate /usr/X11R6/lib/libGL.so.15.0
> /usr/X11R6/lib/libGL.so.15.0
> $ locate /usr/X11R6/lib/libglapi.so.0.0
> /usr/X11R6/lib/libglapi.so.0.0
> 
> and the files themselves exist.
> In fact, /var/db/locate.database is an hour old.
> 
> Does "not in locate dbs" mean something else?

Yes.

It means the locate dbs that match the installed system (go look into 
/usr/lib/locate and /usr/X11R6/lib/locate)

> Does pkg_check use the locate db instead of checking the files themselves?
> 
> Why does pkg_check care about /usr/X11R6/lib,
> and why exactly these three? Is it because some
> installed package mentioned them as a dependency?
> 
> 
> Next, there is a section of files "not found":
> 
>   Not found:
>   /boot
>   /bsd
>   /bsd.rd
>   /bsd.sp
>   /dload
>   ...
> 
> None of these belongs to an installed package, obviously,
You are correct.

Got a point ?

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[YASUOKA Masahiko]

Hi,

On Thu, 26 Nov 2015 09:57:12 -0500
"Joe Gidi"  wrote:
> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
>> On Wed, 11 Nov 2015 15:33:06 -0500
>> "Joe Gidi"  wrote:
>>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in
>>> one
>>> of my systems and tried to boot the November 11th amd64 miniroot58.fs
>>> image to test UEFI booting. I get to the bootloader, but it appears to
>>> fail while loading the kernel and goes into a reboot loop. Here's
>>> everything I see on screen before it reboots:
>>>
>>> probing: pc0 mem[640K 2984M 4M 48K 5103M]
>>> disk: hd0 hd1 hd2*
> OpenBSD/amd64 EFIBOOT 3.29
>>> boot>
>>> cannot open hd0a:/etc/random.seed: No such file or directory
>>> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238
>>
>> I'd like to figure out where the efiboot is stopping.  Can you replace
>> the BOOTX64.EFI in the miniroot58.fs and check the output?
> 
> Sure, I now get these two lines after the 'booting' line:
> 
> GOP setmode failed(7)
> Hit any key to reboot

The bootloader changs the video resolution before start the kernel.
It seems to fail.  "GOP", Graphic Output Protocol, returns an error.
7 means EFI_DEVICE_ERROR.

> Please let me know if I can do any further testing, and thank you for
> looking into this.

Can you provide the result of "machine video" and try to change the
video mode to the best and some others.


And also please try the diff below.

compiled:

  http://yasuoka.net/~yasuoka/BOOTX64.EFI (updated)

diff:

Index: efiboot/efiboot.c
===
RCS file: /cvs/src/sys/arch/amd64/stand/efiboot/efiboot.c,v
retrieving revision 1.9
diff -u -p -r1.9 efiboot.c
--- efiboot/efiboot.c   8 Nov 2015 00:17:29 -   1.9
+++ efiboot/efiboot.c   26 Nov 2015 15:57:56 -
@@ -528,8 +528,10 @@ efi_makebootargs(void)
}
if (bestmode >= 0) {
status = EFI_CALL(gop->SetMode, gop, bestmode);
+#if 0
if (EFI_ERROR(status))
panic("GOP setmode failed(%d)", status);
+#endif
}
 
gopi = gop->Mode->Info;
@@ -569,7 +571,7 @@ efi_makebootargs(void)
 void
 _rtt(void)
 {
-#ifdef EFI_DEBUG
+#if defined(EFI_DEBUG) || 1
printf("Hit any key to reboot\n");
efi_cons_getc(0);
 #endif
Index: libsa/exec_i386.c
===
RCS file: /cvs/src/sys/arch/amd64/stand/libsa/exec_i386.c,v
retrieving revision 1.16
diff -u -p -r1.16 exec_i386.c
--- libsa/exec_i386.c   26 Nov 2015 10:52:40 -  1.16
+++ libsa/exec_i386.c   26 Nov 2015 15:57:56 -
@@ -123,6 +123,7 @@ run_loadfile(u_long *marks, int howto)
 * This code may be used both for 64bit and 32bit.  Make sure the
 * bootarg is 32bit always on even on amd64.
 */
+   printf("%s() calling makebootargs32()\n", __func__);
 #ifdef __amd64__
makebootargs32(av, );
 #else
@@ -134,6 +135,10 @@ run_loadfile(u_long *marks, int howto)
printf("entry point at 0x%lx [%x, %x, %x, %x]\n", entry,
((int *)entry)[0], ((int *)entry)[1],
((int *)entry)[2], ((int *)entry)[3]);
+
+   printf("Hit any key to continue\n");
+   efi_cons_getc(0);
+
 #ifndef EFIBOOT
/* stack and the gung is ok at this point, so, no need for asm setup */
(*(startfuncp)entry)(howto, bootdev, BOOTARG_APIVER, marks[MARK_END],

vmmctl and vmd problem

[freeunix]

/etc/rc.conf.local:
vmd_flags=""

/etc/vmm.conf
vm "vm1.example.com" {
memory 512M
interfaces 1
disk "/dev/sd0a" #usb flash memory
kernel "/bsd"
}

check vmm devices:
ls /dev/vmm*
/dev/vmm

dmesg|grep vmm
vmm0 at mainbus0: initialized
vmm0: 4 VMX capable CPU(s), 4 are EPT capable

cd /dev
./MAKEDEV vmm0
vmm0: unknown device

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

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Joe Gidi]

On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
> Hi,
>
> On Thu, 26 Nov 2015 09:57:12 -0500
> "Joe Gidi"  wrote:
>> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
>>> On Wed, 11 Nov 2015 15:33:06 -0500
>>> "Joe Gidi"  wrote:
 I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in
 one
 of my systems and tried to boot the November 11th amd64 miniroot58.fs
 image to test UEFI booting. I get to the bootloader, but it appears to
 fail while loading the kernel and goes into a reboot loop. Here's
 everything I see on screen before it reboots:

 probing: pc0 mem[640K 2984M 4M 48K 5103M]
 disk: hd0 hd1 hd2*
>> OpenBSD/amd64 EFIBOOT 3.29
 boot>
 cannot open hd0a:/etc/random.seed: No such file or directory
 booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238
>>>
>>> I'd like to figure out where the efiboot is stopping.  Can you replace
>>> the BOOTX64.EFI in the miniroot58.fs and check the output?
>>
>> Sure, I now get these two lines after the 'booting' line:
>>
>> GOP setmode failed(7)
>> Hit any key to reboot
>
> The bootloader changs the video resolution before start the kernel.
> It seems to fail.  "GOP", Graphic Output Protocol, returns an error.
> 7 means EFI_DEVICE_ERROR.
>
>> Please let me know if I can do any further testing, and thank you for
>> looking into this.
>
> Can you provide the result of "machine video" and try to change the
> video mode to the best and some others.
>
>
> And also please try the diff below.

This appears to fix it. I did not have to change the video mode. Output
from the bootloader:

boot> machine video
Mode 0: 80 x 25
Mode 1: 80 x 50
Mode 2: 100 x 31

Current Mode = 2
boot>
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd0a:/bsd: 3263848+1395072+2409472+0+569344=74a238
run_loadfile() calling makebootargs32()
entry point at 0xf000160 [7205c766, 3404, 24448b12, 680a304]
Hit any key to continue

After hitting any key, the kernel loads successfully and takes me into the
installer.

Thanks!

--
Joe Gidi
j...@entropicblur.com

"You cannot buy skill." -- Ross Seyfried

Re: relayd ssl interception and certificate subject

[Uwe Werler]

Thank You very much for the explanation Stuart!

I'll check this.

On 25. Nov  8:02:17, Stuart Henderson wrote:
> On 2015-11-24, Uwe Werler  wrote:
> > Hello,
> >
> > I'm just testing ssl interception and noticed the following problem. 
> > Sometimes the Subject/Subject Alternative Name of the cert is altered with 
> > a different name than the one the original cert has:
> 
> When relayd connects to the server to find out what names to use in
> the subject/SAN, it doesn't send the requested hostname (SNI) in
> the ClientHello, so it only has the information from the server's
> "default" certificate to include in the new generated certificate.
> 
> You can see this for yourself with openssl s_client -connect hostname:443
> compared with openssl s_client -connect hostname:443 -servername hostname.
> 

-- 

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[YASUOKA Masahiko]

On Thu, 26 Nov 2015 11:10:33 -0500
"Joe Gidi"  wrote:
> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
>> On Thu, 26 Nov 2015 09:57:12 -0500
>> "Joe Gidi"  wrote:
>>> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
 On Wed, 11 Nov 2015 15:33:06 -0500
 "Joe Gidi"  wrote:
> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in
> one
> of my systems and tried to boot the November 11th amd64 miniroot58.fs
> image to test UEFI booting. I get to the bootloader, but it appears to
> fail while loading the kernel and goes into a reboot loop. Here's
> everything I see on screen before it reboots:
>
> probing: pc0 mem[640K 2984M 4M 48K 5103M]
> disk: hd0 hd1 hd2*
>>> OpenBSD/amd64 EFIBOOT 3.29
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238

 I'd like to figure out where the efiboot is stopping.  Can you replace
 the BOOTX64.EFI in the miniroot58.fs and check the output?
>>>
>>> Sure, I now get these two lines after the 'booting' line:
>>>
>>> GOP setmode failed(7)
>>> Hit any key to reboot
>>
>> The bootloader changs the video resolution before start the kernel.
>> It seems to fail.  "GOP", Graphic Output Protocol, returns an error.
>> 7 means EFI_DEVICE_ERROR.
>>
>>> Please let me know if I can do any further testing, and thank you for
>>> looking into this.
>>
>> Can you provide the result of "machine video" and try to change the
>> video mode to the best and some others.
>>
>>
>> And also please try the diff below.
> 
> This appears to fix it. I did not have to change the video mode. Output
> from the bootloader:

UEFI seems to have refused changing the video mode since it
isn't to change.

Can you try this again?  (I'd like to verify whether the assumption
above is correct).

compiled:

  http://yasuoka.net/~yasuoka/BOOTX64.EFI (updated)

diff:

Index: efiboot/efiboot.c
===
RCS file: /cvs/src/sys/arch/amd64/stand/efiboot/efiboot.c,v
retrieving revision 1.9
diff -u -p -r1.9 efiboot.c
--- efiboot/efiboot.c   8 Nov 2015 00:17:29 -   1.9
+++ efiboot/efiboot.c   26 Nov 2015 16:21:23 -
@@ -526,10 +526,10 @@ efi_makebootargs(void)
bestsiz = gopsiz;
}
}
-   if (bestmode >= 0) {
+   if (bestmode >= 0 && conout->Mode->Mode != bestmode) {
status = EFI_CALL(gop->SetMode, gop, bestmode);
if (EFI_ERROR(status))
-   panic("GOP setmode failed(%d)", status);
+   printf("GOP setmode failed(%d)\n", status);
}
 
gopi = gop->Mode->Info;

--yasuoka

Multiple interfaces match the same subnet

[bluesun08]

Hi,

my setup:

*/etc/hostname.re0*
up

*/etc/hostname.vlan100*
inet 192.168.100.184 255.255.255.0 192.168.100.255 vlandev re0 description
VLAN1-Net1

*/etc/hostname.vlan178*
inet 192.168.178.184 255.255.255.0 192.168.178.255 vlandev re0 description
VLAN7-Net2

*/etc/hostname.athn0*
inet 192.168.100.185 255.255.255.0
up
media autoselect mode 11g
mediaopt hostap
nwid openbsd2
chan 6
wpakey 

*/etc/hostname.bridge0*
add vlan100
add athn0
up

*/etc/dhcpd.conf*
shared-network LAN {
  option  domain-name "universum.local";
  option  domain-name-servers 192.168.100.184;
  option  time-servers 192.168.100.184;

  subnet 192.168.100.0 netmask 255.255.255.0 {
option routers 192.168.100.184;
range 192.168.100.32 192.168.100.227;
  }
}

*/etc/rc.conf.local*
dhcpd_flags="vlan100 athn0"

Now in "*/var/log/messages*" i get the error messages:
Nov 27 01:31:27 openbsd dhcpd[31924]: Multiple interfaces match the same
subnet: athn0 vlan100
Nov 27 01:31:27 openbsd dhcpd[31924]: Multiple interfaces match the same
shared network: athn0 vlan100

Best regards

Alex









--
View this message in context: 
http://openbsd-archive.7691.n7.nabble.com/Multiple-interfaces-match-the-same-subnet-tp283819.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[Joe Gidi]

On Thu, November 26, 2015 11:27 am, YASUOKA Masahiko wrote:
> On Thu, 26 Nov 2015 11:10:33 -0500
> "Joe Gidi"  wrote:
>> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
>>> On Thu, 26 Nov 2015 09:57:12 -0500
>>> "Joe Gidi"  wrote:
 On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
> On Wed, 11 Nov 2015 15:33:06 -0500
> "Joe Gidi"  wrote:
>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard
>> in
>> one
>> of my systems and tried to boot the November 11th amd64
>> miniroot58.fs
>> image to test UEFI booting. I get to the bootloader, but it appears
>> to
>> fail while loading the kernel and goes into a reboot loop. Here's
>> everything I see on screen before it reboots:
>>
>> probing: pc0 mem[640K 2984M 4M 48K 5103M]
>> disk: hd0 hd1 hd2*
 OpenBSD/amd64 EFIBOOT 3.29
>> boot>
>> cannot open hd0a:/etc/random.seed: No such file or directory
>> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238
>
> I'd like to figure out where the efiboot is stopping.  Can you
> replace
> the BOOTX64.EFI in the miniroot58.fs and check the output?

 Sure, I now get these two lines after the 'booting' line:

 GOP setmode failed(7)
 Hit any key to reboot
>>>
>>> The bootloader changs the video resolution before start the kernel.
>>> It seems to fail.  "GOP", Graphic Output Protocol, returns an error.
>>> 7 means EFI_DEVICE_ERROR.
>>>
 Please let me know if I can do any further testing, and thank you for
 looking into this.
>>>
>>> Can you provide the result of "machine video" and try to change the
>>> video mode to the best and some others.
>>>
>>>
>>> And also please try the diff below.
>>
>> This appears to fix it. I did not have to change the video mode. Output
>> from the bootloader:
>
> UEFI seems to have refused changing the video mode since it
> isn't to change.
>
> Can you try this again?  (I'd like to verify whether the assumption
> above is correct).

Is there something specific you want me to test?

With the latest bootloader you provided, the 'machine video' output is
still the same:

boot> machine video
Mode 0: 80 x 25
Mode 1: 80 x 50
Mode 2: 100 x 31

Current Mode = 2

I am able to boot successfully from miniroot.fs and run through a UEFI
install as described by jasper@ here:
https://blog.jasper.la/openbsd-uefi-bootloader-howto/

The only thing I did differently from his blog post was to use the
bootloader you provided, rather than copying in the one from
/mnt/usr/mdec.

The newly installed system boots successfully, but then it seems to fail
to initialize video properly at the end of the boot process. My monitor
goes into an endless cycle of trying to sync up. I can ssh in and see this
in /var/log/messages:

Nov 26 11:45:55 opteron /bsd: root on sd0a (ef051b8fc18f2fbe.a) swap on
sd0b dump on sd0b
Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
Nov 26 11:45:55 opteron /bsd: drm:pid0:evergreen_init *ERROR* disabling
GPU acceleration
Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
0x802922c0 unpin not necessary
Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
0x802922c0 unpin not necessary
Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
Nov 26 11:45:55 opteron /bsd: error: [drm:pid0:radeonfb_create] *ERROR*
failed to create fbcon object -12
Nov 26 11:45:55 opteron ntpd[27846]: /var/db/ntpd.drift is empty
Nov 26 11:45:55 opteron savecore: no core dump

My video card is:
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00
drm0 at radeondrm0
radeondrm0: msi

And the radeondrm-firmware-20150927 package is installed.

Thanks again for all your help.

--
Joe Gidi
j...@entropicblur.com

"You cannot buy skill." -- Ross Seyfried

Re: can't boot from USB3.0 flash memory

[Nick Holland]

On 11/26/15 08:25, freeu...@ruggedinbox.com wrote:
> I have USB3.0 flash memory.(SANDISK)
> "OpenBSD 5.8 amd64/i386 on USB3.0"
> 
> 1.USB3.0 flash memory connect to USB2.0/1.0
> boot: It's fine.
> 2.USB3.0 flash memory connect to USB3.0
> boot: can't boot!
> 
> anyone don't need boot from USB3.0?

LOTS of details missing here, but if you are saying that under whatever
mysterious circumstance you can not get the USB3 device to boot it
doesn't try to boot at all, this is not an OpenBSD issue.

OpenBSD's boot process is dependent upon the system BIOS until the
kernel is loaded.  So, if there is no attempt to boot, you have a BIOS
issue.  I've certainly seen this.  The answer is a BIOS upgrade that
probably doesn't exist, because many manufacturers barely test this
feature.  Nothing OpenBSD can do to fix it if the HW won't grab and run
the boot code.

Nick.

Re: random.seed question

[Stuart Henderson]

On 2015-11-26, Paul de Weerd  wrote:
> On Thu, Nov 26, 2015 at 01:30:51PM +0100, Marko Cupa?? wrote:
>
>| The reason why I am asking is the fact that I am preparing pcengines
>| apu box which needs to be read-only because of reduced sdcard wear but
>| also because it is going to be placed in remote environment with
>| frequent power outages (daily manual fscks expected if / is rw).

The wear isn't usually a huge problem imho. The fscks probably are though.

>| Also does the following modification to rc look reasonable (not a
>| patch file, I've just put "+" sign to make change more visible)?
>| 
>| random_seed()
>| {
>| +   # make / read-write in order to make next lines possible
>| +   /sbin/mount -uw /
>| # push the old seed into the kernel
>| dd if=/var/db/host.random of=/dev/random bs=65536 count=1
>| status=none chmod 600 /var/db/host.random
>| # ... and create a future seed
>| dd if=/dev/random of=/var/db/host.random bs=65536 count=1
>| status=none # and create a seed file for the boot-loader
>| dd if=/dev/random of=/etc/random.seed bs=512 count=1 status=none
>| chmod 600 /etc/random.seed
>| +   # make / read-only again
>| +   /sbin/mount -ur /
>| }

If you're going that far, it may make more sense to dd it to/from a raw
partition saved just for the job, and not bother with a filesystem on
it.

> That's an option, but you'd need to carry that along yourself.  You're
> already in unsupported territory (with a ro /) but for your own sanity
> I'd recommend trying to keep such changes to a minimum: this will be
> overwritten when you upgrade and it becomes a maintenance burden.

That's needed anyway, even if you're just doing something as simple as
forcing fsck -y. And for this type of system you really do need something,
startup failure due to unclean shutdown is very common. So you're making
one change anyway...

> I'd recommend sticking something in rc.local or creating an @reboot
> cronjob that updates the /etc/random.seed.  May not be ideal (the
> entropy may not be very strong - I don't know if there is much
> difference between just after boot or just before shutdown in this
> regard), but at least it's easier to carry from release to release.

Yes, there will be much more at shutdown, as the entropy is fed from
many sources.

BTW it appears that neither the APU nor APU2 have RDRAND which might
otherwise mitigate this a bit.

Re: output of pkg_check(1)

[Jan Stary]

On Nov 26 16:45:12, es...@nerim.net wrote:
> >   Not found:
> > /boot
> > /bsd
> > /bsd.rd
> > /bsd.sp
> > /dload
> > ...
> > 
> > None of these belongs to an installed package, obviously,
> You are correct.
> Got a point ?

Why does pkg_check even consider them?

Re: random.seed question

[Paul Suh]

> On Thu, Nov 26, 2015 at 01:30:51PM +0100, Marko Cupa?? wrote:
>
> | The reason why I am asking is the fact that I am preparing pcengines
> | apu box which needs to be read-only because of reduced sdcard wear but
> | also because it is going to be placed in remote environment with
> | frequent power outages (daily manual fscks expected if / is rw).
> |
> | I am achieving this by putting ro record in fstab for (the only) /
> | partition and moving /dev, /var and /tmp to mfs and tmpfs mounts.
> |
> | I am concerned about shutdown message about inability to dd random.seed
> | because of read-only file system. What would be the implications of not
> | writing it on shutdown?

Marko,

Rather than rolling your own (unless you are masochistic or have a serious
hacking itch), it might be easier to use one of the existing flash read-only
projects:

http://nmedia.net/flashrd
https://github.com/bconway/resflash

Just a couple of suggestions.


--Paul

[demime 1.01d removed an attachment of type application/pkcs7-signature which 
had a name of smime.p7s]

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Thu, Nov 26, 2015 at 09:00:48AM +0100, Joerg Jung wrote:
> Can you send a dmesg for this Air7,2 please?

Here's my dmesg from today's snapshot for the MacBookAir7,2.

Bryan



OpenBSD 5.8-current (GENERIC.MP) #1667: Thu Nov 26 08:27:08 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
ff
real mem = 8469352448 (8077MB)
avail mem = 8208547840 (7828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8afad000 (32 entries)
bios0: vendor Apple Inc. version "MBA71.88Z.0166.B06.1506051511" date 06/05/2015
bios0: Apple Inc. MacBookAir7,2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT MCFG DMAR
acpi0: wakeup devices PEG0(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) 
ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(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) i7-5650U CPU @ 2.20GHz, 2100.32 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
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-5650U CPU @ 2.20GHz, 2100.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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,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-5650U CPU @ 2.20GHz, 2100.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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,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-5650U CPU @ 2.20GHz, 2100.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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 
oem "3545797981528608836"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD01
cpu0: Enhanced SpeedStep 2100 MHz: speeds: 2201, 2200, 2100, 1800, 1600, 1300, 
1100, 900, 700, 500 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 5G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 6000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1440x900
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)

Re: output of pkg_check(1)

[Jan Stary]

> On Nov 26 16:45:12, es...@nerim.net wrote:
> > Does "not in locate dbs" mean something else?

> Yes.

> It means the locate dbs that match the installed system (go look into 
> /usr/lib/locate and /usr/X11R6/lib/locate)

Index: pkg_check.8
===
RCS file: /cvs/src/usr.sbin/pkg_add/pkg_check.8,v
retrieving revision 1.6
diff -u -p -r1.6 pkg_check.8
--- pkg_check.8 11 Feb 2014 08:58:34 -  1.6
+++ pkg_check.8 26 Nov 2015 17:55:36 -
@@ -108,6 +108,12 @@ may turn on more verbose output.
 .It Fl x
 Disable progress meter.
 .El
+.Sh FILES
+.Bl -ohang -compact
+.It Pa /var/db/pkg/
+.It Pa /usr/lib/locate/
+.It Pa /usr/X11R6/lib/locate/
+.El
 .Sh SEE ALSO
 .Xr fsck 8
 .Sh AUTHORS

Roundrobin Trunking on 5.8

[Kevin Chadwick]

I have upgraded a system from 5.6 to 5.8 and found that whilst the
children of a trunk port show output in tcpdump, the trunk port itself
whilst looking ok in ifconfig gives no aggregated roundrobin output at
all. Any ideas why?

p.s. Has anyone else seen anything similar to the following, if not
then maybe odd MTU settings are to blame for this separate issue?

http://marc.info/?l=openbsd-bugs=144838623025733=2

-- 

KISSIS - Keep It Simple So It's Securable

Re: Roundrobin Trunking on 5.8

[Kevin Chadwick]

> I have upgraded a system from 5.6 to 5.8 and found that whilst the
> children of a trunk port show output in tcpdump, the trunk port itself
> whilst looking ok in ifconfig gives no aggregated roundrobin output at
> all. Any ideas why?

Sorry, it's not 5.8 but 5.8-current i386 most recent snapshot (for
the ace pledge!!).

-- 

KISSIS - Keep It Simple So It's Securable

Re: output of pkg_check(1)

[Jay Patel]

http://bsdguru.in/74/pkg_check-errors-openbsd-5-8

I hope this helps.

On Thursday, November 26, 2015, Jan Stary  wrote:
> The output of "pkg_check -x -v -D nosig"
> (full log bellow) on current/amd64 confuses me.
>
> Firstly,
>
>   System libs NOT in locate dbs:
> /usr/X11R6/lib/libEGL.so.0.0
> /usr/X11R6/lib/libGL.so.15.0
> /usr/X11R6/lib/libglapi.so.0.0
>
> but
>
> $ locate /usr/X11R6/lib/libEGL.so.0.0
> /usr/X11R6/lib/libEGL.so.0.0
> $ locate /usr/X11R6/lib/libGL.so.15.0
> /usr/X11R6/lib/libGL.so.15.0
> $ locate /usr/X11R6/lib/libglapi.so.0.0
> /usr/X11R6/lib/libglapi.so.0.0
>
> and the files themselves exist.
> In fact, /var/db/locate.database is an hour old.
>
> Does "not in locate dbs" mean something else?
> Does pkg_check use the locate db instead of checking the files themselves?
>
> Why does pkg_check care about /usr/X11R6/lib,
> and why exactly these three? Is it because some
> installed package mentioned them as a dependency?
>
>
> Next, there is a section of files "not found":
>
>   Not found:
> /boot
> /bsd
> /bsd.rd
> /bsd.sp
> /dload
> ...
>
> None of these belongs to an installed package, obviously,
> but why would pkg_check even consider them? Manpage says
>
>Other files
>   Checks that there are no other random objects under /usr/local.
>
> but this is not /usr/local. There is /var/spool etc
> - seems like the whole / is traversed.
>
>
> Lastly,
>
>   In dbus-1.10.4v0:x11/dbus,-main:
> /etc/machine-id
>   In libxml-2.9.2p3:textproc/libxml,-main:
> /var/db/xmlcatalog
>
> Yes, these exist, and presumably belong those packages.
> What about them?
>
> Jan
>
>
> full script(1):
>
> # pkg_check -x -v -D nosig
> System libs NOT in locate dbs:
> /usr/X11R6/lib/libEGL.so.0.0
> /usr/X11R6/lib/libGL.so.15.0
> /usr/X11R6/lib/libglapi.so.0.0
>
> Not found:
> /boot
> /bsd
> /bsd.rd
> /bsd.sp
> /dload
> /etc/X11/app-defaults/GV
> /etc/X11/app-defaults/Gnuplot
> /etc/X11/xdm/authdir
> /etc/examples/ftpchroot
> /etc/examples/hosts.lpd
> /etc/fonts/conf.d/10-autohint.conf
> /etc/fstab
> /etc/hostname.re0
> /etc/hosts
> /etc/iked/local.pub
> /etc/iked/private/local.key
> /etc/isakmpd/local.pub
> /etc/isakmpd/private/local.key
> /etc/man.conf
> /etc/mixerctl.conf
> /etc/mixerctl.conf.onboard
> /etc/mk.conf
> /etc/mygate
> /etc/myname
> /etc/pkg.conf
> /etc/random.seed
> /etc/rc.conf.local
> /etc/resolv.conf
> /etc/resolv.conf.tail
> /etc/ssh/ssh_host_dsa_key
> /etc/ssh/ssh_host_dsa_key.pub
> /etc/ssh/ssh_host_ecdsa_key
> /etc/ssh/ssh_host_ecdsa_key.pub
> /etc/ssh/ssh_host_ed25519_key
> /etc/ssh/ssh_host_ed25519_key.pub
> /etc/ssh/ssh_host_rsa_key
> /etc/ssh/ssh_host_rsa_key.pub
> /etc/usermgmt.conf
> /media
> /obsd
> /pflogd.core
> /root/.aucat_cookie
> /root/.config
> /root/.forward
> /root/.ssh
> /root/.viminfo
> /root/.vimrc
> /root/Mail
> /root/OLD
> /root/TODO
> /root/man.conf
> /root/manpages.BekKbaACeqGG
> /root/manpages.Rc8jp6G_lwXv
> /root/manpages.iZk17KSJKAbP
> /root/manpages.qAjqJw7JLGpZ
> /root/manpages.sCWRaNUv_HkX
> /root/manpages.wDzeT7NkP2jH
> /root/typescript
> /usr/X11R6/include/freetype2/config
> /usr/X11R6/include/freetype2/freetype.h
> /usr/X11R6/include/freetype2/ftadvanc.h
> /usr/X11R6/include/freetype2/ftbbox.h
> /usr/X11R6/include/freetype2/ftbdf.h
> /usr/X11R6/include/freetype2/ftbitmap.h
> /usr/X11R6/include/freetype2/ftbzip2.h
> /usr/X11R6/include/freetype2/ftcache.h
> /usr/X11R6/include/freetype2/ftcffdrv.h
> /usr/X11R6/include/freetype2/ftchapters.h
> /usr/X11R6/include/freetype2/ftcid.h
> /usr/X11R6/include/freetype2/fterrdef.h
> /usr/X11R6/include/freetype2/fterrors.h
> /usr/X11R6/include/freetype2/ftfntfmt.h
> /usr/X11R6/include/freetype2/ftgasp.h
> /usr/X11R6/include/freetype2/ftglyph.h
> /usr/X11R6/include/freetype2/ftgxval.h
> /usr/X11R6/include/freetype2/ftgzip.h
> /usr/X11R6/include/freetype2/ftimage.h
> /usr/X11R6/include/freetype2/ftincrem.h
> /usr/X11R6/include/freetype2/ftlcdfil.h
> /usr/X11R6/include/freetype2/ftlist.h
> /usr/X11R6/include/freetype2/ftlzw.h
> /usr/X11R6/include/freetype2/ftmac.h
> /usr/X11R6/include/freetype2/ftmm.h
> /usr/X11R6/include/freetype2/ftmodapi.h
> /usr/X11R6/include/freetype2/ftmoderr.h
> 

Re: Roundrobin Trunking on 5.8

[Michael McConville]

Kevin Chadwick wrote:
> > I have upgraded a system from 5.6 to 5.8 and found that whilst the
> > children of a trunk port show output in tcpdump, the trunk port itself
> > whilst looking ok in ifconfig gives no aggregated roundrobin output at
> > all. Any ideas why?
> 
> Sorry, it's not 5.8 but 5.8-current i386 most recent snapshot (for
> the ace pledge!!).

Obvious question, but: did you go 5.6 -> 5.8 or 5.6 -> 5.7 -> 5.8?

Re: Roundrobin Trunking on 5.8

[Kevin Chadwick]

> Obvious question, but: did you go 5.6 -> 5.8 or 5.6 -> 5.7 -> 5.8?

5.6 -> 5.8 but followed the upgrade guides for both and ran sysmerge
once?

for the emailed bug report for the separate issue I said upgraded but
it was a new install.

-- 

KISSIS - Keep It Simple So It's Securable

Re: UEFI boot-looping on Asus M5A97 LE R2.0 motherboard

[YASUOKA Masahiko]

On Thu, 26 Nov 2015 11:51:03 -0500
"Joe Gidi"  wrote:
> On Thu, November 26, 2015 11:27 am, YASUOKA Masahiko wrote:
>> On Thu, 26 Nov 2015 11:10:33 -0500
>> "Joe Gidi"  wrote:
>>> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
 On Thu, 26 Nov 2015 09:57:12 -0500
 "Joe Gidi"  wrote:
> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
>> On Wed, 11 Nov 2015 15:33:06 -0500
>> "Joe Gidi"  wrote:
>>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard
>>> in
>>> one
>>> of my systems and tried to boot the November 11th amd64
>>> miniroot58.fs
>>> image to test UEFI booting. I get to the bootloader, but it appears
>>> to
>>> fail while loading the kernel and goes into a reboot loop. Here's
>>> everything I see on screen before it reboots:
>>>
>>> probing: pc0 mem[640K 2984M 4M 48K 5103M]
>>> disk: hd0 hd1 hd2*
> OpenBSD/amd64 EFIBOOT 3.29
>>> boot>
>>> cannot open hd0a:/etc/random.seed: No such file or directory
>>> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238
>>
>> I'd like to figure out where the efiboot is stopping.  Can you
>> replace
>> the BOOTX64.EFI in the miniroot58.fs and check the output?
>
> Sure, I now get these two lines after the 'booting' line:
>
> GOP setmode failed(7)
> Hit any key to reboot

 The bootloader changs the video resolution before start the kernel.
 It seems to fail.  "GOP", Graphic Output Protocol, returns an error.
 7 means EFI_DEVICE_ERROR.

> Please let me know if I can do any further testing, and thank you for
> looking into this.

 Can you provide the result of "machine video" and try to change the
 video mode to the best and some others.


 And also please try the diff below.
>>>
>>> This appears to fix it. I did not have to change the video mode. Output
>>> from the bootloader:
>>
>> UEFI seems to have refused changing the video mode since it
>> isn't to change.
>>
>> Can you try this again?  (I'd like to verify whether the assumption
>> above is correct).
> 
> Is there something specific you want me to test?

I had wanted to know the latest one can boot successfuly.
Since I'd like to fix it on the tree.  Thanks for your reports.

> With the latest bootloader you provided, the 'machine video' output is
> still the same:
> 
> boot> machine video
> Mode 0: 80 x 25
> Mode 1: 80 x 50
> Mode 2: 100 x 31
> 
> Current Mode = 2
> 
> I am able to boot successfully from miniroot.fs and run through a UEFI
> install as described by jasper@ here:
> https://blog.jasper.la/openbsd-uefi-bootloader-howto/
> 
> The only thing I did differently from his blog post was to use the
> bootloader you provided, rather than copying in the one from
> /mnt/usr/mdec.
> 
> The newly installed system boots successfully, but then it seems to fail
> to initialize video properly at the end of the boot process. My monitor
> goes into an endless cycle of trying to sync up. I can ssh in and see this
> in /var/log/messages:
> 
> Nov 26 11:45:55 opteron /bsd: root on sd0a (ef051b8fc18f2fbe.a) swap on
> sd0b dump on sd0b
> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
> Nov 26 11:45:55 opteron /bsd: drm:pid0:evergreen_init *ERROR* disabling
> GPU acceleration
> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
> 0x802922c0 unpin not necessary
> Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING*
> 0x802922c0 unpin not necessary
> Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed
> Nov 26 11:45:55 opteron /bsd: error: [drm:pid0:radeonfb_create] *ERROR*
> failed to create fbcon object -12
> Nov 26 11:45:55 opteron ntpd[27846]: /var/db/ntpd.drift is empty
> Nov 26 11:45:55 opteron savecore: no core dump
> 
> My video card is:
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00
> drm0 at radeondrm0
> radeondrm0: msi
> 
> And the radeondrm-firmware-20150927 package is installed.
> 
> Thanks again for all your help.
> 
> --
> Joe Gidi
> j...@entropicblur.com
> 
> "You cannot buy skill." -- Ross Seyfried

Re: option DEBUG in sparc64 kernel

[Stuart Henderson]

On 2015-11-24, Fred  wrote:
> Hi Misc@
>
> I'm trying to build a debug kernel for sparc64 but keep getting the 
> following errors in iommu.c:

You wouldn't normally define DEBUG for everything, just for the
particular files/areas you're interested in (and in many cases they're
called "_DEBUG" rather than just "DEBUG").

Are you just after a kernel with debug symbols? If so, that's done with
makeoptions DEBUG="-g" in kernel config. Otherwise target the particular
area, it's usually simplest to edit the relevant source files.

If you are actually wanting to debug iommu, the DPRINTF format strings
will need fixing up, I expect they haven't been built this way since at
least the time_t/off_t changes.

> ../../../../arch/sparc64/dev/iommu.c:569: warning: format '%lx' expects 
> type 'long unsigned int', but argument 4 has type 'time_t'
> ../../../../arch/sparc64/dev/iommu.c:569: warning: format '%lx' expects 
> type 'long unsigned int', but argument 6 has type 'time_t'

%llx

> ../../../../arch/sparc64/dev/iommu.c: In function 'iommu_dvmamap_load_raw':
> ../../../../arch/sparc64/dev/iommu.c:1020: warning: format '%ld' expects 
> type 'long int', but argument 5 has type 'int'

%d

> ../../../../arch/sparc64/dev/iommu.c:1020: warning: format '%lx' expects 
> type 'long unsigned int', but argument 6 has type 'int'

%x

> expects type 'long long unsigned int', but argument 2 has type 'bus_addr_t'
> ../../../../arch/sparc64/dev/iommu.c:1352: warning: format '%llx' 

%lx

> expects type 'long long unsigned int', but argument 2 has type 'bus_size_t'
> ../../../../arch/sparc64/dev/iommu.c:1360: warning: format '%llx' 

%lx

etc.

Re: random.seed question

[Andy Bradford]

Thus said Paul de Weerd on Thu, 26 Nov 2015 15:54:11 +0100:

> I'd recommend trying  to keep such changes to a  minimum: this will be
> overwritten when you upgrade and it becomes a maintenance burden.

Do files  in /etc  no longer  undergo a round  of sysmerge  before being
written?

Thanks,

Andy
-- 
TAI64 timestamp: 400056575beb

Re: random.seed question

[Theo de Raadt]

> Thus said Paul de Weerd on Thu, 26 Nov 2015 15:54:11 +0100:
> 
> > I'd recommend trying  to keep such changes to a  minimum: this will be
> > overwritten when you upgrade and it becomes a maintenance burden.
> 
> Do files  in /etc  no longer  undergo a round  of sysmerge  before being
> written?

More are now part of the system.  /etc/rc is system, if you modify it,
you will lose your changes.

Re: Wireless PCI hardware

[Tati Chevron]

On Fri, Nov 27, 2015 at 12:08:37AM +0100, Alexander Salmin wrote:

I want OpenBSD in hostap mode with PCI or PCIe ath / athn driver.


Be aware that hostap mode is not particularly reliable, usable, or with
good peformance at the moment.


- TP-Link TL-WN851ND


Works on OpenBSD.

--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com