Issue might be actually the X driver and mesa disagreeing how to handle
the memory buffers.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435
** Bug watch added: Debian Bug tracker #757435
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435
--
You received this bug notification be
At least in my case upgrading kernel to "2.6.37-020637rc2-generic" from
mainline did not do any good.
Fullscreen flash still freezes allways but sound works ok.
I have also tried all the /etc/adobe/ and export env-variable stuff
described in other threads -- no help.
--
You received this bug no
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
I'm seeing the same thing, on Intel 945GME. Happens when using Metacity,
but not when using Compiz.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/778083
Title:
Switching workspaces does
Confirm -- happened several times with natty:
[ 24739.679] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 24739.679]
Backtrace:
[ 24739.728] 0: /usr/bin/X (xorg_backtrace+0x26) [0x4a2e56]
[ 24739.728] 1: /usr/bin/X (mieqEnqueue+0x1f4) [0x4a2124]
[ 24739.728] 2: /usr/bin
I think i hit this same bug while setting mixer input volume and then
closed the setting dialog, 10.10 up-to-date, netbook remix, i386
--
gnome-settings-daemon crashed with signal 5 in xkl_process_error()
https://bugs.launchpad.net/bugs/321041
You received this bug notification because you are a
Bug is that kernel module is not loaded before xstarts.
--
Small graphics performance
https://bugs.launchpad.net/bugs/547187
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
_
On Sun, Mar 21, 2010 at 9:56 PM, Arkashkin wrote:
> Ok, the bug still exist, I have opened th Appearance dialog and it look like
> this:
> http://www.ubuntu-pics.de/bild/48223/screenshot_C5T17G.png
>
Appearance dialog caches the old broken images and you need to force
the recreation of images wi
Here is 2 bugs reported in one bug report!
First one is GPU hang which is hard to fix. The best bet is to try
newer driver version if problem is fixed there.
https://launchpad.net/~xorg-edgers/+archive/ppa and
https://wiki.ubuntu.com/KernelTeam/MainlineBuilds are providing the
the latest version
kkd.log is showing that there is internal problem in mesa dri driver
that it emits more data to command stream that it should. Then kernel is
rejecting the command stream which causes X to crash. There is some bug
in mesa radeon driver.
I thunk that crash won't happen if you disable kwin composite
I was hoping that at least dmesg would show some error message after
crash.
Is there anything after crash in kdm.log?
Also there is quite important bug fixes for your card in the latest
code. if you want to try newer driver you can get it from
https://launchpad.net/~xorg-edgers/+archive/ppa and
h
On Thu, Mar 4, 2010 at 3:10 PM, grawcho wrote:
> your the master ... whatever you say
>
> by the way ... i did not have this problem with karmic kernel but ...
> your the expert
>
> if you need aditional data feel free to contact me
>
Can you collect Xorg.log + dmesg after crash? Also lspci --vvn
On Wed, Mar 3, 2010 at 11:23 PM, RdeWit wrote:
> Hi Pauli,
>
> When would I start this valgrind session? Just any time, just to collect
> information, immediately after the crash happens (logged in from another
> machine), after reboot (when back in X) or in some other way?
>
V
On Tue, Mar 2, 2010 at 12:35 PM, RdeWit wrote:
> An extra comment: the many crashes that I mentioned in my initial report
> have gone away after I replaced my memory modules.
>
> This problem however has not ceased to exist and every once or twice a
> week I get no monitor input (at all) on startu
This bug is already fixed in KMS driver. If Lucid enables KMS by
default the problem will be fixed.
On Mon, Feb 22, 2010 at 10:48 PM, Ben Blout wrote:
> This seems like much more than a wish-list level problem. Many home
> computers are used by more than one person, and with this bug, the
> usab
Your card limit is 2048x2048 for screen sizes if you want DRI. Driver
should disable DRI in case you try to use larger than that sizes. (All
acceleration)
Do you have xorg.log where you have virtual size set in xorg.conf?
--
Virtual screen causes spontaneous complete system lockups
https://bugs.
(WW) EDID preferred timing clock 162.00MHz exceeds claimed max 160MHz,
fixing
You should try to set the 1280x1024 as prefered mode in xorg.log just in
case the highest resolution is causing the problem.
--
Ubuntu unusable by default with ATI HD4670 video card + monitor on DVI link
(blank screen
Please try daily mainline-ppa
https://wiki.ubuntu.com/KernelTeam/MainlineBuilds and you will need a
special firmware
http://xorg.freedesktop.org/wiki/radeonBuildHowTo#TroubleshootingExtraFirmwareforR600.2BAC8-R700
This sounds like null pointer deference in init failure path that was
fixed in 2.6.3
On Fri, Feb 19, 2010 at 1:01 AM, stefan.witwicki wrote:
> Hm.. xrandr reports my virtual screen dimensions as 3200 x 1200, which
> is correct (1600x1200 on VGA + 1600x1200 on LVDS). But maybe my hardware
> does not actual support that large a display area.
>
Good catch. Your card only support onl
On Thu, Feb 18, 2010 at 11:41 PM, stefan.witwicki wrote:
> Pauli,
>
> Thanks for the help.
>
>> fglrx-kernel-source is not part of driver that you want. You should
>> remove it.
>
> After removing that package, I was back to the blackscreen problem
> (e.g. displa
The initial black screen problem looks like kernel modesetting bug. So
workaround would be booting with radeon.modeset=0 to use old UMS driver.
There has bee quite a lot fixes to mode selection in 2.6.33 kernel which
Ubuntu should backport to 2.6.32 kernel to fix the bugs in 2.6.32.
--
[Lucid al
fglrx-kernel-source is not part of driver that you want. You should
remove it.
On Thu, Feb 18, 2010 at 7:35 PM, stefan.witwicki wrote:
>
> ** Attachment added: "Xorg log after installing fglrx-kernel-source"
> http://launchpadlibrarian.net/39370583/Xorg.0.log
>
Your 3D rendering is disabled b
On Thu, Feb 18, 2010 at 7:03 PM, stefan.witwicki wrote:
> Even with the additional package, I am unable to get desktop effects
> working. Typing "compiz" results in the following output:
>
> compiz (core) - Fatal: Software rendering detected.
> compiz (core) - Error: Failed to manage screen: 0
>
xrandr is the tool that you are lookin for:
xrandr --output --gamma 1.0:1.0:1.0
output might be DVI-0 but you can check it with xrandr -q.
But I don't understand why 2nd monitor would mess the gamma settings
in first one. This would need some more investigation to find the
cause for problem.
-
agp module not loaded before drm.
I think this should be fixed in udev.
** Package changed: xserver-xorg-video-ati (Ubuntu) => udev (Ubuntu)
--
Radeon 9250 no 3D.
https://bugs.launchpad.net/bugs/490031
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
On Tue, Feb 16, 2010 at 11:40 PM, Walter Kerkhofs
wrote:
> [ 2.314151] [drm] Initialized drm 1.1.0 20060810
> [ 2.42] [drm] radeon default to kernel modesetting DISABLED.
>
> [ 27.352666] agpgart-amd64 :00:00.0: AGP 3.5 bridge
> [ 27.352686] agpgart-amd64 :00:00.0: putting AG
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host
Bridge [1106:3188] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:80a3]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66
http://bugzilla.kernel.org/show_bug.cgi?id=15186 ?
** Bug watch added: Linux Kernel Bug Tracker #15186
http://bugzilla.kernel.org/show_bug.cgi?id=15186
--
[RV770][Lucid][Kubuntu] graphical glitches
https://bugs.launchpad.net/bugs/522284
You received this bug notification because you are a mem
On Sun, Feb 14, 2010 at 9:52 PM, Ákos Maróy wrote:
> added log files - how would I screen capture the corruption?
>
> --
> screen corruption on 10.04 alpha2
> https://bugs.launchpad.net/bugs/520618
> You received this bug notification because you are subscribed to
> xserver-xorg-video-ati in ubunt
On Sun, Feb 14, 2010 at 9:06 PM, Ákos Maróy wrote:
> what information would you need - maybe I can collect it manually
> instead of apport-collect?
>
dmesg, xorg.log, lspci -vvvnn
Also it would be nice if you could capture the corruption to a
screenshot.
--
screen corruption on 10.04 alpha2
ht
On Tue, Feb 9, 2010 at 7:43 PM, Manoj Iyer wrote:
>
> *snip*
>
> This is a 64bit kernel, I can also upload a x86 kernel on request.
>
Radeon 7500 is far older than x86_64. It is from year 1999 if my
memory servers right.
--
[lucid] desktop runs out of video memory on ATI Radeon Mobility 7500
ht
Problem is that Ubuntu kernel fails to initialize radeon kernel module.
Then failure path has null pointer reference which causes the visible
error message.
Can someone add this to the kernel bugs?
Work around for users hacing this error is to boot older kernel that did
wotk with KMS.
--
[lucid
Do you have dmesg from any of the failed boots?
/var/log/message or /var/log/kern.log should hold the logs from previous boots,
Do you have some custom configuration in xorg.conf? If yes then you
should renme the xorg.conf and test without special configuration.
On Fri, Feb 5, 2010 at 6:31 AM, Ro
No. Too much work compared to benefits when there exist nearly working
solution.
If you cannot use xrandr modelines you should report the bug
bugs.freedesktop.org so it gets fixed before lucid.
http://wiki.debian.org/XStrikeForce/HowToRandR12 for good xrandr
configuration help.
The performance p
KMS=Kernel modesetting which you have to enable by passing modeset=1
to radeon kernel module. KMS driver fixes the bug and the commit you
think about is for KMS case. KMS is still under heavy development and
getting it to working state requires sometimes quite a lot of tweaking
depending of hw.
On
You can install the newest driver from the
https://launchpad.net/~xorg-edgers (DDX only repository) which has static
power management code. You can set ForceLowPowerMode in xorg.conf. You can
see more info about possible options for radeon driver using "man radeon"
command.
2010/1/31 Philip Muškov
** Bug watch added: freedesktop.org Bugzilla #24810
https://bugs.freedesktop.org/show_bug.cgi?id=24810
** Also affects: xserver-xorg-driver-ati via
https://bugs.freedesktop.org/show_bug.cgi?id=24810
Importance: Unknown
Status: Unknown
--
[lucid] desktop runs out of video memory o
It would help if there would be kernel message log from original
problem. Setting up netconsole to stream the kernel messages to 2nd
machine is probably the easiest solution.
Screen corruption is different bug and most likely caused by problematic AGP
transfers.
You can either set your card to
Symptoms are caused by gpu hang (your graphics card is running in a forever
loop). Same time driver is waiting for signal from the card that operations
have done. So result is that the driver gets blocked which blocks most of
others parts of kernel too.
Only solution to aoid this situation is to
This looks like download from screen bug. You can disable the feature with
Option "EXANoDownloadFromScreen" "on"
in xorg.conf
On Thu, Dec 24, 2009 at 12:50 AM, hansvw wrote:
> Experienced the same issue on an older radeon card (radeon 8500)
> following an automated update of xserver-xorg-video-r
This is different problem. This looks a lot like rendering bug that should
be reported in new bug report (unless it is already reported in some newer
bug report)
On Fri, Dec 25, 2009 at 1:56 PM, Reynaldo Matos Hortensi <
lasanhadeberinj...@gmail.com> wrote:
> Hi Extender,
> I have tried with xorg
Few things that could help in problem. You need to add configurations to
/etx/X11/xorg.conf to "Configured Video Device" section. You can find
more etailed info what can be put there using "man radeon" in console.
1. Disabling DRI (Option "DRI" "off")
2. Disable AGP by enabling PCI mode (Option "B
Ideally, this known and safe cause of build failure could be
distinguished from real build failures. Does DKMS check that the headers
are actually available (I think it does not)?
In any case this seems to require some special handling, as nvidia
package control file probably cannot instruct dpkg
The behavior of VT switching points toward a low-level bug, rather than
an application bug (cf. #437607):
0. After first login: X consumes 100% CPU
1. Alt+SysRQ+R (release KB, the VT switching seems to be disabled in default
configuration?)
2. Alt+F1 (switch to VT1)
3. Something (Xorg?) causes th
Same as this? https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/439138
--
Xorg cpu utilization high on every other startup
https://bugs.launchpad.net/bugs/440396
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
_
@srikumar:
That doesn't sound like it's the same bug. For instance, I see this bug
any more.
There can be more than one cause for why X would crash on startup, and this one
has most likely been fixed.
Please file a separate bug report, thanks!
** Changed in: eglibc (Ubuntu Karmic)
Stat
** Summary changed:
- [karmic] Xorg 100% CPU utilization after startup on SSDs
+ [karmic] Xorg 100% CPU utilization -- only after first login
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are
That is, happens also here, with Nvidia proprietary drivers on Karmic,
GeForce 7600 GS. No SSD drives.
--
[karmic, intel] Xorg 100% CPU utilization after startup on SSDs
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
*** This bug is a duplicate of bug 439138 ***
https://bugs.launchpad.net/bugs/439138
** This bug has been marked a duplicate of bug 439138
[karmic, intel] Xorg 100% CPU utilization after startup on SSDs
--
xorg takes 100% cpu -- but only on first login
https://bugs.launchpad.net/bugs/4376
Same bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/437607
--
[karmic, intel] Xorg 100% CPU utilization after startup on SSDs
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
__
.
-
Extract from make.log
-
DKMS make.log for nvidia-185.18.36 for kernel 2.6.31-11-generic (i686)
ti 29.9.2009 00.03.29 +0300
The C compiler '/home/pauli/bin/gcc-cached' does not appear to be able to
create executables. Please make sure you have
your Linux dist
More information: when Xorg is consuming CPU on the first login, when I
switch to another VT, the VT switches immediately back to X. I also
cannot use the "Switch to another user" feature. Like so:
1. Ctrl+Alt+SysRQ+R (release keyboard)
2. Alt+F1 (switch VT)
3. In a fraction of a second, VT switc
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32518230/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/32518232/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32518233/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
On Ubuntu Karmic & Nvidia's non-free drivers: after logging in, Xorg
takes 100% CPU. No application seems to be redrawing anything (no
firefox. Xorg is also the only large CPU user). Apart from the large CPU
usage, everything seems to be working norm
On Fri, Sep 18, 2009 at 11:02 AM, fuzzyBSc <
benjamincarl...@soundadvice.id.au> wrote:
> Just a quick update.
>
> I am still running Jaunty at the present time. I'm pretty busy at the
> current moment and haven't had time to upgrade to Karmic. I have been
> working through the AGP modes in xorg.co
On Fri, Sep 18, 2009 at 5:17 AM, bwat47 wrote:
> Installed alpha 6, I also get this problem. My card is a mobility 2600.
> Login just keeps looping. ctrl alt f1 does not work. How can I change
> the xorg.conf if I can't get to the console?
>
>
You can add text to kernel parameter list in grub to
On Thu, Sep 17, 2009 at 1:13 PM, Alberto Milone <
alberto.mil...@canonical.com> wrote:
> Just a clarification on the issue:
>
> Removing the 3D driver (/usr/lib/dri/r600_dri.so) is a valid workaround
> and the debdiff that I attached in comment 132 prevents mesa from
> building that driver.
>
> We
In #radeon irc channel we found solution for gentoo users with similar
problems. It was caused by commit a381287759b2b65e7de9fb35801c781cab016f10
(log: "drm/radeon/kms/r600: use blit for BO moves") in drm-next branch of
Airlied's kernele tree.
Reverting solves the problem until blit copy code is f
On Tue, Sep 15, 2009 at 3:16 PM, pvautrin wrote:
> Thanks Pauli,
> I was recommended this option some time ago and indeed it restores display
> (forgot to mention it on this thread).
> This problem appeared when I changed motherboard. I was able to access
> xorg.conf of my install
Possibly a duplicate of
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/429003/
--
crash X at start
https://bugs.launchpad.net/bugs/429873
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
Public bug reported:
Fglrx installer overwrites mesa and xserer files causing prombles with
open source drivers even after removal.
Solution would be install fglrx and open drivers to own subdirectories.
Loading would either happen using symbolic links or /etc/ld.so.conf.d/
configuration. Also ke
It doesn't crash but calls probably exit in r600_dri.so. So some package is
not having correct stuff for r600 3D to work. You might find some info from
gdm.log or where ever the Xserver stderr is going to.
On Wed, Sep 16, 2009 at 2:34 PM, Martin Pitt
wrote:
> I don't think it helps much, but I s
You should increase your BIOS AGP apperture sizes to see if it helps. The
PCI error looks like some conflict in how acpi wants to handle card in PCI
mode which causes problems because agpgart has already reserved the memory
area. (PCI bar is usually defaulting to 256M which is a lot more than 64M
a
That sounds like bad problem with DFS or UTS. You can disable them in
xorg.conf with exa optinos to device context. More details are in man
exa to what can be put to xorg.conf.
Can you attach dmesg and xorg.log when modeset=1 is passed to kernel? It
works but kernel doesn't know about module to ha
Can you try Option "BusType" "PCIE" in xorg.conf?
Looks like it is possible bug in your main board AGP driver or AGP
bridge.
--
[HD3650] Kubuntu: garbage screen
https://bugs.launchpad.net/bugs/368187
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@Matthias Klose:
I think it is well possible to test this without any Nvidia hardware:
you probably can just do
$ dpkg-deb -x nvidia-glx-185_185.18.36-0ubuntu2_i386.deb xxx
$ LD_LIBRARY_PATH=$PWD/xxx/usr/lib glxinfo
and observe the crash -- it occurs on shared library load, very likely
b
*** This bug is a duplicate of bug 429003 ***
https://bugs.launchpad.net/bugs/429003
** This bug has been marked a duplicate of bug 429003
[karmic] Xorg (and anything GLX) crashes on startup
--
X server can't start with the NVIDIA driver installed
https://bugs.launchpad.net/bugs/429480
Yo
*** This bug is a duplicate of bug 429003 ***
https://bugs.launchpad.net/bugs/429003
** This bug has been marked a duplicate of bug 429003
[karmic] Xorg (and anything GLX) crashes on startup
--
X11 fails to start with nvidia 185
https://bugs.launchpad.net/bugs/429633
You received this bug
*** This bug is a duplicate of bug 429003 ***
https://bugs.launchpad.net/bugs/429003
** This bug has been marked a duplicate of bug 429003
[karmic] Xorg (and anything GLX) crashes on startup
--
Xorg crashed with SIGSEGV in strtol()
https://bugs.launchpad.net/bugs/429005
You received this
Also, as expected, downgrading libc6 and libc6-i686 to 2.10.1-0ubuntu9
made glxinfo not crash when nvidia-glx-185 is installed. Upgrading the
two packages to 2.10.1-0ubuntu11 made the crash reappear, and removing
nvidia-glx-185 to disappear again. So, this is some kind of mismatch
between the new l
Switching to the "nv" driver, and uninstalling nvidia-glx-185 makes
glxinfo and Xorg not crash any more, so it seems this problem is
localized to the non-free drivers.
--
[karmic] Xorg (and anything GLX) crashes on startup
https://bugs.launchpad.net/bugs/429003
You received this bug notification
Some possibly similar bugs were filed recently:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/429005
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/429002
https://bugs.launchpad.net/ubuntu/+bug/428993
https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bug/428979
https://bugs.laun
** Attachment added: "Xorg log file from a crashed run"
http://launchpadlibrarian.net/31755284/Xorg.log
--
[karmic] Xorg (and anything GLX) crashes on startup
https://bugs.launchpad.net/bugs/429003
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
As of after updates at 2009-09-13 ca. 16:00, Xorg and anything using GLX (eg.
glxinfo) crashes on startup.
The only thing that seems to have been changed then is the upgrade of libc6 to
2.10.1-0ubuntu11.
Log of crashing Xorg run is attached. The corresponding gdb backtrace
On Fri, Sep 11, 2009 at 3:04 PM, Bryce Harrington wrote:
> Hi paniemin,
>
>
> Thanks for including the attached files. Could you also include your
> /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?
>
> [This is an automated message. Apologies if it has reached you
> ina
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/31621758/Dependencies.txt
--
ssh X forwarding fails because user doesn't have access to write to
/var/run/gdm/
https://bugs.launchpad.net/bugs/427572
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Binary package hint: xauth
When I try to connect to ssh server running in Ubuntu Karmic with X
forwarding enabled I get problem that xauth doesn't have access to write
to /var/run/gdm/.
There is no problem if I'm already logged in locally with same user
because authenticatio
I got the packages build locally if I applied small typo fix for missing
comma :) It was simpler than I tough first.
--- nvidia-graphics-drivers-96-96.43.13/debian/control 2009-09-08
11:41:25.0 +0300
+++ new/debian/control 2009-09-08 11:39:18.0 +0300
@@ -111,7 +111,7 @@
Recomme
Looks like build failed because there was multiple palces where 185
driver should have been added but is missing in debian control.
--
nvidia-96-kernel-source fails to build on Karmic
https://bugs.launchpad.net/bugs/391768
You received this bug notification because you are a member of Ubuntu-X,
w
To fix most of freezes it is enough to use xorg-edgers packages. But
there is still sometimes small chance for GPU hang. Now I did compile
vanila kernel for jaunty to get KMS where remaining hang problems have
disappeared.
So non-kms Karmic: Small chance for hang. Reproducing in xmoto level
"Green
On Wed, May 13, 2009 at 11:25 AM, Bryce Harrington
wrote:
> We messed around a bunch with different migration heuristic options with
> the intel driver. Certainly there were some measurable improvements
> when using greedy, however it was found to cause graphics corruption on
> some systems (inde
81 matches
Mail list logo
