tomsaul

Members
  • Content Count

    16
  • Joined

  • Last visited

About tomsaul

  • Rank
    Member

Recent Profile Visitors

497 profile views
  1. Platform oPi Plus 2E with Armbian 5.31 (Legacy). I have configured a WiFi adaptor, and it works fine in connecting to an existing hotspot. When I attempt to use network manager applet (or nm-connection-editor/nmtui from a root prompt) to create an Ad-hoc network I am getting permissions errors. For NM TUI it is 'Unable to save connection: Insufficient privileges.', and similar for the other methods. Can anyone give me some pointers on how to diagnose and/or fix this? From the research I have done the nm-applet error is likely a simple config error (not set up to run as root for this function), but the other avenues failures seem odd.
  2. For current OS installs, to get this to compile edit the file include/ieee80211.h, search for 'extern __inline' and replace with 'static __inline' for the three offending declarations! This allows it to compile cleanly.
  3. Env is ARMBIAN 5.31 stable Ubuntu 16.04.2 LTS 3.4.113-sun8i When I run Kismet on this system (which creates a new interface in Monitor mode - wlan0mon), the original WiFi interface loses any connections, and will no longer function properly. Is this a expected behavior? Is there any way to get both monitor and normal mode to co-exist? I've looked around and don't see any obvious driver updates that would address this. Any suggestions (beyond adding a second WiFi adapter)?
  4. Ditto for me - OrangePi Plus 2E with Legacy kernel. Updated using apt-get upgrade and dist-upgrade, and when I just tried this it has similar error (but also works on an older backup of bin file).
  5. I have installed the 'watchdog' package (apt-get install watchdog' on an Orange Pi Plus 2E, and it does not seem to be working as I would expect. If I write output to /dev/watchdog the system will reboot, but if I stop the watchdog service (and wd_keepalive) the system does not reboot. I did un-comment the path to /dev/watchdog in the settings file, but have generally not changed anything else. Is there some other required setup needed to allow this to function?
  6. When attempting to update to the dev kernel I ran ' apt-get install armbian-firmware sunxi-tools swconfig a10disp ' per the instructions. It is not finding the swconfig and a10disp packages with the standard repositories active (I have done apt-get update). If these are in an alternative location, perhaps add a line in the kernel update instructions (for various Orange Pi in my case) to add it. I see one older message referencing it being available on a beta site. The same command is present for the non-dev instructions. It also seems odd that a10disp is listed for these H3 based boards (but there is also no h3disp package). Are the instructions wrong/old, or do we really need these packages?
  7. In the old system you had an option to search by the message ID. So far I have not found an equivalent in this new incarnation. Were the old IDs transferred, and can they be searched for?
  8. FWIW - I updated a second system, and it is not suffering the same problem. I'd still like to correct the original, but if needed I can flush and do a clean install.
  9. I recently updated the OS (apt-get dist-upgrade), for one of my test systems, and subsequent to this Kismet has stopped working with the wlan0 interface. Everything was working properly before this update. I see it (and wlan0mon) showing Promiscuous mode in the output of iwconfig. I'm not really a Linux person, so any pointers on how I can diagnose/repair?
  10. FWIW - in case others have a similar issue, the problem was quite simple - the system 'disk' was full. Even though there was enough space to do other tasks, and start the UI manually, it apparently didn't have enough to start at boot. After space was cleared, it resumed working as expected.
  11. The system is running from the emmc, so if this is poor quality we all have problems. Power is not a problem (dedicated 2A supply, and unit generally only uses half that). I do not have a nodm.conf on the unit that is misbehaving, or on one that is working properly. If I manually run startx I get the desktop (same as if I run startxfce4). I'll dig around a bit more to see if I somehow killed some critical file in my home directory or elsewhere, but I suspect other causes. And FWIW - the nodm daemon/service is shown in various rc#.d directories. I'll check to see if one of its dependencies is having issues as well.
  12. Perhaps - but since this was showing the desktop (and doing auto-login) before, and spontaneously stopped, the main question is why, and what I need to do to fix it.
  13. So this does show the desktop when run manually. So the question remains as to what would have caused this to no longer be automatically started (and how do I restore that)?
  14. No luck for that - still no desktop. One other note - I am now seeing (noticing) a message about A start job is running for dev-ttyS0.device This message appears several times, with a countdown as it waits for the port. The user manager messages generally appear just after this gives up. I had customized the serial port setup on this system to enable the ports on the 40 pin GPIO header (and as I recall to disable the normal console port).
  15. First, I am generally not a Linux person, so pardon any silly questions here. I am working on an OrangePi Plus 2E with (recent) Armbian. It has been working fine with the Jessie Desktop for several weeks now. I generally am running it 'headless', so I'm not sure exactly when, but sometime between last Saturday and yesterday I seem to have lost the desktop (and autologin, ...). I see a number of messages on the console at boot, including 'Stopped User Manager for user ID 1000' and then removing 'slice' for this user. The system is operating fine, just not the UI. So, how do I get autologin and desktop back (other than a new install)? What might have caused this to happen? I think I saw that a system update was being loaded on one boot. How can I check this? I seem to recall seeing a note that these images were set to auto-update. Is that true, and if so, how can I disable? FWIW - I have done an apt-get update/upgrade, with no change in behavior.