On Sun, Feb 26, 2012 at 3:46 AM, Achim Vollhardt <avoll...@physik.uzh.ch> wrote: > Thanks to Lee, the problem has been solved: > >> Try adding: >> >> leds-alix2.force=1
FYI, daily build should be adding that automatically, via VOYAGE_SYSTEM_MODULES in etc/voyage-profiles/alix.pro [jimc@groucho voyage-profiles]$ more alix.pro VOYAGE_PROFILE=ALIX VOYAGE_SYSTEM_CONSOLE=serial VOYAGE_SYSTEM_SERIAL=38400 VOYAGE_SYSTEM_PCMCIA=no VOYAGE_SYSTEM_MODULES="lm90; w83627hf; scx200_acb base=0x810,0x820; geodewdt; led-class; leds-alix2 force; ledtrig-heartbeat; ledtrig-timer; ledtrig-netdev" Is there a need to have alix2d, alix3d etc ?? could you try daily-build, and verify the module parameters ?? >> >> as a kernel boot parameter and see how it works. >> >> If the kernel has the right options compiled in, this should get you >> going. >> >> The problem is that on the 2Dxx it can detect the LED's... on the 3D3 >> (because of the different BIOS), it cannot. This is the short >> explanation... you can dig on the internet to find why. >> >> >> Cheers! >> >> >> Lee > > > The devices are now listed in the /sys/class/leds folder and can be > accessed.. Thanks again! > > Achim > > _______________________________________________ > Voyage-linux mailing list > Voyage-linux@list.voyage.hk > http://list.voyage.hk/mailman/listinfo/voyage-linux _______________________________________________ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
