Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Tue, Dec 11, 2012 at 03:39:15PM -0500, Jerry Feldman wrote: > On 12/11/2012 01:53 PM, Derek Martin wrote: > > You could follow Bill's suggestion and pull apart the package and see > > what it does. Or you could just test it... Being very careful not to > > run anything else, log in to your system, change the driver back to > > gallium. Log out, and check your ownership and permissions. Then log > > in again, update it to nvidia again, and do your check again. > > > Possibly an easier way is to make sure everything is Kosher including > your home directory permissions and ownership, then after you have > verified, reinstall the package that you think caused the problems, then > double check the ownership et. al. Then you can terminate your X session > by logging out. You should be able to log in once again. Or if the > problem is the same as before, then you can assume that the package you > installed is the culprit. Possibly easier, or possibly harder. It's almost exactly what I suggested, except it leaves out the step of returning the machine to the state it was in prior to upgrading the driver. If the problem is caused by an interaction between those two, skipping that step will obviously not trigger it... -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |