Kevin

  • Content Count

    11
  • Joined

  • Last visited

About Kevin

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Minneapolis, MN

Contact Methods

  • Website URL
    http://n0bel.net
  1. Thank you for the quick response. sunxi-keyboard and sunxi-keypad seem to be too specific for my use.... I'm just looking for one or two push buttons, and something that can be dynamically set (kernel module params or sysfs or fex) I like your idea of taking gpio_keys.c and making a new kernel module and having read the fex file. That may be the route I take. Have you ever heard of a kernel module which takes settings from sysfs and performs gpio to keyboard input? Thanks, Kevin
  2. All of the docs that I see on how to use the kernel gpio_keys refers to dts (device tree). The kernel module is present in Armbian legacy 5.20 Jessie Desktop. /lib/modules/3.4.112...../gpio_keys.ko I understand it should map gpio inputs to keystrokes. But all usage/configuration info I can find refers to entries made in Device Tree -- gpio-keys { compatible = "gpio-keys"; left-key { label = "Left key"; gpios = <&gpio0 17 0>; linux,code = <69>; /* KEY_LEFT */ }; } This refers to some other underlying hardwa
  3. Orange Pi Lite -- 5.20 -- Wifi -- PERFECT! Great work. Do you guys have a donation page?
  4. Orange Pi Lite - Armbian 5.14 The desktop shutdown (or shutdown -h now) shuts down the desktop, the system starts shutting down, then the desktop starts again, then disappears and the system shuts down. Its not a disastrous problem, but just annoying. I've traced it to the fact that 'nodm' is seeing the desktop stop, and then restarting it. Apparently either 'nodm' isn't getting the shutdown signal, or ignoring it, or getting it too late. Any guidance on what 'nodm' config, or some other config might help me to fix this? /K
  5. My fix was not about usb wifi dongles, but about the built in wifi on an orange pi lite.
  6. Yes you need to create /etc/wpa_supplicant.conf if you follow my example exactly.
  7. @msdev: You mean like this: https://pypi.python.org/pypi/python-lirc/1.2.1 You can also pipe irw into python http://www.lirc.org/html/irw.html
  8. This is my final solution to this issue. I hope it works consistently for everyone. This applies to Armbian Jessie 5.15 Desktop. No idea at this point about other versions. After many trials, I find that wicd is broken. Some confirmation can be found here: http://forum.armbian.com/index.php/topic/1775-wicd-gets-erroneous-bad-password/?p=14708 So abandoning wicd, I uncheck all "Automatcially connect to this network". I turned to this post as a guide: http://askubuntu.com/questions/406166/how-can-i-configure-my-headless-server-to-connect-to-a-wireless-network-automati/406167#
  9. When I run wpa_supplicant from the command line directly, the connection takes between 1 and 2 seconds. So their first fix for wicd probably won't work for me. It appears the goal will be to replace wicd with network manager, (with some success by some to accomplish that in that thread). For now I'm abandoning wicd... my solution will be documented next.
  10. @Eric, I've posted my experience so far here: http://forum.armbian.com/index.php/topic/1915-orange-pi-lite-doesnt-connect-to-wifi-networks/#entry14984 The suggestion you found and used was one I've tried. Still secured WiFi only connects maybe 1 out of 10 times, all other times, it returns "Bad Password".
  11. My experience with this is that trying all these various things about fixing the WiFi, work... but only randomly. I reboot or reconnect with the same settings, and 1 out of 10 (aprox) times the connection succeeds. The other times it gives "Bad Password". When it does connect, it is rock solid, until you disconnect. I'm curious to all those who had success with the Orange Pi Lite, actually had continued success on multiple shutdowns/disconnects/powerdowns. Does it actually reliably connect? /K