From: George myglc2 Clemmer <myglc2@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30467@debbugs.gnu.org
Subject: bug#30467: GuixSD fails to display login prompt on headless server
Date: Fri, 23 Feb 2018 10:46:42 -0500 [thread overview]
Message-ID: <86a7vzbtel.fsf@gmail.com> (raw)
In-Reply-To: <20180222124139.26626adf@scratchpost.org>
On 02/22/2018 at 11:41 Danny Milosavljevic writes:
> Hi George,
>
> On Wed, 21 Feb 2018 20:35:34 -0500
> George myglc2 Clemmer <myglc2@gmail.com> wrote:
>
>> I think we got side-tracked to the serial port when my real issue is
>> with the VGA port. Maybe my bug report was not clear. Let me clarify ...
>
> Oh, that changes things. Ludo is debugging some silly UTF-8 problem
> with the virtual terminals on the VGA port right now - might be related,
> or not. Who knows...
Well this problem goes back to November. The problem first appears in
my generation 19 ...
19 GNU with Linux-Libre 4.14.2 (beta) 61 2017-11-30 19:18:15
18 GNU with Linux-Libre 4.13.12 (beta) 62 2017-11-11 13:05:56
... which correspond to ...
19 (GNU Guix) 0.13.0.5042-6e385
18 (GNU Guix) 0.13.0.4589-74bea6
Note: The results cited below are WRT my most recent build done
yesterday, guix (GNU Guix) 0.14.0.2455-26737.
>> GNU with Linuxlibre ..." for a couple seconds, and then 4) a blank.
>
> Is there still a cursor?
NO.
> What happens when you don't use the serial (so no console=...)
The VGA displays ...
- BIOS prompt
- grub menu
- 'Booting GNU linux-libre ...'
- ~1 seconds of messages
- Blank screen w/ no cursor
... which differers in that there are a couple seconds of boot messages.
> and then
> try to write something to /dev/console ? It should show up somewhere.
> Where? On the VGA port?
/home/g1# echo 123 > /dev/console
... shows nothing on the VGA or serial.
next prev parent reply other threads:[~2018-02-23 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 15:01 bug#30467: GuixSD fails to display login prompt on headless server George myglc2 Clemmer
2018-02-15 15:54 ` Danny Milosavljevic
2018-02-15 16:23 ` Leo Famulari
2018-02-15 21:29 ` George myglc2 Clemmer
2018-02-16 0:24 ` George myglc2 Clemmer
2018-02-16 0:53 ` Danny Milosavljevic
2018-02-16 1:38 ` George myglc2 Clemmer
2018-02-17 17:04 ` Danny Milosavljevic
2018-02-22 1:35 ` George myglc2 Clemmer
2018-02-22 3:29 ` George myglc2 Clemmer
2018-02-22 11:41 ` Danny Milosavljevic
2018-02-23 15:46 ` George myglc2 Clemmer [this message]
2018-02-24 14:51 ` Danny Milosavljevic
2018-02-26 17:02 ` George myglc2 Clemmer
2018-02-26 17:32 ` Danny Milosavljevic
2018-02-26 18:50 ` George myglc2 Clemmer
2018-02-27 12:08 ` Danny Milosavljevic
2018-02-27 13:39 ` George myglc2 Clemmer
2018-02-17 17:05 ` Danny Milosavljevic
2018-03-08 14:16 ` myglc2
2018-03-09 23:23 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a7vzbtel.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=30467@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).