AOA Forums AOA Forums AOA Forums Folding For Team 45 AOA Files Home Front Page Become an AOA Subscriber! UserCP Calendar Memberlist FAQ Search Forum Home


Go Back   AOA Forums > Software > OS, Software, Firmware, and BIOS > Linux
Reload this Page I need help installing Nvidia driver in Fedora 11 64 bit please
Arcade FAQ Members List Social Groups Calendar Search Today's Posts Mark Forums Read

Linux Questions and information concerning Linux


Reply
Page 7 of 10 1 2 3 4 5 6 7 8 9 10
 
LinkBack Thread Tools Rate Thread
  #121 (permalink)  
Old 12th December, 2009, 06:35 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

[Daniel@localhost ~]$ su
Password:
[root@localhost Daniel]# mount /boot
mount: /dev/sda1 already mounted or /boot busy
mount: according to mtab, /dev/sda1 is already mounted on /boot
[root@localhost Daniel]# cd /boot/grub
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# sed 's/\(.*\)nouveau[^ ]* \(.*\)/\1\2/' < grub.conf | sed 's/\(.*\)vga[^ ]*\(.*\)/\1\2/' | sed 's_[[:space:]]kernel /vmlinuz.*_&nouveau.modeset=0 vga=0x307_' > grub.conf
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# yum install kernel-headers kernel-firmware kernel-devel
Loaded plugins: presto, refresh-packagekit
Setting up Install Process
Package kernel-firmware-2.6.31.6-166.fc12.noarch already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package kernel-devel.x86_64 0:2.6.31.6-166.fc12 set to be installed
---> Package kernel-headers.x86_64 0:2.6.31.6-166.fc12 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================== ==============================
Package Arch Version Repository Size
================================================== ==============================
Installing:
kernel-devel x86_64 2.6.31.6-166.fc12 updates 6.0 M
kernel-headers x86_64 2.6.31.6-166.fc12 updates 744 k

Transaction Summary
================================================== ==============================
Install 2 Package(s)
Upgrade 0 Package(s)

Total download size: 6.7 M
Is this ok [y/N]: y
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 6.7 M
(1/2): kernel-devel-2.6.31.6-166.fc12.x86_64.rpm | 6.0 MB 00:07
(2/2): kernel-headers-2.6.31.6-166.fc12.x86_64.rpm | 744 kB 00:01
--------------------------------------------------------------------------------
Total 704 kB/s | 6.7 MB 00:09
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : kernel-devel-2.6.31.6-166.fc12.x86_64 1/2
Installing : kernel-headers-2.6.31.6-166.fc12.x86_64 2/2

Installed:
kernel-devel.x86_64 0:2.6.31.6-166.fc12
kernel-headers.x86_64 0:2.6.31.6-166.fc12

Complete!
[root@localhost grub]#
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #122 (permalink)  
Old 12th December, 2009, 06:40 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

[root@localhost grub]# echo '#!/bin/bash' > /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo telinit 3 >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo '[ ! -d /root/nvidia-drivers ] && mkdir /root/nvidia-drivers' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo cd /root/nvidia-drivers >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo cp /home/Daniel/nvidia/NVIDIA-Linux-x86*pkg2.run . >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo chmod 500 NVIDIA-Linux-x86*pkg2.run >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo './$NVIDIA_DRIVERS --silent' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo reboot >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# chmod 700 /root/nv.sh
[root@localhost grub]#
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #123 (permalink)  
Old 12th December, 2009, 06:44 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo '#!/bin/bash' > /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo telinit 3 >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo cd /root/nvidia-drivers >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo './$NVIDIA_DRIVERS --uninstall' >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo reboot >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# chmod 700 /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo '[ `tty` = "/dev/tty2" ] && ./nv.sh' >>/root/.bashrc
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo '[ `tty` = "/dev/tty3" ] && ./nv-remove.sh' >> /root/.bashrc
[root@localhost grub]#
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #124 (permalink)  
Old 12th December, 2009, 06:56 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

Quote:
"It looks like it should be right. But as long as we are being cautious....su and run the following:

Code:

gedit /root/.bashrc /root/nv.sh /root/nv-remove.sh

Paste the contents of the 3 windows that gedit opens up back here so I can see them.
( ONLY TWO WINDOWS!)

# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
[ `tty` = "/dev/tty2" ] && ./nv.sh
[ `tty` = "/dev/tty3" ] && ./nv-remove.sh


sage bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

(gedit:2585): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gedit:2585): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 12th December, 2009 at 06:59 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #125 (permalink)  
Old 12th December, 2009, 07:19 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

Quote:
Originally Posted by Gizmo View Post
Loading the drivers before shutdown will not have any effect. If you are getting a blank grub screen, it's because grub isn't understanding the grub.conf file, so I need you to paste the contents of /boot/grub/grub.conf after running the commands I gave above so I can look at it.
Ah... I don't know where this is located or how to get it....
Attached Thumbnails
I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot.png  
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 12th December, 2009 at 07:24 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #126 (permalink)  
Old 12th December, 2009, 07:52 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

su and:
Code:
gedit /boot/grub/grub.conf
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #127 (permalink)  
Old 12th December, 2009, 08:23 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

NG! NG! Not good NOT GOOD!!
Attached Thumbnails
I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot-1.png  
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 12th December, 2009 at 08:23 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #128 (permalink)  
Old 12th December, 2009, 08:47 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Hmm......looks like your boot partition isn't mounted.

su and then do this:
Code:
mount /boot
gedit /boot/grub/grub.conf /root/nv.sh /root/nv-remove.sh
Show me the contents of all three windows.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #129 (permalink)  
Old 12th December, 2009, 09:25 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

Still just two windows...
Attached Thumbnails
I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot.png   I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot-1.png  
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #130 (permalink)  
Old 12th December, 2009, 10:13 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Can you restore your just your boot partition (the first partition on the drive) without having to restore your entire Fedora install? Somehow, your grub.conf file is being destroyed.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #131 (permalink)  
Old 12th December, 2009, 10:26 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

stupid, Stupid, STUPID! (not you, me)

Ok, once you get your system back to a state where you can boot it, run the following:

Code:
mount /boot
cd /boot/grub
sed 's/\(.*\)nouveau[^ ]* \(.*\)/\1\2/' < grub.conf | sed 's/\(.*\)vga[^ ]*\(.*\)/\1\2/' | sed 's_[[:space:]]kernel /vmlinuz.*_&nouveau.modeset=0 vga=0x307_' > test.conf
cp -p grub.conf grub.conf.giz-bak
cp test.conf grub.conf
gedit /boot/grub/grub.conf /root/nv.sh /root/nv-remove.sh
When gedit pops up, post back the contents of each of the three tabs (I said 'windows' earlier, and meant 'tabs'; you really should learn to read my mind better....)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #132 (permalink)  
Old 12th December, 2009, 10:48 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

This means a restore? My heart bleeds and I question my resolve to go on! LOL

Ok So I restore, then do the latest code BEFORE doing any of the previous code and report back... I'm rebooting now and most likely doing the needed restore, this gives you about 2 hours to get my **** together...LOL

WAIT after the restore I'll have to do a Fedora update to the latest kernel, last night that was 4 hours, but I have a lot of **** for you to get together so that should work out OK! ":O}
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 12th December, 2009 at 10:50 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #133 (permalink)  
Old 12th December, 2009, 11:15 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

No need to hurry, as my wife has informed me that I AM GOING TO TAKE HER TO DINNER AND A MOVIE THIS EVENING (the capital letters came from her, not me). That means that in about 3 hours I'm going to be incommunicado for about 4 more hours.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #134 (permalink)  
Old 13th December, 2009, 12:44 AM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

A really fast update this time, 5 mins. pushing your last code into place now.":O}
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #135 (permalink)  
Old 13th December, 2009, 12:51 AM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

I answered "y" after missing the question the firs time, I saved the changes offered in gedit before closing. I'll await further instructions upon your return...Enjoy your self or pretend to for the sake of your marriage! ":O}
Attached Thumbnails
I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot.png   I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot-1.png  
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 13th December, 2009 at 12:55 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #136 (permalink)  
Old 13th December, 2009, 01:09 AM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

Good news: It boots fine and fast.

ODD news: it boots by first showing a screen with 4 rather large Linux penguins beneath which a screen full of information that goes by to fast to read, followed by screen wide series of yellow vertical lines each about a 1/4 inch wide, going half way down the monitor screen , then the screen flips and enters the "normal boot" that I'm use to seeing... I kid you Not!
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 13th December, 2009 at 01:18 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #137 (permalink)  
Old 13th December, 2009, 01:43 AM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Err...........there shouldn't have been a need to SAVE anything. Everything was already saved. su and run the code below:

Code:
gedit /boot/grub/grub.conf /root/nv.sh /root/nv-remove.sh
When the text editor opens up, I need for you to show me the text from each tab in turn. You can simply copy and paste, no need to do a screen shot unless that is easier for you.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #138 (permalink)  
Old 13th December, 2009, 04:07 AM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

Here ya go!
Attached Thumbnails
I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot.png   I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot-1.png   I need help installing Nvidia driver in Fedora 11 64 bit please-screenshot-2.png  
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Last edited by Daniel ~; 13th December, 2009 at 04:10 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #139 (permalink)  
Old 13th December, 2009, 06:06 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion 		 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Ok. su, run this code, and show me the output from it:

Code:
#make sure that /boot is available
mount /boot
cd /boot/grub
#restore from backup, if it exists.
echo y | cp grub.conf.giz-bak grub.conf
#now make a backup, in case it doesn't exist
echo y | cp grub.conf grub.conf.giz-bak
#fix grub.conf to include nouveau.modeset=0 and vga=0x307
#bearing in mind that they might already be there
sed 's/\(.*\)nouveau[^ ]* \(.*\)/\1\2/' < grub.conf.giz-bak | sed 's/\(.*\)vga[^ ]*\(.*\)/\1\2/' | sed 's_[[:space:]]kernel /vmlinuz.*_& nouveau.modeset=0 vga=0x307_' > grub.conf
#make the nv.sh shell script in /root so that Daniel
#can compile the nvidia drivers
echo '#!/bin/bash' > /root/nv.sh
echo telinit 3 >> /root/nv.sh
echo '[ ! -d /root/nvidia-drivers ] && mkdir /root/nvidia-drivers' >> /root/nv.sh
echo cd /root/nvidia-drivers >> /root/nv.sh
echo 'cp /home/Daniel/nvidia/NVIDIA-Linux-x86*pkg2.run .' >> /root/nv.sh
echo chmod 500 NVIDIA-Linux-x86*pkg2.run >> /root/nv.sh
echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv.sh
echo './$NVIDIA_DRIVERS --silent' >> /root/nv.sh
echo reboot >> /root/nv.sh
chmod 700 /root/nv.sh
#make the nv-remove.sh shell script in /root so that Daniel
echo '#!/bin/bash' > /root/nv-remove.sh
echo telinit 3 >> /root/nv-remove.sh
echo cd /root/nvidia-drivers >> /root/nv-remove.sh
echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv-remove.sh
echo './$NVIDIA_DRIVERS --uninstall' >> /root/nv-remove.sh
echo reboot >> /root/nv-remove.sh
chmod 700 /root/nv-remove.sh
#hardwire the second vconsole to build the drivers as soon as root logs in
echo '[ `tty` = "/dev/tty2" ] && ./nv.sh' >>/root/.bashrc
#hardwire the third vconsole to remove the drivers as soon as root logs in
echo '[ `tty` = "/dev/tty3" ] && ./nv-remove.sh' >> /root/.bashrc

cat grub.conf
cat /root/nv.sh
cat /root/nv-remove.sh
cat /root/.bashrc
Last edited by Gizmo; 13th December, 2009 at 07:46 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #140 (permalink)  
Old 13th December, 2009, 06:50 PM
Daniel ~'s Avatar
Chief BBS Administrator
  
Join Date: September 2001
Location: Seattle Wa.
Posts: 45,606

I didn't actually have to enter every line of this did I ?? ":O}

[Daniel@localhost ~]$ su
Password:
[root@localhost Daniel]# cd /boot/grub
[root@localhost grub]# #restore from backup, if it exists.
[root@localhost grub]#
[root@localhost grub]# cp grub.conf.giz-bak grub.conf
cp: overwrite `grub.conf'? y
[root@localhost grub]#
[root@localhost grub]# #now make a backup, in case it doesn't exist
[root@localhost grub]# cp grub.conf grub.conf.giz-bak
cp: overwrite `grub.conf.giz-bak'? y
[root@localhost grub]#
[root@localhost grub]# #fix grub.conf to include nouveau.modeset=0 and vga=0x307
[root@localhost grub]#
[root@localhost grub]# #bearing in mind that they might already be there
[root@localhost grub]#
[root@localhost grub]# mount /boot
mount: /dev/sda1 already mounted or /boot busy
mount: according to mtab, /dev/sda1 is already mounted on /boot
[root@localhost grub]#
[root@localhost grub]# sed 's/\(.*\)nouveau[^ ]* \(.*\)/\1\2/' < grub.conf.giz-bak | sed 's/\(.*\)vga[^ ]*\(.*\)/\1\2/' | sed 's_[[:space:]]kernel /vmlinuz.*_& nouveau.modeset=0 vga=0x307_' > grub.conf
[root@localhost grub]#
[root@localhost grub]# #make the nv.sh shell script in /root so that Daniel #can compile the nvidia drivers
[root@localhost grub]# #make the nv.sh shell script in /root so that Daniel #can compile the nvidia drivers
[root@localhost grub]# echo '#!/bin/bash' > /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo telinit 3 >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo '[ ! -d /root/nvidia-drivers ] && mkdir /root/nvidia-drivers' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo cd /root/nvidia-drivers >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo 'cp /home/Daniel/nvidia/NVIDIA-Linux-x86*pkg2.run .' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo chmod 500 NVIDIA-Linux-x86*pkg2.run >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# echo './$NVIDIA_DRIVERS --silent' >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# echo reboot >> /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# chmod 700 /root/nv.sh
[root@localhost grub]#
[root@localhost grub]# #make the nv-remove.sh shell script in /root so that Daniel
[root@localhost grub]# echo '#!/bin/bash' > /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]# echo telinit 3 >> /root/nv-remove.sh
[root@localhost grub]# echo cd /root/nvidia-drivers >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]# echo 'NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '\''{print $8}'\'')' >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]# echo './$NVIDIA_DRIVERS --uninstall' >> /root/nv-remove.sh
[root@localhost grub]# echo reboot >> /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]# chmod 700 /root/nv-remove.sh
[root@localhost grub]#
[root@localhost grub]# #hardwire the second vconsole to build the drivers as soon as root logs in
[root@localhost grub]#
[root@localhost grub]# echo '[ `tty` = "/dev/tty2" ] && ./nv.sh' >>/root/.bashrc
[root@localhost grub]#
[root@localhost grub]# #hardwire the second vconsole to build the drivers as soon as root logs in
[root@localhost grub]#
[root@localhost grub]# echo '[ `tty` = "/dev/tty2" ] && ./nv.sh' >>/root/.bashrc
[root@localhost grub]#
[root@localhost grub]# #hardwire the third vconsole to remove the drivers as soon as root logs in
[root@localhost grub]#
[root@localhost grub]# echo '[ `tty` = "/dev/tty3" ] && ./nv-remove.sh' >> /root/.bashrc
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# cat grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root nouveau.modeset=0 vga=0x307
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.6-166.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.31.6-166.fc12.x86_64 ro root=/dev/mapper/VolGroup-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nouveau.modeset=0 vga=0x307
initrd /initramfs-2.6.31.6-166.fc12.x86_64.img
title Fedora (2.6.31.6-145.fc12.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.31.6-145.fc12.x86_64 ro root=/dev/mapper/VolGroup-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nouveau.modeset=0 vga=0x307
initrd /initramfs-2.6.31.6-145.fc12.x86_64.img
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# cat /root/nv.sh
#!/bin/bash
telinit 3
[ ! -d /root/nvidia-drivers ] && mkdir /root/nvidia-drivers
cd /root/nvidia-drivers
cp /home/Daniel/nvidia/NVIDIA-Linux-x86*pkg2.run .
chmod 500 NVIDIA-Linux-x86*pkg2.run
NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '{print $8}')
./$NVIDIA_DRIVERS --silent
reboot
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# cat /root/nv-remove.sh
#!/bin/bash
telinit 3
cd /root/nvidia-drivers
NVIDIA_DRIVERS=$(ls -alt NVIDIA-Linux-x86*-pkg2.run | head -n 1 | awk '{print $8}')
./$NVIDIA_DRIVERS --uninstall
reboot
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]# cat /root/.bashrc
# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
[ `tty` = "/dev/tty2" ] && ./nv.sh
[ `tty` = "/dev/tty2" ] && ./nv.sh
[ `tty` = "/dev/tty3" ] && ./nv-remove.sh
[root@localhost grub]#
[root@localhost grub]#
[root@localhost grub]#
__________________
"Though all men live in ignorance before mystery,
they need not live in darkness...
Justice is foundation and Mercy ETERNAL."
DKE
"All that we do is touched by Ocean
Yet we remain on the shore of what we know."
Richard Wilbur

[img]/forum/attachments/random-nonsense/16515-sigs-dan_drag.jpg[/img]
Subscribers! Ask Pitch about a Custom Sig Graphic

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply
Page 7 of 10 1 2 3 4 5 6 7 8 9 10

Tags
driver , fedora 12 , install , linux , nvidia


« XBMC 9.11 makes your open source home theater look shinier | Installing Adobe Flash Player 10 on Fedora Linux 64-bit with Firefox 64-bit »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Installing Adobe Flash Player 10 on Fedora Linux 64-bit with Firefox 64-bit Gizmo Linux 33 1st January, 2010 08:57 PM
Installing Fedora dabaerman Linux 25 27th January, 2009 04:03 AM
Linux (FEDORA 4) and GeForce Driver! saquib Graphics and Sound cards; Speakers and other Peripherals 3 22nd October, 2005 05:47 PM
loading nVidia drivers on Fedora 3 dolanenwindrift OS, Software, Firmware, and BIOS 0 15th January, 2005 04:44 PM
WinXP Driver Update- Nvidia Corporation Media Driver Version 5.10.2906.0 Pablo Escobar EPoX MotherBoards 1 9th December, 2002 08:47 PM


All times are GMT +1. The time now is 09:13 PM.

Contact Us - AOA Front Page - Privacy Statement - Terms of Service - Top

Copyright ©2001 - 2023, AOA Forums
Don't Click Here Don't Click Here Either

Search Engine Friendly URLs by vBSEO 3.3.0