• Posts

  • Joined

  • Last visited


Profile Information

  • Interests
    Free Software (and Hardware!)

Recent Profile Visitors

2620 profile views
  1. Sorry could not make the meeting. I just read the notes. I am back to work now but locally (almost no travel) so I can have a little time here and there maybe to help with the release somehow. I'll try to hang out in IRC.
  2. I have been wanting to buy one for what seems like months (a year?) now and they have not been able to do a production run due to the supply chain shortages (mainly screens, apparently). I follow them pretty closely, there was some hope maybe after CNY 2022 but then they announced no they could not source screens after all. So your information is really timely @hexdump, thanks a lot for that.
  3. TRS-80

    5.15 broke zfs-dkms

    If I am recalling correctly, it was non-trivial (and thus, took some time) to figure out some solution that worked, in order to make this 'easy' for end users. It sounds like this broke now with kernel going up to 5.15. If I am interpreting this search for zfs Issues on our Jira instance correctly, it looks like the developers are aware of the issue(?). If you make any progress on figuring this out in the meantime, please do post back what you learned.
  4. Generally speaking, yes, just burn to some other sd card and try to boot it and see if the new version works. Follow instructions in documentation. Whatever latest version is for that board, which can be found on download page. I don't own this hardware, I am assuming it will boot from inserted sd card first, but some devices don't work that way (most do).
  5. So I would try uninstalling all those -edge-rockchip64 packages (or just flash new clean Armbian image) and then try to load that driver.
  6. First thing I notice, is that's quite old version of Armbian, can you upgrade?
  7. I think you did not give the most pertinent information. It depends what is your current topology. As redundancy is done at the vdev level in ZFS (if I am remembering my terminology correctly). Depending on that, it can be possible to upgrade in place. Topology will dictate how much effort that takes.
  8. I see this a lot, and I am afraid it's a common misunderstanding. Debian is a distribution, they distribute (mostly user space) packages from various places. The kernels they get wholesale (from, usually). Which is why the kernels in vanilla Debian (generally speaking) are going to be so far behind Armbian's (heavily patched and customized) kernels. In fact, this is essentially one of the main raisons d'être for Armbian in the first place. SBC/ARM is very different from x86, which is much more standardized on a hardware level. And that's also why, the user space comes pretty much straight from upstream vanilla Debian. Because that's not what we do here. Here we are focused on the (much more difficult) low level things, like kernels, bootloaders, etc. Where vanilla Debian do not. It will be nice if one day this is not the case, but I just don't see that happening in foreseeable future.
  9. Yeah, I went ahead and put it into a spoiler (to fold away) but something that big (especially that likely exists publicly in some forge) I would have probably linked to, personally. Well, I give you credit for at least doing some investigation. Other than noticing the great length of that script, I will admit to not investing any time whatsoever studying it any further. However, my immediate thought is: Do you really want to rely on something so complex to continue to be maintained by a third party? Or to fork and maintain yourself? Especially given that bash scripting is admittedly not your cup of tea? Prior to seeing this script, I was already a bit skeptical about how far DietPi strays away from standard Debian ways of doing things. But that was based on very brief experience playing around with it only once some time ago. If we take a step back to the fundamental problem that is trying to be solved here, that seems to me essentially to be backup. And backup is good! However perhaps there is some other better way to go about that?
  10. Do you have something against regular vanilla Debian? As a long time Debian user myself, I would feel much more out of my depth on Manjaro, personally.
  11. Thanks for the info, I learned something. Video and graphical stuff is a bit out of my wheelhouse.
  12. For your amusement, I will leave you with one of my favorite quotes from Bjarne Stroustrup, which I serendipitously came across (again) just yesterday:
  13. No not really. I just like to gripe whenever things are deprecated in favor of 'modern' alternatives, especially ones that surely use (proprietary?) JavaScript. But I have used it, most recently for the last release announcement. When trying to convert the result of HedgeDoc site (Markdown) into the forum, using bbcode was my approach. I almost got it to work. I am not aware of anything else that might even come close to being scriptable. My understanding (from brief research at that time) was that Invision themselves have deprecated it a long time ago already. So I am only ribbing you a bit, not really sure how feasible it is for us to keep it. But there is also, for example, bbcode-mode in Emacs. And I do use Edit With Emacs (FF plug-in) quite often.
  14. Not that I am aware of. Armbian is focused on much lower level things, like kernels, etc. Have you studied the script? Maybe you could adapt it (or even use it directly)?
  15. I vaguely recall some other thread about 'watchdog breaking on newer kernel', did you search the forums?