tricolery

Yeah... looks like network manager was the culprit. I just disabled it and no problems anymore. https://wiki.debian.org/NetworkManager

Hello everyone. I'm experiencing some strange issue with my cubieboard and its connection to the internet. I boot it up and it works correctly, but after a day or two, I can't communicate with it using a ssh program, or vnc viewer. My other two servers that uses Linux Mint is working normally, so I think the problem is not my router. (I even swapped the Ethernet cables between my servers). If I connect a display on my cubieboard and try to ping my Windows computer, then I'm able to ssh my cubieboard using my computer. Sometimes I'm unable to connect to my cubieboard via ssh using my windows and my Android phone, but if I try using my Linux machine, I can connect with ssh with no problems. I thought I was facing that issue with memory clock an my cubieboard was turning off again, but when I connected a display on it, I found out that it was working ( and I was able to use the internet on it, so it still had a connection to the internet, but my three oder computers could not connect to it. Did someone experienced an issue like this one? Sent from my SM-G930F using Tapatalk

Its on my second post of this thread. As I told you, you need any woking uboot just to boot the cubie board and roll back the uboot to 2.53 using your package manager. If you want especificaly the uboot 5.23, you will need to compile it.

Its very easy, dude. 1. You will need a linux machine. (Don't know if it is possible to do it in windows). If you cant install linux on your PC, just try a live version with a pendrive on your PC or you can even flash lubuntu or cubian on your cubieboard NAND. 2. Insert your SD card on the machine you are using. 3. Discover de drive name linux has assigned to you SD card. (A veeery easy way to do it without any code, is to access /dev/ with your linux distro file manager, select all the devices there and leave it selected. Then you insert the memory card on your computer. The files that appeared and is not selected, is your memory card. As a example, mine appeared sdd and sdd1. I applied the uboot on sdd with out th "1". Other way you can do it is typing "lsblk" on your terminal and from the output of that command, find your SD card drive name. 4. Download and extract the uboot. Extract it at any place. (With a simple name to asure we dont have any trouble here) 5. Use the comand sudo dd if=/path_to_your_u-boot/u-boot-sunxi-with-spl.bin of=/dev/your_sdcard_drive_name bs=1024 seek=8 (use sudo for this command even on a live distro. The output of this command should be something like xxxxx bytes writen) 6. Try boot the cubieboard 7. Force version 5.23 of uboot to be installed. If you dont know how to do it with bash, install synapitc (It's apt-get with a UI). (If I remember well, synapitc is not installed on igor image) Brotips: If you use a nand image on cubieboard to fix SD Card, your sd card drive name should be something like mmcblk0. On your PC, most of the linux distros will usualy mount your sdcard as sdx, for x a letter from a to z. If you dont know what linux you can use on your PC, you can use Mint, a very lightweight and easy to use distro. Just go with the 32-bit version(It can use more than 4GB of RAM, but that's another story). Burn a disk with it or search how to use it on a pendrive.

Don't worry. Its just a U-Boot problem. Flash the u-boot from this link to bring it back to life Wake me up inside and roll back to U-boot 5.23.

Yes, this is happening with my cubieboard 2 too.

Yes, I tested it this weekend. With 456 MHz, the test fails after 4 hours running. I used Lima-memtester.

I'm using this repository: https://github.com/linux-sunxi/u-boot-sunxi Its the only one I managed to work on my cubie. Is it dangerous to run MBUS 400 MHz @ 1300 mV? Can this cause any damage on the board? Also, it looks like I dont understand what is mainline. Could you please explain to me? I read mainline many times here, but I dont know if they are all the same thing. I will test this on the weekend. This week I have some tests at university and I will be very busy. I will only need to test 456, since 432 and 480 have already been tested.

I think Igor took care of it: [ 1.529300] axp20_ldo1: 1300 mV [ 1.534695] usb 2-1: new high-speed USB device number 2 using sw-ehci [ 1.539955] axp20_ldo2: 1800 <--> 3300 mV at 3000 mV [ 1.545230] axp20_ldo3: 700 <--> 3500 mV at 2800 mV [ 1.550356] axp20_ldo4: 1250 <--> 3300 mV at 2800 mV [ 1.555716] axp20_buck2: 700 <--> 2275 mV at 1450 mV [ 1.571542] axp20_buck3: 700 <--> 3500 mV at 1300 mV [ 1.576398] axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV I used the mainline U-Boot to make my U-Boot. The only thing I changed was DRAM speed to 432 MHz. I wonder why MBUS is working at 400 MHz.

It's a SK Hynix chip H5TQ4G63AFR-PBC Above it is a i2c rtc module I use to sync the time. And here is the output of a10-meminfo (improved version): And here is the output of tinymembrench:

I will verify the DRAM chip when I arrive home today. When I used Cubian, there was an update that increased a voltage due to some stability issues. See: http://cubian.org/2014/07/05/resolve-stability-issue-on-cb2/ Maybe is the same issue we are facing here? I never had this problem with Cubian nor changed the u-boot. When I arrive home, I will test Cubian with tinymembench so we can check at what speed and voltages Cubian is running. Edit: I found this: https://github.com/maxnet/a10-meminfo Looks like it can dump DRAM settings and also works on a20 boards. (Found it re-reading the links linked to the link I posted above.)

30 hours running lima-memtester and it survived. No memory errors. That companion cube was making me dizzy already. I think 432 MHz is pretty stable for CB2. Just reminding that when it was 480 MHz, it couldn't hold memtester for more than 1 hour.

I'm using just memtester, because when I use lima-memtester I get the error: Please remove 'sunxi_no_mali_mem_reserve' option from your kernel command line. Otherwise the mali kernel driver may be non-functional and actually knock down your system with some old linux-sunxi kernels. Aborted The kernel I use is the one at armbian repository (5.20). I did not change the kernel. Strange, because I'm not using a CLI image. There should be memory reservation for GPU, right? For the benchmark I'm using: stress -c 2 memtester 100M openssl speed -multi 5 I will leave it running for today. Edit: It turns out that my boot.src had Mali memory reservation disabled. I dont know why tough. Running lima-memtester now. Tomorrow I'll come back and report.

I can confirm that 432MHz is stable for Cubieboard 2. My cubieboard 2 is doing a stress test now and it's stable. The test is already running for 5 hours and I will leave it running for today. When it was 480 MHz, the stress test failed in 1 hour. I used 432 MHz instead of 384 MHz because of this topic: https://groups.google.com/forum/#!topic/cubieboard/9WMBFAL7JBE I will upload my u-boot here if anyone is interested. u-boot-sunxi-(432MHz).zip

I'm cloning the u-boot-source from https://github.com/linux-sunxi/u-boot-sunxi(sunxi branch) and I have no Idea where I need to change the clock value. Tried to read the documentation, but without success. Could anyone help me? Thank you!

What file do I change the DRAM speed? I will test 384MHz on my cubieboard 2 too. I know how to compile U-Boot.

I have this same exact problem with cubieboard 2. The HDD that it's connected on its usb still spinning, the lan port leds are blinking and the red led from pmu is lit up, but the other two leds are turned off and I have no response from it. Tried to connect a monitor and a keybord but it did not work. This error occurs once/twice a week.

The board did not boot after compiling uboot either from Igor source and phelum source. I solved it by downgrading uboot to version 5.00 in synaptic package manager. Edit: Nope. Problem still here even with 5.0. Almost giving up

Thank you Igor! I'll try to compile it today. I will try to use the cubieboard to compile it too, since I also don't have linux on my computer like zeppa. I just need to add the line you mentioned anywhere at configs/Cubieboard_defconfig file.

Hello! I have a cubieboard 2 and I have the same problem. If I remove the 5VDC cable and wait a little while after inserting it again, my cubieboard 2 shutdown at starting kernel message. If I insert my cubianX sdcard, boot, shutdown the cubieboard2, remove the cubianX sdcard and insert armbian sdcard, my cubieboard2 boots normaly. I tried to use Phelum U-boot, but without success. Can anyone help me? Edit: I'm also using legacy kernel.