Really big problem to go to 2.2.2 from 2.2.1
-
. . .
NickBecause cause if it is not being used there is no good that can come from it being enabled. Only bad. KISS and avoid the bad. Like this issue, you never now when it will sneak up and bite.
Disabling things in the BIOS that are not being used is not about saving energy. It's about KISS.
Yes, you should be getting the picture.
There is a good and valid reason to do so here too. Apply the KISS principle to things and life is easier.
Many notebooks back in the dial-up days had built-in modems.Not a troll. It's a serious message. I really don't get leaving all that junk enabled if it is not being used. Just makes no sense for router appliance that is desired to be as reliable as possible. Less is more.
It's a prudent KISS to turn it off. In the words of Nike. Just do it! And be done with it.
-
Alright. Who gave me my first smite?
Can't believe someone would smite over this.
-
Som critical info is missing here: when/how will this be solved, will we get an "emergency" update? Should I wait for an update or is this one of such importance that I should go with the update? I don't use IPv6, IPSEC, wireless and the web interface can't be accessed from WAN so I think the openssl vulnerabilities don't apply, please correct me if I am wrong. And I trust my LAN. Any other reasons?
No other problems - only that since 2.2.1 and the other package updates I can't connect with openVPN (network manager) from my openSUSE 13.1; I keep up to date my openSUSE workstation. Works fine from Fedora or Android so I think the openSUSE dudes/updates messed something up, I will investigate.
-
Is there any boot option we could use to override the setting thats caused this? My system has no serial port setting in the bios :(
-
Same problem here.
Hardware: Asrock AMD E350M1
pfSense: Full install
Solution: Disable serial port in BIOSWill changing boot_serial="YES" to boot_serial="NO" in /boot/loader.conf solve the problem permanently?
-
@mir:
Will changing boot_serial="YES" to boot_serial="NO" in /boot/loader.conf solve the problem permanently?
sortof. "/boot/loader.conf" gets overwritten every time you update/reinstall pfSense. But the devs are aware of the issue now, so in the next release, they should have a permanent fix for it.
-
Because cause if it is not being used there is no good that can come from it being enabled. Only bad. KISS and avoid the bad. Like this issue, you never now when it will sneak up and bite.
Disabling things in the BIOS that are not being used is not about saving energy. It's about KISS.
Yes, you should be getting the picture.
There is a good and valid reason to do so here too. Apply the KISS principle to things and life is easier.
Many notebooks back in the dial-up days had built-in modems.Not a troll. It's a serious message. I really don't get leaving all that junk enabled if it is not being used. Just makes no sense for router appliance that is desired to be as reliable as possible. Less is more.
It's a prudent KISS to turn it off. In the words of Nike. Just do it! And be done with it.
Still not sure if troll or not when you advocate disabling serial on a firewall "to keep it simple". You should rather fix the issue and keep the serial there so you can use it in case of emergency.
-
As I run it in a VM at home with no serial port connected, then no issues.
When I add the port, I get the issue described.
-
After upgrade the errors come up :
Kdb: debugger backend: ddb
Amd64
Restalling everything right now!!!
Yes, same problem!
I try upgare and fresh install. But same result.Restart to my Pfsense
Very very slowly write: Kdb: …......................
This is big problem!
-
"Warning: an issue was discovered post-release with a small minority of systems running a full install with no serial console enabled, where the boot is very, very slow because of a serial console-related change. Disabling the serial ports in the BIOS will work around this issue should you encounter it."
I think this is an understatement. It should read: "[..] a majority of systems running full install with no serial console[..]"
-
Its like EVERYBODY :D
-
is this a feature thats been implemented after last weeks snapshot?
i personally haven't had much issue's with the snapshots last couple of weeks but now don't wish to upgrade to -release :) -
is this a feature thats been implemented after last weeks snapshot?
i personally haven't had much issue's with the snapshots last couple of weeks but now don't wish to upgrade to -release :)You can simply check your current snapshot for the setting. My box seems to be fine with the setting with full pfSense (VGA). I've got an Intel SP1200K or some such motherboard.
-
Dear Guys
Yesterday after this tragic error I had to be quick in decision, because here we have many workstations and all were stoped! So I quickly re-installed pfSense 2.2.1 and restored the backup, so everything is working again. So today I decided to upgrade to 2.2.2 again and the error happened again…. so, now i've disabled the serial port on the pfSense setup and the system boot normally. Thank you all. Here the image of the error, the letters write very slowly!
Cheers
-
If the boot menu is fast, press option 3 to go to a loader prompt, then type
unset boot_serial boot -
Hi Jimp,
Yes nice tip! also to fix the problem I commented lines in /boot/loader.conf
##boot_serial="YES"
##comconsole_speed="9600"Cheers, thank you !!!
-
This issue can be also mitigated by connecting a compatible serial console to match the speed:
-
Same problems here, disabling serial fixed for me. Dell Vostro 230.
-
Yet another day of me be glad I am not using equipment with serial console… (-:
-
Every box we ship has a serial console and near as we can tell from the testing, they're all fine, though we enable the serial console and force it on, since the serial console is the only console on most of these units.
Problem seems to be if specific to certain hardware combinations and only those that both have a hardware serial port and also have it disabled.
