On 11/01/2010 03:37 PM, Togan Muftuoglu wrote:

...

I have read that

...

upgrading the kernel to 2.6.36 will cure these problems, but I'm unsure how to go about this.

You are on the right track -- I had nothing but trouble with 2.6.34 and hang and lockups. (There are also 5-20 sec. delays associated with kde4 dbus < 1.3x that are being worked)

Begin with enabling the folliwng line in /etc/zypp/zypp.conf

multiversion = provides:multiversion(kernel)

This will enable you to have two (or more) kernels to be installed.

Make sure you do set multiversion.... Then a zypper up (or zypper up -t package) will grab the new kernel (I can't recall when zypper up defaulted to package instead of patch...) Let us know how 2.6.36 works for you. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2.6.36 has been working fine for me but i'm using a self-compiled kernel. i'd also be interested to know how to do it with zypper. and also whether or not the opensuse repo has all the latest release candidate/release kernels or not. --- On Mon, 11/1/10, Bob Williams wrote:

From: Bob Williams Subject: Re: [opensuse] How to upgrade my kernel? To: opensuse@opensuse.org Date: Monday, November 1, 2010, 5:59 PM On Monday 01 Nov 2010 22:44:01 David C. Rankin wrote:

...

Make sure you do set multiversion....

OK, did that ...

...

Then a zypper up

I opted for zypper up, but the kernel was in the list of packages NOT to be upgraded. :(

...

(or zypper up -t package) will grab the new kernel (I can't recall when zypper up defaulted to package instead of patch...)

Should I have done "zypper up kernel"?

...

Let us know how 2.6.36 works for you.

I will when I get there ;)

Bob -- Registered Linux User #463880        FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.4-desktop, KDE 4.5.2 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 01 Nov 2010 23:28:35 Togan Muftuoglu wrote:

On 11/01/2010 11:59 PM, Bob Williams wrote:

...

On Monday 01 Nov 2010 22:44:01 David C. Rankin wrote:

...

Make sure you do set multiversion....

OK, did that ...

Should I have done "zypper up kernel"?

Why not use Yast to install the software with something you can see. Once you know what you are doing you can use the command line later

Because I respect David's advice, and I've used zypper up in the past for routine upgrades of installed software. However, following my last post, I did fire up Yast, and sure enough, there were the kernel upgrades waiting for me. I installed them... Unfortunately, on rebooting the nvidia drivers (260.19.12) won't work with the new kernel, and the machine just boots to the command line, so I'm no better off. -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2 64-bit, Kernel 2.6.31.14-0.4-desktop, KDE 4.5.2 Intel Core2 Quad Q9400 2.66GHz, 8GB DDR RAM, nVidia GeForce 9600GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 11/01/2010 06:46 PM, Bob Williams wrote:

Because I respect David's advice, and I've used zypper up in the past for routine upgrades of installed software.

Oops, Sorry for not thinking about nvidia, but you have the answer from dwgallien. The kernel updates with zypper versus yast have always befuddled me. I always use zypper, but I do recall using zypper on some kernels, yast on some kernels and I do recall just downloading the dang things and installing them manually with rpm. I guess the errors I've gotten have always been the "Oh yah, that damn thing again..." type and I always do something to fix it... but honestly, I have no recollection of what it is I do at the moment :p Maybe somebody familiar with the way 11.3 zypper kernel updates work with multiversion set can chime in and let us know why zypper lists them as packages that *won't* be installed -- and tell us how to fix it :-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 11/02/2010 12:31 AM, Felix Miata wrote:

Telling you some package will not be installed is just a way of saying an _upgrade_ version is available, as opposed to the _update_ version that zypper up proposes to install.

Ah hah! Thanks Felix! Now I remember what I did in 11.3 that solved the problem with it not grabbing the latest kernel. There is that new option in zypp.conf that provides the old behavior for zypper and yast that prevents build service versions (alternate versions of packages) from being hidden from the update process. (I can't remember what it is called at the moment -- my 11.3 box isn't up) But basically, it prevents you from having to tell yast to 'switch' packages to newer versions in the wanted repository. Somebody with a better memory please post the option. I'll get to my box at work tomorrow and post it if somebody hasn't filled it in. Note, when you set the option that shows all available packages -- just be smart about solving any dependency issue to prevent any conflicts. (All have been simple choices so far with 11.3) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 11/02/2010 06:03 PM, Matt Hayes wrote:

David,

I believe you are referring to vendor stickiness which is explained here http://en.opensuse.org/SDB:Vendor_change_update

That's the one! Thanks Matt. Bob, all, look at this option in zypp.conf if you notice you are not being allowed to update to the latest packages in build service. In order to restore the old-normal pre 11.2 behavior set: solver.allowVendorChange = true Then just pay attention to any dependency issues (Like you did from SuSE 6 - 11.1) and you will be just fine and not have to fight zypper/yast for updates. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 11/01/2010 05:59 PM, Bob Williams wrote:

On Monday 01 Nov 2010 22:44:01 David C. Rankin wrote:

...

...

Make sure you do set multiversion.... OK, did that ...

...

...

Then a zypper up I opted for zypper up, but the kernel was in the list of packages NOT to be upgraded. :(

...

...

Bob, Next best thing is to fire up yast, from the left-column choose repositories from the drop-down. Highlight your kernel:/HEAD repo, then: Packages -> All listed packages -> update if newer version is available. (your zypper up probably choked due to 'kernel-source' being replaced) If all else fails, I usually just download the new kernel files I need into a directory, then I do: rpm -Ivh *.rpm (check the errors to make sure that it is just choking on kernel-source or some other easily explainable file dependency that you are going to replace anyway) Then when you have satisfied yourself, do: rpm -Ivh --replacepkgs --replacefiles *.rpm or just rpm -Ivh --force *.rpm (--force is just shorthand for --replacepkgs --replacefiles) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, November 02, 2010 05:28 Bob Williams wrote:

Success!

Problem: The default kernel that ships with openSUSE 11.3 conflicts with the latest Nvidia graphics drivers, leading to frequent freezing of the system for several seconds at a time. My keyboard buffer was also affected, often sending a jumble of the characters I'd typed each time the system caught up with me.

Solution: Upgrade the kernel.

1. Add this repository, either in YaST or with zypper ar: http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/

2. In YaST software management, upgrade all your kernel packages to the newer kernel - in my case that's 2.6.36-90-desktop. The packages I had to upgrade were kernel-desktop, kernel-desktop-devel and kernel-devel. Install kernel- sources, if it's not already installed, otherwise upgrade it as well. The easiest way to do this upgrade is to select the Kernel:/HEAD repository and click on 'Switch system packages to the versions in this repository'.

3. Build and install the Nvidia drivers.

On the Nvidia website - http://www.nvidia.co.uk/page/home.html - click on 'Download Drivers', enter the details of your graphics card, and download the driver. This will be in the form a shell script, such as NVIDIA-Linux- x86_64-260.19.12.run. (The name will differ if you've selected the 32 bit driver). Save it wherever you like, then make it executable (chmod +x <filename>).

Reboot the computer, selecting the new 2.6.36 kernel. Graphics mode will fail, and you will be left at a console login prompt. Login as root, then cd to the directory containing the Nvidia script. Type:

./NVIDIA-Linux-x86_64-260.19.12.run or whatever your file was called.

Agree to the licence, then accept all the options offered. The final stage is to ask if you want the script to run nvidia-xconfig for you. The default is No, but I would recommend answering yes here, as you will only have to do this later anyway.

Reboot again (:~ # shutdown -r now), and you should be back into a graphical environment.

Many thanks to Matt Hayes, Togan Muftuoglu, David Rankin, michael getachew, dwgallien and Felix Miata, who helped me through this.

Bob

Thank you also for this nice and *easy* to understand way to update/upgrade the kernel and the Nvidia drivers! -- A møøse once bit my sister... Nø realli! She was Karving her initials øn the møøse with the sharpened end of an interspace tøøthbrush given her by Svenge - her brother-in-law - an Oslo dentist and star of many Norwegian møvies: 'The Høt Hands of an Oslo Dentist', 'Fillings of Passion', 'The Huge Mølars of Horst Nordfink'... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Bob Williams [11-02-10 06:31]:

3. Build and install the Nvidia drivers.

On the Nvidia website - http://www.nvidia.co.uk/page/home.html - click on 'Download Drivers', enter the details of your graphics card, and download the driver. This will be in the form a shell script, such as NVIDIA-Linux- x86_64-260.19.12.run. (The name will differ if you've selected the 32 bit driver). Save it wherever you like, then make it executable (chmod +x <filename>).

Reboot the computer, selecting the new 2.6.36 kernel. Graphics mode will fail, and you will be left at a console login prompt. Login as root, then cd to the directory containing the Nvidia script. Type:

./NVIDIA-Linux-x86_64-260.19.12.run or whatever your file was called.

Agree to the licence, then accept all the options offered. The final stage is to ask if you want the script to run nvidia-xconfig for you. The default is No, but I would recommend answering yes here, as you will only have to do this later anyway.

Running nvidia-xconfig generates an xorg.conf file which is only necessary if you have intentions or necessities requiring hand editing of it. I always accept the default/"no" option.

Reboot again (:~ # shutdown -r now), and you should be back into a graphical environment.

Also not necessary, you should be in runlevel 3. You can just issue "startx" from the same console command line which will start the graphic system in runlevel 3, or as root issue "init 5" which will start the graphic system in runlevel 5. ps: very good synopsis, please add it to the wiki. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 02 November 2010 08:02:13 Matt Hayes wrote:

I figured a kernel upgrade might help with the problem, but now that I've seen someone actually do it, I'm a bit more convinced :)

On the IRC and probably this mail list that was mentioned few times that I know about :) I use 2.6.36-89-desktop which is yesterday build of HEAD. Before I used RC version without any problems. The key advice here is to enable multiversion in /etc/zypp/zypp.conf . This should be easy as there is example line: # multiversion = provides:multiversion(kernel) removing # will activate multiversion option for kernel. The reason is that HEAD repo has only the latest build, so if something doesn't work for you, you will have older kernel as easy fallback option, instead of excitement to repair system from Live CD :-) Disadvantage of this option is that it will keep all kernels that you install until you manually remove them. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org