meep

Members
  • Posts

    758
  • Joined

  • Last visited

Report Comments posted by meep

  1. 2 hours ago, Frank1940 said:

    As an old computer user (1981 with a RS Color Computer) who has just enough exposure as to how operating systems function, I kinda understand what to do from this limited set of instructions.  (I also realize that the devil is always in the details. Installing the driver is probably only the first step to what must be done to fully utilize the driver.)  I am also presuming that these mentioned GPU drivers would normally be found in most Linux distributions and, if the hardware associated with one of these GPU drivers was detected when Linux is being installed, the appropriate driver would be installed and made ready for use.

     

    I realize that this a beta release and many features that could/(should) be included in the final release may not be there but I feel that you should be considering the person who wants a straightforward install of all the features he wants without resorting to the command line. 

     

    What I think is needed is a 'Video Setup' icon in the Settings menu which would allow the user to decide whether he wants to include a video driver in his Unraid setup.   If he decides to include a video driver, I would hope that on reboot, the install process would detect and install the proper driver.  If that can't be done, at least, allow the user to chose which driver to install and have a background script do the heavy lifting.  

     

    EDIT:  One more thing.  There should also be detailed information on exactly what GPU hardware each of these drivers support.  i915.conf does not really provide any information as to hardware is actually supported!

    Good points all, but a couple of observations.....

     

    Typical (traditional?) software release schedules consider betas to be functionally complete, and are provided for testing and big fixes only. Limetech don't seem to follow this, and the beta cycle becomes more of an extended alpha with new bits being added all the time. This is likely the root cause of the often unfeasibly long beta cycles, and why they don't talk about release schedules - you cant predict them with this methodology. 

     

    I'd prefer to see scope-limited releases with fixed feature sets, tested efficiently and released on a more regular basis. I think this would also help grow adoption as new users see a healthy, vibrant platform with regular updates and new feature additions.

     

    The second point is, historically, unRaid tends to get new features in a rough & ready manner, something like this release. It works, but requires a degree of pfaffing about in config files and the like to get it set up. The UI tends to follow a release or 2 later when the feature & functionality settles down.

     

    I recall being about for the birth of VMs, when not only did we need to hand code all the VM XML files, but Limetech changed the VM engine very late in the day, and a lot of the knowledge and skill early adopters had built up had to be thrown out and re-learned. For such reasons, it makes sense that they don't focus on a smooth UI early on - if the underlying implementation needs to be re-factored, that would be a waste of work.