From: Max Kovgan <maxk@cs.Technion.AC.IL>
To: linux-ia64@vger.kernel.org
Subject: discontinued zx1 based machine: hp zx6000. problems
Date: Wed, 23 Feb 2005 01:29:05 +0000 [thread overview]
Message-ID: <200502230129.j1N1T5Ap007480@csd.cs.technion.ac.il> (raw)
Hello, list!
Either my hands are skewed or something is wrong with this ia64 port, or even worse.
i am a debian user.
hardware: zx6000, no ps/2, only usb keyboard ( this one has also 2 usb sockets, so it should also be a USB hub )
my woes:
tried installing sarge: linux 2.4.21 (mckinley-smp).
during the installer keyboard worked.
after the installation's 1st boot - everything worked.
ok.. trying to upgrade....
tried 2.6.9-2 ( mckinley-smp ) - installer worked ok.
after a reboot - cannot use neither keyboard nor mouse.
ok, i thought to myself. let's tune a kernel for the machine.
got 2.6.10. vanilla.
configured, built, rebooted:
same result as with mckinley 2.6.9
at 1st i suspected it's a problem of bad usb driver taking over the hardware. so i've rebuilt the system with:
a) only ehci - no success
b) only uhci - no success
c) both.
i probably will next week recompile only with ohci support, and so on through all the combinations.
i just am curious: why don't the keyboard/mouse work ?
i am ready to test code, even to code the code, as soon as can locate who's responsible for the problem (which part of the kernel)
i have grepped through the kernel source about zx1 ... haven't found anything interesting related to usb.
well.... direct me, please.
what shall i do next ?
Best regards,
M.
--
When you are at Rome live in the Roman style; when you are elsewhere live as they live elsewhere. -- St. Ambrose
next reply other threads:[~2005-02-23 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 1:29 Max Kovgan [this message]
2005-02-23 1:41 ` discontinued zx1 based machine: hp zx6000. problems dann frazier
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=200502230129.j1N1T5Ap007480@csd.cs.technion.ac.il \
--to=maxk@cs.technion.ac.il \
--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