The new kernel compiled just fine using my SAKC bash script, but alas, new changes to the new kernel prevent the nVIDIA 295.59 driver from installing as it does with kernel 3.5. Further, the default graphics driver, if you have No KMS in kernel set, produces some strange psychedelic image display for me. So, here we go again attempting to load the nVIDIA proprietary video driver. This issue with nVIDIA is on top of a security problem just discovered with the present nVIDIA driver. But, of course, this is about the new kernel. I would love to hear your comments if you are now using kernel 3.6-rcx.
Linus Torvalds has issued the first release candidate for Linux 3.6, closing the merge window for major changes. Among the new additions is a feature called “Suspend to Both” that offers hybrid standby functionality – when hibernating, the system will preserve its memory contents both in working memory and on a system storage device. Hybrid standby usually behaves like Suspend to RAM; however, if there is a power cut during hibernation, the system can restore the main memory contents from the storage device and resume as expected.
TCP small queues are a modification to the network stack that is designed to prevent the bufferbloat problem. Also new is the support for TCP Fast Open, a protocol extension developed by Google to reduce the overhead when establishing TCP connections in order to speed up HTTP and other connections.
The developers have added the VFIO userspace driver framework; mainly developed for KVM virtualisation, it allows guests to use individual PCIe devices without major performance loss or risk to the host. Btrfs, which continues to be classed as experimental, now supports quotas and gains a send/receive feature which is mainly used by backup solutions to determine the difference between snapshots.
In the coming weeks, the Kernel Log on The H will cover these and numerous further new features of Linux 3.6. Provided that the summer holidays have no major impact on development, the next Linux version should be released in the second half of September. Because Torvalds is about to go on holiday, this merge window closed two days earlier than usual – in the release email for Linux 3.6-rc1, Torvalds also mentioned that he doesn’t like kernel developers who submit their changes immediately prior to the closing of the merge window.
Are you trolling? Firefox is only at version 14, any other numbers higher are probably code for beta trees. My firefox is version 14.0.1 right from the OpenSUSE repos. About the kernel… At “least” version 3.5? 3.5 was just released. And guess what… it is already in obs. Take your pick: software.opensuse.org:
So you have not fully updated your openSUSE installation in order to get the latest Firefox. You may start a new message and obtain help on that subject, but this is about testing the latest kernel version. I have posted info already on how to do that in this thread. The different kernel versions have a different configurations intended for different computer uses such as single user or server. We mostly use kernel-desktop here and the xen kernel is for VM operation. If you don’t know about kernel configs, just stick with kernel-desktop for now is your best course of action.
On 08/03/2012 04:46 PM, jdmcdaniel3 wrote:
>
> Today (8-3-12) finds that the next kernel version 3.6-rc1 has been
> released to test that you can find here: http://tinyurl.com/cn544wy
>
> The new kernel compiled just fine using my SAKC bash script, but alas,
> new changes to the new kernel prevent the nVIDIA 295.59 driver from
> installing as it does with kernel 3.5. Further, the default graphics
> driver, if you have No KMS in kernel set, produces some strange
> psychedelic image display for me. So, here we go again attempting to
> load the nVIDIA proprietary video driver. This issue with nVIDIA is on
> top of a security problem just discovered with the present nVIDIA
> driver. But, of course, this is about the new kernel. I would love to
> hear your comments if you are now using kernel 3.6-rcx.
The patch is trivial. In kernel 3.6, acpi_os_wait_events_complete() does not
have any arguments. In earlier kernels, Nvidia used the argument NULL. The full
patch test is
Index: kernel/nv-acpi.c
===================================================================
--- kernel/nv-acpi.c.orig
+++ kernel/nv-acpi.c
@@ -10,6 +10,7 @@
#define __NO_VERSION__
+#include <linux/version.h>
#include "nv-misc.h"
#include "os-interface.h"
#include "nv-linux.h"
@@ -300,7 +301,11 @@ static int nv_acpi_remove(struct acpi_de
if (pNvAcpiObject->notify_handler_installed)
{
// no status returned for this function
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3, 6, 0))
+ acpi_os_wait_events_complete();
+#else
acpi_os_wait_events_complete(NULL);
+#endif
// remove event notifier
status = acpi_remove_notify_handler(device->handle,
ACPI_DEVICE_NOTIFY, nv_acpi_event);
I was traveling, which is why it took a week to publish this patch.
I have been using 3.6-rc1 since its release. I have found no problems with it.
On 08/07/2012 10:06 PM, jdmcdaniel3 wrote:
>
> lwfinger;2478849 Wrote:
>> On 08/03/2012 04:46 PM, jdmcdaniel3 wrote:
>>>
>>> Today (8-3-12) finds that the next kernel version 3.6-rc1 has been
>>> released to test that you can find here: http://tinyurl.com/cn544wy
>>>
>>> The new kernel compiled just fine using my SAKC bash script, but
>> alas,
>>> new changes to the new kernel prevent the nVIDIA 295.59 driver from
>>> installing as it does with kernel 3.5. Further, the default graphics
>>> driver, if you have No KMS in kernel set, produces some strange
>>> psychedelic image display for me. So, here we go again attempting to
>>> load the nVIDIA proprietary video driver. This issue with nVIDIA is
>> on
>>> top of a security problem just discovered with the present nVIDIA
>>> driver. But, of course, this is about the new kernel. I would love
>> to
>>> hear your comments if you are now using kernel 3.6-rcx.
>>
>> The patch to use kernel 3.6-rc1 with Nvidia driver version 295.71 is at
>> ‘LWFINGER.NET’ (http://tinyurl.com/c5gn9yf). The
>> instructions for use of this patch file are at
>> http://www.lwfinger.net/nvidia_patches//readme.txt.
>>
>> The patch is trivial. In kernel 3.6, acpi_os_wait_events_complete()
>> does not
>> have any arguments. In earlier kernels, Nvidia used the argument NULL.
>> The full
>> patch test is
>>
>>>
> Code:
> --------------------
> > >
> > Index: kernel/nv-acpi.c
> > ===================================================================
> > — kernel/nv-acpi.c.orig
> > +++ kernel/nv-acpi.c
> > @@ -10,6 +10,7 @@
> >
> > #defineNO_VERSION
> >
> > +#include <linux/version.h>
> > #include “nv-misc.h”
> > #include “os-interface.h”
> > #include “nv-linux.h”
> > @@ -300,7 +301,11 @@ static int nv_acpi_remove(struct acpi_de
> > if (pNvAcpiObject->notify_handler_installed)
> > {
> > // no status returned for this function
> > +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3, 6, 0))
> > + acpi_os_wait_events_complete();
> > +#else
> > acpi_os_wait_events_complete(NULL);
> > +#endif
> >
> > // remove event notifier
> > status = acpi_remove_notify_handler(device->handle,
> > ACPI_DEVICE_NOTIFY, nv_acpi_event);
> >
> --------------------
>>>
>>
>> I was traveling, which is why it took a week to publish this patch.
>>
>> I have been using 3.6-rc1 since its release. I have found no problems
>> with it.
>
> Thanks Larry for the patch. The link to the patch just comes up 404
> for me and might be wrong.
The file had a space in the file name on the site. It is now fixed. Sorry for
the inconvenience.
The Patch file links works though it complains of an unknown file type for some reason. The link on the readme info also does not work for me. I just had a couple of 15 hour days in a row and so not much time at home looking at this patch but I would like to see your readme on how the patch is applied and to what we are patching.
On 08/08/2012 06:06 AM, jdmcdaniel3 wrote:
>
> The Patch file links works though it complains of an unknown file type
> for some reason. The link on the readme info also does not work for me.
> I just had a couple of 15 hour days in a row and so not much time at
> home looking at this patch but I would like to see your readme on how
> the patch is applied and to what we are patching.
The other one should also have worked, but did not for some reason.
The readme only tells you how to patch the Nvidia .run file. I stated why the
patch was needed in the first posting, but will repeat it here. Between 3.5 and
3.6, the API for acpi_os_wait_events_complete() was changed. This difference
will not cause any problems. Previously, it had one argument, which was a NULL
in the only place Nvidia calls it. Now it has no arguments - thus there is no
net effect.
I’m running openSUSE 12.2 RC1 (with all the updates bringing it to RC2 I guess). I downloaded the 3.6rc1 kernel, used SAKC script to compile it - had no issues whatsoever.
The main reason why I switched to the 3.6 kernel was to get better stability and support on my Ivy Bridge laptop (UX32VD), and proper support with asus-wmi driver. (The patched driver in 3.2 and 3.4 kernels was giving kernel panics on bootup).
I have an nVidia Hybrid graphics solution so I didn’t try the nvidia proprietary drivers. I’m just using the i915 and the nouveau drivers - and didnt notice any issues. I’m able to even connect external displays over VGA or HDMI and clone/extend displays. (Audio doesn’t work over HDMI - but a totally independent of issue wrt kernel I believe).
I played around with few power management options on the i915 and the drm modules as well as the pcie_aspm=force - one of them seem to be giving kernel panics on bootup, but if it boots up - I dont see any kernel panics afterward. I’m able to come out of standby and hibernate without any issues (except for Wifi state not being restored correctly - I end up turning off and back on the wifi).
Also my Intel 6235 WiFi card seems to be having issues with N-mode (High Tx Excessive retries and Invalid Misc numbers). I had to disable N-mode with 11n_disable=1 to not drop packets I dont believe it is a kernel regression, as this issue seems to have existed for at least 2 years or so with various older Intel Centrino Wifi cards and certain router models. I’m gonna try switching to a different router firmware to see if this issue disappears.
Larry I was able tonight to install your patch file into the nVIDIA driver 295.71 as shown below (save the text in the code block below as the file patch_nvidia_295_71.run_for_3.6):
Index: kernel/nv-acpi.c
===================================================================
--- kernel/nv-acpi.c.orig
+++ kernel/nv-acpi.c
@@ -10,6 +10,7 @@
#define __NO_VERSION__
+#include <linux/version.h>
#include "nv-misc.h"
#include "os-interface.h"
#include "nv-linux.h"
@@ -300,7 +301,11 @@ static int nv_acpi_remove(struct acpi_de
if (pNvAcpiObject->notify_handler_installed)
{
// no status returned for this function
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3, 6, 0))
+ acpi_os_wait_events_complete();
+#else
acpi_os_wait_events_complete(NULL);
+#endif
// remove event notifier
status = acpi_remove_notify_handler(device->handle,
ACPI_DEVICE_NOTIFY, nv_acpi_event);
and using your Terminal command:
sh ./NVIDIA-Linux-x86_64-295.71.run --apply-patch patch_nvidia_295_71.run_for_3.6
This worked great and the modified file installed the nVIDIA driver properly but the main thing was that it now actually works properly when the new kernel 3.6 comes up.
So, I am now running kernel 3.6-rc1 and the nVIDIA driver 295.71 with your very appreciated help. As I said before, my computer actually came up before, but the colors were all wrong and I am still not sure I understand why, but what works with your help.
Well today I find that kernel 3.6-rc2 has been released. It surely has been a while since rc1 came out and I was wondering just what was holding up rc2. I have installed it using S.A.K.C. and I had no issue with the compile or startup. I am using the nVIDIA proprietary video driver version 295.71 with the patch provided by Larry Finger and all seems to be working just fine. You can find the latest kernel release here: linux-3.6-rc2.tar.bz2, You can find more comments from Linus Torvalds on this release here: Subject: Linux 3.6-rc2
Any and all comments are welcome here. Just let us know if you are using kernel 3.6 to day.
Linux users should test the latest kernel from time to time – if they don’t, they shouldn’t be surprised if something important gets broken the next time a major update is released.**
New drivers for old kernel versions – it’s a common request, especially from people new to Linux, and the Linux Kernel Backporting Project wants to make it happen. It’s a great idea, as it can sometimes be injudicious or impossible to swap a tried and tested kernel for a newer kernel and, until now, it’s been hard to get hold of new drivers any other way.
Hopefully users and distributors will only use this new option where they have to. Even now, there are too few users testing the very latest versions of the Linux kernel; the loss is, however, their own, as we can see from the following hypothetical example, based on a problem which cropped up in the c’t laboratory:
In May 2010, a user bought a new PC and installed Ubuntu 10.04 LTS (Linux kernel 2.6.32). It ran without a hitch for two years. As he planned to continue to use the system for a few years still and was keen to have the latest applications, this summer he updated his system to Ubuntu 12.04 LTS (Linux kernel 3.2). Having updated, however, he was disappointed to find that the new version wouldn’t boot. The reason: the manufacturer had implemented a third monitor output on the built-in graphics card using an elaborate wiring scheme not found on any other graphics card of this type; no-one had noticed that a change merged into Linux 2.6.34 did not work with this scheme, as the graphics card in question was not in widespread use.
Linux 3.6 introduces quota and backup functions for Btrfs as well as security enhancements for temp directories. New interfaces enable the kernel to be made aware of changes to the sizes of used partitions.
Last Friday, Linus Torvalds released the second pre-release version of Linux 3.6. Torvalds’ summer holiday meant that this was released two weeks, rather than the usual one, after the first release candidate. The volume of changes that has since found its way into the main development tree remains at the normal level.
As usual, Torvalds and his fellow developers merged all of the major new features intended for Linux 3.6 at the beginning of its development cycle; it is rare for the kernel developers to add, or revert, any major changes or new features during the stabilization phase.
The Kernel Log can, therefore, already provide a comprehensive overview of the key changes and most important new features of Linux 3.6, which is expected to arrive in the second half of September. As usual, the Kernel Log overview will be presented in a series of articles that will cover the various kernel areas. The first article below describes the major changes in the kernel’s file systems and storage support; subsequent articles will look at the kernel’s graphics drivers, network support, architecture code and other hardware drivers.
I dont believe it is a kernel regression, as this issue seems to have existed for at least 2 years or so with various older Intel Centrino Wifi cards and certain router models. I’m gonna try switching to a different router firmware to see if this issue disappears.