Beep or visual signal after booting OpenBSD/sparc64

[Hans Ivers]

Hi everybody,

I've setup a firewall/router on a SunFire v100 using OpenBSD/sparc64
(version 4.5)

Since it's a headless system (all management done via serial port), is
there a way to play a "signal" when the system has finished its
booting sequence, to inform me that services are up and running?
Ideally, it would be a beep sound, but basically any audible or
visible signal is ok for me.

Until now, I've tried various "hacks" :

- shell script ( "\a" in C)
- access to audio system (but the v100 does not seem to have an
internal "speaker" like those I'm more familiar in PC)
- visual signal (there are two alarms linked to green lights in the
front case that can be set in LOM but I understand they are not
accessible within OpenBSD).

Any ideas or suggestions will be most welcome! Thanks in advance,

Hans.

[Jameel Akari]

On Thu, 17 Sep 2009, Hans Ivers wrote:

> there a way to play a "signal" when the system has finished its
> booting sequence, to inform me that services are up and running?
> Ideally, it would be a beep sound, but basically any audible or
> visible signal is ok for me.
...
> - visual signal (there are two alarms linked to green lights in the
> front case that can be set in LOM but I understand they are not
> accessible within OpenBSD).

Does the machdep.led_blink sysctl not work on a V100?

You can set it in /etc/sysctl.conf so it starts blinking once the kernel
has loaded it; or script something in rc.local to toggle it based on
whatever conditions you want:  sysctl -w machdep.led_blink=1

I use this on my Ultra10 firewall boxes to indicate they've at least
attempted to boot.

--
Jameel Akari

[Hans Ivers]

 Hi everybody,

I got time tonight to try both suggestions :

a) eject /dev/rcd0c

it's working perfectly

b) machdep.led_blink=1

no way to make it works. I've enabled this option in /etc/sysctl.conf
or within the root shell (sysctl -w machdep.led_blink=1) without any
visible result.

There is two leds in the front panel of the 1U Sunfire v100 : green
(when poweron) and orange (when faulton is enable in LOM). Both leds
are unresponsive to changes in machdep.led_blink.

Many thanks for your helpful suggestions!


On Thu, Sep 17, 2009 at 2:55 PM, Jameel Akari <jakari@...> wrote:

> On Thu, 17 Sep 2009, Hans Ivers wrote:
>
>> there a way to play a "signal" when the system has finished its
>> booting sequence, to inform me that services are up and running?
>> Ideally, it would be a beep sound, but basically any audible or
>> visible signal is ok for me.
>
> ...
>>
>> - visual signal (there are two alarms linked to green lights in the
>> front case that can be set in LOM but I understand they are not
>> accessible within OpenBSD).
>
> Does the machdep.led_blink sysctl not work on a V100?
>
> You can set it in /etc/sysctl.conf so it starts blinking once the kernel

has
> loaded it; or script something in rc.local to toggle it based on whatever
> conditions you want:  sysctl -w machdep.led_blink=1
>
> I use this on my Ultra10 firewall boxes to indicate they've at least
> attempted to boot.
>
> --
> Jameel Akari

[Ron Wickersham]

On Thu, 17 Sep 2009, Hans Ivers wrote:

---snip---

> b) machdep.led_blink=1
>
> no way to make it works. I've enabled this option in /etc/sysctl.conf
> or within the root shell (sysctl -w machdep.led_blink=1) without any
> visible result.

after changing option in /etc/sysctl.conf is not effective until next
boot...

check man sysctl, on OpenBSD there is no -w option, unlike Solaris or
Linux, etc.    use sysctl machdep.led_blink=1 and it may work (does
on other Ultra-SPARC boxen.

-ron

[Brad-86]

On Thursday 17 September 2009 21:19:28 Ron Wickersham wrote:

> On Thu, 17 Sep 2009, Hans Ivers wrote:
>
> ---snip---
>
> > b) machdep.led_blink=1
> >
> > no way to make it works. I've enabled this option in /etc/sysctl.conf
> > or within the root shell (sysctl -w machdep.led_blink=1) without any
> > visible result.
>
> after changing option in /etc/sysctl.conf is not effective until next
> boot...

He made it pretty clear he tried it manually via sysctl(8).

> check man sysctl, on OpenBSD there is no -w option, unlike Solaris or
> Linux, etc.    use sysctl machdep.led_blink=1 and it may work (does
> on other Ultra-SPARC boxen.

OpenBSD used to have the -w flag and still accepts the flag.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Hans Ivers]

Hi Ron,

Thanks for your suggestion. I've reboot each time I tried a new way
(via sysctl.conf or shell) to enable the "machdep.led_blink" option,
but with no visible success.

If somebody has access to a v100 machine, I would be very grateful if
he/she is able to reproduce my observations that this sysctl option is
not working on Sunfire v100?

Best regards,

Hans.

> after changing option in /etc/sysctl.conf is not effective until next
> boot...
>
> check man sysctl, on OpenBSD there is no -w option, unlike Solaris or
> Linux, etc.    use sysctl machdep.led_blink=1 and it may work (does
> on other Ultra-SPARC boxen.

[Jameel Akari]

On Thu, 17 Sep 2009, Brad wrote:

> On Thursday 17 September 2009 21:19:28 Ron Wickersham wrote:
>> On Thu, 17 Sep 2009, Hans Ivers wrote:
>>
>> ---snip---
>>
>>> b) machdep.led_blink=1
>>>
>>> no way to make it works. I've enabled this option in /etc/sysctl.conf
>>> or within the root shell (sysctl -w machdep.led_blink=1) without any
>>> visible result.
>>
>> after changing option in /etc/sysctl.conf is not effective until next
>> boot...
>
> He made it pretty clear he tried it manually via sysctl(8).
>
>> check man sysctl, on OpenBSD there is no -w option, unlike Solaris or
>> Linux, etc.    use sysctl machdep.led_blink=1 and it may work (does
>> on other Ultra-SPARC boxen.
>
> OpenBSD used to have the -w flag and still accepts the flag.

Yeah, force of habit, I still type it.

I think I do have a V100 or V120 that I can check in person tomorrow.


--
Jameel Akari

[Mark Kettenis]

> Date: Thu, 17 Sep 2009 22:25:11 -0400
> From: Hans Ivers <hansivers@...>
>
> Hi Ron,
>
> Thanks for your suggestion. I've reboot each time I tried a new way
> (via sysctl.conf or shell) to enable the "machdep.led_blink" option,
> but with no visible success.
>
> If somebody has access to a v100 machine, I would be very grateful if
> he/she is able to reproduce my observations that this sysctl option is
> not working on Sunfire v100?

I confirm that machdep.led_blink doesn't work on the v100; there is
no code in the tree to make it work.

There is hope though.  I just committed a minimal driver that talks to
the LOM on these machines.  For now it only provides a temperature
sensor, but I plan to extend the driver to provide some control over
the LEDs.

Cheers,

Mark