All Activity

This stream auto-updates     

  1. Today
  2. Maybe you could bring me on line what problems you experience with the newer kernels? I assume it is the problem that with a bootloader for 1000 MHz you have instabilities? If I´m right then a new bootloader will not help with this. What you can test, commenting out the avs in the dts file, compile a dtb and then test if the kernel is working for you.
  3. That is the reason why we can't update our EspressoBins to kernel 4.19.4x and above anymore without experiencing crashes. Hopefully the new bootloader released by marvell recently will be able to handle the new frequencies in the system.
  4. I haven´t tried an armbian kernel for a while now. I will look into this sometime in the next weeks. But as far as I followed the upstream fix should be in the kernel 4.19.xx. It is just one fix missing regarding a too low voltage, which @sqpr found. I will see if I can point the right people at this patch.
  5. On S905x2 (it's a close platform with S922) eMMC works with this kernel. Perhaps the reason for the settings or is it the result of using a removable connector for the eMMC on the N2. I noticed that if you copy the data in manual parts no more than 500MB, with an intermediate "sync" , everything is copied correctly.
  6. Way back I had such a problem with BIOS, the trick was, divide the HDD into 2 or 3 partitions. Did you try this already?
  7. Did you ever solve this? I may have a similar issue, I've been googling for hours and just found your reply. https://forum.armbian.com/topic/10480-attempted-jessie-to-stretch-failed-likely-dead-on-reboot/
  8. Also this after running apt-get remove --purge network-manager update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but not installed update-initramfs: failed for /boot/initrd.img-3.4.113-sun8i with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (232-25+deb9u11) ... Processing triggers for dbus (1.10.26-0+deb9u1) ... Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1)
  9. One last reply: here's the full output of the 2 main large errors, sorry quite large: Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. invoke-rc.d: initscript network-manager, action "start" failed. ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2019-05-25 15:40:43 AEST; 27ms ago Docs: man:NetworkManager(8) Process: 18510 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=226/NAMESPACE) Main PID: 18510 (code=exited, status=226/NAMESPACE) May 25 15:40:43 orangepizero systemd[1]: Failed to start Network Manager. May 25 15:40:43 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:43 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. dpkg: error processing package network-manager (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but not installed update-initramfs: failed for /boot/initrd.img-3.4.113-sun8i with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: network-manager initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) And this one from journal May 25 15:40:44 orangepizero systemd[18536]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Bad file -- Subject: Process /usr/sbin/NetworkManager could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/sbin/NetworkManager could not be executed and failed. -- -- The error number returned by this process is 9. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Main process exited, code=exited, status=226/NAMESPACE May 25 15:40:44 orangepizero systemd[1]: Failed to start Network Manager. -- Subject: Unit NetworkManager.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has failed. -- -- The result is failed. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. May 25 15:40:44 orangepizero systemd[1]: Stopped Network Manager. -- Subject: Unit NetworkManager.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has finished shutting down. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Start request repeated too quickly. May 25 15:40:44 orangepizero systemd[1]: Failed to start Network Manager. -- Subject: Unit NetworkManager.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has failed. -- -- The result is failed. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. As much as I wish i was a lot smarter and had more time - I will not attempt "takeover.sh" which sounds like a super cool way of rescuing a hosed system. - Complicated and powerful but not something even close to my skillset, super cool though!
  10. Hello! I tried to update jessie dismally, here: https://forum.armbian.com/topic/9984-apt-get-update-pointing-to-404-not-found-ip-151101240204-80/?do=findComment&comment=79685 Since then, I have been attempting to update to strech, I feel like I got close, but it's failed and I strongly suspect, my next reboot will hose it. (I will not reboot it, linux is wondeful!!) I updated my sources.list file to have the following 4 values. deb http://httpredir.debian.org/debian stretch main contrib non-free deb http://httpredir.debian.org/debian stretch-updates main contrib non-free deb http://httpredir.debian.org/debian stretch-backports main contrib non-free deb http://security.debian.org/ stretch/updates main contrib non-free the apt-get update and apt-get upgrade (appear) to be working fine. apt-get dist-upgrade will spit out the following: Errors were encountered while processing: network-manager initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) Upon further investigation I have done the following tips in this post precisely http://forums.debian.net/viewtopic.php?p=122113#p122113 These have failed, it outright refuses to get network-manager on there. Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. journalctl -xe will produce the following: May 25 15:33:28 orangepizero systemd[17220]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Bad file descriptor -- Subject: Process /usr/sbin/NetworkManager could not be executed When I begin to google that information I start reaching even less google hits and possibly even a bug? https://www.google.com/search?rlz=1C1GCEA_enAU767AU767&ei=K9ToXI64A6LYz7sPvr2qwAE&q="NetworkManager.service"+"bad+file+descripor"&oq="NetworkManager.service"+"bad+file+descripor"&gs_l=psy-ab.3..33i160l2.9570.14812..14992...3.0..0.276.4626.0j13j10......0....1..gws-wiz.......0j0i22i30j33i21.bL0kzS4p6yg Finally, when I log in to the system remotely it even says : "ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i" "Kernel was updated, please reboot " However, I feel this is very unwise, until I can be certain that the update and upgrades and clean and autoremove and all the commands to maintain the system at least spit back results indicating success.
  11. Thx mate..this is the right answer on question!
  12. I also would at least consider, a tutorial on how to switch from Jessie to Stretch, assuming this is viable without re-burning an SDcard, I suspect it is.
  13. I do not have that cable, how do I install Armbian in his opi3?
  14. Yesterday
  15. I remember trying to install a usb wifi dongle in the past and while it gave me lots of headaches, i did manage to make it work. It's been a while since i used wifi (it's been a while since i used the SBC too to be honest). Today i decided to power it up at least just to update it. When it was installing kernel related stuff, it gave an error stating it couldn't build the 8192cu module (or something like that), the specific log says scripts/Makefile.build:432: recipe for target '/var/lib/dkms/8192cu/1.10/build/8192cu.o' failed make[1]: *** [/var/lib/dkms/8192cu/1.10/build/8192cu.o] Error 1 Makefile:1368: recipe for target '_module_/var/lib/dkms/8192cu/1.10/build' failed make: *** [_module_/var/lib/dkms/8192cu/1.10/build] Error 2 make: Leaving directory '/usr/src/linux-headers-3.4.113-sun8i' Among a long list of errors. Anyway, i tried using the usb dongle. While it seems to work at first, it has a strange behavior. First of all, now instead of only showing only a wlan1 interface, it also shows a wlxxxxxxxxxxxx one. Sometimes it auto connects to my wifi network on one, sometimes it connects with the other. Another strange thing: When it connects, it gets an ip and i can confirm in my router stats page that it's connected but as soon as i disconnect the lan cable, it looses connection with the router. I have tried most of the things i tried last time i made it work like compiling the rtl8192cu-fixes sources and installing them. I have 8192cu active in modules.conf, lsmod says that 8188eu is also active. I'm a newbie in linux and i already lost 3 hours trying to fix this. What am i missing? is the wlxxxxxxxxxxx supposed to show up? I guess you have all the info you need in the armbianmonitor file, if not, ask away. Thanks in advance. Damn, just noticed i probably posted this in the wrong section [EDIT: Pressed "send" by mistake while still writting)
  16. I had hoped the information might be useful for bisecting which kernel update might be responsible. Is the source of the problem known and fixed, or is the fix being referenced only disabling the 5.85 release? Is it useful for me to search for the older nightlies and narrow it down?
  17. What about ROCK64? Featuring USB3 and GBE. 25$ for the 1GB RAM board.
  18. Do you have a USB-TTL Serial dongle to see what is happening on the debug port header ? My OPi3 is running Armbian since months, and lately 5.1.0 ...
  19. What do you mean ? Is it a DT issue or some things in eMMC driver itself ?
  20. This still works on kernel 4.9. The 5.1 kernel needs patches.
  21. Just to let you know, I've tried this custom "nand-sata-install", and I've faced the "load average > 10", and the install didn't finished, even after 1 hour...
  22. This is/was a limited edition (6pcs, two already broken) gift by TJoe @Code4Sale LLC He made them for Ohio Linux fest:
  23. Well, the soldering attempt did not go that well, more to follow... I received the SATA cable, and the disk is now seen. I'm currently creating a NTFS partition.
  24. I have downloaded the linux distributions from the orangepi.org page and the linux images loaded in microsd with etcher and they work without problem in my orangepi3 but under any distribution of armbian and I do the same procedure with etcher and putting the microsd in my orangepi3 does not load anything there must be another way to load armbian in my orangepi3, sorry for my ignorance
  25. I don't know if I can help to solve this problem, but I can try. I want compile the kernel 5.07 because it's working on orangePi3, an then compile again the last 5.1.3 comparing with previous, in order to found the problem and share here the possible solution. I think that it's only a kernel module that create the bug.
  1. Load more activity