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: Mon, 9 Feb 2009 15:05:00 +0100 [thread overview]
Message-ID: <20090209140500.GA4394@thorin> (raw)
In-Reply-To: <acc911d90902081746y3473176do598cf0b8fef42677@mail.gmail.com>
On Mon, Feb 09, 2009 at 02:46:01AM +0100, step21 wrote:
> Ok, confirmed that keyboard is attached with usb. lsusb wans't very helpful
> cause apart from wireless and bluetooth it only mentioned "apple devices"
> and "linux foundation devices" however os x has a similiar command line tool
> ioreg which with -p IOUSB can be restricted to usb. Output
> http://pastebin.com/m4d3e9c83
> I then updated to the usb patch with rev 1985, and compiled etc. debug still
> seemed to do nothing and as previously terminal_input at_keyboard forces to
> manually swithc the machine off.
Use the following:
insmod uhci ; insmod usb_keyboard ; terminal_input usb_keyboard
It is important to use semicolons, since after "insmod uhci" your keyboard
will stop working (and hopefully be restored with "terminal_input usb_keyboard")
--
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."
next prev parent reply other threads:[~2009-02-09 14:05 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
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 [this message]
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=20090209140500.GA4394@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.