DeterminedOpier

Members
  • Content Count

    65
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Calendar

Everything posted by DeterminedOpier

  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 repositories. It's not like the Microsoft Tuesday night mandatory update, but it chaps my ass in much the same way.
  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 understand what we don't understand. I can tell you that my methodology is to wait until someone posts a useful link and try it, because I have no idea what changing a kernel in armbian config even does, and what it would effect. I wouldn't say it's like "explain it for the dumb people." Because I personally wrote a book on remote web publishing in Perl for John Wiley in 1996, and gave away working software, before anyone even envisioned wordpress. I'm sure a lot of other people who look stupid here are actually not at all. You don't know what you don't know, and I have yet to find a good explanation of how these operating systems work now. I just asked Stephen from Opi if one of his images has hardware acceleration, and he said it did. Yet my experience with his images are that they don't even work. So if someone did this, it would be great to explain why things work here and they don't work there, and why, if it works on an old kernel, why anyone would want to even use "mainline" where all kinds of nasty things are broken (like not being able to log into my gmail). Just an idea. I love @NicoD's approach, even if it is usually not from the perspective of what I use pis for at all. Two wives and six kids later, I don't have a lot of time for retro-gaming. :)
  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. * Changed brand of SD card. * Moved pis to power source not the same as printer, in case it was a voltage sag. * Using shielded printer cables. * Initially we used an OctoFarm overlay program, so tested with and without. * This happened on both Prusa and several CR-10s. And the most telltale of them all was that yesterday I burned a standard Raspberry Pi Octopi image, fired up one of my 3B plusses, and hooked it to one of the CR-10s. The camera came on (which I never got working on the Opi), and the first large 22 hour print just finished. I think there is some kind of communication jam up going on, because though the problem is repeatable, it happened at different times. Some even failed at 2%, same behavior. I didn't have the serial log enabled, but the standard log showed nothing. If you are interested @ldiaz, I am willing to hang in there and continue to test for you. After a week and a half of failed prints, I personally I am completely abandoning the Opis for now and moving to Rpis. Nobody even answered my webcam question, and I know Igor isn't interested in camera stuff historically, so it just isn't worth it for now. I am subscribed to this thread, so if you want to come back and try to figure it out at some point, just let me know and I'll be happy to lasso a printer and see if it works. Thankyou of course for all of your efforts. I love Armbian and appreciate the work that you all bring to the world of experimental computing. I will do whatever I can to help.
  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 that binary dtb file into text, with a program called dtc. pi@citrico-opione:/boot/dtb$ sudo dtc -I dtb /boot/dtb/sun8i-h3-orangepi-one.dtb -O dts -o /boot/dtb/sun8i-h3-orangepi-one.dts that gives you the dts file, which you can open in nano. pi@citrico-opione:/boot/dtb$ sudo nano sun8i-h3-orangepi-one.dts Find the code block that has dr_mode in it. On this board it is usb@1c19000. Change the value to host instead of otb. Then control x, y, enter to save the file. Then you have to convert it back to binary. You can make a backup of your original binary file first if you want, then do this: pi@citrico-opione:/boot/dtb$ sudo dtc -I dts /boot/dtb/sun8i-h3-orangepi-one.dts -O dtb -o /boot/dtb/sun8i-h3-orangepi-one.dtb then reboot. The micro usb is now a regular usb, and my gembird camera came up under lsusb. I also had enabled usb0 in the hardware options in armbian-config, but I don't know if I had to do that. I actually just enabled them all before finding this solution. Still stuck on the video though. Snapshots are working.
  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.
  14. And get this. The snapshot works in octoprint, which is listed as this: http://127.0.0.1:8080/?action=snapshot That was after I switched the ffmpeg path to: /home/pi/ffmpeg_cedrus264_H3/ffmpeg
  15. A few more details: pi@citrico-opione:~/ffmpeg_cedrus264_H3$ v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/video2 USB2.0 PC CAMERA: USB2.0 PC CAM (usb-1c1b000.usb-1): /dev/video0 /dev/video1 pi@citrico-opione:~/ffmpeg_cedrus264_H3$ cd pi@citrico-opione:~$ v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/ pi@citrico-opione:~$ v4l2-ctl -d /dev/video2 --list-formats --list-ctrls Codec Controls mpeg_2_slice_parameters 0x009909fa (unknown): type=103 flags=has-payload mpeg_2_quantization_matrices 0x009909fb (unknown): type=104 flags=has-payload h264_sequence_parameter_set 0x00990ce8 (unknown): type=110 flags=has-payload h264_picture_parameter_set 0x00990ce9 (unknown): type=111 flags=has-payload h264_scaling_matrix 0x00990cea (unknown): type=112 flags=has-payload h264_slice_parameters 0x00990ceb (unknown): type=113 flags=has-payload h264_decode_parameters 0x00990cec (unknown): type=114 flags=has-payload h264_decode_mode 0x00990ced (menu) : min=0 max=0 default=0 value=0 h264_start_code 0x00990cee (menu) : min=0 max=0 default=0 value=0 hevc_sequence_parameter_set 0x00990cf0 (unknown): type=120 flags=has-payload hevc_picture_parameter_set 0x00990cf1 (unknown): type=121 flags=has-payload hevc_slice_parameters 0x00990cf2 (unknown): type=122 flags=has-payload hevc_scaling_matrix 0x00990cf3 (unknown): type=123 flags=has-payload hevc_decode_mode 0x00990cf7 (menu) : min=0 max=0 default=0 value=0 hevc_start_code 0x00990cf8 (menu) : min=0 max=0 default=0 value=0 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'ST12' (Sunxi Tiled NV12 Format, compressed) [1]: 'NV12' (Y/CbCr 4:2:0) USB2.0 PC CAMERA: USB2.0 PC CAM (usb-1c1b000.usb-1): /dev/video0 /dev/video1 I'm still working on it. These commands I got from @ldiaz working on my rpi cameras that didn't work. It seems like the gembird is a common camera though, and it seems like it should be working, but so far it isn't.
  16. Hi guys. I've just spent yet another two hours trying to find an answer to my webcam problem and there does not seem to be an answer from what I can discern. Still working to try to get a camera to work with Octopi from what I have around. Strange thing I discovered that the USB OTG port on the Opi One does not seem to work, but when plugged into my single regular USB, I get this for the camera: pi@citrico-opione:~/ffmpeg_cedrus264_H3$ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 1908:2310 GEMBIRD Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It is one of the known working with mjpeg-streamer https://community.octoprint.org/t/usb-webcams-known-to-work-with-mjpg-streamer/21149 but the notes don't seem to be current. pi@citrico-opione:~/ffmpeg_cedrus264_H3$ ls /dev/video* /dev/video0 /dev/video1 /dev/video2 I have tried some of the old gits out there. My only ray of hope was when I did modprobe hid-gembird it did not error, just seemed to say ok. But still no webcam, just a different message, of/dev/video0: Device or resource busy instead of it not being a video capture device. So I"m out of ideas. Any help would be appreciated. Trying to find an inexpensive webcam solution for octopi using my Opi Ones.
  17. FYI for anyone following this thread in the future, if you are trying to get the old standard orange pi camera (that Steven sells on Ali) to work with Armbian, as of right now it is not supported in the mainline kernel, and the legacy 3.4 kernel is deprecated because the repositories are no longer supported. So for now, they don't work. We'll have to put them away until they are cool and retro like vinyl records.
  18. Hi team. I am having a difficult time getting the standard Opi CSI camera to work on the newest mainline Armbian. I don't have the ability to use a legacy version because it is coupled with a preconfigured Octopi, thanks to @ldiaz. He says that Octopi will work with the camera once the system works with the camera, and I have not been able to get it to work. There are at least a dozen threads here about that camera, but most are dated. And the ones that aren't seem to talk more about performance, and they assume that your camera is working. I also saw one about overlays, which I have no idea how to deal with, or even what they are. Something tells me it just isn't this hard and that there must be some kind of way to deal with this easily, or it just isn't supported right now in this version and that's that. Either is fine. I'm old, and my brain hurts. Thanks in advance.
  19. I caught one thing I hadn't tried from all the threads out there about the gc2035 (orange pi branded) camera. This is what it says. pi@citrico-opione:~/v4l2loopback$ v4l2-ctl -d /dev/video0 -D Driver Info: Driver name : cedrus Card type : cedrus Bus info : platform:cedrus Driver version : 5.4.45 Capabilities : 0x84208000 Video Memory-to-Memory Streaming Extended Pix Format Device Capabilities Device Caps : 0x04208000 Video Memory-to-Memory Streaming Extended Pix Format Media Driver Info: Driver name : cedrus Model : cedrus Serial : Bus info : platform:cedrus Media version : 5.4.45 Hardware revision: 0x00000000 (0) Driver version : 5.4.45 Interface Info: ID : 0x0300000c Type : V4L Video Entity Info: ID : 0x00000001 (1) Name : cedrus-source Function : V4L2 I/O Pad 0x01000002 : 0: Source Link 0x02000008: to remote pad 0x1000004 of entity 'cedrus-proc': Data, Enabled, Immutable
  20. Ok thanks I'm going to keep digging with it. I don't see a guide by @@lex, just that thread that got hijacked, and I don't understand overlays at all at present, but I'll try to figure it out. To me right now the important thing was getting octopi going and being able to install the plugin for the raise cloud. It works fantastic, and I am over the top grateful for the help. The camera is a nice thing, but not a big deal with what I am trying to do with them right now. Eventually I'll get it.
  21. That's like a smart people thread. I'm not one of those guys. They kind of hijacked the thread and the guy never tried the advice buried in there somewhere. Mine is that same orange pi camera though I think.
  22. @ldiaz have you ever tried to get an rpi CSI camera to work with the camera interface? I have tried all of the stuff I could find on the forums sudo apt-get install v4l-utils and what I could understand from this thread: but still nothing, even from just sudo mplayer tv:// Going to try a USB camera now. I just happen to have a pile of those rpi cameras. #edit couldn't get USB camera to work either, but mplayer gave me a different error, and now I have /dev/video 0 1 and 2. #edit2 later found the service in the config script, enabled it, and it got a could not remove klipper service message, but the star was there when I went to check, so it apparently worked. but camera does not