pbbuttons-users — Everything regarding pbbuttons' usage and develpment

Crash on Resume from Sleep

[Ted D. <tjd...@gm...>]

Hello everyone,

I am running Fedora Core 5 on a Titanium PowerBook G4 667MHz,
pbbuttonsd-0.7.2-1.
The machine will go to sleep fine when I press the power button or close th=
e
lid, but upon wakeup, it locks up with the message

Badness in wait_for_ready at drivers/ide/ide-iops.c:516

and then a stack trace.

Can anyone offer any advice?  Please reply directly to me, I'm not on the
list.

Thanks,

Ted

Crash on Resume from Sleep

[Ted D. <tjd...@gm...>]

Hello everyone,

I am running Fedora Core 5 on a Titanium PowerBook G4 667MHz,
pbbuttonsd-0.7.2-1.
The machine will go to sleep fine when I press the power button or close th=
e
lid, but upon wakeup, it locks up with the message

Badness in wait_for_ready at drivers/ide/ide-iops.c:516

and then a stack trace.

Can anyone offer any advice?  Please reply directly to me, I'm not on the
list.

Thanks,

Ted

Re: display autoadjust and blank screen

[Kristian B. <kb...@op...>]

On Thu, 2006-02-23 at 15:42 +0100, Yves-Alexis Perez wrote:
> On Thu, 2006-02-23 at 00:17 +0100, Yves-Alexis Perez wrote:
> > On Wed, 2006-02-22 at 21:39 +0100, Matthias Grimm wrote:
> > > Back to your question. It is not a bug. The responsible code is in
> > > module_display, function display_keyboard(), first part of the
> > > switch(changed){} statement, line 315-316.
> > > 
> > > When automatic mode is active, the brightness keys generate an offset
> > > that will be added to the value from the automatic brightness
> > > controller. This offset will be clipped if the overall brightness
> > > level is out of range. The limits are 1 or BRIGHTNESS_MAX.
> > 
> > ok
> > 
> > > 
> > > You might change the lower limit to 0 to be able to switch off your
> > > display completely also in automatic mode. But keep in mind that this
> > > value still depends on the ambient light level. That means if the
> > > environment goes darker, the backlight might be switched on again.
> > 
> 
> Ok, so, attached is a (dirty) patch which enable switching off the LCD
> while in automatic adjust mode. In order not to depends on the ambient
> light leve i've set the status to OFF, which works but may not be really
> clean.

This might be a bit late, but I made this script a while ago to handle
this. I do agree that pbbuttonsd should handle it with the buttons duh.

#!/bin/sh

# Do not autoadjust the lcd while blanking the screen.
pbbcmd config LCDAUTOADJUST 0

# It take some time to set the brightness to 0, wait until its done.
until [ "`pbbcmd query LCDBRIGHTNESS | sed -e 's/ //g'`" == "0" ]
do
    pbbcmd config LCDBRIGHTNESS 0
done

# Then check at regular interval to see if the user changed the brightness.
while [ "`pbbcmd query LCDBRIGHTNESS | sed -e 's/ //g'`" == "0" ]
do
    sleep 5
done

# Finish by resetting the autoadjust.
pbbcmd config LCDAUTOADJUST 1

--
Kristian

Re: pbbuttonsd not loading every dev event

[Kristian B. <kb...@op...>]

On Sun, 2006-03-19 at 12:08 -0500, Kristian Benoit wrote:
> On Sat, 2006-03-18 at 12:51 +0100, Matthias Grimm wrote: 
> > On Sat, 18 Mar 2006 05:34:27 -0500
> > Kristian Benoit <kb...@op...> wrote:
> > 
> > > I had this problem a few times, pbbuttonsd does not recognize the eject
> > > button. Plus the appletouch (absolute coordinate) events does not reset
> > > the sleep timeout so I must press a key.
> > > 
> > > Some devices have the same vendor/product id. For example, the keyboard
> > > (/dev/input/event3) has the same vendor/product as the eject key
> > > (/dev/input/event4).
> > > 
> > > The appletouch also have the same ids as another event device too with a
> > > lower number. So those where ignored by pbbuttonsd.
> > 
> > Oh no. :-( You can't rely on nothing nowadays. Why do we define
> > standards when nobody follows them anyway? :-/
> >  
> > > I quikfixed my version, but I still have a strange behavior:
> > 
> > Could you please tell me how you did this? We need a good workaround
> > for this quirk.
> 
> As my appletouch is represented by the device /dev/input/event6 and the
> other with the same number is lower, I tried openning the device in
> reverse order, but then the fn button did not work and the screen was
> not dimming anymore. So I hardcoded the device numbers I need:
> 
>  for (n = 0; n < EVDEVCOUNT; n++) {
>         sprintf(filename, "/dev/input/event%d", n);
>         if ((fd = open(filename, O_RDONLY)) >= 0) {
>             ioctl(fd, EVIOCGID, id);
>             venprod = (gpointer) (id[ID_VENDOR]<<16 | id[ID_PRODUCT]);
>             if ((g_list_find_custom (base->inputsources, venprod, cbEventDevices)) == NULL || n == 3 || n == 4 || n == 6)
>                 addInputSource (fd, event_handler, venprod, TRUE);
>             else
>                 close(fd);
>         } else
>             fcnt++;  /* count number of event devices that could not be opened */
>     }
> 
> 
> A real solution would be to configure the event devs we want to use in
> the config file...
> 
> I digged a a bit more and made this patch. It add a sub MODULE INPUT in
> inputmanager.c. Its purpose is to be able to configure the input file
> used by the inputmanager. So a new configuration as been added:
> 
> EventDevices = "/dev/input/event2 /dev/input/event8"
> 
> The default is the old behavior but without checking if some are the
> same vendor_id/product_id.
> 
> ----------------------
> 
> I fixed the bug with the appletouch not reporting it's event. The
> problem is with the synaptics driver doiing a EVIOCGRAB on the event
> device. This prevent the event to be propagated to /dev/input/mice which
> is what one usually wants. If you configure a generic usbmouse and a
> touch pad, you dont want the mouse to move while you scroll with the
> touchpad. As a side effect, no one else can get those events.
> 
> So the solution is to patch the synaptics driver to no more grab the
> event device and configure the usbmouse to use /dev/input/mouse?.
> 
> There is still a little problem, if your mouse is not pluged in when you
> boot, you wont be able to use it without restarting X. A solution is to
> always have the mouse? node. A better solution is to create a new
> mouse/event aggregator like /dev/input/mice and be able to tell each
> mouse/event which aggregator must receive it's events, but this is a
> longer task...
> 
> Kristian


Damn, I forgot the patches... Here it is...

Kristian

Re: pbbuttonsd not loading every dev event

[Kristian B. <kb...@op...>]

On Sat, 2006-03-18 at 12:51 +0100, Matthias Grimm wrote: 
> On Sat, 18 Mar 2006 05:34:27 -0500
> Kristian Benoit <kb...@op...> wrote:
> 
> > I had this problem a few times, pbbuttonsd does not recognize the eject
> > button. Plus the appletouch (absolute coordinate) events does not reset
> > the sleep timeout so I must press a key.
> > 
> > Some devices have the same vendor/product id. For example, the keyboard
> > (/dev/input/event3) has the same vendor/product as the eject key
> > (/dev/input/event4).
> > 
> > The appletouch also have the same ids as another event device too with a
> > lower number. So those where ignored by pbbuttonsd.
> 
> Oh no. :-( You can't rely on nothing nowadays. Why do we define
> standards when nobody follows them anyway? :-/
>  
> > I quikfixed my version, but I still have a strange behavior:
> 
> Could you please tell me how you did this? We need a good workaround
> for this quirk.

As my appletouch is represented by the device /dev/input/event6 and the
other with the same number is lower, I tried openning the device in
reverse order, but then the fn button did not work and the screen was
not dimming anymore. So I hardcoded the device numbers I need:

 for (n = 0; n < EVDEVCOUNT; n++) {
        sprintf(filename, "/dev/input/event%d", n);
        if ((fd = open(filename, O_RDONLY)) >= 0) {
            ioctl(fd, EVIOCGID, id);
            venprod = (gpointer) (id[ID_VENDOR]<<16 | id[ID_PRODUCT]);
            if ((g_list_find_custom (base->inputsources, venprod, cbEventDevices)) == NULL || n == 3 || n == 4 || n == 6)
                addInputSource (fd, event_handler, venprod, TRUE);
            else
                close(fd);
        } else
            fcnt++;  /* count number of event devices that could not be opened */
    }


A real solution would be to configure the event devs we want to use in
the config file...

I digged a a bit more and made this patch. It add a sub MODULE INPUT in
inputmanager.c. Its purpose is to be able to configure the input file
used by the inputmanager. So a new configuration as been added:

EventDevices = "/dev/input/event2 /dev/input/event8"

The default is the old behavior but without checking if some are the
same vendor_id/product_id.

----------------------

I fixed the bug with the appletouch not reporting it's event. The
problem is with the synaptics driver doiing a EVIOCGRAB on the event
device. This prevent the event to be propagated to /dev/input/mice which
is what one usually wants. If you configure a generic usbmouse and a
touch pad, you dont want the mouse to move while you scroll with the
touchpad. As a side effect, no one else can get those events.

So the solution is to patch the synaptics driver to no more grab the
event device and configure the usbmouse to use /dev/input/mouse?.

There is still a little problem, if your mouse is not pluged in when you
boot, you wont be able to use it without restarting X. A solution is to
always have the mouse? node. A better solution is to create a new
mouse/event aggregator like /dev/input/mice and be able to tell each
mouse/event which aggregator must receive it's events, but this is a
longer task...

Kristian

Re: pbbuttonsd not loading every dev event

[Matthias G. <mat...@us...>]

On Sat, 18 Mar 2006 05:34:27 -0500
Kristian Benoit <kb...@op...> wrote:

> I had this problem a few times, pbbuttonsd does not recognize the eject
> button. Plus the appletouch (absolute coordinate) events does not reset
> the sleep timeout so I must press a key.
> 
> Some devices have the same vendor/product id. For example, the keyboard
> (/dev/input/event3) has the same vendor/product as the eject key
> (/dev/input/event4).
> 
> The appletouch also have the same ids as another event device too with a
> lower number. So those where ignored by pbbuttonsd.

Oh no. :-( You can't rely on nothing nowadays. Why do we define
standards when nobody follows them anyway? :-/
 
> I quikfixed my version, but I still have a strange behavior:

Could you please tell me how you did this? We need a good workaround
for this quirk.

 Thanks and Best Regards
   Matthias

Re: increasing brightness seems to be off by one

[Matthias G. <mat...@us...>]

On Mon, 6 Mar 2006 19:24:07 -0600 (GMT-06:00)
mat...@ea... wrote:

> when i dim the screen from on or bright to brigthness level 1 it apears to be at the lowest brightness that is visible.  when i brighten from dark, level 1 seems to be there but extremly faint.  and brightness level 2 from dark is visible as level 1 from bright.  is there a way to change this so that the brightness is the same going bright to dark and dark to bright ?

That's very strange. Could you please retry with disabled framebuffer blanking?
It's the option "UseFBBlank = no".

  Best Regards
    Matthias

increasing brightness seems to be off by one

[<mat...@ea...>]

when i dim the screen from on or bright to brigthness level 1 it apears to be at the lowest brightness that is visible.  when i brighten from dark, level 1 seems to be there but extremly faint.  and brightness level 2 from dark is visible as level 1 from bright.  is there a way to change this so that the brightness is the same going bright to dark and dark to bright ?

matt

strange behavior from pbbuttons 0.7.x

[<mat...@ea...>]

Iupgraded pbbuttonsd on ibook g4 and now it goes to sleep less than minute on battery or power.  Didnt change the config file.  If i downgrade to < 0.7 it works fine again.  What can i do to fix this or debug this?

Thanks

Matt

Re: strange behavior from pbbuttons 0.7.x

[Tom C. <tca...@ch...>]

On Thu, Mar 02, 2006 at 03:06:15AM -0600, Matt Hull wrote:
> i tried all versions of pbbuttonsd on ibook g4 and ibook will goto sleep
> less than minute with no activity battery or power.  didnt change the
> config file.  if i downgrade to < 0.7 it works fine again.  waht can i do
> to fix this ?

I experienced the same problems.  The trouble was the package manager
_not_ upgrading the configuration files.   Purge (Backup?) the old
configuration files and try again.

~ Tom

strange behavior from pbbuttons 0.7.x

[Matt H. <mh...@ui...>]

i tried all versions of pbbuttonsd on ibook g4 and ibook will goto sleep
less than minute with no activity battery or power.  didnt change the
config file.  if i downgrade to < 0.7 it works fine again.  waht can i do
to fix this ?

thanks

matt

Re: display autoadjust and blank screen

[Yves-Alexis P. <co...@co...>]

On Thu, 2006-02-23 at 00:17 +0100, Yves-Alexis Perez wrote:
> On Wed, 2006-02-22 at 21:39 +0100, Matthias Grimm wrote:
> > Back to your question. It is not a bug. The responsible code is in
> > module_display, function display_keyboard(), first part of the
> > switch(changed){} statement, line 315-316.
> > 
> > When automatic mode is active, the brightness keys generate an offset
> > that will be added to the value from the automatic brightness
> > controller. This offset will be clipped if the overall brightness
> > level is out of range. The limits are 1 or BRIGHTNESS_MAX.
> 
> ok
> 
> > 
> > You might change the lower limit to 0 to be able to switch off your
> > display completely also in automatic mode. But keep in mind that this
> > value still depends on the ambient light level. That means if the
> > environment goes darker, the backlight might be switched on again.
> 

Ok, so, attached is a (dirty) patch which enable switching off the LCD
while in automatic adjust mode. In order not to depends on the ambient
light leve i've set the status to OFF, which works but may not be really
clean.


-- 
Yves-Alexis Perez

Re: display autoadjust and blank screen

[Yves-Alexis P. <co...@co...>]

On Wed, 2006-02-22 at 21:39 +0100, Matthias Grimm wrote:
> On Wed, 22 Feb 2006 09:38:43 +0100
> Yves-Alexis Perez <co...@co...> wrote:
>=20
> > Hi there,
> >=20
> > i'd like to know if it's a bug (or a feature) that I can't blank the
> > screen with pbbuttonsd when using Display Autoadjust=3Dyes.
> >=20
> > If it's off, I can set the brightness from 15 to 0. If it's on, I can't
> > go below 1. I've reported this as a bug in debian bts [1] but no news.
>=20
> I'm sorry to hear that but debian bts is for debian only. I don't read
> the debian bugtracker on a regular basis.

Well, the maitainer could be overbooked :)
>=20
> Back to your question. It is not a bug. The responsible code is in
> module_display, function display_keyboard(), first part of the
> switch(changed){} statement, line 315-316.
>=20
> When automatic mode is active, the brightness keys generate an offset
> that will be added to the value from the automatic brightness
> controller. This offset will be clipped if the overall brightness
> level is out of range. The limits are 1 or BRIGHTNESS_MAX.

ok

>=20
> You might change the lower limit to 0 to be able to switch off your
> display completely also in automatic mode. But keep in mind that this
> value still depends on the ambient light level. That means if the
> environment goes darker, the backlight might be switched on again.

hmh, ok, but that won't do the trick :/

>=20
> I haven't got much feedback on this feature if the behaviour is ok
> or not. Nobody complained so far but that means nearly nothing. If you
> have a certain vision on how the behaviour should be, please tell me.
> Possibly it is a general benefit for the function.

I don't know the real behavior in OSX, but when using automatic adjust
you play on offset as well I guess. The difference is, when you switch
off the screen, setting brightness=3D0, it keeps this value even if light
goes darker.

I guess brightness=3D0 could be "forced", whatever the autoadjust switch
state is.
>=20
>   Best Regards
>     Matthias

Thanks for the reply :)

Regards,
--=20
Yves-Alexis Perez

Re: display autoadjust and blank screen

[Matthias G. <mat...@us...>]

On Wed, 22 Feb 2006 09:38:43 +0100
Yves-Alexis Perez <co...@co...> wrote:

> Hi there,
> 
> i'd like to know if it's a bug (or a feature) that I can't blank the
> screen with pbbuttonsd when using Display Autoadjust=yes.
> 
> If it's off, I can set the brightness from 15 to 0. If it's on, I can't
> go below 1. I've reported this as a bug in debian bts [1] but no news.

I'm sorry to hear that but debian bts is for debian only. I don't read
the debian bugtracker on a regular basis.

Back to your question. It is not a bug. The responsible code is in
module_display, function display_keyboard(), first part of the
switch(changed){} statement, line 315-316.

When automatic mode is active, the brightness keys generate an offset
that will be added to the value from the automatic brightness
controller. This offset will be clipped if the overall brightness
level is out of range. The limits are 1 or BRIGHTNESS_MAX.

You might change the lower limit to 0 to be able to switch off your
display completely also in automatic mode. But keep in mind that this
value still depends on the ambient light level. That means if the
environment goes darker, the backlight might be switched on again.

I haven't got much feedback on this feature if the behaviour is ok
or not. Nobody complained so far but that means nearly nothing. If you
have a certain vision on how the behaviour should be, please tell me.
Possibly it is a general benefit for the function.

  Best Regards
    Matthias

display autoadjust and blank screen

[Yves-Alexis P. <co...@co...>]

Hi there,

i'd like to know if it's a bug (or a feature) that I can't blank the
screen with pbbuttonsd when using Display Autoadjust=3Dyes.

If it's off, I can set the brightness from 15 to 0. If it's on, I can't
go below 1. I've reported this as a bug in debian bts [1] but no news.

[0]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D345314
--=20
Yves-Alexis Perez

Brightness problems

[Olivier M. <sh...@ss...>]

Hi,

I have several small brightness problems with my ~June 2005 12" iBook (cpuinfo
below)

The brightness adjust by itself works as intended, however,
 - when switching between (framebuffer) console and X, the brightness is always
set to the maximum (or minimum) value, and I have to press the britghtness keys
once to get it back to the previous level;
 - when suspending-to-ram the computer, then waking it up, its brightness is
once again set to max or min* and I have to press the brightness keys as above
to restore de last setting;
 - when closing the LID, which in my conf is blanking the screen, then
reoppening it, the screen stays black (no image) and, repeating once again the
above key magics, the screen shows up again (this happens with UseFBBlank=yes,
deactivating this feature solve _this_ problem. BTW what's the interest of using
this feature ?).

* max or min does not mean that it is randomly set to one or the other
brightness level. it seems to be dependent on the value of LCD_Brightness when
PBButtonsd has first been started after bootup, or maybe has it been just
changed from min to max with 0.7.4

I think my report is a little unclear, so just ask if information is missing.

cpuinfo:
processor       : 0
cpu             : 7447A, altivec supported
clock           : 599MHz
revision        : 0.2 (pvr 8003 0102)
bogomips        : 598.01
machine         : PowerBook6,5
motherboard     : PowerBook6,5 MacRISC3 Power Macintosh 
detected as     : 287 (iBook G4)
pmac flags      : 0000001b
L2 cache        : 512K unified
memory          : 512MB
pmac-generation : NewWorld

pbbuttonsd version:
pbbuttonsd, version 0.7.4, (c) 2002-2005 Matthias Grimm

The laptop is running Gentoo Linux

-- 
Olivier Mehani <sh...@ss...>

PBButtonsd 0.7.4 released - major feature enhancement

[Matthias G. <mat...@us...>]

Hi,
it's done again :-) A new pbbuttonsd release. Thanks to all that make
it possible. Special thanks to Ren=E9 Nussbaumer and Michael Hanselmann
who gave me the code and knowledge to add support for PMU05 PowerBooks.

This release got support for the ambient light sensor and the keyboard
illumination of latest 15" and 17" Powerbooks. Furthermore the keyboard
mode of USB keyboards can be set the same way as for ADB keyboards, as
long as you use kernel 2.6.16 or later.

As a first big step towards major future enhancements, the main loop
and the input device management of pbbuttonsd was moved to glib. This
change is the basis now for moving pbbuttonsd's IPC system towards
dbus-1 and to implement a dynamically loadable module system for user
space device drivers (USDD).=20

The source is available as usual at http://pbbuttons.berlios.de/
 =20
 Best Regards
   Matthias

Re: Powerbook5,8: FN key mode

[Michael H. <lis...@ha...>]

Hello Matthias

On Sat, Jan 21, 2006 at 11:52:12PM +0100, Matthias Grimm wrote:
> It would be nice if you could test this feature and tell me the results.

It didn't work from the start, but the patch below fixes it. After
applying the patch, it works.

Btw.: The illumination patch I wrote was based on work by Ren=C3=A9
Nussbaumer, who found out that the LMU is not on the I=C2=B2C bus anymore on
the PowerBook5,8. Maybe you want to put that into the ChangeLog, because
not all of the credit should go to me.

Greets,
Michael

diff -urp pbbuttonsd-0.7.3-6g.orig/src/module_pmac.c pbbuttonsd-0.7.3-6g/sr=
c/module_pmac.c
--- pbbuttonsd-0.7.3-6g.orig/src/module_pmac.c	2006-01-22 17:48:40.00000000=
0 +0100
+++ pbbuttonsd-0.7.3-6g/src/module_pmac.c	2006-01-22 20:31:02.000000000 +01=
00
@@ -120,7 +120,7 @@ pmac_init ()
 				TRACKPAD_NOTAP_NAME, TRACKPAD_TAP_NAME, TRACKPAD_DRAG_NAME, TRACKPAD_L=
OCK_NAME, NULL);
 		registerCfgOptionList (sid, "KBDMode", TAG_KBDMODE, 0,
 				N_("'"KEYBOARD_FNDISABLED_NAME"', '"KEYBOARD_FNBACK_NAME"' or '"KEYBOA=
RD_FNTOP_NAME"'"),
-				KEYBOARD_FNDISABLED, KEYBOARD_FNBACK_NAME, KEYBOARD_FNTOP_NAME, NULL);
+				KEYBOARD_FNDISABLED_NAME, KEYBOARD_FNBACK_NAME, KEYBOARD_FNTOP_NAME, N=
ULL);
 		registerCfgOptionList (sid, "Batlog", TAG_BATLOG, 0,
 				N_("'"BATLOG_NONE_NAME"', '"BATLOG_CYCLE_NAME"' or '"BATLOG_LOG_NAME"'=
"),
 				BATLOG_NONE_NAME, BATLOG_CYCLE_NAME, BATLOG_LOG_NAME, NULL);
diff -urp pbbuttonsd-0.7.3-6g.orig/src/module_pmac.h pbbuttonsd-0.7.3-6g/sr=
c/module_pmac.h
--- pbbuttonsd-0.7.3-6g.orig/src/module_pmac.h	2006-01-22 17:48:40.00000000=
0 +0100
+++ pbbuttonsd-0.7.3-6g/src/module_pmac.h	2006-01-22 20:30:58.000000000 +01=
00
@@ -28,7 +28,7 @@
 #define DEFAULT_ADB		"/dev/adb"
 #define DEFAULT_BATLOG		"/var/lib/pbbuttons/%03d_battery.log"
 #define DEFAULT_BATCYCLE	"/var/lib/pbbuttons/battery.cycle"
-#define PATH_FNMODE		"/sys/modules/usbhid/parameters/pb_fnmode"
+#define PATH_FNMODE		"/sys/module/usbhid/parameters/pb_fnmode"
=20
 /* definitions for input device config */
 #define TRACKPAD_NOTAP_NAME	"notap"

--=20
Gentoo Linux developer, http://hansmi.ch/, http://forkbomb.ch/
Unix weanies are as bad at this as anyone.
             -- Larry Wall in <199...@wa...>

Re: Powerbook5,8: FN key mode

[Matthias G. <mat...@us...>]

On Fri, 20 Jan 2006 23:29:09 +0100
Michael Hanselmann <lis...@ha...> wrote:

Hi Michael,
> On Fri, Jan 20, 2006 at 07:30:12PM +0100, Matthias Grimm wrote:
> > Where do you set pb_mode=1? Is it a module parameter?
> 
> Yes. You can change it during runtime trough
> /sys/modules/usbhid/parameters/pb_fnmode (that's what pbbuttonsd might
> have to do).

I added this function to pbbuttonsd beta. You should be able to set
the fnmode as usual with the config option KBDMode = fkeysfirst /
fkeyslast.

Because the option pb_fnmode could be set to "disabled", I added this
mode as well: "KBDMode = disabled". On machines with ADB keyboard the
option "disabled" is not possible and will be forced to "fkeyslast".

The beta version is available at:
    ftp://ftp.berlios.de/pub/pbbuttons/pbbuttonsd-0.7.3-6g.tar.gz

It would be nice if you could test this feature and tell me the results.

 Best Regards
   Matthias

PS: The offer to test is not limited to Michael ;-)

PBButtonsd Public Beta: Support for PMU based ambient sensor

[Matthias G. <mat...@us...>]

Hi,

I add support for the new ambient light sensor connected to the PMU to
pbbuttonsd (Thanks to Michael Hanselmann for his help). This code
change also affected the old sensor connected through I2C. Please test
this functionallity and report any problems or wishes regarding the
function behaviour.

You could download the beta here:
   ftp://ftp.berlios.de/pub/pbbuttons/pbbuttonsd-0.7.3-5g.tar.gz

Your help would really be appreciated. I can't test this code myself
because I don't have access to a PowerBook with an ambient sensor :-(.

 Best Regards
   Matthias

Re: Problem with Aluminium Powerbook

[Nicolas M. <nic...@gm...>]

Thanks for your responsiveness and the information you provided.
Actually I'm running a lot more often linux than MacOS so do you (or
someone else on this list) know how to disable this feature under
linux?

Nicolas

Re: Problem with Aluminium Powerbook

[Wolfram Q. <wo...@mi...>]

Hi Nicolas!

On Wed, Jan 11, 2006 at 04:51:15PM +0100, Nicolas Mainil wrote:
> Hi,
>=20
> I got a serious issue with my aluminium Powerbook: when it is on
> battery, the lid being closed, it shuts down after 4 minutes. It seems
> to be a "hard" shutdown (as when i push the power button during five
> seconds) cause I have to fsck my disk on the next startup. I'm not
> sure it's at all related with pbuttonsd as the problem is
> reproductible with pbbuttonsd started AND stopped but I ask it here
> cause I've no idea of what's causing this issue.

It's a feature not a bug. The hardware shuts your powerbook down due to
reasons I don't know, but al PBs I know do this (I think it is a
fallback in the software to prevent overheating). It is possible to
disable this shutdown via software however, since running MacOS you can
close the lid and work safely if an external screen and USB keyboard are
connected.

HTH,

Wolfi
>=20
> Nicolas
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick
> _______________________________________________
> pbbuttons-users mailing list
> pbb...@li...
> https://lists.sourceforge.net/lists/listinfo/pbbuttons-users

Problem with Aluminium Powerbook

[Nicolas M. <nic...@gm...>]

Hi,

I got a serious issue with my aluminium Powerbook: when it is on
battery, the lid being closed, it shuts down after 4 minutes. It seems
to be a "hard" shutdown (as when i push the power button during five
seconds) cause I have to fsck my disk on the next startup. I'm not
sure it's at all related with pbuttonsd as the problem is
reproductible with pbbuttonsd started AND stopped but I ask it here
cause I've no idea of what's causing this issue.

Nicolas

GKrellm-PMU 2.5 released

[Matthias G. <mat...@us...>]

Hi,

GKrellm-PMU 2.5 has just been released.

This release got support for the new IBaM algorithm of PBButtons and is
able to show accurate time estimations now. The feature is configurable
in the modules config dialog.

The second highlight of this release is the now available Debian
package for Sarge. It is not part of the main distribution yet, but in
the meantime you could download it from http://pbbuttons.berlios.de.

Last but not least the dusty source tree got cleaned up.

 Best Regards
   Matthias

Re: pbbuttonsd patches

[Matthias G. <mat...@us...>]

On Thu, 05 Jan 2006 15:48:36 +0100
Frank Arnold <fr...@sc...> wrote:

> Matthias,
> 
> I've been looking through existing packages of pbbuttonsd and came
> across Mandriva RPMs. They carry some patches with script fixes. I don't
> know if they were brought to your attention because they are rather old.

I didn't know this patches. Thanks for sending them.

- The first is distribution dependent I think.
- The second fixes a bug in the pmcs scripts, which is still present in
  the current release :-(. 
- The third patch is obsolete because the laptop-mode script is no longer
  part of pbbuttonsd. 

  Best Regards
    Matthias