After upgrade no nics found in system

cmb

Information about the NICs is necessary to offer any useful suggestions.

stephenw10

Well we know that is motherboard is this so we know the on-board NIC, despite it being an Intel board, is a Realtek 8111E. No reason for that to disappear. No reason for either to disappear though. Something more fundamental happening here.

Steve

kejianshi

Boot this thing on 2.15 to see if its a software or hardware problem.

Or hey… Lets chat about it a few more days?

nambi

This is a very strange issue, I booted to 2.1.5 both nics detected without issues. backed up. then I read a post about doing this.

hint.agp.0.disabled=1
in loader.conf

so i reinstalled 2.2 to try, this time my nic were detected. I was able to reboot and get pf sense up and running on 2.2,. i then tried to set the nics up again and sure enough they do no detect.
but since I had already saved the info pf sense will boot, I also logged in via gui and I can see both nics are online, when i disconnect any of the cat5's they show offline so they are working but if I setup the nics again they fail to detect.

I would like to alter the loader.config but when I putty into the unit using root and the pfsense path I then go into "shell" I can't seem to locate the the loader.config I can't seem to find the /boot folder

I can now get this to function but I'm afraid if I ever have to reset the nics, I won't be able to.

REaltek 8168/1811 onboard and intel pro/1000 GT 82558 chipset on a riser

screenshot.jpg_thumb

kejianshi

So, run 2.15 abit longer and give the devs a little time to sort it out.

Try again at 2.21 which I'd assume is as sure to come as death and taxes.

stephenw10

@nambi:

I was able to reboot and get pf sense up and running on 2.2,. i then tried to set the nics up again and sure enough they do no detect.

This is a confusing statement. Please define exactly what you mean by 'no detect'. Why did you try to set them up again? Where are you doing that?

Are you trying to using the auto-detect function at the initial setup interfaces screen? Are the two NICs listed above that as valid interfaces?

Steve

phil.davis

I would like to alter the loader.config but when I putty into the unit using root and the pfsense path I then go into "shell" I can't seem to locate the the loader.config I can't seem to find the /boot folder

cd /boot
ls -l loader*

You should put your own changes in loader.conf.local - if it does not already exist, you can easily create an empty one:

touch /boot/loader.conf.local

You can edit it from the command prompt, if you are happy with that, or just go to Diagnostics->Edit File on the web GUI and load and edit it there.

And answer the questions from stephenw10 above - we really need to know if it is just the auto-detect up/down stuff that is not working, or if your NICs are not detected at all…

nambi

I'm up and running (kind of)
thank you, this problem was so tempermental I really don't understand what fixed it, but I did put the suggested fix in the loader.config.local
I'm up and both nic are detected.

I restored from backup the full system (without package info) but many services from the packages still remained and didn't start. I tried to clean up some old packages that didn't work, by reinstalled ontop then removed them and they came out.

for some reason my gui is gone and I get a 503 - Service Not Available. I will reboot and try but I can't do it now too many people already on my back about the downtime.

I really appreciate the help
the nics were being detected upon boot but the autodetect was NOT recognizing them, and when I manually entered the name it also wouldn't accept it.

phil.davis

loader.config.local

For reference of future readers, the correct name of this file is:

loader.conf.local

I guess that nambi has edited the correct file, but just typed the name wrong in the post.

nambi

yes I did thanks for the correction.