• 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle










  • ScottE@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    4 months ago

    So what do I have wrong here?

    Nothing, as far as I’m concerned. I guess DEs have to constantly change or they become stale to some people. I’m an older guy than the normal demographic here too and stale is exactly what I want. I run i3 with a bunch of terminals, a browser, and sublime text when vi in a terminal isn’t enough (yes, it’s really vim, but it’ll always be vi to me), and I xsetroot the classic weave pattern for my background. That’s it. I don’t need or want menus, widgets, themes, file managers or anything else. I guess someday Wayland will win, and I’ll be forced to do something different, but until then, not changing this extremely productive and efficient environment.


  • I don’t use Fedora, but I have ZFS on all my Arch systems for everything (including root fs). So, I’ll make a guess - is the package you installed for ZFS a DKMS kernel module, or a binary one? That’s the first thing. If it’s a DKMS module, I don’t see anything on your output showing it was compiled, which would explain the module not loading. If it’s a binary module in that package, it must be for the exact same version of the kernel that is installed - exact same. If it mismatches then you need either a different kennel or different ZFS package. In either case, you’ll probably need to wire in a hook for your initramfs, but it looks that part might be ok from your output. Hope that helps, good luck. ZFS is incredibly good.


  • One thing with Reolink, for anyone seeing this, just be sure to get one of the hardwired (for power) cameras. I have a wired Reolink doorbell (which is quite nice) and a solar+battery powered Argus which is practically useless other than as a deterrent. The battery powered devices don’t integrate well, no video streams, and have very weak object detection.






  • I don’t have an exact answer to your problem, but I do have a few ideas to think about. I’ve got a few ESP32 WROOM boards running in various applications, so I’m a bit familiar. So here’s my thoughts:

    • I only plug the module into data USB (computer) for the initial firmware provisioning. After that, it’s 100% wifi and USB is only for power using a power supply, not the computer. And I do the initial provisioning with just the bare ESP32 - no breakout board, nothing plugged into GPIO. Get the device up on wifi with NO other configuration in the firmware.
    • I use the “arduino” framework. I don’t know if that’s correct or really matters, I’ve heard it’s the same as “esp32dev” but I don’t really know. I use “arduino” because that’s what the examples used when I setup my first board.
    • Is it possible that the sensor module/board is using the same GPIO that the USB UART uses? There is a lot of shared usage of the GPIO that you’ve got to be careful to work around. The dev tools will often catch this when you compile your firmware, but not always. Again, using wifi after the initial provisioning might be enough if it is sharing GPIO with the serial port.
    • If you repower the ESP32 too many times rapidly it’ll boot into safe mode. You can change the settings on that, but you can also just work slowly - make sure the device is powered on for a few minutes to record a good boot in the flash. It outputs a message in the logs, so it’s handy to always be running the log command in a terminal while developing.

    Hope that helps! They are a lot of fun to integrate with HA.