| Bug ID | 101029 |
|---|---|
| Summary | notebook does not work when not booted using nomodeset AMD APU |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | critical |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | stein12c@gmail.com |
in kernel 4.10 and higher unable to boot without enabling nomo= deset option which also removes 3D acceleration for AMD APU processors with hybrid graph= ics. See the following link for full detail on the bug: ht= tps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683184
| What | Removed | Added |
|---|---|---|
| URL | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683184 |
Please attach the dmesg output corresponding to the problem he= re directly.
| What | Removed | Added |
|---|---|---|
| CC | stein12c@gmail.com |
Created attachment 131361 =
[details]
CurrentDMesg
attached dmesg from another user with the same bug
| What | Removed | Added |
|---|---|---|
| Attachment #131361 is obsolete | 1 |
Comment on attachment 13=
1361 [details]
CurrentDMesg
This dmesg is with nomodeset, so it doesn't contain any information related=
to
the problem.
Please attach the dmesg output from an attempt without nomodeset.
(In reply to Michel D=C3=A4nzer from comment #3) > Comment on attachment 131361 [details] > CurrentDMesg >=20 > This dmesg is with nomodeset, so it doesn't contain any information re= lated > to the problem. >=20 > Please attach the dmesg output from an attempt without nomodeset. I am not sure how to get a dmesg out of it. Does Dmesg log to a file somewhere? I can't boot into the OS and output anything to text file as it just provides a "AMD-Vi: Completion-Wait loop timed out" and a bu= nch of disk checks that kept failing never allowing me to logon. I left it for 8-9 hou= rs and i was still unable to do anything with the system other than a Ctrl-Alt-SysRq REISUB. Please let me know how to proceed. thanks
(In reply to Craig from comment #4) > Does Dmesg log to a file somewhere? Depending on your distro, it might be captured in /var/log/kern.log*, /var/log/dmesg*, or in the systemd journal.
(In reply to Craig from comment #6) > Created attachme= nt 131377 [details] > Bootup Screenshot I am running Ubuntu 17.04. Anyways I have checked through the logs (kern.lo= g, syslog and it appears that the last time it recorded anything in them was = when I was using "nomodeset" on bootup. I have attached screenshots o= f what I get when I boot up without nomodeset as a parameter. Is it possible that it is= not writing to disk when I bootup without "nomodeset"? There is no dm= esg log in the /var/log folder. It appears that I could use journalctl -b but that only wo= rks if I am able to boot into the system or the dmesg command but also needs to= be able to boot into it to run that.
Okay, I guess we need to try another trick: Boot with
modprobe.blacklist=3Damdgpu
on the kernel command line to prevent the amdgpu module from being loaded
automatically. Once the system is booted up, manually run
sudo modprobe amdgpu
This should increase the chance of capturing the dmesg output somewhere.
ok I added the modprobe.blacklist=3Damdgpu to the kernel comma= nd line, wouldnt boot until I also added modprobe.blacklist=3Dradeon. Anyways once I was in = I did run sudo modprobe amdgpu and got the usual "AMD-Vi: Completion-Wait lo= op timed out" amongst other errors. It did log some strange things in kern.log= and syslog. I also ran dmesg -k >/home/craig/DMESG.txt and it created a file= with nothing in it. I will attach the kern.log and syslog... not sure if that he= lps, as you can see i am very new at doing this kind of thing.
| What | Removed | Added |
|---|---|---|
| Attachment #131381 mime type | text/x-log | text/plain |
Looks like https://patchwork.freedesktop.org/patch/146519/ might help, or passing iommu=3Dsoft on the kernel command line might serve as a workaround= .
where do i find the amd_iommu.c in ubuntu 17.04 so that I can = patch it? or is there a different method? I was considering using this syntax: patch -p[num= ] < patchfile patch [options] originalfile patchfile thanks very much
(In reply to Craig from comment #15) > where do i find the amd_iommu.c in ubuntu 17.04 = so that I can patch it? or > is there a different method? I was considering using this syntax: patch > -p[num] < patchfile > patch [options] originalfile patchfile > thanks very much please disregard this i believe i found a solution.
I can't seem to find the amd_iommu.c file, would you be able t= o point me to where it is? also what would be the proper syntax to run the patch program?= it seems to indicate -p or --strip but i am to sure what number to enter after= it.
-p1 should work in the top level directory of a Linux kernel s= ource tree. Have you confirmed that iommu=3Dsoft on the kernel command line works aroun= d the problem?
using iommu=3Dsoft on the kernel command line and it is now ha= rd freezing. I will try and get the patch applied next. I can't Ctrl-Alt-Del or Ctrl-Alt-SysRq-REISUB to reboot.