Christopher Barry | 10 Jan 18:54 2015
Picon

obsd as a phone?

Greetings,

First post here.

I'm developing a wearable device, that will eventually evolve into a
wearable phone. I've been focused on the ME aspects, and have not
zeroed in on HW/SW as yet. The last posts I can find via DDG about obsd
on a phone were from 2010, and people were saying 'no, won't work'.

Anyone have any insights into this idea these days?

Cheers,
-C

lausgans | 27 Dec 13:52 2014
Picon

Wandboard - supported or not?

Hi.

I'm seeing Wandboard mentioned here: http://www.openbsd.org/plat.html 
However i see no mentions neither on http://www.openbsd.org/armv7.html
nor on http://ftp.openbsd.org/pub/OpenBSD/5.5/armv7/INSTALL.armv7
Is there a support for it? If yes, anyone to mention it on the armv7 pages?

Thanks.
Alex

Edwin Amsler | 26 Dec 06:19 2014
Picon

Installer script crashing in snapshot

I downloaded the december 15th snapshot for the Cubieboard miniroot and the installer is crashing. The
file was from the University of Toronto mirror, here’s the URL:
http://openbsd.cs.toronto.edu/pub/OpenBSD/snapshots/armv7/miniroot-sunxi-56.fs

It’s not my AHCI contribution from last month since I’m able to format and write zeros to the connected
laptop drive. The install script is calling something that’s making the kernel panic. Any tips for
troubleshooting? I’ll probably just dump a bunch of `echo`s in there to figure out at what point this
‘alignment fault’ is happening.

Here’s the console dump:

(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? i
At any prompt except password prompts you can escape to a shell by
typing '!'. Default answers are shown in []'s and are selected by
pressing RETURN.  You can exit this program at any time by pressing
Control-C, but this can leave your system in an inconsistent state.

Terminal type? [vt220] 
System hostname? (short form, e.g. 'foo') Cubieboard

Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xd11996bc
DFSR=00000801, DFAR=d1199857, spsr=80000013
r0 =d1199857, r1 =00009c28, r2 =0000bb05, r3 =6d750000
r4 =d1199857, r5 =6d759c28, r6 =661cbb05, r7 =0000ffff
r8 =0000ffff, r9 =9c286d75, r10=bb05661c, r11=d1199740
r12=d1199744, ssp=d1199708, slr=00000008, pc =c0890d9c

panic: Fatal abort
syncing disks... done
(Continue reading)

Patrick Wildt | 23 Dec 22:43 2014
Picon

Re: Boot attempt: SolidRun CuBox-i2

Whoops, I must be very very tired.  I worked a but on the CubieBoard
and misread it.

Yeah, it’s a Cubox, so it’s i.MX.  My fault. :(

> Am 23.12.2014 um 22:25 schrieb Brian Conway <bconway <at> rcesoftware.com>:
> 
> Interesting, even though it's an i.MX6 SoC and not an Allwinner?
> Thanks for the tip, I'll give it a look.
> 
> Brian Conway
> Founder, Owner
> RCE Software, LLC
> 
> 
> On Tue, Dec 23, 2014 at 3:22 PM, Patrick Wildt <mail <at> patrick-wildt.de> wrote:
>> The i.MX version is definitely the wrong one.  You gotta try the SUNXI version.
>> 
>> \Patrick
>> 
>>> Am 23.12.2014 um 21:43 schrieb Brian Conway <bconway <at> rcesoftware.com>:
>>> 
>>> Obviously not supported hardware, but wanted to throw this out in case
>>> it's of use to anyone. I picked up the mid-level CuBox-i2eX
>>> (dual-core, serial over USB,
>>> http://www.solid-run.com/products/cubox-i-mini-computer/cubox-i-specifications/)
>>> model and attempted to load the 12/14/2014 IMX snapshot (via tftp
>>> using SolidRun's Ignition image as the U-Boot source). Logs are below,
>>> let me know if there's any assistance I can in the future. Thanks.
>>> 
(Continue reading)

Brian Conway | 23 Dec 21:43 2014

Boot attempt: SolidRun CuBox-i2

Obviously not supported hardware, but wanted to throw this out in case
it's of use to anyone. I picked up the mid-level CuBox-i2eX
(dual-core, serial over USB,
http://www.solid-run.com/products/cubox-i-mini-computer/cubox-i-specifications/)
model and attempted to load the 12/14/2014 IMX snapshot (via tftp
using SolidRun's Ignition image as the U-Boot source). Logs are below,
let me know if there's any assistance I can in the future. Thanks.

U-Boot SPL 2013.10-rc4 (Oct 27 2014 - 18:17:31)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...

U-Boot 2013.10-rc4 (Oct 27 2014 - 18:17:31)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: WDOG
Board: MX6-CuBox-i
DRAM:  1 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
(Continue reading)

Daniel Bolgheroni | 1 Dec 00:50 2014
Picon

miniroot-sunxi-56.fs on Banana Pi

Hi,

I'm trying to install OpenBSD on a Banana Pi board. So I dd'it the
miniroot-sunxi-56.fs to the SD card and powered the board. This is all I
get:

-------
$ sudo cu -115200 /dev/cuaU0
Connected to /dev/cuaU0 (speed 115200)

U-Boot SPL 2012.10-04277-g7aa9f04-dirty (Mar 28 2013 - 22:17:17)
DRAM: 32MB

-------

Two things comes to mind: and old U-Boot SPL version and the DRAM, which
reports only 32 MB. I tried ArchLinux and it booted, so I can be sure it
isn't a board problem:

-------
$ sudo cu -115200 /dev/cuaU0
Connected to /dev/cuaU0 (speed 115200)

U-Boot SPL 2014.04-10691-g493a12c (Jul 02 2014 - 15:02:40)
Board: Bananapi
DRAM: 1024 MiB
CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
spl: not an uImage at 1600

U-Boot 2014.04-10691-g493a12c (Jul 02 2014 - 15:02:40) Allwinner Technology
(Continue reading)

Ignazio Madonia | 27 Nov 19:19 2014
Picon

(unknown)

*"subscribe arm"*

Edwin Amsler | 20 Nov 23:49 2014
Picon

AHCI problems with Cubieboard A10

Hard drives attached to the SATA port of my Cubieboard aren’t working.

It seems like the hardware is initialized properly, but the drive that is attached to the SATA port never
becomes ready.

For u-boot, I’m using the branch from the sunxi Github repo. It doesn’t come with SATA support compiled
in, so in theory it’s not touching important registers here. I have also used mainline u-boot and tested
that the SATA does work there and that it could read the partition table from different disks (couldn’t
get OBSD to boot there). The hardware shouldn’t be the problem here.

Full `dmesg` output can be found here:
http://pastebin.com/B1Ckzre1

And here’s the relevant bits:
ahci0 at sunxi0 GHC 0x80000000<AE> AHCI 1.1
ahci0: capabilities 0x6726ff80<NCQ,SSNTF,SALP,SAL,SCLO,SAM,SPM,PMD,SSC,PSC,CCCS>, 1 ports, 32
cmds, gen 2 (3Gbps)
ahci0: ports implemented: 0x00000001
ahci0.0: port reset
ahci0: device on port 0 didn't come ready, TFD: 0x80<BSY>
ahci0.0: soft reset
ahci0.0: stopping the port, softreset slot 31 was still active.
ahci0: unable to communicate with device on port 0
scsibus0 at ahci0: 32 targets

Now, what’s the best way to figure out what the problem is here? I’ve started building the kernel so if
someone has patches for me to test with, I’m definitely game to try them out.

Also, is this better to post on a different mailing list?

(Continue reading)

Edwin Amsler | 20 Nov 19:23 2014
Picon

Where is the release of 5.6 for ARMv7 targets?

Is there an official reason why ARMv7 was excluded from the 5.6 release? I’ve got my assumptions, but
I’d like to know if it was a conscious decision or not.

Just curiosity.

Thanks,

Edwin 

Ted Roby | 16 Nov 08:37 2014
Picon

siphash24 on BeagleBone Black Rev. B6

This is a BeagleBone Black board Revision B6.
Running OpenBSD 5.6-current as of 15 November 2014.

When using net/tor:
Tor v0.2.5.10 (git-42b42605f8d8eac2) running on OpenBSD with Libevent
1.4.14b-stable, OpenSSL LibreSSL 2.1 and Zlib 1.2.3.

I can use exit nodes to access external sites like https://check.torproject.org.

But accessing Hidden Services causes a core dump:

Program received signal SIGBUS, Bus error.
0x0010e518 in siphash24 ()
(gdb) bt
#0  0x0010e518 in siphash24 ()
#1  0x00103568 in strmap_set ()
#2  0x00045bf8 in rend_client_cancel_descriptor_fetches ()
#3  0x00045f40 in rend_client_refetch_v2_renddesc ()
#4  0x000bd3cc in connection_ap_handshake_rewrite_and_attach ()
#5  0x000be6e4 in connection_edge_process_inbuf ()
#6  0x000b7f70 in connection_handle_read ()
#7  0x0002b750 in process_signal ()
#8  0x4481f0d4 in event_base_loop (base=0xb7978, flags=0) at
/usr/src/lib/libevent/event.c:350
#9  0x000286a0 in do_main_loop ()
#10 0x000294d4 in tor_main ()
#11 0x00026cc0 in _start ()
#12 0x00000000 in ?? ()

I have reproduced this problem by visiting different http Hidden Services.
(Continue reading)

Tracy Bales | 14 Nov 00:50 2014
Picon

CubieBoard2 (sunxi) boot message...

The developers are getting closer with the sunxi port dated
11/8/14...here's the latest boot message for my CubieBoard2.

After both USB ports are probed, the CubieBoard2 locks up...not sure what's
going on.  There's no panic...just frozen.

U-Boot SPL 2014.01-rc1-09154-gfb357b4 (Jan 07 2014 - 22:30:46)
Board: Cubieboard2
dram: 1024 MiB
CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
spl: not an uImage at 1600

U-Boot 2014.01-rc1-09154-gfb357b4 (Jan 07 2014 - 22:30:46) Allwinner
Technology

CPU:   Allwinner A20 (SUN7I)
Board: Cubieboard2
I2C:   ready
DRAM:  1 GiB
WARNING: Caches not enabled
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   mii0
Warning: failed to set MAC address

Hit any key to stop autoboot:  0
(Continue reading)


Gmane