[repost] acpi on gentoo

[repost] acpi on gentoo

[Nigel]

Trying again to see if anyone had any other ideas.

In addition:
The acpid daemon is running.
The same machine when booted into windows will automatically go to 
powersave mode when the power cable is removed.

TIA
Nigel.

original post  (4th March):


Hello,

I have been trying to get acpid to receive events on gentoo without any 
success.
I an on kernel 2.6.17 (with rev 10 gentoo patched)
acpid: 1.0.4-r4
Toshiba Tecra M3

I have been following the guide at:
http://www.gentoo.org/doc/en/power-management-guide.xml

I'm on 2.6.17

So, whatever they suggested to compile in the kernel or as a module that 
is what I have done.

When I look at /var/log/acpi no events are being generated.

With this test :
on_ac_power && echo AC available || echo Running on batteries

It shows "AC available" when the ac is plugged in, take the cable out, 
and it shows "Running on batteries"

Code:

# acpitool -e
   Kernel version : 2.6.17   -    ACPI version : 20060127
   -----------------------------------------------------------
   Battery #1     : present
     Remaining capacity : 39441 mWh, 82.47%, 00:27:29
     Design capacity    : 50760 mWh
     Last full capacity : 47822 mWh, 94.21% of design capacity
     Capacity loss      : 5.788%
     Present rate       : 18295 mW
     Charging state     : charging
     Battery type       : rechargeable, Li-ION
     Model number       : G71C0004G810
     Serial number      : 0100027803
   Battery #2     : slot empty

   AC adapter     : on-line
    Fan :  off

   CPU type               : Intel(R) Pentium(R) M processor 2.13GHz
   CPU speed              : 800.000 MHz
   Cache size             : 2048 KB
   Bogomips               : 1600.29
   Processor ID           : 0
   Bus mastering control  : yes
   Power management       : yes
   Throttling control     : no

  Limit interface        : no
   Active C-state         : C3
   C-states (incl. C0)    : 4
   Usage of state C1      : 10 (0.0 %)
   Usage of state C2      : 161443 (35.8 %)
   Usage of state C3      : 144440 (32.1 %)

   Thermal info   :

   wakeup devices :


I can modify this:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
and the processor speed with follow the governor which I set.

I can also run: acpitool -l 4
for example, and dim the lcd display.

Also, I have th battery indicator applet in gnome, this also changes 
correctly with respect to having the power connected, or not.

Most things seem to work as they should, except acpid is not receiving 
events.

Code:

  # ls -R /proc/acpi/
/proc/acpi/:
ac_adapter  dsdt                 event  info            processor
battery     embedded_controller  fadt   power_resource  toshiba

/proc/acpi/ac_adapter:
ADP1

/proc/acpi/ac_adapter/ADP1:
state

/proc/acpi/battery:
BAT1  BAT2

/proc/acpi/battery/BAT1:
alarm  info  state

/proc/acpi/battery/BAT2:
alarm  info  state

/proc/acpi/embedded_controller:

/proc/acpi/power_resource:

/proc/acpi/processor:
CPU0

/proc/acpi/processor/CPU0:
info  limit  power  throttling

/proc/acpi/toshiba:
fan  keys  lcd  version  video


Modules at run time :
Code:

  # lsmod
Module                  Size  Used by
cisco_ipsec           545996  0
snd_pcm_oss            16992  0
snd_mixer_oss          12928  1 snd_pcm_oss
snd_seq_oss            23872  0
snd_seq_midi_event      5184  1 snd_seq_oss
snd_seq                37456  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          5708  2 snd_seq_oss,snd_seq
snd_intel8x0           24924  0
snd_ac97_codec         78496  1 snd_intel8x0
snd_ac97_bus            1792  1 snd_ac97_codec
snd_pcm                54472  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              15236  2 snd_seq,snd_pcm
snd_page_alloc          6728  2 snd_intel8x0,snd_pcm
toshiba_acpi            4756  0
speedstep_centrino      5456  1
processor              16896  1 speedstep_centrino
ipw2200               140268  0
nvidia               4541396  12
sky2                   28740  0



The AC and battery modules are compiled in kernel as the guide suggests.


# acpi_available; echo $?
0

# grep -i "^config_acpi" .config
CONFIG_ACPI=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y

# lsof |grep "/proc/acpi/event"
acpid     13843       root    3r      REG        0,3        0 4026532088 
/proc/acpi/event


Even if I run strace against acpid I can't seen anything happening.


One interesting though, if I do : modprobe button
then every 30 seconds or so I get:
received event "battery BAT1 00000080 00000001"

Even when i do rmmod button I still keep getting these events.
The only way to go back to "normal" behaviour is to reboot.

Any suggestions as to what might be my problem here ?

TIA
Nigel.

Re: [repost] acpi on gentoo

[Luming Yu]

On 3/11/07, Nigel <nigels@hotmail.com> wrote:
>
> Trying again to see if anyone had any other ideas.
>
> In addition:
> The acpid daemon is running.
> The same machine when booted into windows will automatically go to
> powersave mode when the power cable is removed.
>

what condition is your battery in? It makes sense if battery power is very low.
If battery is still full, then it sounds like a bug.  You need to test
the latest base kernel before entering a acpi bug into
bugzilla.kernel.org.

> One interesting though, if I do : modprobe button
> then every 30 seconds or so I get:
> received event "battery BAT1 00000080 00000001"
>
> Even when i do rmmod button I still keep getting these events.
> The only way to go back to "normal" behaviour is to reboot.
>
> Any suggestions as to what might be my problem here ?
>
I guess your battery power level is low.

Re: [repost] acpi on gentoo

[Nigel]

response inline

Luming Yu said on 11/3/2007 3:12 PM:
> On 3/11/07, Nigel <nigels@hotmail.com> wrote:
>>
>> Trying again to see if anyone had any other ideas.
>>
>> In addition:
>> The acpid daemon is running.
>> The same machine when booted into windows will automatically go to
>> powersave mode when the power cable is removed.
>>
> 
> what condition is your battery in? It makes sense if battery power is 
> very low.
   Battery #1     : present
     Remaining capacity : 47822 mWh, 100.0%
     Design capacity    : 50760 mWh
     Last full capacity : 47822 mWh, 94.21% of design capacity
(similar output was included in the original post)

Regardless of battery condition should I not still get an event for 
removing and reinserting the power cable? (Obviously waiting for a 
minute or two in-between )

> If battery is still full, then it sounds like a bug.  You need to test
> the latest base kernel before entering a acpi bug into
> bugzilla.kernel.org.

It works just fine on 2.6.19-r5 (gentoo)
Whilst is *may* have been a bug, the issue should no longer exist on a 
newer kernel.

> 
>> One interesting though, if I do : modprobe button
>> then every 30 seconds or so I get:
>> received event "battery BAT1 00000080 00000001"
>>
>> Even when i do rmmod button I still keep getting these events.
>> The only way to go back to "normal" behaviour is to reboot.
>>
>> Any suggestions as to what might be my problem here ?
>>
> I guess your battery power level is low.

Nope, that's not it.
Don't really get your logic either. *Only* when a certain module is 
loaded and after that *only* a reboot stops these messages means that 
the battery is low?

> </
> 

So, I take it that my choice is limited to using the newer kernel ?
I would normally not hesitate to use the newer kernel but my employer's 
vpn client is limited to 2.6.17

Nigel.

Re: [repost] acpi on gentoo

[Alexey Starikovskiy]

Nigel wrote:
> response inline
>
> Luming Yu said on 11/3/2007 3:12 PM:
>> On 3/11/07, Nigel <nigels@hotmail.com> wrote:
>>>
>>> Trying again to see if anyone had any other ideas.
>>>
>>> In addition:
>>> The acpid daemon is running.
>>> The same machine when booted into windows will automatically go to
>>> powersave mode when the power cable is removed.
>>>
>>
>> what condition is your battery in? It makes sense if battery power is 
>> very low.
>   Battery #1     : present
>     Remaining capacity : 47822 mWh, 100.0%
>     Design capacity    : 50760 mWh
>     Last full capacity : 47822 mWh, 94.21% of design capacity
> (similar output was included in the original post)
>
> Regardless of battery condition should I not still get an event for 
> removing and reinserting the power cable? (Obviously waiting for a 
> minute or two in-between )
>
>> If battery is still full, then it sounds like a bug.  You need to test
>> the latest base kernel before entering a acpi bug into
>> bugzilla.kernel.org.
>
> It works just fine on 2.6.19-r5 (gentoo)
> Whilst is *may* have been a bug, the issue should no longer exist on a 
> newer kernel.
>
>>
>>> One interesting though, if I do : modprobe button
>>> then every 30 seconds or so I get:
>>> received event "battery BAT1 00000080 00000001"
>>>
>>> Even when i do rmmod button I still keep getting these events.
>>> The only way to go back to "normal" behaviour is to reboot.
>>>
>>> Any suggestions as to what might be my problem here ?
>>>
>> I guess your battery power level is low.
>
> Nope, that's not it.
> Don't really get your logic either. *Only* when a certain module is 
> loaded and after that *only* a reboot stops these messages means that 
> the battery is low?
>
>> </
>>
>
> So, I take it that my choice is limited to using the newer kernel ?
> I would normally not hesitate to use the newer kernel but my 
> employer's vpn client is limited to 2.6.17
>
> Nigel.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

2.6.19-rc5 has EC driver almost re-written (drivers/acpi/ec.c). Please 
check if putting it into 2.6.17 works/helps. You may also try to put an 
2.6.20/21-rc version of the same file... It has even more changes.


Regards,
    Alex.

RE: [repost] acpi on gentoo

[Nigel]

 > Date: Sun, 11 Mar 2007 18:57:58 +0300
 > From: alexey.y.starikovskiy@linux.intel.com
 > To: nigels@hotmail.com
 > CC: luming.yu@gmail.com; linux-acpi@vger.kernel.org
 > Subject: Re: [repost] acpi on gentoo
 >
 > Nigel wrote:
 > > response inline
 > >
 > > Luming Yu said on 11/3/2007 3:12 PM:
 > >> On 3/11/07, Nigel <nigels@hotmail.com> wrote:
 > >>>
 > >>> Trying again to see if anyone had any other ideas.
 > >>>
 > >>> In addition:
 > >>> The acpid daemon is running.
 > >>> The same machine when booted into windows will automatically go to
 > >>> powersave mode when the power cable is removed.
 > >>>
 > >>
 > >> what condition is your battery in? It makes sense if battery power is
 > >> very low.
 > > Battery #1 : present
 > > Remaining capacity : 47822 mWh, 100.0%
 > > Design capacity : 50760 mWh
 > > Last full capacity : 47822 mWh, 94.21% of design capacity
 > > (similar output was included in the original post)
 > >
 > > Regardless of battery condition should I not still get an event for
 > > removing and reinserting the power cable? (Obviously waiting for a
 > > minute or two in-between )
 > >
 > >> If battery is still full, then it sounds like a bug. You need to test
 > >> the latest base kernel before entering a acpi bug into
 > >> bugzilla.kernel.org.
 > >
 > > It works just fine on 2.6.19-r5 (gentoo)
 > > Whilst is *may* have been a bug, the issue should no longer exist on a
 > > newer kernel.
 > >
 > >>
 > >>> One interesting though, if I do : modprobe button
 > >>> then every 30 seconds or so I get:
 > >>> received event "battery BAT1 00000080 00000001"
 > >>>
 > >>> Even when i do rmmod button I still keep getting these events.
 > >>> The only way to go back to "normal" behaviour is to reboot.
 > >>>
 > >>> Any suggestions as to what might be my problem here ?
 > >>>
 > >> I guess your battery power level is low.
 > >
 > > Nope, that's not it.
 > > Don't really get your logic either. *Only* when a certain module is
 > > loaded and after that *only* a reboot stops these messages means that
 > > the battery is low?
 > >
 > >> </
 > >>
 > >
 > > So, I take it that my choice is limited to using the newer kernel ?
 > > I would normally not hesitate to use the newer kernel but my
 > > employer's vpn client is limited to 2.6.17
 > >
 > > Nigel.
 > > -
 > > To unsubscribe from this list: send the line "unsubscribe 
linux-acpi" in
 > > the body of a message to majordomo@vger.kernel.org
 > > More majordomo info at http://vger.kernel.org/majordomo-info.html
 >
 > 2.6.19-rc5 has EC driver almost re-written (drivers/acpi/ec.c). Please
 > check if putting it into 2.6.17 works/helps. You may also try to put an
 > 2.6.20/21-rc version of the same file... It has even more changes.
 >
 >
 > Regards,
 > Alex.

I tried copying all of the directories with "acpi" and a few .h files as 
well (from 2.6.19-rc5) . This is what I get:

# make
   CHK     include/linux/version.h
   HOSTCC  scripts/basic/fixdep
   HOSTCC  scripts/basic/split-include
   HOSTCC  scripts/basic/docproc
   HOSTCC  scripts/kconfig/conf.o
   HOSTCC  scripts/kconfig/kxgettext.o
   HOSTCC  scripts/kconfig/mconf.o
   HOSTCC  scripts/kconfig/zconf.tab.o
   HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf -s arch/i386/Kconfig
#
# using defaults found in .config
#
   SPLIT   include/linux/autoconf.h -> include/config/*
   CC      arch/i386/kernel/asm-offsets.s
   GEN     include/asm-i386/asm-offsets.h
   CC      scripts/mod/empty.o
   HOSTCC  scripts/mod/mk_elfconfig
   MKELF   scripts/mod/elfconfig.h
   HOSTCC  scripts/mod/file2alias.o
   HOSTCC  scripts/mod/modpost.o
   HOSTCC  scripts/mod/sumversion.o
   HOSTLD  scripts/mod/modpost
   HOSTCC  scripts/kallsyms
   HOSTCC  scripts/conmakehash
   HOSTCC  scripts/bin2c
   CC      init/main.o
   CHK     include/linux/compile.h
   UPD     include/linux/compile.h
   CC      init/version.o
   CC      init/do_mounts.o
   LD      init/mounts.o
   CC      init/initramfs.o
   CC      init/calibrate.o
   LD      init/built-in.o
   HOSTCC  usr/gen_init_cpio
   GEN     usr/initramfs_data.cpio.gz
   AS      usr/initramfs_data.o
   LD      usr/built-in.o
   CC      arch/i386/kernel/process.o
   CC      arch/i386/kernel/semaphore.o
   CC      arch/i386/kernel/signal.o
   AS      arch/i386/kernel/entry.o
   CC      arch/i386/kernel/traps.o
   CC      arch/i386/kernel/irq.o
   CC      arch/i386/kernel/ptrace.o
   CC      arch/i386/kernel/time.o
   CC      arch/i386/kernel/ioport.o
   CC      arch/i386/kernel/ldt.o
   CC      arch/i386/kernel/setup.o
arch/i386/kernel/setup.c: In function 'parse_cmdline_early':
arch/i386/kernel/setup.c:869: warning: implicit declaration of function 
'disable_ioapic_setup'
   CC      arch/i386/kernel/i8259.o
   CC      arch/i386/kernel/sys_i386.o
   CC      arch/i386/kernel/pci-dma.o
   CC      arch/i386/kernel/i386_ksyms.o
   CC      arch/i386/kernel/i387.o
   CC      arch/i386/kernel/bootflag.o
   CC      arch/i386/kernel/quirks.o
   CC      arch/i386/kernel/i8237.o
   CC      arch/i386/kernel/topology.o
   CC      arch/i386/kernel/alternative.o
   CC      arch/i386/kernel/acpi/boot.o
   CC      arch/i386/kernel/acpi/earlyquirk.o
arch/i386/kernel/acpi/earlyquirk.c: In function 'check_acpi_pci':
arch/i386/kernel/acpi/earlyquirk.c:60: warning: implicit declaration of 
function 'early_pci_allowed'
   CC      arch/i386/kernel/acpi/cstate.o
arch/i386/kernel/acpi/cstate.c: In function 
'acpi_processor_ffh_cstate_enter':
arch/i386/kernel/acpi/cstate.c:141: warning: implicit declaration of 
function 'mwait_idle_with_hints'
   CC      arch/i386/kernel/acpi/processor.o
   LD      arch/i386/kernel/acpi/built-in.o
   CC      arch/i386/kernel/cpu/common.o
   CC      arch/i386/kernel/cpu/proc.o
   CC      arch/i386/kernel/cpu/amd.o
   CC      arch/i386/kernel/cpu/cyrix.o
   CC      arch/i386/kernel/cpu/centaur.o
   CC      arch/i386/kernel/cpu/transmeta.o
arch/i386/kernel/cpu/transmeta.c: In function 'init_transmeta':
arch/i386/kernel/cpu/transmeta.c:12: warning: 'cpu_freq' may be used 
uninitialized in this function
   CC      arch/i386/kernel/cpu/intel.o
   CC      arch/i386/kernel/cpu/intel_cacheinfo.o
   CC      arch/i386/kernel/cpu/rise.o
   CC      arch/i386/kernel/cpu/nexgen.o
   CC      arch/i386/kernel/cpu/umc.o
   LD      arch/i386/kernel/cpu/cpufreq/built-in.o
   CC [M]  arch/i386/kernel/cpu/cpufreq/speedstep-centrino.o
   CC [M]  arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.o
   CC      arch/i386/kernel/cpu/mcheck/mce.o
   CC      arch/i386/kernel/cpu/mcheck/k7.o
   CC      arch/i386/kernel/cpu/mcheck/p4.o
   CC      arch/i386/kernel/cpu/mcheck/p5.o
   CC      arch/i386/kernel/cpu/mcheck/p6.o
   CC      arch/i386/kernel/cpu/mcheck/winchip.o
   CC      arch/i386/kernel/cpu/mcheck/non-fatal.o
   LD      arch/i386/kernel/cpu/mcheck/built-in.o
   CC      arch/i386/kernel/cpu/mtrr/main.o
   CC      arch/i386/kernel/cpu/mtrr/if.o
   CC      arch/i386/kernel/cpu/mtrr/generic.o
   CC      arch/i386/kernel/cpu/mtrr/state.o
   CC      arch/i386/kernel/cpu/mtrr/amd.o
   CC      arch/i386/kernel/cpu/mtrr/cyrix.o
   CC      arch/i386/kernel/cpu/mtrr/centaur.o
   LD      arch/i386/kernel/cpu/mtrr/built-in.o
   LD      arch/i386/kernel/cpu/built-in.o
   CC      arch/i386/kernel/timers/timer.o
   CC      arch/i386/kernel/timers/timer_none.o
   CC      arch/i386/kernel/timers/timer_tsc.o
   CC      arch/i386/kernel/timers/timer_pit.o
   CC      arch/i386/kernel/timers/common.o
   CC      arch/i386/kernel/timers/timer_pm.o
   LD      arch/i386/kernel/timers/built-in.o
   CC      arch/i386/kernel/reboot.o
   CC      arch/i386/kernel/apm.o
arch/i386/kernel/apm.c: In function 'apm':
arch/i386/kernel/apm.c:1285: warning: 'event' may be used uninitialized 
in this function
   CC      arch/i386/kernel/mpparse.o
   CC      arch/i386/kernel/apic.o
   CC      arch/i386/kernel/nmi.o
   CC      arch/i386/kernel/io_apic.o
   CC      arch/i386/kernel/module.o
   CC      arch/i386/kernel/sysenter.o
   LDS     arch/i386/kernel/vsyscall.lds
   AS      arch/i386/kernel/vsyscall-int80.o
   AS      arch/i386/kernel/vsyscall-note.o
   SYSCALL arch/i386/kernel/vsyscall-int80.so
   AS      arch/i386/kernel/vsyscall-sysenter.o
   SYSCALL arch/i386/kernel/vsyscall-sysenter.so
   AS      arch/i386/kernel/vsyscall.o
   CC      arch/i386/kernel/doublefault.o
   CC      arch/i386/kernel/vm86.o
   CC      arch/i386/kernel/early_printk.o
   SYSCALL arch/i386/kernel/vsyscall-syms.o
   LD      arch/i386/kernel/built-in.o
arch/i386/kernel/acpi/built-in.o:(.bss+0x0): multiple definition of 
`acpi_disabled'
arch/i386/kernel/setup.o:(.bss+0x4): first defined here
make[1]: *** [arch/i386/kernel/built-in.o] Error 1
make: *** [arch/i386/kernel] Error 2

If there is a relatively simple way to get this to work. Let me know.
Otherwise I'll just leave it, and hopefully in a year or so I'll be able 
  to upgrade.

Thanks,
Nigel.

Re: [repost] acpi on gentoo

[Alexey Starikovskiy]

Nigel wrote:
>
> > Date: Sun, 11 Mar 2007 18:57:58 +0300
> > From: alexey.y.starikovskiy@linux.intel.com
> > To: nigels@hotmail.com
> > CC: luming.yu@gmail.com; linux-acpi@vger.kernel.org
> > Subject: Re: [repost] acpi on gentoo
> >
> > Nigel wrote:
> > > response inline
> > >
> > > Luming Yu said on 11/3/2007 3:12 PM:
> > >> On 3/11/07, Nigel <nigels@hotmail.com> wrote:
> > >>>
> > >>> Trying again to see if anyone had any other ideas.
> > >>>
> > >>> In addition:
> > >>> The acpid daemon is running.
> > >>> The same machine when booted into windows will automatically go to
> > >>> powersave mode when the power cable is removed.
> > >>>
> > >>
> > >> what condition is your battery in? It makes sense if battery 
> power is
> > >> very low.
> > > Battery #1 : present
> > > Remaining capacity : 47822 mWh, 100.0%
> > > Design capacity : 50760 mWh
> > > Last full capacity : 47822 mWh, 94.21% of design capacity
> > > (similar output was included in the original post)
> > >
> > > Regardless of battery condition should I not still get an event for
> > > removing and reinserting the power cable? (Obviously waiting for a
> > > minute or two in-between )
> > >
> > >> If battery is still full, then it sounds like a bug. You need to 
> test
> > >> the latest base kernel before entering a acpi bug into
> > >> bugzilla.kernel.org.
> > >
> > > It works just fine on 2.6.19-r5 (gentoo)
> > > Whilst is *may* have been a bug, the issue should no longer exist 
> on a
> > > newer kernel.
> > >
> > >>
> > >>> One interesting though, if I do : modprobe button
> > >>> then every 30 seconds or so I get:
> > >>> received event "battery BAT1 00000080 00000001"
> > >>>
> > >>> Even when i do rmmod button I still keep getting these events.
> > >>> The only way to go back to "normal" behaviour is to reboot.
> > >>>
> > >>> Any suggestions as to what might be my problem here ?
> > >>>
> > >> I guess your battery power level is low.
> > >
> > > Nope, that's not it.
> > > Don't really get your logic either. *Only* when a certain module is
> > > loaded and after that *only* a reboot stops these messages means that
> > > the battery is low?
> > >
> > >> </
> > >>
> > >
> > > So, I take it that my choice is limited to using the newer kernel ?
> > > I would normally not hesitate to use the newer kernel but my
> > > employer's vpn client is limited to 2.6.17
> > >
> > > Nigel.
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe 
> linux-acpi" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> > 2.6.19-rc5 has EC driver almost re-written (drivers/acpi/ec.c). Please
> > check if putting it into 2.6.17 works/helps. You may also try to put an
> > 2.6.20/21-rc version of the same file... It has even more changes.
> >
> >
> > Regards,
> > Alex.
>
> I tried copying all of the directories with "acpi" and a few .h files 
> as well (from 2.6.19-rc5) . This is what I get:
>
> [skipped]
I asked if copying of single file helps... I didn't ask you to copy all 
acpi files two kernel releases back and make it work...
> If there is a relatively simple way to get this to work. Let me know.
Copy one file: drivers/acpi/ec.c
> Otherwise I'll just leave it, and hopefully in a year or so I'll be 
> able  to upgrade.
>
Ok.
> Thanks,
> Nigel.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: [repost] acpi on gentoo

[Nigel Nigel]

----------------------------------------
> Date: Mon, 12 Mar 2007 14:16:51 +0300
> From: alexey.y.starikovskiy@linux.intel.com
> To: nigels@hotmail.com
> CC: linux-acpi@vger.kernel.org
> Subject: Re: [repost] acpi on gentoo
> 
> Nigel wrote:
> >
> > > Date: Sun, 11 Mar 2007 18:57:58 +0300
> > > From: alexey.y.starikovskiy@linux.intel.com
> > > To: nigels@hotmail.com
> > > CC: luming.yu@gmail.com; linux-acpi@vger.kernel.org
> > > Subject: Re: [repost] acpi on gentoo
> > >
> > > Nigel wrote:
> > > > response inline
> > > >
> > > > Luming Yu said on 11/3/2007 3:12 PM:
> > > >> On 3/11/07, Nigel  wrote:
> > > >>>
> > > >>> Trying again to see if anyone had any other ideas.
> > > >>>
> > > >>> In addition:
> > > >>> The acpid daemon is running.
> > > >>> The same machine when booted into windows will automatically go to
> > > >>> powersave mode when the power cable is removed.
> > > >>>
> > > >>
> > > >> what condition is your battery in? It makes sense if battery 
> > power is
> > > >> very low.
> > > > Battery #1 : present
> > > > Remaining capacity : 47822 mWh, 100.0%
> > > > Design capacity : 50760 mWh
> > > > Last full capacity : 47822 mWh, 94.21% of design capacity
> > > > (similar output was included in the original post)
> > > >
> > > > Regardless of battery condition should I not still get an event for
> > > > removing and reinserting the power cable? (Obviously waiting for a
> > > > minute or two in-between )
> > > >
> > > >> If battery is still full, then it sounds like a bug. You need to 
> > test
> > > >> the latest base kernel before entering a acpi bug into
> > > >> bugzilla.kernel.org.
> > > >
> > > > It works just fine on 2.6.19-r5 (gentoo)
> > > > Whilst is *may* have been a bug, the issue should no longer exist 
> > on a
> > > > newer kernel.
> > > >
> > > >>
> > > >>> One interesting though, if I do : modprobe button
> > > >>> then every 30 seconds or so I get:
> > > >>> received event "battery BAT1 00000080 00000001"
> > > >>>
> > > >>> Even when i do rmmod button I still keep getting these events.
> > > >>> The only way to go back to "normal" behaviour is to reboot.
> > > >>>
> > > >>> Any suggestions as to what might be my problem here ?
> > > >>>
> > > >> I guess your battery power level is low.
> > > >
> > > > Nope, that's not it.
> > > > Don't really get your logic either. *Only* when a certain module is
> > > > loaded and after that *only* a reboot stops these messages means that
> > > > the battery is low?
> > > >
> > > >>  > > >>
> > > >
> > > > So, I take it that my choice is limited to using the newer kernel ?
> > > > I would normally not hesitate to use the newer kernel but my
> > > > employer's vpn client is limited to 2.6.17
> > > >
> > > > Nigel.
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe 
> > linux-acpi" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > > 2.6.19-rc5 has EC driver almost re-written (drivers/acpi/ec.c). Please
> > > check if putting it into 2.6.17 works/helps. You may also try to put an
> > > 2.6.20/21-rc version of the same file... It has even more changes.
> > >
> > >
> > > Regards,
> > > Alex.
> >
> > I tried copying all of the directories with "acpi" and a few .h files 
> > as well (from 2.6.19-rc5) . This is what I get:
> >
> > [skipped]
> I asked if copying of single file helps... I didn't ask you to copy all 
> acpi files two kernel releases back and make it work...
> > If there is a relatively simple way to get this to work. Let me know.
> Copy one file: drivers/acpi/ec.c

Sorry, I should have explained in more detail. I did copy just the one file to start with, and  got this :
CHK     include/linux/version.h
CHK     include/linux/compile.h
CC      drivers/acpi/ec.o
drivers/acpi/ec.c: In function 'acpi_ec_gpe_handler':
drivers/acpi/ec.c:467: warning: implicit declaration of function
'acpi_os_execute'
drivers/acpi/ec.c:467: error: 'OSL_EC_BURST_HANDLER' undeclared (first
use in this function)
drivers/acpi/ec.c:467: error: (Each undeclared identifier is reported
only once
drivers/acpi/ec.c:467: error: for each function it appears in.)
make[2]: *** [drivers/acpi/ec.o] Error 1
make[1]: *** [drivers/acpi] Error 2
make: *** [drivers] Error 2


Is there something I can do to get this going ?

> > Otherwise I'll just leave it, and hopefully in a year or so I'll be 
> > able  to upgrade.
> >
> Ok.
> > Thanks,
> > Nigel.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Re: [repost] acpi on gentoo

[Alexey Starikovskiy]

Nigel Nigel wrote:
>
>
>
>
>
> ----------------------------------------
>   
>> Date: Mon, 12 Mar 2007 14:16:51 +0300
>> From: alexey.y.starikovskiy@linux.intel.com
>> To: nigels@hotmail.com
>> CC: linux-acpi@vger.kernel.org
>> Subject: Re: [repost] acpi on gentoo
>>
>> Nigel wrote:
>>     
>>>> Date: Sun, 11 Mar 2007 18:57:58 +0300
>>>> From: alexey.y.starikovskiy@linux.intel.com
>>>> To: nigels@hotmail.com
>>>> CC: luming.yu@gmail.com; linux-acpi@vger.kernel.org
>>>> Subject: Re: [repost] acpi on gentoo
>>>>
>>>> Nigel wrote:
>>>>         
>>>>> response inline
>>>>>
>>>>> Luming Yu said on 11/3/2007 3:12 PM:
>>>>>           
>>>>>> On 3/11/07, Nigel  wrote:
>>>>>>             
>>>>>>> Trying again to see if anyone had any other ideas.
>>>>>>>
>>>>>>> In addition:
>>>>>>> The acpid daemon is running.
>>>>>>> The same machine when booted into windows will automatically go to
>>>>>>> powersave mode when the power cable is removed.
>>>>>>>
>>>>>>>               
>>>>>> what condition is your battery in? It makes sense if battery 
>>>>>>             
>>> power is
>>>       
>>>>>> very low.
>>>>>>             
>>>>> Battery #1 : present
>>>>> Remaining capacity : 47822 mWh, 100.0%
>>>>> Design capacity : 50760 mWh
>>>>> Last full capacity : 47822 mWh, 94.21% of design capacity
>>>>> (similar output was included in the original post)
>>>>>
>>>>> Regardless of battery condition should I not still get an event for
>>>>> removing and reinserting the power cable? (Obviously waiting for a
>>>>> minute or two in-between )
>>>>>
>>>>>           
>>>>>> If battery is still full, then it sounds like a bug. You need to 
>>>>>>             
>>> test
>>>       
>>>>>> the latest base kernel before entering a acpi bug into
>>>>>> bugzilla.kernel.org.
>>>>>>             
>>>>> It works just fine on 2.6.19-r5 (gentoo)
>>>>> Whilst is *may* have been a bug, the issue should no longer exist 
>>>>>           
>>> on a
>>>       
>>>>> newer kernel.
>>>>>
>>>>>           
>>>>>>> One interesting though, if I do : modprobe button
>>>>>>> then every 30 seconds or so I get:
>>>>>>> received event "battery BAT1 00000080 00000001"
>>>>>>>
>>>>>>> Even when i do rmmod button I still keep getting these events.
>>>>>>> The only way to go back to "normal" behaviour is to reboot.
>>>>>>>
>>>>>>> Any suggestions as to what might be my problem here ?
>>>>>>>
>>>>>>>               
>>>>>> I guess your battery power level is low.
>>>>>>             
>>>>> Nope, that's not it.
>>>>> Don't really get your logic either. *Only* when a certain module is
>>>>> loaded and after that *only* a reboot stops these messages means that
>>>>> the battery is low?
>>>>>
>>>>>           
>>>>>>  > > >>
>>>>>>             
>>>>> So, I take it that my choice is limited to using the newer kernel ?
>>>>> I would normally not hesitate to use the newer kernel but my
>>>>> employer's vpn client is limited to 2.6.17
>>>>>
>>>>> Nigel.
>>>>> -
>>>>> To unsubscribe from this list: send the line "unsubscribe 
>>>>>           
>>> linux-acpi" in
>>>       
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>>           
>>>> 2.6.19-rc5 has EC driver almost re-written (drivers/acpi/ec.c). Please
>>>> check if putting it into 2.6.17 works/helps. You may also try to put an
>>>> 2.6.20/21-rc version of the same file... It has even more changes.
>>>>
>>>>
>>>> Regards,
>>>> Alex.
>>>>         
>>> I tried copying all of the directories with "acpi" and a few .h files 
>>> as well (from 2.6.19-rc5) . This is what I get:
>>>
>>> [skipped]
>>>       
>> I asked if copying of single file helps... I didn't ask you to copy all 
>> acpi files two kernel releases back and make it work...
>>     
>>> If there is a relatively simple way to get this to work. Let me know.
>>>       
>> Copy one file: drivers/acpi/ec.c
>>     
>
> Sorry, I should have explained in more detail. I did copy just the one file to start with, and  got this :
> CHK     include/linux/version.h
> CHK     include/linux/compile.h
> CC      drivers/acpi/ec.o
> drivers/acpi/ec.c: In function 'acpi_ec_gpe_handler':
> drivers/acpi/ec.c:467: warning: implicit declaration of function
> 'acpi_os_execute'
> drivers/acpi/ec.c:467: error: 'OSL_EC_BURST_HANDLER' undeclared (first
> use in this function)
> drivers/acpi/ec.c:467: error: (Each undeclared identifier is reported
> only once
> drivers/acpi/ec.c:467: error: for each function it appears in.)
> make[2]: *** [drivers/acpi/ec.o] Error 1
> make[1]: *** [drivers/acpi] Error 2
> make: *** [drivers] Error 2
>
>
> Is there something I can do to get this going ?
>
>   
change call to acpi_os_execute to call to acpi_os_queue_for_execution() 
as it was in 2.6.17.
It is just rename of the function in this case.
>>> Otherwise I'll just leave it, and hopefully in a year or so I'll be 
>>> able  to upgrade.
>>>
>>>       
>> Ok.
>>     
>>> Thanks,
>>> Nigel.
>>> -
>>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>       
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>     
>
> _________________________________________________________________
> Explore the seven wonders of the world
> http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Re: [repost] acpi on gentoo

[Nigel]

Alexey Starikovskiy said on 12/03/2007 2:46 PM:
> Nigel Nigel wrote:
>>
>>
>>
>>
>>
>> ----------------------------------------
>>  
>>> Date: Mon, 12 Mar 2007 14:16:51 +0300
>>> From: alexey.y.starikovskiy@linux.intel.com
>>> To: nigels@hotmail.com
>>> CC: linux-acpi@vger.kernel.org
>>> Subject: Re: [repost] acpi on gentoo
>>>
>>> Nigel wrote:
>>>    
>>>>> Date: Sun, 11 Mar 2007 18:57:58 +0300
>>>>> From: alexey.y.starikovskiy@linux.intel.com
>>>>> To: nigels@hotmail.com
>>>>> CC: luming.yu@gmail.com; linux-acpi@vger.kernel.org
>>>>> Subject: Re: [repost] acpi on gentoo
>>>>>
>>>>> Nigel wrote:
>>>>>        
>>>>>> response inline
>>>>>>
>>>>  
>>>>
>>>> [skipped]
>>>>       
>>> I asked if copying of single file helps... I didn't ask you to copy 
>>> all acpi files two kernel releases back and make it work...
>>>    
>>>> If there is a relatively simple way to get this to work. Let me know.
>>>>       
>>> Copy one file: drivers/acpi/ec.c
>>>     
>>
>> Sorry, I should have explained in more detail. I did copy just the 
>> one file to start with, and  got this :
>> CHK     include/linux/version.h
>> CHK     include/linux/compile.h
>> CC      drivers/acpi/ec.o
>> drivers/acpi/ec.c: In function 'acpi_ec_gpe_handler':
>> drivers/acpi/ec.c:467: warning: implicit declaration of function
>> 'acpi_os_execute'
>> drivers/acpi/ec.c:467: error: 'OSL_EC_BURST_HANDLER' undeclared (first
>> use in this function)
>> drivers/acpi/ec.c:467: error: (Each undeclared identifier is reported
>> only once
>> drivers/acpi/ec.c:467: error: for each function it appears in.)
>> make[2]: *** [drivers/acpi/ec.o] Error 1
>> make[1]: *** [drivers/acpi] Error 2
>> make: *** [drivers] Error 2
>>
>>
>> Is there something I can do to get this going ?
>>
>>   
> change call to acpi_os_execute to call to 
> acpi_os_queue_for_execution() as it was in 2.6.17.
> It is just rename of the function in this case.

I changed this:
 status = acpi_os_execute(OSL_EC_BURST_HANDLER,acpi_ec_gpe_query, ec);

To this:
status = acpi_os_queue_for_execution(OSD_PRIORITY_MED,acpi_ec_gpe_query, 
ec);

Not sure if this is the right thing there: OSD_PRIORITY_MED

It compiles with a warning:

# make
CHK     include/linux/version.h
CHK     include/linux/compile.h
LD [M]  drivers/acpi/processor.o
Kernel: arch/i386/boot/bzImage is ready  (#29)
Building modules, stage 2.
 MODPOST
WARNING: drivers/acpi/processor.o - Section mismatch: reference to
 .init.data: from .text between 'acpi_processor_power_init' (at
 offset 0xe75) and 'acpi_safe_halt'


 LD [M]  drivers/acpi/processor.k


Is this warning a problem  ?

Well, nothing seems to have changed it works as before. Still no events 
received by acpid

>>>> Otherwise I'll just leave it, and hopefully in a year or so I'll be 
>>>> able  to upgrade.
>>>>
>>>>       
>>> Ok.
>>>    
>>>> Thanks,
>>>> Nigel.
>>>> -
>>>> To unsubscribe from this list: send the line "unsubscribe 
>>>> linux-acpi" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>       
>>> -
>>> To unsubscribe from this list: send the line "unsubscribe 
>>> linux-acpi" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>     
>>
>> _________________________________________________________________
>> Explore the seven wonders of the world
>> http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> </pre
>