• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Now that you have a working setup, make a backup. Then, experiment with either starting over and only doing a few of the steps OR experiment with removing some of those parameters. Find your minimum set of working parameters this way, then you can look them up to find out more about what each parameter does that you discovered to be essential.

    I can for sure tell you that passing the render device is required for hardware transcoding, but I’m not sure what else is required. The iommu and vfio parameters are related to passing the entire gpu device into a container, but I don’t know anything about Proxmox so I can’t comment on whether that would be required for your situation.



  • DOCSIS (AKA internet service over coaxial cable) deals in some number of bonded channels, meaning portions of the total available bandwidth on the wire. They asymmetrically allocate channels to download speeds to overcome the limitations of the older copper wire technology. 100Mbps symmetrical is beyond what most of their existing “Broadband” infrastructure can support in rural and underserved areas, so they complained about it being unreasonable. 100Mbps symmetrical is certainly possible over DOCSIS, but speeds are only as fast as the weakest link… And there are a helluva lot of weak links outside of high population density areas.









  • Creating a driver requires a deep understanding of some pretty low-level pieces of Linux. If you’re new to Linux, you should probably start with some “new to Linux” tutorials and get an understanding of some basic command line usage. Work your way up to being able to follow a guide on compiling the Linux kernel (without any of your own modifications). After that, you can seek out guides on creating a driver.

    As a second note, fingerprint drivers are categorically difficult to work with, so this would really be jumping in on the deepest of deep ends. You can do it! But it will take a LOT of self-education.




  • Unfortunately, I think you’re unlikely to find anything besides the ones made by the big companies: Google, Apple, Samsung, and Garmin are the ones I know. They each have agreements with the banks and credit card companies to handle the secure exchange of data required for the touch payment system. In fact, there are still some issues resulting from a lack of cooperation (such as Citi Bank not working with Garmin Pay because they can’t be bothered to set up the relationship). I imagine an open source software would be unable to get the banks to pay attention to them to establish a partnership, or would otherwise be declined because the financial institutions wouldn’t trust them.