https://bugzilla.kernel.org/show_bug.cgi?id=71461
Bug ID: 71461
Summary: monitor doesn't get detected after boot
Product: Drivers
Version: 2.5
Kernel Version: 3.13.5
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: tom.ty89(a)gmail.com
Regression: No
My card is Radeon HD5850.
The result might varies between different boot. Either the screens would not be
detected at all or they seem to be detected with a non-optimal resolution (in
console, while gdm shows a broken screen)
If a monitor is connected before boot, others can get detected correctly
afterwards.
If only one monitor is connected, turning it off can make the signal lost.
Reboot or suspend/resume (after turning it on again) can bring the signal back.
(Yet dpms would cause no problem at all)
The only way to reproduce the problem if DVI is involved is to disconnect it
physically, otherwise only powering off the monitor is required. My guess is
DVI detects display with a different mechanism.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66977
Priority: medium
Bug ID: 66977
Assignee: dri-devel(a)lists.freedesktop.org
Summary: get_num_groups not supported by libclc
Severity: trivial
Classification: Unclassified
OS: Linux (All)
Reporter: jcharest(a)gmail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 82499
--> https://bugs.freedesktop.org/attachment.cgi?id=82499&action=edit
Here is the patch to call the appropriate intrinsic
Currently libclc does not support get_num_groups on r600 so it will give out an
error when used in an opencl kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56659
Priority: medium
Bug ID: 56659
Assignee: dri-devel(a)lists.freedesktop.org
Summary: DRI_PRIME: triangle, rendering inside of which occurs
with a noticeable delay
Severity: normal
Classification: Unclassified
OS: All
Reporter: runetmember(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 69414
--> https://bugs.freedesktop.org/attachment.cgi?id=69414&action=edit
Example of artifact
Hello!
Please look at attached screenshot - there is triangle where we still see part
of old frame, that was displayed on screen few frames before. I doesn't sure
about terminology, but from my point of view looks like rendering in this
triangle is lag behind rest of the screen.
This issue happen for me only for applications launched with enabled offloading
rendering (DRI_PRIME=1). It's reproducible not only in "Left 4 Dead 2" but also
in other applications. Even in Chromium (if you launch it with
"--ignore-gpu-blacklist" option that enabled hardware rendering on Mesa, and
"DRI_PRIME=1" that enable offloading rendering) display same artifact
(triangle) while scrolling pages. Also you may notice this artifact in
glxgears, if you you run it in fullscreen mode.
Software:
Kubuntu 12.10 x86_64 updated from Xorg Edgers PPA.
Mesa: 9.1~git20121029.00e6819e
libdrm-radeon1: git20121025.bc494b31
xserver-xorg-video-radeon: git20120928.e8cb0b72
xserver-xorg-core: 1.13.0+git20120920.70e57668
Enabled or disabled V-Sync in KWin settings doesn't make the difference.
Enabled or disabled V-Sync in game settings doesn't make the difference.
Screenshot taken with stock Kubuntu kernel (3.5.0-17). With 3.7rc3 kernel issue
still reproducible, but just a bit less noticeable.
Hardware:
Acer Aspire 7560G laptop,
AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO)
Discrete AMD Radeon HD 6650M (TURKS)
"xrandr --listproviders" output:
Providers: number : 2
Provider 0: id: 138 cap: 0xd, Source Output, Source Offload, Sink Offload
crtcs: 2 outputs: 3 associated providers: 1 name:radeon
Provider 1: id: 85 cap: 0xd, Source Output, Source Offload, Sink Offload crtcs:
6 outputs: 0 associated providers: 1 name:radeon
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=83436
Priority: medium
Bug ID: 83436
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Sudden framerate drops in multiple games
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: gutigen(a)outlook.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 105680
--> https://bugs.freedesktop.org/attachment.cgi?id=105680&action=edit
dmesg
I'm having a lot of fps drops in TF2, Unigine Heaven, Xonotic, Wine games.
Framerate goes from even something like stable 100fps to sudden 5-15fps, it
hangs there for few seconds and goes back up to usual.
On top of that I've noticed some performance decrease in above apps by even
20%.
This is happening since last week (maybe friday? something around the weekend).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66384
Priority: medium
Bug ID: 66384
Assignee: dri-devel(a)lists.freedesktop.org
Summary: VDPAU playback hangs when moving window between xrandr
monitors
Severity: normal
Classification: Unclassified
OS: All
Reporter: mgorny(a)gentoo.org
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r600
Product: Mesa
I'm running live xorg/mesa with Radeon HD5450. I have two monitors connected
and set up side-by-side using xrandr like the following:
$ xrandr --output VGA-0 --mode 1280x960 --right-of DVI-0
Now, when I play a movie using mplayer2 with VDPAU driver and move the movie
onto second monitor without pausing it first, the playback hangs for a minute
or two. Then it resumes like nothing happened, no messages neither on console
nor in dmesg.
What's interesting is that it seems to happen only after moving half of the
window. If I have it partially on both monitors, it plays back fine. After the
hang it plays fine again, and if I then move it back to the first monitor, it
again hangs after moving half of it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=53118
Bug #: 53118
Summary: Rendering error in unigine heaven when
GL_ARB_shader_bit_encoding is used.
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: thomas.lindroth(a)gmail.com
Created attachment 65111
--> https://bugs.freedesktop.org/attachment.cgi?id=65111
screenshot
Textures are rendered incorrectly in unigine heaven on latest git drivers with
kernel 3.5.0 when shaders are set to high and ambient occlusion is on. The
problem is fixed when exporting
MESA_EXTENSION_OVERRIDE="-GL_ARB_shader_bit_encoding"
Hardware is juniper.
--
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=74329
Priority: medium
Bug ID: 74329
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Please expose OES_texture_float and
OES_texture_half_float on the ES3 context
Severity: minor
Classification: Unclassified
OS: Linux (All)
Reporter: org.freedesktop(a)io7m.com
Hardware: All
Status: NEW
Version: 10.0
Component: Drivers/DRI/R600
Product: Mesa
Hello.
Original discussion on mailing list:
http://lists.freedesktop.org/archives/mesa-users/2014-February/000761.html
Essentially, for the purposes of testing code in an ES3 context as it would be
run on an ES2 context (that is, taking the paths the code would take based on
the extensions present on ES2), it would be nice if the ES3 context exposed
OES_texture_float and OES_texture_half_float.
The current ES3 context on this hardware exposes GL_EXT_texture_rg and
GL_EXT_color_buffer_float, and can therefore definitely support
OES_texture_float and OES_texture_half_float. All that would (apparently) be
required would be for floating point textures to be specified in an ES2
compatible manner (with format and internalformat set to GL_RED|GL_RG, and type
set to GL_FLOAT).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Priority: medium
Bug ID: 73530
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Asus U38N: Black screen with Radeon driver in Linux
3.10, 3.11 and 3.12
Severity: major
Classification: Unclassified
OS: All
Reporter: paulepanter(a)users.sourceforge.net
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Copying my message to list dri-devel [1].
As reported in the channel #radeon on <irc.freenode.net>, with the
laptop Asus U38N-C4010H with an AMD Radeon HD 7600G
(Trinity A8-4555M) I am unable to get something displayed on the screen
with modesetting enabled. The backlight of the screen is on, but nothing
is shown on the screen. Booting with `radeon.modeset=0` on the Linux
kernel command line works. I was able to reproduce this problem with
Grml with Linux 3.10 and 3.11 and Debian Sid/unstable with Linux 3.12.6.
Attaching a VGA monitor to the mini VGA connector using an adapter,
nothing was shown on the monitor either.
The following is the output I get when starting with `radeon.modeset=0`
and then doing `sudo modprobe -r radeon` and `sudo modprobe radeon
modeset=1`.
Jan 11 06:42:24 myhostname kernel: [ 1060.871165] [drm] radeon kernel
modesetting enabled.
Jan 11 06:42:24 myhostname kernel: [ 1060.871244] checking generic
(d0000000 1f0000) vs hw (d0000000 10000000)
Jan 11 06:42:24 myhostname kernel: [ 1060.871247] fb: conflicting fb hw
usage radeondrmfb vs EFI VGA - removing generic driver
Jan 11 06:42:24 myhostname kernel: [ 1060.871322] Console: switching to
colour dummy device 80x25
Jan 11 06:42:24 myhostname kernel: [ 1060.871836] [drm] initializing
kernel modesetting (ARUBA 0x1002:0x9908 0x1043:0x1557).
Jan 11 06:42:24 myhostname kernel: [ 1060.871882] [drm] register mmio
base: 0xFEB00000
Jan 11 06:42:24 myhostname kernel: [ 1060.871884] [drm] register mmio
size: 262144
Jan 11 06:42:24 myhostname kernel: [ 1060.871913] [drm] ACPI VFCT
contains a BIOS for 00:01.0 1002:9908, size 19968
Jan 11 06:42:24 myhostname kernel: [ 1060.871925] ATOM BIOS: 113
Jan 11 06:42:24 myhostname kernel: [ 1060.871997] radeon 0000:00:01.0:
VRAM: 768M 0x0000000000000000 - 0x000000002FFFFFFF (768M used)
Jan 11 06:42:24 myhostname kernel: [ 1060.872000] radeon 0000:00:01.0:
GTT: 1024M 0x0000000030000000 - 0x000000006FFFFFFF
Jan 11 06:42:24 myhostname kernel: [ 1060.872003] [drm] Detected VRAM
RAM=768M, BAR=256M
Jan 11 06:42:24 myhostname kernel: [ 1060.872005] [drm] RAM width
64bits DDR
Jan 11 06:42:24 myhostname kernel: [ 1060.872088] [TTM] Zone kernel:
Available graphics memory: 1581256 kiB
Jan 11 06:42:24 myhostname kernel: [ 1060.872091] [TTM] Initializing
pool allocator
Jan 11 06:42:24 myhostname kernel: [ 1060.872101] [TTM] Initializing
DMA pool allocator
Jan 11 06:42:24 myhostname kernel: [ 1060.872129] [drm] radeon: 768M of
VRAM memory ready
Jan 11 06:42:24 myhostname kernel: [ 1060.872133] [drm] radeon: 1024M
of GTT memory ready.
Jan 11 06:42:24 myhostname kernel: [ 1060.874660] radeon 0000:00:01.0:
firmware: direct-loading firmware radeon/TAHITI_uvd.bin
Jan 11 06:42:24 myhostname kernel: [ 1060.874989] [drm] GART: num cpu
pages 262144, num gpu pages 262144
Jan 11 06:42:24 myhostname kernel: [ 1060.882325] [drm] Loading ARUBA
Microcode
Jan 11 06:42:24 myhostname kernel: [ 1060.882749] radeon 0000:00:01.0:
firmware: direct-loading firmware radeon/ARUBA_pfp.bin
Jan 11 06:42:24 myhostname kernel: [ 1060.883100] radeon 0000:00:01.0:
firmware: direct-loading firmware radeon/ARUBA_me.bin
Jan 11 06:42:24 myhostname kernel: [ 1060.883456] radeon 0000:00:01.0:
firmware: direct-loading firmware radeon/ARUBA_rlc.bin
Jan 11 06:42:24 myhostname kernel: [ 1060.884967] [drm] PCIE GART of
1024M enabled (table at 0x0000000000276000).
Jan 11 06:42:24 myhostname kernel: [ 1060.885159] radeon 0000:00:01.0:
WB enabled
Jan 11 06:42:24 myhostname kernel: [ 1060.885166] radeon 0000:00:01.0:
fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr
0xffff880129f11c00
Jan 11 06:42:24 myhostname kernel: [ 1060.885905] radeon 0000:00:01.0:
fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr
0xffffc90011db5a18
Jan 11 06:42:24 myhostname kernel: [ 1060.885910] radeon 0000:00:01.0:
fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr
0xffff880129f11c04
Jan 11 06:42:24 myhostname kernel: [ 1060.885914] radeon 0000:00:01.0:
fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr
0xffff880129f11c08
Jan 11 06:42:24 myhostname kernel: [ 1060.885918] radeon 0000:00:01.0:
fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr
0xffff880129f11c0c
Jan 11 06:42:24 myhostname kernel: [ 1060.885922] radeon 0000:00:01.0:
fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr
0xffff880129f11c10
Jan 11 06:42:24 myhostname kernel: [ 1060.885929] [drm] Supports vblank
timestamp caching Rev 1 (10.10.2010).
Jan 11 06:42:24 myhostname kernel: [ 1060.885931] [drm] Driver supports
precise vblank timestamp query.
Jan 11 06:42:24 myhostname kernel: [ 1060.885958] radeon 0000:00:01.0:
irq 52 for MSI/MSI-X
Jan 11 06:42:24 myhostname kernel: [ 1060.885982] radeon 0000:00:01.0:
radeon: using MSI.
Jan 11 06:42:24 myhostname kernel: [ 1060.886266] [drm] radeon: irq
initialized.
Jan 11 06:42:24 myhostname kernel: [ 1060.905813] [drm] ring test on 0
succeeded in 2 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.905876] [drm] ring test on 3
succeeded in 2 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.905885] [drm] ring test on 4
succeeded in 1 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.961514] [drm] ring test on 5
succeeded in 1 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.981502] [drm] UVD initialized
successfully.
Jan 11 06:42:24 myhostname kernel: [ 1060.985538] [drm] Enabling audio
0 support
Jan 11 06:42:24 myhostname kernel: [ 1060.985544] [drm] Enabling audio
1 support
Jan 11 06:42:24 myhostname kernel: [ 1060.985549] [drm] Enabling audio
2 support
Jan 11 06:42:24 myhostname kernel: [ 1060.985553] [drm] Enabling audio
3 support
Jan 11 06:42:24 myhostname kernel: [ 1060.985557] [drm] Enabling audio
4 support
Jan 11 06:42:24 myhostname kernel: [ 1060.985560] [drm] Enabling audio
5 support
Jan 11 06:42:24 myhostname kernel: [ 1060.986106] [drm] ib test on ring
0 succeeded in 0 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.986644] [drm] ib test on ring
3 succeeded in 0 usecs
Jan 11 06:42:24 myhostname kernel: [ 1060.987175] [drm] ib test on ring
4 succeeded in 1 usecs
Jan 11 06:42:24 myhostname kernel: [ 1061.007977] [drm] ib test on ring
5 succeeded
Jan 11 06:42:24 myhostname kernel: [ 1061.032890] [drm] radeon atom DIG
backlight initialized
Jan 11 06:42:24 myhostname kernel: [ 1061.032894] [drm] Radeon Display
Connectors
Jan 11 06:42:24 myhostname kernel: [ 1061.032897] [drm] Connector 0:
Jan 11 06:42:24 myhostname kernel: [ 1061.032899] [drm] eDP-1
Jan 11 06:42:24 myhostname kernel: [ 1061.032901] [drm] HPD1
Jan 11 06:42:24 myhostname kernel: [ 1061.032904] [drm] DDC: 0x6530
0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
Jan 11 06:42:24 myhostname kernel: [ 1061.032906] [drm] Encoders:
Jan 11 06:42:24 myhostname kernel: [ 1061.032908] [drm] LCD1:
INTERNAL_UNIPHY2
Jan 11 06:42:24 myhostname kernel: [ 1061.032909] [drm] Connector 1:
Jan 11 06:42:24 myhostname kernel: [ 1061.032911] [drm] VGA-1
Jan 11 06:42:24 myhostname kernel: [ 1061.032912] [drm] HPD2
Jan 11 06:42:24 myhostname kernel: [ 1061.032915] [drm] DDC: 0x6540
0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
Jan 11 06:42:24 myhostname kernel: [ 1061.032916] [drm] Encoders:
Jan 11 06:42:24 myhostname kernel: [ 1061.032917] [drm] CRT1:
INTERNAL_UNIPHY2
Jan 11 06:42:24 myhostname kernel: [ 1061.032919] [drm] CRT1:
NUTMEG
Jan 11 06:42:24 myhostname kernel: [ 1061.032920] [drm] Connector 2:
Jan 11 06:42:24 myhostname kernel: [ 1061.032922] [drm] HDMI-A-1
Jan 11 06:42:24 myhostname kernel: [ 1061.032923] [drm] HPD3
Jan 11 06:42:24 myhostname kernel: [ 1061.032925] [drm] DDC: 0x6550
0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
Jan 11 06:42:24 myhostname kernel: [ 1061.032926] [drm] Encoders:
Jan 11 06:42:24 myhostname kernel: [ 1061.032928] [drm] DFP1:
INTERNAL_UNIPHY
Jan 11 06:42:25 myhostname kernel: [ 1061.082355] [drm] Internal
thermal controller without fan control
Jan 11 06:42:25 myhostname kernel: [ 1061.082493] [drm] radeon: power
management initialized
Jan 11 06:42:26 myhostname kernel: [ 1062.360915] [drm] fb mappable at
0xD1488000
Jan 11 06:42:26 myhostname kernel: [ 1062.360922] [drm] vram apper at
0xD0000000
Jan 11 06:42:26 myhostname kernel: [ 1062.360926] [drm] size 8294400
Jan 11 06:42:26 myhostname kernel: [ 1062.360928] [drm] fb depth is 24
Jan 11 06:42:26 myhostname kernel: [ 1062.360931] [drm] pitch is
7680
Jan 11 06:42:26 myhostname kernel: [ 1062.361231] fbcon: radeondrmfb
(fb0) is primary device
Jan 11 06:42:28 myhostname kernel: [ 1064.675993] Console: switching to
colour frame buffer device 240x67
Jan 11 06:42:28 myhostname kernel: [ 1064.681973] radeon 0000:00:01.0:
fb0: radeondrmfb frame buffer device
Jan 11 06:42:28 myhostname kernel: [ 1064.681976] radeon 0000:00:01.0:
registered panic notifier
Jan 11 06:42:28 myhostname kernel: [ 1064.682222] [drm] Initialized
radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0
The screen turns off shortly (backlight too) and then only the backlight
comes back up.
As requested by Alex [2] I am going to attach the two files.
[1] http://lists.freedesktop.org/archives/dri-devel/2014-January/051737.html
[2] http://lists.freedesktop.org/archives/dri-devel/2014-January/051791.html
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=80922
Priority: medium
Bug ID: 80922
Assignee: dri-devel(a)lists.freedesktop.org
Summary: XCOM :Enemy Unknown will crash and kill the output
after some time.
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: half-shot(a)molrams.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 102280
--> https://bugs.freedesktop.org/attachment.cgi?id=102280&action=edit
glxinfo
Wish I could describe it better but there is no better words. The game will
lock up the card and the monitor output will go blank, although once I got
lucky and it crashed to the terminal spewing errors about radeon. Due to the
fact that the system crashes the only. This crash usually happens during a
gameplay sequence and has not happened in a menu as of yet. The crash also will
usually recover the first time after loosing visual output for 10 seconds but
then will cut out a second (or rarely a third) and not return to the game.
Due to it crashing randomly (no specific scene causing it) and always requiring
about a hour of play, would it make sense to be a memory issue?
It did not occur to me that I would need Dmesg output, if its needed then
remind me and I will reproduce another crash with the log file.
I also have a apitrace, but it totals 23GB and I do not know which bit would
need trimming.
System Specs:
AMD PhenomII X6 T55
AMD RadeonHD 7950
Mesa 10.3.0-devel (git-370184e)
LLVM 3.5.0 (svn)
--
You are receiving this mail because:
You are the assignee for the bug.