This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Thank you! Many roads to Rome.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I attached the script.
** Attachment added: "backlight.sh"
http://launchpadlibrarian.net/48162134/backlight.sh
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I had to make a little modification for the script so it will work after
reboot too:
st...@stoto-laptop:~$ cat backlight.sh
#!/bin/bash
if [ `ls -al
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness | awk
{'print $1'}` != -rwxrwxrwx ]; then
gksudo chmod 777
/sys/d
I found a solution:
I made a script, with that i can control the brightness:
st...@stoto-laptop:~$ cat backlight.sh
#!/bin/bash
$act
act=`cat /sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness`
echo $1
case "$1" in
inc)
if [[ $act -lt 255 ]]; then
Peter S. wrote:
> However i am able to control the brightness width the following command:
>
> sudo echo 180 | sudo tee
> /sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
>
> Where 180 is the brightness, it goes from 0 to 255.
>
> Any way to bind it to the keyboard backlight
However i am able to control the brightness width the following command:
sudo echo 180 | sudo tee
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
Where 180 is the brightness, it goes from 0 to 255.
Any way to bind it to the keyboard backlight keys?
--
[Jaunty] MacBook 5.1
I have a fresh install of 10.4 and the problem still exists. nvidia-bl
package fixed my screen backlight control but, i still cant activate my
keyboard backlight on my macbook 5.1. I will attach a report.
** Tags added: apport-collected
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
ht
@Chris: I am pretty sure that nvidia-bl only controls the screen, not
the keyboard backlight and hence this bug is still valid (well for me it
definitely doesn't fix it)
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
[Jaunty] MacBook 5.1 keyboard backlight not support
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
This bug can be closed. It was resolved with the release of the nvidia-
bl-dkms 0.15 series of packages. Thanks for checking.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Chris,
This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest development release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/lucid.
If it remains an issue
As of ubuntu 9.10 beta 5, the default driver for the mactel keys doesn't
work. But pommez, at least the latest git commit as of today, works
almost well -- only F1/F2 for LCD backlight don't work. So whoever is
taking care of an update for 9.10, please do so ...
--
[Jaunty] MacBook 5.1 keyboard b
You should not use pommed on these newer macs. It is depreciated.
Instead the driver should be patched.
Ricky
On Jun 21, 2009, at 10:22 AM, Jim Rorie wrote:
> Someone updated the community docs to state that pommed now works. I
> installed it and does work, but there are some differences.
Someone updated the community docs to state that pommed now works. I
installed it and does work, but there are some differences. #1) The
option to swap the default Fn behavior becomes disabled and the
suggested configuration for pommed doesn't appear to work. #2) pommed
appears to have the keybo
The hal-applesmc package in the mactel-support ppa is now updated for
jaunty.
This hal interface for the applesmc Linux module is required for the
keyboard backlight and adjustment keys to work properly.
** Changed in: mactel-support
Status: New => In Progress
--
[Jaunty] MacBook 5.1 ke
Sorry, I just realised that my previous post should go in the "left-speaker"
bug :-p
Nikos
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
OK, folks if you stick your ear just below the right speaker (and a bit
on the left), right where the woofer lies, you might hear just enough to
convince you that the woofer works _also_ under Ubuntu as I did right
now. So, I confirm hearing the woofer but... it's so weak as if it's not
there at al
Yep I can confirm all those bugs too with MBP5,2 Jaunty 64.
There seems to be a common denominator in all them and that is
gnome-power-manager. Which i suspect we may need a PPA version of in order to
resolve this completely and those other issues.
--
[Jaunty] MacBook 5.1 keyboard backlight
Yep, thanks for the information.
* Your description is more than accurate ( with respect to
[https://bugs.launchpad.net/bugs/357112 Bug 357112]). I 've just posted
a confirmation to attract more attention to the bug.
* The same for [https://bugs.launchpad.net/bugs/357107 Bug 357107].
* About [ht
Nikos, please see Bug 357112. I haven't tried the PPA mentioned above by
P. Dunbar, but maybe Bug 357107 and Bug 360177 still apply, too.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of
P. Dunbar, Thanks a lot for the hint!
The F-keys for the keyboard backlight work the same way like for the
display. I still feel however that they are not that _responsive_ as
they could/should.
Nikos
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/33794
After more searching regarding this same issue seen in Intrepid it seems there
was a gnome-power-manager provided in the PPA to help address light-sensor
readings adjusting the brightness of keyboard backlight.
I've also tried mucking around in this file
/usr/share/hal/fdi/information/10freede
Install this and it will work:
https://edge.launchpad.net/~adamhorden/+archive/ppa/+sourcepub/523564
/+listing-archive-extra
I have other issues with it being that now it generally ALWAYS keep the
keyboard backlight on. Doesn't seem to effectively utilize the light
sensors. I mentioned the issue
P. Dunbar,
It does not work for me either, as for everyone else I suppose. Also, I
don't see anywhere in the wiki [1] a reference in the wiki about the
backlit-keyboard F-keys (F5, F6) working.
Cheers, Nikos
[1] https://help.ubuntu.com/community/MacBookPro5-1_5-2/Jaunty
--
[Jaunty] MacBook 5.1
any ideas here? someone updated the mbp5-1,5-2 jaunty wiki that its
working for them. can anyone else confirm this working? It does not
work for me and I'm on released Jaunty 64-bit on MBP5,2.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You r
I confirm this bug with Jaunty 64-bit on a MacBookPro4,1. To activate
keyboard backlight, I have to use these commands:
$ sudo modprobe applesmc
$ echo 150 | sudo tee
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
h
I confirm this bug with Jaunty 64-bit on a MacBookPro4,1. To activate
keyboard backlight, I have to use these commands:
$ sudo modprobe applesmc
$ echo 150 | sudo tee
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
h
that and gnome-power-manager I believe.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
My guess is: hal-applesmc - 0.14
is available for intrepid and not Jaunty yet...
But I'm not sure if it can get working without that modification.
And I think I recall reading Henrik isn't working on Jaunty anymore and he
created that package for Intrepid.
--
[Jaunty] MacBook 5.1 keyboard backli
I'm curious as to why this worked without manual modification using the
Mactel PPA for Intrepid but not for Jaunty. What was provided in that
package that's not provided in the Jaunty package?
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You rece
so GPM sees the button press events correctly it appears...
how do we get it communicating with leds_smc_kbd_backlight now to actually
bring the backlight on or off?
If anyone would like more output please let me know.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.laun
the hal-find-by-capability --capability keyboard_backlight
outputs nothing
if i try:
hal-device | grep kbd
41: udi = '/org/freedesktop/Hal/devices/leds_smc_kbd_backlight'
linux.sysfs_path =
'/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight' (string)
info.udi = '/org/freedesktop
since the applesmc module seems to be working, what does
hal-find-by-capability --capability keyboard_backlight
output? at first i got 2 devices, which seems to confuse gnome-power-manager.
additionally,
gnome-power-manager --no-daemon --verbose sometimes gives valuable diagnostics.
ciao,
Mario
I tried looking at pommed to get this working as well but the current version
in the repos (1.25) says:
Unknown Apple machine: MacBookPro5,2
so that's a dead end for now.
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notifi
I usually sudo -i first then I run the command and you don't get permission
denied.
You could also run it the same way as
echo 255 | sudo tee -a
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
Both work, I like your path better cause its shorter.
--
[Jaunty] MacBook 5.1
I don't know if this is relevant but when I run:
# echo 255 >
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
I get permission denied. However, I can run:
# echo 255 | sudo tee -a /sys/class/leds/smc::kbd_backlight/brightness
..from the intrepid docs and it works flawless
I can manually control keyboard backlight with
echo 255 > /sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
to fully turn on or echo 0 to turn it off... This was after the install of
applesmc-dkms.
There does seem to be some oddity traversing the directory structure
there as
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Changed in: mactel-support
Importance: Undecided => Low
** Also affects: hal
Importance: Undecided
Status: New
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bug
** Description changed:
The keyboard backlight on the MacBook 5.1 is not supported as of Jaunty
(Ubuntu 9.04) Alpha 5. This is supported in Intrepid (Ubuntu 8.10) by
- the Mactel PPA packages.
+ the Mactel PPA packages hal-applesmc, hid-dkms, and possibly nvidia-bl-
+ dkms, though I installed
** Attachment added: "lspci output"
http://launchpadlibrarian.net/23442652/lspci.txt
** Also affects: ubuntu
Importance: Undecided
Status: New
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because
42 matches
Mail list logo