Re: Starting isc_named earlier

2015-08-23 Thread Edgar Pettijohn

On 08/23/15 12:40, Theo de Raadt wrote:

something like this would probably do it, but would be undone anytime
you update
or at least I think it will be undone, but maybe not I don't have any 
experience with making changes to it.


--- /etc/rc Sat Aug 22 03:06:56 2015
+++ /etc/rc.new Sun Aug 23 12:27:53 2015
@@ -371,7 +371,7 @@
   make_keys

   echo -n 'starting early daemons:'
-start_daemon syslogd ldattach pflogd nsd unbound ntpd
+start_daemon syslogd ldattach pflogd isc_named ntpd
   start_daemon iscsid isakmpd iked sasyncd ldapd npppd
   echo '.'

probably have to add something to /etc/rc.conf.local like 
isc_named_flags=YES



On 08/23/15 12:00, George wrote:

Hi guys,

I was wondering if someone might have a hint on how to start isc_name
(on 5.7) earlier than network services like DHCP and NFS. This was OK
for me on 5.6 when it was in base but now I have issues as my configs
are tied to DNS services on the local machine.

I read a bit and fiddled with the rc code, getting failures there, ... I
am maybe not looking in the right place??

Or don't use ISC BIND.  Start your migrationg towards unbound / nsd,
which are the new, safer toolkit for DNS.

In my opinion, ISC BIND falls soundly into this catagory:

 https://en.wikipedia.org/wiki/Unsafe_at_Any_Speed

As a former corvair owner I guarantee it was perfectly safe while parked.


general reluctance to spend money on improving safety

Except in this case, it is not the manufacturers, but the drivers
failing to spend time catching up.

There is a general reluctance by many system administrators to
 (a) comprehend that two decades of research has demonstrated the
 unsoundness of resource record caching when doing
 mixed authoritative + recursive
 (b) because it can do do mixed mode, in practice BIND encourages
 doing so
 (c) in part, NSD and unbound were written to stop that practice
 (d) Some of you are sticks in the mud, and deserve to get hurt.




wtfs write error when running newfs

2015-08-23 Thread Alessandro DE LAURENZIS
Dear misc@ readers,

I'm trying to build a new FFS on a internal IDE HDD connected to a
laptop through an IDE-to-USB case.

The device seems to be correctly detected (full dmesg in [1]):

[snip]
Aug 23 20:55:39 poseidon /bsd: umass0 at uhub1
Aug 23 20:55:39 poseidon /bsd:  port 1 configuration 1 interface 0 Super Top 
USB 2.0  IDE DEVICE rev 2.00/2.01 addr 2
Aug 23 20:55:39 poseidon /bsd: umass0: using SCSI over Bulk-Only
Aug 23 20:55:39 poseidon /bsd: scsibus5 at umass0: 2 targets, initiator 0
Aug 23 20:55:39 poseidon /bsd: sd1 at scsibus5 targ 1 lun 0: Maxtor 6, Y080P0, 
0 0 SCSI0 0/direct fixed
Aug 23 20:55:39 poseidon /bsd: sd1: 78167MB, 512 bytes/sector, 160086528 sectors
[snip]

The disk has been labeled using disklabel(8):

[snip]
root@poseidon:[~] disklabel sd1   
# /dev/rsd1c:
type: SCSI
disk: SCSI disk
label: Y080P0  
duid: 12ac56f9054d3e03
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 9964
total sectors: 160086528
boundstart: 0
boundend: 160086528
drivedata: 0 

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  a:1600865280  4.2BSD   2048 163841 
  c:1600865280  unused   
[snip]

But when I try to launch the newfs command, the following error message
is issued:

[snip]
root@poseidon:[~] newfs sd1a
newfs: wtfs: write error on block 160086527: No such file or directory
[snip]

I really don't understand what's happening; I tried to build an ext2fs
in Linux on the same disk, and all is ok, so this shouldn't be an h/w
failure...

Any hints/feedback?

All the best

[1]
OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2087387136 (1990MB)
avail mem = 2020290560 (1926MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (73 entries)
bios0: vendor LENOVO version 7LETD0WW (2.30 ) date 02/27/2012
bios0: LENOVO 7735WX2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT ASF! SSDT SSDT SSDT 
SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) IGBE(S4) EXP0(S4) 
EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 798.18 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 798.00 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 5 (EXP3)
acpiprt6 at acpi0: bus 13 (EXP4)
acpiprt7 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB4, EHC0, EHC1
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 42T5264 serial  4317 type LION oem Panasonic
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit offline
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
cpu0: Enhanced SpeedStep 798 MHz: speeds: 2101, 2100, 1600, 1200, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c
vga1 at pci0 dev 2 function 0 Intel GM965 Video rev 0x0c
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, 

Start isc_named earlier

2015-08-23 Thread g . lister
On Sun Aug 23 15:40:57 2015 GMT+0200, Richard Thornton wrote:
 When this test box, a Sempron 3400 begins to boot, USB is recognized:
 
 OpenBSD 5.7 (RAMDISK_CD) #806: Sun Mar  8 11:08:49 MDT 2015
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
 real mem = 3404660736 (3246MB)
 avail mem = 3312402432 (3158MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf (53 entries)
 bios0: vendor Phoenix Technologies, LTD version 3.13 date 11/15/2005
 bios0: Compaq Presario 061 EL426AA-ABA SR1710NX NA611
 acpi0 at bios0: rev 0
 acpi0: sleep states S0 S1 S3 S4 S5
 acpi0: tables DSDT FACP SSDT SRAT MCFG APIC
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: AMD Sempron(tm) Processor 3400+, 1990.12 MHz
 cpu0: 
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 128KB 
 64b/line 16-way L2 cache
 cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully 
 associative
 cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully 
 associative
 cpu0: AMD erratum 89 present, BIOS upgrade may be required
 cpu0: apic clock running at 198MHz
 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus 2 (P2P_)
 acpiprt2 at acpi0: bus 1 (AGP_)
 pci0 at mainbus0 bus 0
 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10
 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00
 pci1 at ppb0 bus 1
 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 pciide0 at pci0 dev 18 function 0 ATI SB400 SATA rev 0x00: DMA
 pciide0: using apic 2 int 22 for native-PCI interrupt
 pciide0: port 0: device present, speed: 1.5Gb/s
 wd0 at pciide0 channel 0 drive 0: Maxtor 6L100M0
 wd0: 16-sector PIO, LBA48, 95396MB, 195371568 sectors
 wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5
 ohci0 at pci0 dev 19 function 0 ATI SB400 USB rev 0x00: apic 2 int 18, 
 version 1.0, legacy sup 



Starting isc_named earlier

2015-08-23 Thread George
Hi guys,

I was wondering if someone might have a hint on how to start isc_name
(on 5.7) earlier than network services like DHCP and NFS. This was OK
for me on 5.6 when it was in base but now I have issues as my configs
are tied to DNS services on the local machine. 

I read a bit and fiddled with the rc code, getting failures there, ... I
am maybe not looking in the right place??

Any hints appreciated.
Regards,
George



Re: Starting isc_named earlier

2015-08-23 Thread Theo de Raadt
 something like this would probably do it, but would be undone anytime 
 you update
 
 --- /etc/rc Sat Aug 22 03:06:56 2015
 +++ /etc/rc.new Sun Aug 23 12:27:53 2015
 @@ -371,7 +371,7 @@
   make_keys
 
   echo -n 'starting early daemons:'
 -start_daemon syslogd ldattach pflogd nsd unbound ntpd
 +start_daemon syslogd ldattach pflogd isc_named ntpd
   start_daemon iscsid isakmpd iked sasyncd ldapd npppd
   echo '.'
 
 
 On 08/23/15 12:00, George wrote:
  Hi guys,
 
  I was wondering if someone might have a hint on how to start isc_name
  (on 5.7) earlier than network services like DHCP and NFS. This was OK
  for me on 5.6 when it was in base but now I have issues as my configs
  are tied to DNS services on the local machine.
 
  I read a bit and fiddled with the rc code, getting failures there, ... I
  am maybe not looking in the right place??

Or don't use ISC BIND.  Start your migrationg towards unbound / nsd,
which are the new, safer toolkit for DNS.

In my opinion, ISC BIND falls soundly into this catagory:

https://en.wikipedia.org/wiki/Unsafe_at_Any_Speed

general reluctance to spend money on improving safety

Except in this case, it is not the manufacturers, but the drivers
failing to spend time catching up.

There is a general reluctance by many system administrators to
(a) comprehend that two decades of research has demonstrated the
unsoundness of resource record caching when doing
mixed authoritative + recursive
(b) because it can do do mixed mode, in practice BIND encourages
doing so
(c) in part, NSD and unbound were written to stop that practice
(d) Some of you are sticks in the mud, and deserve to get hurt.



Accessing USB with OpenBSD 5.7/amd64

2015-08-23 Thread Richard Thornton
When this test box, a Sempron 3400 begins to boot, USB is recognized:

OpenBSD 5.7 (RAMDISK_CD) #806: Sun Mar  8 11:08:49 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 3404660736 (3246MB)
avail mem = 3312402432 (3158MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf (53 entries)
bios0: vendor Phoenix Technologies, LTD version 3.13 date 11/15/2005
bios0: Compaq Presario 061 EL426AA-ABA SR1710NX NA611
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT SRAT MCFG APIC
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Sempron(tm) Processor 3400+, 1990.12 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 128KB 
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully 
associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully 
associative
cpu0: AMD erratum 89 present, BIOS upgrade may be required
cpu0: apic clock running at 198MHz
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P2P_)
acpiprt2 at acpi0: bus 1 (AGP_)
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10
ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pciide0 at pci0 dev 18 function 0 ATI SB400 SATA rev 0x00: DMA
pciide0: using apic 2 int 22 for native-PCI interrupt
pciide0: port 0: device present, speed: 1.5Gb/s
wd0 at pciide0 channel 0 drive 0: Maxtor 6L100M0
wd0: 16-sector PIO, LBA48, 95396MB, 195371568 sectors
wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5
ohci0 at pci0 dev 19 function 0 ATI SB400 USB rev 0x00: apic 2 int 18, 
version 1.0, legacy support
ohci1 at pci0 dev 19 function 1 ATI SB400 USB rev 0x00: apic 2 int 18, 
version 1.0, legacy support
ehci0 at pci0 dev 19 function 2 ATI SB400 USB2 rev 0x00: apic 2 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1
ATI SB400 SMBus rev 0x11 at pci0 dev 20 function 0 not configured
pciide1 at pci0 dev 20 function 1 ATI SB400 IDE rev 0x00: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide1 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: LITE-ON, COMBO SOHC-4836K, SPJ2 ATAPI 
5/cdrom removable
cd0(pciide1:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
ATI SB400 ISA rev 0x00 at pci0 dev 20 function 3 not configured
ppb1 at pci0 dev 20 function 4 ATI SB400 PCI rev 0x00
pci2 at ppb1 bus 2
rl0 at pci2 dev 3 function 0 Realtek 8139 rev 0x10: apic 2 int 21, 
address 00:15:f2:76:1d:d0
rlphy0 at rl0 phy 0: RTL internal PHY
VIA VT6306 FireWire rev 0x80 at pci2 dev 5 function 0 not configured
vendor Conexant, unknown product 0x2f20 (class communications subclass 
miscellaneous, rev 0x00) at pci2 dev 9 function 0 not configured
ATI SB400 AC97 rev 0x02 at pci0 dev 20 function 5 not configured
pchb1 at pci0 dev 24 function 0 AMD AMD64 0Fh HyperTransport rev 0x00
pchb2 at pci0 dev 24 function 1 AMD AMD64 0Fh Address Map rev 0x00
pchb3 at pci0 dev 24 function 2 AMD AMD64 0Fh DRAM Cfg rev 0x00
pchb4 at pci0 dev 24 function 3 AMD AMD64 0Fh Misc Cfg rev 0x00
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 ATI OHCI root hub rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 ATI OHCI root hub rev 1.00/1.00 addr 1
isa0 at mainbus0
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

But in the end, the USB appears diabled:

uhub1: device problem, disabling port 4
uhub2: device problem, disabling port 1
softraid0 at root
scsibus1 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
syncing disks... 


The hardware itself seems ok, since I have tried other OS's, Linux, as 
well as FreeBSD;  neither seemed to have issues with this particular 
system with USB.  I have searched on the OpenBSD docs for a obvious solution,
but nothing obvious is found.  To be sure, accesing USB is not that important 
to me, but I was curious, if there was some sort of boot parameter which I 
could set, in order to fully access the USB ports with OpenBSD.


Richard 



Re: Starting isc_named earlier

2015-08-23 Thread Edgar Pettijohn
something like this would probably do it, but would be undone anytime 
you update


--- /etc/rc Sat Aug 22 03:06:56 2015
+++ /etc/rc.new Sun Aug 23 12:27:53 2015
@@ -371,7 +371,7 @@
 make_keys

 echo -n 'starting early daemons:'
-start_daemon syslogd ldattach pflogd nsd unbound ntpd
+start_daemon syslogd ldattach pflogd isc_named ntpd
 start_daemon iscsid isakmpd iked sasyncd ldapd npppd
 echo '.'


On 08/23/15 12:00, George wrote:

Hi guys,

I was wondering if someone might have a hint on how to start isc_name
(on 5.7) earlier than network services like DHCP and NFS. This was OK
for me on 5.6 when it was in base but now I have issues as my configs
are tied to DNS services on the local machine.

I read a bit and fiddled with the rc code, getting failures there, ... I
am maybe not looking in the right place??

Any hints appreciated.
Regards,
George




Re: cdio(1) cdrip (error correction / why WAVE).

2015-08-23 Thread Geoff Steckel

On 08/23/2015 10:31 AM, n...@nawi.is wrote:

Hello !

I have here many audio cd's which I plan to rip - ripping with cdio(1)'s
cdrip works without problems. Now I ask myself, whether cdio(1) does some
error correction for scratched discs or, if the drive produces some errors
(like other tools promotes) ? The reason why I ask is, I want to rip and
don't want to control each disc after ripping (nothing like could another
tool had more or better functions). Or maybe this function is overrated
(for example if a lower speed is used to rip).

Audio CDs were designed with simple error correction assuming the
drive would interpolate data to conceal any missed samples.
Therefore ripping good data is difficult and error prone.
User intervention is often necessary.

I use cdparanoia to rip. In my experience it is the only program which
reliably returns the same data from a disc read on multiple occasions.
It attempts to defeat all error correction and concealment in the drive.
It then does all its own error correction and reports all instances of
non-perfect reads.

You will have to check the status output by cdparanoia for every disc.
Even using it, while ripping badly scratched discs I sometimes have
to slow to x4 or x2. It's possible you could write a script which
checked the status and re-ran cdparanoia at slower and slower speeds.

It is important to clean the discs very carefully before ripping.
The quality of the drive is very important. I use Samsung (Toshiba-Samsung)
or Pioneer drives. Also, drives wear out. After reading about 1000 discs
each, two drives failed without any obvious error indications. I had
to re-rip 100 discs on new drives.


Only curios, why is WAVE used to save the tracks and not AIFF (code,
license, portability ... ) ?
  No complain / flame because the target format
will be FLAC as it looks now.

Thanks for answers.


WAV is the format M$ used for uncompressed audio. AIFF was much
less widely implemented.

I use sox for all my format conversions. Simple  quick.
It accepts and writes many formats and does all the bulk
processing I need.

I hope this helps.

Geoff Steckel



Re: Starting isc_named earlier

2015-08-23 Thread George
On Sun, 23 Aug 2015 12:49:20 -0500
Edgar Pettijohn ed...@pettijohn-web.com wrote:

 On 08/23/15 12:40, Theo de Raadt wrote:
  something like this would probably do it, but would be undone
  anytime you update
 or at least I think it will be undone, but maybe not I don't have any 
 experience with making changes to it.
 
  --- /etc/rc Sat Aug 22 03:06:56 2015
  +++ /etc/rc.new Sun Aug 23 12:27:53 2015
  @@ -371,7 +371,7 @@
 make_keys
 
 echo -n 'starting early daemons:'
  -start_daemon syslogd ldattach pflogd nsd unbound ntpd
  +start_daemon syslogd ldattach pflogd isc_named ntpd
 start_daemon iscsid isakmpd iked sasyncd ldapd npppd
 echo '.'
 
 probably have to add something to /etc/rc.conf.local like 
 isc_named_flags=YES

Thanks for taking the time. FYI the 2 changes, above, did not work it
still fails starting. I shall look into moving to the other 2 when I
get the time.

Thank you both.

 
  On 08/23/15 12:00, George wrote:
  Hi guys,
 
  I was wondering if someone might have a hint on how to start
  isc_name (on 5.7) earlier than network services like DHCP and
  NFS. This was OK for me on 5.6 when it was in base but now I have
  issues as my configs are tied to DNS services on the local
  machine.
 
  I read a bit and fiddled with the rc code, getting failures
  there, ... I am maybe not looking in the right place??
  Or don't use ISC BIND.  Start your migrationg towards unbound / nsd,
  which are the new, safer toolkit for DNS.
 
  In my opinion, ISC BIND falls soundly into this catagory:
 
   https://en.wikipedia.org/wiki/Unsafe_at_Any_Speed
 As a former corvair owner I guarantee it was perfectly safe while
 parked.
 
  general reluctance to spend money on improving safety
 
  Except in this case, it is not the manufacturers, but the drivers
  failing to spend time catching up.
 
  There is a general reluctance by many system administrators to
   (a) comprehend that two decades of research has demonstrated
  the unsoundness of resource record caching when doing
   mixed authoritative + recursive
   (b) because it can do do mixed mode, in practice BIND
  encourages doing so
   (c) in part, NSD and unbound were written to stop that practice
   (d) Some of you are sticks in the mud, and deserve to get hurt.



Re: IPSec OpenBSD road warrior

2015-08-23 Thread bergers89
I did some further experiments and I think that i need gif/gre tunnels
between those two hosts.  But an additional problem is: How do I set up
such a tunnel when I have no static ip on my notebook (even behind a NAT
gateway) ? 



Re: Booting problem of my OpenBSD 5.7 road warrior

2015-08-23 Thread Stefan Sperling
On Sun, Aug 23, 2015 at 03:06:40PM +0800, Zhi-Qiang Lei wrote:
 My road warrior has a PPPoE external connection and a tunnel connection,
 established with OpenVPN, which would encrypt the packets from some special
 devices.
 
 It works so well so far with the help with these rules in /etc/pf.conf:
 
 pass in quick on $int_if from $arch to !internal_addresses route-to $tun_if
 pass in quick on $int_if from $raspbmc to external_addresses route-to
 $tun_if
 pass out quick on $tun_if from any to any nat-to ($tun_if)
 
 However, every time when I reboot the machine, pf fails to load the rules
 because the tunnel is not ready. The tunnel generally would take some minutes
 to establish. Is it possible to defer the loading of pf rules until all
 interfaces are ready? I also tried to parenthesize $tun_if, but it failed due
 to syntax errors.
 
 pass in quick on $int_if from $arch to !internal_addresses route-to
 ($tun_if)
 pass in quick on $int_if from $raspbmc to external_addresses route-to
 ($tun_if)
 pass out quick on $tun_if from any to any nat-to ($tun_if)
 
 Best regards and thanks,
 Zhi-Qiang Lei

If your local tun_if IP is static, you can set it in /etc/hostname.tun0
and then use persist-local-ip in openvpn's config file. That will allow
your pf rules to load on boot. OpenVPN will use the existing local IP.

If your local tun_if IP is dynamic, you could put an anchor in your
pf rule set:
  anchor openvpn/*
and then add rules to this anchor when openvpn comes up (e.g. from openvpn's
up script):
  printf 'pass in quick on $int_if from $arch to !internal_addresses route-to 
$tun_if\npass in quick on $int_if from $raspbmc to external_addresses 
route-to\n$tun_if\npass out quick on $tun_if from any to any nat-to 
($tun_if)\n' | pfctl -a openvpn/up -f -

Note the use of single quotes to prevent the shell from expanding $int_if etc.



Booting problem of my OpenBSD 5.7 road warrior

2015-08-23 Thread Zhi-Qiang Lei
My road warrior has a PPPoE external connection and a tunnel connection,
established with OpenVPN, which would encrypt the packets from some special
devices.

It works so well so far with the help with these rules in /etc/pf.conf:

pass in quick on $int_if from $arch to !internal_addresses route-to $tun_if
pass in quick on $int_if from $raspbmc to external_addresses route-to
$tun_if
pass out quick on $tun_if from any to any nat-to ($tun_if)

However, every time when I reboot the machine, pf fails to load the rules
because the tunnel is not ready. The tunnel generally would take some minutes
to establish. Is it possible to defer the loading of pf rules until all
interfaces are ready? I also tried to parenthesize $tun_if, but it failed due
to syntax errors.

pass in quick on $int_if from $arch to !internal_addresses route-to
($tun_if)
pass in quick on $int_if from $raspbmc to external_addresses route-to
($tun_if)
pass out quick on $tun_if from any to any nat-to ($tun_if)

Best regards and thanks,
Zhi-Qiang Lei



cdio(1) cdrip (error correction / why WAVE).

2015-08-23 Thread nawi
Hello !

I have here many audio cd's which I plan to rip - ripping with cdio(1)'s
cdrip works without problems. Now I ask myself, whether cdio(1) does some
error correction for scratched discs or, if the drive produces some errors
(like other tools promotes) ? The reason why I ask is, I want to rip and
don't want to control each disc after ripping (nothing like could another
tool had more or better functions). Or maybe this function is overrated
(for example if a lower speed is used to rip).

Only curios, why is WAVE used to save the tracks and not AIFF (code,
license, portability ... ) ? No complain / flame because the target format
will be FLAC as it looks now.

Thanks for answers.



Supermicro X9SBAA-F COM2 not working

2015-08-23 Thread Atanas Vladimirov

Hi,

This motherboard has 3 serial pors:
COM0 as header from WPCM450
COM1 which is internally connected as SOL (Serial-Over-LAN)
COM2 Fast 16550 UART COM port on the I/O back panel from S1260 as a PCI 
device.


COM0/1 are working:
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
com1: console

COM2 is not working:
Intel Atom S1200 UART rev 0x01 at pci0 dev 20 function 0 not 
configured


 # pcidump -v
 0:20:0: Intel Atom S1200 UART
0x: Vendor ID: 8086 Product ID: 0c5f
0x0004: Command: 0107 Status: 0010
0x0008: Class: 07 Subclass: 00 Interface: 02 Revision: 01
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line 
Size: 00

0x0010: BAR io addr: 0xf000/0x0008
0x0014: BAR mem 32bit addr: 0xfe48/0x0100
0x0018: BAR empty ()
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 15d9 Product ID: 0651
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
0x0040: Capability 0x05: Message Signaled Interrupts (MSI)
0x0050: Capability 0x01: Power Management

I found a dmesg from NetBSD[1]:

puc0 at pci0 dev 20 function 0: Intel S1200 UART (com)
com2 at puc0 port 0 (16550-compatible): ioaddr 0xf000, interrupting at 
ioapic0 pin 16

com2: ns16550a, working fifo
com2: console

If it would help I can boot FreeBSD or Linux(Debian?).

[1] http://dmesgd.nycbug.org/index.cgi?action=dmesgddo=viewid=2549

 dmesg is from GENERIC.MP with option XHCI_DEBUG because of a problem 
with usb3


OpenBSD 5.8-current (XHCI_DEBUG.MP) #0: Fri Aug 21 22:26:33 EEST 2015
vl...@ns.bsdbg.net:/sys/arch/amd64/compile/XHCI_DEBUG.MP
real mem = 4261285888 (4063MB)
avail mem = 4128247808 (3937MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe9510 (23 entries)
bios0: vendor American Megatrends Inc. version 1.1 date 04/29/2014
bios0: Supermicro X9SBAA
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SPMI EINJ ERST HEST BERT
acpi0: wakeup devices PRP4(S1)
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) Atom(TM) CPU S1260 @ 2.00GHz, 1995.22 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,

SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2.0.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU S1260 @ 2.00GHz, 1995.00 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,

SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xc000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PRP1)
acpiprt2 at acpi0: bus 2 (PRP2)
acpiprt3 at acpi0: bus 4 (P3P4)
acpicpu0 at acpi0: C1(1000@20 halt), PSS
acpicpu1 at acpi0: C1(1000@20 halt), PSS
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 175 degC
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
ipmi at mainbus0 not configured
cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1900, 1800, 1700, 1600, 
1500, 1400, 1300, 1200, 1100, 1000, 900, 800, 700, 6

00 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Atom S1260 Host rev 0x01
ppb0 at pci0 dev 1 function 0 Intel Atom S1200 PCIE rev 0x01
pci1 at ppb0 bus 1
ahci0 at pci1 dev 0 function 0 Marvell 88SE9230 AHCI rev 0x10: msi, 
AHCI 1.2

ahci0: port 0: 6.0Gb/s
ahci0: port 2: 3.0Gb/s
ahci0: port 7: 1.5Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: ATA, ST3160316AS, JC4B SCSI3 0/direct 
fixed naa.5000c50040390431

sd0: 152627MB, 512 bytes/sector, 312581808 sectors
sd1 at scsibus1 targ 2 lun 0: ATA, HDT722516DLA380, V43O SCSI3 
0/direct fixed naa.5000cca205ddd62d

sd1: 157066MB, 512 bytes/sector, 321672960 sectors
uk0 at scsibus1 targ 7 lun 0: Marvell, Console, 1.01 ATAPI 3/processor 
removable

ppb1 at pci0 dev 2 function 0 Intel Atom S1200 PCIE rev 0x01
pci2 at ppb1 bus 2
xhci0 at pci2 dev 0 function 0 Renesas uPD720201 xHCI rev 0x03: msi
xhci0: xHCI version 1.0
xhci0: CAPLENGTH=0x20
xhci0: DOORBELL=0x800
xhci0: 

Re: Supermicro X9SBAA-F COM2 not working

2015-08-23 Thread Atanas Vladimirov

On 24.08.2015 01:22, Atanas Vladimirov wrote:

Hi,

This motherboard has 3 serial pors:
COM0 as header from WPCM450
COM1 which is internally connected as SOL (Serial-Over-LAN)
COM2 Fast 16550 UART COM port on the I/O back panel from S1260 as a PCI 
device.


COM0/1 are working:
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
com1: console

COM2 is not working:
Intel Atom S1200 UART rev 0x01 at pci0 dev 20 function 0 not 
configured


 Theo made me happy :)
 Thanks.
 http://marc.info/?l=openbsd-cvsm=144037187832235w=2



Re: cdio(1) cdrip (error correction / why WAVE).

2015-08-23 Thread Geoff Steckel
On 08/23/2015 05:03 PM, Christian Weisgerber wrote:
 On 2015-08-23, n...@nawi.is n...@nawi.is wrote:

 (like other tools promotes) ? The reason why I ask is, I want to rip and
 don't want to control each disc after ripping (nothing like could another
 tool had more or better functions). Or maybe this function is overrated
 There are tools in ports, notably audio/cdparanoia, that claim to
 go through great effort to add extra-robust data verification,
 synchronization, error handling and scratch reconstruction capability.

 That was important in the 1990s, but I don't know if it actually
 makes any sense or even works with modern drives.

(Some) Modern drives are much better than older ones.

However, the extremely variable quality of CD pressing and the
widespread use of CD-R to distribute short runs instead
of paying for a master has made the job of reading the disc harder.
Damage to discs from air pollution and salt spray is still
a problem.

Cdparanoia reads the raw data stream before high-level error correction
in the drive. That's available on (almost) every modern drive.
The actual RF stream as eight-to-14 modulated bits is not
available on any drive I've heard of. The decoded subframes are available
on some drives but cdparanoia doesn't process them.

By performing the low level processing it can presumably
do somewhat better error correction than the drives. Most importantly,
it can report cases where the drive would mask errors by
replacing the bad data with interpolated (stuff). It also rereads
any sector in error and does overlapped reads to be sure no
data has been lost between reads. In some cases, drives duplicate
data which is also detected.

I strongly recommend cdparanoia as the best cd-audio reading
program I've found. There may be ones (as above) which reach down
yet another level. I've found that using a good drive (good
manufacture and not used to death) only 1 out of 750 of
my random collection of discs can't be read successfully.

Geoff Steckel



Re: Start isc_named earlier

2015-08-23 Thread Richard Thornton
‎I see from the output usbdevs - vd that all the USB ports are seen. It must be 
something simple, will continue researching it.

Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
  Original Message  
From: g.lis...@nodeunit.com
Sent: Sunday, August 23, 2015 12:56 PM
To: secularsolutions...@gmail.com
Subject: Re: Start isc_named earlier

I am really sorry, but don't. .. I was hijacking your message to right a new 
question and then i happened to move my finger the wrong way and boom 
send...

Sorry

On Sun Aug 23 18:47:32 2015 GMT+0200, Richard Thornton wrote:
 OK will try that.
 
 Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
 Original Message 
 From: g.lis...@nodeunit.com
 Sent: Sunday, August 23, 2015 12:18 PM
 To: misc@openbsd.org
 Cc: misc@openbsd.org
 Subject: Start isc_named earlier
 
 On Sun Aug 23 15:40:57 2015 GMT+0200, Richard Thornton wrote:
  When this test box, a Sempron 3400 begins to boot, USB is recognized:
  
  OpenBSD 5.7 (RAMDISK_CD) #806: Sun Mar 8 11:08:49 MDT 2015
  dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
  real mem = 3404660736 (3246MB)
  avail mem = 3312402432 (3158MB)
  mainbus0 at root
  bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf (53 entries)
  bios0: vendor Phoenix Technologies, LTD version 3.13 date 11/15/2005
  bios0: Compaq Presario 061 EL426AA-ABA SR1710NX NA611
  acpi0 at bios0: rev 0
  acpi0: sleep states S0 S1 S3 S4 S5
  acpi0: tables DSDT FACP SSDT SRAT MCFG APIC
  acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
  cpu0 at mainbus0: apid 0 (boot processor)
  cpu0: AMD Sempron(tm) Processor 3400+, 1990.12 MHz
  cpu0: 
  FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF
  cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 128KB 
  64b/line 16-way L2 cache
  cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully 
  associative
  cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully 
  associative
  cpu0: AMD erratum 89 present, BIOS upgrade may be required
  cpu0: apic clock running at 198MHz
  ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
  acpiprt0 at acpi0: bus 0 (PCI0)
  acpiprt1 at acpi0: bus 2 (P2P_)
  acpiprt2 at acpi0: bus 1 (AGP_)
  pci0 at mainbus0 bus 0
  pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10
  ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00
  pci1 at ppb0 bus 1
  vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00
  wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
  pciide0 at pci0 dev 18 function 0 ATI SB400 SATA rev 0x00: DMA
  pciide0: using apic 2 int 22 for native-PCI interrupt
  pciide0: port 0: device present, speed: 1.5Gb/s
  wd0 at pciide0 channel 0 drive 0: Maxtor 6L100M0
  wd0: 16-sector PIO, LBA48, 95396MB, 195371568 sectors
  wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5
  ohci0 at pci0 dev 19 function 0 ATI SB400 USB rev 0x00: apic 2 int 18, 
  version 1.0, legacy sup 
 


-- 



Re: cdio(1) cdrip (error correction / why WAVE).

2015-08-23 Thread Liviu Daia
On 23 August 2015, Geoff Steckel g...@oat.com wrote:
[...]
 Also, drives wear out. After reading about 1000 discs each, two drives
 failed without any obvious error indications.
[...]

After reading about 1000 discs, chances are the lens in your drive
has gathered dust.  You can try to clean it gently with isopropyl
alcohol or similar.

Regards,

Liviu Daia



Re: cdio(1) cdrip (error correction / why WAVE).

2015-08-23 Thread Christian Weisgerber
On 2015-08-23, n...@nawi.is n...@nawi.is wrote:

 I have here many audio cd's which I plan to rip - ripping with cdio(1)'s
 cdrip works without problems. Now I ask myself, whether cdio(1) does some
 error correction for scratched discs or, if the drive produces some errors

cdio does not perform any error correction.  It simply asks the drive
for the data and accepts what it gets.

 (like other tools promotes) ? The reason why I ask is, I want to rip and
 don't want to control each disc after ripping (nothing like could another
 tool had more or better functions). Or maybe this function is overrated

There are tools in ports, notably audio/cdparanoia, that claim to
go through great effort to add extra-robust data verification,
synchronization, error handling and scratch reconstruction capability.

That was important in the 1990s, but I don't know if it actually
makes any sense or even works with modern drives.

 Only curios, why is WAVE used to save the tracks and not AIFF (code,
 license, portability ... ) ?

Because WAV is the most commonly used interchange format for
uncompressed audio and, as typically used, is really simple: It
just adds a minimal header in front of the raw audio data.

-- 
Christian naddy Weisgerber  na...@mips.inka.de



Re: Starting isc_named earlier

2015-08-23 Thread Stuart Henderson
On 2015-08-23, George g.lis...@nodeunit.com wrote:
  -start_daemon syslogd ldattach pflogd nsd unbound ntpd
  +start_daemon syslogd ldattach pflogd isc_named ntpd
 start_daemon iscsid isakmpd iked sasyncd ldapd npppd
 echo '.'
 
 probably have to add something to /etc/rc.conf.local like 
 isc_named_flags=YES

 Thanks for taking the time. FYI the 2 changes, above, did not work it
 still fails starting. I shall look into moving to the other 2 when I
 get the time.

isc_named needs to start after ldconfig, which is too late for the things
you ask about. 

You could use unbound as resolver, even if it's just on localhost. If it
needs to resolve a name that BIND is authoritative for before BIND starts,
it'll just query your other NS instead.

  I was wondering if someone might have a hint on how to start
  isc_name (on 5.7) earlier than network services like DHCP and
  NFS. This was OK for me on 5.6 when it was in base but now I have
  issues as my configs are tied to DNS services on the local
  machine.

Having NFS rely on DNS is not ideal. I don't see why dhcpd would
need DNS to run at all?



Re: Video card detected but does not initialize leading to black display during kernel probing

2015-08-23 Thread Research
Hi,

As a follow-up on my original e-mail (please see below for original message), I 
noticed an e-mail in this list from Gautam Goel that described a similar 
situation with Radeon video cards.  I followed the instructions from Gerald 
Hanuer and have a functional solution to my problem.

In case anyone else is dealing with Radeon graphic cards or installing OpenBSD 
onto a similar iMac, I’ve listed the steps I took below.

My first attempt was to use “boot -c” and “disable radeondrm” and “quit” from 
the kennel config as per Gautam’s e-mail.  In my case, this didn’t work - when 
I would get to the kernel config prompt, no text I entered would display and 
typing the commands in blindly did not work.  For whatever reason, text input 
via keyboard did not work.

As per Gerald’s e-mail, I manually downloaded firmware from OpenBSD.org for 
Radeon hardware 
(http://firmware.openbsd.org/firmware/5.7/radeondrm-firmware-20131002p0.tgz).  
I then ssh’ed into the iMac, mounted a USB thumb drive that I had copied the 
driver to and then ran “sudo fw_update -p /path/to/copied/firmware”.  I ran 
“sudo fw_update -i” to check if anything else was required and discovered that 
I needed another piece of firmware 
(http://firmware.openbsd.org/firmware/5.7/uvideo-firmware-1.2p1.tgz).  I 
followed the same procedure again and rebooted the iMac via SSH.

Thank you Gautam and Gerald, for your e-mail’s to the list!



On Aug 23, 2015, at 1:27 AM, Research resea...@nativemethods.com wrote:

 Hello,
 
 Recently I install OpenBSD 5.7 (amd64) on a iMac 12, 1 (15” iMac from 2011).  
 I applied all 5.7 errata and am current as of August 23, 2015.
 
 The full dmesg follows this -email, but a snippet shows the kernel is having 
 trouble with the video card:
 
 
 error: [drm:pid0:ni_init_microcode] *ERROR* ni_cp: Failed to load firmware 
 radeon-turks_pfp
 error: [drm:pid0:evergreen_startup] *ERROR* Failed to load firmware!
 drm:pid0:evergreen_init *ERROR* disabling GPU acceleration
 drm:pid0:radeon_bo_unpin *WARNING* 0xff026eb6e2b0 unpin not necessary
 drm:pid0:radeon_bo_unpin *WARNING* 0xff026eb6e2b0 unpin not necessary
 error: [drm:pid0:evergreen_init] *ERROR* radeon: MC ucode required for NI+.
 drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU init
 radeon_hwmon_fini stub
 ttm_pool_mm_shrink_fini stub
 drm0 detached
 radeondrm0 detached
 vga1 at pci1 dev 0 function 0 ATI Radeon HD 6600M rev 0x00
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation), using wskbd0
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 
 
 On the first line I noticed “Failed to load firmware” in relation to the 
 video card (ATI Radeon HD 6600M).
 
 My questions are:
 
 1. Is a firmware blob needed that I must acquire and then provide to the 
 kernel ?
 
 2. In a worst case scenario, can I configure the kernel to not probe the 
 video card and stick with the standard
 VGA output ?  The video works when booting from the install RAM disk and 
 while there is not a lot of room
 for displaying text, it’s still more usable in that state.
 
 DMESG follows
 =-=-=-=-=-=-=-=
 
 
 OpenBSD 5.7 (GENERIC.MP) #2: Sat Aug 22 22:22:41 EDT 2015
 
 RTC BIOS diagnostic error 64ROM_cksum,config_unit,invalid_time
 real mem = 8548204544 (8152MB)
 avail mem = 8316731392 (7931MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (61 entries)
 bios0: vendor Apple Inc. version IM121.88Z.0047.B21.1506101610 date 06/10/15
 bios0: Apple Inc. iMac12,1
 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 SSDT SSDT SSDT
 acpi0: wakeup devices P0P2(S4) GFX0(S4) EC__(S4) HDEF(S4) GIGE(S4) RP01(S4) 
 ARPT(S4) RP02(S4) RP03(S4) RP05(S4) EHC1(S3) EHC2(S3)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpihpet0 at acpi0: 14318179 Hz
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.41 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,NXE,LONG,LAHF,PERF,ITSC
 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.1.0, IBE
 cpu1 at mainbus0: apid 2 (application processor)
 cpu1: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.02 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,NXE,LONG,LAHF,PERF,ITSC
 cpu1: 256KB 64b/line 8-way L2 cache
 cpu1: smt 0,