Messages

Thank you Tixx7. This helped greatly, just to add for ease. Use the Porkbun guide https://kb.porkbun.com/article/190-getting-started-with-the-porkbun-api. Take note of the "green box", this is you only time to get the secret key. As mentioned in the thread you need to have the DNS record already created, I tested it w/o and it failed with this in the log.

Code Select Expand

FAILED: updating xxxx.xxxxxx.com: No applicable existing records.
I created an A record with the wrong IP to test, and you should see this in the log:

Code Select Expand

SUCCESS: updating ipv4: good: xxxx.xxxxxx.com.com address set to xxx.xxx.xxx.xxx
And the IP should be updated in your Porkbun DNS.

Total noob here, just bought my first domain on porkbun and trying to get this setup. I get the same "No applicable existing records" error.

When you say you created an A record with the wrong IP, is that what you put in the Answer/Value box? What is supposed to go in there? Or are we just filling it in to finish the record and then ddclient fixes it?

Looks like it went without a hitch all the way to 25.1.8_1. I was even away for the last bits and started the update through my zerotier connection. So it seems that disabling a serial port years ago that I'm never going to use is what caused my issue. That seems like a stupid way to bork an install. I'm curious as to what got changed but, I'm not learned enough yet to understand what I'd be reading in all those changelogs.

Just tried to go to 24.7 and got the same problem. Tried re-enabling the serial ports in BIOS and ran

Code Select Expand

set hint.uart.0.at="isa"
boot

and it went through. Didn't know which one actually fixed it so during the next reboot I didn't run the loader prompt and it continued just fine. Seems it doesn't like the serial ports being disabled.

Edit: I'm going to see if it will let me go all the way up to latest. Will report back.

Okay, guess that means I'll have to wait until 25.7 it sounds like. Though it does also sound like I should be able to go to 24.7 at least, if I'm not mistaken.

Code Select Expand

set hint.uart.0.at="isa"
boot


Is there a difference between that and:

Code Select Expand

set hint.uart.0.at="isa"
autoboot

That's what I tried when pf gave me the issue, after asking on their forum, and it didn't change anything. Also tried with both uart.0 and uart.1 together which was also suggested.

I think you are misleading us with your posts and/or you are looking at the wrong cause for your issue (recent Intel microcode is also breaking some systems).

The UART not working for older hardware *was* fixed in 25.1.6. The age of the hardware can be irrelevant as the BIOS is responsible for advertising a device as ISA or ACPI in FreeBSD. FreeBSD *thought* that ISA is deprecated, but their code is likely faulty because the consoles are not even connected via ISA in the first place.

https://github.com/opnsense/src/commit/52bb0884e6

That being said they did try to fix newer devices not booting  so now these devices don't have a console anymore.

If there was a best of both worlds we would go for it, but going back to the old way that works for most is the best approach at the moment.

Before I knew this was potentially a FreeBSD issue, this is what finally gave me the motivation to switch from pf to opn.

I originally tried installing 25.1.7 but I had the same issue I did with pf and it would hang at:

isa0: <ISA bus> on isab0

It's running bare metal on an Dell R510.

I did get 24.1.10 to go but I'm afraid to try any newer.

Is there a way to determine if it's FreeBSD or the Intel microcode issue? And, what would be needed to prevent either?