[talk] [nycbug-talk] APU

Sun Apr 6 19:47:23 EDT 2014

On Sun, Apr 6, 2014 at 5:58 PM, Jared Davenport <jared at thegridsource.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 04/06/2014 04:20 PM, George Rosamond wrote:
>> Jared Davenport:
>>>
>>>
>>> On 04/06/2014 02:21 PM, George Rosamond wrote:
>>>> Jared Davenport:
>>>>>
>>>>>
>>>>> On 01/09/2014 10:13 AM, George Rosamond wrote:
>>>>>> Jared Davenport:
>>>>>>>
>>>>>>>
>>>>>>> On 12/19/2013 10:45 AM, George Rosamond wrote:
>>>>>>>> Jared Davenport:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 12/18/2013 11:45 PM, Jim B. wrote:
>>>>>>>>>> * Jared Davenport <jared at thegridsource.com>
>>>>>>>>>> [2013-12-18 22:57]:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 12/18/2013 09:11 PM, Jim B. wrote:
>>>>>>>>>>>> * Jared Davenport <jared at thegridsource.com>
>>>>>>>>>>>> [2013-12-18 12:20]:
>>>>>>>>>> [snip]
>>>>>>>>>>> Thanks Jim,
>>>>>>>>>>>
>>>>>>>>>>> I went ahead and added those lines.  Here is the
>>>>>>>>>>>  verbose output:
>>>>>>>>>>>
>>>>>>>>>>> http://pastebin.com/DUhrt8uP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Ok, I didn't see anything odd.  I would note
>>>>>>>>>> however that FreeBSD 10-RCx is still undergoing
>>>>>>>>>> fixes prior to release.
>>>>>>>>>>
>>>>>>>>>> pfsense 2.1 (latest stable version) is actually
>>>>>>>>>> based on FreeBSD 8.3 according to the release
>>>>>>>>>> notes.
>>>>>>>>>>
>>>>>>>>>> If all you want to do is get your board to run
>>>>>>>>>> FreeBSD, try installing a slightly older version -
>>>>>>>>>> 9.1, 9.2, or even 8.3 directly.
>>>>>>>>>>
>>>>>>>>>> Releases for amd64 are at:
>>>>>>>>>>
>>>>>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/
>>>>>>>>>
>>>>>>>>> Good call on that.  I tried the same configuration,
>>>>>>>>> with FreeBSD 8.4, and it worked!
>>>>>>>>>
>>>>>>>>> FreeBSD 8.4 dmesgd:
>>>>>>>>> http://www.nycbug.org/?action=dmesgd&dmesgid=2505
>>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks for posting JD!
>>>>>>>>
>>>>>>>>> FreeBSD 9.2 and FreeBSD 10 were a no-go.  I'm still
>>>>>>>>> not sure why.
>>>>>>>>
>>>>>>>> Well, the obvious to me would be using mbr v gpt.
>>>>>>>>
>>>>>>>> What does the BIOS look like?  That could very much
>>>>>>>> matter.
>>>>>>>
>>>>>>> That very well could be it.  The BIOS says it's coreboot
>>>>>>>  2.08.00, specifically,
>>>>>>> coreboot-EDK_2.08.00_20130410_221-1434-g871c820-dirty
>>>>>>>
>>>>>>> I've added the BIOS message here:
>>>>>>> http://pastebin.com/111eTfZm
>>>>>>>
>>>>>>>>
>>>>>>>> also, for troubleshooting, I believe that these two
>>>>>>>> should help in the /etc/rc.conf:
>>>>>>>>
>>>>>>>> rc_debug="YES" rc_info="YES"
>>>>>>>>
>>>>>>>> I need to get my hands on one or more of these too...
>>>>>
>>>>>> Reraising the thread...
>>>>>
>>>>>> Did you order through a reseller in the US or through PC
>>>>>> Engines directly?  Pricing?
>>>>>
>>>>>> I have a bunch of place I could start using these in the
>>>>>> very near-term.. replacing a lot of older Soekrii and
>>>>>> Alixen.
>>>>>
>>>>>> g
>>>>>
>>>>> If you're still interested, the APU1C is now in production
>>>>> and available for pre-order.
>>>>>
>>>>> http://www.pcengines.ch/order1.php?c=4 or
>>>>> http://store.netgate.com/PC-Engines-C69.aspx
>>>>>
>>>>> Specs: from http://www.pcengines.ch/apu1c.htm
>>>>>
>>>>> I'm not sure if the FreeBSD ?9 boot problem was ever sorted
>>>>> out on the production model.
>>>>>
>>>
>>>> Yes... I'm just waiting on delivery at this point.
>>>
>>>> How are people doing installs?  Off install media directly?
>>>> Netboot? Building an image and dd'g to the microsd card?
>>>
>>> The APU I have came with a 16gb mSATA SSD (msata16a).  I
>>> installed both FreeBSD & pfSense using a USB stick with the
>>> memstick install image, which I modified to boot into the serial
>>> console.
>>
>> Cool.  But you couldnt book FBSD 10.x or -current, right?
>>
>> Was that resolved?
>
> FreeBSD 9, 10, and -CURRENT were unable to boot when I tested.  John
> Baldwin helped figure out that it was probably an ACPI problem with
> the firmware on the test APU, which was preventing later versions of
> FreeBSD from loading, but I'm not sure if the issue's been resolved on
> the production model.  It would be nice to check.

I don't follow this stuff closely, but there have been issues with the
BIOS being broken, up to just last week or so when a fixed BIOS was
finally released.

>>> It would be nice if we have APU-specific images that we can just
>>> dd to a SD/mSATA/USB device.
>>>
>>
>> Sure... very nice.
>>
>> I know gjb@ has been working on RPi images.  There is really too
>> much hardware out there to start doing images for, with too many
>> FreeBSD branches that are live, on too many architectures.
>>
>> RPi has a 'flavor of the day' feel (or did?) that it does sorta
>> justify doing images for.
>>
>>>
>>>> also pfsense... all fine?  It's 8.x, so any later problems
>>>> shouldn't matter.
>>>
>>> When I tested pfSense on the APU, it worked fine.  FreeBSD 8.x
>>> also booted ok.
>>
>> k.
>>
>> g _______________________________________________ talk mailing
>> list talk at lists.nycbug.org
>> http://lists.nycbug.org/mailman/listinfo/talk
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTQc4WAAoJEHIvhc7WejMgVEsIAJ3UvsfVPLp1+H9rId4FIcOO
> AWJuuh9DXISLNTZXCWA4M2Lj/iY8LdaDnTQ+CXW/ADj2PwWMREMdTBApv9bD1TZ8
> AvUTfpJASmzI17oT6o1UVcvWcOi5Z/meV9uPrnJCx6CjQXLPFU+qR6B0/zLXxbw9
> EI5oRerikBnDPmDPWrbrUQY8oMsjea222HwiMRuD4wCSFuxcu+AaCxC6RLMt/BI/
> coqsyBdNn478EUsegCRRBubdpDkmmGtlfPOgFWfVaLzGLyDtHy8eCh4g7Qf537ZQ
> 0+hJWLlqYDH6QcKfvbGuoXW9Q5bICj5LrIZPq/dqqfaEs6B6NlxqnOOPKQvCTFs=
> =UVVZ
> -----END PGP SIGNATURE-----
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org/mailman/listinfo/talk