Gareth Halfacree

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

Gareth Halfacree's Achievements

  1. That's what I thought, Thank you, Igor, for finally revealing your true colours for all to see. Good luck with the future of your project.
  2. I literally have done that. You didn't like it, remember? I found a bug, I posted about the bug in the forum without ever directly contacting any Armbian representatives... and you attacked me for it. Make your mind up, Igor. Do you want me to report bugs, or don't you? I'm not - you are. You tell me that finding bugs is far too costly for the Armbian project in one breath, then tell me that the community finding bugs is "dirt cheap" on the other. You can't have it both ways. Especially if you attack those who actually report bugs. For free. I see we're back to name-calling. Remind me of the forum rules on that again? You called me a redneck. You called me a jerk. You've called me all this and more. If I were to put a name to your behaviour, it would be "bully." Really? Because... ...others would disagree. Are you willing to look in the mirror and examine your actions, Igor, or are we done here?
  3. No, they're not. You just told me that finding symptoms is dirt cheap, so why aren't you doing it? If it's so cheap, it will have absolutely zero impact on the project's running costs. Likewise. Perhaps if people had felt they could ask questions on this, the Helios64 forum, without the risk you would attack them and demand money with menaces, the Kobol team wouldn't have abandoned ship. But, instead, you decide to go on the attack - even when the Kobol team was having a perfectly pleasant conversation with a user. Show me where I have personally attacked you. Show me where I have called you names. Show me where I have actively lied about your conduct. You can't, because I haven't. You are the only one behaving that way. You could, yes. This is your project. You are in ultimate control. But banning me because of your own behaviour would prove once and for all that you are incapable of reflecting on your actions, of change. It would be the ultimate admission that you are in the wrong, and that you have zero defence for your actions. Or you could reflect. You could modify your attitude. You could work with community members, instead of against them. Imagine how much could have been achieved if your response to my original post had been something along the lines of "hey, thanks for the report, that's clearly broken, unfortunately we don't have the resources to look at it yet, but here's the source code and we'd really appreciate any input you could offer." There are always two paths to take. Maybe try the road less travelled.
  4. Aside from actively attempt to help other Helios64 users, thus actively reducing your support workload without any return? Not much, I guess. I tried to get you to see that your attitude will be the death of the project, but I think I'm going to have to give up on that. Then why didn't you spot the problem before you released the update? Why didn't you spot that the previous update broke the fans? Why didn't you spot that the update prior to that broke the Ethernet? Why didn't you spot that the update prior to *that* corrupted boot files? Those are all issues that you would never have known existed without reports from the community. The only reason you think "finding symptoms is dirt cheap" is because you farm your testing off on the community. Then if anyone has the temerity to actually report something like, I dunno, that you accidentally removed the 2.5Gb Ethernet driver from the build and didn't notice, you attack them and demand payment. And you don't see this as a problem. This is a forum, yes. Remind me, does the forum have rules against harassment? Against personal attacks? Against calling people things like, oh, I don't know, "redneck"? Communities are fostered from the inside out. You need to decide what kind of community you want to foster.
  5. You cannot defend against abuse by being abusive - especially towards those who are not being abusive themselves. And yet - and I made this point the last time we had this discussion, but I'd really really appreciate it if you'd read and understand it this time - you've spent an entire morning arguing with me over something you now admit I'd never done in the first place. Time that could have been productively spent on something - anything - else, whether that's fixing bugs or just going outside and enjoying the sunshine. You're falling back into your old patterns here, Igor. Show me where I have ever demanded that you work on my problems. You can't, because I never have. I have reported problems, and I have even asked the community for advice on how to resolve said problems. I have never, ever approached you or any member of the Armbian development team for assistance, much less made demands. In fact, I literally asked you to leave me alone the last time you decided to attack me. I had hoped your begrudging apology was the beginning of change. Apparently, fruitlessly.
  6. I will assume this is an apology. I am not forcing you to do anything. I would like you to stop responding to innocent bug reports in an incredibly aggressive manner. That would be nice. I also don't know how open source projects work better than anyone else, and have never claimed to. You were the one assuming that, somehow, in the year 2021, putting Armbian on my NAS was literally the very first time I'd ever encountered FOSS - a very, very incorrect assumption. You maintained that assumption even after I corrected you, on more than on occasion, because it allowed you to believe I have no idea what I'm talking about and thus dismiss my very valid concerns out-of-hand. I'll make no bones about it: that's literally the only reason I'm here. That, and to help others do the same. It would have been nice if we could have worked together - me in the self-interest of having my NAS not die every time I apt update, and you in the self-interest of not having a bunch of people complaining to you that their NAS dies every time they apt update - but it's clear that's not going to happen.
  7. That is an outright lie, and you know it. Here is the thread in question. I asked a simple question. The next day, a Kobol team member - not Armbian - posted a response. I tried what was suggested, and replied. The day after, the same Kobol team member posted another suggestion. Then, without any further prompting or posts on my part, you jumped in with an aggressive reply - moved by your own forum moderators to here and renamed "random rant" because it was so unwarranted and off-topic - telling me you "don't have time to care what 'customers' need" and that if I wanted the installer to work as expected I was "welcome to organise and finance its refactoring, development, research." Until that point, I had not responded unless in reply. I had waited patiently. I was polite. At no point at all prior to your interjection did I "build pressure" or "bump topics." If you're resorting to literally lying about my conduct on the forum, I think it's clear you know you're in the wrong here.
  8. I have never asked for either. I did report, politely, a bug with an installation tool, which was not - and still is not - set up to handle updating the bootloader on the eMMC from a SATA install, and you jumped down my throat. Remember? Because I do. Incorrect. As I've told you before, I've been involved with FOSS and open hardware for decades now and have worked on projects both bigger and smaller than Armbian. I have plenty of expertise on the topic, and I am telling you now that accurate bug reports help a project - and that you are doing nothing to encourage said reports, and are in fact actively discouraging them. This, from the man who accuses me of hostility? Remarkable. Funny. I use Ubuntu on my other devices, and I don't think you could accuse Canonical of not being "serious" about it - yet I can communicate directly with the developers and am thanked, rather than attacked, for my bug reports. Wrong. Armbian is your project, and you seem intent in running it into the ground. Your website says different, Igor. "SUPPORTED". "High level of software maturity". Neither of those claims are true, from what you're saying. Perhaps your next priority, though far be it from me to assign such, should be correcting your website?
  9. As I keep trying to explain, and you keep missing, bug reports and testing are a generally-accepted way to help an open-source project. The fact you don't realise that is why Armbian is a dead end for any kind of serious use. Well, that's certainly an upgrade on your usual demand for a €50 a month subscription. I leave it up to the reader to decide who is being hostile here - and as for "giving me gold," you are constantly breaking my NAS. That's the opposite of gold.
  10. As I can see, which is why I am making sure to move away from Armbian - and I recommend anyone reading this to do the same. It's simply not a project you can rely upon for daily use. For messing around with as a hobbyist, sure, why not. But to actually rely upon? Impossible. Especially when the founder doesn't understand that bug reports - especially bug reports from beta/nightly users, which have been specifically requested right here in this thread - have value to the project. With an attitude like that, Armbian will never become anything more than a hobbyist's curiosity. I'll repeat for clarity, so others reading this thread don't misunderstand my meaning: this is going to keep happening. Future updates will continue to break the Helios64, and other devices, and there is nothing you can do about it. Armbian, as Igor says, simply doesn't have the resources to properly test its updates before release, much less actually respond to bug reports. You will not be able to rely on it to keep your Helios64 running and your data safe. If you're happy with that, by all means continue to use it; otherwise, I'd advise looking into alternative software and/or moving to a new NAS altogether.
  11. Oh, I've tried reporting problems. Igor told me (and many, many others) that if I wasn't paying €50 a month to Armbian he wasn't interested, so I stopped.
  12. No, the storage is fine - Armbian 21.08.1 is yet another update that hoses something on the Helios64. Last time it was the fans, the time before that the 2.5Gb Ethernet port (twice), and this time it's the eMMC. You'll need to follow the instructions upthread to downgrade the kernel to get the eMMC working again. Then cross your fingers it gets fixed at some point in the future.
  13. If anyone has installed the update but *not* rebooted, it's a quick (temporary) fix: sudo apt install linux-dtb-current-rockchip64=21.05.4 linux-headers-current-rockchip64=21.05.4 linux-image-current-rockchip64=21.05.4
  14. Another month, another big batch of DRDY errors as the btrfs scrub runs.
  15. I'd suggest getting one or more drives, setting them up in a btrfs mirror, dding a bunch of random onto them, and scrubbing. It's possible dding alone will trigger the error, but if it doesn't then scrubbing certainly should. $ sudo mkfs.btrfs -L testdisks -m raid1 -d raid1 /dev/sdX /dev/sdY /dev/sdZ $ sudo mkdir /media/testdisks $ sudo chown USER /media/testdisks $ sudo mount /dev/sdX /media/testdisks -o user,defaults,noatime,nodiratime,compress=zstd,space_cache $ cd /media/testdisks $ dd if=/dev/urandom of=/media/testdisks/001.testfile bs=10M count=1024 $ for i in {002..100}; do cp /media/testdisks/001.testfile /media/testdisks/$i.testfile; done $ sudo btrfs scrub start -Bd /media/testdisks The options on the mount are set to mimic my own. Obviously change the number and name of the devices and the username to match your own. It's also set to create 100 files of 10GB each for a total of 1TB of data; you could try with 10 files for 100GB total first to speed things up, but I've around a terabyte of data on my system so figured it was worth matching the real-world scenario as closely as possible.