Looks like with the latest update the problem is solved.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
[vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in
Virt
Funny thing that without any paravirtualization (paravirtualization
interface = none in vbox settings) everything works (but of course much
slower).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1
(In reply to AndrewK from comment #73)
> (In reply to nv28m from comment #71)
> > nouveau.agpmode=0 seems to work here too, also after comming back from
> > suspend.
> >
> > Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> > boot/suspend scripts. The scrolling and rxvt
Even more interesting, your trace actually has
[0] 1012.956817 MMIO32 R 0x100080 0xe100 PFB+0x80 => 0xe100
[0] 1012.956820 MMIO32 W 0x100080 0xe100 PFB+0x80 <= 0xe100
Which means that it _starts out_ at 0xe100. Was this trace done on a
clean boot, or had the nvidia module alre
BTW, interesting. In your VBIOS, it tells us to do
0xcbf2: 7a 80 00 10 00 00 00 00 e0 ZM_REG
R[0x100080] = 0xe000
Which is why that bit gets lost on resume (but not on kexec, since init
scripts don't run, since the adapter is already init'd). Good to know,
that means that
(In reply to comment #63)
> For the first two options I think it could be useful to grep through all
> those dumps collected over the years and check which cards have this set.
Yeah, I'll try to have a look later on.
>
> Option 3 could definately tell if it's only used for a particular memory
>
(In reply to comment #61)
> At the end I got what I wanted. The winner is:
> nvapoke 00100080 e100
>
> This register is e000 after suspend or after clean boot. So all this
> trouble only because of a single bit was not set ;(
Fantastic! I was secretly hoping that by ignoring the issue for
(In reply to comment #55)
> So something is initialized by the nvidia driver, which is not touched by
> nouveau but is required for correct operation.
>
> Is there a way I could help? Like dumping register states with/without the
> nvidia init?
You could do a mmiotrace of the nvidia driver. It's
** Attachment removed: "Screenshot from 2018-04-24 00-06-51.png"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1766358/+attachment/5126130/+files/Screenshot%20from%202018-04-24%2000-06-51.png
** Attachment added: "Screenshot from 2018-04-24 00-06-51--.png"
htt
Public bug reported:
Today I noticed that the are few processes that load my CPU about 100%.
I check the syslog, and there are lot of following messages:
```
Apr 24 00:09:48 Ilias-HP gnome-shell[1588]: [AppIndicatorSupport-WARN]
Attempting to re-register :1.58/org/ayatana/NotificationItem/multil
Nine is included into mesa mainline since 11.0, so it would be nice to
see it enabled in this half-experimental ppa:ubuntu-x-swat/updates
Currently there is wine from ppa:commendsarnex/winedri3 ppa which
formally working with oibaf PPA
> we are dependant on mesa build with Gallium Nine from the oib
(In reply to Alex Perez from comment #14)
> Ping. I am still experiencing problems with incorrect colors with the very
> latest Mesa, compiled from a fresh git checkout today.
Mesa 11.0.3+ work fine on a PPC G5 with a NV34 GPU. Haven't tested much
else. I don't think this is a "core" issue anymore
There is no mention of nouveau anywhere in here, indications of the
other bug are that nouveau vs nvidia doesn't matter, and I see no
indication of DRI_PRIME ever getting set. I believe this is
miscategorized, it's unclear to me why this is in the fd.o bugtracker at
all, sounds like some ubuntu thi
This bug is a couple years old with no updates, no mention of the
hardware, no mention of software versions, or anything else that would
make this investigatable. Feel free to reopen if it's still an issue and
you can provide fresh information with fresh software versions.
--
You received this bu
This bug should have been fixed in ~3.18 or so. Re 'ret' being special,
it is, see nvif_unpack macro definition. Feel free to reopen if you're
still seeing pink lines on Kepler GPUs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
*** Bug 89991 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT
*** Bug 78570 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT
To anyone looking to pile on with a "me too" comment: Only do so *AFTER*
verifying that commit 4f6029da is the first bad commit for you.
[Also, check that it's still happening with the latest kernel... 3.17 at
the time of writing.]
BobbyJ: I'm guessing you didn't do that. File your own bug with a
Looks like Ben made a more complete fix, now available as part of
http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.18
More specifically
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-3.18&id=a522946174b5ae389af0856c422d865a63c70316
Please test & confirm.
--
You rece
Try updating your intel ddx -- nouveau is not responsible for the
contents of the images it renders when in reverse-prime mode -- the
primary gpu is (in your case, intel).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel i
*** Bug 81614 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/925048
Title:
[GTX 580] X seems to hang a login prompt -- PFIFO
(In reply to comment #12)
> This bug is affecting me also, see the last duplicated bug. Any progress in
> fixing this? Maybe some help in testing (for ex.) required?
It's a bit of a mystery unfortunately. Adding to the annoyance, Ben said
that it does work just fine on his NVC8, although he has th
*** Bug 77371 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT
(In reply to comment #44)
> I'm sorry Ilia, I'm a normal user, no kernel developer.
If you're unable/unwilling/whatever-the-reason to do some amount of
debugging, you will be best-served by your distribution's support
channels.
--
You received this bug notification beca
(In reply to comment #42)
> Ilia, I don't know how to do that.
Use your favourite search engine to see how to use 'git bisect'. You may
even be able to find some guide specific to your distro. If you can't
narrow the problem down, we definitely won't be able to help
(In reply to comment #40)
> I hit this bug upon upgrade from Ubuntu 12.04 to 14.04. I can confirm
> nouveau is working in Ubuntu kernel 3.7.10 and it freezes on resume in
> 3.13.0.
> My hardware:
>
> 02:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M]
> (rev b1) (prog-if 00 [
(In reply to comment #29)
> Created attachment 95418 [details] [review]
> another patch for gddr5 ram
>
> I made this patch using my mmiotrace, but it doesn't help either.
Oh well. Indeed the values in your mmiotrace are different, but your and
Andrew's mmiotrace are the only traces I've seen tha
Created attachment 95408
initialize stuff for gddr5 ram
This patch is based on Andrew's mmiotrace. I saw a sequence of init that
I didn't see in other traces for working cards. Andrew -- would be
interesting if you could check it out and see if it helps. The algorithm
I came up with is insane -- t
Would you be able to do a bisect between 3.7 and 3.8?
Another user identified commit 4f6029da58ba (in bug #67878) which came
in between 3.7 and 3.8 -- perhaps you have the same issue? It's a
different card, so might be different... a bunch of stuff changed
between 3.7 and 3.8.
--
You received th
(In reply to comment #37)
> I've been following this ticket and attempting to poke around a bit. I just
> tested my hardware with various points in the 3.6, 3.7, and 3.7-rc kernels,
> and all of those still gave me a non-responsive screen with messages like
> the following after resume. e.g., on Li
(In reply to comment #18)
> It still doesn't find the firmware after updating the initramfs (sudo
> update-initramfs -u -k all), whether it is placed at
> /lib/firmware/nouveau/nvd9_fuc*, /lib/firmware/nouveau/fuc*,
> /lib/firmware//nouveau/nvd9_fuc* or
> /lib/firmware//nouveau/fuc*. (The script u
(In reply to comment #16)
> Created attachment 92127 [details]
> kernel log 3.13rc+firmware
>
> What does "not in the initrd" mean? The files were in /lib/firmware/nouveau
> with the names the script gave them (nvd9_fuc*).
But was this /lib/firmware/nouveau available when the nouveau module
load
Out of curiousity, does using blob pgraph fw help with this issue?
You can extract it yourself by using the instructions at
http://nouveau.freedesktop.org/wiki/NVC0_Firmware/ or you can try using
my script (https://raw2.github.com/imirkin/re-
vp2/master/extract_firmware.py) with the 325.15 blob, a
(In reply to comment #12)
> The blob firmware (in the standard 3.11 kernel) turns the login screen
> blank, with no recognisable error in the log.
Was this with mmiotrace'd firmware or with firmware extracted using my
script? If the latter, try moving nvd7_fuc*[cd] over nvd9_fuc*[cd] --
perhaps th
*** Bug 71662 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
[NVS 4200M] X freeze, "unhandled status 0x008000
No response to re-test request in over a month. Closing as invalid.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1005292
Title:
EOG shows black stripe in pictures
To man
a to file bugs about it. [Also note that most CPU/GPU chips have
overheat protection.]
> OK, Ilia. Where do yo recommend to post such report about "power management
> not supported" issues?
I would recommend sitting tight and waiting for this functionality to be
released. The N
This is not the appropriate forum to track "power management not
supported" issues. This is something that's being worked on, when it's
supported, should it not work, feel free to file bugs then.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
What backlight driver is being used? Please post your dmesg. Are you
booting with acpi_backlight=vendor ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouve
Can someone confirm that this is fixed in newer kernels as Ben said it
should be?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouveau: dark screen after su
Does this still happen with newer versions of the kernel/xf86-video-
nouveau?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1005292
Title:
EOG shows black stripe in pictur
Re-closing this. The people who reopened posters (a) had totally
different hardware, (b) did not provide any actual info, and (c) didn't
add themselves to cc.
If someone should still have issues regarding backlight, please file a
full issue as instructed by http://nouveau.freedesktop.org/wiki/Bugs
I confirm that it's still an issue for me. DistroRelease: Ubuntu 10.10,
Ubuntu 10.04. Last updates don't solved that issue. It looks like
something connected with KMS.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Assignee: (unassigned) => Ilia (look256)
--
You rece
I confirm that it's still an issue for me. DistroRelease: Ubuntu 10.10,
Ubuntu 10.04. Last updates don't solved that issue. It looks like
something connected with KMS.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification bec
Well. I confirm? that it's still an issue for me. I'll check if it was
solved by updates this week and describe it here. let's set 25.02.11 as
a deadline :).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https:
Well, it looks like I'm affected by the same bug. But my xrandr shows
the state of monitor cables correctly. But the second monitor goes to
the safemode on booting ubuntu 10.04 and 10.10. it affected kernel
2.6.32 and 2.6.34 in 10.04. and bare installing 10.10
radeon x1600.
--
You received this
freedesktop bug 26808 is marked as resolved now. Is this going to be
fixed in Lucid?
--
[i855] GPU hung (drm i915 intel) on Lucid Lynx
https://bugs.launchpad.net/bugs/528467
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
___
I'm using dual seat setup (2 xservers/2 monitors/2 keyboards/etc.) and
has exactly this problem (on both seats) after upgrading to Jaunty.
"End" key (code 115) is affected too. xset r workaround works for me
too.
Related `xset q` output before running xset r (note the second line ending with
e5ef
48 matches
Mail list logo
