Hi all below ill post what i have done so far, after all that i still get a black screen after rebooting, so im runing on x11 failsafe.
Installed development tools and sources needed for nvidia kernel module build.
Checked what type of kernel i have and installed all the components below with all the dependencies they pull in.
uname -r
2.6.37.1-1.2-desktop
zypper install gcc make kernel-desktop-devel kernel-devel
Added nomodeset into /boot/grub/menu.lst
###Donāt change this comment - YaST2 identifier: Original name: linux###
title Desktop ā openSUSE 11.4 - 2.6.37.1-1.2
root (hd0,0)
kernel /boot/vmlinuz-2.6.37.1-1.2-desktop root=/dev/disk/by-id/ata-SAMSUNG_HD300LJ_S0D7J1UL503503-part1 resume=/dev/disk/by-id/ata-SAMSUNG_HD300LJ_S0D7J1UL503503-part4 splash=silent quiet showopts vga=0x346 nomodeset
initrd /boot/initrd-2.6.37.1-1.2-desktop
Set NO_KMS_IN_INITRD to Yes in /etc/sysconfig/kernel
grep NO_KMS_IN_INITRD /etc/sysconfig/kernel
NO_KMS_IN_INITRD=āyesā
Added blacklist nouveau to /etc/modprobe.d/50-blacklist.conf
grep nouveau /etc/modprobe.d/50-blacklist.conf
blacklist nouveau
Rebuild initrd and rebooted
mkinitrd
reboot
After reboot switched to run level 3, login as root (or as user and su to root)
init 3
login: root
password:
Install the NVIDIA driver, run nvidia-xconfig (the -X option) and reboot
Once the proprietary driver is built, there should be no need for nomodeset in the /boot/grub/menu.lst. In fact, that will likely make things worse after the proprietary driver is built and installed. Remove it.
Also, do you have any left over /etc/X11/xorg.conf file? If so, remove it (back it up some where).
Last time you took that off did you have Set NO_KMS_IN_INITRD to Yes in /etc/sysconfig/kernel ?
Note also ānomodesetā can always be applied as a grub boot code ā¦ ensuring a boot is still possible in case that kernel panic problem still exitis.
So tuguix, I do load the 64 bit nVIDIA proprietary video driver all of the time. I do normally add the nomodeset kernel command and the NO_KMS-IN_INITRD=yes and I have not been blacklisting the nouveau driver, but all seems to load OK for me. I must ask if this openSUSE 11.4 install is 32 or 64 bit, but based on the NVIDIA driver it looks to be 32 bit. The 64 bit driver is called NVIDIA-Linux-x86_64-260.19.44.run. Further, are you using KDE or the GNOME desktop? My suggestion is if you are able to run 64 bit software, then dump the 32 bit stuff which is not working for you and go 64 bit and then see what you get.
Jump up to the 270.xx beta. I think its up to at least 270.29. Get it from the Nvidia site and install it the hard way. I tried every suggestion on the entire internet to get 260.19 to work with my GS 7600 card and nothing helped. The 270.xx beta driver worked with none of the tweaks you are trying.
To uninstall the nVIDIA driver when loaded the hard way you would use the run option --uninstall in place of the -aqX you were using to install the driver.
YUPIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
The 270.26 beta drivers from nvidia work perfect, the 260.19.44 must have a bug.
Thank you all for your help guys, hope i can help you one of this days.
āThe fear from freedom makes you proud of being a slaveā
Linux forever!!!
The 260.19.xxx series caused major problems for 32-bit KDE users on openSUSE ā¦ where it was not clear if the problem was the nVidia 32-bit driver, KDE or openSUSE distro. A lot of frustrated users stated some very unpolite things about openSUSE for this claiming it HAD to be an openSUSE (and not KDE nor nVidia driver) problem. Search the forum and you will find some massive threads.
64-bit users, and most 32-bit KDE and LXDE and Xfce users did not have the problem.
Fortunately, as you discovered, the 270.xx series sorts this, although the 270.26 does NOT work for all, neither does the 270.29 work for all (it works for many). I have not read of any 270.30 complaints for this same problem, but there may be some.
Anyway, Iām glad to read the 270.26 (?? ) worked for you. If you find problems launching vlc, or amarok, or other apps (requiring something like āstrace vlcā) then consider the 270.30.
>
> tuguix;2308886 Wrote:
>> I wonder whatās wrong with the nvidia 260.19.44?
>> Any ideas?
>
> The 260.19.xxx series caused major problems for 32-bit KDE
users on
> openSUSE ā¦ where it was not clear if the problem was the
nVidia 32-bit
> driver, KDE or openSUSE distro. A lot of frustrated users
stated some
> very unpolite things about openSUSE for this claiming it
HAD to be an
> openSUSE (and not KDE nor nVidia driver) problem. Search
the forum and
> you will find some massive threads.
>
> 64-bit users, and most 32-bit KDE and LXDE and Xfce users
did not have
> the problem.
>
> Fortunately, as you discovered, the 270.xx series sorts
this, although
> the 270.26 does NOT work for all, neither does the 270.29
work for all
> (it works for many). I have not read of any 270.30
complaints for this
> same problem, but there may be some.
>
> Anyway, Iām glad to read the 270.26 (?? ) worked for you.
If you find
> problems launching vlc, or amarok, or other apps (requiring
something
> like āstrace vlcā) then consider the 270.30.
>
Iāve been running 270-18 with no problems on 64 bit. J went
to Nvidia website looking for 270-30. But cannot find it
under the beta drivers. Is there a link to it?
>
> upscope;2309420 Wrote:
>> Iāve been running 270-18 with no problems on 64 bit. J
went to Nvidia
>> website looking for 270-30. But cannot find it under the
beta drivers.
>> Is there a link to it?
>>
>
> Just look on the nVida news forum. Its a stickie. āCurrent
NVIDIA
> Linux graphics driver releases - nV News Forumsā
> (http://www.nvnews.net/vbulletin/showthread.php?t=122606)
and that
> leads one here: ā270.30 (beta) for Linux x86/x86_64
released - nV News
> Forumsā
(http://www.nvnews.net/vbulletin/showthread.php?p=2399427)
ā¦
> etc ā¦
>
Thanks
