I've checked various pages but haven't found a solution for access my LEDs: So my Pogo has a red and a green one, sys/class looks like: lrwxrwxrwx 1 root root 0 Aug 16 16:01 sheevaplug:blue:health -> ../../devices/gpio-leds/leds/sheevaplug:blue:health lrwxrwxrwx 1 root root 0 Aug 16 16:01 sheevaplug:red:misc -> ../../devices/gpio-leds/leds/sheevaplug:red:misc ok, pogo is notby cholat - Displays
Damn a) you're right. Output of fw_printenv was fooling me b) how could it have ever been worked before? Weird c) Don't want to break the "never touch a working uboot"-rule, though 2017.07 features sound promising. But I'm a sissy.by cholat - uBoot
Hi. I use uboot 2011.5 (or 2012? I have to double check later). I'm booting Debian via USB stick, everything is working fine so far. But there seems to be a problem with UBootEnvVariables: some parameters are ignored, i.e. if I enter /usr/sbin/fw_setenv serverip=172.17.0.3, it's not listed in output of fw_printenv. Thus netconsole is not working. It's weird, because it has been woby cholat - uBoot