Jump to content

IcerJo

Members
  • Posts

    22
  • Joined

Posts posted by IcerJo

  1. On 3/6/2022 at 6:11 AM, bunducafe said:

    Since 4 weeks now I am runnign the helios64 together with OpenMediavault 6 with the full CPU capacity and ondemand governor.

    Before I had always problems when doing an scheduled task but with OMV6 the problem seems to be solved. I am quite pleased now with the performance and a rocksolid NAS.

     

    Mind if I ask which kernel are you using? and did you experience any problems adding any addon's? I had no problems with a fresh install of Bullseye on my Helios4 but had issues when I tried adding snapraid and mergerfs on my Helios64 with the stock Bullseye Kernel.

     

    Also Experiencing a freeze/issue When installing OMV through armbian-config where it freezes at the end while processing triggers for man-db

  2. Hi,
     
    Seem stable after one year of multiple testing with this settings:
    - Last Kernel Linux 5.10.63-rockchip64 but in logs i have a regulator voltage error.. (with Linux 5.10.43-rockchip64, not this issue..)
    - Max/Min CPU Freq 1,2GHz & Governor to Performance (advise here and i think it the best advise i never see... https://wiki.debian.org/InstallingDebianOn/Kobol/Helios64)
     
    With another setting like this it's simple:
    - Totaly instable randomly: Kernel Panic, lost network Freeze... (with docker container, ramdomly crash is daily...)
     
    After many reading, i think Rockchip and Linux Kernel have a big problem with Governor and CPU Frequency Management
     
    I am not a Guru and maybe i write bigs errors or sh..
     
    Have a good day
    I have my CPU set to scale from the lowest number and 1.4 for the high-end, and performance set to on demand and have no problems, anything above 1.4 and it crashes within days.

    Sent from my Pixel 4a (5G) using Tapatalk

  3. Thank you @Igor, my apologies and thank you for all you and the team do. I plan to donate to Armbian when some of my remodeling projects are done.

    and That would be swell @Heisath, I did see in the FAQ's that we may not be "supported" Officially but we are in a Community type of support, so if you were able to acquire and run Edge/Nightly that would definitely help out in the long run :)

  4. I see you updated your Device, there is a known issue with the kernel in question, there is another thread that details how you can revert back to the old .43 kernel to regain access. If you look  the following post/instructions you should be good to go. 

     I'm curious  as to why no one referred you to that post. I know the title of the Thread is about upgrading to Bullseye but it also got sidetracked to troubleshooting Armbian 21.08.1 and the EMMC read only error/problem.

  5. On 8/31/2021 at 6:24 AM, IcerJo said:

    Thanks, I guess I'll stick with what works/caused me to be stable for this long emoji16.png

     

    Edit: I opted to start fresh and am testing the stability of the new kernel's Govenor and cpu frequencies via SD Card till they fix the EMMC issue's which then at that time i will push Armbian back to the EMMC.
    So far 22 hours with no problems.
    Sent from my Pixel 4a (5G) using Tapatalk
     

    Just after 24hours system randomly rebooted while i was out of the house, so back to the old trick of setting the max to 1.4ghz and min to 408mhz

  6. I opted to just setup an SD Card with the latest, and redo my OMV install on it, since that's technically all I use it for at this time, I was able to get the old system booted with no problems by pushing re-pushing the bootloader but wasn't able to install the Deb files, and I am not that confident in my linux skill set, though i learned a few new tips and tricks during the troubleshooting! I'll repush to EMMC once issues have eventually been resolved, or i may downgrade the kernel and push, i'll see later.

     

    Thank you @ebin-dev for your advice and assistance and thank you @TDCroPower for the RSync article!

  7. 46 minutes ago, TDCroPower said:

    I don't have a clean backup of the eMMC unfortunately, will probably have to introduce in the future to have a backup for such a step.

    I found the following tutorial to clone the system from the emmc to a connected media....
    https://averagelinuxuser.com/backup-and-restore-your-linux-system-with-rsync/

    After that I would have to somehow downgrade my emmc backup on the media?
    Does anyone have a tip which files have to be replaced?

    After that I should clone from the fixed medium to a new SD and boot from it, now I should see my system again or?
    And then in the armbian-config with...
    System&security -> Install to -> system on emmc, boot from emmc
    ... to clone the image again on the emmc...

    https://wiki.kobol.io/helios64/install/transfer/

    Thank you for the Rsync guide, I'm going to give this a try real quick, I had to modify the parameters since i had my usb SD card reader mounted as /media/USB, the rsync just finished. I'm going to shutdown, and pop the SD Card in and see what happens :)

     

  8. Can you explain how you got your system back?
    Unfortunately, I also updated to 21.08.01 tonight and urgently need a downgrade to get the system back.
    Would be very grateful to you!
    If you can SSH in or possibly boot off of an SD card with the latest image, you can reinstall the bootloader, it at least gets it up and running, least for me that means I can get in and see my drives and wrote to the, but I fear the emmc is still somewhat locked down but yet it lete turn ash back on.

    Sent from my Pixel 4a (5G) using Tapatalk


  9. [mention=17374]bunducafe[/mention]You could try to update the bootloader on emmc first. [mention=16373]IcerJo[/mention] claims that this would make it writable again. Then you could downgrade linux on emmc to 21.05.4. There is no need to format emmc - alternatively you could also repair errors in the filesystem with 'fsck -f /dev/mmcblk2p1'. You will see that something needs to be corrected. If you trust that everything is fine after that you are done.
    Seems like it doesn't make it fully writeable, but it does let the system boot and I'm able to access all of my files and save some changes in the system, like turn some services on and off. But I couldnt write the 3 files to the emmc to do a downgrade so unless I messed up I am at a loss but would gladly try the above mentioned.

    Sent from my Pixel 4a (5G) using Tapatalk

  10. 31 minutes ago, ebin-dev said:

    @bunducafe dpkg -i *.deb did the job;  @IcerJo I would not trust a "temporary" fix I do not understand.

     

    In Essence I did what you stated but by using armbian-config to re-push the bootloader. How would one go about making the emmc Write-able in order to install the 3 packages to downgrade the kernel? Or would I need to re-setup OpenMediavault and everything, and run it from the SDcard or copy it over to the emmc from the SD Card with the old kernel, and then do a kernel freeze for time being till issue is resolved?

  11. 41 minutes ago, ebin-dev said:

     

    You are using kernel 5.10.60 (Armbian 21.08.1).  Several Armbian patches did not compile with this version of the kernel - it is therefore unstable (see the parallel thread - upgrading to Bullseye). The kernel panic occurred after 150372 seconds = 41.77 hours of operation !

     

    Ahh, so it's essentially a ticking time bomb? I pushed the bootloader from an SD card and got my system back up yesterday.

  12. 20 minutes ago, bunducafe said:

    Uh, I should have followed this thread a little bit earlier as I ran into the emmc issue (no write permission) and the system does not come up and I cannot manipulate anything.

    For now I am back with sd cards and will probably stick to it as I can make clones from the sdcard a bit easier with my setup here.

     

    Is there an easy way to roll back the actual kernel?

    I don't know much when it comes to armbian, but from the temp fix I did, it seems like the bootloader was the culprit/issue, I installed/pushed a new bootloader via the latest image on an sd card and my system is back up and running with the latest kernel with no problems. Or rather i think it might be a combination of issues, I am not sure how the bootloader being pushed would work if the kernel is the culprit but at least my system is back up and stable till they have a proper fix implemented.

     

    I read another Post where its a Kernel Panic that Occurs at 150372 seconds = 41.7 hours..

  13. On 8/31/2021 at 6:18 AM, bunducafe said:
    I am with Buster, but regarding the ondemand governor: I have set them from the very beginning from 400 and 1400 and the system has been running rocksolid after this.

    Thanks, I guess I'll stick with what works/caused me to be stable for this long

     

    Edit: I opted to start fresh and am testing the stability of the new kernel's Govenor and cpu frequencies via SD Card till they fix the EMMC issue's which then at that time i will push Armbian back to the EMMC.
    So far 22 hours with no problems.
    Sent from my Pixel 4a (5G) using Tapatalk
     

  14. On 8/27/2021 at 2:58 PM, meymarce said:

    I think I tried that and it did not work very well for me, will do some testing this weekend again though and give it some tries and report. Maybe my Uboot did not get updated last time as that requires manual input

    Any update? I know I set my Max and Minimum cpu frequencies to the same for both the 4 cores and 2 upper cores. and never looked back lol If ondemand and cpu frequencies have been fixed that would probably add some robustness.

  15. 8 hours ago, Igor said:


    We can only hold / remove upgrades for entire rockchip64 current family (5.10.y) but this bug has to be solved asap since this is temporally solution / hack. 

    Howdy Igor! A workaround I found that seems to work for me, was to boot from the latest release from an SD card, and update the bootloader. It seemed to let me back in and stopped giving me the login loop i was experiencing. I am running Buster.

  16. 4 hours ago, pierre said:

    Hello,

    Same problem for me: impossible to install update: the following packages have unmet dependencies: armbian-bsp-cli-helios64

     

    image.png.7b0a16ce8177f12fe1d9b8fe3c1dd7fc.png

     

    So what can we do to fix this bug ?

     

    Thank you.

    Pierre

     

     

    I had the same issue, I had to uncheck CLI and the linux-buster-root-current, then installed updates, followed by the CLI alone, after installing the CLI the root-current 21.05.1 went away/was no longer available for me to attempt an install..

     

  17. I set my Helios64 up last week, and placed it at it's final home/location. My unit had been running perfectly fine for 2 days then sometime this morning before I woke up it crashed and auto rebooted. System has been up for 2 hours now. Following the guide above, I have changed my cpufreq to 400mhz-1.4Ghz and I set the governor to OnDemand and will see if stability will last beyond two days :). Hopefully whatever the culprit is, will be fully ironed out by or before the Armbian becomes fully supported I was just on the site and it now says supported lol.

     

    Thanks again to all!

  18. On 10/22/2020 at 9:21 PM, gprovost said:

    Euhhh wait, can you share the link of the PSU you buy because it's not always guaranty it's the same pin out (unless it's PSU for synology).

     

    Here a good replacement https://www.amazon.com/TAIFU-4-Pin-12V-8-33A-Replacement/dp/B07NCG1P8X

    Thank you! I canceled delivery of the psu I ordered and then ordered the one you linked, It has arrived today and the issue is now resolved! Thank you for saving me from making a grave mistake!

  19. 21 hours ago, gprovost said:

     

    Before going any further, yes you need a multi-meter to narrow down the issue which is probably just a faulty PSU and need to be replaced.

    I Have ordered a New Power Supply and will test the system with it when it comes in. It was kinda hard to find a 4pin with 12v 8 amps, I'm still searching for my multimeter but can't seem to find it. I do appreciate your guidance and support! If the new Power Supply has the same issue which (which I doubt), I will then order a new Multimeter and do some testing when I get back home on Sunday.

     

    Thanks Again!

  20. On 10/6/2020 at 4:08 AM, gprovost said:

     

    Humm if you still get 0V on 12V molex but you are sure that the PSU is ok, then it could the 0-ohm resistors R106 or R107 that are dead, maybe due to a power surge. Can you do a continuity test with your multi-meter on those 2 resistor (highlighted in yellow below) ? If you confirm R106 and R107 doesn't let juice go through then you can bypass them by doing 2x dirty solder bridges as shown with the 2 red lines below.

     

    image.png.8256bedd75ce381f62c9a0b896ec426f.png

     

    Seems like my Helios4 may have the same issue, I've at least diagnosed it to the point that I know it's a power issue, If I mess with the cables, I can get 2 drives to boot, but the other 2 either wont show or if i get it going it seems like the system itself wont boot up. I am currently looking for my multimeter to test this part out. I don't currently own a soldering iron but can quickly get one, Any particular Solder that you recommend for the Dirty Solder?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines