Supermicro sys-5018a-ftn4 no startup sound

Guest

Is there anything I can run or provide to help troubleshoot this?

Jump into the BIOS and activate Power on self test (POST) perhaps you will hear the beep
then before pfSense is booting. And it is like it is, the POST will be done before any kind of
OS will booting, but only during the boot phase, so no OS can be involved in this.

tha_toadman

Jump into the BIOS and activate Power on self test (POST) perhaps you will hear the beep
then before pfSense is booting.

I do hear this beep when it POST's. It's the pfSense startup/shutdown chime that I don't hear. This feature would be nice to have back as the unit is headless.

Guest

@tha_toadman:

Jump into the BIOS and activate Power on self test (POST) perhaps you will hear the beep
then before pfSense is booting.

I do hear this beep when it POST's. It's the pfSense startup/shutdown chime that I don't hear. This feature would be nice to have back as the unit is headless.

Perhaps also interesting for you to know Beeper problem

stephenw10

If any of you come up with a solution to this, I'd love to hear it. (in all senses of that!)

Steve

iorx

Got limited knowledge of BSD but here my google aquired info on beep in BSD

# sysctl -a | grep hw.syscons.bell
hw.syscons.bell: 1

That means thats the hardware is found and that kernelmodule is loaded as long; as I understand it.

# beep

doesn't beep

# echo "BP" > /dev/speaker

Got the silent treatment from the above also…

So I still got a very nice and quiet box* when it comes to boot up, shutdown and restart. :)

[SYS-5018A-FTN4 & pfSense 2.2.4]

Guest

From dlogan:

Supermicro sys-5018a-ftn4 & amd64 version 2.1.5

From iorx:

SYS-5018A-FTN4 & pfSense 2.2.4

And based on this informations I was posting the link where another
member (@robi) was posting the following comment about:
This tune is not played by Supermicro boards for some reason.

iorx

Yes, and? :)
I'm I missing something here? Should I use a different thread?

More people have the issue but no one got an solution what I can see.

I was just going to rule out that I haven't missed something obvious by showing what I tried.

miken32

I guess still no update on this? Surprising that devs haven't been able to figure this one out, since they sell the hardware. It's a great feature when you have to remote troubleshoot over the phone with someone who is clueless!

tha_toadman

Unfortunately there's been no update. It is the last missing feature that I have yet to resolve.

cmb

We haven't even looked at it prior to now. At a quick review, it doesn't work in 2.3 either on that hardware. That's so far down my list of priorities it won't get any attention for 2.3 at a minimum. If someone wants to dig into it, you're more than welcome. It's either a hardware issue or a FreeBSD issue.