I'm with problems to compile Direct App Launch ACPI driver for Linux.
I pasted the output when I try make.
make -C /lib/modules/`uname -r`/build SUBDIRS=/home/maluta/devel/acpi/quickstart modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.24.1'
scripts/Makefile.build:46: *** CFLAGS was changed in "/home/maluta/devel/acpi/quickstart/Makefile". Fix it to use EXTRA_CFLAGS. Pare.
make[1]: ** [_module_/home/maluta/devel/acpi/quickstart] Erro 2
make[1]: Saindo do diretório `/usr/src/linux-2.6.24.1'
make: ** [quickstart.ko] Erro 2
I didn't found EXTRA_FLAGS in Makefile.
My other question is in order to compile properly, what flag in kernel config must I set?
Best regards,
Tiago Maluta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
I'm trying it just for hobbie, I think its a great idea.
Thanks,
Tiago Maluta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
I'm trying it just for hobbie, I think its a great idea.
Thanks,
Tiago Maluta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
> I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
Yes, quickstart relies on a hardware function commonly found on "Vista Capable" computers. In your case your hardware seems to support it (the module loads successfully) but there are no hardware buttons implemented.
Can you send me your ACPI DSDT? I would like to check.
I'm with problems to compile Direct App Launch ACPI driver for Linux.
I pasted the output when I try make.
make -C /lib/modules/`uname -r`/build SUBDIRS=/home/maluta/devel/acpi/quickstart modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.24.1'
scripts/Makefile.build:46: *** CFLAGS was changed in "/home/maluta/devel/acpi/quickstart/Makefile". Fix it to use EXTRA_CFLAGS. Pare.
make[1]: ** [_module_/home/maluta/devel/acpi/quickstart] Erro 2
make[1]: Saindo do diretório `/usr/src/linux-2.6.24.1'
make: ** [quickstart.ko] Erro 2
I didn't found EXTRA_FLAGS in Makefile.
My other question is in order to compile properly, what flag in kernel config must I set?
Best regards,
Tiago Maluta
> I'm with problems to compile Direct App Launch ACPI driver for Linux.
> I pasted the output when I try make.
> make -C /lib/modules/`uname -r`/build SUBDIRS=/home/maluta/devel/acpi/quickstart modules
> make[1]: Entrando no diretório `/usr/src/linux-2.6.24.1'
> scripts/Makefile.build:46: *** CFLAGS was changed in "/home/maluta/devel/acpi/quickstart/Makefile". Fix it to use EXTRA_CFLAGS. Pare.
> make[1]: ** [_module_/home/maluta/devel/acpi/quickstart] Erro 2
> make[1]: Saindo do diretório `/usr/src/linux-2.6.24.1'
> make: ** [quickstart.ko] Erro 2
> I didn't found EXTRA_FLAGS in Makefile.
On the Makefile you have on line 13:
CFLAGS+=-c -Wall -Wstrict-prototypes -Os -pipe
just replace that line by:
EXTRA_CFLAGS+=-c -Wall -Wstrict-prototypes -Os -pipe
> My other question is in order to compile properly, what flag in kernel config must I set?
You will need CONFIG_ACPI enabled on your kernel.
> Best regards,
> Tiago Maluta
Thanks for your interest on quickstart,
Angelo Arrifano
It's now fixed on version 1.00-r1.
Thanks for reporting,
Angelo Arrifano
I obtained success changing CFLAGS to EXTRA_CFLAGS and loading the module (modprobe quickstart).
My kernel (2.6.24.1) has the ACPI settings:
# grep CONFIG_ACPI /usr/src/linux/.config
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
But, when I type:
# cat /sys/devices/platform/quickstart/buttons
none
Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
I'm trying it just for hobbie, I think its a great idea.
Thanks,
Tiago Maluta
I obtained success changing CFLAGS to EXTRA_CFLAGS and loading the module (modprobe quickstart).
My kernel (2.6.24.1) has the ACPI settings:
# grep CONFIG_ACPI /usr/src/linux/.config
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
(...)
But, when I type:
# cat /sys/devices/platform/quickstart/buttons
none
Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
I'm trying it just for hobbie, I think its a great idea.
Thanks,
Tiago Maluta
> Instead of QBTN,DBTN,MUBN,PIBN,WEBN,LVBN,VOBN... Is quickstart in someway hardware dependent?
> I'm using SiS chipset in my motherboard, but I think if the ACPI kernel works, quickstart would work.
Yes, quickstart relies on a hardware function commonly found on "Vista Capable" computers. In your case your hardware seems to support it (the module loads successfully) but there are no hardware buttons implemented.
Can you send me your ACPI DSDT? I would like to check.
cat /sys/firmware/acpi/tables/DSDT | bzip2 > dsdt.bz2
Thanks,
Angelo Arrifano