From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Subject: Re: kmscon not working on MacBook
Date: Mon, 09 Mar 2020 17:45:45 +0100
Message-ID: <87h7yx1npi.fsf@gnu.org>
References: <86lfoqy8h0.fsf@dismail.de> <87pne3d5t6.fsf@gnu.org>
 <60bd323b399bc4fafefc74d7fa84c0db@dismail.de>
 <20200308120400.bdrkyo653fhbtkml@pelzflorian.localdomain>
 <87a74q8spt.fsf_-_@gnu.org>
 <20200309074358.jly3mtrevwm75wip@pelzflorian.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:52615)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <ludo@gnu.org>) id 1jBLXK-0005PZ-0x
 for guix-devel@gnu.org; Mon, 09 Mar 2020 12:45:50 -0400
In-Reply-To: <20200309074358.jly3mtrevwm75wip@pelzflorian.localdomain>
 (pelzflorian@pelzflorian.de's message of "Mon, 9 Mar 2020 08:43:58
 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org, jbranso@dismail.de

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> On Sun, Mar 08, 2020 at 10:03:26PM +0100, Ludovic Court=C3=A8s wrote:
>> In the past, Mathieu, Florian, and others looked at similar issues on
>> some graphics boards.  Perhaps there=E2=80=99s something we can do here =
to
>> special-case this hardware?
>>=20
>> Ludo=E2=80=99.
>
> The affected hardware is diverse and I see no pattern.  I would favor
> restarting with mingetty.  However, the installer runs but just has no
> display, so I do not know how to detect it.
>
> My Macbook using =E2=80=9CNVIDIA Corporation MCP89 [GeForce 320M] (rev a2=
)=E2=80=9D
> runs the installer just fine.
>
> A desktop PC using =E2=80=9CNVIDIA Corporation GM107 [GeForce GTX 750 Ti]=
 (rev
> a2)=E2=80=9D runs it just fine too.
>
> Another PC using =E2=80=9CAdvanced Micro Devices, Inc. [AMD/ATI] Oland PRO
> [Radeon R7 240/340]=E2=80=9D runs the installer just fine (but not Xorg X=
).
>
> A laptop Acer Aspire 5738 using =E2=80=9CAdvanced Micro Devices,
> Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]=E2=80=9D *fa=
ils*
> with a black screen; manual installation is required (which I have not
> tested but probably works).
>
> Another laptop Uniwill U50SI1 using =E2=80=9CSilicon Integrated Systems [=
SiS]
> 771/671 PCIE VGA Display Adapter (rev 10)=E2=80=9D *fails* the same way.
> Manual install works fine.  Note that I cannot boot non-Windows
> install images (Debian or Guix) on this machine, only via DVD, and
> Xorg X server only runs using uvesafb with a v86d helper.
>
> None of these installers flicker; the screen is black or it runs fine.

For the cases where kmscon actually fails (exit with a non-zero code),
a solution would be the following: instead of running kmscon directly,
we run a wrapper around it that spawn mingetty (as you suggested) when
kmscon exits with non-zero.

(Perhaps the flickering Joshua mentioned was actually due to kmscon
being continuously restarted by shepherd?)

However, in cases where kmscon does *not* exits and simply produces a
black screen, I don=E2=80=99t see what can be done.  In the cases you list
above, does kmscon simply sit there without exiting?

At any rate, thanks for the testing & detailed info!

Ludo=E2=80=99.