PfSense 2.2 on an X750e - network drivers required?



  • On previous versions of pfSense there have been issues with the network drivers and there were alternative if_sk and if_msk drivers available from https://sites.google.com/site/pfsensefirebox/home. Is an equivalent still required?

    Also is the hw.msk.msi_disable=1 line still needed in /boot/loader.conf?

    Thanks,

    Steve


  • Netgate Administrator

    There are drivers here that seem to work fine:
    https://forum.pfsense.org/index.php?topic=20095.msg460754#msg460754

    And yes still disable MSI.

    However just a quick report that my home X750e failed to upgrade. It failed to reboot with this error:

    (ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 6e 7e 77 40 00 00 00 00 01 00
    (ada0:ata0:0:0:0): CAM status: Command timeout
    (ada0:ata0:0:0:0): Error 5, Retries exhausted
    ata0: DMA limited to UDMA33, controller found non-ATA66 cable
    

    So you might want to add the new values that disable DMA to your loader.conf.local file so they are copied across:
    https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes

    Also, inexplicably, probably just a coincidence but I most msk3 completely.  :-\

    Steve



  • Hi Steve,

    Thanks. I'll copy over those drivers. The standard ones seem to be working, but I'll update once I'm past the other issues.

    In order to get squid and lcdproc to install I had to disable package signature checking. Not sure why that would be. Can't think it's specific to my config, and surely upgrade of those will have been tested. lcdproc still won't start (seeing timeouts) and squid is refusing to proxy.  :-\

    I too had the ATA issue but by the time that happened editing the /boot/loader.conf.local file was a bit tricky.

    Simply stop the boot and type the following at the OK prompt.

    set hint.ata.0.mode=PIO4
    boot
    

    Once you're up and running add the following to /boot/loader.conf.local.

    hint.ata.0.mode=PIO4
    

    Steve



  • @stephenw10:

    There are drivers here that seem to work fine:
    https://forum.pfsense.org/index.php?topic=20095.msg460754#msg460754

    And yes still disable MSI.

    However just a quick report that my home X750e failed to upgrade. It failed to reboot with this error:

    (ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 6e 7e 77 40 00 00 00 00 01 00
    (ada0:ata0:0:0:0): CAM status: Command timeout
    (ada0:ata0:0:0:0): Error 5, Retries exhausted
    ata0: DMA limited to UDMA33, controller found non-ATA66 cable
    

    So you might want to add the new values that disable DMA to your loader.conf.local file so they are copied across:
    https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes

    Also, inexplicably, probably just a coincidence but I most msk3 completely.  :-\

    Steve

    I lost one to this.  Had a 4G cf card in it.

    You mean lost?  Im going to the site where my 550 with the MSK interface card is later.  Ill see if I get the same results.


  • Netgate Administrator

    @chpalmer:

    You mean lost?

    I mean after I hooked up the console, noted the error and switched back to the previous slice msk3 no longer appeared in the boot log. That meant it still would boot because it stopped at the prompt asking me to reassign the interfaces. That gets ugly though because you have to assign them in order so with one less available you can only leave off the last one. Also PPPoE interfaces don't back up nicely after you've reassigned WANs.  :-
    Should have kept a cold spare! Or an HA pair.  ;)

    Since I've had an x550e running 2.2 for sometime I didn't foresee any issues but it was a fresh install.

    Steve



  • Hi Stephen,

    Have you checked those drivers with 2.2? I had some issues when I tried them, but I shall have another go. Is it just the LED behaviour that changed or something else?

    Steve


  • Netgate Administrator

    I was running them on my test box with various 2.2 betas/rcs with no problems. I've not tried them on 2.2 release yet. As far as I know the only change was to the led registers but I didn't compile the binaries.  ;)

    Steve



  • @Steve:

    Hi Steve,

    Thanks. I'll copy over those drivers. The standard ones seem to be working, but I'll update once I'm past the other issues.

    In order to get squid and lcdproc to install I had to disable package signature checking. Not sure why that would be. Can't think it's specific to my config, and surely upgrade of those will have been tested. lcdproc still won't start (seeing timeouts) and squid is refusing to proxy.  :-\

    I too had the ATA issue but by the time that happened editing the /boot/loader.conf.local file was a bit tricky.

    Simply stop the boot and type the following at the OK prompt.

    set hint.ata.0.mode=PIO4
    boot
    

    Once you're up and running add the following to /boot/loader.conf.local.

    hint.ata.0.mode=PIO4
    

    Steve

    for us new users once you break the boot and enter the lines above how do you boot? what the command to boot…..


  • Netgate Administrator

    Once you enter 'boot' and press return it should continue booting.

    Steve