[Leaplist] installed Ubuntu restrictive Nvidia x crashed

[Stephen Cullum]

Thanks Richard.

Richard F. Ostrow Jr. wrote:
> A simple call of:
>
> sed s/\"nvidia\"/\"vesa\"/g /etc/X11/xorg.conf
>
> will output a modified xorg.conf to stdout that will go back to your
> working drivers. Look at the output, verify that it looks OK, then commit
> it.
> On Tue, July 14, 2009 5:32 am, Fred Moore wrote:
>   
>> Stephen Cullum wrote:
>>     
>>> I up graded my daughter's computer from dapper to hardy today. Every
>>> thing went well . Logged in and from the apple let installed the
>>> nvidia restrictive drivers. Rebooted and every thing went well until
>>> the log in screen . It went white and the mouse froze then jerked. I
>>> rebooted and from grub dropped down to a root shell. How can I reset
>>> my x server from using the restrictive drivers and use the original
>>> configuration which worked? If the old xorg.conf file was backed up
>>> can I simply copy that back to the xorg.conf file and roll back to the
>>> original configuration using the original driver? Under dapper I used
>>> the restrictive driver for it and it worked.
>>>
>>> Thanks for any help offered.
>>>
>>>       
>> It may have been backed up (depends on how it was changed) look at
>> /etc/X11/ and see if you have a xorg.conf with a date stamp added
>> something like xorg.conf.20071209151604  (from my machine, guess its
>> been a while since it was changed) if so copy it over xorg.conf.
>>
>> If not, boot the livecd after it starts copy the running xorg.conf over
>> the xorg.conf on the hard drive, which should be mounted, or write it to
>> a usb drive, then boot to a terminal and copy it over..
>>
>> hope this gets you out of your fix..  been there.. Fred
>>
>>
>> --
>> Lots of soaring generalities, without a single hard fact in sight. Saves
>> the trouble of having to do research.
>> Fred/WD8KNI
>>
>> _______________________________________________
>> Leaplist mailing list
>> Leaplist at leap-cf.org
>> http://lists.leap-cf.org/mailman/listinfo/leaplist
>>
>>     
>
>
>   


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.