Discussion:
[Bug 104917] Xorg 1.19 aborts because it can't find any graphics devices/screens in Fedora 27/28 32 bit
b***@freedesktop.org
2018-06-05 16:22:03 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #14 from RobbieTheK <***@fordham.edu> ---
Created attachment 140034
--> https://bugs.freedesktop.org/attachment.cgi?id=140034&action=edit
xorg conf files requested

tar archive of conf files from /etc/X11/xorg.conf.d/ and
/usr/share/X11/xorg.conf.d/
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-05 09:26:35 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #11 from Michel DÀnzer <***@daenzer.net> ---
Please attach the corresponding dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-04 20:24:46 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

Alan Coopersmith <***@oracle.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|Server/DDX/Xorg |Driver/Radeon
Assignee|xorg-***@lists.x.org |xorg-driver-***@lists.x.org
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-05 15:52:34 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #13 from Michel DÀnzer <***@daenzer.net> ---
Still no idea what's wrong. Please also attach all files in
/etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ (if there are any
symlinks, attach the real files they resolve to, and mention the symlink name
in the comment when attaching it).
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-05 13:42:07 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #12 from RobbieTheK <***@fordham.edu> ---
Created attachment 140033
--> https://bugs.freedesktop.org/attachment.cgi?id=140033&action=edit
dmesg log

Perhaps a clue in here?

[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: setting as boot VGA device
[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[Fri May 25 12:08:27 2018] pci 0000:09:0d.0: vgaarb: bridge control possible
[Fri May 25 12:08:27 2018] vgaarb: loaded

[Fri May 25 12:08:30 2018] [drm] radeon kernel modesetting enabled.
[Fri May 25 12:08:30 2018] [drm] initializing kernel modesetting (RV100
0x1002:0x5159 0x1028:0x016C 0x00).
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: VRAM: 128M 0x00000000D0000000 -
0x00000000D7FFFFFF (16M used)
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: GTT: 512M 0x00000000B0000000 -
0x00000000CFFFFFFF
[Fri May 25 12:08:30 2018] [drm] Detected VRAM RAM=128M, BAR=128M
[Fri May 25 12:08:30 2018] [drm] RAM width 32bits DDR
[Fri May 25 12:08:30 2018] [TTM] Zone kernel: Available graphics memory:
424444 kiB
[Fri May 25 12:08:30 2018] [TTM] Zone highmem: Available graphics memory:
1679744 kiB
[Fri May 25 12:08:30 2018] [TTM] Initializing pool allocator
[Fri May 25 12:08:30 2018] [TTM] Initializing DMA pool allocator
[Fri May 25 12:08:30 2018] [drm] radeon: 16M of VRAM memory ready
[Fri May 25 12:08:30 2018] [drm] radeon: 512M of GTT memory ready.
[Fri May 25 12:08:30 2018] [drm] GART: num cpu pages 131072, num gpu pages
131072
[Fri May 25 12:08:30 2018] [drm] PCI GART of 512M enabled (table at
0x0000000035C80000).
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: WB disabled
[Fri May 25 12:08:30 2018] radeon 0000:09:0d.0: fence driver on ring 0 use gpu
addr 0x00000000b0000000 and cpu addr 0x7a045d80
[Fri May 25 12:08:30 2018] [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[Fri May 25 12:08:30 2018] [drm] Driver supports precise vblank timestamp
query.
[Fri May 25 12:08:30 2018] [drm] radeon: irq initialized.
[Fri May 25 12:08:30 2018] [drm] Loading R100 Microcode
[Fri May 25 12:08:30 2018] [drm] radeon: ring at 0x00000000B0001000
[Fri May 25 12:08:30 2018] [drm] ring test succeeded in 1 usecs
[Fri May 25 12:08:30 2018] [drm] ib test succeeded in 0 usecs
[Fri May 25 12:08:30 2018] [drm] No TV DAC info found in BIOS
[Fri May 25 12:08:30 2018] [drm] Radeon Display Connectors
[Fri May 25 12:08:30 2018] [drm] Connector 0:
[Fri May 25 12:08:30 2018] [drm] VGA-1
[Fri May 25 12:08:30 2018] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[Fri May 25 12:08:30 2018] [drm] Encoders:
[Fri May 25 12:08:30 2018] [drm] CRT1: INTERNAL_DAC1
[Fri May 25 12:08:30 2018] [drm] Connector 1:
[Fri May 25 12:08:30 2018] [drm] VGA-2
[Fri May 25 12:08:30 2018] [drm] DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[Fri May 25 12:08:30 2018] [drm] Encoders:
[Fri May 25 12:08:30 2018] [drm] CRT2: INTERNAL_DAC2
[Fri May 25 12:08:30 2018] [drm] Connector 2:
[Fri May 25 12:08:30 2018] [drm] DVI-I-1
[Fri May 25 12:08:30 2018] [drm] HPD1
[Fri May 25 12:08:30 2018] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[Fri May 25 12:08:30 2018] [drm] Encoders:
[Fri May 25 12:08:30 2018] [drm] CRT2: INTERNAL_DAC2
[Fri May 25 12:08:30 2018] [drm] DFP1: INTERNAL_TMDS1
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-08 18:49:36 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #15 from RobbieTheK <***@fordham.edu> ---
(In reply to Michel DÀnzer from comment #13)
Post by b***@freedesktop.org
Still no idea what's wrong. Please also attach all files in
/etc/X11/xorg.conf.d/ and /usr/share/X11/xorg.conf.d/ (if there are any
symlinks, attach the real files they resolve to, and mention the symlink
name in the comment when attaching it).
I take it the config files didn't help? Is there any other debug/verbose
logging that I can enable?
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-06-23 04:02:45 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=104917

--- Comment #16 from RobbieTheK <***@fordham.edu> ---
Helli Michel do you need any more logs from me? Or are the backtraces I put
accidentally in https://bugs.freedesktop.org/show_bug.cgi?id=81678 sufficient?
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...