DeterminedOpier

Members
  • Content Count

    65
  • Joined

  • Last visited

About DeterminedOpier

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. This wasn't meant to be criticism. I was not saying that you are mean. In my experience you have been anything but mean. As you said these boards would be paperweights if it were not for the work that you have done.
  2. Thanks Nico. Explaining it as you did, it is difficult to understand why the default download is Mainline. I would think it would be easier to provide the patched and fixed Legacy as the first choice, but if you need Mainline, it works on most things. I have always just assumed and if Mainline was available you should probably use that because the repositories aren't going to exist long on the Legacy versions of the versions of the kernel. So frustrating when you have a computer worked out and you are happy oh, then you get a message that's your version is no longer supported by the reposito
  3. Yea I actually don't understand why you deal with any of this nonsense Igor. The internet became a mean, entitled place where nobody has any accountability except the people like you who offer themselves for the betterment of mankind. I tried to help some when I can, because the nice and grateful ones do make it somewhat worthwhile and fun. But OMG the bullshit you have to put up with at the top of this food chain I don't know how you continue.
  4. Thankyou for the time you take to clarify explanations. You know, @NicoD, I think a great article/video for you would be to explain the difference between the versions of debian/ubuntu (buster, bionic, jessie, etc.), and the different versions of the kernel. What is legacy vs mainline? What does it mean when one has support and the other doesn't? (can't you just copy it over). Why are these features, like hardware acceleration, so difficult to make work? I would write it if I understood it, but I don't. And as you can see in this thread, smart guys like all of you don't even un
  5. I bailed to x86 lol. I've been beating mi head against the wall of these arm boards enough lately.
  6. Yeah I have not been willing to switch the nightly builds because the last time I did it random things break. I only broke this board out because my laptop got dropped and I have to send it back to Dell. It is pretty much standard operating procedure for me to pick the one and has a known bug with no sound. I can use my phone for YouTube for a couple days
  7. This is still not working on the latest Buster for the N2. I switched to legacy kernel and the audio sink returned to normal, but it broke other things so I went back. http://ix.io/2vZM
  8. I don't know what that means lol, but I will try to figure it out when I return to the Opi attempt at octoprint. Thankyou.
  9. Yes, that is exactly why I decided to just give up for now and move to the Rpi. It definitely on prints longer than 12 hours, but the last one happened at like 2%. Once we get things rolling with all of our printers I will enable the serial log and attempt a long print again, and get back to you with it. Thanks for the followup @ldiaz.
  10. So, @ldiaz, and others who may be interested in this thread. The Orange Pi One experiment is a complete failure. Octoprint installs correctly, connects, prints, all just fine and everything is seamless. But, and this is obviously a huge but, long prints eventually fail, and usually late. So you wake up to a 20 hour print that should still be going, and the print head is frozen at over 80%. So essentially a whole day got taken up, for nothing. This has happened repeatedly, over a dozen times, while I tested and retested to eliminate variables.
  11. I have made the change on several of these Orange Pi Ones now, and you don't have to do anything in armbian-config. Just that one field in the dtb file is it.
  12. For those who may be finding this thread later, I made some interesting progress today. The Orange Pi One has only one regular USB port, which, using OctoPi, you need for the printer. But it does have also a USB OTG, which you may call Micro USB, and I have never used it for anything. Initially I plugged in the camera to that with an adapter, and got nothing on lsusb at all. After some digging, I found the way to cure this. You have to edit the dtb file in the /boot/ dtb/ directory for your board. All the supported boards are in there. Then you have to convert tha
  13. Another update. I was able to update OctoPi to 1.4.2 and the printer connected. It was on the second try actually, but it did connect, using the two AUTO settings. So @ldiaz it is working fine with no errors updating the base software and the plugins.