OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Openbsd 4.0 For Zaurus, Joke or Beta?
zs_ftp
post Aug 17 2006, 12:47 PM
Post #1





Group: Members
Posts: 14
Joined: 10-July 06
From: Russia, Novosibirsk
Member No.: 10,367



Has come on ftp:// ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus
And very strongly was surprised.
There is OpenBSD 4.0.
It is a joke or beta?
blink.gif
Go to the top of the page
 
+Quote Post
mathemajikian
post Aug 18 2006, 01:46 AM
Post #2





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



To quote Andy

QUOTE
post Aug 6 2006, 05:24 PM Post #10
It will be marked -beta pretty much until 4.0 stable is released. Think of it as -current.

-Andy
Go to the top of the page
 
+Quote Post
zs_ftp
post Aug 18 2006, 02:06 AM
Post #3





Group: Members
Posts: 14
Joined: 10-July 06
From: Russia, Novosibirsk
Member No.: 10,367



QUOTE(mathemajikian @ Aug 18 2006, 03:46 PM)
To quote Andy

QUOTE
post Aug 6 2006, 05:24 PM Post #10
It will be marked -beta pretty much until 4.0 stable is released. Think of it as -current.

-Andy

*




Ок. Thanx
Go to the top of the page
 
+Quote Post
mathemajikian
post Aug 18 2006, 02:36 AM
Post #4





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



It seems that support for machdep.allowaperture in 4.0-beta [really during 3.9 current phase... thanks Andy] has been removed. (One of the reasons why you should mergemaster /etc after upgrade)

machdep.allowaperture=2 ----> Operation not supported

vi /etc/sysctl

Comment out or dd machdep.allowaperture=2

#machdep.allowaperture=2

or

dd machdep.allowaperture=2


# $OpenBSD: sysctl.conf,v 1.40 2006/01/28 18:22:43 brad Exp $
#
# This file contains a list of sysctl options the user wants set at
# boot time. See sysctl(3) and sysctl(8) for more information on
# the many available variables.
#
#net.inet.ip.forwarding=1 # 1=Permit forwarding (routing) of IPv4 packets
#net.inet.ip.mforwarding=1 # 1=Permit forwarding (routing) of IPv4 multicast packets
#net.inet6.ip6.forwarding=1 # 1=Permit forwarding (routing) of IPv6 packets
#net.inet6.ip6.accept_rtadv=1 # 1=Permit IPv6 autoconf (forwarding must be 0)
#net.inet.tcp.rfc1323=0 # 0=Disable TCP RFC1323 extensions (for if tcp is slow)
#net.inet.tcp.rfc3390=0 # 0=Disable RFC3390 for TCP window increasing
#net.inet.esp.enable=0 # 0=Disable the ESP IPsec protocol
#net.inet.ah.enable=0 # 0=Disable the AH IPsec protocol
#net.inet.esp.udpencap=0 # 0=Disable ESP-in-UDP encapsulation
#net.inet.ipcomp.enable=1 # 1=Enable the IPCOMP protocol
#net.inet.etherip.allow=1 # 1=Enable the Ethernet-over-IP protocol
#net.inet.tcp.ecn=1 # 1=Enable the TCP ECN extension
#ddb.panic=0 # 0=Do not drop into ddb on a kernel panic
#ddb.console=1 # 1=Permit entry of ddb from the console
#fs.posix.setuid=0 # 0=Traditional BSD chown() semantics
#vm.swapencrypt.enable=0 # 0=Do not encrypt pages that go to swap
#vfs.nfs.iothreads=4 # number of nfsio kernel threads
#net.inet.ip.mtudisc=0 # 0=disable tcp mtu discovery
#kern.usercrypto=0 # 0=disable userland use of /dev/crypto
#kern.splassert=2 # 2=enable with verbose error messages
#machdep.apmwarn=10 # battery % when apm status messages enabled
#machdep.kbdreset=1 # permit zkbd(4) power key to do a nice halt
#machdep.maxspeed=520 # set change maximum processor speed
#machdep.lidsuspend=1 # closing the lid will suspend machine
#hw.setperf=0 # 0=slowest speed, 100=fastest speed
Go to the top of the page
 
+Quote Post
iamasmith
post Aug 18 2006, 02:58 AM
Post #5





Group: Members
Posts: 1,248
Joined: 6-July 04
Member No.: 3,928



Actually the aperture setting can only be changed in secure level 0, when fully booted the system is in secure level 1.

This isn't needed for X on the Zaurus now though and you should have it set to 0 anyway.

-Andy
Go to the top of the page
 
+Quote Post
mathemajikian
post Aug 18 2006, 03:06 AM
Post #6





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



Heres an interesting read found at:

http://marc.theaimsgroup.com/?l=openbsd-mi...114233317926101

-------------------------------------------------------------------------------------------------------------------------------------------------------------
I would like to educate people of something which many are not aware
of -- how X works on a modern machine.

Some of our architectures use a tricky and horrid thing to allow X to
run. This is due to modern PC video card architecture containing a
large quantity of PURE EVIL. To get around this evil the X developers
have done some rather expedient things, such as directly accessing the
cards via IO registers, directly from userland. It is hard to see how
they could have done other -- that is how much evil the cards contain.
Most operating systems make accessing these cards trivially easy for X
to do this, but OpenBSD creates a small security barrier through the
use of an "aperture driver", called xf86(4)

http://www.openbsd.org/cgi-bin/man.cgi?query=xf86

This device exists on i386, amd64, alpha, cats, macppc, and sparc64.
(Other architectures do not need such a thing, since they have less evil).

So let's say X wants to use the "aperture". Permission to use it is
controlled by the following sysctl(8) variable:

# sysctl -a machdep.allowaperture
machdep.allowaperture=0

The three possible values are 0 (aperture disabled), 1 (small window
for very old video cards), or 2 (large window for modern video cards
which have more evil in them). If you are running X on one of the
architectures listed above, you will have it set to 1 or 2.

The aperture setting cannot be changed once the system has booted
multiuser because the system securelevel locks it. The initial
setting of this variable however comes from a line in /etc/sysctl.conf.
You will find a line like this (ie. 2, for a fancy video card):

machdep.allowaperture=2 # See xf86(4)

If you had a machine that was not running X you might see either of
the following (# is a comment character, so that is why these are the
same).

#machdep.allowaperture=2 # See xf86(4)
machdep.allowaperture=0 # See xf86(4)

The kernel default is 0.... but for a few releases the OpenBSD install
script has had the question:

Do you expect to run the X Window System? [yes]

And if you answered "yes" (or just hit return), /etc/sysctl.conf was
changed, so that the setting became "2".

Well, recently we have changed our minds, because we still feel that
the aperture is too dangerous.
And the vendors keep finding creative
ways to squeeze more and more evil into their video cards!

Please be aware that other operating systems don't even have an
aperture device, because they simply let root processes talk to the
video cards (via /dev/mem). Their X servers also run entirely as
root, while ours is now privilege seperated and running jailed as user
_x11. Even so, our privilege seperated X server is talking directly
to the IO registers of a video card with much evil in it. And many
newer video cards are very smart, capable, and thus dangerous. So we
have concerns.

Therefore, after 3.9, that default for the install script question is
being changed to "no".

If you are not using X we recommend ensuring that the aperture is closed.
Please edit /etc/sysctl.conf, change to machdep.allowaperture=0, and
reboot.

-------------------------------------------------------------------------------------------------------------------------------------------------------

From the manpage:

Access to the /dev/xf86 device is allowed when the sysctl(8) variable
machdep.allowaperture is greater than or equal to 1. This variable
(which has a default value of 0) can only be raised when the security
level is less than or equal to 0, so it should be set in
/etc/sysctl.conf. The possible values for machdep.allowaperture are:

0 the aperture driver is disabled. Opening it returns EPERM.

1 the aperture driver allows access to standard VGA framebuffer and
BIOS. Access to pci(4) configuration registers is also allowed.

2 in addition to allowing access to pci(4) configuration registers,
the aperture driver allows access to the whole first megabyte of
physical memory, permitting use of the int10 emulation in X.Org
6.8 and later. Note that this can cause some security problems,
since the process that has access to the aperture driver can also
access part of the kernel memory. This mode is not supported on
alpha or sparc64.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Go to the top of the page
 
+Quote Post
iamasmith
post Aug 18 2006, 03:14 AM
Post #7





Group: Members
Posts: 1,248
Joined: 6-July 04
Member No.: 3,928



Actually I will correct myself after reading the arm32_machdep.c source that implements the aperture sysctl.

The aperture value may be lowered only in securelevels above 0, to be raised the kernel must be in securelevel 0.

-Andy
Go to the top of the page
 
+Quote Post
mathemajikian
post Aug 18 2006, 03:23 AM
Post #8





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



QUOTE
edit /etc/sysctl.conf, change to machdep.allowaperture=0, and
reboot.


I edited /etc/sysctl.conf as stated above and during boot it still told me operation not supported. smile.gif (I just wanted to see what would happen)
Go to the top of the page
 
+Quote Post
iamasmith
post Aug 18 2006, 03:28 AM
Post #9





Group: Members
Posts: 1,248
Joined: 6-July 04
Member No.: 3,928



QUOTE(mathemajikian @ Aug 18 2006, 11:23 AM)
QUOTE
edit /etc/sysctl.conf, change to machdep.allowaperture=0, and
reboot.


I edited /etc/sysctl.conf as stated above and during boot it still told me operation not supported. smile.gif (I just wanted to see what would happen)
*



smile.gif I stand corrected... the code is still in the module but the GENERIC configuration used to build the Zaurus kernel now has the 'option APERTURE' line removed so the sysctl is no longer available to set.. well spotted ^^

-Andy
Go to the top of the page
 
+Quote Post
jpmatrix
post Nov 7 2006, 10:52 AM
Post #10





Group: Members
Posts: 1,019
Joined: 15-February 05
From: France
Member No.: 6,477



latest 4.0 seems to be officially out for our Zaurus smile.gif
alleluia !

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

is it better to take it or the latest snapshot ?

ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus
Go to the top of the page
 
+Quote Post
mathemajikian
post Nov 8 2006, 12:54 AM
Post #11





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



I would go with the snapshot, then in a month or so download the latest source via cvsup and rebuild your system.

QUOTE(jpmatrix @ Nov 7 2006, 06:52 PM)
Go to the top of the page
 
+Quote Post
jpmatrix
post Jan 24 2007, 02:50 PM
Post #12





Group: Members
Posts: 1,019
Joined: 15-February 05
From: France
Member No.: 6,477



hi back guys!

well, what is the latest state of openbsd 4 on the zaurus, specially the C3000 ?
i swapped from openbsd to pdaxii13 because my main trouble with openbsd was suspend/resume bugs. are there still here ?
Go to the top of the page
 
+Quote Post
mathemajikian
post Jan 25 2007, 03:12 AM
Post #13





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



QUOTE(jpmatrix @ Jan 24 2007, 10:50 PM)
i swapped from openbsd to pdaxii13 because my main trouble with openbsd was suspend/resume bugs. are there still here?


I haven't had any issues with suspend/resume on my SL-C3200 since OBSD-3.9. When you install make sure you are using the latest snapshot and tweak /etc/sysctl.conf.
Go to the top of the page
 
+Quote Post
danboid
post Jan 25 2007, 04:52 AM
Post #14





Group: Members
Posts: 682
Joined: 26-December 05
From: Rochdale, Lancashire
Member No.: 8,789



I know this is a longshot but I don't suppose there is SRAM support i.e hardware accelerated gfx for cxx00 Zauru in the Open/NetBSD kernels is there?

Has somebody done any benchmarks of Linux 2.4 vs 2.6 vs Open and NetBSD on the c3x00?
Go to the top of the page
 
+Quote Post
mathemajikian
post Jan 25 2007, 12:19 PM
Post #15





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



QUOTE(danboid @ Jan 25 2007, 12:52 PM)
Has somebody done any benchmarks of Linux 2.4 vs 2.6 vs Open and NetBSD on the c3x00?


Linux will beat the BSD ports hands down when it comes to speed. Further information concerning this can be found here: http://www.oesf.org/forums/index.php?showtopic=17871

Here are some results in regards to OpenBSD vs. NetBSD on the Zaurus:

NetBSD
==============================================================

BYTE UNIX Benchmarks (Version 4.1.0)
System --
Start Benchmark Run: Wed Nov 29 13:24:20 UTC 2006
1 interactive users.
1:24PM up 3:47, 1 user, load averages: 0.34, 1.15, 1.35
-r-xr-xr-x 1 root wheel 159837 Nov 27 13:39 /bin/sh
/bin/sh: ELF 32-bit LSB executable, ARM, version 1, for NetBSD 4.99.4, dynamically linked (uses shared libs), not stripped
/dev/wd1a 1919534 855052 968506 46% /
Dhrystone 2 using register variables 560689.8 lps (10.0 secs, 10 samples)
Double-Precision Whetstone 6.4 MWIPS (9.4 secs, 10 samples)
System Call Overhead 181715.3 lps (10.0 secs, 10 samples)
Pipe Throughput 126797.1 lps (10.0 secs, 10 samples)
Pipe-based Context Switching 3133.6 lps (10.0 secs, 10 samples)
Process Creation 229.3 lps (30.0 secs, 3 samples)
Execl Throughput 88.6 lps (29.7 secs, 3 samples)
File Read 1024 bufsize 2000 maxblocks 62050.0 KBps (30.0 secs, 3 samples)
File Write 1024 bufsize 2000 maxblocks 3333.0 KBps (30.0 secs, 3 samples)
File Copy 1024 bufsize 2000 maxblocks 2986.0 KBps (30.0 secs, 3 samples)
File Read 256 bufsize 500 maxblocks 31599.0 KBps (30.0 secs, 3 samples)
File Write 256 bufsize 500 maxblocks 2327.0 KBps (30.0 secs, 3 samples)
File Copy 256 bufsize 500 maxblocks 1987.0 KBps (30.0 secs, 3 samples)
File Read 4096 bufsize 8000 maxblocks 69800.0 KBps (30.0 secs, 3 samples)
File Write 4096 bufsize 8000 maxblocks 3733.0 KBps (30.0 secs, 3 samples)
File Copy 4096 bufsize 8000 maxblocks 3185.0 KBps (30.0 secs, 3 samples)
Shell Scripts (1 concurrent) 96.0 lpm (60.0 secs, 3 samples)
Shell Scripts (8 concurrent) 17.0 lpm (60.0 secs, 3 samples)
Shell Scripts (16 concurrent) 8.3 lpm (60.0 secs, 3 samples)
Arithmetic Test (type = short) 71922.4 lps (10.0 secs, 3 samples)
Arithmetic Test (type = int) 75597.8 lps (10.0 secs, 3 samples)
Arithmetic Test (type = long) 75598.0 lps (10.0 secs, 3 samples)
Arithmetic Test (type = float) 3757.3 lps (10.0 secs, 3 samples)
Arithmetic Test (type = double) 2143.4 lps (10.0 secs, 3 samples)
Arithoh 36216277.1 lps (10.0 secs, 3 samples)
C Compiler Throughput 45.0 lpm (60.0 secs, 3 samples)
Dc: sqrt(2) to 99 decimal places 3488.3 lpm (30.0 secs, 3 samples)
Recursion Test--Tower of Hanoi 8641.5 lps (20.0 secs, 3 samples)


INDEX VALUES
TEST BASELINE RESULT INDEX

Dhrystone 2 using register variables 116700.0 560689.8 48.0
Double-Precision Whetstone 55.0 6.4 1.2
Execl Throughput 43.0 88.6 20.6
File Copy 1024 bufsize 2000 maxblocks 3960.0 2986.0 7.5
File Copy 256 bufsize 500 maxblocks 1655.0 1987.0 12.0
File Copy 4096 bufsize 8000 maxblocks 5800.0 3185.0 5.5
Pipe Throughput 12440.0 126797.1 101.9
Pipe-based Context Switching 4000.0 3133.6 7.8
Process Creation 126.0 229.3 18.2
Shell Scripts (8 concurrent) 6.0 17.0 28.3
System Call Overhead 15000.0 181715.3 121.1
=========
FINAL SCORE 16.7
# uname -a
NetBSD 4.99.4 NetBSD 4.99.4 (GENERIC) #1: Tue Nov 28 01:34:53 CST 2006 /stuff/src/zaurus/src/sys/arch/zaurus/compile/obj/GENERIC zaurus


OpenBSD
==============================================================

BYTE UNIX Benchmarks (Version 4.1.0)
System -- loki.my.domain
Start Benchmark Run: Wed Nov 29 13:22:31 MST 2006
1 interactive users.
1:22PM up 33 mins, 1 user, load averages: 0.61, 0.30, 0.20
-r-xr-xr-x 3 root bin 374992 Sep 17 18:33 /bin/sh
/bin/sh: ELF 32-bit LSB executable, ARM, version 1, for OpenBSD, statically linked, stripped
/dev/wd0a 3887390 2291582 1401440 62% /
Dhrystone 2 using register variables 448812.1 lps (10.0 secs, 10 samples)
Double-Precision Whetstone 4.8 MWIPS (8.3 secs, 10 samples)
System Call Overhead 122784.8 lps (10.1 secs, 10 samples)
Pipe Throughput 69276.0 lps (10.1 secs, 10 samples)
Pipe-based Context Switching 2862.0 lps (10.1 secs, 10 samples)
Process Creation 202.8 lps (30.0 secs, 3 samples)
Execl Throughput 59.4 lps (29.7 secs, 3 samples)
File Read 1024 bufsize 2000 maxblocks 24216.0 KBps (30.0 secs, 3 samples)
File Write 1024 bufsize 2000 maxblocks 1777.0 KBps (30.0 secs, 3 samples)
File Copy 1024 bufsize 2000 maxblocks 1457.0 KBps (30.0 secs, 3 samples)
File Read 256 bufsize 500 maxblocks 14192.0 KBps (30.0 secs, 3 samples)
File Write 256 bufsize 500 maxblocks 1066.0 KBps (30.0 secs, 3 samples)
File Copy 256 bufsize 500 maxblocks 970.0 KBps (30.0 secs, 3 samples)
File Read 4096 bufsize 8000 maxblocks 2390.0 KBps (30.0 secs, 3 samples)
File Write 4096 bufsize 8000 maxblocks 1600.0 KBps (30.0 secs, 3 samples)
File Copy 4096 bufsize 8000 maxblocks 666.0 KBps (30.0 secs, 3 samples)
Shell Scripts (1 concurrent) 127.2 lpm (60.1 secs, 3 samples)
Shell Scripts (8 concurrent) 18.3 lpm (60.0 secs, 3 samples)
Shell Scripts (16 concurrent) 9.0 lpm (60.0 secs, 3 samples)
Arithmetic Test (type = short) 64132.8 lps (10.0 secs, 3 samples)
Arithmetic Test (type = int) 73502.0 lps (10.2 secs, 3 samples)
Arithmetic Test (type = long) 74533.2 lps (10.0 secs, 3 samples)
Arithmetic Test (type = float) 2865.4 lps (10.0 secs, 3 samples)
Arithmetic Test (type = double) 1409.4 lps (10.2 secs, 3 samples)
Arithoh 1292431.3 lps (10.0 secs, 3 samples)
C Compiler Throughput no measured results
Dc: sqrt(2) to 99 decimal places 1341.1 lpm (30.0 secs, 3 samples)
Recursion Test--Tower of Hanoi 6667.9 lps (20.0 secs, 3 samples)


INDEX VALUES
TEST BASELINE RESULT INDEX

Dhrystone 2 using register variables 116700.0 448812.1 38.5
Double-Precision Whetstone 55.0 4.8 0.9
Execl Throughput 43.0 59.4 13.8
File Copy 1024 bufsize 2000 maxblocks 3960.0 1457.0 3.7
File Copy 256 bufsize 500 maxblocks 1655.0 970.0 5.9
File Copy 4096 bufsize 8000 maxblocks 5800.0 666.0 1.1
Pipe Throughput 12440.0 69276.0 55.7
Pipe-based Context Switching 4000.0 2862.0 7.2
Process Creation 126.0 202.8 16.1
Shell Scripts (8 concurrent) 6.0 18.3 30.5
System Call Overhead 15000.0 122784.8 81.9
=========
FINAL SCORE 10.6
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 22nd December 2014 - 01:10 AM