--- Comment #2 from Stewart Adam <s.adam(a)diffingo.com> 2008-11-24 14:15:09 ---
(In reply to comment #1)
Can you explain the scope and the goals of this package a little more
It's essentially a better livna-config-display which handles things
will obsolete livna-config-display. It essentially enables three key things:
* Parallel installation of multiple graphic drivers
* Auto-selection of the most appropriate driver out of the graphic drivers
installed on the local system
* Hooks to allow any GPU driver to be configured with rpmfusion-config-display
(ie, user packaged ones)
- Are we going to write config files for every card out there, OR
- Are you going to extract this information from the Appendix A of README files
inside the Nvidia driver packages (I don't know about ATI), OR
- Do the end users have to write these config files by themselves?
For now (during
the testing phase), since none of our packaged drivers have a
config file for rpmfusion-config-display, users will have to write it
themselves. Once this has been reviewed & accepted, I'll write up the config
files for each driver and package them so no user intervention will be
required. A config file is required per driver, not per card, and the PCI IDs
for the cards are taken from the driver support lists (ie Appendix A).
About the software: I couldn't figure out what I should put for
the version in
the config file. I have kmod-nvidia-newest installed. I tried
version = newest
version = 177
version = 177.82
version = 177.xx
None worked. Either the script fails, or the window shows up but says "No
(I would go through the code but I didn't have time this weekend. )
the README.developers file - version is the driver version (177.82).
"newest" should be in the filename, for example
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.