Friday, December 31, 2010
uninterruptedly running program in the background but need enter password or something ?
For instance, wanna copy a big file, more than 10G, say, from remote host to local machine by a shell like :
scp -r user@hostname/ip:/home/data/bigdata /home/user/
but fearful of the interruption if the session will be terminated, so use nohup to achieve an interrupted execution to guard against being drawn to end due to the termination somehow of the current login session. by
nohup scp -r user@hostname/ip:/home/data/bigdata /home/user/
But most of the time you also want to lay this task go in the background since it should take a multitude of time to remote-copy a file as big as 10G, so change into
nohup scp -r user@hostname/ip:/home/data/bigdata /home/user/ &
By this point it comes what I want to share: you are guaranteed to run across an OOPS:
nohup: ignoring input and appending output to `nohup.out'
[1]+ Exit 1 nohup scp -r user@hostname/ip:/home/data/bigdata /home/user/
this is just because the process is suspended to receive a user input for password.
So there seemingly exists an ambivalent occasion here. By session controlling command, we can circumvent around this plausible dilemma:
nohup scp -r user@hostname/ip:/home/data/bigdata /home/user/
enter the password
CTRL+Z ( force the foreground process back to the background to run like a daemon )
[1] 3581
bg $jobid (you can see the jobid appearing after CTRL+Z, here it is 1)
Later if wanna change it back to run in the foreground, do it by
fg $jobid.
* you can also change the default output of nohup and include all the copying log into a self-defined log file by
nohup scp -r user@hostname/ip:/home/data/bigdata /home/user/ 1> bigdata.scp.log 2>&1
Restore Linux installation after installing Windows 7 which overwrote the MBR
By default Linux uses the grub Bootloader to manage OS booting with support of multiple OS, and this makes Linux, Fedora distribution say, really gentle as it is generous to keep its predecessors in the context of multiple boot of operating systems.
As such if you install Linux on top of current Windows system, the installer simply adds an boot item for the existing windows start up. It is not true the other way around, however!
When you install a Windows OS on top of current Linux, windows bootloader will not care about things already exist and bit of bluntly overwrite the grub bootloader thus make you lose the Linux boot.
Good news is there do be a way to remedy this loss, the marvellous guy I will be thankful to get the grub back is grub4dos.
Here we go from Windows 7!
1. Download grub4dos from sourceforge at http://sourceforge.net/projects/grub4dos/files/GRUB4DOS/grub4dos%200.4.4/grub4dos-0.4.4.zip/download
2. unpack and retrieve following files
glrdr
glrdr.mbr
menu.lst
place them under the root directory of the boot partition in Windows like C:\
3. expand a slot for the grub bootloader in current Windows bootloader (bootmgr) using bcdedit :
bcdedit /create /d "Grub4Dos" /application bootsector
note to record the id generated in the output.
then use this same id with following commands:
bcdedit /set {id} device partition=C:
bcdedit /set {id} path \grldr.mbr
bcdedit /displayorder {id} /addlast
bcdedit /set {id} path \grldr.mbr
bcdedit /displayorder {id} /addlast
As a result this will add an item for grub4dos in the Windows bootloader, so that we can boot Linux through grub4dos indirectly.
4. add boot item in the grub bootloader
edit menu.lst to make sure it contains item(s) for the "lost" Linux boot, it should seem like the example below:
default 0
timeout 3
hiddenmenu title Windows 7
find --set-root --ignore-floppies /bootmgr
chainloader /bootmgr
title Fedora (2.6.31.5-127.fc12.x86_64)
root (hd0,0)/boot
kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro root=/dev/sda1 LANG=zh_CN.UTF-8 KEYBOARDTYPE=pc
KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.x86_64.img
title fedora (2.6.32.21-168.fc12.x86_64)
root (hd0,0)/boot
kernel /vmlinuz-2.6.32.21-168.fc12.x86_64 ro root=/dev/sda1 LANG=zh_CN.UTF-8 KEYBOARDTYPE=pc
KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.32.21-168.fc12.x86_64.img
If you do not remember what the file names are such as initramfs-2.6.31.5-127.fc12.x86_64.img and vmlinuz-2.6.31.5-127.fc12.x86_64, esp. those other values like the stuff on the kernel line (" root=/dev/sda1 LANG=zh_CN.UTF-8 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet), you can
find a tool to look at the /boot/grub/grub.conf in the current Windows, a reliable one I have ever use is ext2fs which can be downloaded from http://www.chrysocome.net/explore2fs. For other similar tools, Google around with "ext file explorer for windows".
5. Now restart windows, in the boot menu, select "Grub4Dos" you will see the classical GRUB interface and you can select the Linux boot item with different kernel version therein. By this, we get Linux installation back and enjoy the dual or multiple boot at one host. In fact the Linux boot restoration steps described above is somewhat similar to that for fresh installation of Linux from Windows 7 without using a Boot CD/DVD.
How to restore or upgrade Fedora linux without losing user data at all
When you are inflicted with some faults of current Linux, the Fedora distribution, say, you might want to restore the OS kernel only without impairing all current user data even user applications installed after the previous installation, just like for Windows 2000/NT/XP/7, etc. there is a "restoring installation" option during the installation tour.
Just follow steps below to achieve this, given all your user data including configurations and profiles even history records like cookies, etc. are located at /home/user, and /home is mounted differently from the OS kernel and its legacy things. For example, you have "df -h" leading to output like following things:
/dev/sda1 99G 7.5G 86G 8% /
tmpfs 2.0G 468K 2.0G 1% /dev/shm
/dev/sda2 148G 70G 71G 50% /home
[ For upgrading to a higher version of Linux even to a different distribution, the guide below is just exactly suited ]
1. download and place installation package
a. get the OS installation image, Fedora-14-x86_64-DVD.iso, say from the official site
b. extract files and directories from the image and copy them to the partition holding data you want to keep, e.g. the /home at /dev/sda2 in this case
su
mkdir /mnt/fcinstall
mount -o loop -t iso9660 Fedora-14-x86_64-DVD.iso /mnt/fcinstall
cp -fr /mnt/fcinstall/isolinux/{vmlinuz,initrd.img} /mnt/fcinstall/images /home
mv Fedora-14-x86_64-DVD.iso /home
* you can also use some unpacking tool for extracting from ISO instead of using mount.
2. edit /boot/grub/grub.conf and add following :
(presuming current partition is (hd0, 0) in terms of (hard_drive, partition), corresponding to sda1 listed above in this case)
title fcinstall
root (hd0, 0)
kernel /vimlinuz
initrd /initrd.img
*this is to prepare for a boot item in the bootloader for reinstalling. You can either add a new item exclusively for this reinstallation like above
or just modify the bootloader item for the Linux in the current use,
3. keep everything you want to retain AWAY from the OS partition, for example, all stuff other than that are under /home/. if you have ever installed VirtualBox and created an virtual windows Xp image as the root account, you will need to :
move /root/.VirtualBox /home/user, say. this step is the first IMPORTANT really.
4. after ascertaining nothing missed on the /home partition as the user data to keep, restart now
5. following steps is verisimilar to the ordinary fresh installation of Linux, except certain cautions as follows:
a. at this step
CHOOSE "create custom layout"
b. in the partition editing interface,
choose /dev/sda1 to edit, and mount it onto "/", and format it. (it is advisable to format it since we want to a clean fresh installation not patching things up or left garbage there). Should format into "ext4" file system as well.
and, choose /dev/sda2 to edit, NOTE that just to mount it to /home and NEVER choose to format it, otherwise everything we are doing is just of no damn use and become meaningless! this is the second KEY step, i.e. the single most IMPORTANT step for your goal towards "restorative installation"
c. back to the partition interface and go next, then follow every step as the fresh installation until it is finished and restart again.
6.restore the user profile
Now create the user account you had before, /home/user for instance.
su
useradd -d /home/user -G user -p ****** -s /bin/bash user
By skipping the -m option, a skeleton profile will not be copied to /home/user, and we are to keep using original data all and get it associated with this restored user account as before.
if you like to use GUI, in the following interface
Mind you, do NOT choose "Create home directory".
(Actually after the reinstallation, you DO need a user account other than root to login the system, so just do it right there. The way I was doing is to create a temporary user account and then delete it just because I wan habituated to think of the command line operation then! )
7. Post restoration - Site clearing !
Now that we get a reinstalled linux and everything kept there just like before the restoration, we can safely remove the boot item for our recovery task.
- edit /boot/grub/grub.conf and remove what we added right now.
- unmount /mnt/fcinstall
- remove the installation image and boot bzImage we copied to /home/ before if you like. Surely you can simply keep them there in case we need another reinstallation afterwards, hope you will not be of that bad luck though :)
Now, you just are going to enjoy everything you have before, including the Desktop, gnome-terminal settings, Mozilla bookmarks even visit history, application (like VirtualBox and Windows Xp virtual OS, etc.) and .....
[ Other Notes ]
From this text, written from my definite practice (which is not so smooth at the time though), we should suggest that in the future use of Linux :
Install new application as into the user partition (or a single other partition than that for holding the OS itself) as possible. The same principles is applicable for data placement. In order to keep this consistency, you have better to designated "--prefix=/home/user/..." if you are to install some extraneous packages and modules by building the source code.
In a word, the more spread you anchored your data, the less handy to do a restorative installation being described.
Just follow steps below to achieve this, given all your user data including configurations and profiles even history records like cookies, etc. are located at /home/user, and /home is mounted differently from the OS kernel and its legacy things. For example, you have "df -h" leading to output like following things:
/dev/sda1 99G 7.5G 86G 8% /
tmpfs 2.0G 468K 2.0G 1% /dev/shm
/dev/sda2 148G 70G 71G 50% /home
[ For upgrading to a higher version of Linux even to a different distribution, the guide below is just exactly suited ]
1. download and place installation package
a. get the OS installation image, Fedora-14-x86_64-DVD.iso, say from the official site
b. extract files and directories from the image and copy them to the partition holding data you want to keep, e.g. the /home at /dev/sda2 in this case
su
mkdir /mnt/fcinstall
mount -o loop -t iso9660 Fedora-14-x86_64-DVD.iso /mnt/fcinstall
cp -fr /mnt/fcinstall/isolinux/{vmlinuz,initrd.img} /mnt/fcinstall/images /home
mv Fedora-14-x86_64-DVD.iso /home
* you can also use some unpacking tool for extracting from ISO instead of using mount.
2. edit /boot/grub/grub.conf and add following :
(presuming current partition is (hd0, 0) in terms of (hard_drive, partition), corresponding to sda1 listed above in this case)
title fcinstall
root (hd0, 0)
kernel /vimlinuz
initrd /initrd.img
*this is to prepare for a boot item in the bootloader for reinstalling. You can either add a new item exclusively for this reinstallation like above
or just modify the bootloader item for the Linux in the current use,
3. keep everything you want to retain AWAY from the OS partition, for example, all stuff other than that are under /home/. if you have ever installed VirtualBox and created an virtual windows Xp image as the root account, you will need to :
move /root/.VirtualBox /home/user, say. this step is the first IMPORTANT really.
4. after ascertaining nothing missed on the /home partition as the user data to keep, restart now
5. following steps is verisimilar to the ordinary fresh installation of Linux, except certain cautions as follows:
a. at this step
CHOOSE "create custom layout"
b. in the partition editing interface,
choose /dev/sda1 to edit, and mount it onto "/", and format it. (it is advisable to format it since we want to a clean fresh installation not patching things up or left garbage there). Should format into "ext4" file system as well.
and, choose /dev/sda2 to edit, NOTE that just to mount it to /home and NEVER choose to format it, otherwise everything we are doing is just of no damn use and become meaningless! this is the second KEY step, i.e. the single most IMPORTANT step for your goal towards "restorative installation"
c. back to the partition interface and go next, then follow every step as the fresh installation until it is finished and restart again.
6.restore the user profile
Now create the user account you had before, /home/user for instance.
su
useradd -d /home/user -G user -p ****** -s /bin/bash user
By skipping the -m option, a skeleton profile will not be copied to /home/user, and we are to keep using original data all and get it associated with this restored user account as before.
if you like to use GUI, in the following interface
(Actually after the reinstallation, you DO need a user account other than root to login the system, so just do it right there. The way I was doing is to create a temporary user account and then delete it just because I wan habituated to think of the command line operation then! )
7. Post restoration - Site clearing !
Now that we get a reinstalled linux and everything kept there just like before the restoration, we can safely remove the boot item for our recovery task.
- edit /boot/grub/grub.conf and remove what we added right now.
- unmount /mnt/fcinstall
- remove the installation image and boot bzImage we copied to /home/ before if you like. Surely you can simply keep them there in case we need another reinstallation afterwards, hope you will not be of that bad luck though :)
Now, you just are going to enjoy everything you have before, including the Desktop, gnome-terminal settings, Mozilla bookmarks even visit history, application (like VirtualBox and Windows Xp virtual OS, etc.) and .....
[ Other Notes ]
From this text, written from my definite practice (which is not so smooth at the time though), we should suggest that in the future use of Linux :
Install new application as into the user partition (or a single other partition than that for holding the OS itself) as possible. The same principles is applicable for data placement. In order to keep this consistency, you have better to designated "--prefix=/home/user/..." if you are to install some extraneous packages and modules by building the source code.
In a word, the more spread you anchored your data, the less handy to do a restorative installation being described.
How to copy all including hidden files or directories using linux shell
While copying all stuff under a directory into another place, by
cp $SRC/* $DST
will fail to copy all the hidden file (prefixing with ., the dot) in the end.
A foolproof way to achieve this is to go sinuously :
cp $SRC/* $SRC/.* $DST
there will come up with prompt like :
cp: omitting directory `$SRC/.'
cp: omitting directory `$SRC/..'
just turn back on it. having got thing done.
cp $SRC/* $DST
will fail to copy all the hidden file (prefixing with ., the dot) in the end.
A foolproof way to achieve this is to go sinuously :
cp $SRC/* $SRC/.* $DST
there will come up with prompt like :
cp: omitting directory `$SRC/.'
cp: omitting directory `$SRC/..'
just turn back on it. having got thing done.
Surfing Troves: Q&A for Oracle Distributed Database Application De...
Surfing Troves: Q&A for Oracle Distributed Database Application De...: "p { margin-bottom: 0.08in; }h2 { margin-bottom: 0.08in; }h2.western { font-family: 'Liberation Sans','Arial',sans-serif; font-size: 14pt; fo..."
Fedora Linux : can not see any icon on the desktop or the Gnome-Terminal configuration all grayed
This is simply because nautilus (Fedora file explorer/manager) failed to create the "Desktop" directory under $HOME of current the login user.
So to fix this, just manually create the directory by
mkdir -p $HOME/Desktop
logout and then log back in, both problems will get solved.
So to fix this, just manually create the directory by
mkdir -p $HOME/Desktop
logout and then log back in, both problems will get solved.
Thursday, December 30, 2010
Nvidia driver problems in Fedora Linux X86_64 - checking nvidia.ko failed or Segment fault in starting the drive module
1. for the first issue, however reinstalling the driver, updating by
nvidia-installer -a --update (internet access should be firstly ready)
or just copy the complained nvidia.ko file to the path that
the /etc/init.d/nvidia script searches, e.g. /lib/modules/$(uname -r)/kernel/drivers/video/nvidia. All seems no effect !
try to find the driver release of fedora for nvidia display driver :
yum list "*nvidia*" leads to a multitude of stuff related to the driver
----------------------
akmod-nvidia.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
akmod-nvidia-173xx.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
akmod-nvidia-96xx.x86_64 96.43.18-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-173xx.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-173xx-2.6.32.26-175.fc12.x86_64.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.17.fc12.x86_64.x86_64 190.53-1.fc12.3 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.19.fc12.x86_64.x86_64 190.53-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.22.fc12.x86_64.x86_64 190.53-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.3.fc12.x86_64.x86_64 190.53-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.5-127.fc12.x86_64.x86_64 190.42-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-145.fc12.x86_64.x86_64 190.42-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-162.fc12.x86_64.x86_64 190.42-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-166.fc12.x86_64.x86_64 190.42-1.fc12.8 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.9-174.fc12.x86_64.x86_64 190.53-1.fc12 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.10-90.fc12.x86_64.x86_64 1:195.36.15-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.11-99.fc12.x86_64.x86_64 1:195.36.15-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.12-114.fc12.x86_64.x86_64 1:195.36.24-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.12-115.fc12.x86_64.x86_64 1:195.36.24-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.14-127.fc12.x86_64.x86_64 1:195.36.31-1.fc12 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.16-141.fc12.x86_64.x86_64 1:195.36.31-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.16-150.fc12.x86_64.x86_64 1:195.36.31-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.19-163.fc12.x86_64.x86_64 1:195.36.31-1.fc12.3 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.21-166.fc12.x86_64.x86_64 1:195.36.31-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.23-170.fc12.x86_64.x86_64 1:195.36.31-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.26-175.fc12.x86_64.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.8-58.fc12.x86_64.x86_64 190.53-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.9-70.fc12.x86_64.x86_64 1:195.36.15-1.fc12 rpmfusion-nonfree-update
.................
just use the correct version for current kernel, for example
yum -y install kmod-nvidia-2.6.32.21-166.fc12.x86_64.x86_64
then go to /etc/init.d/, ./nvidia status, Got it !
2. when the problem got resolved as above, there comes another :
During the start-up, it reports as :
Enabling the nvidia driver: /etc/rc.d/init.d/functions: line $LINENO Segmentation fault "$@" (core dumped)....
For this one, Leight123Linux 's cure is really great, simple but definitely efficacious :
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.broken
nvidia-config-display disable
nvidia-config-display enable
see the source I consulted to :
http://forums.fedoraforum.org/archive/index.php/t-247152.html
Just this simple, the nasty problem got fixed up!
Thanks to Leigh123linux again for this useful tip!
[ For a complete guide for installing Nvidia Driver on Fedora Linux, here is a good reference at http://www.if-not-true-then-false.com/2010/fedora-14-nvidia-drivers-install-guide-disable-nouveau-driver/ ]
nvidia-installer -a --update (internet access should be firstly ready)
or just copy the complained nvidia.ko file to the path that
the /etc/init.d/nvidia script searches, e.g. /lib/modules/$(uname -r)/kernel/drivers/video/nvidia. All seems no effect !
try to find the driver release of fedora for nvidia display driver :
yum list "*nvidia*" leads to a multitude of stuff related to the driver
----------------------
akmod-nvidia.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
akmod-nvidia-173xx.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
akmod-nvidia-96xx.x86_64 96.43.18-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-173xx.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-173xx-2.6.32.26-175.fc12.x86_64.x86_64 173.14.27-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.17.fc12.x86_64.x86_64 190.53-1.fc12.3 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.19.fc12.x86_64.x86_64 190.53-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.22.fc12.x86_64.x86_64 190.53-1.fc12.5 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.12-174.2.3.fc12.x86_64.x86_64 190.53-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.5-127.fc12.x86_64.x86_64 190.42-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-145.fc12.x86_64.x86_64 190.42-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-162.fc12.x86_64.x86_64 190.42-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.6-166.fc12.x86_64.x86_64 190.42-1.fc12.8 rpmfusion-nonfree-updates
kmod-nvidia-2.6.31.9-174.fc12.x86_64.x86_64 190.53-1.fc12 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.10-90.fc12.x86_64.x86_64 1:195.36.15-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.11-99.fc12.x86_64.x86_64 1:195.36.15-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.12-114.fc12.x86_64.x86_64 1:195.36.24-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.12-115.fc12.x86_64.x86_64 1:195.36.24-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.14-127.fc12.x86_64.x86_64 1:195.36.31-1.fc12 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.16-141.fc12.x86_64.x86_64 1:195.36.31-1.fc12.1 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.16-150.fc12.x86_64.x86_64 1:195.36.31-1.fc12.2 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.19-163.fc12.x86_64.x86_64 1:195.36.31-1.fc12.3 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.21-166.fc12.x86_64.x86_64 1:195.36.31-1.fc12.4 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.23-170.fc12.x86_64.x86_64 1:195.36.31-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.26-175.fc12.x86_64.x86_64 1:195.36.31-1.fc12.7 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.8-58.fc12.x86_64.x86_64 190.53-1.fc12.6 rpmfusion-nonfree-updates
kmod-nvidia-2.6.32.9-70.fc12.x86_64.x86_64 1:195.36.15-1.fc12 rpmfusion-nonfree-update
.................
just use the correct version for current kernel, for example
yum -y install kmod-nvidia-2.6.32.21-166.fc12.x86_64.x86_64
then go to /etc/init.d/, ./nvidia status, Got it !
2. when the problem got resolved as above, there comes another :
During the start-up, it reports as :
Enabling the nvidia driver: /etc/rc.d/init.d/functions: line $LINENO Segmentation fault "$@" (core dumped)....
For this one, Leight123Linux 's cure is really great, simple but definitely efficacious :
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.broken
nvidia-config-display disable
nvidia-config-display enable
see the source I consulted to :
http://forums.fedoraforum.org/archive/index.php/t-247152.html
Just this simple, the nasty problem got fixed up!
Thanks to Leigh123linux again for this useful tip!
[ For a complete guide for installing Nvidia Driver on Fedora Linux, here is a good reference at http://www.if-not-true-then-false.com/2010/fedora-14-nvidia-drivers-install-guide-disable-nouveau-driver/ ]
Fedora Linux : Always got wrong IP configured
while the network configuration in the ifcfg-eth0 is as follows:
IPADDR=x.x.31.231
BROADCAST=x.255.255.255
NETWORK=x.x.31.0
NETMASK=255.255.255.0
GATEWAY=x.x.31.1
after /sbin/ifup eth0
/sbin/ifconfig eth0 displays a magic configuration as :
eth0 Link encap:Ethernet HWaddr xxxxxx
inet addr:x.x.35.200 Bcast:x.x.35.255 Mask:255.255.255.128
.........................
fiddling over and over (ifdown then ifup, and also including to restart network and NetManager services), just no damn a use! The system always applies this weird IP configuration !!
Finally, the bug got found by just "grep "x.x.35.200" /etc/sysconfig/network-scripts/* ", there is another file
ifcfg-reference there that contains this surprising configuration above.
Move this extraneous file, either deleting or moving to other directory, the problem got rid of !
IPADDR=x.x.31.231
BROADCAST=x.255.255.255
NETWORK=x.x.31.0
NETMASK=255.255.255.0
GATEWAY=x.x.31.1
after /sbin/ifup eth0
/sbin/ifconfig eth0 displays a magic configuration as :
eth0 Link encap:Ethernet HWaddr xxxxxx
inet addr:x.x.35.200 Bcast:x.x.35.255 Mask:255.255.255.128
.........................
fiddling over and over (ifdown then ifup, and also including to restart network and NetManager services), just no damn a use! The system always applies this weird IP configuration !!
Finally, the bug got found by just "grep "x.x.35.200" /etc/sysconfig/network-scripts/* ", there is another file
ifcfg-reference there that contains this surprising configuration above.
Move this extraneous file, either deleting or moving to other directory, the problem got rid of !
Linux : Access network service in Single user mode
1. Enter the Level 1 - Single User Mode
In the grub boot memu, select the entry for the OS you want to start up, press "e" to edit :
Just remove the tailing "rhgb quiet" and append " single" instead;
then press "b" to enter the single user mode.
2. In order to access the network service
most of the time, the reason why you might want to enter this level 1 mode is probably your failure to start up the Linux normally so you would want to use networking for downloading something, thus you should need network access, which is disabled by default in Level 1, single user mode
a. check the network device configuration to see if it is right there and the item agrees with your need or desire.
e.g. cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
NETWORK=
NETMASK=
IPADDR=
GATEWAY=
USERCTL=no
b. then start network service by
/sbin/service network start
c. if you run into problems like "Temporary failure in name resolution..." while you are going to download from a website, you should check the /etc/resolv.conf to see if there places at least one nameserver and the server is really reachable. if not, you should add like
nameserver x.x.x.x
nameserver x.x.x.x
if you do not know what to fill here after "nameserver", you can refer to other machine within the same domain as yours current which is available for network access.
(Sometimes, when you restarted the NetworkManager service, this name resolution configuration might also be cleared, then you will need to edit like above too).
d. to verify if it got fixed, try something like wget
wget www.google.com, for instance, it now works well if you can get the index.html from this site.
In the grub boot memu, select the entry for the OS you want to start up, press "e" to edit :
Just remove the tailing "rhgb quiet" and append " single" instead;
then press "b" to enter the single user mode.
2. In order to access the network service
most of the time, the reason why you might want to enter this level 1 mode is probably your failure to start up the Linux normally so you would want to use networking for downloading something, thus you should need network access, which is disabled by default in Level 1, single user mode
a. check the network device configuration to see if it is right there and the item agrees with your need or desire.
e.g. cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
NETWORK=
NETMASK=
IPADDR=
GATEWAY=
USERCTL=no
b. then start network service by
/sbin/service network start
c. if you run into problems like "Temporary failure in name resolution..." while you are going to download from a website, you should check the /etc/resolv.conf to see if there places at least one nameserver and the server is really reachable. if not, you should add like
nameserver x.x.x.x
nameserver x.x.x.x
if you do not know what to fill here after "nameserver", you can refer to other machine within the same domain as yours current which is available for network access.
(Sometimes, when you restarted the NetworkManager service, this name resolution configuration might also be cleared, then you will need to edit like above too).
d. to verify if it got fixed, try something like wget
wget www.google.com, for instance, it now works well if you can get the index.html from this site.
Wednesday, December 29, 2010
Surfing Troves: Can not find the cairo library or version is lower...
Surfing Troves: Can not find the cairo library or version is lower...: "One more prerequisite for GTK+, which might be complaining the lower version than required or simply loss of it: try to reinstall in the..."
Subscribe to:
Posts (Atom)