2.4.4 fails upgrade and fresh installation

jbhowlesr

@jimp if I do this and if i get a prompt, I’m unclear as to what I need to do with this file that’s been mentioned

/boot/loader.conf.local

Rico

-Rico

jbhowlesr

@rico

Perfect. This is exactly what I have been asking for. Thank you so much.

On my way home and will give that a shot when I get there.

jbhowlesr

@rico

Big shout out here cause this worked and the system is installing now.

I’ll post again after it’s all up and running and report any further issues

jbhowlesr

@rico

Sir, pfsense is running great. However, anytime a reboot occurs, I gotta enter the disable=1 string in your photo. How do I automate this so it can reboot unattended?

Rico

Now to make it persistent run
echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
after booting from console or SSH.

-Rico

jbhowlesr

@rico

To make sure I’m following you

Open >> "/boot/loader.conf.local” using the pfsense file editor”

And add echo "hint.sdhci_pci.1.disabled="1"" to the bottom of the file.

Save then restart the system.

Gertjan

echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local

is the same thing as opening the file /boot/loader.conf.local and adding
hint.sdhci_pci.1.disabled="1"
in it.

jbhowlesr

@gertjan

I’m in the file system now. A file called loader.conf.local does not exist. However, a file called loader.conf exists and I made a copy of it and renamed to loader.conf.local and edited that file with the line above.

EDIT: just tried this and it didn’t work. Obviously I’m missing something?

Rico

Just login via SSH and type or copy/paste
echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
reboot and thats it.

-Rico

stephenw10

The file: /boot/loader.conf.local should contain only the line:
hint.sdhci_pci.1.disabled=1

You might add more stuff to it later but since you had to just create it it shouldn't right now.

Steve

jbhowlesr

@stephenw10

Thank you much. I did this and it worked like a champ. It’s now booting automatically without needing interaction.

jbhowlesr

@stephenw10 @Rico If I may ask, what is STHC I and why is it now becoming a problem

stephenw10

SDHCI is the FreeBSD driver for the SD card bus. For whatever reason it is not playing nicely with the hardware on your board (and a number of other boards). As jimp referred to above the upgrade to FreeBSD 11.2 brought some changes to that driver including the ability to use a different mode which seems incompatible here. If you really needed that you might be able to force it to use the lesser mode but that's not something I've ever tried.

https://www.freebsd.org/cgi/man.cgi?query=sdhci&apropos=0&sektion=0&manpath=FreeBSD+11.2-RELEASE&arch=default&format=html

Steve

jbhowlesr

@stephenw10
I appreciate the response. It’s funny that an issue is occurring with a feature my board lacks. It’s all good though. Perhaps it’s the lack of this hardware that’s causing the issue.

Are there any plans to address this concern going forward or at least build in so form of acception handling?

stephenw10

As far as I know it's a FreeBSD issue, it may have been fixed already in 12. It could also be the BIOS reporting incorrectly to FreeBSD. Manufacturers love to test in Windows only and then ship!
It would be tough for us to disable anything there by default as some systems boot from SD card. It's a relative minority of boards that are affected.

Steve