I did not see any differences besides minor changes in detected cpu frequency, BogoMIPS and the order of some lines about hard disks and network interfaces. I scanned through the docs I have on hand and the only caveat for cursor positioning is that the VGA popup cursor must entirely be within the bounds of the pipe. Result is at least nearly the same: You receive free shipping if your order includes at least AED of eligible items. Could you please check this?
|Date Added:||25 January 2014|
|File Size:||63.38 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Thank you in advance! I’ll get in contact with the kernel team to get this moving on their end. Where will the cursor be positioned when it’s re-enabled after switching? I’ll try to test with kernel 2. Now that I’ve got some hardware to test on I noticed that moving the mouse changes the behaviour of the broken screen, so I suspected that the hardware cursor might be involved.
Captiva – E | Souq – UAE
Did you use krandrtray or xrandr? Bug Watch Updater bug-watch-updater on Your Mobile number has been verified! I e9102w the dmesg output with drm.
I also tested the given kernel on a Fujitsu-Siemens Esprimo E and it looks good. Since we don’t use that cursor But even in this case that should not provoke a crash of the graphics.
It seems that the issue still exists after removing the vesa fb driver. My real working environment is a little bit outdated an I think it might be difficult to update all components. Changed in linux Ubuntu Lucid: This information was last pulled 35 minutes ago.
I hope I can respond faster now if you need further ccaptiva. Launchpad Janitor janitor wrote on Can we get this patch also applied to Lucid? Please test and give feedback here. Christian, I’ve seen other reports where kdrandrtray behaves differently than xrandr, so I’m inclined to believe that therein lies a few other bugs.
I scanned through the docs I have on hand and the only caveat for cursor positioning is that the VGA popup cursor must entirely be within the bounds of the pipe.
We will send you an SMS containing a verification code. Will you please try the latest linux kernel for example: I’ll send this off to Eric with the tested-by, thanks! I suspect that the resolution changes are only a part of this problem.
This bug affects 2 people. Unfortunately there hasn’t been much progress in the last weeks so I hope someone who has been related to this bug could help.
Should I pay a subscription fee to always have free shipping? As noted on the upstream bug this patch does not quite completely resolve this.
Wow, never would have suspected that. Attached are two dmesg outputs, given with drm debug set to 4. I “parked” my cursor on the upper left of the screen and cycled resolution about fifty times without any problems. Please try the updated patch. Sometimes it’s possible to switch back to a working mode by captlva using the shell history.
I’ll test whether fiddling with this cursor code makes a difference. You need to log in to change this bug’s status.