Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Running on fit-pc2i

    Scheduled Pinned Locked Moved Hardware
    8 Posts 3 Posters 2.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      djzort
      last edited by

      There are a few threads about this, but i wanted to note that in linux the fit-pc2i (and fit-pc2) require this module/kernel boot option

      libata.force=40c

      as apparently poor libata cant get the cable type right.

      it seems in freebsd there are only the following options (as touched on in http://doc.pfsense.org/index.php/Booting_Options)

      hw.ata.setmax: 0
      hw.ata.wc: 1
      hw.ata.atapi_dma: 1
      hw.ata.ata_dma_check_80pin: 1
      hw.ata.ata_dma: 1

      im curious if there is a way of coercing freebsd in to similar behavior as in linux?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        This page seems relevant:
        http://www.pl0rt.org/text/freebsd-on-fitpc-2i/

        Steve

        1 Reply Last reply Reply Quote 0
        • D
          djzort
          last edited by

          thats a great link, thank you!

          1 Reply Last reply Reply Quote 0
          • D
            djzort
            last edited by

            In case this dies of link rot, i found that…

            To install you need to add both these two boot arguments. When prompted at the boot loader, select the prompt and set both of the below options.

            hw.ata.ata_dma=0
            hw.ata.ata_dma_check_80pin=0

            Then type 'boot'

            Infact, even with these settings i had an dma error installing the first time and had to try again.
            Note that the installer doesn't add these options to /boot/loader.conf, so you will have to do that manually.

            At first boot, you will need to once again add this option as a boot argument.

            hw.ata.ata_dma_check_80pin=0

            Then having booted in to pfsense, manually add the above line to /boot/loader.conf manually using vi or echo, or whatever.

            ie.
            echo "hw.ata.ata_dma_check_80pin=0" >> /boot/loader.conf

            1 Reply Last reply Reply Quote 0
            • W
              wallabybob
              last edited by

              Better to change /boot/loader.conf.local than /boot/loader.conf since /boot/loader.conf.local is supposed to survive a firmware upgrade whereas /boot/loader.conf might not.

              1 Reply Last reply Reply Quote 0
              • D
                djzort
                last edited by

                great tip! thanks wallabybob

                i wonder if its ok to create a page on doc.pfsense.org  ?

                1 Reply Last reply Reply Quote 0
                • D
                  djzort
                  last edited by

                  just adding a note, that 2.1-RELEASE doesnt seem to need this any more.

                  though i have not done a clean install, just an upgrade.

                  loader.conf.local seems to be wiped though, when upgrading.

                  1 Reply Last reply Reply Quote 0
                  • D
                    djzort
                    last edited by

                    with regards to the watchdog timer, thread here but i cannot reply http://forum.pfsense.org/index.php?topic=43844.0

                    according to -> http://lwn.net/Articles/342308/

                    its a derivative of the IXP2000 linux driver

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.