You are not logged in.
Hello Dear Arch users,
On my laptop, since I upgraded to testing/linux 4.19.9 I cannot boot.
I tried to boot by using the following kernel parameters, and it works fine :
amdgpu.powerplay = 0
amdgpu.dc = 0
I suppose this problem is related to this old topic that I created myself:
https://bbs.archlinux.org/viewtopic.php?id=234901
This evening I will try:
- to upgrade all kernels (both linux and linux-hardened) to the last version/release,
- to start the hardened kernel with and without kernel options mentionned above,
- to start the NON-hardened kernel with and without kernel options mentionned above.
Then I will tell you.
Regards,
Me
Last edited by PolePosition (2018-12-31 16:27:19)
Life is not linear.
-----------
Arch power !
Offline
A short description of "cannot boot" would be nice. What happens and where exactly does it fail?
Offline
Possibly related https://bugs.archlinux.org/task/61117#comment175504
Offline
Hi,
Thanks. I read the link from @loqs.
I have the same laptop as the user "velemas" :
My system is Asus ROG GL702ZC with RX 580:
I will upgrade to last testing kernel and firmware this evening and it should be all right.
I'll confirm tomorrow.
Life is not linear.
-----------
Arch power !
Offline
Hi,
I had the same issue after Upgrading (boot stops after at KMS stage) on my Desktop with Vega64.
Possibly related https://bugs.archlinux.org/task/61117#comment175504
Downgrading kernels didn't help, but downgrading linux-firmware to 20181026.1cb4e51-1 after booting with nomodeset is a workaround for me until the next linux-firmware update.
I could not try linux mainline due to zfs-dkms not compiling.
Offline
I ran into the same issue, but after upgrading to 4.20.0-rc7-mainline I could finally boot into gdm. I also tried a different linux-firmware, but it didn't make any difference for me.
Offline
Hi,
I tried to upgrade to last stable kernel version of the repos but it doesn't help.
I still have to boot with the additional kernel parameter :
amdgpu.dc=0
Life is not linear.
-----------
Arch power !
Offline
Hi,
just to clarify my previous post:
My setup is pretty simple: RX580, GNOME with 4k resolution via DisplayPort (if that matters)
I removed any kernel parameters (I initially tried amdgpu.dc=0, without success). Instead I just compiled linux-mainline from AUR which is `4.20rc7-1` at the time of writing.
Since then I have the RX580 running flawlessly for me without issues.
Offline
I have the exact same laptop. Updated my system and boots to a black screen.
Offline
Hi Girafferson,
A workaround is to press the 'e' touch during GRUB step, and to add the kernel parameter "amdgpu.dc=0", then press F10 to boot.
Probably the problem has been introduced between linux-4.19.8 and linux-4.19.9. Not sure...
Can anyone tell me whether this issue is known by kernel/AMD developers?
Shall we open a bug report?
If the problem has been fixed in 4.20 it should be backported to 4.19, don't you think?
Regards
Life is not linear.
-----------
Arch power !
Offline
Several posters in this thread mentioned using gdm .
Has anyone tried to boot to multi-user.target (see systemd wiki page) to verify if this is a gdm / display manager problem or a kernel problem ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Hi Lone_Wolf,
I never use gdm.
But to be sure, I ran:
pacman -Qs gdm
and found "gdm libgdm".
Therefore I ran
pacman -R gdm libgdm
and also had to remove
pacman -R gnome-shell gdm libgdm
Then I restarted and checked systemctl
multi-user.target loaded active active Multi-User System
network-pre.target loaded active active Network (Pre)
network.target loaded active active Network
paths.target loaded active active Paths
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slices
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
timers.target loaded active active Timers
logrotate.timer loaded active waiting Daily rotation of log files
man-db.timer loaded active waiting Daily man-db cache update
shadow.timer loaded active waiting Daily verification of password and grou>
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
So as you can see multi-user.target is active.
After removing gdm libgdm and gnome-shell I tried to restart the mainline linux kernel from the repos but still get a black screen.
Had to restart by using CTRL+DEL then restart the mainline linux kernel with the kernel parameter "amdgpu.dc=0".
Last edited by PolePosition (2018-12-24 13:04:14)
Life is not linear.
-----------
Arch power !
Offline
I have also the Asus ROG GL702ZC and I have the same problem. I have to clarify something.
The system boots. And it boots correctly.... In a black screen.
The system does not initialize the internal monitor by it self. If I plug an external monitor both monitors work correct. After that if I unplug the external monitor the internal monitor continue to display image correct.
Up until kernel 4.19.8 everything is ok
With the kernels 4.19.9 11 12 the problem persist.
Offline
Im also have the black screen problem. When i turn on the computer, immediately the screen goes black and the external screen goes to save mode. The shorcuts doesnt work so im only have the hard reset button. There is no logs in journalctl about that session. I changed the resolution in grub but there is no difference.
I started two have this problem two weeks ago with the lts kernel. I changed to zen and arch but its the same.
Arch Plasma
AMD ATI Mobility Radeon HD 4225/4250
4.19.12-arch1-1-ARCH
Last edited by iara (2018-12-24 17:36:12)
Offline
@iara what packages were updated that caused the issue? What is the version of linux-firmware on your system? Do you use any out of tree kernel modules such DKMS drivers?
Edit:
If you are sure you have no out of tree kernel modules you could try linux 4.20.arch1-1 from staging.
Last edited by loqs (2018-12-24 17:42:44)
Offline
The only thing that it may be different with my system is that I have default installation of Antergos.
Firmware is the last one 20181218.0f22c85-1
Offline
FiltatosV6 I would suggest trying linux 4.20.
Offline
@iara what packages were updated that caused the issue? What is the version of linux-firmware on your system? Do you use any out of tree kernel modules such DKMS drivers?
-what packages were updated that caused the issue?
I don know what packages but i updated these: https://paste.debian.net/hidden/d49a4f3d/
-What is the version of linux-firmware on your system?
linux-firmware-20181218.0f22c85-1
-Do you use any out of tree kernel modules such DKMS drivers?
Im not sure about this but i think im not using them. sorry.
Offline
The two commits for amdgpu for linux-lts 4.14.88
commit eff5e74f7b680d51c9cd9a087f18ce99788b2aba
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Wed Nov 28 23:25:41 2018 -0500
drm/amdgpu/gmc8: update MC firmware for polaris
commit a81a7c9c9ea3042ab02d66ac35def74abf091c15 upstream.
Some variants require different MC firmware images.
Acked-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 99e6900dfa125ef5062e7b0595f6ce5eb75a6d2c
Author: Junwei Zhang <Jerry.Zhang@amd.com>
Date: Thu Nov 22 17:53:00 2018 +0800
drm/amdgpu: update mc firmware image for polaris12 variants
commit d7fd67653f847327e545bdb198b901ee124afd7c upstream.
Some new variants require updated firmware.
Signed-off-by: Junwei Zhang <Jerry.Zhang@amd.com>
Reviewed-by: Evan Quan <evan.quan@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
If you downgrade linux-lts to 4.14.87 without changing any other packages does linux-lts then work correctly?
Offline
Hi,
as FiltatosV6 wrote, the problem occurred between 4.19.8 and 4.19.9 (I am 95% sure of that).
Below are the DKMS modules that are installed on my system:
local/dkms 2.5-4
Dynamic Kernel Modules System
local/virtualbox-host-dkms 5.2.22-1
VirtualBox Host kernel modules sources
I have the feeling it is related to KMS issue because at that specific time I normally get flickering but now I only get a black screen.
Here is the version of linux-firmware I use:
local/linux-firmware 20181218.0f22c85-1 (base)
My system is fully up to date.
Sorry but I do not feel confortable with the idea of installing a Staging package... :-/
I just tried with linux-lts 4.14.90 and it works fine (with no need to use the amdgpu.dc=0 kernel parameter).
Last edited by PolePosition (2018-12-24 21:35:21)
Life is not linear.
-----------
Arch power !
Offline
@PolePosition https://bugs.freedesktop.org/show_bug.cgi?id=109122 looks to be the continuation of velemas from https://bugs.archlinux.org/task/61117#comment175504
You can try reverting the commit that velemas identified as the cause to confirm the issue is the same. Other than that I am out of suggestions.
Offline
The two commits for amdgpu for linux-lts 4.14.88
If you downgrade linux-lts to 4.14.87 without changing any other packages does linux-lts then work correctly?
Ok but the problem is present in the lts, zen and arch linux kernel. Currently im using the arch kernel and once a day (in the first boot) the screen start with a black screen until i hard reset and turn on again.
Offline
loqs wrote:The two commits for amdgpu for linux-lts 4.14.88
If you downgrade linux-lts to 4.14.87 without changing any other packages does linux-lts then work correctly?Ok but the problem is present in the lts, zen and arch linux kernel. Currently im using the arch kernel and once a day (in the first boot) the screen start with a black screen until i hard reset and turn on again.
You downgraded linux-lts and the issue is still present in 4.14.87?
Offline
iara wrote:loqs wrote:The two commits for amdgpu for linux-lts 4.14.88
If you downgrade linux-lts to 4.14.87 without changing any other packages does linux-lts then work correctly?Ok but the problem is present in the lts, zen and arch linux kernel. Currently im using the arch kernel and once a day (in the first boot) the screen start with a black screen until i hard reset and turn on again.
You downgraded linux-lts and the issue is still present in 4.14.87?
Yes. I have to hard reseting four times until the system boots properly. What can i do? Open a new thread with my problem?
Last edited by iara (2018-12-28 13:17:31)
Offline
Yes. I have to hard reseting four times until the system boots properly. What can i do? Open a new thread with my problem?
I would suggest trying 4.20.arch1-1 from testing. Do not enable the testing repositories as kernel space and user space is separate you can safely update jus the kernel package.
If that does not resolve the issue yes start a new thread with all the relevant information from this one.
Offline