On Mon, Mar 09, 2020 at 05:45:45PM +0100, Ludovic Courtès wrote:
> However, in cases where kmscon does *not* exits and simply produces a
> black screen, I don’t see what can be done.  In the cases you list
> above, does kmscon simply sit there without exiting?
> 

When run with --debug, kmscon displays not quite helpful errors:

[0000.488942] DEBUG: pty: forking child 28378 (pty_spawn() in src/pty.c:422)
[0000.490819] DEBUG: pty: HUP on pty of child 28378 (pty_input() in src/pty.c:520)
[0000.490866] DEBUG: eloop: child 28378 exited with status 1 (sig_child() in src/eloop.c:350)
[0000.490883] INFO: pty: child exited: pid: 28378 status: 256 (sig_child() in src/pty.c:536)

over and over again.  (The errors are visible after killing kmscon.)

I’m not sure if that is a good means for detection.



"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> A laptop Acer Aspire 5738 using “Advanced Micro Devices,
> Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]” *fails*
> with a black screen; manual installation is required (which I have not
> tested but probably works).
>

I could get the installer to display properly by using my unfinished
package for the useful v86d helper (attached):

guix package -f v86d.scm
ln -s /gnu/store/yj9mxi0yr4ksg5v7031mdrc8fvb2wxrb-linux-libre-5.4.24/lib/ /lib
modprobe uvesafb v86d=/root/.guix-profile/sbin/v86d

Without the symbolic linking, kmscon displays a flickering Module
uvesafb not found in directory /lib/modules…

I will try to properly package v86d now (without bundled libraries).
uvesafb does not work on my Macbook though; I believe it conflicts
with modesetting.

Regards,
Florian