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

    Reverting from 23.5 to 2.7.2 breaks when using my RealTek 2.5GB NICs

    Off-Topic & Non-Support Discussion
    2
    8
    362
    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.
    • M
      mark_lab_user
      last edited by

      I was going to upgrade to 23.09.1 but that would now cost me an annual fee so I am going back to the CE version 2.7.2 with a fresh install.
      Did this to ensure I was up-to-date especially with regards to Openssl 3.x.

      Then I added the latest Realtek kernel module realtek-re-kmod-199.00_1 package.
      I does NOT work.

      So I installed FreeBSD 14 and hauled in all the updates and got to 14-RELEASEi-p5 and then installed the aforementioned driver.
      It works. All this on the same Motherboard just to make sure my hardware had not failed.

      I wonder what I am doing wrong with pfSense. I guess I have a kernel mismatch error.

      Not sure where to begin because I don't have any old Intel 1GB Nics sitting around. (Stupid me, I purged old stuff from my junk drawers).

      Please see my post from mid year 2023 regarding the Realtek cards working well previously.

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

        @mark_lab_user said in Reverting from 23.5 to 2.7.2 breaks when using my RealTek 2.5GB NICs:

        Then I added the latest Realtek kernel module realtek-re-kmod-199.00_1 package.
        I does NOT work.

        That isn't the pkg from 2.7.2:

        [2.7.2-RELEASE][admin@t70.stevew.lan]/root: pkg search realtek
realtek-re-kmod-198.00_3       Kernel driver for Realtek PCIe Ethernet Controllers

        You have to use the pkg from 2.7.2 otherwise the module wont match the kernel and won't load.

        Steve

        M 1 Reply Last reply Reply Quote 1
        • M
          mark_lab_user @stephenw10
          last edited by

          @stephenw10 Thank you. I will try again. Makes sense to me. Just did not know how to troubleshoot.

          1 Reply Last reply Reply Quote 1
          • M
            mark_lab_user
            last edited by

            Up and running with the Realtek 2.5GB NICs.

            This is solved!

            Thank you to stephenw10 !

            We are very fortunate to have great community support !

            I do see a problem on the console that I don't get with FreedBSD14...

            Timeouts on boot up. Not a show stopper but maybe I have a potential hardware issue lurking.
            Mar 12 15:17:00 pfSense2 php-cgi[530]: rc.bootup: Resyncing OpenVPN instances.
            Mar 12 15:17:00 pfSense2 kernel: done.
            Mar 12 15:19:30 pfSense2 kernel: re1: link state changed to DOWN
            Mar 12 15:19:30 pfSense2 kernel: ahcich1: Timeout on slot 6 port 0
            Mar 12 15:19:30 pfSense2 kernel: ahcich1: is 00000000 cs 00000000 ss 00000040 rs 00000040 tfd 50 serr 00000000 cmd 0000ce17
            Mar 12 15:19:30 pfSense2 kernel: (ada0:ahcich1:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
            Mar 12 15:19:30 pfSense2 kernel: (ada0:ahcich1:0:0:0): CAM status: Command timeout
            Mar 12 15:19:30 pfSense2 kernel: (ada0:ahcich1:0:0:0): Retrying command, 3 more tries remain

            Thinking that the Mobo is good still after all these years. It is a classic ASRock Z87 Pro3 with intel i7 and 8 cores but maybe the SSD is old or somewhat degraded.
            I get the CAM timeouts with FreeBSD14 but they are short-lived and I don't get the ahcich1 messages. But I do with pfSense as seen above

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

              Yup that is a drive or drive controller error. I have had SSDs that showed similar drive errors but never actually failed. However it did occasionally cause it to fail to boot. Not a huge problem on a test box but unacceptable for anything 'production'.

              M 1 Reply Last reply Reply Quote 1
              • M
                mark_lab_user @stephenw10
                last edited by

                @stephenw10 Hey, that is good news that you confirmed my hypothesis. I don't feel so dumb now.

                Thanks muchly.

                M 1 Reply Last reply Reply Quote 0
                • M
                  mark_lab_user @mark_lab_user
                  last edited by

                  @mark_lab_user

                  Now for a really dumb question. Does this forum allow direct messaging?

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

                    There is a chat facility that serves that function. It's generally better to keep things public though so others can benefit or contribute.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post