UnixOutlaw

Members
  • Content Count

    15
  • Joined

  • Last visited

About UnixOutlaw

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

667 profile views
  1. Already tried that - still won't resolve hostnames on my LAN (two different LANs - my home LAN and my work LAN)... NSSWITCH usually one of the first places I look (hangover from Solaris)... hosts: files mdns4_minimal dns myhostname Also - noticed some wildly different results from /sys/power/axp_pmu/battery/ output compared to Armbian Xenial on the same hardware... I don't know if that's because Bionic is drawing more power and battery never gets to 100%... but its always around 96% and always "discharging" ╰─➤ cat /sys/power/axp_pmu/battery/capacity 96 ╰─➤ cat /sys/power/axp_pmu/battery/charging 0
  2. thanks for that info - the issue I have with Armbian, I can resolve the Armbian hosts on my LAN from other machines (all Linux), but from Armbian itself I can't resolve other host's names... Not 100% sure what "publish-workstation" does - but it kinda sounds like advertising itself on the LAN? Anyway I reset that to "yes" on a Linux laptop (x86_64) and on Armbian, and it's the same as before... I might try out stretch then... avahi works out of the box for me on Raspbian Stretch...
  3. Update : it's not working on any of my Armbian machines... doesn't work on Xenial Armbian 5.7 on bananapi, or Xenial Armbian 5.6 on orangepi+ 2E... those machine names can be resolved from other hosts on the LAN, but they themselves are unable to resolve other machine names on my LAN. I could have sworn it was working previouisly. Close this topic - clearly not related to Armbian Bionic... I have no idea what's going on...
  4. Banana Pi (original "model 1") A20 Was running flawlessly on Xenial - latest updates - almost everything worked (I run it on a LiPo battery to transport back and forth from work to keep my Resilio Sync data "in sync") Resilio seems to work fine - except in Bionic I can't use avahi to resolve names on my LAN... this worked in Xenial on the same hardware. The reason I decided to try out Bionic? Couldn't find a resource to upgrade from OpenSSH 7.2 to 7.3 or greater (I'm making heavy use of features not available in OpenSSH 7.2 on my other machines). I've tried tweaking my /etc/nsswitch.conf file to no avail... Sheesh - "avahi" just worked out of the box on Armbian Xenial - and it works out of the box on Bionic on x86_64... Works out of the box on Raspbian Stretch on my RPi 3B. Works out of the box on Armbian 5.6 (Xenial) on my Orange Pi+ 2E... Qualification : avahi works on the Banana in that other hosts can reach it (e.g. "ping ffrwchnedd.local" works from any other machine) - so it's announcing itself on my LAN, but it cannot use avahi to reach other hosts by hostname.local (no problem pining actual IP address of other devices). If I can't resolve this soon - I'll go back to Xenial and try and figure out how to do some version control on my ~/.ssh/config file(s) (I have a common one symlinked from my Resilio Sync folders). P.S. I didn't upgrade in place - I just booted from a fresh flashed SD card so I can backout to Armbian 5.6 Xenial without too much pain (other than re-syncing 130 GB of Resilio Sync folders - stored on 256 GB USB drive).
  5. I downloaded 5.20 Jessie Legacy for one of my PineA64+ 2 GB the other night - dumped to SD-card - booted.... and hey presto after apt-get upgrade and reboot - using all of my 64 GB card... automagically? I didn't have to do anything... I'm now running it "headless" as a Tomcat server running Apache Guacamole - and it's nice and quick - and I'm getting gigabit from the NIC too... Thanks guys awesome job on Armbian! Kinda wish I could run it on my RPi3 and NTC CHIP... Got it running on one of my Pine boards, my OPi+ 2E and BananaPI... I dropped a paypal Donation in to Igor earlier today...
  6. Awesome - I spent the whole morning reading this thread (and it killed my morning - which is a good thing!). I learned more reading this whole 4 page thread - than in five months hanging around the Pine64 forum - I call that "moderator" a couple of nasty names - Pompous Princess - or Merkin777... Can't believe the amount of bullshit information that "A" hole has steered me wrong with! Thanks for all the insiteful info from contributors on this forum and this thread!
  7. I've got Armbian running on a BananaPI - it cr@ps all over Bananian... I've got Armbian running on OPi+2E - love it... I've got Armbian running on one of my Pine64+ (got DietPI on the other one)... As for "backups" - I was early on frustrated by the lack of Dropbox support (in ARM world but mostly for NTC CHIP). Initially ad some rsync scripts - but it got a bit unwieldy... So - now I use "unison" - push stuff (not everything) from my Dropbox folder on an x86 Linux machine to an NTC CHIP accessible from the worldwide interwebs (and via dyndns) - I can then use unison to sync copies I have on ARM devices (running Linux) and even my ghastly Surface Pro 3 at work running the Microsoft Bash Shell (the canonical thing you get from Insiders Fast Track build). Mostly all I'm replicating is shell scripts and SSH keys... I don't think I'd use it for lots of large files (e.g. music)... However - I have noticed a few little niggly things with Unison - versions on either side need to be fairly close. e.g. I enabled Sid on my OPi+2E - and "apt-get dist-upgrade" replaces Unison 2.40 with 2.48 (and they're incompatible) - so I have to disable Sid, update, then apt-get install - but it's workable...
  8. I couldn't get WiFi working on my home network Armbian Jessie on OPi+2E using wicd - so I removed wicd and installed network-manager and network-manager-xfce... and it just worked...
  9. Well there ya go! Fixed it myself... I'd previously enabled sid and stretch repos - then commented them out. Removed comments, "apt-get update", then "apt-get upgrade" - now I can install the prerequisite / dependencies! -- edit -- Only enabled "sid" - not both stretch and sid...
  10. I actually removed wicd (and associated packages) and installed network-manager and network-manager-gnome... Not a big fan of wicd... I just keep connection entries in /etc/NetworkManager/system-connections/ for the various Networks I join... e.g. One for a Corporate / Enterprise SSID - couldn't connect to it using wicd (file originally created on an amd64 Ubuntu 15.10 machine) - wasn't able to generate the file using either wicd or NetworkManager - but I had the file handy... Just had to remove the MAC address (as seems to get a different MAC address on boot each time - on wlan0, OPi+ 2E).
  11. OPi+ 2E : Active settings: cpu 1296 mhz allowed, 1296 mhz possible, 4 cores active dram 672 mhz hdmi/gpu active usb ports active eth0 10Mb/s/Half, Link: no wlan1 IEEE 802.11bgn ESSID:"Navitas Corporate" Mode:Managed Frequency:2.437 GHz Access Point: 34:6F:90:9C:AE:93 Bit Rate=43.3 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=65/70 Signal level=-45 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:15 Invalid misc:183 Missed beacon:0 wlan0 unassociated Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
  12. Trying to install qutebrowser in Armbian on OPi+ 2E (H3) - but get stuck on dependencies : apt-get install python-tox python3-pyqt5 python3-pyqt5.qtwebkit python3-sip python3-pypeg2 python3-jinja2 python3-yaml This is then followed up (if successful) by : dpkg -i qute-package.deb However cannot install all those dependencies (if I remove python3-pypeg2 from the list) : root@sporange:~/qutebrowser-0.8.2# apt-get install python-tox python3-pyqt5 python3-pyqt5.qtwebkit python3-sip python3-jinja2 python3-pygments python3-yaml Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-pyqt5 : Depends: libqt5designer5 (>= 5.0.2) but it is not going to be installed Depends: libqt5gui5 (>= 5.3.0) but it is not going to be installed Depends: libqt5help5 (>= 5.3.0) but it is not going to be installed Depends: libqt5printsupport5 (>= 5.3.0) but it is not going to be installed Depends: libqt5widgets5 (>= 5.3.0) but it is not going to be installed python3-pyqt5.qtwebkit : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be installed Depends: libqt5webkit5 (>= 5.2.0) but it is not going to be installed Depends: libqt5widgets5 (>= 5.2.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. And then if I download : https://qutebrowser.org/python3-pypeg2_2.15.2-1_all.deb Install that - still get other dependency issues - end up in a seemingly endless loop... Anyone have any clues / pointers? I've managed to install xombrero and dwb - but I was just getting used to qutebrowser (Windows, x86 Linux, ARM Linux [pine <dietPI>,CHIP <ChipOS>) and would really like this running on Armbian on the OPi+ 2E. I might see if I get same issues on my BananaPI running Armbian... P.S. slightly off topic - however I was "considering" getting stuck in and having a look at porting / running Armbian on CHIP (Allwinner R8) - but no idea on the difficulty level of this. I've got 5 CHIPs (one inside a PocketCHIP) and getting another 4 more in the next few weeks.
  13. I just got my 2E the other day - did nand-sata-install yesterday - and it worked flawlessly... Maybe try doing a "factory" install of Android to the eMMC (no idea how you do that - I hate Android - only use it because I "have" to on my phone) - then boot Armbian off SD card, then try the nand-sata-install again? My 2E came with Android on the eMMC (everything in Chinese)... Personally - love how fast the 2E boots off eMMC... Love Armbian too... when I get more "financial" I'll chip in to the project...
  14. Oh well - thanks for the heads up - guess I'll have to "think outside the plox"... Which means I'll be in the market for something like the Plox to keep the OPi+ 2E running - mainly just as a UPS for when I close the lid on the Lapdock
  15. Hi, Just signed on - I've got Armbian running on my BananaPI (i.e. the original plain Jane BPi) - and liking it on there so far. So - I was impressed with Armbian on there - and shelled out and got the OPi+ 2E - flashed an SDCard with Armbian - booted up - and really liking it. Only got it yesterday (took like a month after arriving in the country [AU]). Did nand-sata-install, successful and rebooted - and now running Armbian off eMMC - runs sweet. Really impressed so far - VASTLY better experience than Pine64 (I'm looking for a desktop experience on Arm - for no other reason than "because it's there"). Got Chromium browser working - synergy KVM and Plank Dock... full blown desktop experience. So - all I need now is to be able to run it off a LiPo battery. I tried joining the OrangePi org forum - but my forum ID is awaiting verification - and I haven't received an email from them - so no idea how that works - so I'm posting here. I'm assuming I can just use a couple of the pins on the RasbPI 40 pin connector - but - which ones, and - most importantly - will the H3 CHIP charge a LiPo that's hooked up? Found the attached pinouts diagram - there's two that are 3.3V+ - but no idea if that's in or out - or do I use the +5V pins on 2 or 4? Right now I'm running off a Plox Brick into the Pwr IN jack - the Plox is one of the few bricks I've got that allow simultaneous charging and output... However I'm using a Lapdock - and I'd rather run off this - however neither of the regular USB ports provide power - and even the USB "otg" output on the Lapdock disconnects power when opening/closing the lapdock lid... So I was thinking of rigging up a battery, and a female "otg" connector straight into the 40 pin PI array - but not sure which pins... I'm guessing 2 or 4, with 6 for ground...