Re: Question about /etc/mail post 5.6 upgrade

2014-11-09 Thread Antoine Jacoutot
On Sat, Nov 08, 2014 at 10:43:52PM -0800, Eric Lalonde wrote:
> Hello,
> 
> I recently upgraded from 5.5 to 5.6. I was surprised to see that the
> various apparently sendmail-specific files in /etc/mail are not in the
> ‘Files to delete and move’ list in upgrade56.html, now that sendmail
> is no longer in base. I suspect that either there are other reasons to
> keep the contents of this directory as-is post 5.6 upgrade, or I
> missed a step in the upgrade guide. I’m new to OpenBSD, so clue sticks
> are welcome.

Sendmail is still here on 5.6. It's just not the default MTA anymore.
It got removed after 5.6 was tagged (i.e. was will become 5.7) and it will be 
part of the files to delete:
http://www.openbsd.org/faq/current.html#20140915

-- 
Antoine



5.6 Icmp6 checksum / pf

2014-11-09 Thread Bastien Durel
Hi,

I recently upgraded to 5.6, and got problems with icmpv6

I have a gif tunnel for IPv6:
[root@fremen root]# ifconfig gif0   


gif0: flags=8051 mtu 1280
description: Sixxs
priority: 0
groups: gif egress
tunnel: inet 78.194.94.73 -> 212.100.184.146
inet6 fe80::200:24ff:fecf:42ac%gif0 -> prefixlen 64 scopeid 0x10
inet6 2001:6f8:202:19c::2 -> 2001:6f8:202:19c::1 prefixlen 128

When I initiate a ping from this interface, it works as intended:

08:59:38.376107 2001:6f8:202:19c::2 > 2001:41d0:8:91a::1: icmp6: echo request 
(id:392e seq:0) [icmp6 cksum ok] (len 16, hlim 64)
08:59:38.410385 2001:41d0:8:91a::1 > 2001:6f8:202:19c::2: icmp6: echo reply 
(id:392e seq:0) [icmp6 cksum ok] (len 16, hlim 57)
08:59:39.389383 2001:6f8:202:19c::2 > 2001:41d0:8:91a::1: icmp6: echo request 
(id:392e seq:1) [icmp6 cksum ok] (len 16, hlim 64)
08:59:39.421397 2001:41d0:8:91a::1 > 2001:6f8:202:19c::2: icmp6: echo reply 
(id:392e seq:1) [icmp6 cksum ok] (len 16, hlim 57)

But when a ping from outside reached it, the echo reply is sent with a
bad (0) checksum, and the packet is dropped by te other side:

09:40:28.852102 2001:41d0:8:91a::1 > 2001:6f8:202:19c::2: icmp6: echo request 
(id:6c10 seq:1) [icmp6 cksum ok] (len 64, hlim 57)
09:40:28.852251 2001:6f8:202:19c::2 > 2001:41d0:8:91a::1: icmp6: echo reply 
(id:6c10 seq:1) [bad icmp6 cksum 0! -> 2d93] (len 64, hlim 64)
09:40:29.860327 2001:41d0:8:91a::1 > 2001:6f8:202:19c::2: icmp6: echo request 
(id:6c10 seq:2) [icmp6 cksum ok] (len 64, hlim 57)
09:40:29.860432 2001:6f8:202:19c::2 > 2001:41d0:8:91a::1: icmp6: echo reply 
(id:6c10 seq:2) [bad icmp6 cksum 0! -> 8a71] (len 64, hlim 64)

It works correctly with this pf rule disabled:
pass in on gif0 reply-to ( gif0 2001:6f8:202:19c::1 ) keep state

What's the correct way to handle correct return-path ?

Regards,

-- 
Bastien Durel



Re: CVS: cvs.openbsd.org: src

2014-11-09 Thread Sébastien Marie
On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> On 24.10.2014 00:33, Robert Peichaer wrote:
> 
> I'm following -current and decided to try autoinstall(8) from
> /auto_upgrade.conf when I moved to newer snapshot.
> I made a custom auto_upgrade.conf on my root [sd2a] partition but when I
> boot a newer bsd.rd,
> auto_upgrade.conf is not on the miniroot. I escaped to shell, mounted sd2a
> on /mnt and copied auto_upgrade.conf to miniroot.
> Then Autoupgrade completed as it should.
> The question is whether there are any easier steps to make auto_upgrade from
> local file, not by using dhcp/tftp/http?
> Thanks,
> Atanas

The auto_upgrade.conf is searched in the ramdisk partition (which was
into bsd.rd). As thevoid@ wrote, you could rebuild a new bsd.rd image to
include it.

Personnally, I extract the ramdisk image from bsd.rd, mount it, copy the
auto_upgrade.conf to it, and restore the ramdisk into bsd.rd.

Here the "pseudo-script" I use:

# build rdsetroot
( cd /usr/src/distrib/common && cc -o /tmp/rdsetroot elf32.c elf64.c 
elfrdsetroot.c )

# extract ramdisk from bsd.rd
/tmp/rdsetroot -x bsd.rd ramdisk.img

# mount ramdisk
vnconfig vnd0 ramdisk.img
mount /dev/vnd0a /mnt

# copy config file
cp auto_upgrade.conf /mnt/auto_upgrade.conf

# umount ramdisk
umount /dev/vnd0a
vnconfig -u vnd0

# put modified ramdisk in bsd.rd
/tmp/rdsetroot bsd.rd ramdisk.img

# cleanup
rm ramdisk.img

And now, you could boot your modified bsd.rd.
-- 
Sébastien Marie



Re: X220 Backlight Buttons stopped working in 5.6

2014-11-09 Thread Riccardo Mottola

Hi,

Henrik Friedrichsen wrote:

Okay, a suspend & resume cycle seems to have fixed it somehow.

if you check the archives, I think I rised the same issue with my 
ThinkPad T60. The annoyance is that you always need a suspend/resume 
cycle, after every boot.

It looks like the max value is "off".
Riccardo



Re: CVS: cvs.openbsd.org: src

2014-11-09 Thread thevoid
On Sun, 9 Nov 2014 10:09:49 +0100 =?utf-8?Q?S=C3=A9bastien?= Marie 
 wrote:
> On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> > On 24.10.2014 00:33, Robert Peichaer wrote:
> > 
> > I'm following -current and decided to try autoinstall(8) from
> > /auto_upgrade.conf when I moved to newer snapshot.
> > I made a custom auto_upgrade.conf on my root [sd2a] partition but when I
> > boot a newer bsd.rd,
> > auto_upgrade.conf is not on the miniroot. I escaped to shell, mounted sd2a
> > on /mnt and copied auto_upgrade.conf to miniroot.
> > Then Autoupgrade completed as it should.
> > The question is whether there are any easier steps to make auto_upgrade from
> > local file, not by using dhcp/tftp/http?
> > Thanks,
> > Atanas
> 
> The auto_upgrade.conf is searched in the ramdisk partition (which was
> into bsd.rd). As thevoid@ wrote, you could rebuild a new bsd.rd image to
> include it.
> 
> Personnally, I extract the ramdisk image from bsd.rd, mount it, copy the
> auto_upgrade.conf to it, and restore the ramdisk into bsd.rd.
> 
> Here the "pseudo-script" I use:
> 
> # build rdsetroot
> ( cd /usr/src/distrib/common && cc -o /tmp/rdsetroot elf32.c elf64.c 
> elfrdsetroot.c )
> 
> # extract ramdisk from bsd.rd
> /tmp/rdsetroot -x bsd.rd ramdisk.img
> 
> # mount ramdisk
> vnconfig vnd0 ramdisk.img
> mount /dev/vnd0a /mnt
> 
> # copy config file
> cp auto_upgrade.conf /mnt/auto_upgrade.conf
> 
> # umount ramdisk
> umount /dev/vnd0a
> vnconfig -u vnd0
> 
> # put modified ramdisk in bsd.rd
> /tmp/rdsetroot bsd.rd ramdisk.img
> 
> # cleanup
> rm ramdisk.img
> 
> And now, you could boot your modified bsd.rd.
> -- 
> Sébastien Marie
> 

i like this. for this particular purpose, this is definitely a better method.



Re: CVS: cvs.openbsd.org: src

2014-11-09 Thread Atanas Vladimirov

On 09.11.2014 12:59, thev...@openmailbox.org wrote:

On Sun, 9 Nov 2014 10:09:49 +0100 =?utf-8?Q?S=C3=A9bastien?= Marie
 wrote:

On Sat, Nov 08, 2014 at 10:57:41PM +0200, Atanas Vladimirov wrote:
> On 24.10.2014 00:33, Robert Peichaer wrote:
>
> I'm following -current and decided to try autoinstall(8) from
> /auto_upgrade.conf when I moved to newer snapshot.
> I made a custom auto_upgrade.conf on my root [sd2a] partition but when I
> boot a newer bsd.rd,
> auto_upgrade.conf is not on the miniroot. I escaped to shell, mounted sd2a
> on /mnt and copied auto_upgrade.conf to miniroot.
> Then Autoupgrade completed as it should.
> The question is whether there are any easier steps to make auto_upgrade from
> local file, not by using dhcp/tftp/http?
> Thanks,
> Atanas

The auto_upgrade.conf is searched in the ramdisk partition (which was
into bsd.rd). As thevoid@ wrote, you could rebuild a new bsd.rd image 
to

include it.

Personnally, I extract the ramdisk image from bsd.rd, mount it, copy 
the

auto_upgrade.conf to it, and restore the ramdisk into bsd.rd.

Here the "pseudo-script" I use:

# build rdsetroot
( cd /usr/src/distrib/common && cc -o /tmp/rdsetroot elf32.c elf64.c 
elfrdsetroot.c )


# extract ramdisk from bsd.rd
/tmp/rdsetroot -x bsd.rd ramdisk.img

# mount ramdisk
vnconfig vnd0 ramdisk.img
mount /dev/vnd0a /mnt

# copy config file
cp auto_upgrade.conf /mnt/auto_upgrade.conf

# umount ramdisk
umount /dev/vnd0a
vnconfig -u vnd0

# put modified ramdisk in bsd.rd
/tmp/rdsetroot bsd.rd ramdisk.img

# cleanup
rm ramdisk.img

And now, you could boot your modified bsd.rd.
--
Sébastien Marie



i like this. for this particular purpose, this is definitely a better 
method.


I like it too. Thank you both.



Re: ping6 to Link Local disturbed by pf set skip?

2014-11-09 Thread Pieter Verberne

On 2014-11-08 11:18, Pieter Verberne wrote:

On 2014-11-07 14:35, Pieter Verberne wrote:

My problem:

`ping6 fe80::200:24ff:fecd:7df8%pppoe0` with pf disabled is no 
problem.

ping6, with pf enabled and 'set skip on lo0' does not work very well:


I could reproduce this very easily with a clean -current installation.



This problem started in 5.1. 5.0 is working.

http://www.openbsd.org/51.html:

pf(4) improvements:

One-shot rule support for pf(4), for use with proxies via anchors.
NAT64 support in PF using the af-to keyword.
Much improved IPv6 fragment handling.
Various enhancements with ICMP and especially ICMPv6 states
Improved IPv6 Neighbor Discovery and Multicast Listener Discovery 
handling.
pfctl(8) now prints port numbers instead of service names by 
default.

Netflow v9 and ipfix support for pflow(4).
Many pfsync(4) fixes and improvements including jumbo frames and 
automatically requesting a bulk update after a physical interface comes 
online.




Re: Updating ports from CVS question

2014-11-09 Thread Stuart Henderson
On 2014-11-07, Steve Williams  wrote:
>
> Having the ports.tar.gz that corresponds to the snapshot you install is 
> nice because 2 months down the road you can compile/install something 
> that will work on your system even when there is no package available 
> that will work on your system.
>
> If you try to cvs up your ports to -current 2 months after installing a 
> snapshot, odds are that something won't compile. OpenBSD works FANTASTIC 
> as long as you keep things consistent. Follow base, -current, or 
> snapshots.  Don't try to mix and match and you should have smooth sailing.

You can always "cvs up -D 2014/10/01" or similar ... I don't think
I ever used ports.tar.gz. But then, if I'm running -current and packages
don't install, I usually take that as a cue to spend 10 minutes or so
updating the system and packages ;)



Ipsec Blackberry OS 10

2014-11-09 Thread Ionel Coman
Hello ,

I'm  trying to set up an ipsec connection from my Blackberry Z30  to
Openbsd 5.6.
I'm new to openbsd ipsec.
When setting up the connection I do see my requests go to the server,but the
vpn tunnel is
not established.
Any help would be greatly appreciated !

ikev2 "bb10" esp \
from 192.168.0.0/24 to any \
local em0 peer any \
ikesa enc aes-128 auth hmac-sha1 group modp1024 \
childsa enc aes-128 auth hmac-sha1 \
srcid IPV4 dstid IPV4 \
ikelifetime 86400 \
lifetime 10800 \
eap "mschap-v2" \
tag "$name-$id"

ikev2_recv: IKE_SA_INIT request from initiator 79.xxx.xxx.xxx:500 to
81.xxx.xxx.xxx:500 policy 'bb10' id 0, 400 bytes
ikev2_recv: ispi 0xe1625a1286b597d8 rspi 0x
ikev2_policy2id: srcid FQDN/IPV4 length 8
ikev2_pld_parse: header ispi 0xe1625a1286b597d8 rspi 0x
nextpayload SA version 0x20 exchange IKE_SA_INIT flags 0x08 msgid 0 length 400
response 0
ikev2_pld_payloads: payload SA nextpayload KE critical 0x00 length 112
ikev2_pld_sa: more 0 reserved 0 length 108 proposal #1 protoid IKE spisize 0
xforms 11 spi 0
ikev2_pld_xform: more 3 reserved 0 length 8 type DH id MODP_1024
ikev2_pld_xform: more 3 reserved 0 length 8 type DH id MODP_768
ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA1
ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_MD5
ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC
ikev2_pld_attr: attribute type KEY_LENGTH length 256 total 4
ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC
ikev2_pld_attr: attribute type KEY_LENGTH length 192 total 4
ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC
ikev2_pld_attr: attribute type KEY_LENGTH length 128 total 4
ikev2_pld_xform: more 3 reserved 0 length 8 type ENCR id 3DES
ikev2_pld_xform: more 3 reserved 0 length 8 type ENCR id DES
ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA1_96
ikev2_pld_xform: more 0 reserved 0 length 8 type INTEGR id HMAC_MD5_96
ikev2_pld_payloads: payload KE nextpayload NONCE critical 0x00 length 136
ikev2_pld_ke: dh group MODP_1024 reserved 0
ikev2_pld_payloads: payload NONCE nextpayload NOTIFY critical 0x00 length 68
ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28
ikev2_pld_notify: protoid IKE spisize 0 type NAT_DETECTION_SOURCE_IP
ikev2_nat_detection: peer source 0xe1625a1286b597d8 0x
79.xxx.xxx.xxx:500
ikev2_pld_notify: NAT_DETECTION_SOURCE_IP detected NAT, enabling UDP
encapsulation
ikev2_pld_payloads: payload NOTIFY nextpayload NONE critical 0x00 length 28
ikev2_pld_notify: protoid IKE spisize 0 type NAT_DETECTION_DESTINATION_IP
ikev2_nat_detection: peer destination 0xe1625a1286b597d8 0x
81.xxx.xxx.xxx:500
sa_state: INIT -> SA_INIT
ikev2_sa_negotiate: score 5
sa_stateok: SA_INIT flags 0x00, require 0x00
sa_stateflags: 0x00 -> 0x10 sa (required 0x00 )
ikev2_sa_keys: SKEYSEED with 20 bytes
ikev2_sa_keys: S with 112 bytes
ikev2_prfplus: T1 with 20 bytes
ikev2_prfplus: T2 with 20 bytes
ikev2_prfplus: T3 with 20 bytes
ikev2_prfplus: T4 with 20 bytes
ikev2_prfplus: T5 with 20 bytes
ikev2_prfplus: T6 with 20 bytes
ikev2_prfplus: T7 with 20 bytes
ikev2_prfplus: Tn with 140 bytes
ikev2_sa_keys: SK_d with 20 bytes
ikev2_sa_keys: SK_ai with 20 bytes
ikev2_sa_keys: SK_ar with 20 bytes
ikev2_sa_keys: SK_ei with 16 bytes
ikev2_sa_keys: SK_er with 16 bytes
ikev2_sa_keys: SK_pi with 20 bytes
ikev2_sa_keys: SK_pr with 20 bytes
ikev2_add_proposals: length 44
ikev2_next_payload: length 48 nextpayload KE
ikev2_next_payload: length 136 nextpayload NONCE
ikev2_next_payload: length 36 nextpayload NOTIFY
ikev2_nat_detection: local source 0xe1625a1286b597d8 0xb144236f4734436b
81.x.x.x:500
ikev2_next_payload: length 28 nextpayload NOTIFY
ikev2_nat_detection: local destination 0xe1625a1286b597d8 0xb144236f4734436b
79.x.x.x.:500
ikev2_next_payload: length 28 nextpayload CERTREQ
ikev2_add_certreq: type X509_CERT length 21
ikev2_next_payload: length 25 nextpayload NONE
ikev2_pld_parse: header ispi 0xe1625a1286b597d8 rspi 0xb144236f4734436b
nextpayload SA version 0x20 exchange IKE_SA_INIT flags 0x20 msgid 0 length 329
response 1
ikev2_pld_payloads: payload SA nextpayload KE critical 0x00 length 48
ikev2_pld_sa: more 0 reserved 0 length 44 proposal #1 protoid IKE spisize 0
xforms 4 spi 0
ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC
ikev2_pld_attr: attribute type KEY_LENGTH length 128 total 4
ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA1
ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA1_96
ikev2_pld_xform: more 0 reserved 0 length 8 type DH id MODP_1024
ikev2_pld_payloads: payload KE nextpayload NONCE critical 0x00 length 136
ikev2_pld_ke: dh group MODP_1024 reserved 0
ikev2_pld_payloads: payload NONCE nextpayload NOTIFY critical 0x00 length 36
ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28
ikev2_pld_no

Sun/Cassini Quad Gigabit Card Not Detected

2014-11-09 Thread Jeff
Hi,

I've installed OpenBSD 5.6 (i386) on a dual processor XEON box which
has a 4 port Sun (Sun# 501-6738-10) Gigabit NIC card.  dmesg doesn't
have any indication that the card is installed. Booting Linux shows
the card as Sun/Cassini which I believe should be handled by the "cas"
driver.

pcidump shows the following (I think that the NS Saturn is the NIC
card):

Domain /dev/pci0:
 0:0:0: Intel E7505 Host
 0:0:1: Intel E7505 Error Reporting
 0:1:0: Intel E7505 AGP
 0:2:0: Intel E7505 PCI
 0:2:1: Intel E7505 PCI
 0:30:0: Intel 82801BA Hub-to-PCI
 0:31:0: Intel 82801DB LPC
 0:31:1: Intel 82801DB IDE
 0:31:3: Intel 82801DB SMBus
 1:0:0: NVIDIA Riva TNT2
 2:28:0: Intel 82870P2 IOxAPIC
 2:29:0: Intel 82870P2 PCIX-PCIX
 2:30:0: Intel 82870P2 IOxAPIC
 2:31:0: Intel 82870P2 PCIX-PCIX
 3:1:0: Broadcom BCM5703X
 3:2:0: Intel unknown
 4:0:0: NS Saturn
 4:1:0: NS Saturn
 4:2:0: NS Saturn
 4:3:0: NS Saturn
 6:1:0: TI TSB43AB22 FireWire


Any ideas on how to get OpenBSD to recognise this card?

Thanks!
Jeff
Any ideas on how to get OpenBSD to recognise this card?

Thanks!
Jeff



Re: Sun/Cassini Quad Gigabit Card Not Detected

2014-11-09 Thread Jeff
Rafael,

Thanks for responding.  Here are the outputs that you
requested:

dmesg:

OpenBSD 5.6 (GENERIC.MP) #299: Fri Aug  8 00:10:33 MDT 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.67 GHz
cpu0: 
FPU,V86,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,CNXT-ID,xTPR,PERF
real mem  = 2146906112 (2047MB)
avail mem = 2099359744 (2002MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/26/06, BIOS32 rev. 0 @ 0xfb000, SMBIOS 
rev. 2.2 @ 0xf (57 entries)
bios0: vendor IBM version "-[OPE151A]-" date 09/26/2006
bios0: IBM -[6221LJU]-
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP ASF! APIC
acpi0: wakeup devices HUB0(S5) HUBA(S5) HUBB(S5) PS2M(S4) PS2K(S4) USB0(S1) 
USB1(S1) USB3(S1) MODM(S5) PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 6 (application processor)
cpu1: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.67 GHz
cpu1: 
FPU,V86,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,CNXT-ID,xTPR,PERF
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
ioapic1 at mainbus0: apid 5 pa 0xfec8, version 20, 24 pins
ioapic2 at mainbus0: apid 6 pa 0xfec80400, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (HUB0)
acpiprt2 at acpi0: bus 5 (HUBA)
acpiprt3 at acpi0: bus 3 (HUBB)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xa800 0xcc000/0x1800
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E7505 Host" rev 0x03
agp at pchb0 not configured
"Intel E7505 Error Reporting" rev 0x03 at pci0 dev 0 function 1 not configured
ppb0 at pci0 dev 1 function 0 "Intel E7505 AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA Riva TNT2" rev 0x15
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb1 at pci0 dev 2 function 0 "Intel E7505 PCI" rev 0x03
pci2 at ppb1 bus 2
"Intel 82870P2 IOxAPIC" rev 0x04 at pci2 dev 28 function 0 not configured
ppb2 at pci2 dev 29 function 0 "Intel 82870P2 PCIX-PCIX" rev 0x04
pci3 at ppb2 bus 3
bge0 at pci3 dev 1 function 0 "Broadcom BCM5703X" rev 0x02, BCM5702/5703 A2 
(0x1002): apic 6 int 0, address 00:0c:76:4e:5d:6e
brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
ppb3 at pci3 dev 2 function 0 vendor "Intel", unknown product 0x537c rev 0x07
pci4 at ppb3 bus 4
"NS Saturn" rev 0x30 at pci4 dev 0 function 0 not configured
"NS Saturn" rev 0x30 at pci4 dev 1 function 0 not configured
"NS Saturn" rev 0x30 at pci4 dev 2 function 0 not configured
"NS Saturn" rev 0x30 at pci4 dev 3 function 0 not configured
"Intel 82870P2 IOxAPIC" rev 0x04 at pci2 dev 30 function 0 not configured
ppb4 at pci2 dev 31 function 0 "Intel 82870P2 PCIX-PCIX" rev 0x04
pci5 at ppb4 bus 5
"Intel E7505 PCI" rev 0x03 at pci0 dev 2 function 1 not configured
ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x82
pci6 at ppb5 bus 6
"TI TSB43AB22 FireWire" rev 0x00 at pci6 dev 1 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x02: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide0: channel 1 disabled (no drives)
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x02: apic 4 int 17
iic0 at ichiic0
iic0: addr 0x22 01=01 02=02 03=03 04=04 05=05 06=06 07=07 08=08 09=09 0a=0a 
0b=0b 0c=0c 0d=0d 0e=0e 0f=0f 10=10 11=11 12=12 13=13 14=14 15=15 16=16 17=17 
18=18 19=19 1a=1a 1b=1b 1c=1c 1d=1d 1e=1e 1f=1f 20=20 21=21 22=22 23=23 24=24 
25=25 26=26 27=27 28=28 29=29 2a=2a 2b=2b 2c=2c 2d=2d 2e=2e 2f=2f 30=30 31=31 
32=32 33=33 34=34 35=35 36=36 37=37 38=38 39=39 3a=3a 3b=3b 3c=3c 3d=3d 3e=3e 
3f=3f 40=40 41=41 42=42 43=43 44=44 45=45 46=46 47=47 48=48 49=49 4a=4a 4b=4b 
4c=4c 4d=4d 4e=4e 4f=4f 50=50 51=51 52=52 53=53 54=54 55=55 56=56 57=57 58=58 
59=59 5a=5a 5b=5b 5c=5c 5d=5d 5e=5e 5f=5f 60=60 61=61 62=62 63=63 64=64 65=65 
66=66 67=67 68=68 69=69 6a=6a 6b=6b 6c=6c 6d=6d 6e=6e 6f=6f 70=70 71=71 72=72 
73=73 74=74 75=75 76=76 77=77 78=78 79=79 7a=7a 7b=7b 7c=7c 7d=7d 7e=7e 7f=7f 
80=80 81=81 82=82 83=83 84=84 85=85 86=86 87=87 88=88 89=89 8a=8a 8b=8b 8c=8c 
8d=8d 8e=8e 8f=8f 90=90 91=91 92=92 93=93 94=94 95=95 96=96 97=97 98=98 99=99 
9a=9a 9b=9b 9c=9c 9d

Re: Turning off Nvidia GPU card in Optimus configuration

2014-11-09 Thread Eugene Yunak
On Sunday, November 9, 2014, Lampshade  wrote:

> Hi
> I was trying half year ago to use OpenBSD 5.5, but system heated my
> laptop. I have Intel and Nvidia GPU in laptop. I can not disable Nvidia GPU
> via BIOS. Laptop always exposes and enables two GPUs by default.  OpenBSD
> does not disabled Nvidia GPU, so it heated laptop. I have tried OpenBSD 5.6
> and it still heats my laptop. On Linux Nvidia's GPU is disabled
> automatically. I wanted to find how to disable my card manually, I used
> acpi_call Linux module (on Linux of course). In my laptop script
> turn_off_gpu.sh is disabling GPU when I strip methods variable to:
>
> methods="
> \_SB.PCI0.PEG0.PEGP._OFF"
>
> and enables when:
> methods="
> \_SB.PCI0.PEG0.PEGP._ON"
>
> Is there any way in OpenBSD to send first (disabling) command to hardware?
> It is the only reason I don't use OpenBSD. Maybe somebody can write few
> lines of code and I will compile kernel for myself?
>
> References:
> http://linux-hybrid-graphics.blogspot.com/2010/07/u … ch-onoff.html
> https://github.com/mkottman/acpi_call
>
>
acpi_call support would be awesome!
Another use case for it is setting minimum and maximum
battery charge levels for thinkpads newer than xx30 line.


--
The best the little guy can do is what
the little guy does right



Basic question about following current

2014-11-09 Thread Theodore Wynnychenko
Hello

I am thinking of taking the plunge and following current.
It all seems straightforward.
I have looked at the FAQ's and other sources.
I understand that it goes like this (simplistically):

Get a new snapshot from mirror
Sysmerge etc/xetc
Cp bsd.rd to /
Boot into bsd.rd
Follow upgrade
Reboot
Sysmerge again to be sure
Update packages (pkg_add -ui)

So far, got it.
But, I am confused about ports.
If I have something build from ports, I would want to update that as well,
right?

I see that there is a "ports.tar.gz" in the snapshot directory.  But, in the
FAQ it says: "You must make sure your kernel, 'userland' (the supporting
utilities and files) and ports tree are all in sync."

There is no src, sys, or xenocara in the snapshot directory (I saw the
explanation in the FAQ or somewhere, and it makes total sense).

Therefore, my question is: if I am trying to update a port (using "make
update" from a local ports tree), should I use the "ports.tar.gz" that is in
the snapshot directory by uncompressing it over the top of the ports tree I
already have?  Or, should I download the current source and ports trees
using anoncvs, and do the "make update" from the most current ports tree in
anoncvs?  Or, is either choice ok?

I guess this comes down to a fundamental not understanding of exactly
whether or not the local ports tree needs access to the current source tree
or not, when trying to build or update a port.

Thanks
Ted



Re: Basic question about following current

2014-11-09 Thread Fred

On 11/09/14 19:09, Theodore Wynnychenko wrote:

Hello

I am thinking of taking the plunge and following current.
It all seems straightforward.
I have looked at the FAQ's and other sources.
I understand that it goes like this (simplistically):

Get a new snapshot from mirror
Sysmerge etc/xetc

This first sysmerge is not necessary.

Cp bsd.rd to /
Boot into bsd.rd
Follow upgrade
Reboot
Sysmerge again to be sure
Update packages (pkg_add -ui)

So far, got it.
But, I am confused about ports.
If I have something build from ports, I would want to update that as well,
right?

I see that there is a "ports.tar.gz" in the snapshot directory.  But, in the
FAQ it says: "You must make sure your kernel, 'userland' (the supporting
utilities and files) and ports tree are all in sync."


cvs up -Pd in your /usr/ports directory should bring your ports up to 
current.




There is no src, sys, or xenocara in the snapshot directory (I saw the
explanation in the FAQ or somewhere, and it makes total sense).

Therefore, my question is: if I am trying to update a port (using "make
update" from a local ports tree), should I use the "ports.tar.gz" that is in
the snapshot directory by uncompressing it over the top of the ports tree I
already have?  Or, should I download the current source and ports trees
using anoncvs, and do the "make update" from the most current ports tree in
anoncvs?  Or, is either choice ok?


You can you the ports.tar.gz as the starting point.



I guess this comes down to a fundamental not understanding of exactly
whether or not the local ports tree needs access to the current source tree
or not, when trying to build or update a port.


If you are using current then you need the latest ports tree - cvs up 
should do the trick.


hth

Fred



Re: Sun/Cassini Quad Gigabit Card Not Detected

2014-11-09 Thread Miod Vallat
> Hi,
> 
> I've installed OpenBSD 5.6 (i386) on a dual processor XEON box which
> has a 4 port Sun (Sun# 501-6738-10) Gigabit NIC card.  dmesg doesn't
> have any indication that the card is installed. Booting Linux shows
> the card as Sun/Cassini which I believe should be handled by the "cas"
> driver.

The cas(4) driver for this hardware is not enabled in the i386 and amd64
kernels, and is probably untested on these platforms.

You might want to add

cas*at pci?

to the kernel configuration file and rebuild it, and see if it works.

Miod



sndio: watchdog timeout when recording from internal mic on Thinkpad T400

2014-11-09 Thread Gregor Best
Hi people,

I'm trying to record audio from my Thinkpads internal microphone
on -current (-ish, but as far as I see, there are no sound related
changes missing). The audio device is:

   azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi
   azalia0: codecs: Conexant CX20561
   audio0 at azalia0

As far as I understand it, starting sndiod with

   sndiod -d -C 2:3

should make mic2 (the internal microphone) the default. If I now
try recording without explicitly specifying an audio device, after
a few seconds, sndio prints

   snd0: watchdog timeout

and the audio device gets closed, without any of the audio making
it into the recording application. As far as I can see, the timeout
occurs during sio_open(SIO_DEVANY, SIO_REC, 0) inside the application.
Recording from the external microphone (ADC channels 0:1) works
fine.

What would be the easiest way for me to debug this?

Below is the output of mixerctl:

   inputs.dac-0:1=150,150
   inputs.dac-2:3=150,150
   inputs.beep=85
   record.adc-2:3_source=mic2
   record.adc-2:3=126,126
   record.adc-0:1_source=mic
   record.adc-0:1=126,126
   outputs.hp_source=dac-0:1
   outputs.hp_boost=off
   inputs.mic=189,189
   outputs.mic_dir=input-vr80
   outputs.spkr_source=dac-2:3
   outputs.spkr_eapd=on
   inputs.mic2=126,126
   outputs.hp_sense=unplugged
   outputs.mic_sense=unplugged
   outputs.master=151,151
   outputs.master.mute=off
   outputs.master.slaves=dac-0:1,dac-2:3
   record.volume=126,126
   record.volume.mute=off
   record.volume.slaves=adc-2:3,adc-0:1

Thanks for your help.

-- 
   Gregor Best



xHCI not configured on Intel 7 series

2014-11-09 Thread Joe Gidi
I see that xHCI has been enabled in -current and I'd like to start testing
on my system, but the driver is not attaching:

"Intel 7 Series xHCI" rev 0x04 at pci0 dev 20 function 0 not configured

I know xHCI is brand-new and under heavy development; is it expected to
support this controller at this time?

Oh, not related, but I notice this "warning: no entropy supplied by boot
loader" line appearing in recent snaps. Any cause for concern?

Full dmesg:

OpenBSD 5.6-current (GENERIC.MP) #544: Fri Nov  7 10:36:24 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8454504448 (8062MB)
avail mem = 8225640448 (7844MB)
warning: no entropy supplied by boot loader
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec350 (88 entries)
bios0: vendor Dell Inc. version "A18" date 10/06/2014
bios0: Dell Inc. Precision T1650
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT SSDT DMAR ASF! SLIC
acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) USB1(S3)
USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4)
PXSX(S4) RP02(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz, 3193.35 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
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 99MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz, 3192.74 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz, 3192.74 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz, 3192.74 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P1)
acpiprt2 at acpi0: bus -1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus -1 (PEG0)
acpiprt11 at acpi0: bus -1 (PEG1)
acpiprt12 at acpi0: bus -1 (PEG2)
acpiprt13 at acpi0: bus -1 (PEG3)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpicpu2 at acpi0: C3, C2, C1, PSS
acpicpu3 at acpi0: C3, C2, C1, PSS
acpitz0 at acpi0: critical temperature is 106 degC
acpitz1 at acpi0: critical temperature is 106 degC
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
acpibat2 at acpi0: BAT2 not present
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD01
acpivout1 at acpivideo0: DD02
acpivout2 at acpivideo0: DD03
acpivout3 at acpivideo0: DD04
acpivout4 at acpivideo0: DD05
acpivout5 at acpivideo0: DD06
acpivout6 at acpivideo0: DD07
acpivout7 at acpivideo0: DD08
cpu0: Enhanced SpeedStep 3193 MHz: speeds: 3201, 3200, 3100, 3000, 2900,
2700, 2600, 2500, 2400, 2300, 2200, 2100, 1900, 1800, 1700, 1600 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Xeon E3-1200 v2 Host" rev 0x09
vga1 at pci0 dev 2 function 0 "Intel HD Graphics P4000" rev 0x09
intagp at vga1 not configured
inteldrm0 at vga1
drm0 at inteldrm0
drm: Memory us

httpd slowcgi notes

2014-11-09 Thread Elijah Buck
Hello,

I've upgraded my 5.4 server to 5.5 and then 5.6 and have switched
from nginx to httpd. This is all excellent.

I wanted to share how I made httpd work for me. I host a simple
static site, but also need '301 Moved Permanently' support, which
httpd does not seem to support at this time. However, httpd does
support FastCGI, so I use a small Perl CGI script called via slowcgi
to set the 301 redirect header.

It is a bit underdocumented that the 'root' httpd option can be
used to tell slowcgi which script to execute.

##httpd.conf##

ext_addr="egress"
server "www.example.com" {
listen on $ext_addr port 80
}
server "old.example.com" {
listen on $ext_addr port 80
fastcgi socket "/run/slowcgi.sock"
root "/cgi-bin/redir.pl"
}


##redir.pl##

#!/usr/bin/perl -Tw
use CGI;
my $q = CGI->new();
print $q->redirect(
  -location => 'http://www.example.com',
  -status => '301 Moved Permanently',
);

You will also have to setup perl in the chroot and start slowcgi.

Cheers,
Elijah



Re: Sun/Cassini Quad Gigabit Card Not Detected

2014-11-09 Thread Jeff
Miod,

Thanks!

I've made progress.  OpenBSD now recognizes the four cas NIC's
and detects active/no carrier, but won't pass any traffic.  I suspect
that it's because the mac addr (lladdr) is all zero's

Jeff

On Sun, Nov 09, 2014 at 07:43:15PM +, Miod Vallat wrote:
> > Hi,
> > 
> > I've installed OpenBSD 5.6 (i386) on a dual processor XEON box which
> > has a 4 port Sun (Sun# 501-6738-10) Gigabit NIC card.  dmesg doesn't
> > have any indication that the card is installed. Booting Linux shows
> > the card as Sun/Cassini which I believe should be handled by the "cas"
> > driver.
> 
> The cas(4) driver for this hardware is not enabled in the i386 and amd64
> kernels, and is probably untested on these platforms.
> 
> You might want to add
> 
> cas*  at pci?
> 
> to the kernel configuration file and rebuild it, and see if it works.
> 
> Miod



No closing quote

2014-11-09 Thread Jason Adams
Everytime /etc/netstart runs I get a no closing quote message.

Hate to obsess about trivialities but wondering If I've messed something up.
All interfaces seem to work just fine.

-- 
Those who do not understand Unix are condemned to reinvent it, poorly.



Re: No closing quote

2014-11-09 Thread Jason Adams
On 11/09/2014 02:30 PM, h410g3n wrote:
> I encountered the same problem.
>
> You must have just upgraded from 5.5 and forgot to run sysmerge, right? :D
>
> Jason Adams wrote:
>> Everytime /etc/netstart runs I get a no closing quote message.
>>
>> Hate to obsess about trivialities but wondering If I've messed something up.
>> All interfaces seem to work just fine.
>>

Did upgrade.
Did NOT forget to run sysmerge. 

That's the google answer, but its not the REAL answer.

-- 
Those who do not understand Unix are condemned to reinvent it, poorly.



Re: No closing quote

2014-11-09 Thread Philip Guenther
On Sun, Nov 9, 2014 at 2:33 PM, Jason Adams  wrote:
> On 11/09/2014 02:30 PM, h410g3n wrote:
>> I encountered the same problem.
>>
>> You must have just upgraded from 5.5 and forgot to run sysmerge, right? :D
>>
>> Jason Adams wrote:
>>> Everytime /etc/netstart runs I get a no closing quote message.
>>>
>>> Hate to obsess about trivialities but wondering If I've messed something up.
>>> All interfaces seem to work just fine.
>
> Did upgrade.
> Did NOT forget to run sysmerge.
>
> That's the google answer, but its not the REAL answer.

It's also the "crystal ball at the shop for repairs" answer when
there's no data in the report.

Since you didn't show them, I'll take the next guess with "you have a
quoted string in an /etc/hostname.* file which contains whitespace".

(If that's the case, I think the solution depends on which the string
is there for, but why guess when you can just show a (possibly
redacted) version?)


And if *that's* not the case, then how about you run /etc/netstart
with sh -x and debug it?


Philip Guenther



Re: xHCI not configured on Intel 7 series

2014-11-09 Thread Andrew Fresh
On Sun, Nov 09, 2014 at 03:54:50PM -0500, Joe Gidi wrote:
> I see that xHCI has been enabled in -current and I'd like to start testing
> on my system, but the driver is not attaching:
> 
> "Intel 7 Series xHCI" rev 0x04 at pci0 dev 20 function 0 not configured

> OpenBSD 5.6-current (GENERIC.MP) #544: Fri Nov  7 10:36:24 MST 2014

This Nov 7th amd64 snapshot did not catch the commit that enabled xHCI.
If you wait for the next snapshot or build a kernel yourself you may
have better luck.

l8rZ,
-- 
andrew - http://afresh1.com

Software doesn't do what you want it to do, it does what you tell it do.
  -- Stefan G. Weichinger.



Re: No closing quote

2014-11-09 Thread Jason Adams
On 11/09/2014 03:19 PM, Philip Guenther wrote:
> On Sun, Nov 9, 2014 at 2:33 PM, Jason Adams  wrote:
>> On 11/09/2014 02:30 PM, h410g3n wrote:
>>> I encountered the same problem.
>>>
>>> You must have just upgraded from 5.5 and forgot to run sysmerge, right? :D
>>>
>>> Jason Adams wrote:
 Everytime /etc/netstart runs I get a no closing quote message.

 Hate to obsess about trivialities but wondering If I've messed something 
 up.
 All interfaces seem to work just fine.
>> Did upgrade.
>> Did NOT forget to run sysmerge.
>>
>> That's the google answer, but its not the REAL answer.
> It's also the "crystal ball at the shop for repairs" answer when
> there's no data in the report.
>
> Since you didn't show them, I'll take the next guess with "you have a
> quoted string in an /etc/hostname.* file which contains whitespace".
>
> (If that's the case, I think the solution depends on which the string
> is there for, but why guess when you can just show a (possibly
> redacted) version?)
>
>
> And if *that's* not the case, then how about you run /etc/netstart
> with sh -x and debug it?
>
>
> Philip Guenther
Definitely no quoted anything with white space in any hostname.if.
If fact even when they only have one parameter: dhcp, this happens.

And it happens very near the top of netstart
---
# sh -x /etc/netstart
+ [ -n ]
+ . /etc/rc.d/rc.subr
+ FUNCS_ONLY=1
+ [ -n 1 ]
+ return
+ _rc_parse_conf
/etc/netstart: no closing quote
---

It even happens when you give it a non-existent hostneme file:

-
# sh -x /etc/netstart aex0
+ [ -n ]
+ . /etc/rc.d/rc.subr
+ FUNCS_ONLY=1
+ [ -n 1 ]
+ return
+ _rc_parse_conf
/etc/netstart: no closing quote
+ [ 1 -gt 0 ]
+ [ 1 -gt 0 ]
+ ifstart aex0
netstart: /etc/hostname.aex0: No such file or directory
+ shift
+ [ 0 -gt 0 ]
+ return
#
---

-- 
Those who do not understand Unix are condemned to reinvent it, poorly.



Patch to enable ZTE MF821 modem in umsm.c (semi-working, need help)

2014-11-09 Thread Jakub Skrzypnik
Let me start rapidly ;)

Index: usb/umsm.c
===
RCS file: /cvs/src/sys/dev/usb/umsm.c,v
retrieving revision 1.100
diff -u -p -d -h -p -r1.100 umsm.c
--- usb/umsm.c 12 Jul 2014 21:24:33 - 1.100
+++ usb/umsm.c 9 Nov 2014 23:52:30 -
@@ -169,11 +169,13 @@ static const struct umsm_type umsm_devs[
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER2 }, DEV_UMASS6},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER3 }, DEV_UMASS7},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER4 }, DEV_UMASS4},
+// {{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER5 }, DEV_UMASS6},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_K3565Z }, 0},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF112 }, DEV_UMASS4},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF633 }, 0},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF637 }, 0},
{{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MSA110UP }, 0},
+ {{ USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF821 }, 0},

{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_EXPRESSCARD }, 0},
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_MERLINV620 }, 0},
Index: usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.639
diff -u -p -d -h -p -r1.639 usbdevs
--- usb/usbdevs 31 Oct 2014 21:17:42 - 1.639
+++ usb/usbdevs 9 Nov 2014 23:52:30 -
@@ -3417,9 +3417,11 @@ product ZTE MF633 0x0016 ZTE MF633 USUP
product ZTE MF637 0x0031 ZTE MF637 HSUPA USB modem
product ZTE K3565Z 0x0063 ZTE K3565-Z USB MSM modem
product ZTE UMASS_INSTALLER4 0x0083 ZTE USB MSM installer
+product ZTE UMASS_INSTALLER50x0166  ZTE USB MSM installer
product ZTE MSA110UP 0x0091 ONDA MSA110UP USB MSM modem
product ZTE UMASS_INSTALLER2 0x0103 ZTE USB MSM installer
product ZTE MF112 0x0117 ZTE MF112 HSUPA USB modem
+product ZTE MF821 0x0167  ZTE MF821 LTE USB modem
product ZTE HSUSB 0x1364 ZTE HSUSB
product ZTE UMASS_INSTALLER 0x2000 ZTE USB MSM installer
product ZTE AC2746 0xfff1 AC2746 CDMA USB modem
Index: usb/usbdevs.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
retrieving revision 1.651
diff -u -p -d -h -p -r1.651 usbdevs.h
--- usb/usbdevs.h 31 Oct 2014 21:17:53 - 1.651
+++ usb/usbdevs.h 9 Nov 2014 23:52:30 -
@@ -3431,7 +3431,9 @@
#define USB_PRODUCT_ZTE_UMASS_INSTALLER 0x2000 /* ZTE USB MSM installer */
#define USB_PRODUCT_ZTE_AC2746 0xfff1 /* AC2746 CDMA USB modem */
#define USB_PRODUCT_ZTE_UMASS_INSTALLER3 0xfff5 /* ZTE USB CDMA installer */
+#define USB_PRODUCT_ZTE_UMASS_INSTALLER50x0166  /* ZTE USB
MSM installer */
#define USB_PRODUCT_ZTE_AC8700 0xfffe /* AC8700 CDMA USB modem */
+#define USB_PRODUCT_ZTE_MF821 0x0167/* ZTE MF821 LTE modem */

/* Quanta products */
#define USB_PRODUCT_QUANTA_RT3070 0x0304 /* RT3070 */
Index: usb/usbdevs_data.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
retrieving revision 1.645
diff -u -p -d -h -p -r1.645 usbdevs_data.h
--- usb/usbdevs_data.h 31 Oct 2014 21:17:53 - 1.645
+++ usb/usbdevs_data.h 9 Nov 2014 23:52:30 -
@@ -8409,6 +8409,10 @@ const struct usb_known_product usb_known
   USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF637,
   "ZTE MF637 HSUPA USB modem",
},
+{
+USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MF821,
+"ZTE MF821 LTE USB modem",
+},
{
   USB_VENDOR_ZTE, USB_PRODUCT_ZTE_K3565Z,
   "ZTE K3565-Z USB MSM modem",
@@ -8417,6 +8421,10 @@ const struct usb_known_product usb_known
   USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER4,
   "ZTE USB MSM installer",
},
+{
+USB_VENDOR_ZTE, USB_PRODUCT_ZTE_UMASS_INSTALLER5,
+"ZTE USB MSM installer",
+},
{
   USB_VENDOR_ZTE, USB_PRODUCT_ZTE_MSA110UP,
   "ONDA MSA110UP USB MSM modem",

OK, now some explaination. This isn't a very innovative patch. I'm only
adding a ZTE MF821 LTE modem to the list of usbdevs and umsm.c enabled
devices.

But, wait, there's more! It doesn't to USB modeswitching (look at thhis
commented line in umsm.c), because any of DEV_UMASS* methods won't work.
So, I used to tell modem to be always a modem, not a fake CDROM drive by AT
command "AT+ZCDRUN=8" which I done via serial terminal emulator on my home
MikroTik box. It disables "USB CDROM" mode (number 9 enables it back) and
reports modem always as modem. And here ends my competence, now I'll only
describe how modem behaves in certain situations:

* USB VID is 19d2 (ZTE one), at boot (red led) it shows as PID 0166 and
after some seconds (green led, associated to network) it becomes a PID 0167.

* On a clean OpenBSD kernel, when I plug that modem in, OpenBSD loads
ugen/umass device driver for internal microSD reader in modem and a cdrom
driver for "installation CD" (a ROM with device drivers for Microshit
Windoze). None of umsm/ucom drivers is loaded.

* With AT+ZCDRUN=8 option, on clean kernel, modem behaves in the same way.

* On kernel with that patch

Re: Sun/Cassini Quad Gigabit Card Not Detected

2014-11-09 Thread Jeff
Hi,

Here is the output from dmesg after the kernel rebuild:


OpenBSD 5.6 (CASSINI) #1: Sun Nov  9 16:38:22 EST 2014
r...@firewall-m.rtr.com:/usr/src/sys/arch/i386/compile/CASSINI
cpu0: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu0: 
FPU,V86,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,CNXT-ID,xTPR,PERF
real mem  = 2146906112 (2047MB)
avail mem = 2099343360 (2002MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/26/06, BIOS32 rev. 0 @ 0xfb000, SMBIOS 
rev. 2.2 @ 0xf (57 entries)
bios0: vendor IBM version "-[OPE151A]-" date 09/26/2006
bios0: IBM -[6221LJU]-
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP ASF! APIC
acpi0: wakeup devices HUB0(S5) HUBA(S5) HUBB(S5) PS2M(S4) PS2K(S4) USB0(S1) 
USB1(S1) USB3(S1) MODM(S5) PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 6 (application processor)
cpu1: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu1: 
FPU,V86,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,CNXT-ID,xTPR,PERF
cpu2 at mainbus0: apid 7 (application processor)
cpu2: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu2: 
FPU,V86,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,CNXT-ID,xTPR,PERF
cpu3 at mainbus0: apid 1 (application processor)
cpu3: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu3: 
FPU,V86,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,CNXT-ID,xTPR,PERF
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
ioapic1 at mainbus0: apid 5 pa 0xfec8, version 20, 24 pins
ioapic2 at mainbus0: apid 6 pa 0xfec80400, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (HUB0)
acpiprt2 at acpi0: bus 5 (HUBA)
acpiprt3 at acpi0: bus 3 (HUBB)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xa800 0xcc000/0x1800
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E7505 Host" rev 0x03
agp at pchb0 not configured
"Intel E7505 Error Reporting" rev 0x03 at pci0 dev 0 function 1 not configured
ppb0 at pci0 dev 1 function 0 "Intel E7505 AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA Riva TNT2" rev 0x15
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb1 at pci0 dev 2 function 0 "Intel E7505 PCI" rev 0x03
pci2 at ppb1 bus 2
"Intel 82870P2 IOxAPIC" rev 0x04 at pci2 dev 28 function 0 not configured
ppb2 at pci2 dev 29 function 0 "Intel 82870P2 PCIX-PCIX" rev 0x04
pci3 at ppb2 bus 3
bge0 at pci3 dev 1 function 0 "Broadcom BCM5703X" rev 0x02, BCM5702/5703 A2 
(0x1002): apic 6 int 0, address 00:0c:76:4e:5d:6e
brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
ppb3 at pci3 dev 2 function 0 vendor "Intel", unknown product 0x537c rev 0x07
pci4 at ppb3 bus 4
cas0 at pci4 dev 0 function 0 "NS Saturn" rev 0x30: apic 6 int 4, address 
00:00:00:00:00:00
nsgphy0 at cas0 phy 1: DP83865 10/100/1000 PHY, rev. 8
cas1 at pci4 dev 1 function 0 "NS Saturn" rev 0x30: apic 6 int 5, address 
00:00:00:00:00:00
gentbi0 at cas1 phy 0: Generic ten-bit interface, rev. 0
cas2 at pci4 dev 2 function 0 "NS Saturn" rev 0x30: apic 6 int 6, address 
00:00:00:00:00:00
nsgphy1 at cas2 phy 1: DP83865 10/100/1000 PHY, rev. 8
cas3 at pci4 dev 3 function 0 "NS Saturn" rev 0x30: apic 6 int 7, address 
00:00:00:00:00:00
gentbi1 at cas3 phy 0: Generic ten-bit interface, rev. 0
"Intel 82870P2 IOxAPIC" rev 0x04 at pci2 dev 30 function 0 not configured
ppb4 at pci2 dev 31 function 0 "Intel 82870P2 PCIX-PCIX" rev 0x04
pci5 at ppb4 bus 5
"Intel E7505 PCI" rev 0x03 at pci0 dev 2 function 1 not configured
ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x82
pci6 at ppb5 bus 6
"TI TSB43AB22 FireWire" rev 0x00 at pci6 dev 1 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x02: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide0: channel 1 disabled (no drives)
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x02: apic 4 int 17
iic0 at ichiic0
iic0: addr 0x22 01=01 02=02 03=03 04=04 05=05 06=06 07=07 08=08 09=09 0a=0a 

Re: No closing quote

2014-11-09 Thread Philip Guenther
On Sun, Nov 9, 2014 at 4:17 PM, Jason Adams  wrote:
> Definitely no quoted anything with white space in any hostname.if.
> If fact even when they only have one parameter: dhcp, this happens.
>
> And it happens very near the top of netstart
> ---
> # sh -x /etc/netstart
> + [ -n ]
> + . /etc/rc.d/rc.subr
> + FUNCS_ONLY=1
> + [ -n 1 ]
> + return
> + _rc_parse_conf
> /etc/netstart: no closing quote

Oh, then your /etc/rc.conf.local** has something not permitted by the
new, more restrictive syntax.  To quote the upgrade faq;

rc.conf.local is no longer a shell script. Variables (notably
pkg_scripts) must now be on single lines.


Philip Guenther

** or your /etc/rc.conf, if you ignored the comments and edited it



Re: No closing quote

2014-11-09 Thread Jason Adams
On 11/09/2014 04:54 PM, Philip Guenther wrote:
> On Sun, Nov 9, 2014 at 4:17 PM, Jason Adams  wrote:
>> Definitely no quoted anything with white space in any hostname.if.
>> If fact even when they only have one parameter: dhcp, this happens.
>>
>> And it happens very near the top of netstart
>> ---
>> # sh -x /etc/netstart
>> + [ -n ]
>> + . /etc/rc.d/rc.subr
>> + FUNCS_ONLY=1
>> + [ -n 1 ]
>> + return
>> + _rc_parse_conf
>> /etc/netstart: no closing quote
> Oh, then your /etc/rc.conf.local** has something not permitted by the
> new, more restrictive syntax.  To quote the upgrade faq;
>
> rc.conf.local is no longer a shell script. Variables (notably
> pkg_scripts) must now be on single lines.
>
>
> Philip Guenther
>
> ** or your /etc/rc.conf, if you ignored the comments and edited it
Bingo!

There was no problem in my rc.conf.local.

My rc.conf was a shell script with a date in the comments from 2103.
The one I extracted from etc56.tgz was NOT a shell script and had  date 2014 in 
the comments.

Making the appropriate backups, I carefully inspected the two for differences, 
and saw nothing
that looked problematic.

So I swapped in the the one I extracted from etc56.tgz into /etc and rebooted.
No more closing quote messages.  Everything seems to be running normally

Upon detailed inspection I think I may have edited rc.conf several months 
before I upgraded.
(This is exactly my second OpenBSD install, as you probably already guessed.)

sysmerge didn't show any differences previously AND
it doesn't show any differences NOW after I swapped in the one from etc56.tgz

No clue why that is.

Thanks for your help.

(i386 system)



-- 
Those who do not understand Unix are condemned to reinvent it, poorly.



ARP Networks VPS not booting after upgrade to 5.6

2014-11-09 Thread William Orr
Hey,

I went through and update to 5.6 from 5.5 on my VPS from ARP Networks
(qemu). Update seemed to go well, except now my box halts shortly after
initializing USB devices.

(message continued below dmesg)

booting hd0a:/bsd: 7721392+2124652+1096312+0+609056
[100+554112+368667]=0xfe6368
entry point at 0x10001e0 [7205c766, 3404, 24448b12, dba0a304]
[ using 923720 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2014 OpenBSD. All rights reserved.
http://www.OpenBSD.org

OpenBSD 5.6 (GENERIC) #310: Fri Aug  8 00:14:24 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 788508672 (751MB)
avail mem = 758833152 (723MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x2ef0 (10 entries)
bios0: vendor Bochs version "Bochs" date 01/01/2007
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: QEMU Virtual CPU version 0.12.3, 2600.56 MHz
cpu0:
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MM
X,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,NXE,LONG,LAHF,ABM,SSE4A,PERF
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 1000MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 10240MB, 20971520 sectors
atapiscsi0 at pciide0 channel 0 drive 1
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom
removable
wd0(pciide0:0:0): using PIO mode 0, DMA mode 2
cd0(pciide0:0:1): using PIO mode 0
atapiscsi1 at pciide0 channel 1 drive 0
scsibus2 at atapiscsi1: 2 targets
cd1 at scsibus2 targ 0 lun 0:  ATAPI 5/cdrom
removable
cd1(pciide0:1:0): using PIO mode 0
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 1 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 1
int 9
iic0 at piixpm0
iic0: addr 0x18 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
iic0: addr 0x1a 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
iic0: addr 0x29 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
iic0: addr 0x2b 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
iic0: addr 0x4c 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
iic0: addr 0x4e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00
words 00= 01= 02= 03= 04= 05= 06= 07=
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x03: apic 1 int 11,
address 52:54:00:27:27:49
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: density unknown
fd1 at fdc0 drive 1: density unknown
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
nvram: invalid checksum

---

My first thought was to disable uhci, but that still freezes a bit later.

>> OpenBSD/amd64 BOOT 3.28
boot> boot -c
booting hd0a:/bsd: 7721392+2124652+1096312+0+609056
[100+554112+368667]=0xfe6368
entry point at 0x10001e0 [7205c766, 3404, 24448b12, dba0a304]
[ using 923720 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University