Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Hmm thats weird according to windows drivers it doesnt. Then ill try anyway when i have time I also borrowed a fancy one from the electrical engineering faculty. Ill pick it up thursday.
  2. Okay lets do this thing. I found 2 candidates. The red one sais: EFTDI 1730-C E5339001 FT232RL the black one sais: SILLABS CP2102 DCL00X 1612+ Ill try the black one
  3. So i will no do the following, correct ? After reflash: sudo nano /etc/armbianEnv.txt --> set verbority to 7 sudo apt-get update && sudo apt-get upgrade armbianmonitor -u --> Garther results sudo reboot (and then it crashes) That’s it ? But then the log crash info isn’t logged ? How do i log the serial output ? I do have an USB to TTL converter. (sorry for the noobish question, im trying my best)
  4. I am willing to help i’m however a mechanical engineer not a computer science professional. Problem is, if i run an upgrade after the flashing is complete my rockpi 4b will perform an upgrade but when i reboot the system crashes. I wont even see a booting output over hdmi. I just plug in the power and nothing. So will i be able to even log the error ? I can of course remove the emmc module and mount it and grab an errors file, is that what you are pointing towards me doing ? If so, can you make a complete noob proof description? I’m happy to help you all out here on the forum.
  5. Its my own backup image of the EMMc module using dd. It’s a Ubuntu beaver image with all my software and configurations on it. So since its my own tailored image i don’t think its useful to paste the name here Does disableing kernel upgrade even fix the problem? Or does it for example stop the update of uboot? I was hoping the following would fix my issues: sudo apt-mark hold linux-image-generic linux-headers-generic
  6. The image was from 2 april 2020, so it was the latest kernel version from that date. I’m reflashing now, ill post the kernel version after i can access my system again.
  7. Hi there, I’ve reflashed my armbian board and ran an upgrade, boot failed to boot again. I will skip upgrading the kernel until this is fixed. I was wondering, is there a way i can update to kernel version 5.7.14 ? Ive checked armbian config, but the kernel selection module is empty. thank you.
  8. I think im experiencing this exact same problem. I was running armbian Ubuntu in my RockPi 4b on a 128 gb emmc module. I logged in over ssh and got the message ‘kernel updated please reboot’ I rebooted and nothing. Not even a flashing red light. No video output. Unfortunatley im unable to make big changes to the board now, my house is being renovated and i cant reach my computer stuff. Is there maybe a way i can select an old kernel without booting in the system ? Maybe mounting the emmc on a computer and manually editing the grub file ? I’m very sad Last complete system backup using dd was in april.
  9. My rockpi 4 board also got f*cked. booting from emmc. dammit.
  10. MEMEs


    hi there, I just rebooted my rockpi 4b after a kernel update (i run armbian on emmc). i think this updated really f*cked up the rockpi. board wont turn on, no output to screen, only green light turns on, have not seen the red light blink since. i'm pretty sad about this. Can't supply any more information for obvious reasons..... time to buy a asus pn50 and just run regular ubuntu. I'm done with SBC with weird hardware.
  11. Fixed it! Apperantly it's an xrdp bug... This solved my problems : Raspberry pi
  12. Ive been doing some digging and it seems that the xRDP service is failed after a reboot: sudo systemctl status xrdp.service ● xrdp.service - xrdp daemon Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2020-01-02 19:13:28 CET; 44s ago Docs: man:xrdp(8) man:xrdp.ini(5) Process: 4517 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=1/FAILURE) Process: 4509 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, status=0/SUCCESS) Jan 02 19:13:28 rock systemd[1]: Starting xrdp daemon... Jan 02 19:13:28 rock systemd[1]: xrdp.service: Control process exited, code=exited status=1 Jan 02 19:13:28 rock systemd[1]: xrdp.service: Failed with result 'exit-code'. Jan 02 19:13:28 rock systemd[1]: Failed to start xrdp daemon. Some googling around revealed that this could be a recent bug in xRDP, more people have been reporting the behavior in the past months: Got xrdp Starting xrdp yields the following output, even after stopping the service first: sudo systemctl start xrdp.service Job for xrdp.service failed because the control process exited with error code. See "systemctl status xrdp.service" and "journalctl -xe" for details. Journal to log has no info from xrdp, just some login fail from OpenVPN i need to fix.
  13. Edit: Nevermind the unknown state seems to be normal.... I think there is something wrong with my local host, it’s states as unknown: ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 0e:24:d9:ea:96:09 brd ff:ff:ff:ff:ff:ff inet brd scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 2001:980:cd62:1:cc7d:c076:afd7:4863/64 scope global temporary dynamic valid_lft 3723sec preferred_lft 3226sec inet6 2001:980:cd62:1:adbf:9afd:ce2e:f8bd/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3723sec preferred_lft 3226sec inet6 fe80::3935:53f9:bb77:cddc/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6c:21:a2:37:91:7e brd ff:ff:ff:ff:ff:ff Should that be a source of the problem ?
  14. Hi there, First of all, have a nice christmas. Especially you Igor, im still amazed by what armbian is. I'd like to ask a question regarding a problem i'm having. Last two days i've been setting up my rockpi 4 as a replacement server. I had everything configured correctly and working. I left the rock on over night and discovered this morning that i couldn' t connect over SSH and vnc/rdp anymore. Since i couldn't connect and the rock was headless i pulled the power an forced a reboot. After the reboot i could connect to ssh but not over rdp or vnc. My app jump desktop gives the following error: Could not create SSH tunnel. Please make sure tcp forwarding is enabled on the server. Details: Chanel open failure (connection failed). The weird thing is, i have not changed anything since the last time, it just doesn't work anymore now so i dont know where to look to solve the issue. I have the following settings: address: (port is forwared in the router and open in ufw) ssh tunnel: username@ip_address with private key (also tried username@local ip with key. no effect) (ssh is working so the keys or the adresses should not be the problem, tried the exact same keys and both ip as local ip for ssh) My sshd_config file is in the attatchment. note that i have set allowtcp forwarding to 'yes' as was requested in the error log of jump desktop. I've also tried re-enabling rdp in armbian-config no effect I've also tried running vncserver mp effect I've hooked up the system to a monitor and it just normally boots to desktop as expected. Does anyone have some tips where i should start looking for this problem ? I have a hard time doing this since it happened without me interfering. Thank you in advance. sshd.txt
  • Create New...