Netgate SG-1000 microFirewall

Author Topic: PC Engines apu2 experiences  (Read 44647 times)

0 Members and 1 Guest are viewing this topic.

Offline Veldkornet

  • Jr. Member
  • **
  • Posts: 33
  • Karma: +5/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #120 on: February 08, 2018, 02:45:40 pm »
Well, I decided to have a look at these LED's. Installed the driver, LED's work.
During boot, the LED's all dance, and if I install the gwled package, they show the gateway status. Wonderful :)

Only, I noticed that gwled has a service, but doesn't start... it's annoying. Is this normal? See attachment. (On a sidenote, does anyone else 2x haproxy services?).

Secondly, I noticed the following in the my /var/log/dmesg.boot:

ada0: <Samsung SSD 850 EVO mSATA 250GB EMT41B6Q> ACS-2 ATA SATA 3.x device
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 238475MB (488397168 512 byte sectors)
ada0: quirks=0x3<4K,NCQ_TRIM_BROKEN>

What does this 4K,NCQ_TRIM_BROKEN mean exactly in normal English?

I also note that they have a solution below, but again, not quite sure what the difference is between the two....

Quote
if you're on 11.1-RELEASE or 11-RELEASE, you should add below on /boot/loader.conf.

 If no other quirks is required:
    kern.cam.ada.0.quirks="0x0"

 If you need 4k quirks but want to drop NCQ_TRIM one:
    kern.cam.ada.0.quirks="0x1"

      *4k one is bit0 (0x1), and NCQ_TRIM one is bit1 (0x2).

The example above assumes the affected drive is recognized as ada0.
You should change "ada.0" to whatever appropreate.


Online jwt

  • Administrator
  • Sr. Member
  • *****
  • Posts: 369
  • Karma: +104/-34
    • View Profile
Re: PC Engines apu2 experiences
« Reply #121 on: February 08, 2018, 04:14:42 pm »

What does this 4K,NCQ_TRIM_BROKEN mean exactly in normal English?



4k means "TRIM only works on 4096 byte requests that are 4096 byte aligned".

NCQ_TRIM means TRIM doesn't work if you send it as a queued request.  For some drives, the SSD stops working with first trim request is issued from the filesystem (UFS or ZFS).

There is a bug that is fixed in 11.1-RELEASE.   These quirks keep your drive working.

If you're running pfSense 2.4.x you can re-enable 4K sectors and TRIM by clearing the quirks with:

    kern.cam.ada.0.quirks="0x0"

in /boot/loader.conf

or, if you need 4k quirks but want to drop NCQ_TRIM one:
    kern.cam.ada.0.quirks="0x1"

4k one is bit0 (0x1), and NCQ_TRIM one is bit1 (0x2).


Or you can wait for pfSense 2.4.3, which will contain a software fix.

Offline PiBa

  • Hero Member
  • *****
  • Posts: 840
  • Karma: +133/-1
  • PiBa-NL(on IRC)
    • View Profile
Re: PC Engines apu2 experiences
« Reply #122 on: February 09, 2018, 12:58:39 pm »
On a sidenote, does anyone else have 2x haproxy services?
I havn't seen that before..you should only have the lowercase 'haproxy' service.. Probably need to edit the config.xml to remove the wrong service tag.. (backup>edit>restore)or the more tricky:(edit /conf/config.xml,delete /tmp/config.cache) just make sure to keep the xml format valid..

Offline pvoigt

  • Full Member
  • ***
  • Posts: 251
  • Karma: +1/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #123 on: February 12, 2018, 11:23:29 am »
I am using an APU2C4 with BIOS version 4.0.7.

It looks like PC Engines no longer maintains their web pages under
https://www.pcengines.ch/apu2c4.htm

I am unable to find any binaries for latest versions 4.0.x and 4.6.x and appreciate any hints on that.

All I can find are related release infos/changelogs
https://github.com/pcengines/release_manifests/blob/coreboot-4.6.x/CHANGELOG.md

and source codes of coreboot
https://github.com/pcengines/coreboot/releases

Peter

Offline software

  • Newbie
  • *
  • Posts: 9
  • Karma: +1/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #124 on: February 12, 2018, 02:12:48 pm »
I see some ROMs on the github:
https://github.com/pcengines/apu2-documentation

APU2 ROM should be there in legacy and mainline mode

Offline pvoigt

  • Full Member
  • ***
  • Posts: 251
  • Karma: +1/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #125 on: February 12, 2018, 02:51:29 pm »
I see some ROMs on the github:
https://github.com/pcengines/apu2-documentation

APU2 ROM should be there in legacy and mainline mode

Yeah, thanks a lot. Nevertheless, these are not the latest versions. I would have never searched for binaries in the documentation folder ;-).

Offline valnar

  • Sr. Member
  • ****
  • Posts: 378
  • Karma: +0/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #126 on: February 12, 2018, 06:10:31 pm »
Wow, I'm running 4.07.  Any reason to go higher for pfSense?  What's the recommended BIOS?

Offline kevindd992002

  • Sr. Member
  • ****
  • Posts: 409
  • Karma: +5/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #127 on: February 13, 2018, 01:23:42 am »
I thought 4.07 is the latest?

Offline pvoigt

  • Full Member
  • ***
  • Posts: 251
  • Karma: +1/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #128 on: February 13, 2018, 04:48:14 am »
I thought 4.07 is the latest?

No, development is going on. Unfortunately, version schema is confusing and PC Engines does not update their corresponding web page. Moreover, binaries are at least for me, difficult to find.

What I have understood so far: There are two actively developed branches: 4.0.x denoted as "legacy" and a "mainline" 4.5.x/4.6.x. Latest versions are 4.0.14 and 4.6.6, respectively. Latest binary downloads for APU2 are available as 4.0.11 and 4.6.1.

One thing that I have just become aware of: coreboot determines the version number of the APU2 BIOS ROM but the APU2 ROM consists of several other components with its own version numbers like e.g. seabios and ipxe.

Offline valnar

  • Sr. Member
  • ****
  • Posts: 378
  • Karma: +0/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #129 on: February 13, 2018, 05:44:22 am »
I guess I should have read outside of the PCEngines website!  Thanks for that info.

OK, so has everyone successfully run 4.6.6 or should I just go to 4.0.11?

Offline kevindd992002

  • Sr. Member
  • ****
  • Posts: 409
  • Karma: +5/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #130 on: February 14, 2018, 01:37:36 am »
I thought 4.07 is the latest?

No, development is going on. Unfortunately, version schema is confusing and PC Engines does not update their corresponding web page. Moreover, binaries are at least for me, difficult to find.

What I have understood so far: There are two actively developed branches: 4.0.x denoted as "legacy" and a "mainline" 4.5.x/4.6.x. Latest versions are 4.0.14 and 4.6.6, respectively. Latest binary downloads for APU2 are available as 4.0.11 and 4.6.1.

One thing that I have just become aware of: coreboot determines the version number of the APU2 BIOS ROM but the APU2 ROM consists of several other components with its own version numbers like e.g. seabios and ipxe.

Oh I see. So everything is on github? I remember choosing between 4.0.x and 4.5.x before and many people we're having problems with 4.5.x for some reason. And this is why I chose to go with 4.0.7. Did this change now? Would it be recommended to go with the mainline this time?

I guess I should have read outside of the PCEngines website!  Thanks for that info.

OK, so has everyone successfully run 4.6.6 or should I just go to 4.0.11?

Me too! All along I thought their website was updated.

Offline valnar

  • Sr. Member
  • ****
  • Posts: 378
  • Karma: +0/-0
    • View Profile
Re: PC Engines apu2 experiences
« Reply #131 on: February 14, 2018, 05:37:28 am »
I just went to 4.0.11 and it's working fine.  I didn't see anything listed in the bios's after 4.0.11 that was relevant to APU2 boards.

I also noticed that PC Engines recommends the 4.0x track here:
http://pcengines.ch/howto.htm#bios