https://bugzilla.kernel.org/show_bug.cgi?id=53391
Summary: nouveau: wrong display output order
Product: Drivers
Version: 2.5
Kernel Version: 3.8-rc6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: stijn+bugs(a)linux-ipv6.be
Regression: No
My graphics card is a Gainward GTX480
(http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1
mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being
the closest to the PCIe slot, then DVI 2, and finally the mini HDMI.
My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor
to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor
on DVI 1. Grub is displayed on the primary monitor, and the kernel initially
outputs to the primary monitor as well.
However, as soon as the nouveau module is loaded, the primary monitor goes to
standby and the kernel now uses the secondary monitor (on DVI 2) as primary.
When X starts (no Xorg.conf file), it is also displayed on the secondary
monitor.
When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the
primary monitor. X with nvidia.ko also uses DVI 1 as the primary display.
Finally, when booting Windows, the startup screen is also displayed on the
monitor connected to DVI 1.
Here comes the weird part: when I am in X, and run xrandr, it does show 3
connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only
active one. So it seems that in X, the output order is correct, but with
nouveaufb the DVI connectors are swapped.
I will attach the output of dmesg here. If anything else is needed, please let
me know and I'll be happy to add it.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=51381
Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for
more than 5secs aborting, when disabled via
vgaswitcheroo
Product: Drivers
Version: 2.5
Kernel Version: Linux version 3.6.9-1-ARCH (tobias@T-POWA-LX) (gcc
version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 4
08:04:10 CET 2012
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: a(a)anrd.net
Regression: Yes
Created an attachment (id=88591)
--> (https://bugzilla.kernel.org/attachment.cgi?id=88591)
journald log
After updating from 3.6.6 to 3.6.9 my laptop with Intel graphics and ATI HD
5650 will not resume from suspend. I use vgaswitcheroo to disable the ATI card
at boot. On resume the computer almost hangs (I can press power button and wait
5 minutes for a proper shutdown, but no other interaction is possible). It logs
a lot of messages saying:
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing D098 (len 72,
WS 0, PS 0) @ 0xD0C7
Steps to reproduce:
echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch
[suspend and resume]
Actual results:
Almost freeze.
Expected results:
Resume and work as normal.
Log is attached, but if you need anything else just ask.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=58981
Summary: Bisected regression; boot failure with Radeon 9250 PCI
256MB + KMS
Product: Drivers
Version: 2.5
Kernel Version: 2.6.35,3.2.45,3.10-rc2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: jdietrch(a)fastmail.fm
Regression: Yes
I have a Radeon 9250 PCI 256MB video card in my machine. I discovered that this
machine would not boot with 3.2.45 when KMS was enabled by default in the
kernel config. Immediately after the grub menu, the screen would go black and
nothing more would happen. Or sometimes columns of character-sized "marks"
would appear on the screen. In either case, though, the machine would not boot.
So I went back to 2.6.33 and found that booting with KMS did work just fine
there.
So I used git bisect to find where the problem arose, and that pointed to this
commit which was merged for 2.6.35:
commit 6b8b1786a8c29ce6e32298b93ac8d4a18a2b11c4
Author: Jerome Glisse <jglisse(a)redhat.com>
Date: Wed Apr 7 10:21:31 2010 +0000
drm/radeon/kms: enable use of unmappable VRAM V2
I confirmed this result of git bisect by checking out 2.6.35 final and
reverting that one commit, and the resulting kernel booted fine with KMS
enabled by default.
I also tried 3.10-rc2 and that booted fine when I added radeon.modeset=0 to the
kernel commandline.
I will attach files with dmesg output and lspci. Please let me know if there is
anything else I can do. I'll be happy to test a proposed fix if that would be
helpful.
Thank you,
James Dietrich
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=64721
Bug ID: 64721
Summary: Radeon HD6450 fails on all distro's out of box.
Product: Drivers
Version: 2.5
Kernel Version: Linux 3.2.04-amd64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: ichapman(a)videotron.ca
Regression: No
I think I'm at the right place to report video card frustrations.
Radeon HD450 fails to work out of the box with any Linux.
With Debian Wheezy I need to edit the grub line starting with linux and add
vga=791 to do anything. vga=771 fails
With Knoppix 7.0 I need vga=771 and that's okay, but vga=791 the left half of
screen is on right and right on left. The cursor moves to right falls off the
screen and re-appears on left side. Very strange.
With DebianMint I need vga=771 or 791 to get it to work.
On my Acer Aspire laptop with a Radeon HD6310 I do not need any of this vga=
stuff.
I am sure that this is not a driver problem. All the vga=xxx does is kick it
somewhere so that I loads the driver.
My Motherboard is M2V-Mx from Asus and once the /etc/default/grub is fixed with
GRUB_CMDLINE_LINUX="vga=791" or 771 it's okay. (sudo update-grub of course)
I recently junked my Nvidia 8500GT video because the driver for that became
sick, the worst feature was not being able to display the layout of the pcb
tool unless I disabled the driver and used cpu sw rendering on the video but
that's an other story. Ian.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32556
Summary: screen flickers all the time with desktop image
appearing only briefly
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: 3ntr0p13(a)gmail.com
Created an attachment (id=41344)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41344)
dmesg
Machine is the same as in bug report 28331 although with different software
components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor
4000+, this time running a 64 bits debian squeeze.
The machine is a small factor desktop machine designed around laptop
components, so the graphic card is an integrated radeon x1200.
When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the
time
making the machine unusable, while with debian kernel 2.6.32-5 such "flick to
black" event occur from time to time, making it annoying but usable.
While booting with radeon.modeset=0 the problem doesn't exhibits itself
The following packages version from debian squeeze are installed:
xserver-xorg 1:7.5+8
xserver-xorg-core 2:1.7.7-10
xserver-xorg-video-radeon 1:6.13.1-2+squeeze1
Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that
machine (when booted on 2.6.37-rc6).
Regards,
Gildas
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32422
Summary: Large images displayed in Firefox appear corrupted
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: da_fox(a)mad.scientist.com
Created an attachment (id=41150)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41150)
Picture describing a thousand words.
"A picture says more than a thousand words" (aka see attachment)
This is what happens when I try to view the XKCD "Online Communities 2" map
(http://xkcd.com/802_large/) or other large images in firefox.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75992
Priority: medium
Bug ID: 75992
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Display freezes & corruption with an r7 260x on
3.14-rc6
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: edt(a)aei.ca
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 95520
--> https://bugs.freedesktop.org/attachment.cgi?id=95520&action=edit
log of boot
I recently added a R7 260X to my system. While the card works with 3.13 its
supposed work much better with 14-rc. This is not the case. My system is
unstable without radeon.dpm=0 which was the default in .13.
linux 3.14-rc6 (with an up to date arch, stable X and mesa-git (10.2) mesa 10.1
and 10.0 also show very similar problems.
When X started I did notice some corruption. There are sets of two rectangles
about of a height of 2 or 3 mm, width of 25m or so with a second about a cm
below. The often occurs in chomium especially when scrolling. Runing the
unigine-sanctuary or unigine-tropics demo/benchmark programs also produce the
above problems and eventually stall.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=79488
Priority: medium
Bug ID: 79488
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Checkerboard tearing on Radeon card
Severity: normal
Classification: Unclassified
OS: All
Reporter: dan.doel(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 100211
--> https://bugs.freedesktop.org/attachment.cgi?id=100211&action=edit
dmesg while the machine is in the 'tearing' state
For several months now, I've occasionally run into situations where my screen
displays a strange artifact or tearing pattern. It is only visible when things
are changing, of course, and it looks like the monitor is divided into small
squares, and two different 'frames' are drawn alternately. Here is a video of
the problem I took back at the end of February:
https://www.youtube.com/watch?v=e2T8BeE0j74
I've just encountered this again, and it reminded me to finally post a bug.
You'll notice that the video was recorded on a cell phone. I tried using a
desktop recorder (the one built into gnome-shell) and the resulting video did
not display the artifacts. So it would seem to be happening at a level below
what capture can detect.
I'll attach dmesg and xorg logs from when the problem is happening. You'll see
that there are lots of page flip errors in both. However, I think that actually
might be a red herring. Doing a tail -f on the logs, I can cause artifacts to
display (for instance, selecting a different channel in my irc client, causing
highlighting to change, which briefly displays checkerboard highlights) without
a corresponding xorg error. And I also frequently see those errors accompanied
by ordinary tearing. But I can't definitively say that they aren't related,
either.
I'm using:
mesa from git as of about a week ago (rev 63069)
latest glamor (as of 2014-03-13)
xf86-video-ati 7.3.0
kernel 3.14.4
But this has been happening for significantly longer than just those versions.
I have a Radeon HD 7870 (pitcairn).
I'm not certain that I've assigned this bug to the right project, although at
least some of the visible errors involve drm. Apologies if it's the fault of
something else, though.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=79318
Priority: medium
Bug ID: 79318
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] The Witcher 2 wine graphical corruption
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Card is an AMD Radeon HD 7950. I’m using kernel 3.15-rc5 + cherrypicks + PTE
patches (VRAM page table entry compression) + hyperz (R600_DEBUG=hyperz). I’m
also using libdrm git, xf86-video-ati git, llvm 3.5 git with a rebased Tom
Stellard’s si-spill-fixes-v4 branch, mesa git (OpenGL core profile version
string: 3.3 (Core Profile) Mesa 10.3.0-devel (git-57730d6)) and Keith Packard’s
xorg-server glamor-server branch (1.16.0 RC 2).
As you can see from the attached screenshot there is graphical corruption:
http://files.linuxsystems.it/files/the_witcher_2_wine_radeonsi.png
It works flawlessly with Catalyst.
--
You are receiving this mail because:
You are the assignee for the bug.