On Fri, Jan 3, 2014 at 4:41 PM, KurtE <[email protected]> wrote: > >> sudo iwconfig wlan0 power off >> > Thanks, it appears this device does not support that: > > kurt@arm:~/Raspberry_Pi/Phoenix$ sudo iwconfig wlan0 power off > Error for wireless request "Set Power Management" (8B2C) : > SET failed on device wlan0 ; Operation not supported.
darn, i know it works for some devices.. I usually just run Atheros chipsets... > On other note, looking back up where I used to get information about setting > up ttyO1... > http://blog.pignology.net/2013/05/getting-uart2-devttyo1-working-on.html > > It looks like since I last did this, there was another way (Angstrom), by > adding the info to: > "just add you BB-UART2 to /media/BEAGLEBONE/uEnv.txt, with the key > capemgr.enable_partno." > > with This Debian build my /media directory is empty. Should creating this > directory and file work here as well? The only place on my machine I found > uEnv.txt is in the /boot/uboot directory. There's a hint here, "/boot/uboot/uEnv.txt" root@beaglebone:~# cat /boot/uboot/uEnv.txt | grep cape #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > Or should I try the way I was doing before, something like: echo uart2pinmux >> $SLOTS > where $slots was defined earlier on as: > export PINS=/sys/kernel/debug/pinctrl/44e10800.pinmux/pins > export SLOTS=/sys/devices/bone_capemgr.9/slots > (the .9 sometimes changes, earlier I had .8) Yeap, never hardcode .8 or .9 in your script, always check.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
