Re: Acer arcade instantOn and grub

[Marco Gerards]

"address@hidden" <address@hidden> writes:

Hi,

> i have a nice question for you :)
> in many acer laptops there is a second poweron button which is called "arcade 
> button".
> this is a normal power on button, as you can see:
>
> # more /proc/bus/input/devices
> I: Bus=0019 Vendor=0000 Product=0002 Version=0000
> N: Name="Power Button (FF)"
> P: Phys=button_power/button/input0
> S: Sysfs=/class/input/input0
> U: Uniq=
> H: Handlers=kbd event0
> B: EV=3
> B: KEY=100000 0 0 0
>
> ...
>
> I: Bus=0019 Vendor=0000 Product=0001 Version=0000
> N: Name="Power Button (CM)"
> P: Phys=PNP0C0C/button/input0
> S: Sysfs=/class/input/input2
> U: Uniq=
> H: Handlers=kbd event2
> B: EV=3
> B: KEY=100000 0 0 0
>
> when laptop is new (read "when you haven't overridden window's bootloader"), 
> pressing the normal power on button causes a normal boot sequence, but 
> pressing the arcade button causes a different boot sequence.
>
> i don't really want to restore windows boot loader, so: is there a way to 
> replicate this job with grub or grub2?
>
> for any further info please ask.

Is this information stored somehow?  So how can the bootloader
determine what is done?  In that case you can use scripting in GRUB 2
to make use of this information.  It can't be done yet, but surely
GRUB 2 can be modified to use this.

--
Marco