• Content Count

  • Joined

  • Last visited

About meetyg

  • Rank

Recent Profile Visitors

353 profile views
  1. Good news! It seems that after the change mentioned above, the network has been fairly stable. I don't know why at first there were some connectivity pauses, but after it hasn't happened since then, and seems stable! Thanks!
  2. I'm having similar problems. I tried the suggested temporary solution. At first I thought that it didn't change anything, because I lost connectivity again. But after a few hours the ethernet connection came back (which never happened before, when ethernet was lost, the only solution was to pull the power plug and restart it). It seems like after the boot.cmd change, ehternet connection is randomly gowing up and down. Is there any news on this? Any ideas?
  3. OK, so maybe its a wierd combination of hardware/software incompatibilities. I can live with slowness I get now, since its much faster than when I first started. I will try to play with network setup to see if I can improve something. I really dont want to run FAs kernel just tried it to compare, to see if its a HW or OS problem. Thats why I'm here asking for help. Thanks for now! I will update here if I find a solution, for knowledge.
  4. OK, so here are my findings: I was able to use a previous version of Armbian. Then I went back to the newer version and it worked! But, there is a difference: Last time, I did all the connection to NanoPi using a Windows laptop, directly connected to the NanoPi. This tine I was using an older Linux netbook, also directly connected to the NanoPi (ethernet cable). I am suspecting this has has to do with the ethernet speed, as my older Netbook has a slower 100mbps NIC, and my laptop has a 1000mbps NIC. I then connected it again to my newer laptop and the sluggish response was back. So I played a bit with the NIC speed, and as I lowered it, the responsiveness was better, but still not perfect. Lastly, I connected it to my 1000mbps switch, and while it is usuable, it is sluggish to respond: For example, when running ´htop´ on an idle system, the uptime sometime freezes, jumping 2-5 seconds. As I mentioned before, all this behaviour didn't happen with other images I tried. I suspect that maybe there is a wrong configuration of NIC on Armbian (at least on last version, I haven't had the time to go back again to earlier version and test it again connected to the switch). Maybe it has to do with tx offloading like I read some other board have problems with? Armbian monitor logs are here: BTW: The memory chips are NOT from the problematic numbers. Thanks for your help!
  5. Thanks for your reply. I will try an older version, and check the memory chip numbers. The SD card is the same one I used for Dietpi, so I don't think its the problem. I installed Dietpi before Armbian, then tried Armbian (because lack of Docker support in Dietpi/FriendlyElec kernel). Then when I saw that Armbian was stuck/slow, I reinstalled Dietpi just to check. All this wad done on the same Sd card, and currently Dietpi is running fine on it. I'm not sure I will be able to run Armbianmonitor on the Nanopi with latest version. Its simply to slow to do anything (as if it were underclocked to 1 hz or something). Every keystroke in SSH takes a few seconds to show up. I'll update after flashing...
  6. Hi there! I recently installed Armbian (Stretch: Armbian_5.83_Nanopifire3_Debian_stretch_next_4.14.115) on my new NanoPi Fire3. I was able to boot, but it responds so slow, that it is unusable! For example, when I SSH into it, it takes a log time to show me the login prompt. When I enter the username and press enter, it takes about 5 seconds to ask me for password. When I enter password, it takes about 10 seconds to show me the Armbian banner. I wasn't even able to go past the changing of unix password on first login, because it just "froze". I have installed the image twice on my SD card, just to make sure it isn't a corrupted install. I'm using a good PSU, and a good quality Samsung EVO 32GB sd card. I have tried installing DietPi, and FriendlyElec's 64 bit xenial image, without problems! This behavior happens only with Armbian. I want to use Armbian because I understood that it supports Docker on the Fire3 (is this true?) I haven't tried the Ubuntu version of Armbian, since it has Desktop, and I'm looking for a headless OS. BTW, is the Armbian Stretch image for the NanoPi 64 bit? Thank you guys for the excellent work!
  7. Hi, I found this: ,I guess this is what I needed. Seems a bit complicated, I think I will work a bit without the SATA drive, to see if it worth the effort (Armbian is great, I'm just not sure its the best image for my needs). If I'll get to it, I'll update here if I was successful or not.
  8. OK... Do you have any HowTo that explains this how to compile and then load u-boot on the SD ? I'm sorry for the ignorance, but I'm a bit of a newbie
  9. Thank you Wolf, but as I said the problem seems to be software related, specifically with the newer kernel.
  10. Hello, First I would like to thank Igor for his amazing work on Armbian! I know that the Lamobo/BPI R1 is very problematic with power and SATA, but when I installed Armbian 5.1 jessie with the legacy kernel, it seems that the SATA is working fine. But when I tried the same Armbian 5.1 with vanilla kernel it wasn't able to boot and the hard drive made knocking noises. Just to make sure, I disconnected the HD and it booted fine. I think that this is a software problem (maybe uboot?) because as I mentioned it works with the older kernel. I tried installing the uboot package bananapro-next as Igor adviced someone with a banana pro but it didn't help. I'm using a good 2A power adapter and a quality cable so I guess that solves the hardware side of the problem. I would really like to have the newer kernel with Docker support because I want to be able to run Docker containers. Any ideas about the software side? Thank in advance.