Laurence Rochfort | 18 Aug 11:45 2014

Cubietruck/Cubieboard 3 support

Hello all,

I can't find reference to Cubietruck/Cubieboard 3 in the mailing list
archive, or on the OpenBSD website.

Has this been tested at all? Is it likely that it would work enough to
provide gigabit ethernet and SATA?


Sacha El Masry | 13 Aug 16:50 2014

Zaurus: current level of support

I have had OpenBSD 4.2 on the Zaurus C3100 for years now, and in need of
further (latest) software, I decided to upgrade.

There are at least three problems that did not exist on 4.2:

1. When the system gets to the 'boot>' prompt, it fails, as it's unable
to find /bsd, for whatever reason. Of course, I just load the Linux
partition with the 'b' and 'd' key combination, and run:

  $ insmod zbsd...
  $ cp bsd /proc/zboot

and it's off, booting as it always used to, after which everything works
as usual.

2. When the device comes out of sleep/suspend, it never brings back the
backlight, forcing the following:

  $ wsconsctl display.backlight=100

which is a tad inconvenient, as I may not be in a shell (having
suspended with the lid), and as the keyboard isn't exactly accurate,
often sending more than one character for one keypress.

3. X just doesn't work-it tries to load, returning half a minute later
with an error message.

While none of these are complete show-stoppers, the booting always
worked fine, in all the versions up to 4.2, the backlight wasn't a
problem, and X worked. On the other hand, it is nice that the SD card is
(Continue reading)

Laurence Rochfort | 8 Aug 16:50 2014

Video support in armv7


I don't see reference to any kind of video support for the devices
listed on the armv7 page. Is there support of any kind?


Mike Bregg | 1 Aug 19:35 2014

Beaglebone Black Rev C internal mmc I/O errors


I'm trying to install the latest armv7 snapshot (June 18) on the 
internal 4GB mmc of a Beaglebone Black Rev C.  The mmc is recognized by 
the installer, but when the installer tries to create the disklabel, it 
spits out a bunch of I/O errors.

Installing on an SDCard (sd0) works perfectly fine, and I should note 
that installing Arch Linux on the internal nand works as well, so I 
don't think it's a hardware issue.  I also tried 5.5 release with the 
same results.

Does anyone have any suggestions or pointers?  I found a similar thread 
on Google, but it was from Dec 2013, and there didn't appear to be a 

Relevant info from the serial console below.


Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) [sd0] sd1
Use DUIDs rather than device names in fstab? [yes]
fdisk: sd1: Input/output error
MBR has invalid signature; not showing it.
Use (W)hole disk or (E)dit the MBR? [whole]
Creating a msdos partition and an OpenBSD partition for rest of 
sd1...fdisk: sd1: Input/output error
(Continue reading)

Jim Winiger | 31 Jul 03:22 2014

Monsanto and Farm Bureau "Guilty of Class C Felony Forgery"

Monsanto & Farm Bureau "Guilty of Class C Felony Forgery" of my
signature! . . . . Jim Winiger

Posey County Indiana Prosecutor, Trent VanHaaften, said this is a "Class
C Felony Forgery" Punishable by 2 to 8 years in Prison

This group was never charged, they were protected by the Posey Superior
Court "The Dishonorable Judge James Redwine" and his friend, Evansville,
Indiana Attorney Larry Daly.

To read about and view the Forgeries, click here>> Monsanto - Farm Bureau
- Winiger Home

This message is in Compliance with the US CAN-SPAM Act of 2003

This is an Informational Message, not a Commercial Advertisement

Neoklis Kyriazis | 24 Jul 08:34 2014

Re: miniroot-am335x-55.fs installing to BeagleBone Black: no sd1

>>  No idea, this works fine on my BeagleBone Black (rev. A5C).
>>  Can you send a dmesg?

Here is dmesg as produced after booting the miniroot. I added
(from memory) a message I just caught at the very start of boot:

WARNING: No entropy supplied by boot loader
NAND: No NAND device found!!!

# dmesg
OpenBSD 5.5-current (RAMDISK-OMAP) #1: Mon Jun 16 22:16:25 EDT 2014
    root <at>
real mem  = 536870912 (512MB)
avail mem = 515153920 (491MB)
warning: no entropy supplied by boot loader
mainbus0 at root
cpu0 at mainbus0: ARM Cortex A8 R3 rev 2 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0: BeagleBone
prcm0 at omap0 rev 0.2
sitaracm0 at omap0: control module, rev 1.0
intc0 at omap0 rev 5.0
omap0: device edma unit 0 not configured
dmtimer0 at omap0 rev 3.1
dmtimer1 at omap0 rev 3.1
omdog0 at omap0 rev 0.1
omgpio0 at omap0: rev 0.1
omgpio1 at omap0: rev 0.1
omgpio2 at omap0: rev 0.1
(Continue reading)

Neoklis Kyriazis | 22 Jul 18:36 2014

miniroot-am335x-55.fs installing to BeagleBone Black: no sd1


I am trying to install the latest arm7 snap on a BeagleBone Black
using miniroot-am335x-55.fs but it only offers sd0 (the SD card)
for installation. I installed to the SD card OK and the build-in
emmc is visible as /dev/sd1.

From (poor!) memory, the installation kernel gave a message that
it failed to enable the built-in emmc. I had tried a 5.4 snapshot
and I remember I was able to install to the built-in emmc. Any 

idea what causes the problem, or what I may be doing wrong?

Thank you.


Best Regards 

Neoklis - Ham Radio Call: 5B4AZ

Mike Bregg | 15 Jul 22:12 2014

Re: Cubieboard2 Again

On 2014-07-15 10:42, Patrick Wildt wrote:
> Hi,
> The U-Boot used might not be suitable for the A20, only for the A10.
> You can probably look for a newer one which works on both on the
> intarwebs or compile yourself a new one using the maker’s u-boot git
> sources.  After you flashed the sunxi miniroot, overwrite parts of it
> using the proper u-boot. Then it should work better.
> \Patrick

Hi Patrick,

Thanks for your suggestion.  The boot process begins now, but it seems 
to be hanging after probing the usb devices:

OpenBSD 5.5-current (RAMDISK-SUNXI) #1: Mon Jun 16 22:29:53 EDT 2014

root <at>
real mem  = 1073741824 (1024MB)
avail mem = 1036132352 (988MB)
warning: no entropy supplied by boot loader
mainbus0 at root
cortex0 at mainbus0
ampintc0 at cortex0 nirq 160
cpu0 at mainbus0: ARM Cortex A7 rev 4 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(32b/l,2way) I-cache, 32KB(64b/l,4way) wr-back D-cache
sunxi0 at mainbus0: A20
sxipio0 at sunxi0
(Continue reading)

Mike Bregg | 15 Jul 17:59 2014

Cubieboard2 Again


I was just wondering if anyone has had any success getting OpenBSD 
installed on a Cubieboard2 (A20).  According to, it should be supported.  I see some 
posts from a few months ago on this list, but no updates since then, and 
Google is yielding little.

I've tried writing both 5.5 release, and the latest snapshot (June 18) 
to a couple of SD Cards, but the same as previous post from April 27, I 
only see the following output from the serial console when I boot the 

U-Boot SPL 2012.10-04280-g1a8ac55 (May 23 2013 - 14:01:59)

and then the system hangs.

Any advice or suggestions are appreciated.


Matthieu Herrb | 29 Jun 16:32 2014

fix multicast filter on imxenet(4)


The patch below is from brad <at> . It corrects the input filter on
imxenet(4) to correctly let multicat packets through.

With this patch my sabre lite board is able to auto-configure IPv6
correctly and do neighbour discovery.

Inspired by the FreeBSD driver


PS: Brad, I don't want to steal the commit from you. If someone ok's
the diff, please commit it if you can.

Index: imxenet.c
RCS file: /cvs/OpenBSD/src/sys/arch/armv7/imx/imxenet.c,v
retrieving revision 1.4
diff -u -p -u -r1.4 imxenet.c
--- imxenet.c	6 Nov 2013 19:03:07 -0000	1.4
+++ imxenet.c	29 Jun 2014 14:25:05 -0000
 <at>  <at>  -477,10 +477,6  <at>  <at>  imxenet_init(struct imxenet_softc *sc)
 	/* clear outstanding interrupts */
 	HWRITE4(sc, ENET_EIR, 0xffffffff);

-	/* set address filter */
-	HWRITE4(sc, ENET_GAUR, 0);
-	HWRITE4(sc, ENET_GALR, 0);
(Continue reading)

patrick keshishian | 27 Jun 06:58 2014

gpioctl on beaglebone black


I'm trying to play with the GPIO on bbb. I must be
misunderstanding how this is supposed to (expected)
to work.

I've been looking through the gpioctl (gpio) manuals,
but i'm still confused, and could use a pointer.

here is a demo:

# gpioctl gpio1 7
pin 7: state 1

# gpioctl gpio1 7 off
pin 7: state 1 -> 0

# gpioctl gpio1 7
pin 7: state 1


# gpioctl gpio1 7 off
pin 7: state 0 -> 0

err... help?


# sysctl kern.version
(Continue reading)