I’ve got a Dell D610 laptop with a Mobility X300 integrated card. The
radeon driver works fine with 11.4 but with 12.1 beta 1, I have serious
issues with display corruption and lockups.
Anyone seen anything like this? I can run with ‘nomodeset’ and GNOME
boots to fall-back mode, but I’d like to actually have the gnome-shell
stuff working.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
You are not alone 
(https://bugzilla.novell.com/show_bug.cgi?id=721657)
Hendrik
On Sat, 08 Oct 2011 18:46:03 +0000, hendwolt wrote:
> You are not alone
> (https://bugzilla.novell.com/show_bug.cgi?id=721657)
>
> Hendrik
As long as it’s a known issue, I’m good - thanks!
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I’ve got a Dell D610 laptop with a Mobility X300 integrated card. The
radeon driver works fine with 11.4 but with 12.1 beta 1, I have serious
issues with display corruption and lockups.
Thanks for the heads up - I’ve got an old ThinkPad Z60m, which has the same chipset. It has 11.4 installed currently, but I won’t consider upgrading until I see a fix is implemented.
On Sat, 08 Oct 2011 22:46:02 +0000, deano ferrari wrote:
>> I’ve got a Dell D610 laptop with a Mobility X300 integrated card. The
>> radeon driver works fine with 11.4 but with 12.1 beta 1, I have serious
>> issues with display corruption and lockups.
> Thanks for the heads up - I’ve got an old ThinkPad Z60m, which has the
> same chipset. It has 11.4 installed currently, but I won’t consider
> upgrading until I see a fix is implemented.
In conjunction with the bug that was referenced, nomodeset does solve the
issue in general, but removes any HW acceleration, so gnome-shell (and
probably compiz) won’t run.
So the system is usable, but now I have to decide if I want to leave it
at 12.1 or go back to 11.4 until beta 2.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
There is also a much older bug report on this: https://bugzilla.novell.com/show_bug.cgi?id=678264
In that bug report, wrt the X300, one will note this suggestion, which proposes more than ‘just’ nomodeset:
Workaround for R3xx/R4xx users (Radeon 9600/X300/Xxxx)
------------------------------------------------------
- disabled KMS by adding 'nomodeset' to boot options.
- add the following section to your /etc/X11/xorg.conf.d/50-device.conf
Section "Module"
Disable "dri"
Disable "dri2"
EndSection
…and for users with R5xx (Radeon X1xx series) who may be reading this thread also, it has a different suggestion for them:
Workaround for R5xx users (Radeon X1xx series)
-----------------------------------------------
- disable KMS by adding 'nomodeset' to kernel boot options
(/boot/grub/menu.lst).
- add the following section to your /etc/X11/xorg.conf.d/50-device.conf
Section "Module"
Disable "dri"
Disable "dri2"
EndSection
- use this "Device" in your /etc/X11/xorg.conf./50-device.conf
Section "Device"
Identifier "Default Device"
Driver "radeonhd"
Option "AccelMethod" "xaa"
EndSection
I don’t think, that Bug 678264 is the same issue. The radeon driver in 11.4 (and the 12.1 milestones including M5) worked for me. I tried the suggested changes to 50-device.conf, but that did not change anything. There are still some minor display corruptions.
Agree its likely not the same. Bug 678264 was purportedly resolved. But I have seen regressions, and in my view it was worth trying the changes from Bug 678264 to investigate that possibility (of a regression). From what you say about your 50-device.conf efforts, you tried this and it made no difference.
On Sun, 09 Oct 2011 05:36:03 +0000, oldcpu wrote:
> There is also a much older bug report on this:
> https://bugzilla.novell.com/show_bug.cgi?id=678264
>
> In that bug report, wrt the X300, one will note this suggestion, which
> proposes more than ‘just’ nomodeset:
Thanks, Lee, I’ll check it out.
My hope is to have the radeon driver working with GNOME3 not in fallback
mode, as that config does work with 11.4.
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sun, 09 Oct 2011 07:26:03 +0000, oldcpu wrote:
> hendwolt;2391740 Wrote:
>> I don’t think, that Bug 678264 is the same issue. The radeon driver in
>> 11.4 (and the 12.1 milestones including M5) worked for me. I tried the
>> suggested changes to 50-device.conf, but that did not change anything.
>> There are still some minor display corruptions.
>
> Agree its likely not the same. Bug 678264 was purportedly resolved. But
> I have seen regressions, and in my view it was worth trying the changes
> from Bug 678264 to investigate that possibility (of a regression). From
> what you say about your 50-device.conf efforts, you tried this and it
> made no difference.
Yeah, that does look different, as X doesn’t seem to crash here, it just
“goes all wonky” (to use a technical description <g>).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sat, 08 Oct 2011 14:15:28 +0000, Jim Henderson wrote:
> I’ve got a Dell D610 laptop with a Mobility X300 integrated card. The
> radeon driver works fine with 11.4 but with 12.1 beta 1, I have serious
> issues with display corruption and lockups.
>
> Anyone seen anything like this? I can run with ‘nomodeset’ and GNOME
> boots to fall-back mode, but I’d like to actually have the gnome-shell
> stuff working.
>
> Jim
There’s a note on the open bug on this that the latest kernel update
fixes it - can anyone confirm?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I suspect its not so easy for anyone to confirm. The note you observed on the bug report says:
Seems that newer kernel 3.1.0-rc9-1-default works fine.
Factory snapshot has only rc7 … ie kernel-default-3.1.rc7-3.1.nosrc.rpm
I note, though in factory:
http://download.opensuse.org/factory/repo/oss/suse/x86_64/
the rpm kernel-default-3.1.rc9-1.1.x86_64.rpm
so I assume anyone who wanted to test this would need to download that rpm, and solve any dependencies, and update to that kernel, and pray it did not break anything (as it is VERY cutting edge).
If it were me, I would download the kernel (and its dependencies) and do the update with an “rpm -i” command to KEEP the old kernel while I tried any such update, as there is a GOOD CHANCE the rc9 could break one’s system and force a re-install.
I would NOT add the repository and install unless one configures YaST to keep the old kernel. Keeping the old kernel while installing the new will allow a dual boot to either kernel.
I got the kernel 3.1.0-rc9-1-desktop from the factory repository an can confirm that I do not need to use “nomodeset” anymore. There are still some corruptions here and there; the same as with “nomodeset”.
On Wed, 19 Oct 2011 20:06:02 +0000, hendwolt wrote:
> I got the kernel 3.1.0-rc9-1-desktop from the factory repository an can
> confirm that I do not need to use “nomodeset” anymore. There are still
> some corruptions here and there; the same as with “nomodeset”.
That’s excellent news, I’ll have to give this a try on my system when
I’ve got a chance (probably this weekend).
And oldcpu, you raise several excellent points - playing with a kernel
not even yet in factory could be hazardous to those unfamiliar with doing
so. 
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Thu, 20 Oct 2011 01:27:13 +0000, Jim Henderson wrote:
> On Wed, 19 Oct 2011 20:06:02 +0000, hendwolt wrote:
>
>> I got the kernel 3.1.0-rc9-1-desktop from the factory repository an can
>> confirm that I do not need to use “nomodeset” anymore. There are still
>> some corruptions here and there; the same as with “nomodeset”.
>
> That’s excellent news, I’ll have to give this a try on my system when
> I’ve got a chance (probably this weekend).
>
> And oldcpu, you raise several excellent points - playing with a kernel
> not even yet in factory could be hazardous to those unfamiliar with
> doing so.
>
> Jim
The bug was closed as being resolved now - guess it’s time to grab the
RC1 live media and give it a whirl.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I seem to be having a similar issue still here: updated to 12.1 - udevadm stalls
I have an ATI video card, and currently using kernel 3.1.0-rc9-1-desktop.
I have no 3d acceleration with the open source radeon driver, ATI radeon 4870.
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
I haven’t had very good luck with the open source radeon driver, but my graphics card has been EOL’d by ATI, so I guess I am out of luck.
With 11.4, I didn’t have any graphics related issues that I could see. The UI was slightly on the unresponsive side, but at least things looked nice.
With the move to 12.1 (Beta and then RC1), I’ve been getting the corrupt screen garbage when doing basic things like opening a menu, restoring a window, the thumbnail previews in the taskbar, etc.
To top it off, I can reliably crash the desktop (not sure if it’s kwin or plasma or X that crashes), simply by invoking the taskbar thumbnail and then clicking the thumbnail to minimize or restore the window. Every time. I imagine it’s plasma, because the plasmoids have to reload after this happens.
Turning off effects with ALT+SHIFT+F12 doesn’t “fix” the screen corruption issue.
This used to happen with all of the kubuntus since 10.10 or so. That’s what prompted me to openSUSE, since I wasn’t seeing these issues in 11.4. Now that they have returned, my best guess would be that since 11.4 was using an older kernel, this is something brought on by the inclusion of KMS. So my question would be, would using nomodeset as a boot parameter help in my case? What will I be missing out on?
For reference, I believe the card is an ATI Mobility X1200. I can get the rv number later, though I think it’s rv560.
Hmm … ??? … maybe an RS-690.
If you type :
man radeon
you can read up on the open source radeon driver.
If you type:
man radeonhd
you can read up on the radeonhd driver.
Did you try the radeonhd driver ?
Did you try the radeon driver (hard coded in the 50-device.conf) together with the ‘nomodeset’ boot code ?
I imagine you are probably right. I am not at that machine right now.
Did you try the radeonhd driver ?
Did you try the radeon driver (hard coded in the 50-device.conf) together with the ‘nomodeset’ boot code ?
Haven’t tried radeonhd. Is this a simple matter of installing radeonhd, whereby the radeon driver is de-selected?