Hi all,
I have an 64 bit based laptop with openSuse 11.3 KDE installed on it, my grafic card is a Geforce GT330M and I have the last official drivers from Nvidia installed Version: 260.19.29
My problem is that I have always freezes of the system that allow me to move the mouse, but I cannot do anything more.
Anyone can help me ?
Thanks
Hi all,
I have an 64 bit based laptop with openSuse 11.3 KDE installed on it, my grafic card is a Geforce GT330M and I have the last official drivers from Nvidia installed Version: 260.19.29
My problem is that I have always freezes of the system that allow me to move the mouse, but I cannot do anything more.
Anyone can help me ?
Thanks
This sounds like a hardware problem, but can be caused by a driver problem. When you say you installed the nVidia proprietary video driver, how did you install it? Did you load the nVidia driver the hard way? Did you add the kernel option **nomodeset **to your Grub menu.lst file? Did you set the kernel option NO_KMS_IN_INITRD = Yes in the /etc/sysconfig Editor? Finally, what is your present kernel version? Have you loaded the most recent kernel updates for openSUSE 11.3?
Thank You,
I’m not really sure want the hard way means, but think that’s what I did…. I downloaded the file and simply executed the *.run file. I didn’t add any option in the menu.lst file and to the /etc/sysconfig . My kernel version is 2.6.34.7-0.5
thanks
So, in order to install the nVidia driver and get it to work, you must add the nomodeset kernel load option in your grub menu.lst file. Here is an example from my menu.lst file.
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.7-0.5
savedefault 3
root (hd0,1)
kernel /boot/vmlinuz-2.6.34.7-0.5-desktop root=/dev/disk/by-id/ata-WDC_WD6000HLHX-01JJPV0_WD-WXA1C20K0415-part2 resume=/dev/disk/by-id/ata-WDC_WD6000HLHX-01JJPV0_WD-WXA1C20K0415-part1 splash=silent quiet **nomodeset **showopts vga=0x346
initrd /boot/initrd-2.6.34.7-0.5-desktop
To edit this file using KDE I would enter the menu Run Command:
kdesu kwrite /boot/grub/menu.lst
To just look, you can open a terminal session and type:
cat /boot/grub/menu.lst
To set the NO_KMS_IN_INITRD = Yes, open YaST / System / etc/sysconfig Editor / System / Kernel / NO_KMS_IN_INITRD change to Yes and press OK in bottom right. Reboot when done for these to take effect. I can say that I did not think you could even load the nVidia driver if the nomodeset command was not used in your menu.lst file.
Thank You,
jdmcdaniel3 wrote:
>
> So, in order to install the nVidia driver and get it to work, you must
> add the nomodeset kernel load option in your grub menu.lst file. Here
> is an example from my menu.lst file.
>
>
> Code:
> --------------------
> ###Don’t change this comment - YaST2 identifier: Original name:
> ###linux###
> title Desktop – openSUSE 11.3 - 2.6.34.7-0.5
> savedefault 3
> root (hd0,1)
> kernel /boot/vmlinuz-2.6.34.7-0.5-desktop
> root=/dev/disk/by-id/ata-WDC_WD6000HLHX-01JJPV0_WD-WXA1C20K0415-
part2
> resume=/dev/disk/by-id/ata-WDC_WD6000HLHX-01JJPV0_WD-WXA1C20K0415-
part1
> splash=silent quiet *nomodeset *showopts vga=0x346 initrd
> /boot/initrd-2.6.34.7-0.5-desktop
> --------------------
> To edit this file using KDE I would enter the menu Run Command:
>
>
> Code:
> --------------------
> kdesu kwrite /boot/grub/menu.lst
> --------------------
> To just look, you can open a terminal session and type:
>
>
> Code:
> --------------------
> cat /boot/grub/menu.lst
>
> --------------------
> To set the NO_KMS_IN_INITRD = Yes, open YaST / System / etc/sysconfig
> Editor / System / Kernel / NO_KMS_IN_INITRD change to Yes and press OK
> in bottom right. Reboot when done for these to take effect. I can
> say that I did not think you could even load the nVidia driver if the
> nomodeset command was not used in your menu.lst file.
>
> Thank You,
>
I have 11.3 and I do not have NOMODESET in my grub menu. I run the
Nvidia 260-19-21 driver installed from YaST and the Nvidia Repo. I do
have No_KMS set to yes. I experience a slight delay at times when
Desktop Effects is enabled. Have not had time to look into it.
–
Russ
openSUSE 11.3 (2.6.34.7-0.5-default)|KDE 4.5.3 Release 10|
Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS
I have 11.3 and I do not have NOMODESET in my grub menu. I run the
Nvidia 260-19-21 driver installed from YaST and the Nvidia Repo. I do
have No_KMS set to yes. I experience a slight delay at times when
Desktop Effects is enabled. Have not had time to look into it.
–
Russ
Russ, while your PC does not go up in flames without the **nomodeset command, it is still recommended if you are loading the nVidia proprietary binary video driver to use this kernel load option. I found this explanation of the nomodeset **command:
> What is “nomodeset” SUPPOSED to do?
The newest kernels have (God knows why) moved the video
mode setting into the kernel (the only explanation I’ve
ever seen for why this is a good idea is that the monitor
goes “click” less often that way). So all the programming
of the hardware specific clock rates and registers on the
video card happen in the kernel during initial boot
rather than in the X driver when the X server starts.
(And the X driver developers hate having to deal with
both possibilities, so they’d really like no one to ever
use nomodeset).
The “nomodeset” kernel parameter turns off this feature
and leaves the system BIOS video setting in place during
boot.
Because the kernel may need the video driver loaded to
do mode setting, the nouveau driver is probably included
in the initrd image, hence the need for both “nomodeset”
and “rdblacklist=nouveau” to keep the kernel out of the
video mode business so the binary nvidia driver can
then do mode setting when X starts with no conflicting
drivers loaded in the kernel.
Thanks Steven P. Ulrick for your explanation of nomodeset. Following is a note from the nVidia HOWTO on installing their driver the hard way:
NOTE: The nvidia installer does not work as long as a Xserver is still
running and the nvidia kernel module is still loaded. Therefore
please boot into runlevel 3 by specifying “3” as kernel boot
option or switch to runlevel 3 (“init 3”) and unload the kernel
module (“rmmod nvidia”) before running the nvidia installer.
Since openSUSE 11.3 use “nomodeset” as additional kernel boot
option.
Here is a excerpt from the openSUSE 11.3 release notes:
Initializing Graphics with KMS (Kernel Mode Setting)
With openSUSE 11.3 we are switching to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding **nomodeset **to the kernel boot command line. To set this permanently, add it to the kernel command line in /boot/grub/menu.lst. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with modeset=0 in initrd, i.e. KMS is disabled. In the rare cases when loading the DRM module from initrd is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module in initrd completely. For this set the NO_KMS_IN_INITRD sysconfig variable to yes via YAST, which then recreates initrd afterwards. Reboot your machine. On Intel without KMS the Xserver falls back to the fbdev driver (the intel driver only supports KMS). On ATI for current GPUs it falls back to radeonhd. On NVIDIA without KMS the nv driver is used (the nouveau driver only supports KMS).
And the best part about using nomodeset is, it costs nothing to use and follows the suggestions of many experts on the subject.
Thank You,
jdmcdaniel3 wrote:
>
>> I have 11.3 and I_do_not_have_NOMODESET_in_my_grub_menu. I run
>> the Nvidia 260-19-21 driver installed from YaST and the Nvidia Repo.
>> I do have No_KMS set to yes. I experience a slight delay at times
>> when Desktop Effects is enabled. Have not had time to look into it.
>>
>> –
>> RussRuss, while your PC does not go up in flames without the
>> *nomodeset
> command, it is still recommended if you are loading the nVidia
> proprietary binary video driver to use this kernel load option. I
> found this explanation of the nomodeset *command:
>
>> > What is “nomodeset” SUPPOSED to do?
>>
>> The newest kernels have (God knows why) moved the video
>> mode setting into the kernel (the only explanation I’ve
>> ever seen for why this is a good idea is that the monitor
>> goes “click” less often that way). So all the programming
>> of the hardware specific clock rates and registers on the
>> video card happen in the kernel during initial boot
>> rather than in the X driver when the X server starts.
>> (And the X driver developers hate having to deal with
>> both possibilities, so they’d really like no one to ever
>> use nomodeset).
>>
>> The “nomodeset” kernel parameter turns off this feature
>> and leaves the system BIOS video setting in place during
>> boot.
>>
>> Because the kernel may need the video driver loaded to
>> do mode setting, the nouveau driver is probably included
>> in the initrd image, hence the need for both “nomodeset”
>> and “rdblacklist=nouveau” to keep the kernel out of the
>> video mode business so the binary nvidia driver can
>> then do mode setting when X starts with no conflicting
>> drivers loaded in the kernel.Thanks Steven P. Ulrick for your
>> explanation of nomodeset. Following
> is a note from the nVidia HOWTO on installing their driver the hard
> way:
>
>> NOTE: The nvidia installer does not work as long as a Xserver is
>> still running and the nvidia kernel module is still loaded. Therefore
>> please boot into runlevel 3 by specifying “3” as kernel boot
>> option or switch to runlevel 3 (“init 3”) and unload the kernel
>> module (“rmmod nvidia”) before running the nvidia installer.
>> Since openSUSE 11.3 use “nomodeset” as additional kernel boot
>> option.
>> Here is a excerpt from the openSUSE 11.3 release notes:
>
>> INITIALIZING GRAPHICS WITH KMS (KERNEL MODE SETTING)
>> With openSUSE 11.3 we are switching to KMS (Kernel Mode Setting)
>> for Intel, ATI and NVIDIA graphics, which now is our default. If you
>> encounter problems with the KMS driver support (intel, radeon,
>> nouveau), disable KMS by adding *nomodeset *to the kernel boot
>> command line. To set this permanently, add it to the kernel command
>> line in /boot/grub/menu.lst. This option makes sure the appropriate
>> kernel module (intel, radeon, nouveau) is loaded with modeset=0 in
>> initrd, i.e. KMS is disabled.
>> In the rare cases when loading the DRM module from initrd is a
>> general problem and unrelated to KMS, it is even possible to disable
>> loading of the DRM module in initrd completely. For this set the
>> NO_KMS_IN_INITRD sysconfig variable to yes via YAST, which then
>> recreates initrd afterwards. Reboot your machine.
>> On Intel without KMS the Xserver falls back to the fbdev driver
>> (the intel driver only supports KMS). On ATI for current GPUs it
>> falls back to radeonhd. On NVIDIA without KMS the nv driver is used
>> (the nouveau driver only supports KMS).
>>
>> And the best part about using nomodeset is, it costs nothing to use
> and follows the suggestions of many experts on the subject.
>
> Thank You,
>
Thanks, I’ll set it in menu.lst and see what happens.
–
Russ
openSUSE 11.3 (2.6.34.7-0.5-default)|KDE 4.5.3 Release 10|
Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS
I’ve done everything but it still doesn’t work correctly, now it only freezes the shortcuts on start menu, the shortcuts I have on the desktop work fine.
So, lets start by giving us the output from the free command, this is what it looks like on my PC:
james@linux-ew60:~> **free**
total used free shared buffers cached
Mem: 8186576 4235968 3950608 0 209592 3376520
-/+ buffers/cache: 649856 7536720
Swap: 2104476 0 2104476
Next, lets get the output from the fdisk command, you must be root to do this. Here is what it looks like on my PC:
james@linux-ew60:~> **su -**
Password:
linux-ew60:~ # **fdisk -l**
Disk /dev/sda: 2000.4 GB, 2000397852160 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4cbc9c09
Device Boot Start End Blocks Id System
/dev/sda1 * 1 243202 1953512448 7 HPFS/NTFS
Disk /dev/sdb: 600.1 GB, 600127266816 bytes
255 heads, 63 sectors/track, 72961 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x46f71f1a
Device Boot Start End Blocks Id System
/dev/sdb1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sdb2 * 263 19092 151251975 83 Linux
/dev/sdb3 19093 72962 432705294 83 Linux
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009698d
Device Boot Start End Blocks Id System
/dev/sdc1 1 182402 1465136128 7 HPFS/NTFS
Is it possible you are running out or memory and/or disk space? Depending on what we find, it may be time to consider updating your kernel outside of what comes with openSUSE 11.3, going for 2.6.36 or 2.6.37 which was just released.
Thank You,
total used free shared buffers cached
Mem: 6106580 1263432 4843148 0 34736 884316
-/+ buffers/cache: 344380 5762200
Swap: 2097148 0 2097148
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd7622a0f
Device Boot Start End Blocks Id System
/dev/sda1 1 1443 11588608 27 Unknown
/dev/sda2 1443 1456 102400 7 HPFS/NTFS
/dev/sda3 1456 32774 251564032 7 HPFS/NTFS
/dev/sda4 * 32774 60802 225129472 f W95 Ext'd (LBA)
/dev/sda5 32774 57277 196816896 7 HPFS/NTFS
/dev/sda6 57277 57538 2097152 82 Linux swap / Solaris
/dev/sda7 57538 58844 10485760 83 Linux
/dev/sda8 58844 60802 15725568 83 Linux
here it is!
Here is a disk usage list I created manually by looking at the “My Computer” icon on the desktop that tells me how much free space all mounted drives are reporting. Put this same thing together with your computer. Again, I created this manually with KWRITE while looking at the “My Computer” icon and posted it here.
Device Filesystem Total space Available space Used Space
/home ext4 406.2 GiB 341.1 GiB 65.1 GiB
/ ext4 142.0 GiB 112.6 GiB 29.4 GiB
LM_HDC ntfs-3g 1,863.0 GiB 1,821.1 GiB 41.9 GiB
LM_HDD ntfs-3g 1,397.3 GiB 1,236.1 GiB 161.2 GiB
I am going to suggest you update your kernel to 2.6.37 by using SAKC if your disk space usage looks OK. But, it will not work if your computer locks up during its creation and that can take up to an hour to finish. To compile your own kerenl, you must go into YaST / Software Repositories, select View Patterns and then check or enable Base Development, C++ Development and Kernel Development and let all of this install. Next, visit the following message to get the SAKC script file:
S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.00
Message #17 has the most recent version of SAKC. Message #22 has a nice companion file called KLIST to make starting SAKC easier. To make reloading the nVIDIA video driver easier, I have another script called LNVHW here:
LNVHW - Load NVIDIA (driver the) Hard Way from runlevel 3
Look at message #12 for more information on getting the most recent script file. It is my thought right now that you need to update your kernel and if this does not help you have a hardware problem. If you have never use a script file before, just read through the material and ask any questions you might have.
Thank You,
df -h
in a terminal will save you some typing 
brunomcl, thanks so much for the information. You know that you learn something new everyday and the df -h command was a good one to learn.
df -h
If it weren’t for the fact I forget two things every day for the one I learn, I would think I was getting smarter, but oh well, I guess not. Still, I give you my gold start award for the day. df, is that for disk-formation?
Thank You,
You’re welcome. I think it stand for disk free.
I know the feeling. I think I’m rapidly approaching the age when I’ll be able to ponderously say to new engineers: “Son, I’ve already forgotten more than you learned your entire life”. Now that’s a scary thought for you - and me! 