Announcement

**molostoff** · Oct 08, 2009, 06:38 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

For me its happens with OpenGL KDE desktop effects set on.

I have ati video card.

Setting OpenGL to off simply stops crashes.

By the way, KDE without opengl - is not kindly useful.

Please, give back opengl on ati card!

**sblass** · Oct 08, 2009, 07:18 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

I don't think I have OpenGL effects set on, nor can I find out. The one program that is GUARANTEED to bomb is System Settings - it doesn't even begin to open. And currently can't get Arora/Opera/Konqueror to run, either.

The 1-pixel white fringing on the main desktop goes away after doing Ctrl-F2 / Ctrl-F1 toggle.

Currently Kontact/KMail and Adept are running, virtually without bombing. Strangely enough Kmahjongg/Kpat/Ksudoku all run just fine. Thought for a moment that Kstars did, too, but it just bombed.

Weird!!

**molostoff** · Oct 08, 2009, 07:29 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

It seems to me that some solution I have got:

https://lists.ubuntu.com/archives/ub...er/029312.html

setting radeon.modeset=1 is helpful indeed and disables crashes. tty mode looks fine to me with this param.

I have used direct test providing "radeon.modeset=1" into /etc/defaults/grub (default kernel options where option splash resides). Then update-grub to rebuild grub.cfg.

I suspect there is a better place for customize radeon driver settings:

/etc/modprobe.conf (create if missing):
options radeon modeset=1

it still slower than vesa, but works...

also good source to get involved is https://edge.launchpad.net/~xorg-edgers/+archive/ppa

**sblass** · Oct 08, 2009, 11:25 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Thank you so much, molostoff!

Creating file /etc/modprobe.conf, with contents 'options radeon modeset=1' did the trick.

**tkteo** · Oct 09, 2009, 08:25 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

I am experiencing the same problem sblass described. So perhaps it is not coincidence that the problem occurs on my system with ATI Radeon video.

I will try the workaround that molostoff has posted and report back.

**tkteo** · Oct 09, 2009, 08:57 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Darn. The workaround does not work well. As in, it works, but I had to add more workarounds to it.

What happened in my case:

I booted via grub to the recovery mode kernel option and to the command line. I added the line "options radeon modeset=1" to /etc/modprobe.conf

Then I rebooted and selected the normal kernel bootup option during grub.

I got a super BSOD. A Black screen of death. Lol? I then had to unplug the power from my computer before I could try any more workarounds.

Second try: I booted to recovery mode and selected command prompt with networking. Entered root password when prompted, then "sudo kdm"

That worked. At least I am able to type this followup posting in Kubuntu instead of THAT other operating system. Lol?

**molostoff** · Oct 09, 2009, 09:03 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Originally posted by tkteo

That worked. At least I am able to type this followup posting in Kubuntu instead of THAT other operating system. Lol?

There could be a diff between ati cards (and other hw essentials) and a status of currently appearing new updates. For example, a have received new updates that broke this radeon tweak. Still in search.... It looks like there are intensive opengl developments and so on.... :/

**fsaravia** · Oct 09, 2009, 09:28 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

my system (dell inspiron 6400, kubuntu karmic, ATI X1400, last update 2009/10/08) crashes when opening menu...

solution: turn desktop effects of from command line (if enabled)

open konsole and type:

qdbus org.kde.kwin /KWin org.kde.KWin.toggleCompositing

now i can use my laptop, but no fancy effects yet

/var/log/kdm.log after crash:
*********************************WARN_ONCE******** *************************
File radeon_dma.c function radeonReleaseDmaRegions line 348
Leaking dma buffer object!
************************************************** *************************
X: radeon_bo_legacy.c:207: legacy_is_pending: Assertion `bo_legacy->is_pending <= bo->cref' failed.

see http://www.mail-archive.com/dri-deve.../msg43452.html

**tkteo** · Oct 09, 2009, 09:45 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Yup, I just updated some packages from the Karmic repositories, which have rendered (pun intended) the workaround ineffective.

And I am typing these remarks while booted into that other OS. Weep!

**molostoff** · Oct 09, 2009, 06:44 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Originally posted by fsaravia

X: radeon_bo_legacy.c:207: legacy_is_pending: Assertion `bo_legacy->is_pending <= bo->cref' failed.

see http://www.mail-archive.com/dri-deve.../msg43452.html

With new mesa libs that come in update an radeon.modeset is still helping/working.
anyway, it looks like a bug, so i have submitted it into https://bugs.launchpad.net/ubuntu/+s...rg/+bug/446845

**tkteo** · Oct 09, 2009, 10:26 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Thank you so very much for your help. I have subscribed to the bug report, and will update things on my end when I can.

**tkteo** · Oct 09, 2009, 11:43 PM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Originally posted by fsaravia

solution: turn desktop effects of from command line (if enabled)

open konsole and type:

qdbus org.kde.kwin /KWin org.kde.KWin.toggleCompositing

now i can use my laptop, but no fancy effects yet

fsaravia's suggeston to toggle off the desktop effects via the command line does help so far. After toggling off, I went into Kubuntu System Settings, then Desktop, then turned off all desktop effects by unchecking the box.

So far so good.

On the other hand, the radeon.modeset=1 method does not work for me at all, regardless of whether I am including the option via /etc/defaults/grub or /etc/modprobe.conf

I also ran "sudo update-grub" after creating the /etc/defaults/grub file but I do not see the "radeon.modeset=1" option present anywhere in menu.lst

Is there something I did wrong?

molostoff: would you please list the contents of what /etc/defaults/grub and /etc/modprobe.conf should be?

thanks,
tkteo

**molostoff** · Oct 10, 2009, 12:27 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Originally posted by tkteo

molostoff: would you please list the contents of what /etc/defaults/grub and /etc/modprobe.conf should be?

thanks,
tkteo

/etc/default/grub:

Code:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.modeset=1 splash"
GRUB_CMDLINE_LINUX=""

/etc/modprobe.conf:

Code:

options radeon modeset=1

as for me, with the latest updates i have received it seems that modprobe.conf does not help anymore, only grub kernel option helps.

I am not sure which updates you have already received and which are still pending for you, so both methods are desirable, but grub option is prefered, i suppose.

I still dont know better solution, modeset=1 slows down kubuntu opengl effects, slows down video and in overall is a resource hog solution, eventually freezing desk, but now the tty console with vbemode=3 autoenabled at boot by radeon driver is indeed only one thing i like from this "patch".

Still looking for good solution to make workable on ati card! Please, help return happy day!

**tkteo** · Oct 10, 2009, 04:15 AM

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Note: right now I have managed to update my kernel boot options in menu.lst to include "radeon.modeset=1" by referring to the following:

https://wiki.ubuntu.com/X/RadeonKMS
https://help.ubuntu.com/community/BootOptions

I added "radeon.modeset=1" to the end of the "# kopt=root=" line in menu.lst , then ran "sudo update-grub".

Announcement

KDM Problem (??) - New KDE BSOD-Like Feature?

KDM Problem (??) - New KDE BSOD-Like Feature?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment