pbbuttons-users — Everything regarding pbbuttons' usage and develpment

Re: problem coming back from blanking the screen

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

On Mon, 9 Apr 2007 13:52:16 +0200
Joost Kremers <joo...@fa...> wrote:

Hi,
> i'm having a problem with screen-blanking. if i set the option
> onAC_TimerAction and/or onBattery_TimerAction to 'blankscreen', pbbuttons
> nicely blanks the screen after the interval i've set. however, it does not
> respond to key presses or mouse movements to unblank the screen. the only
> way to unblank the screen is to press Fn-F1, Fn-F2 (i usually have to press
> them both, in any order).

Most problems of this kind occur due to system configuration problems.
- Have you the module evdev loaded? (lsmod | grep evdev).
- Do you use udev? If not please check that you have enough event device
  nodes in /dev/input.

> since i'm not running the latest version of pbbuttonsd (0.7.8), i
> downloaded 0.8.0 and tried to compile that. it bombed out with the
> following error, however:

There is no reason to update pbbuttonsd if the version 0.7.8 does all you
want it to do.

The compilation error you got was not caused by pbbuttonsd. Something is
missing on your system. Please check that you have the correct kernel
headers installed. Most distributors have a special kernel header package.

> my system:
> iBook G3 800MHz
> Slackintosh 11.0
> Kernel: Linux teuctli 2.6.17.13 #1 PREEMPT Tue Sep 12 18:00:15 CEST 2006 ppc GNU/Linux
> 	(this is the stock Slackintosh kernel)

There's no reason why pbbuttonsd should not run on your system. I think most
problems will be gone after you checked the above configuration issues.

> ps: when you do a google search for pbbuttonsd, the first link points to
> <http://pbbuttons.sourceforge.net/projects/pbbuttonsd/>, which appears to
> be the old homepage. the download section has version 0.7.2 as the
> latest. perhaps it would be a good idea to replace this page with a redirect?

Interesting. Sourceforge _has_ a redirect to pbbuttons.berlios.de. You called
a subpage directly and I didn't redirect only requests on the main page. Anyway,
I should remove the old pages from the server. Thanks for the info.

 Best Regards
  Matthias

problem coming back from blanking the screen

[Joost K. <joo...@fa...>]

hi,

i'm having a problem with screen-blanking. if i set the option
onAC_TimerAction and/or onBattery_TimerAction to 'blankscreen', pbbuttons
nicely blanks the screen after the interval i've set. however, it does not
respond to key presses or mouse movements to unblank the screen. the only
way to unblank the screen is to press Fn-F1, Fn-F2 (i usually have to press
them both, in any order).

since i'm not running the latest version of pbbuttonsd (0.7.8), i
downloaded 0.8.0 and tried to compile that. it bombed out with the
following error, however:

===============

Compiling driver_backlight_pmu.c:                                     [ERROR]  
  gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../intl -I../libpbbipc -I/usr/include/glib
  -2.0 -I/usr/lib/glib-2.0/include -g -O2 -c driver_backlight_pmu.c
  driver_backlight_pmu.c: In function `pmubl_get_brightness':
  driver_backlight_pmu.c:90: error: `__u32' undeclared (first use in this funct
  ion)
  driver_backlight_pmu.c:90: error: (Each undeclared identifier is reported onl
  y once
  driver_backlight_pmu.c:90: error: for each function it appears in.)
  driver_backlight_pmu.c:90: error: syntax error before ')' token
  driver_backlight_pmu.c: In function `pmubl_set_brightness':
  driver_backlight_pmu.c:131: error: `__u32' undeclared (first use in this func
  tion)
  driver_backlight_pmu.c: In function `driver_backlight_pmu_init':
  driver_backlight_pmu.c:176: error: `__u32' undeclared (first use in this func
  tion)
  driver_backlight_pmu.c:176: error: syntax error before ')' token
make[2]: *** [driver_backlight_pmu.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

===============

my system:

iBook G3 800MHz
Slackintosh 11.0
Kernel: Linux teuctli 2.6.17.13 #1 PREEMPT Tue Sep 12 18:00:15 CEST 2006 ppc GNU/Linux
	(this is the stock Slackintosh kernel)
pbbuttonsd: 0.7.8

any other info i should provide?

tia

joost


ps: when you do a google search for pbbuttonsd, the first link points to
<http://pbbuttons.sourceforge.net/projects/pbbuttonsd/>, which appears to
be the old homepage. the download section has version 0.7.2 as the
latest. perhaps it would be a good idea to replace this page with a redirect?

-- 
Joost Kremers, PhD
University of Cologne
Institute for German Language and Literature
Albertus Magnus Platz
50923 Cologne, Germany
Tel. +49 221 / 4703807

Re: manual lcd off reset by return from idle

[timotheus <tim...@us...>]

Hi Matthias,

I tried your recommended source change with pbbuttonsd
0.7.9. Unfortunately, the new pbbuttonsd with patched source did not
demonstrate any change in behavior.

To reproduce:
   - in xorg.conf, put displays in clone mode
   - in Section "Device", use the option:
         Option          "PanelOff"              "1"

Run X11. Let the machine idle 10 minutes or so. Move the mouse. The LCD
panel turns on at minimum dimness instead of remaining off. Very bad for
the life of the LCD.

Currently, I just use a script that kills pbbuttonsd whenever I run X11
in clone mode; but this is obviously an undesirable hack.

Linux kernel version:   2.6.19

Some questions:
   - could there be another location in the pbbuttonsd source that needs
     to be modified?
   - is it possible that some kernel-level driver for the LCD affects
     this issue? (I doubt that it would affect more than the dim
     buttons)

Regards,
-timotheus

> Date: Sun, 11 Feb 2007 12:04:46 +0100
> From: Matthias Grimm <mat...@us...>

> > - when panel birghtness is > 0, save before dimming/suspending lcd,
> >   restore after return from idle (implemented)
> > - when panel brightness is == 0, save before dimming/suspending lcd,
> >   restore lcd to brightness of 0 after return from idle (not possible)
> >
> > I do think that this is a bug. The LCD should not turn on due to user
> > interaction if the LCD was turned off by the user prior to idling the
> > machine. If you disagree, please consider providing a pbbuttonsd option
> > for this purpose.
> 
> This behaviour is definitely not a bug; it's a design decision. I
> thought that it would be irritating that the display once switched to
> darkness by hand will stay dark forever. But this is my personal
> opinion and you are the first one who responded to this feature.
> 

> In the meantime you could help yourself by editing the source of pbbuttonsd.
> In module_display.c, function display_change_brightness() you will find a
> switch - case statement. In the case section OP_DIM_RECOVER comment the
> following lines out:
>    if (base->lcdlight.target == LCD_BRIGHTNESS_OFF)
>        base->lcdlight.target = LCD_BRIGHTNESS_MIN;
> 
> After this change pbbuttonsd should do what you want.

New version of PowerPrefs

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

Hi,
The new release of pbbuttonsd made it necessary to update PowerPrefs a
bit.

This release got support for the new automatic ambient light controller
model in pbbuttonsd and any other new feature of pbbuttonsd 0.8.0. To
make this instantly visible the version numbers of both programs have
been aligned.

A lot of ancient restrictions were eliminated and all GUI elements were
adapted to pbbuttonsds modern and flexible driver system. 

As usual it could be downloaded at
http://prdownloads.sourceforge.net/pbbuttons/powerprefs-0.8.0.tar.gz?download

 Have fun
  Matthias

Pbbuttonsd 0.8.0 is out

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

Hi,

After four month of development I finished version 0.8.0.

This release adds support for Apples MacBooks an MacBook Pros to
pbbuttonsd. This includes support for LCD and keyboard backlight
control, ambient light sensor with automatic brightness adjustment and
basic ACPI support.

Furthermore the automatic brightness controller was replaced by a new
one. The new model results in a more precise brightness adjustment of
LCD backlight and keyboard illumination and is easier and more flexible
to configure.

This release uses a new configuration file which is called
pbbuttonsd.cnf and follows a standard format from freedesktop.org. The
old file is no longer read and must be moved manually to the new format
(which is not so difficult :-) ).

The developer documentation uses doxygen now. call configure with
--with-doxygen-docs and make will generate it.

A whole bunch of bug fixes complete this release. 

The package is ready for download at
http://prdownloads.sourceforge.net/pbbuttons/pbbuttonsd-0.8.0.tar.gz?download

 Have fun
   Matthias

manual lcd off reset by return from idle

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

Hi Tim,

I saw you bug report on sourceforge.net, unfortunately after I
published the new release :-/. Nevertheless I would like to comment it.

> - when panel birghtness is > 0, save before dimming/suspending lcd,
>   restore after return from idle (implemented)
> - when panel brightness is == 0, save before dimming/suspending lcd,
>   restore lcd to brightness of 0 after return from idle (not possible)
>
> I do think that this is a bug. The LCD should not turn on due to user
> interaction if the LCD was turned off by the user prior to idling the
> machine. If you disagree, please consider providing a pbbuttonsd option
> for this purpose.

This behaviour is definitely not a bug; it's a design decision. I
thought that it would be irritating that the display once switched to
darkness by hand will stay dark forever. But this is my personal
opinion and you are the first one who responded to this feature.

I would like to open a discussion if we should revise the design decision
on pbb...@li....

In the meantime you could help yourself by editing the source of pbbuttonsd.
In module_display.c, function display_change_brightness() you will find a
switch - case statement. In the case section OP_DIM_RECOVER comment the
following lines out:
   if (base->lcdlight.target == LCD_BRIGHTNESS_OFF)
       base->lcdlight.target = LCD_BRIGHTNESS_MIN;

After this change pbbuttonsd should do what you want.

 Best regards
   Matthias

Release Candidate #1 for pbbuttonsd 0.8.0 is out

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

Hi fellows,

The first release candidate for the upcomming pbbuttonsd version 0.8.0
is out.

It includes support for the new Intel-base Apple MacBooks and MacBook
Pros. LCD and keyboard backlight control, ambient light sensor with
automaticThis is the release candidate one for the upcomming pbbuttonsd
version 0.8.0. It includes support for the new Intel-base Apple
MacBooks and MacBook Pros. LCD and keyboard backlight control, ambient
light sensor with automatic brightness adjustment and basic ACPI
support should work.

Furthermore this release got a new configuration file format, that
follows a standard from freedesktop.org. It is very similar to the old
one but the file handling is completely done by the glib now. The
configuration file has been renamed to pbbuttonsd.cnf to keep the old
one during installation.

Some configuration options were removed and a few others have been
renamed. If you need special configuration, please have a look at the
default configuration file in the package.

In this context I would like to reduce the amount of configuration
options a bit. Candidates for this are the key definitions for
brightness and volume control because the keys are well defined and the
kernel provide symbolic names for the keycodes. Has anybody redefined
the brightness or volume control keys on his machine?

A few small bugfixes complete this release.

Please test this release and tell me any problems you may find.
Especially feedback regarding the new MacBook support is very welcome.

The release candidate could be downloaded from:
   http://pbbuttons.berlios.de/projects/pbbuttonsd/download.html

or directly from the ftp server:
  ftp://ftp.berlios.de/pub/pbbuttons/pbbuttonsd-0.8.0-rc1.tar.gz

 Best regards
   Matthias

Pbbuttons wiki removed from the net

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

Hi,

I just removed the pbbuttonsd wiki from the web server.
The reasons for this are easy:
 1. Low traffic (0%). It seems that there is no need for a wiki to store
    PPC hardware and software related information.
 2. Spammers have discovered and polluted the wiki. The barrier was
    high but nevertheless they did it. :-(

 Best Regards
   Matthias

Upcomming PBButtonsd 0.8 with (Intel) MacBook support

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

Hi,

The next release of pbbuttonsd will include support for the new
Intel-base Apple MacBooks. The support includes LCD and keyboard
backlight control, ambient light sensor with automatic brightness
adjustment and basic ACPI support.

Beta testers could ask me for the source code or load it directly from
the CVS repository on SourceForge.net. Any help would be appreciated to
find the last quirks in the program.

 Best Regards
   Matthias

PBButtons 0.7.9 is out

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

Hi,

Pbbuttonsd 0.7.9 has been released. This release got support for the
new SysFS backlight interface introduced with kernel 2.6.18. In this
context parts of the client API had to be redesigned. Brightness values
are transmitted as percentage now rather than in device dependent units.
The fading mechanism was redesigned to become device independent too.
See the Changelog and manual pages for full details.

Attention: Client programmers should take care about the changes and
           adapt their programms as soon as possible.

Please have also a look at the chapter "Kernel Configuration" in the man
page for the correct settings.

New versions of GtkPBButtons (0.6.9) and PowerPrefs (0.5.1) are
available too. Both programms were adapted to the client API changes
mentioned above and some minor bugs were fixed.

 Best Regards
   Matthias

Re: extent brightness adjust in 2.6.18?

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

On Wed, 27 Sep 2006 01:15:27 -0400
timotheus <pbb...@ts...> wrote:

> The 'actual_brightness' file is read-only and seems to always have the
> same value as 'brightness'.
> 
> The 'brightness' file is writable and immediately adjusts the
> LCD. Appropriate values are 0 (full dark), 1 (min. brightness), to the
> value of 'max_brightness', which is 127 on this laptop.
> 
> 'max_brightness' is the maximum value allowed to be written to
> 'brightness', otherwise an error is displayed on the terminal:

I found the same. Pbbuttons will use max_brightness and brightness.

> The sysfs brightness value *does* smoothly adjust the LCD by each
> increment from 0 to 127, as demonstrated with the command:

The release candidate of pbbuttonsd (in CVS) uses all supported
brightness levels so we don't need a transformation table or something
like that.

> One interesting note.  Pbbuttonsd 0.7.x has a bug that sometimes
> occurs by leaving the machine idle for hours and then returning to
> using it.  The display remains at maximum brightness and
> does not respond to F1/F2 adjustments until using these keys to adjust
> to full-dark, and then increasing brightness again.
> 
> When this bug is active, the display brightness value is '127'.  But,
> the maximum value pbbuttonsd sets by using F1/F2 is '120'.  I assume
> that this bug will disappear when using the sysfs interface anyways,
> but thought it interesting.

Never heard about this before.
- Was the display dimmed or completely dark before you re-using it?
- What about sleep mode? Did the machine idle all the time?
- Was the option UseFBBblank activated in your configuration?

Try to set UseFBBlank = "no". New PowerBooks were reported to have
problems with this option and I think recent kernels don't need it any
longer anyway. 

Please tell me if that behaviour is fixed with the release candidate.

  Best Regards
    Matthias

pbbuttons with sysfs backlight support

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

Hi,

I did it or better I *believe* I did it :-)

The code of the upcoming release is in CVS. It has got a class
backlight with several low level drivers (two at the moment: sysfs and
pmu). The driver which suits best will be auto-detected.

Because the SysFS interface supports much more brightness steps I had
to redefine parts of the client API. Especially the brightness messages
and the fading mechanism. You need to update following options in your
configuration file: LCD_Brightness, LCD_Fadingspeed, KBD_Brightness and
KBD_Fadingspeed. Please see the man page pbbuttonsd.conf.5 for details.

The brightness message sent to clients uses percentage now and the
fading speed will be given as device independent time value (see man
page for details). This assures that the behaviour of pbbuttonsd is
always the same, whatever backlight driver is used. Unfortunately this
will confuse most of the clients including gtkpbbuttons. A patched
version of gtkpbbuttons is in the repository too.

Please try the CVS version and tell me any issues you find. Also
positive feedback is welcome.

If you are unfamiliar with CVS but nevertheless want to test the
release candidate, please see on
         http://sourceforge.net/cvs/?group_id=47862

You will find a detailed information how to get the source.

After the source is on your hard disk, run the autogen.sh script in the
main directory. After that 'make' and 'make install' should do the job.

  Best Regards
    Matthias

PS: If anybody has problems with CVS please tell me. I will send you a
    preliminary package for test.

Re: extent brightness adjust in 2.6.18?

[timotheus <pbb...@ts...>]

Resending due to local mail issues. Sorry if this becomes a duplicate post.

>> 
>> 1. Do you see more than one entry in /sys/class/backlight?
>

For me, I have a PowerBook5,2 running kernel 2.6.18 (with unrelated
patches).

>corsac@hidalgo: ls -R /sys/class/backlight                           [~]
>/sys/class/backlight:
>total 0
>drwxr-xr-x 2 root root 0 1904-01-01 00:10 radeonbl0
>
>/sys/class/backlight/radeonbl0:
>total 0
>-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 actual_brightness
>-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 brightness
>-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 max_brightness
>-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 power
>lrwxrwxrwx 1 root root    0 2006-09-24 12:20 subsystem
>-> ../../../class/backlight

Same for me.

>
>> 2. If so, what are they for? 
>> 3. Has the keyboard backlight an entry in /sys/class/backlight too?
>
>No it seems not (but maybe I'm lacking some config option)
>
>>    I studied the kernel source and found no clue for that but I might
>>    have missed something.

My subjective impression from the code and recent kernel trends:

The keyboard is unrelated.  This is a kernel reworking to have a
backlight class for all LCD backlights.  Radeon is one of the first,
but not to be the only, driver with the same backlight sysfs
interface. This allows independence of the PMU driver and merging of
PC and Mac code. This information is somewhat mentioned in the driver
help (make menuconfig , help items).

I have no part in developing this driver, but from experimentation
I have determined the following.

The 'actual_brightness' file is read-only and seems to always have the
same value as 'brightness'.

The 'brightness' file is writable and immediately adjusts the
LCD. Appropriate values are 0 (full dark), 1 (min. brightness), to the
value of 'max_brightness', which is 127 on this laptop.

'max_brightness' is the maximum value allowed to be written to
'brightness', otherwise an error is displayed on the terminal:

    # echo 128 > brightness
    bash: echo: write error: Invalid argument

'power' has the value of 0, seemingly always.



Relation to current pbbuttonsd release 0.7.8:

pbb value  ,	   sysfs-brightness value

1	   ,	   8
2	   ,	   16
3	   ,	   24
4	   ,	   32
5	   ,	   40
6	   ,	   48
7	   ,	   56
8	   ,	   64
9	   ,	   72
10	   ,	   80
11	   ,	   88
12	   ,	   96
13	   ,	   104
14	   ,	   112
15	   ,	   120



The sysfs brightness value *does* smoothly adjust the LCD by each
increment from 0 to 127, as demonstrated with the command:

# (for n in `seq 1 127`; do echo $n > brightness; sleep .05s; done)


One interesting note.  Pbbuttonsd 0.7.x has a bug that sometimes
occurs by leaving the machine idle for hours and then returning to
using it.  The display remains at maximum brightness and
does not respond to F1/F2 adjustments until using these keys to adjust
to full-dark, and then increasing brightness again.

When this bug is active, the display brightness value is '127'.  But,
the maximum value pbbuttonsd sets by using F1/F2 is '120'.  I assume
that this bug will disappear when using the sysfs interface anyways,
but thought it interesting.

Best regards,
timotheus

Re: extent brightness adjust in 2.6.18?

[timotheus <pbb...@ts...>]

>> 
>> 1. Do you see more than one entry in /sys/class/backlight?
>

For me, I have a PowerBook5,2 running kernel 2.6.18 (with unrelated
patches).

>corsac@hidalgo: ls -R /sys/class/backlight                           [~]
>/sys/class/backlight:
>total 0
>drwxr-xr-x 2 root root 0 1904-01-01 00:10 radeonbl0
>
>/sys/class/backlight/radeonbl0:
>total 0
>-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 actual_brightness
>-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 brightness
>-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 max_brightness
>-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 power
>lrwxrwxrwx 1 root root    0 2006-09-24 12:20 subsystem
>-> ../../../class/backlight

Same for me.

>
>> 2. If so, what are they for? 
>> 3. Has the keyboard backlight an entry in /sys/class/backlight too?
>
>No it seems not (but maybe I'm lacking some config option)
>
>>    I studied the kernel source and found no clue for that but I might
>>    have missed something.

My subjective impression from the code and recent kernel trends:

The keyboard is unrelated.  This is a kernel reworking to have a
backlight class for all LCD backlights.  Radeon is one of the first,
but not to be the only, driver with the same backlight sysfs
interface. This allows independence of the PMU driver and merging of
PC and Mac code. This information is somewhat mentioned in the driver
help (make menuconfig , help items).

I have no part in developing this driver, but from experimentation
I have determined the following.

The 'actual_brightness' file is read-only and seems to always have the
same value as 'brightness'.

The 'brightness' file is writable and immediately adjusts the
LCD. Appropriate values are 0 (full dark), 1 (min. brightness), to the
value of 'max_brightness', which is 127 on this laptop.

'max_brightness' is the maximum value allowed to be written to
'brightness', otherwise an error is displayed on the terminal:

    # echo 128 > brightness
    bash: echo: write error: Invalid argument

'power' has the value of 0, seemingly always.



Relation to current pbbuttonsd release 0.7.8:

pbb value  ,	   sysfs-brightness value

1	   ,	   8
2	   ,	   16
3	   ,	   24
4	   ,	   32
5	   ,	   40
6	   ,	   48
7	   ,	   56
8	   ,	   64
9	   ,	   72
10	   ,	   80
11	   ,	   88
12	   ,	   96
13	   ,	   104
14	   ,	   112
15	   ,	   120



The sysfs brightness value *does* smoothly adjust the LCD by each
increment from 0 to 127, as demonstrated with the command:

# (for n in `seq 1 127`; do echo $n > brightness; sleep .05s; done)


One interesting note.  Pbbuttonsd 0.7.x has a bug that sometimes
occurs by leaving the machine idle for hours and then returning to
using it.  The display remains at maximum brightness and
does not respond to F1/F2 adjustments until using these keys to adjust
to full-dark, and then increasing brightness again.

When this bug is active, the display brightness value is '127'.  But,
the maximum value pbbuttonsd sets by using F1/F2 is '120'.  I assume
that this bug will disappear when using the sysfs interface anyways,
but thought it interesting.

Best regards,
timotheus

Re: extent brightness adjust in 2.6.18?

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

On Sat, 2006-09-23 at 12:10 -0400, timotheus wrote:
> This is fixed with kernel option:
>     CONFIG_PMAC_BACKLIGHT_LEGACY=y
> 
> >However, I think that the kernel remains in control of the F1/F2
> >brightness buttons and does not let pbbuttonsd read the button.
> 
> Perhaps a new pbbuttonsd will be updated to use /sys/class/backlight/
> instead of the PMU? 

Is there any news on this ? Do you need help ? (I may look at the code
but don't really know where to start)
-- 
Yves-Alexis

Re: extent brightness adjust in 2.6.18?

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

On Sun, 2006-09-24 at 10:45 +0200, Matthias Grimm wrote:
> Yes it will. I am just working on that. Maybe you could help me a bit
> and answer some questions.
> 
> 1. Do you see more than one entry in /sys/class/backlight?

I'm running 2.6.18-rc6 on a powerbook 5,6 (keyboard backlight present
and working)

corsac@hidalgo: ls -R /sys/class/backlight                           [~]
/sys/class/backlight:
total 0
drwxr-xr-x 2 root root 0 1904-01-01 00:10 radeonbl0

/sys/class/backlight/radeonbl0:
total 0
-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 actual_brightness
-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 brightness
-r--r--r-- 1 root root 4.0K 2006-09-24 12:20 max_brightness
-rw-r--r-- 1 root root 4.0K 2006-09-24 12:20 power
lrwxrwxrwx 1 root root    0 2006-09-24 12:20 subsystem
-> ../../../class/backlight
--w------- 1 root root 4.0K 2006-09-24 12:20 uevent


> 2. If so, what are they for? 
> 3. Has the keyboard backlight an entry in /sys/class/backlight too?

No it seems not (but maybe I'm lacking some config option)

>    I studied the kernel source and found no clue for that but I might
>    have missed something.
> 
Regards;
-- 
Yves-Alexis

Re: extent brightness adjust in 2.6.18?

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

On Sat, 23 Sep 2006 12:10:41 -0400
timotheus <pbb...@ts...> wrote:

> This is fixed with kernel option:
>     CONFIG_PMAC_BACKLIGHT_LEGACY=y
> 
> >However, I think that the kernel remains in control of the F1/F2
> >brightness buttons and does not let pbbuttonsd read the button.
> 
> Perhaps a new pbbuttonsd will be updated to use /sys/class/backlight/
> instead of the PMU?

Yes it will. I am just working on that. Maybe you could help me a bit
and answer some questions.

1. Do you see more than one entry in /sys/class/backlight?
2. If so, what are they for? 
3. Has the keyboard backlight an entry in /sys/class/backlight too?
   I studied the kernel source and found no clue for that but I might
   have missed something.

 Best Regards
   Matthias

Re: extent brightness adjust in 2.6.18?

[timotheus <pbb...@ts...>]

This is fixed with kernel option:
    CONFIG_PMAC_BACKLIGHT_LEGACY=y

>However, I think that the kernel remains in control of the F1/F2
>brightness buttons and does not let pbbuttonsd read the button.

Perhaps a new pbbuttonsd will be updated to use /sys/class/backlight/
instead of the PMU?

Regards,
timotheus

extent brightness adjust in 2.6.18?

[timotheus <pbb...@ts...>]

Hi,

There is a small issue with pbbuttonsd and kernel version 2.6.18.

Adjusting the LCD brightness works *only* when compiled with the new
option:
    CONFIG_FB_RADEON_BACKLIGHT=y

However, I think that the kernel remains in control of the F1/F2
brightness buttons and does not let pbbuttonsd read the button.  The
shift-F1/F2-key does not increase/decrease the brightness to
maximum/minimum extent like it does with kernels 2.6.17 and
older. Instead, it only increments/decrements by one level of
brightness, the same as if no shift-key is held.

This is the same regardless of KBDMode, but that is expected on my ADB
keyboard.  Details of the powerbook in question are at:
    http://tstotts.net/linux/gentoopb.html

Regards,
timotheus

PBButtonsd 0.7.8 released - minor bug fix

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

Hi,

Problems with an unstable autoconf package leads to some unresolved
script variables in configure. I rollback to an old version and fixed
the problem. Pbbuttonsd should compile and install as usual again. 

And what is a new release without a new feature ;-) This release got
an additional input handler that works around the synaptics trackpad
driver that blocks certain event devices for exclusive use.

I'm sorry about the short distance between the last two releases. I try
to plan releases better in the future (and request any bugtracker _before_
the release ;-)).

  Best Regards
    Matthias

PBButtonsd 0.7.7 released - minor feature enhencement

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

Hi,

a new pbbuttonsd release is out

This release now uses sysfs and open firmware to detect the machine
type and the I2C device, the LMU is connected to. This leads to a more
detailed machine identification and a more reliable detection of
ambient light sensor and keyboard illumination. 

A fix of a possible division by zero error in the ALSA module completes
this release.

You could download the package at usual locations:
   http://pbbuttons.berlios.de

 Have fun
   Matthias

upcoming new pbbuttonsd in CVS

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

Hi,
the upcoming new version of pbbuttonsd is in CVS. This version got new
detection routines for the machine type and the LMU controller. Both
use the open firmware device-tree now. Following conditions must be
fulfilled for the new detection routines to work:
  1. /proc/device-tree must exist
  2. i2c-dev kernel module must be loaded (on machines with a LMU).

Please test it and give me any feedback.

  Best Regards
    Matthias

Re: New I2C and machine probing method

[Juan A. D. <ju...@li...>]

nueces@galateia[~/ofp]$ strings /proc/device-tree/model
PowerBook6,7
nueces@galateia[~/ofp]$ cat /proc/cpuinfo
processor       : 0
cpu             : 7447A, altivec supported
clock           : 1333.333000MHz
revision        : 0.2 (pvr 8003 0102)
bogomips        : 73.47
timebase        : 18432000
platform        : PowerMac
machine         : PowerBook6,7
motherboard     : PowerBook6,7 MacRISC3 Power Macintosh
detected as     : 287 (iBook G4)
pmac flags      : 0000001b
L2 cache        : 512K unified
pmac-generation : NewWorld
nueces@galateia[~/ofp]$ ./of_probing

Probing machine...
  Machine: ID =3D 67
  OF: '/proc/device-tree/uni-n@f8000000/i2c@f8001000/reg'
    Path incomplete! One or more elements not found.
  LMU: No LMU found!


--=20
Juan A. Diaz

Re: New I2C and machine probing method

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

On Sun, 16 Jul 2006 15:45:57 +0200
Matthias Grimm <mat...@us...> wrote:

Thanks a lot for your support so far. I put the new knowledge into a
revised program and attached it again. Changes are:

- There are two known locations for the lmu-controller in the
  device-tree so far. Both are supported now.
- adding I/O error support. To communicate with the LMU the program
  must be run as root. If there was any problem with the device, an
  I/O error message would occur on terminal.
- removing all the silly warnings
- detailed machine identification by name added

I hope you give it another try :-)

 Best Regards
   Matthias

Re: New I2C and machine probing method

[Johannes B. <joh...@si...>]

> 2. detecting the LMU I2C address
>    The program looked for the "lmu-controller" in the device tree and
>    read the attached data to find out the I2C address.
>    This test will only have a result, if you have a PowerBook with an
>    ambient light sensor. Otherwise the program won't find an LMU.
>    If your machine definitely has an ambient light sensor and the program
>    won't find it, the device tree path might be wrong. In this case please
>    send me the correct path or an tar archive of /proc/device-tree.

I haven't tested it, but a quick look at the code suggests it won't find
it here:

johannes:/proc/device-tree/uni-n@f8000000/i2c@f8001000/i2c-bus@0/lmu-micro@84$
hd compatible
00000000  6c 6d 75 2d 63 6f 6e 74  72 6f 6c 6c 65 72 00     |lmu-controller.|
0000000f

...$ hd device_type
00000000  6c 6d 75 2d 63 6f 6e 74  72 6f 6c 6c 65 72 00     |lmu-controller.|

johannes