Your message dated Tue, 02 Apr 2019 14:29:11 +0100 with message-id <603cce7816442a5033d77a171962fa90039cf219.camel@decadent.org.uk> and subject line Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen has caused the Debian Bug report #926149, regarding AMD: Add nomodeset kernel parameter to avoid black screen to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 926149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926149 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: AMD: Add nomodeset kernel parameter to avoid black screen
- From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
- Date: Mon, 01 Apr 2019 15:59:12 +0800
- Message-id: <[🔎] 874l7i9mwf.fsf@jidanni.org>
Package: installation-reports With the latest AMD CPUs the kernel will attempt to use the AMDGPU kernel driver. Alas this will result in a black screen on the minimal system installed by the installer. Therefore on all three of these lines in /boot/grub/grub.cfg linux /boot/vmlinuz-... root=... the parameter "nomodeset" needs to occur. Yes, even for the "recovery mode entry". (Users reading this bug would want to add it by using "e" when looking at the grub boot screen, to get their system booted. Then put it in GRUB_CMDLINE_LINUX= in /etc/default/grub and then run grub-install. For full logs please see #925556.
--- End Message ---
--- Begin Message ---
- To: 926149-done@bugs.debian.org
- Subject: Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Tue, 02 Apr 2019 14:29:11 +0100
- Message-id: <603cce7816442a5033d77a171962fa90039cf219.camel@decadent.org.uk>
- In-reply-to: <[🔎] 87bm1obldn.fsf@jidanni.org>
- References: <[🔎] 874l7i9mwf.fsf@jidanni.org> <[🔎] b55c286e8b4a9db96bf37cca9d10861ffd027305.camel@decadent.org.uk> <[🔎] 87bm1obldn.fsf@jidanni.org>
On Tue, 2019-04-02 at 21:13 +0800, 積丹尼 Dan Jacobson wrote: > I'll be very happy to help you test this week. > Next week I wish to proceed with final installation though. > > BH> Was the firmware (firmware-amd-graphics package) installed on your test > BH> system? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925556#25 > mentions what ISO I used, and all logs are attached to that bug report. > > Note I do all my installs offline with just the ISO. So you used a netinst image with no network. I don't think this should be expected to work. Ben. > I recall having worked around the /dev/sdX issue, one can get as far as > (Staring at the stuck screen with one of the last messages being amdgpudrmfb ...) > > I recall with nomodeset in effect, logs will contain > [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. > but at least one can still use the computer. -- Ben Hutchings Klipstein's 4th Law of Prototyping and Production: A fail-safe circuit will destroy others.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---