The latest kernel 3.12-rc1 has been released for testing!
I have compiled and installed it and it is working just fine with VirtualBox 4.2.18 for your information. For now, I have all but gave up on nVIDIA staying inline with kernel updates, but one never knows I guess.
Ok I got virtualbox from Oracle installed. My mistake was trying to install while running vbox
apper just said that the install was aborted by user. When I tried with Yast then I got the real reason why the install failed
On Wed 18 Sep 2013 01:16:03 AM CDT, jdmcdaniel3 wrote:
dale14846;2585770 Wrote:
> Ok I got virtualbox from Oracle installed. My mistake was trying to
> install while running vbox
> apper just said that the install was aborted by user. When I tried
> with Yast then I got the real reason why the install failed
Yes, VirtualBox 4.2.18, downloaded from Oracle is working just fine with
kernel 3.12 and I am using dkms to auto install it.
By the way, I am sorry I missed that you had already started a kernel
3.12 thread. That was my mistake.
Thank You,
Hi
Can someone running the 3.12 kernel, post the output from;
modinfo sdhci_pci
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 12.3 (x86_64) GNOME 3.8.4 Kernel 3.7.10-1.16-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I have noticed I was having some sort of video artifacts showing up on screen using the nVIDIA open source driver with kernel 3.12-rc2 loaded. I dropped back to kernel 3.11.1 and have no such issue. Has anyone else using the “nouveau” driver seen this with the rc2 release by chance? My video card is listed as being a “NVIDIA GK104 [GeForce GTX 660 Ti]” and I have noted that in kernel 3.11 I also had problem with the same open source drive on a nVIDIA GT 620 and the “nouveau” driver for some reason. I had to drop back to kernel 3.10.11 on that PC.
I really think something is going on here, but not sure what it is.
I am experiencing the same and even worse as I can’t use my machine due to graphics being corrupted and not working. This is with kernel 3.12.0-rc2-3.g954d4c1-desktop. Installed from HEAD repo.
After reboot, I can see the Grub menu, default timeout waiting for boot, then a blackscreen with some artifacts and no graphics. CLI doesn’t work, X doesn’t. I’ve tried booting with nomodeset, that works with defaulting to a low resolution (1024x768).
I have a NVidia GTX570 card with lspci presenting as: NVIDIA Corporation GF110 [GeForce GTX 570] (rev a1)
Sounds like a graphic problem in the making. In order to make a complaint on the kernel, at least in my case, I would need to remove the VirtualBox driver as it taints the kernel, as I understand it. Do you have any extraneous binaries compiled into kernel 3.12 such as the one from VirtualBox?
On 09/28/2013 08:26 AM, jdmcdaniel3 wrote:
>
> sirdeiu;2588154 Wrote:
>> I am experiencing the same and even worse as I can’t use my machine due
>> to graphics being corrupted and not working. This is with kernel
>> 3.12.0-rc2-3.g954d4c1-desktop. Installed from HEAD repo.
>>
>> After reboot, I can see the Grub menu, default timeout waiting for boot,
>> then a blackscreen with some artifacts and no graphics. CLI doesn’t
>> work, X doesn’t. I’ve tried booting with nomodeset, that works with
>> defaulting to a low resolution (1024x768).
>>
>> I have a NVidia GTX570 card with lspci presenting as: -NVIDIA
>> Corporation GF110 [GeForce GTX 570] (rev a1)-
>
> Sounds like a graphic problem in the making. In order to make a
> complaint on the kernel, at least in my case, I would need to remove the
> VirtualBox driver as it taints the kernel, as I understand it. Do you
> have any extraneous binaries compiled into kernel 3.12 such as the one
> from VirtualBox?
Not all taints are equal, and you do not need to worry about the flavor from the
VBox routines. The set of taint flags are as follows:
Non-zero if the kernel has been tainted. Numeric values, which
can be ORed together:
1 - A module with a non-GPL license has been loaded, this
includes modules with no license.
Set by modutils >= 2.4.9 and module-init-tools.
2 - A module was force loaded by insmod -f.
Set by modutils >= 2.4.9 and module-init-tools.
4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
8 - A module was forcibly unloaded from the system by rmmod -f.
16 - A hardware machine check error occurred on the system.
32 - A bad page was discovered on the system.
64 - The user has asked that the system be marked "tainted". This
could be because they are running software that directly modifies
the hardware, or for other reasons.
128 - The system has died.
256 - The ACPI DSDT has been overridden with one supplied by the user
instead of using the one provided by the hardware.
512 - A kernel warning has occurred.
1024 - A module from drivers/staging was loaded.
2048 - The system is working around a severe firmware bug.
4096 - An out-of-tree module has been loaded.
The VBox drivers set the 4096 bit. The critical one for developers is bit 1,
which is the one used by proprietary code that has a binary blob, such as the
nVidia driver, or Broadcom’s wl. All bits up to 256 would be suspect, but you
are not likely to hit any of those.
So it seems. I’ve no other modules compiled into the kernel. Just installed from HEAD repo, reboot, fail. Forgot to mention in the previous post that this was running on OpenSUSE 13.1 B1. Which is coming along very good I might add. Small nags here and there, but still quite solid. Looking forward to it’s full release in November.
EDIT: Also maybe I or we need to report a bug on this ?
Do you have a link to best way to report a kernel issue, considering I have never done such a thing before? Also, for someone in my position, is a kernel bug report something anyone will else will look at if submitted by me, in your estimation?
On 09/28/2013 04:26 PM, jdmcdaniel3 wrote:
>
> lwfinger;2588187 Wrote:
>> On 09/28/2013 08:26 AM, jdmcdaniel3 wrote:
>>>
>>> sirdeiu;2588154 Wrote:
>>>> I am experiencing the same and even worse as I can’t use my machine
>> due
>>>> to graphics being corrupted and not working. This is with kernel
>>>> 3.12.0-rc2-3.g954d4c1-desktop. Installed from HEAD repo.
>>>>
>>>> After reboot, I can see the Grub menu, default timeout waiting for
>> boot,
>>>> then a blackscreen with some artifacts and no graphics. CLI doesn’t
>>>> work, X doesn’t. I’ve tried booting with nomodeset, that works with
>>>> defaulting to a low resolution (1024x768).
>>>>
>>>> I have a NVidia GTX570 card with lspci presenting as: -NVIDIA
>>>> Corporation GF110 [GeForce GTX 570] (rev a1)-
>>>
>>> Sounds like a graphic problem in the making. In order to make a
>>> complaint on the kernel, at least in my case, I would need to remove
>> the
>>> VirtualBox driver as it taints the kernel, as I understand it. Do you
>>> have any extraneous binaries compiled into kernel 3.12 such as the one
>>> from VirtualBox?
>>
>> Not all taints are equal, and you do not need to worry about the flavor
>> from the
>> VBox routines. The set of taint flags are as follows:
>>
>>>
> Code:
> --------------------
> > >
> > Non-zero if the kernel has been tainted. Numeric values, which
> > can be ORed together:
> >
> > 1 - A module with a non-GPL license has been loaded, this
> > includes modules with no license.
> > Set by modutils >= 2.4.9 and module-init-tools.
> > 2 - A module was force loaded by insmod -f.
> > Set by modutils >= 2.4.9 and module-init-tools.
> > 4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
> > 8 - A module was forcibly unloaded from the system by rmmod -f.
> > 16 - A hardware machine check error occurred on the system.
> > 32 - A bad page was discovered on the system.
> > 64 - The user has asked that the system be marked “tainted”. This
> > could be because they are running software that directly modifies
> > the hardware, or for other reasons.
> > 128 - The system has died.
> > 256 - The ACPI DSDT has been overridden with one supplied by the user
> > instead of using the one provided by the hardware.
> > 512 - A kernel warning has occurred.
> > 1024 - A module from drivers/staging was loaded.
> > 2048 - The system is working around a severe firmware bug.
> > 4096 - An out-of-tree module has been loaded.
> >
> --------------------
>>>
>>
>> The VBox drivers set the 4096 bit. The critical one for developers is
>> bit 1,
>> which is the one used by proprietary code that has a binary blob, such
>> as the
>> nVidia driver, or Broadcom’s wl. All bits up to 256 would be suspect,
>> but you
>> are not likely to hit any of those.
>
> Do you have a link to best way to report a kernel issue, considering I
> have never done such a thing before? Also, for someone in my position,
> is a kernel bug report something anyone will else will look at if
> submitted by me, in your estimation?
The attention it will receive will depend on the completeness of the report.
So I have compiled and loaded up kernel 3.12-rc3 to see if any video corruption is still present. So far so good, but we will see.
I have a question, perhaps only Larry knows, where is the change-log posted for each new kernel release candidate? Is there just one or how does that really work?
>
> I have noticed I was having some sort of video artifacts showing
up on
> screen using the nVIDIA open source driver with kernel 3.12-rc2
> loaded.
> I dropped back to kernel 3.11.1 and have no such issue. Has
anyone
> else
> using the “nouveau” driver seen this with the rc2 release by
chance?
> My video card is listed as being a “NVIDIA GK104 [GeForce GTX 660
Ti]”
> and I have noted that in kernel 3.11 I also had problem with the
same
> open source drive on a nVIDIA GT 620 and the “nouveau” driver for
some
> reason. I had to drop back to kernel 3.10.11 on that PC.
>
> I really think something is going on here, but not sure what it
is.
>
> Thank You for using openSUSE,
>
James I saw this yesterday on the openSUSE 13.1 Live-KDE DVD. The
rescue DVD also had some problem but eventallly came up in the XFCE
GUI. Very hard to read. Problem appears to be in nouveau drivers.
Today I will create a DVD and try reinstall of 13.1 which I never
got running with Nvidia even with patch. Will try from ground zero
again.
Both reported they could not setup my Intel sound system. Will look
into that also.
I am not sure how long one should wait to decide an issue is fixed, but with kernel 3.12-rc3, I have seen no video issues today at all. That is why I had wondered if a video fix had been put through which might show in a change log for the new kernel.
On 09/30/2013 02:26 PM, jdmcdaniel3 wrote:
>
> I am not sure how long one should wait to decide an issue is fixed, but
> with kernel 3.12-rc3, I have seen no video issues today at all. That is
> why I had wondered if a video fix had been put through which might show
> in a change log for the new kernel.
Between 3.12-rc2 and -ec3, there are no patches for nouveau. The fix could,
however, have been in some other component.
There are several fixes in drm/i915 and drm/radeon.