All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Bugfix] Hang on new mac laptops
Date: Sun, 8 Feb 2009 19:00:59 +0100	[thread overview]
Message-ID: <20090208180059.GA22127@thorin> (raw)
In-Reply-To: <acc911d90902080902p572ed0d5vfd416a99cc3a9141@mail.gmail.com>

On Sun, Feb 08, 2009 at 06:02:27PM +0100, step21 wrote:
> I made an *.efi with a few modules (for convenience and cause the minimal
> build somehow didn't want to load anything, but that could have been me)
> Then I loaded at_keyboard with "insmod at_keyboard" that worked. Then when I
> do "terminal_input at_keyboard" it doesn't give me a new prompt and seems to
> "hang".
> How to further debug this?

Before insmod:

  set debug=at_keyboard

and check the output (of both commands)

> What is expected behaviour?

Expected behaviour is that your prompt doesn't hang like you described,
but lets you continue typing instead.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-02-08 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 21:30 [Bugfix] Hang on new mac laptops phcoder
2009-02-03 22:06 ` Pavel Roskin
2009-02-04  7:56   ` phcoder
2009-02-07 22:34     ` Robert Millan
2009-02-08 17:02       ` step21
2009-02-08 18:00         ` Robert Millan [this message]
2009-02-08 18:52           ` step21
2009-02-08 19:55             ` Robert Millan
2009-02-09  1:46               ` step21
2009-02-09 14:05                 ` Robert Millan
2009-03-11 20:57     ` phcoder

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090208180059.GA22127@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.