Realtek Driver Suddenly Not Working



  • I'm currently running the 2.2.4-RELEASE. Sometime this week, I updated from a version between 2.2.0 - 2.2.3 to 2.2.4, and didn't notice any immediate issues. Today, I wanted to upgrade one of the NICs in my box, so I brought it down, added the NIC and powered back up. Now, the onboard Realtek NIC that I was using for my WAN connection is no longer showing. Dmesg shows the following:

    
    [2.2.4-RELEASE][admin@nihilanth.grossnet]/: dmesg | grep -i re0
    re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0x2000-0x20ff irq 16 at device 0.0 on pci1
    pcib1: allocated prefetch range (0xe0100000-0xe0100fff) for rid 18 of re0
    re0: Lazy allocation of 0x1000 bytes rid 0x18 type 3 at 0xe0100000
    re0: MSI count : 1
    re0: MSI-X count : 4
    pcib1: allocated prefetch range (0xe0104000-0xe0107fff) for rid 20 of re0
    re0: Lazy allocation of 0x4000 bytes rid 0x20 type 3 at 0xe0104000
    re0: attempting to allocate 1 MSI-X vectors (4 supported)
    re0: using IRQ 257 for MSI-X
    re0: Using 1 MSI-X message
    re0: Chip rev. 0x54000000
    re0: MAC rev. 0x00000000
    re0: Unknown H/W revision: 0x54000000
    device_attach: re0 attach returned 6</realtek> 
    

    Based on a few similar issues I've seen on the pfsense forms and elsewhere, it looks like something happened with the re module. Some people report that rebuilding the module fixes the issue; but I don't have the first clue how to do this on pfsense (I would assume I don't even have the sources downloaded). How can I rebuild this module (if needed)? Also, has anyone run into this before, or does anyone have any ideas of how I could attempt to fix this? I'm running Okay at the moment (the upgraded NIC went from a single port to a dual port, so I'm online using only the add-on NIC), but I would like to get the onboard online.

    Thanks for any help, I didn't expect my short weekend update to turn into a project; but I guess that stuff like this happens all the time  :P



  • I'm having the exact same issue on a fresh install of 2.2.6:

    
    [2.2.6-RELEASE][admin@pfSense.kuriyasu.home]/root: dmesg |grep re0
    re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xe000-0xe0ff mem 0x81204000-0x81204fff,0x81200000-0x81203fff irq 18 at device 0.0 on pci3
    re0: Using 1 MSI-X message
    re0: ASPM disabled
    re0: Chip rev. 0x54000000
    re0: MAC rev. 0x00100000
    re0: Unknown H/W revision: 0x54000000
    device_attach: re0 attach returned 6</realtek> 
    

    I tried compiling the the if_re.ko module on a FreeBSD 10.1 box and moving the file over to /boot/kernel and loading it manually, but it appears the module is compiled into the pfSense kernel already:

    
    [2.2.6-RELEASE][admin@pfSense.kuriyasu.home]/boot/kernel: kldload if_re
    kldload: can't load if_re: module already loaded or in kernel
    
    

    Any help would be appreciated.  I'm using other NICS currently for LAN/WAN, but would like to be able to use the built in NIC as a dedicated management port.


Log in to reply