From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Please add better line editing
Date: Mon, 03 Apr 2017 09:06:07 +0000 [thread overview]
Message-ID: <CAEaD8JOzeRYcvmpdHw5p8=M8wRsPRHKHK=hNwAhicVYSgQSLEA@mail.gmail.com> (raw)
In-Reply-To: <CAN9vWDLpS_YRpz=sA8XWW4Q5eRDB=nhM0=V_4_R2xAkMHAy+aA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Sun, Apr 2, 2017, 19:48 Michael Zimmermann <sigmaepsilon92@gmail.com>
wrote:
> are you booting grub in BIOS or UEFI mode? GRUB in BIOS mode is
> usually pretty slow because it constantly has to switch between real
> and protected mode.
Not an issue.
> In UEFI, GRUB is running at full speed.
>
Doesn't matter.
Most common reason for slowness is high graphics resolution.
>
> Ofc, that doesn't help you if you need to boot in BIOS mode, but it's
> a hint at where the slowness may come from.
>
> Thanks
> Michael
>
> On Mon, Mar 27, 2017 at 9:43 AM, gobnat <gobnat@optusnet.com.au> wrote:
> > Hi
> >
> > I've had trouble with booting my system recently and have had to edit the
> > parameters during boot. I have a long boot line (kernel text + 115 chars
> of
> > optional params) and getting to the right place (about char 80) is very
> > tedious. The key repeat seems to be very slow. It also buffers the key
> > repeats. I release the key and the cursor continues moving for several
> > seconds. I need to press the arrow key, hold it down and guess when it's
> > going to get where I want it.
> >
> > Also nice to have would be ctrl+left/right to navigate one "word" at a
> time.
> >
> > Thanks
> >
> > Brendan
> >
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: Type: text/html, Size: 3417 bytes --]
prev parent reply other threads:[~2017-04-03 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 7:43 Please add better line editing gobnat
2017-04-03 5:48 ` Michael Zimmermann
2017-04-03 9:06 ` Vladimir 'phcoder' Serbinenko [this message]
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='CAEaD8JOzeRYcvmpdHw5p8=M8wRsPRHKHK=hNwAhicVYSgQSLEA@mail.gmail.com' \
--to=phcoder@gmail.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.