From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204725] New: black screen
Date: Wed, 28 Aug 2019 22:23:55 +0000 [thread overview]
Message-ID: <bug-204725-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=204725
Bug ID: 204725
Summary: black screen
Product: Drivers
Version: 2.5
Kernel Version: linux-5.3-rc6, linux-5.3-rc6 latest,
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: drjoms@gmail.com
Regression: No
Created attachment 284671
--> https://bugzilla.kernel.org/attachment.cgi?id=284671&action=edit
black screen kernel 5.30
Hello,
Hardware: Linux (none)dimko's Desktop 5.2.10 #1 SMP PREEMPT Tue Aug 27 22:48:11
IST 2019 x86_64 AMD Ryzen 5 1600 Six-Core Processor AuthenticAMD GNU/Linux
32 gigs of ram, nvme sdd.
OS: Gentoo AMD 64 bit
Soft:
sys-devel/llvm
Latest version available: 10.0.0.9999
media-libs/mesa
Latest version available: 9999
* x11-base/xorg-server
Latest version available: 1.20.5
x11-drivers/xf86-input-evdev-2.10.6
x11-drivers/xf86-input-libinput-0.28.2
x11-drivers/xf86-video-amdgpu-19.0.1
x11-drivers/xf86-video-vesa-2.4.0
all drivers are compiled/installed after mesa/xorg installation, so no linkage
problem can occur.
problem:
Under linux-5.3-rc6 I get completely black screen.
output of 'startx -- :0' is not indicative of problem.
As far as I am concerned, silent failure with complete failure of output
system, hence high priority.
See dmesg please for more info.
md5sum /lib/firmware/amdgpu/navi10_*
d80e7585b046f9da0edfdf5c4840030c /lib/firmware/amdgpu/navi10_asd.bin
3f52075a7db731365236d3050aa23d9e /lib/firmware/amdgpu/navi10_ce.bin
d99c5124e5560153768a71cec8a4726e /lib/firmware/amdgpu/navi10_gpu_info.bin
98ddcd564bddf7ed6045afff4abf6704 /lib/firmware/amdgpu/navi10_me.bin
c9cd7f8cdd97c18f3068887f1877e2a6 /lib/firmware/amdgpu/navi10_mec2.bin
c9cd7f8cdd97c18f3068887f1877e2a6 /lib/firmware/amdgpu/navi10_mec.bin
2dd1563ba76158c98d9409eb94daab2e /lib/firmware/amdgpu/navi10_pfp.bin
39a53ba9e86b52fa6be045932bb0b12f /lib/firmware/amdgpu/navi10_rlc.bin
a4b33f7ad896e7b876dcb224f02faf4c /lib/firmware/amdgpu/navi10_sdma1.bin
a4b33f7ad896e7b876dcb224f02faf4c /lib/firmware/amdgpu/navi10_sdma.bin
26f69a4d53d4511c4587ce3713a70d99 /lib/firmware/amdgpu/navi10_smc.bin
0273f9cd89f85d58942e1a57be143077 /lib/firmware/amdgpu/navi10_sos.bin
b0f5b346a394d9ec4027ef01ba3853c7 /lib/firmware/amdgpu/navi10_vcn.bin
firmware is loaded into kernel at time of compilation.
usual compilation set done:
make -j12
make modules (this one seems redundant)
make modules_install
make install
grub-mkconfig -o /boot/grub/grub.cfg
after that /usr/src/linux is checked for link to current version of kernel.
additional notes.
machine IS responsive after start, just not the screen.
Brand new video card. works in kernel 5.2.10 in VESA mode
power cable checked
motherboard bios updated literally today till latest version
as far as I know no proprietary drivers loaded.
Module Size Used by
bridge 147456 0
stp 16384 1 bridge
llc 16384 2 bridge,stp
tun 53248 4
uvcvideo 106496 0
videobuf2_vmalloc 16384 1 uvcvideo
kvm_amd 90112 4
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 24576 1 uvcvideo
joydev 24576 0
mousedev 24576 0
kvm 651264 1 kvm_amd
videodev 184320 2 videobuf2_v4l2,uvcvideo
snd_virtuoso 49152 2
irqbypass 16384 5 kvm
snd_usb_audio 208896 0
videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo
snd_oxygen_lib 49152 1 snd_virtuoso
snd_hwdep 16384 1 snd_usb_audio
snd_usbmidi_lib 28672 1 snd_usb_audio
snd_mpu401_uart 16384 1 snd_oxygen_lib
snd_rawmidi 32768 2 snd_usbmidi_lib,snd_mpu401_uart
i2c_piix4 24576 0
sr_mod 28672 0
cdrom 36864 1 sr_mod
acpi_cpufreq 20480 0
k10temp 16384 0
Possibly some proprietary firmware is loaded in.
At least firmware from above, for AMDGPU itself.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-08-28 22:23 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 22:23 bugzilla-daemon [this message]
2019-08-28 22:25 ` [Bug 204725] black screen bugzilla-daemon
2019-08-28 22:34 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-29 2:36 ` bugzilla-daemon
2019-08-30 16:27 ` bugzilla-daemon
2019-08-31 4:31 ` bugzilla-daemon
2019-08-31 4:55 ` bugzilla-daemon
2019-08-31 17:58 ` bugzilla-daemon
2019-08-31 19:52 ` bugzilla-daemon
2019-08-31 19:56 ` bugzilla-daemon
2019-08-31 19:57 ` bugzilla-daemon
2019-08-31 20:39 ` bugzilla-daemon
2019-08-31 20:53 ` bugzilla-daemon
2019-08-31 20:55 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:57 ` bugzilla-daemon
2019-08-31 21:09 ` bugzilla-daemon
2019-08-31 21:11 ` bugzilla-daemon
2019-08-31 21:13 ` bugzilla-daemon
2019-08-31 21:38 ` bugzilla-daemon
2019-08-31 22:03 ` bugzilla-daemon
2019-08-31 22:07 ` bugzilla-daemon
2019-08-31 22:08 ` bugzilla-daemon
2019-09-01 0:43 ` bugzilla-daemon
2019-09-01 0:48 ` bugzilla-daemon
2019-09-01 7:17 ` bugzilla-daemon
2019-09-01 7:20 ` bugzilla-daemon
2019-09-01 7:22 ` bugzilla-daemon
2019-09-01 7:25 ` bugzilla-daemon
2019-09-01 7:30 ` bugzilla-daemon
2019-09-01 7:35 ` bugzilla-daemon
2019-09-01 7:40 ` bugzilla-daemon
2019-09-01 8:53 ` bugzilla-daemon
2019-09-01 8:59 ` bugzilla-daemon
2019-09-01 9:04 ` bugzilla-daemon
2019-09-01 9:04 ` bugzilla-daemon
2019-09-01 9:20 ` bugzilla-daemon
2019-09-01 9:29 ` bugzilla-daemon
2019-09-01 9:29 ` bugzilla-daemon
2019-09-01 17:08 ` bugzilla-daemon
2019-09-01 18:28 ` bugzilla-daemon
2019-09-02 10:42 ` bugzilla-daemon
2019-09-02 17:26 ` bugzilla-daemon
2019-09-02 18:06 ` bugzilla-daemon
2019-09-02 20:37 ` bugzilla-daemon
2019-09-03 21:17 ` bugzilla-daemon
2019-09-03 21:23 ` bugzilla-daemon
2019-09-03 21:25 ` bugzilla-daemon
2019-09-03 21:28 ` bugzilla-daemon
2019-09-03 21:30 ` bugzilla-daemon
2019-09-04 16:20 ` bugzilla-daemon
2019-10-05 11:49 ` bugzilla-daemon
2019-10-07 14:24 ` bugzilla-daemon
2019-10-07 16:11 ` bugzilla-daemon
2019-10-14 20:57 ` bugzilla-daemon
2019-10-14 20:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-204725-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.