The battery was almost 'empty', but putting a new one did not help.
I tried with other PSU, the MB has a standby light when it gets electricity and it lights, when I turn with the MB on, then the power meter I have in the plug jumps from 0...
Checking the PSU first step would be to simply only connect a spinning disc and see if it spins up.
WRT switches, the switches in many a power distribution cords will generate quite an arc when flipped. When that collapses, there is a voltage...
Absorbs electricity (I have a meter on the plug), the MB is fanless, but the fan of the PSU moves, the screen remains blank without cursor.
Since without RAM it does not peep as it should do, it has probably not reached the point of testing RAM...
What do you mean by "doesn't boot"? Do you mean it doesn't power up at all? Are the fans spinning up? Or is it powering up but you only get a black screen with a blinking cursor? Or is it showing more than that on the screen? If so, what is it...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
did you fully finish the upgrade and also upgraded all packages? (i.e. freebsd-update install, reboot, freebsd-update install, pkg upgrade -f, freebsd-update install)
please show the outputs of freebsd-version -kru and pkg info php83
Hi sko ,
This is a new fresh install, not an upgrade.
# freebsd-version -kru
15.0-RELEASE-p5
15.0-RELEASE-p5
15.0-RELEASE-p5
# pkg info php83
php83-8.3.30
Name : php83
Version : 8.3.30
Installed on : Tue Mar 31 03:30:46...
Yes, I did, and I also wrote that above.
It is a "silentmaxx FANLESS II 500Watt" PSU. I hope it is not the cause, I would like to use it.
I wrote that I powered off with the switch. I mean the mechanical switch, like unplugging.
The other did...
What about the CMOS battery? Did you remove that and let it drain?
Other than that, it smells like the CPU got damages by a power spike. But you did not tell what switch you used. The one for ACPI, the one on the PSU or maybe one in the power cord?
Of course I unplugged, disassembled the whole PC, connected the motherboard alone with speaker and other PSU,
And of course no "shutdown -h now".
I wrote all this above.
Hi Alain De Vos
I need to stay on 8.3.x for compatibility reasons for a couple of months more.
The scripts aren't changed (Mostly Magento), and worked in CLI-mode on FreeBSD 13.5 with PHP 8.3.30.
I'm lost! :p
I have only just become aware that I have a /usr/bin/xdg-open.
I don't where it came from but I've just found that if I'm using dired in doom emacs and press '!' I get a prompt for which command I want to run on the current file.
I must have...
Update: above didn't completely fix the issue, I also updated /etc/mail/mailer.conf with the following content:
# Execute the Postfix sendmail program, named /usr/local/sbin/sendmail
#
sendmail /usr/local/sbin/sendmail
send-mail...
No.
I have a power meter on the plug. When I switch on, it consumes, when hold the switch turns of and do not consume.
It seems there is no power on self test (POST), otherwise without RAM it would peep.
We jumped from FreeBSD 13 to FreeBSD 15 last night, and everything seems to be working just fine.
Except this, when we run PHP 8.3.30 in CLI only, we always get exited on signal 11 (core dumped) - even if the script was ran successfully.
NOTE...
I powered of with the switch a computer, it does not boot anymore, no peep even if I take all memory out.
I took all peripheral out, tried with other PSU, reset the BIOS with the jumper and also took battery out for a while.
A similar problem I...
What he want is something like littlesnitch on Mac/OS, ie a per app fw. IMHO, the only way to do this on FreeBSD is to use many UID as needed, and launch apps with their own uid like freebsd_lg said above. Dont know other way to do that. And yes...
When you, for example, want to search and substitute including line breaks, then emacs and sam are superior to vi.
vi is good for writing config files, mails, and such things.
With sam I have the problem of the background color, and that the...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
Alain De Vos : Yeah, Discord is the place to look if you wanna see social engineering in action. The late Kevin Mitinck did his social engineering over the phone, he just picked his words to get the humans to divulge admin access codes. These...
Yes, I made a screenshot at ... one moment... 18:19:09 MEST (my clock widget is on the picture).
I'll keep that FOREVER! What a bummer!
Maybe the admins should evaluate Zope as backend and use a open source forum SW? Plone is reknoŵn for it's...
Kudos to the team for taking the extra step and removing DNS records as a preventive measure until the scope of the problem was understood. I love that forum management are setting the example for good net citizenship.
You are only as good as the latest software you're running and the ability to keep up with those. We had a failure in keeping up with XF and that will not happen again. This was the first security event in the 18 years that these forums have...
A XSS vulnerability in XenForo.
https://forums.freebsd.org/threads/forum-outage.102193/
Same happened to linux.org
https://www.linux.org/threads/whoops-a-xenforo-xss-vulnerability-bit-us.64521/
Wow. 2.7 million people have gone to stack overflow to find out how to exit vi. There's an old bash.org post about it, which I'd always thought was a joke. (The vi article link https://vivianvoss.net/blog/vi)
I can't find the bash.org post...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
You are only as good as the latest software you're running and the ability to keep up with those. We had a failure in keeping up with XF and that will not happen again. This was the first security event in the 18 years that these forums have...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
You are only as good as the latest software you're running and the ability to keep up with those. We had a failure in keeping up with XF and that will not happen again. This was the first security event in the 18 years that these forums have...
Kudos to the team for taking the extra step and removing DNS records as a preventive measure until the scope of the problem was understood. I love that forum management are setting the example for good net citizenship.
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
You are only as good as the latest software you're running and the ability to keep up with those. We had a failure in keeping up with XF and that will not happen again. This was the first security event in the 18 years that these forums have...
Opened a 294141 for the new update.
From 39820069c36312562d6fa31a190df401a03d24f7 Mon Sep 17 00:00:00 2001
From: Yusuf Yaman <nxjoseph@FreeBSD.org>
Date: Mon, 30 Mar 2026 17:38:41 +0300
Subject: [PATCH] x11/sfwbar: Update 1.0_beta16.1 =>...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
Hi guys, sorry that the FreeBSD Forums were offline for a couple of hours.
We were hit by an exploit against a slightly outdated XenForo version that we were still running.
The same exploit hit quite a number of XenForo installations today...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.