battery issue with xfce4

On Sep 27, 4:09 am, emmel <em....TakeThisOut@invalid.invalid> wrote:
> Thus Jeff spoke:
>
> > Hi, i am using Xfce4 in slackware 13.0 with my laptop, and i installed
> > xfce4-battery-plugin
> > but when i add the plugin itto xfce4-panel, it does not work, no icon
> > on the panel.
> > and i found no status files in the following path
> > /proc/acpi/ac_adapter
> > /proc/acpi/battery
> > /sys/class/power_supply
> > and i had added  these two lines "/sbin/modprobe/button & /sbin/
> > modprobe battery" in /etc/rc.d/rc.modules
>
> That's your problem right here. /proc/acpi/battery/BAT1/{status|info}
> both have to exist or there's no way for the program to get the
> necessary information. That *should* be provided by the acpi battery
> module, but if it does not... Tough luck.

when the kernel >2.6.24,the path "proc" had be obsolete, and the
status of battery could be found in path /sys/class/power_supply
and you are right , there's no way for the program to get the
necessary information of battery
and when i run acpitool, it said no battery available. same as the ac
adapter.
it seems acpi battery module does not support my battery.doesn't it?
but any way, thank you for your help.

Thus Jeff spoke:

> On Sep 27, 4:09 am, emmel <em....DeleteThis@invalid.invalid> wrote:
>> Thus Jeff spoke:
>>
>> > Hi, i am using Xfce4 in slackware 13.0 with my laptop, and i installed
>> > xfce4-battery-plugin
>> > but when i add the plugin itto xfce4-panel, it does not work, no icon
>> > on the panel.
>> > and i found no status files in the following path
>> > /proc/acpi/ac_adapter
>> > /proc/acpi/battery
>> > /sys/class/power_supply
>> > and i had added  these two lines "/sbin/modprobe/button & /sbin/
>> > modprobe battery" in /etc/rc.d/rc.modules
>>
>> That's your problem right here. /proc/acpi/battery/BAT1/{status|info}
>> both have to exist or there's no way for the program to get the
>> necessary information. That *should* be provided by the acpi battery
>> module, but if it does not... Tough luck.
>
> when the kernel >2.6.24,the path "proc" had be obsolete, and the
> status of battery could be found in path /sys/class/power_supply

Oops. I still use the proc interface from command line, but then I
probably have configured the kernel to allow for some legacy acpi
interface.

> and you are right , there's no way for the program to get the
> necessary information of battery
> and when i run acpitool, it said no battery available. same as the ac
> adapter.

Does acpitool come with Slack? I don't seem to have that on my system.

> it seems acpi battery module does not support my battery.doesn't it?
> but any way, thank you for your help.

I wish I could have been more helpful. Maybe Google will turn up some
information for your particular hardware?

On Sep 28, 3:11 am, emmel <em....RemoveThis@invalid.invalid> wrote:
> Thus Jeff spoke:
>
>
>
> > On Sep 27, 4:09 am, emmel <em....RemoveThis@invalid.invalid> wrote:
> >> Thus Jeff spoke:
>
> >> > Hi, i am using Xfce4 in slackware 13.0 with my laptop, and i installed
> >> > xfce4-battery-plugin
> >> > but when i add the plugin itto xfce4-panel, it does not work, no icon
> >> > on the panel.
> >> > and i found no status files in the following path
> >> > /proc/acpi/ac_adapter
> >> > /proc/acpi/battery
> >> > /sys/class/power_supply
> >> > and i had added  these two lines "/sbin/modprobe/button & /sbin/
> >> > modprobe battery" in /etc/rc.d/rc.modules
>
> >> That's your problem right here. /proc/acpi/battery/BAT1/{status|info}
> >> both have to exist or there's no way for the program to get the
> >> necessary information. That *should* be provided by the acpi battery
> >> module, but if it does not... Tough luck.
>
> > when the kernel >2.6.24,the path "proc" had  be obsolete, and the
> > status of battery could be found in path  /sys/class/power_supply
>
> Oops. I still use the proc interface from command line, but then I
> probably have configured the kernel to allow for some legacy acpi
> interface.
>
> > and you are right ,  there's no way for the program to get the
> > necessary information of battery
> > and when i run acpitool, it said no battery available. same as the ac
> > adapter.
>
> Does acpitool come with Slack? I don't seem to have that on my system.
>
> > it seems acpi battery module does not support my battery.doesn't it?
> > but any way, thank you for your help.
>
> I wish I could have been more helpful. Maybe Google will turn up some
> information for your particular hardware?

i download acpitools from the siackbuilds site.
but last time i setup windows xp, it is good.
and emmel, i could not find the config of legacy acpi, i used the
kernel hugesmp.s
where to setup it? thanks.

Thus Jeff spoke:

> On Sep 28, 3:11 am, emmel <em... DeleteThis @invalid.invalid> wrote:
>> Thus Jeff spoke:
>>
>> > On Sep 27, 4:09 am, emmel <em... DeleteThis @invalid.invalid> wrote:
>> >> Thus Jeff spoke:
>>
>> >> > Hi, i am using Xfce4 in slackware 13.0 with my laptop, and i installed
>> >> > xfce4-battery-plugin
>> >> > but when i add the plugin itto xfce4-panel, it does not work, no icon
>> >> > on the panel.
>> >> > and i found no status files in the following path
>> >> > /proc/acpi/ac_adapter
>> >> > /proc/acpi/battery
>> >> > /sys/class/power_supply
>> >> > and i had added  these two lines "/sbin/modprobe/button & /sbin/
>> >> > modprobe battery" in /etc/rc.d/rc.modules
>>
>> >> That's your problem right here. /proc/acpi/battery/BAT1/{status|info}
>> >> both have to exist or there's no way for the program to get the
>> >> necessary information. That *should* be provided by the acpi battery
>> >> module, but if it does not... Tough luck.
>>
>> > when the kernel >2.6.24,the path "proc" had  be obsolete, and the
>> > status of battery could be found in path  /sys/class/power_supply
>>
>> Oops. I still use the proc interface from command line, but then I
>> probably have configured the kernel to allow for some legacy acpi
>> interface.
>>
>> > and you are right ,  there's no way for the program to get the
>> > necessary information of battery
>> > and when i run acpitool, it said no battery available. same as the ac
>> > adapter.
>>
>> Does acpitool come with Slack? I don't seem to have that on my system.
>>
>> > it seems acpi battery module does not support my battery.doesn't it?
>> > but any way, thank you for your help.
>>
>> I wish I could have been more helpful. Maybe Google will turn up some
>> information for your particular hardware?
>
> i download acpitools from the siackbuilds site.

Ah. I'll have a look.

> but last time i setup windows xp, it is good.

You have to realise that Linux is *not* Windows. That is especially true
when it comes to hardware that is supported by some proprietary driver
instead of open standards.
It's odd, though, that any newer hardware shouldn't use the ACPI
battery interface. I thought all machines built over the last ten years
or so did. What's the make of your machine?

> and emmel, i could not find the config of legacy acpi, i used the
> kernel hugesmp.s
> where to setup it? thanks.

In short: You don't. You'd have to build your own kernel for that, but
if you have to ask, you probably shouldn't.

> You have to realise that Linux is *not* Windows. That is especially true
>when it comes to hardware that is supported by some proprietary driver
>instead of open standards.
> It's odd, though, that any newer hardware shouldn't use the ACPI
>battery interface. I thought all machines built over the last ten years
>or so did. What's the make of your machine?

i remembered i bought this notebook on 2006. and its maker is Benq S53
you said any newer hardware should not use ACPI battery interface
then how they get information of battery or ac adapter?
the main problem for me is that there is no file in the following
address, which mean the acpi daemon can not get
the information from the ac adapter and battery.
/proc/acpi/ac_adapter
/proc/acpi/battery
/sys/class/power_supply

i checked the config file of hugesmp.s
ac adapter and battery had been built to module.
CONFIG_PM=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION="\"\""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_BLACKLIST_YEAR=2001
CONFIG_ACPI_PCI_SLOT=m
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_X86_APM_BOOT=y
CONFIG_APM=m
and i added line "/sbin/modprobe battery" and "/sbin/modprobe ac" in /
etc/rc.d/rc.modules

Thus Jeff spoke:

>> You have to realise that Linux is *not* Windows. That is especially true
>>when it comes to hardware that is supported by some proprietary driver
>>instead of open standards.
>> It's odd, though, that any newer hardware shouldn't use the ACPI
>>battery interface. I thought all machines built over the last ten years
>>or so did. What's the make of your machine?
>
> i remembered i bought this notebook on 2006. and its maker is Benq S53

That isn't *too* old...

> you said any newer hardware should not use ACPI battery interface
> then how they get information of battery or ac adapter?

Actually I said it was odd for a newer make not to use ACPI.

> the main problem for me is that there is no file in the following
> address, which mean the acpi daemon can not get
> the information from the ac adapter and battery.
> /proc/acpi/ac_adapter
> /proc/acpi/battery
> /sys/class/power_supply

/sys/class/power_supply is the new interface and should *always* be
present, regardless of the kernel configuration (I think).

> i checked the config file of hugesmp.s
> ac adapter and battery had been built to module.
> CONFIG_ACPI=y
> CONFIG_ACPI_SLEEP=y
> CONFIG_ACPI_PROCFS=y
> CONFIG_ACPI_PROCFS_POWER=y
> CONFIG_ACPI_SYSFS_POWER=y
> CONFIG_ACPI_PROC_EVENT=y
> CONFIG_ACPI_AC=m
> CONFIG_ACPI_BATTERY=m
> CONFIG_ACPI_BUTTON=m
> CONFIG_ACPI_VIDEO=m
> CONFIG_ACPI_FAN=m
> CONFIG_ACPI_DOCK=y
> CONFIG_ACPI_PROCESSOR=m
> CONFIG_ACPI_HOTPLUG_CPU=y
> CONFIG_ACPI_THERMAL=m
> CONFIG_ACPI_BLACKLIST_YEAR=2001
> CONFIG_ACPI_PCI_SLOT=m
> CONFIG_X86_PM_TIMER=y
> CONFIG_ACPI_CONTAINER=m
> CONFIG_X86_APM_BOOT=y
> CONFIG_APM=m
> and i added line "/sbin/modprobe battery" and "/sbin/modprobe ac" in /
> etc/rc.d/rc.modules

Let's see...

CONFIG_ACPI_PROCFS_POWER:

For backwards compatibility, this option allows
deprecated power /proc/acpi/ directories to exist, even when
they have been replaced by functions in /sys.
The deprecated directories (and their replacements) include:
/proc/acpi/battery/* (/sys/class/power_supply/*)
/proc/acpi/ac_adapter/* (sys/class/power_supply/*)
This option has no effect on /proc/acpi/ directories
and functions, which do not yet exist in /sys

Say N to delete power /proc/acpi/ directories that have moved to /sys/


CONFIG_ACPI_SYSFS_POWER:

Say N to disable power /sys interface


You see? Everything's fine and hugesmp should export everything to
/sys/class/power_supply if there is hardware support. I don't think you
even need to do any manual modprobes as this ought to be handled by the
module autoloader - again, if your hardware is supported.

After some nominal digging on the net I turned up this:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/117773

So it seems you have some of these 'smart' (Ha!) batteries. The kernel
option for that baby is probably ACPI_SBS with the modules sbs and
sbshc.

HTH/HANDA

On Sep 30, 2:37 am, emmel <em....TakeThisOut@invalid.invalid> wrote:
> Thus Jeff spoke:
>
> >> You have to realise that Linux is *not* Windows. That is especially true
> >>when it comes to hardware that is supported by some proprietary driver
> >>instead of open standards.
> >>        It's odd, though, that any newer hardware shouldn't use the ACPI
> >>battery interface. I thought all machines built over the last ten years
> >>or so did. What's the make of your machine?
>
> > i remembered i bought this notebook on 2006. and its maker is Benq S53
>
> That isn't *too* old...
>
> > you said any newer hardware should not use  ACPI battery interface
> > then how they get information of battery or ac adapter?
>
> Actually I said it was odd for a newer make not to use ACPI.
>
> > the main problem for me is that there is no file in the following
> > address, which mean the acpi daemon can not get
> > the information from the ac adapter and battery.
> > /proc/acpi/ac_adapter
> > /proc/acpi/battery
> > /sys/class/power_supply
>
> /sys/class/power_supply is the new interface and should *always* be
> present, regardless of the kernel configuration (I think).
>
>
>
> > i checked the config file of hugesmp.s
> > ac adapter and battery had been built to module.
> > CONFIG_ACPI=y
> > CONFIG_ACPI_SLEEP=y
> > CONFIG_ACPI_PROCFS=y
> > CONFIG_ACPI_PROCFS_POWER=y
> > CONFIG_ACPI_SYSFS_POWER=y
> > CONFIG_ACPI_PROC_EVENT=y
> > CONFIG_ACPI_AC=m
> > CONFIG_ACPI_BATTERY=m
> > CONFIG_ACPI_BUTTON=m
> > CONFIG_ACPI_VIDEO=m
> > CONFIG_ACPI_FAN=m
> > CONFIG_ACPI_DOCK=y
> > CONFIG_ACPI_PROCESSOR=m
> > CONFIG_ACPI_HOTPLUG_CPU=y
> > CONFIG_ACPI_THERMAL=m
> > CONFIG_ACPI_BLACKLIST_YEAR=2001
> > CONFIG_ACPI_PCI_SLOT=m
> > CONFIG_X86_PM_TIMER=y
> > CONFIG_ACPI_CONTAINER=m
> > CONFIG_X86_APM_BOOT=y
> > CONFIG_APM=m
> > and i added line "/sbin/modprobe battery" and "/sbin/modprobe ac" in /
> > etc/rc.d/rc.modules
>
> Let's see...
>
> CONFIG_ACPI_PROCFS_POWER:            
>
> For backwards compatibility, this option allows  
> deprecated power /proc/acpi/ directories to exist, even when
> they have been replaced by functions in /sys.  
> The deprecated directories (and their replacements) include:
> /proc/acpi/battery/* (/sys/class/power_supply/*)
> /proc/acpi/ac_adapter/* (sys/class/power_supply/*)
> This option has no effect on /proc/acpi/ directories
> and functions, which do not yet exist in /sys      
>
> Say N to delete power /proc/acpi/ directories that have moved to /sys/
>
> CONFIG_ACPI_SYSFS_POWER:          
>
> Say N to disable power /sys interface  
>
> You see? Everything's fine and hugesmp should export everything to
> /sys/class/power_supply if there is hardware support. I don't think you
> even need to do any manual modprobes as this ought to be handled by the
> module autoloader - again, if your hardware is supported.
>
> After some nominal digging on the net I turned up this:https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/11...
>
> So it seems you have some of these 'smart' (Ha!) batteries. The kernel
> option for that baby is probably ACPI_SBS with the modules sbs and
> sbshc.
>
> HTH/HANDA

Tnank you for your help! -_-