Re: weird speakup or hardware bug?

[Chris Brannon <chris@the-brannons.com>]

Deedra Waters <deedra@the-brannons.com> writes:

> I'm not even sure where to begin. switching from arch to gentoo seems to
> have changed certain things like my ethernet now works?
>
> But, what's happening here is that for all of my consoles, speakup has
> the numlock as on and i have to change it before i can use speakup
> commands. Anyone seen this before?

I shouldn't let this thread dangle; we found a solution.
Basically, use setleds to set the current and default state of the
numlock at boot time.
There's a script to do this which is distributed with OpenRC on Gentoo.
But it sets the numlock, instead of clearing it.
I made a new script based on that one, but mine disables the numlock
instead.  If you're on Gentoo, you can put the following script in
/etc/init.d and add it to your boot runlevel.  Don't overwrite their
numlock script with it; give it a name of its own.

=== BEGIN SCRIPT ===
#!/sbin/runscript
description="Disable numlock for consoles"

ttyn=${rc_tty_number:-${RC_TTY_NUMBER:-12}}

depend()
{
	need localmount
	keyword -openvz -prefix -vserver -lxc
}

_setleds()
{
	[ -z "$1" ] && return 1

	local dev=/dev/tty t= i=1 retval=0
	[ -d /dev/vc ] && dev=/dev/vc/

	while [ $i -le $ttyn ]; do
		setleds -D "$1"num < $dev$i || retval=1
		: $(( i += 1 ))
	done

	return $retval
}

stop()
{
	true
}

start()
{
	ebegin "Disabling numlock on ttys"
	_setleds -
	eend $? "Failed to disable numlock"
}

=== END SCRIPT ===