Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
There is some sort of bug with my nVidia 7800GT that causes the graphic installer to load up artifacted, frozen, and jumbled. So instead, I did a text-based install. After rebooting, I went straight to a command line, and I found out that I had to modify /etc/inittab so that the default runlevel is 5. I did that, rebooted, and the Fedora load screen came up artifacted and frozen as with Anaconda.
I then started all over, but this time, after changing the default runlevel, I edited /etc/X11/xorg.conf and replaced the video device driver field from nv to vesa. I rebooted and could achieve the log in screen, but I had expected the initial setup program in which I create an account to run, and it didn't. I assume this is because I had already booted once to change xorg.conf and inittab. I can only log in as root, and none of the options that the first time boot program configures were set. Does anyone know how to manually start this utility?
In the mean time, I am trying to install nVidia's drivers so that I don't waste my 7800GT with vesa drivers. I downloaded the latest linux drivers from the nVidia website, copied them to my HD, and switched back to runlevel 3 because the driver installation requires X to be disabled. I entered sh <whateverdrivernamewas>.rpm, but I recieved an error saying that the installer needed to compile an interface with the kernel of some sort. I then downloaded the correct kernel source RPM from the Fedora FTP and rebooted. I entered rpm -Uvh <kernelname>.rpm, and consequently recieved an error that looked something like this:
Failed dependencies: /usr/sbin/hardlink is needed by kernel-devel-blahblahblah.rpm
Note: I also recieved a warning concerning a signature of some sort, but I have since learned that the --nosignature switch will override this.
I am at my nerves' end right now. Am I using the wrong switches when attempting to install the kernel sources? I hope someone knows what is going on here and can provide me with a solution. My linux knowledge is limited... any help would be greatly appreciated. Next up: the nightmare of getting my Linksys WMP54GX wireless PCI adapter to function on FC5. Sigh.
Also, I had devel and source mixed up... but I did install devel after I found the hardlink rpm.
New problem though:
I'll try to post the exact error, but the nvidia script claimed it could not successfully build nvidia.ko for a number of possible reasons. I'm going to boot back up into linux and write down that message... can't find my USB pendrive, d'oh.
No fix is necessary. The FC5 kernel is compiled with the distributed gcc, which is what he should be using to install the nvidia driver. If he is getting a mismatch, then the system is in a weird, partially updated state, or using files from conflicting repositories. In either case, the system is in an unstable state.
I've only seen this when folks perform a base install (from CD/DVD), then add and enable a bunch of repositories, then perform an update.
Mace, my issue is that I have yet to configure my wireless adapter, and therefore cannot use any network services. I am relying on booting up windows, burning resources to a CDRW, and booting back into Fedora.
I only disabled SELinux after first recieving that dependency error. I have now reenabled it, and used these commands from stanton-finley.net's FC5 installation notes:
To prevent SElinux problems with the ATI fglrx or nVidia modules type the following in the root terminal:
setsebool -P allow_execstack=1
Hit enter. Also type:
setsebool -P allow_execmod=1
Hit enter. Reboot your machine. Your ATI fglrx or nVidia drivers should be enabled after you reboot.
Even after using those commands, which I have seen numerous times after googling the dependency error, I still recieve said error.
If you believe the error is SELinux related, you can:
1. setenforce 0
2. run the nvidia installation
3. setenforce 1
The setenforce command temporarily tells SELinux not to enforce violations (it still logs them). Disabling SELinux can cause other problems - files are no longer tagged properly, so when SELinux is re-enabled, access violations can occur. Using setenforce does not cause that problem.