P5GC and Lan cards drive me crazy!
gsp last edited by
I am trying to install 2.0.1 pfsense on ASUS P5GC having on board 5 USRobotics 7902A Gigabit LAN PCI… Everything seems FINE! The system sees the cards they are getting IP's interfaces UP but NO NETWORK COMMUNICATION!!!! no ping.. nothing... ifconfig shows normal info... The only card that is operating normally is the onboard lan!!!!!!!.. Tried to exchange USRobotics with DLink DGE-528T and happens the same!!! I have the latest bios installed... The strange thing is that with previous versions of PFsense it was happening like the opposite.. all PCI USRobotics were working and the onboard didn't BUT the onboard wasn't recognized as hardware which was normal...
Those USR cards are actually Realtek 8169 NICs from some Googling, does that seem correct?
The D-Link DGE-528T is also a Realtek 8169 card so swapping it is not a good test.
When you say older version do you mean 2.0 or 1.2.3?
gsp last edited by
Hi Steve, thanks for your answer, actually USRobotics are RTL8169S but Dlink ones write on the chip DLG10028C it seems to be D-Link chipset? i am not sure…. Yes i mean 1.2.3 version... Now the update is this... I tried DLink card on a Small Factor HP workstation and voila! it works!!.. So maybe its the motherboard? But HOW is it explained that version 1.2.3 works just fine and ver 2.0.1 not? Now on the HP i have other problem even that i partitioned my HD to use 20GB from 160 it stucks on installation on 38% staying there forever!!... :(
wallabybob last edited by
Now on the HP i have other problem even that i partitioned my HD to use 20GB from 160 it stucks on installation on 38% staying there forever!!… :(
The universe has not yet ended so you are exaggerating, at least a little, in saying "forever". I recall my fresh installation of pfSense 2.0.1 from USB stick seemed to be stuck on 38% long enough for me to think it had hung. You might need to be a bit more patient. I suspect waiting an hour should be more than enough. I didn't record how long I waited and I haven't repeated it to time the wait at 38%.