public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <jerdfelt@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] USB Support
Date: Thu, 15 Jun 2000 20:19:19 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205150@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205134@msgid-missing>

On Thu, Jun 15, 2000, Jonathan_Kwahk@Dell.com <Jonathan_Kwahk@Dell.com> wrote:
> I think USB keyboard upon boot up and EFI shell is dependent on the firmware
> build you have as well as the hardware revision.  I have gotten certain USB
> keyboards and mice to work within the BIOS configuration manager and EFI
> Shell.   However, when you run ELI vmlinux it'll report an error.  With
> PS/2, you get farther along the installation (complete it).

I'm interested in finding out what errors you're seeing. ELI uses the
standard Text Input protocol which EFI should handle regardless if it's
PS/2 or USB.

> Someone has recommended that I download all the patches and updates,
> recompile the kernel, and install it.

I'll try this as well.

> So far, USB mouse/keyboard doesn't work IN the installation.  I'm not
> talking about the kernel load or the OS itself.  Just the installation.
> Turbolinux 0505.

Gotcha. I haven't tried this. I don't know why this wouldn't work except
for explicitily not compiling in USB for the install kernel.

> I'll see what happens when I get the updates recompiled.

JE




  parent reply	other threads:[~2000-06-15 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-13 16:17 [Linux-ia64] USB Support Jonathan_Kwahk
2000-06-13 18:15 ` Johannes Erdfelt
2000-06-13 19:49 ` Jonathan_Kwahk
2000-06-13 19:53 ` Johannes Erdfelt
2000-06-15  9:40 ` Eric Wang
2000-06-15 17:47 ` Johannes Erdfelt
2000-06-15 18:16 ` David Mosberger
2000-06-15 20:09 ` Jonathan_Kwahk
2000-06-15 20:19 ` Johannes Erdfelt [this message]
2000-06-15 22:29 ` Jonathan_Kwahk

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=marc-linux-ia64-105590678205150@msgid-missing \
    --to=jerdfelt@valinux.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox