Skip to main content

Nvidia drivers on Lenovo T520

Update: Unless you are playing games or something, I see no reason to use the Nvidia drivers.  After I installed the Nvidia drivers the external display was not auto-detected and required a restart of Gnome-shell to recognize the updated config.  Once I did that, it started in Gnome-fallback mode?  Bummer...  So - nouveau is the better option... IMO.

I had decided to put Fedora 16 back on my rig.  I know this install won't be on this machine long as it has some quirky issues (sudden desktop lockups, WLAN occasionally flakes out, etc... I digress...)  I also decided to try the Nvidia proprietary driver, along with using the discrete Nvidia graphics chipset.

So - the process was fairly straight-forward.

# yum -y update
# rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
# rpm -Uvh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
# yum install akmod-nvidia xorg-x11-drv-nvidia-libs
# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
# dracut /boot/initramfs-$(uname -r).img $(uname -r)

update /etc/default/grub
GRUB_CMDLINE_LINUX="rd.lvm.lv=vg_neo/lv_swap rd.md=0 rd.dm=0  KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_neo/lv_root LANG=en_US.UTF-8"
to include the 2 nouveau entries
GRUB_CMDLINE_LINUX="rd.lvm.lv=vg_neo/lv_swap rd.md=0 rd.dm=0  KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_neo/lv_root LANG=en_US.UTF-8 rdblacklist=nouveau nouveau.modeset=0"

# grub2-mkconfig -o /boot/grub2/grub.cfg

Reboot your Lenovo and press the ThinkVantage button when it asks, press F1 to edit BIOS settings.
go into Config | Display
I changed it to the Discrete Value, disabled the OS detect Optimus
When you now boot you should notice immediately that your grub has higher resolution.

Otherwise everything else seems the same.  But...

Using Nouveau I would get around 60FPS using glxgears...
Using Nvidia ...
[jradtke@neo bin]$ glxgears
30718 frames in 5.0 seconds = 6143.429 FPS
30892 frames in 5.0 seconds = 6178.211 FPS

It will actually drive the machine enough to have the fan spin up.  Was this worth the 30 minutes I devoted to this?  Probably not - as I am fairly certain that my external monitor will no longer work using this driver and my battery life will be diminished... but GLXgears rocks now. ;-)

Comments

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un