Of course.  I installed kmod-nvidia, booted to run level 3, and I've 
pasted the output of the commands you referenced below.

Linux xps 2.6.32-131.12.1.el6.x86_64 #1 SMP Tue Aug 23 11:13:45 CDT 2011 
x86_64 x86_64 x86_64
GNU/Linux

/lib/modules/2.6.32-131.12.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
/lib/modules/2.6.32-71.el6.x86_64/extra/nvidia/nvidia.ko
/lib/modules/2.6.32-131.6.1.el6.x86_64/weak-updates/nvidia/nvidia.ko

# 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,2)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_xps-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,2)/grub/splash.xpm.gz
#hiddenmenu
title Scientific Linux (2.6.32-131.12.1.el6.x86_64)
     root (hd0,2)
     kernel /vmlinuz-2.6.32-131.12.1.el6.x86_64 ro 
root=/dev/mapper/vg_xps-lv_root rd_LVM_LV=vg_xps/lv_root 
rd_LVM_LV=vg_xps/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet 
crashkernel=256M nouveau.modeset=0 rdblacklist=nouveau
     initrd /initramfs-2.6.32-131.12.1.el6.x86_64.img
title Scientific Linux (2.6.32-131.6.1.el6.x86_64)
     root (hd0,2)
     kernel /vmlinuz-2.6.32-131.6.1.el6.x86_64 ro 
root=/dev/mapper/vg_xps-lv_root rd_LVM_LV=vg_xps/lv_root 
rd_LVM_LV=vg_xps/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet 
crashkernel=256M
     initrd /initramfs-2.6.32-131.6.1.el6.x86_64.img
title Windows 7 Ultimate
     rootnoverify (hd0,0)
     chainloader +1

Kevin


On 09/10/2011 10:08 AM, Phil Perry wrote:
> On 10/09/11 06:36, Kevin Thomas wrote:
>> Ok, I jujst got a brand new Dell XPS laptop a few days ago. I managed to
>> install Windows 7 and SL 6.1 side by side in a dual boot setup. This
>> laptop has the core i7 processor, which means it has integrated Intel HD
>> 3000 graphics, but it also has a 2GB Nvidia GT540M (with optimus)
>> discrete card as well. I know that optimus is not natively supported
>> yet, but according to the SL forums, the generic nvidia driver can be
>> installed instead (kmod-nvidia). The instructions said to just do "yum
>> install kmod-nvidia". This installed the drivers for me and when I
>> rebooted, I saw the plymouth-rings splash screen for the first time
>> ever, but the system hung. I restarted again and pushed ESC to see the
>> messages and the screen flickered a few times and it stopped on
>> "registering binary handler for windows applications" Some googling
>> informed me that this was due to the wine service being enabled, so I
>> disabled it and restarted. This time, it got hung on "starting atd:" and
>> the screen flickered a few times. I have a feeling that if I disabled
>> atd, it would just hang on the next service. I had to uninstall the
>> kmod-nvidia package just to boot my system again. There has to be a way
>> to get the nvidia driver working. Any help would be appreciated.
>>
>> Kevin
>>
>
>
> In order to help troubleshoot, could you please provide some more 
> information. Please install kmod-nvidia and see if you can boot to 
> runlevel 3 and provide the following information (output from the 
> following commands):
>
> uname -a
> find /lib/modules -name nvidia.ko
> cat /boot/grub/grub.conf
>
> Thanks.