Error booting OpenBSD 5.5 on Macbook Air

2014-06-09 Thread Anders Jensen-Waud
Hello, 

I am trying to boot OpenBSD 5.5 (amd64) from an SD memory card on my Macbook 
Air (most recent model).

When I boot from the SD card (both bsd and bsd.mp) the boot process hangs at 
“root device: “

The SSD drive in the machine is identified as sd0 upon boot. The OpenBSD boot 
loader identifies both hd0 and hd1. I also tried asking the kernel to ASK for a 
root device by issuing: boot hd0a:/bsd.mp -a, but with no luck. 

Any ideas how I can boot from this card successfully? 

Cheers

Anders

(Note: I created the OpenBSD installation by mounting the SD card in VirtualBox 
on Mac OS X and then installing OpenBSD onto it inside the VM. The installation 
wen fine.)



Re: Radeondrm on OpenBSD 5.5 stable

2014-06-09 Thread Jonathan Gray
On Sun, Jun 08, 2014 at 07:01:56AM -0500, Stan Gammons wrote:
 Is there a known problem with the Radeon driver on OpenBSD 5.5 AMD64 
 stable?   I noticed the text on the console was scrolling very slow 
 while src.tar.gz was extracting.  I didn't time it, but it seem to take 
 2 to 3 times as long to return to the command line compared to 
 extracting the same file on a slower i386 machine.   Syslog output is below.

Well things are going to be slow when all the acceleration is being
disabled.  It isn't clear if the problem you're encountering is
due to something like missing firmware as you didn't include a dmesg.

 
 
 
 Jun  7 22:47:09 gateway /bsd: radeondrm0: VRAM: 128M 0xD000 
 - 0xD7FF (128M used)
 Jun  7 22:47:09 gateway /bsd: radeondrm0: GTT: 512M 0xA000 - 
 0xBFFF
 Jun  7 22:47:09 gateway /bsd: drm: PCIE GART of 512M enabled (table at 
 0x0891F000).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_ring_test] *ERROR* 
 radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_init] *ERROR* 
 radeon: cp isn't working (-22).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:rs690_startup] *ERROR* 
 failed initializing CP (-22).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:rs690_init] *ERROR* 
 Disabling GPU acceleration
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_fini] *ERROR* 
 Wait for CP idle timeout, shutting down CP.
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_gui_wait_for_idle] 
 *ERROR* radeon: wait for empty RBBM fifo failed ! Bad things might happen.
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_disable] *ERROR* 
 Failed to wait GUI idle while programming pipes. Bad things might happen.
 Jun  7 22:47:09 gateway /bsd: drm: radeon: cp finalized
 Jun  7 22:47:09 gateway /bsd: radeondrm0: 1600x900
 Jun  7 22:47:09 gateway /bsd: wsdisplay0 at radeondrm0 mux 1: console 
 (std, vt100 emulation), using wskbd0
 Jun  7 22:47:09 gateway /bsd: wsdisplay0: screen 1-5 added (std, vt100 
 emulation)Jun  7 22:47:09 gateway /bsd: radeondrm0: VRAM: 128M 
 0xD000 - 0xD7FF (128M used)
 Jun  7 22:47:09 gateway /bsd: radeondrm0: GTT: 512M 0xA000 - 
 0xBFFF
 Jun  7 22:47:09 gateway /bsd: drm: PCIE GART of 512M enabled (table at 
 0x0891F000).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_ring_test] *ERROR* 
 radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_init] *ERROR* 
 radeon: cp isn't working (-22).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:rs690_startup] *ERROR* 
 failed initializing CP (-22).
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:rs690_init] *ERROR* 
 Disabling GPU acceleration
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_fini] *ERROR* 
 Wait for CP idle timeout, shutting down CP.
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_gui_wait_for_idle] 
 *ERROR* radeon: wait for empty RBBM fifo failed ! Bad things might happen.
 Jun  7 22:47:09 gateway /bsd: error: [drm:pid0:r100_cp_disable] *ERROR* 
 Failed to wait GUI idle while programming pipes. Bad things might happen.
 Jun  7 22:47:09 gateway /bsd: drm: radeon: cp finalized
 Jun  7 22:47:09 gateway /bsd: radeondrm0: 1600x900
 Jun  7 22:47:09 gateway /bsd: wsdisplay0 at radeondrm0 mux 1: console 
 (std, vt100 emulation), using wskbd0
 Jun  7 22:47:09 gateway /bsd: wsdisplay0: screen 1-5 added (std, vt100 
 emulation)



Re: Error booting OpenBSD 5.5 on Macbook Air

2014-06-09 Thread Anders Østergaard Jensen-Waud
Note: I would like to provide a dmesg, but am not sure how to do this
when the system cannot boot successfully.

I took a photo of the boot screen with my phone, which is shown here:

https://www.dropbox.com/s/7ne9jpx8vja2rck/2014-06-09%2015.55.27.jpg

On Mon, Jun 9, 2014 at 4:01 PM, Anders Jensen-Waud aojen...@gmail.com wrote:
 Hello,

 I am trying to boot OpenBSD 5.5 (amd64) from an SD memory card on my Macbook 
 Air (most recent model).

 When I boot from the SD card (both bsd and bsd.mp) the boot process hangs at 
 “root device: “

 The SSD drive in the machine is identified as sd0 upon boot. The OpenBSD boot 
 loader identifies both hd0 and hd1. I also tried asking the kernel to ASK for 
 a root device by issuing: boot hd0a:/bsd.mp -a, but with no luck.

 Any ideas how I can boot from this card successfully?

 Cheers

 Anders

 (Note: I created the OpenBSD installation by mounting the SD card in 
 VirtualBox on Mac OS X and then installing OpenBSD onto it inside the VM. The 
 installation wen fine.)



-- 
Best regards,

Anders Jensen-Waud
E-mail: aojen...@gmail.com
Phone: +61 478 320 664



Re: Error booting OpenBSD 5.5 on Macbook Air

2014-06-09 Thread Alexander Polakov
* Anders Østergaard Jensen-Waud aojen...@gmail.com [140609 08:58]:
 Note: I would like to provide a dmesg, but am not sure how to do this
 when the system cannot boot successfully.
 
 I took a photo of the boot screen with my phone, which is shown here:
 
 https://www.dropbox.com/s/7ne9jpx8vja2rck/2014-06-09%2015.55.27.jpg
 
 On Mon, Jun 9, 2014 at 4:01 PM, Anders Jensen-Waud aojen...@gmail.com wrote:
  Hello,
 
  I am trying to boot OpenBSD 5.5 (amd64) from an SD memory card on my 
  Macbook Air (most recent model).
 
  When I boot from the SD card (both bsd and bsd.mp) the boot process hangs 
  at “root device: “
 
  The SSD drive in the machine is identified as sd0 upon boot. The OpenBSD 
  boot loader identifies both hd0 and hd1. I also tried asking the kernel to 
  ASK for a root device by issuing: boot hd0a:/bsd.mp -a, but with no luck.
 
  Any ideas how I can boot from this card successfully?
 
  Cheers
 
  Anders
 
  (Note: I created the OpenBSD installation by mounting the SD card in 
  VirtualBox on Mac OS X and then installing OpenBSD onto it inside the VM. 
  The installation wen fine.)

It is probably the same problem I'm having on Macbook Pro (late 13): all
usb ports are USB3 on this device, and usb3 is not yet supported by
openbsd. You can try enabling xhci* by compiling custom kernel, but it's
still experimental and probably would not work (I've tried, no luck).

-- 
Alexander Polakov | plhk.ru



keyboard layout on macppc

2014-06-09 Thread luca suriano
I have just installed OpenBSD 5.5 on ibook G3 12'' 800Mhz.

My problem is italian keyboard layout.

$ wsconsctl encoding=it
wsconsctl: encoding it: no such variable

I don't understand why, on i386 and amd64 works well, I have problems only on 
macppc arch.

Many thanks.

-- 
Information wants to be free



Re: keyboard layout on macppc

2014-06-09 Thread Zé Loff
On Mon, Jun 09, 2014 at 02:12:05PM +0200, luca suriano wrote:
 I have just installed OpenBSD 5.5 on ibook G3 12'' 800Mhz.
 
 My problem is italian keyboard layout.
 
 $ wsconsctl encoding=it
 wsconsctl: encoding it: no such variable

I think this should be 'keyboard.encoding', not just 'encoding'.

-- 



Re: keyboard layout on macppc

2014-06-09 Thread luca suriano
* - 13:26:02 (Monday 09 June 2014)
* - Zé Loff:

  $ wsconsctl encoding=it
  wsconsctl: encoding it: no such variable
 I think this should be 'keyboard.encoding', not just 'encoding'.

I tried but it doesn't work.

$ wsconsctl keyboard.encoding=it
wsconsctl: WSKBDIO_SETENCODING: Invalid argument

-- 
Information wants to be free



Re: keyboard layout on macppc

2014-06-09 Thread bodie

On 09.06.2014 14:43, luca suriano wrote:

* - 13:26:02 (Monday 09 June 2014)
* - Zé Loff:


 $ wsconsctl encoding=it
 wsconsctl: encoding it: no such variable
I think this should be 'keyboard.encoding', not just 'encoding'.


I tried but it doesn't work.

$ wsconsctl keyboard.encoding=it
wsconsctl: WSKBDIO_SETENCODING: Invalid argument


Try kbd -l just to see what's available. Because looking
here 
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/wsconsctl/keysym.c?rev=1.7

I can see that IT is not present in base system. Of course
you can still switch to IT in X with setxkbmap



Re: keyboard layout on macppc

2014-06-09 Thread Mats O Jansson
On Mon, 9 Jun 2014, bodie wrote:

 On 09.06.2014 14:43, luca suriano wrote:
  * - 13:26:02 (Monday 09 June 2014)
  * - Zé Loff:
  
$ wsconsctl encoding=it
wsconsctl: encoding it: no such variable
   I think this should be 'keyboard.encoding', not just 'encoding'.
  
  I tried but it doesn't work.
  
  $ wsconsctl keyboard.encoding=it
  wsconsctl: WSKBDIO_SETENCODING: Invalid argument
 
 Try kbd -l just to see what's available. Because looking
 here http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/wsconsctl/keysym.c?rev=1.7
 I can see that IT is not present in base system. Of course
 you can still switch to IT in X with setxkbmap

You can see that IT is not present in base system? Don't drive a car!

IT is present. see 
http://.openbsd.org/cgi-bin/cvsweb/src/sys/dev/wscons/wsksymdef.h?rev=1.36

The following is my guess since i havn't seen a dmesg:

The computer has the keyboard hanging on adb, and adb keyboard driver 
doesn't have an IT layout. The later verified.

-moj



Re: keyboard layout on macppc

2014-06-09 Thread luca suriano
* - 16:50:39 (Monday 09 June 2014)
* - Mats O Jansson:

[...]
 You can see that IT is not present in base system? Don't drive a car!
 
 IT is present. see 
 http://.openbsd.org/cgi-bin/cvsweb/src/sys/dev/wscons/wsksymdef.h?rev=1.36
 
 The following is my guess since i havn't seen a dmesg:
 
 The computer has the keyboard hanging on adb, and adb keyboard driver 
 doesn't have an IT layout. The later verified.

Now I'm a little bit confused, I don't understand if there is a way to
set up Italian keyboard layout.

There is akbd Apple Keyboard Device and an item is Apple ibook
Keyboard, can i use it for my purpose? 

-- 
Information wants to be free



Re: Radeondrm on OpenBSD 5.5 stable

2014-06-09 Thread Stan Gammons

On 06/09/2014 01:56 AM, Jonathan Gray wrote:

On Sun, Jun 08, 2014 at 07:01:56AM -0500, Stan Gammons wrote:

Is there a known problem with the Radeon driver on OpenBSD 5.5 AMD64
stable?   I noticed the text on the console was scrolling very slow
while src.tar.gz was extracting.  I didn't time it, but it seem to take
2 to 3 times as long to return to the command line compared to
extracting the same file on a slower i386 machine.   Syslog output is below.

Well things are going to be slow when all the acceleration is being
disabled.  It isn't clear if the problem you're encountering is
due to something like missing firmware as you didn't include a dmesg.




It loads or tries to load firmware at boot.

Here's the dmesg info.


OpenBSD 5.5 (GENERIC.MP) #0: Sat Jun  7 22:45:43 CDT 2014
r...@gateway.home.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4141809664 (3949MB)
avail mem = 4022943744 (3836MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (52 entries)
bios0: vendor Award Software International, Inc. version FK date 
08/31/2010

bios0: Gigabyte Technology Co., Ltd. GA-MA74GM-S2
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) 
USB5(S3) USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) 
PCE6(S4) PCE7(S4) PCE8(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) II X2 250 Processor, 3021.32 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully 
associative
cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully 
associative

cpu0: AMD erratum 721 detected and fixed
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 201MHz
cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) II X2 250 Processor, 3020.91 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully 
associative
cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully 
associative

cpu1: AMD erratum 721 detected and fixed
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (P2P_)
acpiprt2 at acpi0: bus 2 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus -1 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE8)
acpiprt9 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpibtn0 at acpi0: PWRB
cpu0: 3021 MHz: speeds: 3000 2300 1800 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 ATI RS740 Host rev 0x00
ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 ATI Radeon 2100 rev 0x00
drm0 at radeondrm0
radeondrm0: apic 2 int 18
ppb1 at pci0 dev 2 function 0 ATI RS690M PCIE rev 0x00: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 Intel 82571EB rev 0x06: apic 2 int 18, 
address 00:15:17:cd:db:42
em1 at pci2 dev 0 function 1 Intel 82571EB rev 0x06: apic 2 int 19, 
address 00:15:17:cd:db:43
ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 
22, AHCI 1.1

scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: ATA, Maxtor 7Y250M0, YAR5 SCSI3 0/direct 
fixed t10.ATA_Maxtor_7Y250M0_Y64Y10TE_

sd0: 239372MB, 512 bytes/sector, 490234752 sectors
sd1 at scsibus0 targ 1 lun 0: ATA, Maxtor 6Y250M0, YAR5 SCSI3 0/direct 
fixed t10.ATA_Maxtor_6Y250M0_Y64DMDWE_

sd1: 239371MB, 512 bytes/sector, 490232639 sectors
cd0 at scsibus0 targ 2 lun 0: HL-DT-ST, DVDRAM GH24NS95, RN01 ATAPI 
5/cdrom removable
ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 16, 
version 1.0, legacy support
ohci1 at pci0 dev 18 function 1 ATI SB700 USB rev 0x00: apic 2 int 16, 
version 1.0, legacy support

ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 ATI EHCI root hub rev 

Re: issues with amd64 on Apple MacPro

2014-06-09 Thread Allan Streib
bodie bodz...@openbsd.cz writes:

 Is your user in staff in /etc/login.conf ?

Yes, userinfo: 

login   astreib
passwd  
uid 1000
groups  astreib wheel
change  NEVER
class   staff
gecos   Allan Streib
dir /home/astreib
shell   /bin/ksh
expire  NEVER

 What's your ulimit -a output?

time(cpu-seconds)unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 524288
stack(kbytes)4096
lockedmem(kbytes)3391926
memory(kbytes)   10174016
nofiles(descriptors) 512
processes128

Thanks,

Allan



Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread opendaddy
On 5. mars 2014 at 5:11 PM, Peter N. M. Hansteen  wrote:

 [...snip...]

 So here's your chance! A good article could earn you undeadly.org
fame and megabytes of fan mail!

I'll get started right away!

O.D.

On 5. mars 2014 at 5:11 PM, Peter N. M. Hansteen 
wrote:openda...@hushmail.com writes:

 Anybody have any thoughts on how to achieve this?

Speed is desirable, of course, at least to some degree. I for one
would appreciate much if somebody beat me to writing a well researched
article about how to optimize OpenBSD as it is *right now* for desktop
wonderfulness.  

The reason I say this is after mucking about quite a bit with more or
less relevant settings (on my by now four years old laptop) in order
to get back some of the performance lost to endless code bloat in
windowing environments, desktop suites, browsers and websites, I was
at least a bit relieved to find yesterday evening that tweaking some
settings in login.conf actually had enough effect that I consider the
machine mostly usable again.

There's bound to be quite a few other things you can do, but digging
deep enough is almost certain to be time consuming enough that I'm
likely to postpone doing further research or a writeup until my now
relatively usable system has helped me finish a few delayed tasks.

So here's your chance! A good article could earn you undeadly.org fame
and megabytes of fan mail!

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673
seconds.



Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic

2014-06-09 Thread Mattieu Baptiste
Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a écrit :
 I know it’s no consolation to you but using a Kingston 30 GB mSATA from
amazon works perfectly. The APU is on the May bios and I’ve had no issues.

 Didn’t the PCEngines mSATA drive have problems in general? There’s a
mention on here about issues with the a version - is that yours?
http://pcengines.ch/msata16b.htm

Theoritically, I should have the new firmware (that's what told my vendor).
But it seems there are still problems with these.

Thanks for the tip concerning the Kingston drive.



Re: keyboard layout on macppc

2014-06-09 Thread Mats O Jansson
On Mon, 9 Jun 2014, luca suriano wrote:

 Now I'm a little bit confused, I don't understand if there is a way to
 set up Italian keyboard layout.
 
 There is akbd Apple Keyboard Device and an item is Apple ibook
 Keyboard, can i use it for my purpose? 

Yes, set encoding to e.g. US. Modify keyboard.map with wsconsctl as shown 
by the man page. Do it as a script so you can redo it when ever needed.

wsconsctl keyboard.map will show the current map.

When you have something useful it would be easy to convert it to the 
internal keyboard map format in sys/dev/adb/akbdmap.h. Most large maps 
starts with US and modifies it.

-moj
 
 -- 
 Information wants to be free



Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread Allan Streib
openda...@hushmail.com writes:

 Speed is desirable, of course, at least to some degree. I for one
 would appreciate much if somebody beat me to writing a well researched
 article about how to optimize OpenBSD as it is *right now* for desktop
 wonderfulness.  

Hear hear. For a desktop I want something that's stable, consistent, and
secure more than I care about squeezing out every bit of theoretical
performance.

 There's bound to be quite a few other things you can do, but digging
 deep enough is almost certain to be time consuming enough that I'm
 likely to postpone doing further research or a writeup until my now
 relatively usable system has helped me finish a few delayed tasks.

Can you share what you changed in login.conf, and what problems were
resolved as a result?

Allan



Dear undeadly.org admins

2014-06-09 Thread misc nick
Thank you for maintaining for so many years OpenBSD's official news site. 
I understand that you are not paid for the time you have dedicated.

That being said, please fix the fucking archive search. I know i can
use google to search undeadly. However, nobody should have to.
In addition, when the official OpenBSD news site is broken, 
it makes the OpenBSD project look broken too. And it's a pity
because OpenBSD is far from broken.



Re: Dear undeadly.org admins

2014-06-09 Thread Giancarlo Razzolini
Em 09-06-2014 15:05, misc nick escreveu:
 Thank you for maintaining for so many years OpenBSD's official news site. 
 I understand that you are not paid for the time you have dedicated.

 That being said, please fix the fucking archive search. I know i can
 use google to search undeadly. However, nobody should have to.
 In addition, when the official OpenBSD news site is broken, 
 it makes the OpenBSD project look broken too. And it's a pity
 because OpenBSD is far from broken.

Why, instead of whine about it, won't you volunteer? On the about page
they say you can send an e-mail to edit...@undeadly.org

Also, OpenBSD do not look broken whatever happens to undeadly. They are
separate things.

Cheers,

-- 
Giancarlo Razzolini
GPG: 4096R/77B981BC



Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic

2014-06-09 Thread Andre Keller
Hi Matthieu,

On 09.06.2014 19:30, Mattieu Baptiste wrote:
 Thanks for the tip concerning the Kingston drive. 

fwiw, I'm running april 5th firmware (I'm not aware of any may firmware,
probably a confusion about date format, http://xkcd.com/1179/ ftw.)
using a kingston SMS200S3/30G without any issues.

hth
andre



Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic

2014-06-09 Thread Liviu Daia
On 9 June 2014, Mattieu Baptiste mattie...@gmail.com wrote:
 Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit :
[...]
  Didn???t the PCEngines mSATA drive have problems in
  general? There???s a mention on here about issues with the a version
  - is that yours? http://pcengines.ch/msata16b.htm

 Theoritically, I should have the new firmware (that's what told my
 vendor).

You do, according to the dmesg you posted in your first message.

 But it seems there are still problems with these.
[...]

This time it's the particular model of the disk shipped by PCEngines
that has problems, not the firmware.  A quick search reveals that many
other people had to replace it with something else.  Just make sure to
search before you buy.

Regards,

Liviu Daia



OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread wessels
Several systems need a newer version of OpenBSD. Systems are Alix 2d with
an AMD Geode, a bit dated but it works.
Current systems run OpenBSD 4.4 and the hardware acceleration via glxsb
works perfectly:
# openssl speed -evp aes-128-cbc -engine cryptodev
engine cryptodev set.
To get the most accurate results, try to run this
program when this computer is idle.
Doing aes-128-cbc for 3s on 16 size blocks: 174939 aes-128-cbc's in 0.19s
Doing aes-128-cbc for 3s on 64 size blocks: 164809 aes-128-cbc's in 0.23s
Doing aes-128-cbc for 3s on 256 size blocks: 132123 aes-128-cbc's in 0.14s
Doing aes-128-cbc for 3s on 1024 size blocks: 73053 aes-128-cbc's in 0.08s
Doing aes-128-cbc for 3s on 8192 size blocks: 13744 aes-128-cbc's in 0.02s
OpenSSL 0.9.7j 04 May 2006
built on: date not available
options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial)
blowfish(idx)
compiler: information not available
available timing options: USE_TOD HZ=100 [sysconf value]
timing function used: getrusage
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192
bytes
aes-128-cbc  14928.13k45003.84k   240522.58k   957520.28k
7205814.27k

But same hardware and OpenBSD 5.5 yields:

# openssl speed -evp aes-128-cbc -engine cryptodev
invalid engine cryptodev
694556312:error:25066067:DSO support routines:DLFCN_LOAD:could not load the
shared
library:/usr/src/lib/libssl/crypto/../src/crypto/dso/dso_dlfcn.c:187:filename(/usr/lib/engines/libcryptodev.so):
File not found
694556312:error:25070067:DSO support routines:DSO_load:could not load the
shared library:/usr/src/lib/libssl/crypto/../src/crypto/dso/dso_lib.c:244:
694556312:error:260B6084:engine routines:DYNAMIC_LOAD:dso not
found:/usr/src/lib/libssl/crypto/../src/crypto/engine/eng_dyn.c:450:
694556312:error:2606A074:engine routines:ENGINE_by_id:no such
engine:/usr/src/lib/libssl/crypto/../src/crypto/engine/eng_list.c:417:id=cryptodev
694556312:error:25066067:DSO support routines:DLFCN_LOAD:could not load the
shared
library:/usr/src/lib/libssl/crypto/../src/crypto/dso/dso_dlfcn.c:187:filename(libcryptodev.so):
File not found
694556312:error:25070067:DSO support routines:DSO_load:could not load the
shared library:/usr/src/lib/libssl/crypto/../src/crypto/dso/dso_lib.c:244:
694556312:error:260B6084:engine routines:DYNAMIC_LOAD:dso not
found:/usr/src/lib/libssl/crypto/../src/crypto/engine/eng_dyn.c:450:
Doing aes-128-cbc for 3s on 16 size blocks: 674503 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 64 size blocks: 185206 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 256 size blocks: 47602 aes-128-cbc's in 3.01s
Doing aes-128-cbc for 3s on 1024 size blocks: 24007 aes-128-cbc's in 2.99s
Doing aes-128-cbc for 3s on 8192 size blocks: 3029 aes-128-cbc's in 3.02s
OpenSSL 1.0.1c 10 May 2012
built on: date not available
options:bn(64,32) rc4(4x,int) des(ptr,risc1,16,long) aes(partial) idea(int)
blowfish(idx)
compiler: information not available
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192
bytes
aes-128-cbc   3597.35k 3951.06k 4048.54k 8221.80k
8216.41k

# dmesg
OpenBSD 5.5 (GENERIC) #276: Wed Mar  5 09:57:06 MST 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class)
499 MHz
snip
glxpcib0 at pci0 dev 15 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit
3579


We planned an upgrade years to OpenBSD 5.0 but that was cancelled. I did
however had a system lying around from back then with OpenBSD 5.0 on it so
I tested that as well, and it doesn't work. Same result as OpenBSD 5.5.

Suggestions how to get this (acceleration) working again?
Should it be invoked differently?

Thank you for your time and interest,

Wessels



Re: OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread Sime Ramov
On Mon, 9 Jun 2014 21:40:16 +0200, wessels wessels...@gmail.com wrote:
 Suggestions how to get this (acceleration) working again? Should it be
 invoked differently?

Is `sysctl kern.usercrypto` enabled?



Re: OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread wessels
Thanks Sime,

yes setting kern.usercrypto=1 did the trick. Apparently in OpenBSD 4.4 that
was enabled by default and this was changed in a later release.

# sysctl kern.usercrypto=1
kern.usercrypto: 0 - 1
# openssl speed -evp aes-128-cbc -engine cryptodev
engine cryptodev set.
Doing aes-128-cbc for 3s on 16 size blocks: 162949 aes-128-cbc's in 0.17s
Doing aes-128-cbc for 3s on 64 size blocks: 154781 aes-128-cbc's in 0.17s
Doing aes-128-cbc for 3s on 256 size blocks: 124542 aes-128-cbc's in 0.13s
Doing aes-128-cbc for 3s on 1024 size blocks: 69869 aes-128-cbc's in 0.10s
Doing aes-128-cbc for 3s on 8192 size blocks: 13602 aes-128-cbc's in 0.04s
OpenSSL 1.0.1c 10 May 2012
built on: date not available
options:bn(64,32) rc4(4x,int) des(ptr,risc1,16,long) aes(partial) idea(int)
blowfish(idx)
compiler: information not available
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192
bytes
aes-128-cbc  15336.38k58270.49k   245251.94k   715458.56k
2785689.60k

Sometime these things are so simple but the information isn't findable. I
hope that people stumbling upon this problem as find this thread.

Thanks again,

Wessels



Re: OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread Otto Moerbeek
On Mon, Jun 09, 2014 at 10:11:08PM +0200, wessels wrote:

 Thanks Sime,
 
 yes setting kern.usercrypto=1 did the trick. Apparently in OpenBSD 4.4 that
 was enabled by default and this was changed in a later release.
 
 # sysctl kern.usercrypto=1
 kern.usercrypto: 0 - 1
 # openssl speed -evp aes-128-cbc -engine cryptodev
 engine cryptodev set.
 Doing aes-128-cbc for 3s on 16 size blocks: 162949 aes-128-cbc's in 0.17s
 Doing aes-128-cbc for 3s on 64 size blocks: 154781 aes-128-cbc's in 0.17s
 Doing aes-128-cbc for 3s on 256 size blocks: 124542 aes-128-cbc's in 0.13s
 Doing aes-128-cbc for 3s on 1024 size blocks: 69869 aes-128-cbc's in 0.10s
 Doing aes-128-cbc for 3s on 8192 size blocks: 13602 aes-128-cbc's in 0.04s
 OpenSSL 1.0.1c 10 May 2012
 built on: date not available
 options:bn(64,32) rc4(4x,int) des(ptr,risc1,16,long) aes(partial) idea(int)
 blowfish(idx)
 compiler: information not available
 The 'numbers' are in 1000s of bytes per second processed.
 type 16 bytes 64 bytes256 bytes   1024 bytes   8192
 bytes
 aes-128-cbc  15336.38k58270.49k   245251.94k   715458.56k
 2785689.60k
 
 Sometime these things are so simple but the information isn't findable. I
 hope that people stumbling upon this problem as find this thread.
 
 Thanks again,
 
 Wessels

But check if it really helps in your case, and not just openssl speed calls.
It was disabled for a reason.

-Otto



Re: keyboard layout on macppc

2014-06-09 Thread luca suriano
* - 19:04:17 (Monday 09 June 2014)
* - Mats O Jansson:

 Yes, set encoding to e.g. US. Modify keyboard.map with wsconsctl as shown 
 by the man page. Do it as a script so you can redo it when ever needed.
 
 wsconsctl keyboard.map will show the current map.
 
 When you have something useful it would be easy to convert it to the 
 internal keyboard map format in sys/dev/adb/akbdmap.h. Most large maps 
 starts with US and modifies it.

Many thanks.

-- 
Information wants to be free



Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread Peter N. M. Hansteen
Allan Streib str...@cs.indiana.edu writes:

 Can you share what you changed in login.conf, and what problems were
 resolved as a result?

I mucked around with increasing the shared memory limits, and in fact
it helped certain browsers go from glacial response times to merely 'a
tad slow at times, YMMW'.

http://home.nuug.no/~peter/transition/bsdcan2014/desktop.html and the
following slide has the meat, such as it is.

There's more work to be done for any 'OpenBSD as the ultimate desktop'
article, though.

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.



Re: OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread wessels
Otto thanks for the warning. Any details about why it was disabled? Anyhow
tomorrow I'll begin further testing but things do look good.

Many thanks all. I was a bit afraid that I hit nasty bug but not sofar.

Kind regards,

Wessels


On Mon, Jun 9, 2014 at 10:21 PM, Otto Moerbeek o...@drijf.net wrote:

 On Mon, Jun 09, 2014 at 10:11:08PM +0200, wessels wrote:

  Thanks Sime,
 
  yes setting kern.usercrypto=1 did the trick. Apparently in OpenBSD 4.4
 that
  was enabled by default and this was changed in a later release.
 
  # sysctl kern.usercrypto=1
  kern.usercrypto: 0 - 1
  # openssl speed -evp aes-128-cbc -engine cryptodev
  engine cryptodev set.
  Doing aes-128-cbc for 3s on 16 size blocks: 162949 aes-128-cbc's in 0.17s
  Doing aes-128-cbc for 3s on 64 size blocks: 154781 aes-128-cbc's in 0.17s
  Doing aes-128-cbc for 3s on 256 size blocks: 124542 aes-128-cbc's in
 0.13s
  Doing aes-128-cbc for 3s on 1024 size blocks: 69869 aes-128-cbc's in
 0.10s
  Doing aes-128-cbc for 3s on 8192 size blocks: 13602 aes-128-cbc's in
 0.04s
  OpenSSL 1.0.1c 10 May 2012
  built on: date not available
  options:bn(64,32) rc4(4x,int) des(ptr,risc1,16,long) aes(partial)
 idea(int)
  blowfish(idx)
  compiler: information not available
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes256 bytes   1024 bytes   8192
  bytes
  aes-128-cbc  15336.38k58270.49k   245251.94k   715458.56k
  2785689.60k
 
  Sometime these things are so simple but the information isn't findable. I
  hope that people stumbling upon this problem as find this thread.
 
  Thanks again,
 
  Wessels

 But check if it really helps in your case, and not just openssl speed
 calls.
 It was disabled for a reason.

 -Otto



Re: OpenBSD 5.5 support for hw crypto in OpenSSL

2014-06-09 Thread Otto Moerbeek
On Mon, Jun 09, 2014 at 10:37:21PM +0200, wessels wrote:

 Otto thanks for the warning. Any details about why it was disabled? Anyhow
 tomorrow I'll begin further testing but things do look good.
 
 Many thanks all. I was a bit afraid that I hit nasty bug but not sofar.

Almost all of the the time, the speedup wasn't there due to context
switching etc. I even seems to remember that you could not switch it
on even, but that seems to have changed. Sorry, can't remember the
details.

-Otto



Re: Radeondrm on OpenBSD 5.5 stable

2014-06-09 Thread Stan Gammons
On 06/09/2014 01:56 AM, Jonathan Gray wrote:
 On Sun, Jun 08, 2014 at 07:01:56AM -0500, Stan Gammons wrote:
 Is there a known problem with the Radeon driver on OpenBSD 5.5 AMD64
 stable?   I noticed the text on the console was scrolling very slow
 while src.tar.gz was extracting.  I didn't time it, but it seem to take
 2 to 3 times as long to return to the command line compared to
 extracting the same file on a slower i386 machine.   Syslog output is below.
 Well things are going to be slow when all the acceleration is being
 disabled.  It isn't clear if the problem you're encountering is
 due to something like missing firmware as you didn't include a dmesg.



I tried to send this earlier and apparently it didn't send for some reason.

It loads or tries to load firmware at boot.

Here's the dmesg info.


OpenBSD 5.5 (GENERIC.MP) #0: Sat Jun  7 22:45:43 CDT 2014
r...@gateway.home.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4141809664 (3949MB)
avail mem = 4022943744 (3836MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (52 entries)
bios0: vendor Award Software International, Inc. version FK date 
08/31/2010
bios0: Gigabyte Technology Co., Ltd. GA-MA74GM-S2
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) 
USB5(S3) USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) 
PCE6(S4) PCE7(S4) PCE8(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) II X2 250 Processor, 3021.32 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully 
associative
cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully 
associative
cpu0: AMD erratum 721 detected and fixed
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 201MHz
cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) II X2 250 Processor, 3020.91 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully 
associative
cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully 
associative
cpu1: AMD erratum 721 detected and fixed
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (P2P_)
acpiprt2 at acpi0: bus 2 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus -1 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE8)
acpiprt9 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpibtn0 at acpi0: PWRB
cpu0: 3021 MHz: speeds: 3000 2300 1800 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 ATI RS740 Host rev 0x00
ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 ATI Radeon 2100 rev 0x00
drm0 at radeondrm0
radeondrm0: apic 2 int 18
ppb1 at pci0 dev 2 function 0 ATI RS690M PCIE rev 0x00: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 Intel 82571EB rev 0x06: apic 2 int 18, 
address 00:15:17:cd:db:42
em1 at pci2 dev 0 function 1 Intel 82571EB rev 0x06: apic 2 int 19, 
address 00:15:17:cd:db:43
ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 
22, AHCI 1.1
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: ATA, Maxtor 7Y250M0, YAR5 SCSI3 0/direct 
fixed t10.ATA_Maxtor_7Y250M0_Y64Y10TE_
sd0: 239372MB, 512 bytes/sector, 490234752 sectors
sd1 at scsibus0 targ 1 lun 0: ATA, Maxtor 6Y250M0, YAR5 SCSI3 0/direct 
fixed t10.ATA_Maxtor_6Y250M0_Y64DMDWE_
sd1: 239371MB, 512 bytes/sector, 490232639 sectors
cd0 at scsibus0 targ 2 lun 0: HL-DT-ST, DVDRAM GH24NS95, RN01 ATAPI 
5/cdrom removable
ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 16, 
version 1.0, legacy support
ohci1 at pci0 dev 18 function 1 ATI SB700 USB rev 0x00: apic 2 int 16, 
version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17

Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread STeve Andre'

On 03/05/14 10:08, openda...@hushmail.com wrote:

Anybody have any thoughts on how to achieve this?

Thanks.

O.D.



Lots of others have replied to this, but I'm going to jump in with
a few comments.

Probably the biggest reason OpenBSD will never be the fastest OS
around is the simple fact that when optimizing for speed, you
sacrifice other things.  Like security.  Security, or correctness, means
you are looking for the most reliable way to do something, not the
fastest.  Mechanisms like pro-police (or a new name for it?) are
going to slow things down a little.  I think Theo said that all the
security systems slow a system down by less than 5%.  I believe
that.  The effect isn't huge but some would call that too much.

Oh Well.

When something can be done more efficiently, it is.  But not at
the cost of potential security problems.  The MP code is a classic
case of something written that strives to avoid race conditions
at all costs.  Me, I'd rather lose a few percent rather than have
a hole.

Lastly, I will remind you that the fastest OS compared to OpenBSD
is very likely less than 15%.  Say its 25% even, and you could get
faster hardware to accomedate that.

In an era of ever increasing hardware speed, optimizing on anything
other than security and stability is foolish.

--STeve Andre'



Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic

2014-06-09 Thread Chris Cappuccio
Mattieu Baptiste [mattie...@gmail.com] wrote:
 Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit :
  I know it???s no consolation to you but using a Kingston 30 GB mSATA from
 amazon works perfectly. The APU is on the May bios and I???ve had no issues.
 
  Didn???t the PCEngines mSATA drive have problems in general? There???s a
 mention on here about issues with the a version - is that yours?
 http://pcengines.ch/msata16b.htm
 
 Theoritically, I should have the new firmware (that's what told my vendor).
 But it seems there are still problems with these.
 
 Thanks for the tip concerning the Kingston drive.

I've been using the Sandisk X110 msata. Borat says great success!



Re: hplip

2014-06-09 Thread Stuart Henderson
On 2014-06-08, Maurice McCarthy m...@mythic-beasts.com wrote:
 I bought a new, cheap HP Deskjet 2540 printer (usb and wireless).
snip

/usr/local/share/doc/pkg-readmes/hplip* should help a lot (it also refers
to the pkg-readme for cups which you'll also need to follow for USB).



running cvs update as root (was: Re: New install)

2014-06-09 Thread Jonathan Thornburg
In message http://marc.info/?l=openbsd-miscm=140224659303522w=1,
Miod Vallat wrote (about an anoncvs update to /usr/src)
 you should not run this command as root

http://www.openbsd.org/anoncvs.html  shows the 'cvs update' command being
run by root (# shell prompt), and I wouldn't expect any non-root user
to have write permission to /usr/src anyway.  So... why is doing the
cvs-update as root a bad idea?

ciao,

-- 
-- Jonathan Thornburg [remove -animal to reply] 
jth...@astro.indiana-zebra.edu
   Dept of Astronomy  IUCSS, Indiana University, Bloomington, Indiana, USA
   currently on the west coast of Canada
   There was of course no way of knowing whether you were being watched
at any given moment.  How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork.  It was even conceivable
that they watched everybody all the time.  -- George Orwell, 1984



Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread John D. Verne
On Mon, Jun 09, 2014 at 04:12:07PM -0400, STeve Andre' wrote:
 On 03/05/14 10:08, openda...@hushmail.com wrote:
 Anybody have any thoughts on how to achieve this?
 
 Thanks.
 
 O.D.
 
 
 Lots of others have replied to this, but I'm going to jump in with
 a few comments.
 
 Probably the biggest reason OpenBSD will never be the fastest OS
 around is the simple fact that when optimizing for speed, you
 sacrifice other things.  Like security.  Security, or correctness, means
 you are looking for the most reliable way to do something, not the
 fastest.  Mechanisms like pro-police (or a new name for it?) are
 going to slow things down a little.  I think Theo said that all the
 security systems slow a system down by less than 5%.  I believe
 that.  The effect isn't huge but some would call that too much.
 
Indeed.

Good, fast, or cheap.  Choose any two.

This is an engineering maxim that has held up for quite some time now.
There is a tension between these that cannot be resolved completely, and
there will always be trade-offs to be made.

-- 
John D. Verne
j...@clevermonkey.org



Re: running cvs update as root (was: Re: New install)

2014-06-09 Thread John D. Verne
On Mon, Jun 09, 2014 at 03:07:17PM -0700, Jonathan Thornburg wrote:
 In message http://marc.info/?l=openbsd-miscm=140224659303522w=1,
 Miod Vallat wrote (about an anoncvs update to /usr/src)
  you should not run this command as root
 
 http://www.openbsd.org/anoncvs.html  shows the 'cvs update' command being
 run by root (# shell prompt), and I wouldn't expect any non-root user
 to have write permission to /usr/src anyway.  So... why is doing the
 cvs-update as root a bad idea?
 
I'd like to hear from the experts, as well.

That being said, if you make /usr/src, /usr/xenocara, usr/ports owned by
root:wsrc, and chmod g+rwx all the directories, a regular user in that
group seems to be able to do everything but install.

With the caveat that if root has built previously in the same tree, you
might have to clean up some stuff by hand. For example, I can build a
kernel as a regular user, but I had to have root clear out the compile
dir made by config, as this was last invoked by root.

-- 
John D. Verne
j...@clevermonkey.org



Re: running cvs update as root (www patch?)

2014-06-09 Thread Jean-Philippe Ouellet
On Mon, Jun 09, 2014 at 03:07:17PM -0700, Jonathan Thornburg wrote:
 http://www.openbsd.org/anoncvs.html  shows the 'cvs update'
 command being run by root (# shell prompt)

One example (the latest one added) in the Using CVS to ... section
uses $, as do all the examples in the Example usages ... section.
Perhaps they should all be $? I'm not sure, but diff at the end if so.

 I wouldn't expect any non-root user to have write permission to
 /usr/src anyway.

Just add a non-root user to the wsrc group and
$ sudo chmod -R g+w /usr/{src,obj,ports,whatever}
The relevant dirs should be group-writable by default anyway, but
if you've checked out as root on top of it without a proper umask,
then it would cause issues.

 why is doing the cvs-update as root a bad idea?

Why would you run it as root if you don't need to?  It takes
potentially-malicious input from the network and isn't super-tiny.

Just general principle of least priveledge, it's not like you
/can't/ run it as root (lest your source tree be corrupted or
something).


If this change were to be made, should there also be a note about
wsrc, umask 002, and the rationale for not running as root?
Tar examples are also #, perhaps those should be changed as well?

Index: build/mirrors/anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.35
diff -u -p -r1.35 anoncvs.html.head
--- build/mirrors/anoncvs.html.head 9 May 2014 14:02:39 -   1.35
+++ build/mirrors/anoncvs.html.head 10 Jun 2014 00:45:26 -
@@ -221,14 +221,14 @@ If you don't have a CD handy, use the me
 
 p (If you are following icurrent/i):
 pre
-   # strongcd /usr/strong
-   # strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P 
src/strong
+   $ strongcd /usr/strong
+   $ strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P 
src/strong
 /pre
 
 p (If you are following the patch branch for 5.5):
 pre
-   # strongcd /usr/strong
-   # strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_5 
-P src/strong
+   $ strongcd /usr/strong
+   $ strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_5 
-P src/strong
 /pre
 !-- DO NOT EDIT ANONCVS.HTML MANUALLY - IT IS GENERATED FROM TEMPLATES! --
 
@@ -258,14 +258,14 @@ Confirm this, and the fingerprint will t
 li Anytime afterwards, to `update' this tree:
 p (If you are following icurrent/i):
 pre
-   # strongcd /usr/src/strong
-   # strongcvs -q up -Pd/strong
+   $ strongcd /usr/src/strong
+   $ strongcvs -q up -Pd/strong
 /pre
 
 p (If you are following the patch branch for 5.5):
 pre
-   # strongcd /usr/src/strong
-   # strongcvs -q up -rOPENBSD_5_5 -Pd/strong
+   $ strongcd /usr/src/strong
+   $ strongcvs -q up -rOPENBSD_5_5 -Pd/strong
 /pre
 
 Every time you ran this it would synchronize your /usr/src tree.
@@ -278,8 +278,8 @@ If you are updating a source tree that y
 from a different server, or from a CD, you strongmust/strong
 add the em-d [cvsroot]/em option to cvs.
 pre
-   # strongcd /usr/src/strong
-   # strongcvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd/strong
+   $ strongcd /usr/src/strong
+   $ strongcvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd/strong
 /pre
 /ul
 
@@ -289,24 +289,24 @@ it is similar to src:
 ulli
 p (If you are following icurrent/i):
 pre
-   # strongcd /usr/strong
-   # strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P 
ports/strong
+   $ strongcd /usr/strong
+   $ strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P 
ports/strong
 /pre
 p (If you are following the patch branch for 5.5):
 pre
-   # strongcd /usr/strong
-   # strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_5 
-P ports/strong
+   $ strongcd /usr/strong
+   $ strongcvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_5 
-P ports/strong
 /pre
 li Anytime afterwards, to `update' this tree:
 p (If you are following icurrent/i):
 pre
-   # strongcd /usr/ports/strong
-   # strongcvs -q up -Pd/strong
+   $ strongcd /usr/ports/strong
+   $ strongcvs -q up -Pd/strong
 /pre
 p (If you are following the patch branch for 5.5):
 pre
-   # strongcd /usr/ports/strong
-   # strongcvs -q up -rOPENBSD_5_5 -Pd/strong
+   $ strongcd /usr/ports/strong
+   $ strongcvs -q up -rOPENBSD_5_5 -Pd/strong
 /pre
 /ul
 
@@ -318,8 +318,8 @@ For those who like to see screenfulls of
 To make a diff of a locally patched module (here icd.c/i) to include with
 a bug report:
 pre
-   # strongcd /usr/strong
-   # strongcvs diff -u src/sys/scsi/cd.c gt; /tmp/patch/strong
+   $ strongcd /usr/strong
+   $ strongcvs diff -u src/sys/scsi/cd.c gt; /tmp/patch/strong
 /pre
 
 p



Re: hplip

2014-06-09 Thread Maurice McCarthy
On Mon, Jun 09, 2014 at 11:15:30PM + or thereabouts, Stuart Henderson wrote:
 On 2014-06-08, Maurice McCarthy m...@mythic-beasts.com wrote:
  I bought a new, cheap HP Deskjet 2540 printer (usb and wireless).
 snip
 
 /usr/local/share/doc/pkg-readmes/hplip* should help a lot (it also refers
 to the pkg-readme for cups which you'll also need to follow for USB).
 
Thanks Stuart,

I kept all your advice from when I had the SX205 so I've already done all that. 
I'm coming to the conclusion that hp:/net works whereas hp:/usb does not. 

Just to say I tried to update the personal port which you made for me but it 
failed only because of the new 'signify', I think. That is the internal check 
sum was not calculated in the first place. I didn't have the heart to ask again 
for help over it. I reckoned it would be better if I learned more myself.

Not to worry, the darn new thing works anyhow.

Thanks again
Moss



Re: running cvs update as root (was: Re: New install)

2014-06-09 Thread Miod Vallat
 http://www.openbsd.org/anoncvs.html  shows the 'cvs update' command being
 run by root (# shell prompt), and I wouldn't expect any non-root user
 to have write permission to /usr/src anyway.  So... why is doing the
 cvs-update as root a bad idea?

Is this a kind of bad joke? Running anything as root unless it
absolutely requires root privileges is a bad idea. Put yourself in the
wsrc group, and you'll be able to write into /usr/src.

Miod



Re: Radeondrm on OpenBSD 5.5 stable

2014-06-09 Thread Jonathan Gray
On Mon, Jun 09, 2014 at 04:53:23AM -0500, Stan Gammons wrote:
 On 06/09/2014 01:56 AM, Jonathan Gray wrote:
 On Sun, Jun 08, 2014 at 07:01:56AM -0500, Stan Gammons wrote:
 Is there a known problem with the Radeon driver on OpenBSD 5.5 AMD64
 stable?   I noticed the text on the console was scrolling very slow
 while src.tar.gz was extracting.  I didn't time it, but it seem to take
 2 to 3 times as long to return to the command line compared to
 extracting the same file on a slower i386 machine.   Syslog output is 
 below.
 Well things are going to be slow when all the acceleration is being
 disabled.  It isn't clear if the problem you're encountering is
 due to something like missing firmware as you didn't include a dmesg.
 
 
 
 It loads or tries to load firmware at boot.
 
 Here's the dmesg info.

So it seems something isn't working right with the GART.
Could you try the following diff to force it to a smaller size?

Diff against -current but will likely apply to 5.5

Index: sys/dev/pci/drm/radeon/rs400.c
===
RCS file: /cvs/src/sys/dev/pci/drm/radeon/rs400.c,v
retrieving revision 1.4
diff -u -p -r1.4 rs400.c
--- sys/dev/pci/drm/radeon/rs400.c  9 Feb 2014 12:33:44 -   1.4
+++ sys/dev/pci/drm/radeon/rs400.c  10 Jun 2014 04:57:21 -
@@ -54,6 +54,8 @@ void rs400_gart_adjust_size(struct radeo
rdev-mc.gtt_size = 32 * 1024 * 1024;
return;
}
+   DRM_ERROR(Forcing to 32M GART size\n);
+   rdev-mc.gtt_size = 32 * 1024 * 1024;
 }
 
 void rs400_gart_tlb_flush(struct radeon_device *rdev)



Re: Vision 2020: Making OpenBSD the world's fastest OS

2014-06-09 Thread Amit Kulkarni
 Lastly, I will remind you that the fastest OS compared to OpenBSD
 is very likely less than 15%.  Say its 25% even, and you could get
 faster hardware to accomedate that.


Come on, that is a false assertion. OpenBSD does have its warts, like
everybody else out there. They are different warts compared to others. But
IMHO running it slow with security is better than running it fast, and not
paying attention to secuirty.



 In an era of ever increasing hardware speed, optimizing on anything
 other than security and stability is foolish.


Yet, security and stability is why I stay with OpenBSD, as does most
everybody who discover it.