From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 193651] Amdgpu error messages at boot with Amd RX460
Date: Sat, 25 Mar 2017 20:58:13 +0000 [thread overview]
Message-ID: <bug-193651-2300-sqtSWKM6k1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-193651-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=193651
Milo (milomak@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |milomak@gmail.com
--- Comment #15 from Milo (milomak@gmail.com) ---
(In reply to fin4478 from comment #8)
> Alex, thanks for the new firmware. Still Bios recognition errors at boot,
> but otherwise ok.
>
> [ 3.461112] [drm] BIOS signature incorrect 20 7
> [ 3.461117] amdgpu 0000:01:00.0: Invalid PCI ROM header signature:
> expecting 0xaa55, got 0xffff
>
> Steven, you are using Tonga gpu and radeon kernel driver that fails at boot
> and the system using VESA driver. The amdgpu driver has support for Tonga,
> but you need to make a custom 4.11-wip kernel. Stock distribution kernels do
> not have stable amdgpu code. Creating a custom kernel in Debian:
> Use the command:
> git clone -b drm-next-4.11-wip git://people.freedesktop.org/~agd5f/linux
>
> The kernel configuration file of Debian Official kernel are available in
> /boot, named after the kernel release. Copy the .config file to the linux
> directory. Connect all your devices and run the command: make
> localmodconfig. You can use the command make defconfig too for creating
> initial .config file.
>
> Use the command: make xconfig and check that you have enabled: Reroute
> Broken IRQ, Virtualization KVM and 300Hz CPU timer, I also disabled Swap,
> Kernel Debug, CPU Freq scaling , Cpu handling in Acpi, Used Bios to control
> CPU and devices. In the drivers->graphics->amdgpu enable cik support for a
> gcn 1.1 gpu and si support for a gcn 1.0 gpu.
>
> Create debian kernel package:
> export CONCURRENCY_LEVEL=4
> fakeroot make-kpkg --initrd kernel_image
>
> Install the kernel package with Gdebi. To make a custom kernel to boot, add
> a line to /etc/initramfs-tools/modules:
> unix
> And run: sudo update-initramfs
> Reboot.
I tried the above but notice that it fails when trying to build headers.
If I am trying to build a 4.10.5 kernel, could I copy files from what was
downloaded when I ran the git command?
--
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 prev parent reply other threads:[~2017-03-25 20:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 13:58 [Bug 193651] New: Amdgpu error messages at boot with Amd RX460 bugzilla-daemon
2017-01-31 16:26 ` [Bug 193651] " bugzilla-daemon
2017-01-31 16:26 ` bugzilla-daemon
2017-01-31 16:26 ` bugzilla-daemon
2017-01-31 16:27 ` bugzilla-daemon
2017-01-31 16:33 ` bugzilla-daemon
2017-01-31 16:35 ` bugzilla-daemon
2017-02-01 22:11 ` bugzilla-daemon
2017-02-02 10:19 ` bugzilla-daemon
2017-02-02 10:32 ` bugzilla-daemon
2017-02-02 15:01 ` bugzilla-daemon
2017-02-02 15:49 ` bugzilla-daemon
2017-02-02 22:26 ` bugzilla-daemon
2017-02-02 22:28 ` bugzilla-daemon
2017-02-02 22:31 ` bugzilla-daemon
2017-03-25 20:58 ` bugzilla-daemon [this message]
2017-03-26 3:22 ` bugzilla-daemon
2017-03-26 7:50 ` bugzilla-daemon
2017-03-26 10:16 ` bugzilla-daemon
2017-03-26 10:18 ` bugzilla-daemon
2017-04-03 22:51 ` bugzilla-daemon
2017-04-04 12:15 ` bugzilla-daemon
2017-04-04 13:36 ` bugzilla-daemon
2017-04-05 18:59 ` bugzilla-daemon
2017-06-01 12:34 ` bugzilla-daemon
2017-09-15 21:48 ` bugzilla-daemon
2017-10-23 18:11 ` bugzilla-daemon
2017-10-24 17:18 ` bugzilla-daemon
2017-11-13 7:51 ` bugzilla-daemon
2018-12-05 2:29 ` bugzilla-daemon
2019-11-11 11:05 ` 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-193651-2300-sqtSWKM6k1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).