Superkoning

Members
  • Content Count

    28
  • Joined

  • Last visited

About Superkoning

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I bought a new 32GB SD-card, put Armbian Bionic on it, and succesfully upgraded to Cosmic. FWIW: $ grep -irn cosmic /etc/apt/* | grep -vi "#" /etc/apt/sources.list:1:deb http://ports.ubuntu.com/ cosmic main restricted universe multiverse /etc/apt/sources.list:4:deb http://ports.ubuntu.com/ cosmic-security main restricted universe multiverse /etc/apt/sources.list:7:deb http://ports.ubuntu.com/ cosmic-updates main restricted universe multiverse /etc/apt/sources.list:10:deb http://ports.ubuntu.com/ cosmic-backports main restricted universe multiverse /etc/apt/sources.list.distUpgrade:1:deb http://ports.ubuntu.com/ cosmic main restricted universe multiverse /etc/apt/sources.list.distUpgrade:4:deb http://ports.ubuntu.com/ cosmic-security main restricted universe multiverse /etc/apt/sources.list.distUpgrade:7:deb http://ports.ubuntu.com/ cosmic-updates main restricted universe multiverse /etc/apt/sources.list.distUpgrade:10:deb http://ports.ubuntu.com/ cosmic-backports main restricted universe multiverse and lines still with Bionic (otherwise I got errors): $ grep -irn bionic /etc/apt/* | grep -vi "#" /etc/apt/sources.list.d/armbian.list:1:deb http://apt.armbian.com bionic main bionic-utils bionic-desktop /etc/apt/sources.list.d/armbian.list.distUpgrade:1:deb http://apt.armbian.com bionic main bionic-utils bionic-desktop sander@cubox:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.10 Release: 18.10 Codename: cosmic And this is what I wanted to achieve: sander@cubox:~$ openssl version OpenSSL 1.1.1 11 Sep 2018
  2. Superkoning

    Disable X Windows from console

    I don't want X to start (on my Armbian Ubuntu), so in that file, I now have NODM_ENABLED=false ... and X does not start. Great.
  3. OK. Worth a try. I'll report back. Thank you.
  4. On my Cubox, can I upgrade Armbian Bionic to Cosmic? Is that going to work? I'm not using any GUI / HDMI stuff, so that is not relevant for me Reason of my question: I want OpenSSL 1.1.1 (with TLS1.3), which is a part of Cosmic (and not of Bionic).
  5. Superkoning

    Cubox-i: Ethernet not working

    What if you issue ethtool -s eth0 speed 100 duplex full
  6. Superkoning

    Cubox-i: Ethernet not working

    OK ... I've now connected the Cubox directly to my Genexis fiber router (instead of the Chinese GigE switch).
  7. Superkoning

    Cubox-i: Ethernet not working

    This is weird: after a few reboots, I get above 100 Mbps speeds on my Cubox, and ethtool says the interface is at 1000 Mbps. Weird, $ sudo ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Link detected: yes
  8. Superkoning

    Cubox-i: Ethernet not working

    Ah, I found a workaround: root@cubox:~# ethtool -s eth0 speed 100 duplex full root@cubox:~# ... and now I have (Fast) Ethernet. I yet have to find a way to make this permanent. EDIT: I made it permanent based on this instruction: https://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-permanent.html ... changing ETHTOOL="/usr/sbin/ethtool" to ETHTOOL="sbin/ethtool" History shows: sudo nano /etc/init.d/100Mbs sudo chmod +x /etc/init.d/100Mbs sudo update-rc.d 100Mbs defaults sudo /etc/init.d/100Mbs start with in /etc/init.d/100Mbs : #!/bin/sh ETHTOOL="/sbin/ethtool" DEV="eth0" SPEED="100 duplex full" case "$1" in start) echo -n "Setting eth0 speed 100 duplex full..."; $ETHTOOL -s $DEV speed $SPEED; echo " done.";; stop) ;; esac exit 0
  9. Superkoning

    Cubox-i: Ethernet not working

    I installed Armbian_5.59_Cubox-i_Debian_stretch_next_4.14.66 on my Cubox-i. Boots nicely, but ethernet is not working. The ethernet cable/connection is working, because the cable does work via and ethernet-to-usb connector to the same cubox. EDIT: Oh, I must say that ethernet-to-usb is fast etnernet, not GigE /EDIT Dmesg included. Plus dmesg | grep network stuff. Tips how to proceed? root@cubox:~# cat dmesg.cubox.no-eth.txt | grep -i -e eth -e netw [ 0.793426] fec 2188000.ethernet: 2188000.ethernet supply phy not found, using dummy regulator [ 0.806213] fec 2188000.ethernet eth0: registered PHC device 0 [ 10.900568] Atheros 8035 ethernet 2188000.ethernet-1:00: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet-1:00, irq=POLL) [ 10.900651] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.984996] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 13.985019] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready dmesg.cubox.no-eth.txt
  10. Superkoning

    FYI: auto-mount USB-disk with "usbmount"

    $ apt search usbmount Sorting... Done Full Text Search... Done usbmount/xenial,xenial,now 0.0.22 all [installed] automatically mount and unmount USB mass storage devices and sudo apt-get install usbmount HTH
  11. Superkoning

    Quick Review of Rock960 Enterprise Edition AKA Ficus

    Hey tkaiser ... you have a nice parquet floor! And thanks for the review ... it looks like a nice board.
  12. root's crontab: * * * * * /root/green-on-and-off.sh with that script being: for i in `seq 10` do echo 0 > /sys/class/leds/nanopi:green:pwr/brightness sleep 0.2 echo 1 > /sys/class/leds/nanopi:green:pwr/brightness sleep 0.2 done Result: green LED is always on, but flashes off/on 10 times each minute. That's a good sign of life for me.
  13. Wow ... it works! Thank you The blue LED: root@nanopineo2:~# echo 1 > /sys/class/leds/nanopi:blue:status/brightness root@nanopineo2:~# echo 0 > /sys/class/leds/nanopi:blue:status/brightness The green LED root@nanopineo2:~# echo 0 > /sys/class/leds/nanopi:green:pwr/brightness root@nanopineo2:~# echo 1 > /sys/class/leds/nanopi:green:pwr/brightness
  14. OK, thanks, I will try ... as soon as I get my Neo2 back to life ... ;-)
  15. Sometimes it's unclear if my Nanopi NEO2 is still running, or fully locked up / FUBAR. Ping and SSH give no result. As there is no HDMI, I have no way to check if it's still there. So I was thinking: can I let the green LED flash each x seconds as a sign of life? Quote from Igor: "Both are accessible via sysfs, green is configurable while blue is not lit and reacting to anything. ". So a crontab script that writes something to /sys/ <LED> ... ? Feedback appreciated.