laurentppol

Hi there, I have OPi3 (not B nor LTS), now I got an SSD module ( https://allegro.pl/oferta/dysk-ssd-128gb-msata-6gb-s-13044566959 ), and it does not seem to work (nothing related in lsblk). I am using Armbian 21.02.3). Any ideas? the red LED is on, mechanically looks compatible with socket do I need something to enable this? armbianmonitor -u : http://ix.io/4Bkf

Did as described above. What does it mean "The following packages have been kept back:"?

root@orangepi4:/var/spool/cron/crontabs# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepi4 BOARD_NAME="Orange Pi 4" BOARDFAMILY=rk3399 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=9b04dbfd8 VERSION=22.08.8 LINUXFAMILY=rockchip64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image BRANCH=current root@orangepi4:/var/spool/cron/crontabs# uname -a Linux orangepi4 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 GNU/Linux Yes, upgraded from buster. Upgrade as described here: No, didn't reproduce on fresh install (have no spare uSD).

https://paste.armbian.com/bupucukoca It's me, created other account as I was thinking that lost pwd.

Here is output from systemctl status: root@orangepi4:~# systemctl status lightdm.service | more ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-06-10 06:00:37 CEST; 3h 2mi n ago Docs: man:lightdm(1) Process: 2440 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manage r 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS) Process: 2443 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 2443 (code=exited, status=1/FAILURE) cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Scheduled restart job, re start counter is at 5. cze 10 06:00:37 orangepi4 systemd[1]: Stopped Light Display Manager. cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Start request repeated to o quickly. cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Failed with result 'exit- code'. cze 10 06:00:37 orangepi4 systemd[1]: Failed to start Light Display Manager. cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Triggering OnFailure= dep endencies. root@orangepi4:~# What should I look for? Found this in logs: root@orangepi4:~# tail -50 /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2443 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-slick-greeter.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/11-armbian.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: [LightDM] contains unknown option xserver-allow-tcp [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.04s] DEBUG: Monitoring logind for seats [+0.04s] DEBUG: New seat added from logind: seat0 [+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.04s] DEBUG: Seat seat0: Starting [+0.04s] DEBUG: Seat seat0: Creating greeter session [+0.04s] DEBUG: Seat seat0: Failed to find session configuration slick-greeter [+0.04s] DEBUG: Seat seat0: Failed to create greeter session [+0.04s] DEBUG: Failed to start seat: seat0 root@orangepi4:~# [+0.00s] DEBUG: [LightDM] contains unknown option xserver-allow-tcp or this: [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration There is no [ERROR] only [DEBBUG]. Any ideas?

And for wake-up on LAN ether-wake didn't work.

I can see it fails to start. Will look on this. But now I have another question (want to ask before test: how to wake-up OPi4? ether-wake? As it does not have "power" button. And for lightdm: What does in mean?

Oooops, 5 days and no one has idea?

Hi there, now I have pure bug report: done apt update + apt ugprade, GUI frozen, even no SSH, about an hour later (I was outside my house) (probably) restarted but up to multiuser, no GUI at all. Howeve I CAN log over SSH, sthe issue "startx", but ONLY as ROOT. (much indesired, as ex web browser should never be started as root). I can enable remote X in /etc/X11/xinit/xserverrc , then start remote X session. Also "init 5" attempts to start X, but crashes. How to diagnose and repair? Laurent

I have "plain" OPi4 (not B, nor LTS), after todays update to 5.15.25 #22.02.1 Armbian Buster, network works fine. Didn't tested BT / WiFi / HDMI (during boot) as I don't use then on this box. May test later if someone needs.

Can't enable (using armbian-config) GUI ("desktop") without enabling 'auto-login". If I try to do so, GUI simply doesn't start. OrangePi 4 (not B), Armbian Buster. Which log shoud I look for info / include on forum?

Ok, You want to be "strict": - it IS a bug report: - look at the output of iwconfig! Card is WiFi AC and utility shows 300Mbps! It N, not AC troughtput! Also, I have connected 2 of such cards, and iperf shows ONLY <150Mbps! Both on USB3. 2m apart. I want to do some investigation, but question in subject remains also.

Pls move BACK, just provided armbianmonitor -u output!. And my question is NOT a bug report, "3rd party HW" WORKS, but I have some questions. And help choosing right driver on x86_64 PC.

OrangePi 4, Question in subject as I found at least 3: - https://github.com/morrownr/88x2bu - https://github.com/fastoe/RTL8812BU - # REALTEK RTL88x2B USB Linux Driver **Current Driver Version**: 5.13.1 **Support Kernel**: 2.6.24 ~ 5.17 (with unofficial patches) (forgot URL). On Armbian system "automagically" configures card after inserting, can configure as AP, only iwconfig shows as follow: wlxb44bd62f536b IEEE 802.11bgn ESSID:"ARMBIAN" Nickname:"<WIFI@REALTEK>" Mode:Master Frequency:5.2 GHz Access Point: B4:4B:D6:2F:53:6B Bit Rate:300 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=1/100 Signal level=1/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 No mention of A / AC. root@orangepi4:~# lsmod | grep 88 88x2bu 2506752 0 Driver (both Realtek and "morrownr") on x86_64 is much bigger - 3MB+. root@orangepi4:~# armbianmonitor -u System diagnosis information will now be uploaded to no results to fetchPlease post the URL in the forum where you've been asked for. root@orangepi4:~# armbianmonitor -u System diagnosis information will now be uploaded to curl: (52) Empty reply from server Please post the URL in the forum where you've been asked for. root@orangepi4:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/3RPY Please post the URL in the forum where you've been asked for.

Hi there, Xunlong seller says max size of uSD is 32GB. But I have seen thread posts that mention 128GB. So my question is: what is the max uSD card size with RK3399?

Hi there, I have searched a bit, but didn't found HOW (step by step) make my OPi4 (with Armbian installed) an BitCoin factory. Looks it is a quite good candidate, 6 cores (2 BIG), GPU (I know, this is not Nvidia ;p). For the moment not busy doing anything. Could someone provide some kind of HOWTO on topic? (google reports small number of BC diggers for Linux). I have found some howto and (for ARMHF, not 64) binaries to make Linux machine "full" node of BC network, but not on digging BC.

Looks there is a problem with one of my routers, not OPi3... Small change in routing scheme and I get WWW from IP Webcam on phone.

Ooops, not so fast: httping works (to telephone, Android does not respond to ping), but using browser I get to.... OPi3 HTTP server, NOT phone. iptables are just clear. How to solve this? root@orangepi3:~# iptables-save | more root@orangepi3:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.60 0.0.0.0 UG 100 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0 192.168.10.0 192.168.1.30 255.255.255.0 UG 100 0 0 eth0 192.168.15.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0

Storage - external USB->SATA HDD, 320GB, about 2GB/24h @ 1fps, software: motion, set to permanently record at 1fps from IP Webcam on old Android phone (Xperia L), image set 1280x1024. Plus cron replica to remote storage every 10min (WiFi link). Separate WiFi network (different channel from other apps for performance reasons, this is why I have set up OPi3 as AP and want routing). Satisfaction level: very high :). lanefu: THX very much.

Hi there, I have an OPi3 box that acts as home surveillance server. It has WiFi configured as AP, client is Android phone with static IP/routing and IP Camera software. Problem is, that there is NO IP routing. I CAN access video / pictures from phone on OPi box, but NOT from my LAN. Below is routing table and iptables. Looks ok but not working. I am able to access (from LAN) WiFi IP of OPi. Also can access video served by "motion" software on OPi. But no direct connection to Android phone. root@orangepi3:/tmp# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.60 0.0.0.0 UG 100 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0 192.168.10.0 192.168.1.30 255.255.255.0 UG 100 0 0 eth0 192.168.15.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 root@orangepi3:/tmp# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Laurent

Ok, found solution: - restarted from scratch (*.img file -> uSD), - connected "real HDMI" (some overscan) TV, keyboard, - gone trough initial config (root passwd, "normal" user), - configured WiFi (had no wired Eth at my neighbour) using nmtui, - now SSH works in both directions. So conclusion is: the problem was / is (still no video on VGA) with cheap HDMI->VGA converter.

Logged as root using HDMI TV / usb keyboard, changed password, but stuck at new user creation stage, as there are too restrictive rules for password (used CRTL-C). Then useradd / passwd. Now I still get "connection reset by xx.xx.xx.xx port 22. 1). How to login on device by net?, 2). How to resume initial Armbian setup process once logged? on my other PIs I had no problem with this initial setup and got to GUI w/o problem.

Will do later on (as HDMI display is at my neighbour). What (if?) is the default root password? Blank?

OK, got it connected to "real HDMI", see attached picture. Looks it is starting, NMAP shows SSH port open (the only), but system refuses SSH connection (as no root password has been set?) ssh root@192.168.1.153 Connection reset by 192.168.1.153 port 22 What should I do next? Connect to console or there is another (easier) way? Red LED is solid, Green flashes fast 2 times, then some space, and again.

Thanks for claryfying, tomorrow will try "live" HDMI display, if not OK will connect serial (THX for speed indication) :)