Problems with LED pattern and keyboard light - maemo.org

raverpol | # 1 | 2010-06-10, 21:12 | Report

Hi guys

I have problem with LED patterns and keyboard light. They don't work and when I try to LED Patterns program and do LED test there is error msg: "Exit status: 65280 faild to set red led current"

Anybody knows what is wrong??

raverpol | # 2 | 2010-06-16, 22:53 | Report

hi guys
any idea??

baron von bubba | # 3 | 2010-07-03, 00:05 | Report

bump.
same problem for me.
did you sort this?
or anybody know a solution please?

Last edited by baron von bubba; 2010-07-03 at 00:20.

nitro99 | # 4 | 2010-07-03, 12:14 | Report

Hey count me in too. restoring the original MCE.ini also does not help

The Following 2 Users Say Thank You to nitro99 For This Useful Post:
ajayjohn, MaemoNoob

pH5 | # 5 | 2010-07-03, 12:39 | Report

Originally Posted by raverpol View Post

I have problem with LED patterns and keyboard light. They don't work and when I try to LED Patterns program and do LED test there is error msg: "Exit status: 65280 faild to set red led current"

Anybody knows what is wrong??

This is the LED pattern editor failing to open /sys/class/leds/lp5523:r/led_current for writing. Could you open the terminal and check if it exist?

Code:

~ $ ls /sys/class/leds/lp5523:r
brightness   led_current  subsystem    uevent
device       power        trigger

Is the LED driver loaded (does the led_class and leds_lp5523 kernel modules appear in lsmod output)?

Code:

~ $ lsmod | grep leds_lp5523
leds_lp5523           9792  0
led_class             2948  2 leds_lp5523,leds_twl4030_vibra

The Following 3 Users Say Thank You to pH5 For This Useful Post:
baron von bubba, strank, Zentenario

baron von bubba | # 6 | 2010-07-05, 07:44 | Report

Originally Posted by pH5 View Post

This is the LED pattern editor failing to open /sys/class/leds/lp5523:r/led_current for writing. Could you open the terminal and check if it exist?

Code:

~ $ ls /sys/class/leds/lp5523:r
brightness   led_current  subsystem    uevent
device       power        trigger

Is the LED driver loaded (does the led_class and leds_lp5523 kernel modules appear in lsmod output)?

Code:

~ $ lsmod | grep leds_lp5523
leds_lp5523           9792  0
led_class             2948  2 leds_lp5523,leds_twl4030_vibra

thanks for reply.

Originally Posted by

no such file or directory

"twl4030:vibrator" is the only folder i have in /sys/class/leds

The Following 3 Users Say Thank You to baron von bubba For This Useful Post:
ironm8, strank, Zentenario

nitro99 | # 7 | 2010-07-08, 06:37 | Report

Same results here too

the LED drivers is loaded but there is no such files in the /sys/class/leds only twl4030:vibrator

If these files were deleted any way to get it back?

pH5 | # 8 | 2010-07-08, 07:55 | Report

Originally Posted by nitro99 View Post

Same results here too

the LED drivers is loaded but there is no such files in the /sys/class/leds only twl4030:vibrator

If these files were deleted any way to get it back?

Can you check what appears in the dmesg output when you remove and reinsert the kernel module (needs rootsh installed)?

Code:

~ $ sudo gainroot
/home/user # rmmod leds_lp5523
/home/user # modprobe leds_lp5523
/home/user # dmesg
...
lp5523 2-0032: LP5523 Programmable led chip found
i2c_omap i2c_omap.2: controller timed out
lp5523 2-0032: got interrupt from led chip
lp5523 2-0032: interrupt from led chip 4f
lp5523 2-0032: all engines configured
lp5523 2-0032: disabling engines
Registered led device: lp5523:kb1
Registered led device: lp5523:kb2
Registered led device: lp5523:kb3
Registered led device: lp5523:kb4
Registered led device: lp5523:b
Registered led device: lp5523:g
Registered led device: lp5523:r
Registered led device: lp5523:kb5
Registered led device: lp5523:kb6
/home/user #

The Following 3 Users Say Thank You to pH5 For This Useful Post:
baron von bubba, strank, Zentenario

nitro99 | # 9 | 2010-07-08, 09:21 | Report

Ok done all that but strangely there is no line with 'lp' in it.
i did 'dmesg | grep lp'....no result...

shld i post my complete result here?

baron von bubba | # 10 | 2010-07-10, 07:42 | Report

sorted out, just did a reflash, emmc and firmware.

seems i had done it in the wrong order last time!

The Following User Says Thank You to baron von bubba For This Useful Post:
noobmonkey