Christos

Members
  • Content count

    284
  • Joined

  • Last visited

About Christos

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

754 profile views
  1. Christos

    Which method to setup WiFi hotspot on OPiPC?

    Ok, thanks @Igor Are there any recommended dongles for legacy 3.4.113 ? Any that tested/work ok?
  2. Christos

    Which method to setup WiFi hotspot on OPiPC?

    Thanks @WarHawk_AVG Unfortunately could not setup a hotspot in OPiPC using the armbian-config. Tried to use various usb/wifi dongles and with none that I used got any results. Also, I bought one of the specified in the download page as supported, the Comfast with RTL8811AU chipset. OPiPC runnning latest 5.51 Debian (8) legacy kernel 3.4.113 simply does not even recognizes it for use as client. Not creating the wlan0 device at all. ___ ____ _ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___| _ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | _| |_ | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ |_ _| \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____| |_| |___/ Welcome to ARMBIAN 5.51 user-built Debian GNU/Linux 8 (jessie) 3.4.113-rt143-sun8i System load: 0.00 0.03 0.05 Up time: 22 min Memory usage: 16 % of 997MB IP: 192.168.1.70 CPU temp: 51°C Usage of /: 11% of 15G dmesg [ 826.660215] ehci_irq: highspeed device connect [ 826.910179] usb 4-1: new high-speed USB device number 5 using sunxi-ehci [ 827.062370] usb 4-1: New USB device found, idVendor=0bda, idProduct=a811 [ 827.062406] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 827.062437] usb 4-1: Product: 802.11ac WLAN Adapter [ 827.062460] usb 4-1: Manufacturer: Realtek [ 827.062483] usb 4-1: SerialNumber: 00e04c000001 root@orangepipcplus:~# ifconfig eth0 Link encap:Ethernet HWaddr e2:bd:ab:0f:e9:b7 inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2a02:582:d0e:e00:e0bd:abff:fe0f:e9b7/64 Scope:Global inet6 addr: fe80::e0bd:abff:fe0f:e9b7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:567 errors:0 dropped:0 overruns:0 frame:0 TX packets:855 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45453 (44.3 KiB) TX bytes:138041 (134.8 KiB) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@orangepipcplus:~# @Igor @zador.blood.stained So, am I missing something? Do I need to do something in order for the device to be identified? Is the download page with supported/tested interfaces valid ? https://www.armbian.com/orange-pi-pc/ Can I use the Comfast RTL8811AU dongle?
  3. Hi, Got Debian (8) legacy 3.4.113 server/console and would like to setup a WiFi hotspot. (latest Armbian build 5.51) Seen two methods in Armbian docs 1. -> https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-set-wireless-access-point and via armbian_config in https://docs.armbian.com/User-Guide_Armbian-Config/ 2. -> https://www.youtube.com/watch?v=__BJtInOQFY So I'm a bit buffled about it. Got some questions Got a RTL8188CUS is it suported nowadays? or should I get a specific other one? Do I need to have internet/ethernet/lan connection active during the hotspot creation via armbian_config? After I execute the armbian config method, there are a few screens as in the video, probing various methods, and then the system without reporting any error returns to its menu selection but do not show the "Manage..access point". After that what do I need to do have the WiFi hotspot up? How can I give it the required parameters eg ip, passphrase key for users to connect, SSID etc, is there any guide for it ? PS. Also tried with a OPiPCPlus that has onboard wlan and armbian config result is the same, did not give the "Manage .. access point" menu after run. It also not support WiFi access point creation?
  4. Christos

    Unattended upgrades, how to stop them?

    @Igor @guidol Ooops, in the latest 5.51 it looks we cannot remove only unattended-upgrades, if doing so we also lose the most useful armbian-config amongst others (armbian-config python3-software-properties software-properties-common) So, we cannot remove only unattended-upgrades? If so, if we set to "0" all options in 02-armbian-periodic, is it the same and no unattended upgrade will ever happen? ___ ____ _ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___| | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____| |___/ Welcome to ARMBIAN 5.51 user-built Debian GNU/Linux 8 (jessie) 3.4.113-rt143-sun8i System load: 0.67 0.18 0.06 Up time: 0 min Memory usage: 6 % of 997MB IP: 192.168.1.42 CPU temp: 52°C Usage of /: 24% of 3.6G Last login: Tue Jul 3 13:48:59 2018 root@pisdr:~# apt-get remove unattended-upgrades Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: armbian-config python3-software-properties software-properties-common unattended-upgrades 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 721 kB disk space will be freed. Do you want to continue? [Y/n]
  5. Christos

    Unattended upgrades, how to stop them?

    @guidol Thanks for the links, already did that though and seen that there is a bit of difference in armbian, there are two files in armbian for periodic config (02periodic and 02-periodic) and since I know that some services might need to always be present (for any reason) in armbian, so I asked the question. The question is actually, can I totally remove the unnatended upgrades package in armbian? or what is the best method in armbian for unattended upgrades Not to run? PS. Using Xenial, legacy
  6. Hi, Need to have unattended upgrades stopped and not run uppon every boot. What is the best way to do this?
  7. Thanks @Arglebargle for the hint According to wiki "zram was introduced into the mainline Linux kernel in version 3.14" -> https://en.wikipedia.org/wiki/Zram I would be really interested to see if by reverting this and not including it in a new version, things could come back to normal for the supported legacy.
  8. If you use a 16GB card it is normal/ok as I tested here, the problems start to happen when using 8GB and are evident mainly in 4GB cards. Thanks for the hint in zram config, I'll try to tweak and see the results.
  9. @Igor I'll test if this could solve the issue. Though, if you read my first post, I started having the issue before the ZRAM (3 *) adjustment, it was there from 5.49, the ZRAM adjustment came after 5.50 bump so I'm not so sure that it could fix things entirely. I'll perform the tests by having another build now and report back.
  10. @Igor (lol about recent github acquiring..) The 8GB cards are brand new, bought them yesterday just to test and it shows that dhclient in Xenial has problems even with them. When I flash the same 4GB with the old xenial image (5.46) it works just fine! (and as I said etcher verification reports no issues) So, although it also crossed my mind that the cards gone bad, it looks that they are ok and something else might lurks underneath in the latest versions..
  11. @Igor @zador.blood.stained I am a bit buffled. Latest image that I created and works correctly with IPv4 network addressing was (did not test/build after that until now) Armbian_5.46_Orangepipc_Ubuntu_xenial_default on 11/Jun I use a 4GB Class10 microSD for all my test builds so far. Two scenarios are done, a plain client by getting IPv4 addressing and a DHCP server setup with isc-dhcp-server. Now the 5.50 image is built from repo for up/and to commit "Adjusted ZRAM implementation" ( 46d754f909980c37cb56533a5a0b0874f2719480 ) Tested the Xenial console with 3 microSD cards, sizes 4, 8, 16GB all Class10 (same brand). All flashed and verified with Etcher and boot/start ok otherwise. 1. Ethernet client networking/addressing does not work with a 4 GB SD card. 2. Ethernet client with many reboot attempts it occasionally/sometimes works (most of the times though not), with 8 GB SD card, 3. Ethernet client does work always with 16GB SD card. With 4GB it shows 20% space utilization, with 8GB, 10% space utilization so obviously space is not directly related but for some reason card size does play a role.. Did also the same test with Debian Jessie legacy console build 1. Ethernet client networking/addressing works ok but DHCP server does not work with a 4 GB SD card. 2. Ethernet client and DHCP server work ok with 8 GB SD card, 3. Ethernet client and DHCP server work ok with 16GB SD card. Dont know if those tests have any meaning at all, but I am buffled as I said. It looks that there might be problems in 4GB or 8GB cards in Ubuntu and in 4GB in Debian, that is one thing that I understand in the latest Armbian versions. So, is there any rule on microSD card size for Armbian? Is there something else that somehow is broken (new ZRam maybe?) and gives that effect on network IPv4 addressing? Is it me that I'm missing something?
  12. A day later also tested the 5.50, same OPi PC legacy, Ubuntu server/console image build. Same problem, no IPv4 addressing problem. @Igor @zador.blood.stained Is there anything I miss or build has a broken networking config in the latest (5.49, 5.50) versions?
  13. Hi, Just did a fresh 5.49 build, OPi PC, legacy, Ubuntu console/server. Ethernet network is not working (out of the box) It does not get an IPv4 address automatically Tried to and got it enabled via nmtui, it was showing an 'eth0' as activated and a 'Wired connection 1' as deactivated. I activated the wired connection1, it automatically removed the eth0 from the list and then it has taken an IP address. Did a reboot, though after reboot it was again not working, it did not retained settings. NMTUI show again eth0 as activated and 'wired connection' as deactivated. And no IP address is given to the board. So, am I missing something? PS. with 5.49 legacy, Debian console/server, IPv4 works ok out of the box.