From: "Virgil" <yyz001@euroseek.com>
To: linux-laptop@vger.kernel.org
Subject: Kernel problems with HP ze4145
Date: Thu, 24 Apr 2003 20:56:39 -0400 [thread overview]
Message-ID: <web-3290494@euroseek.com> (raw)
Hello,
This particular laptop has an Athlon XP1800 mobile
processor with an ALI USB 1.1 controller. It uses a
synaptics PS/2 touchpad. In the following I'll try to best
describe the problem I have.
Kernel versions covered: 2.4.19 - 2.4.21pre6 patched with
acpi-patch. Distribution: none (LFS 4.0)
1) I compiled the kernel with usb support built-in (not as
modules). Upon booting and entering the login prompt, the
keyboard is blocked (i.e. I can't write anything with it).
If I press the power button, the computer enters runlevel
6 (so it is not frozen) and powers off.
2) Recompile the kernel with usb as modules (usbcore and
usb-ohci) and do a script in /etc/rc.d/init.d/ to load the
modules at boot time. Symptoms stay as above.
3) Remove the script from /etc/rc.d/rc3.d (e.g.). Boot.
Login as root. The keyboard works (yee!). Do cat
/dev/mouse. Keyboard no longer works (all three LEDs light
up). Reboot.
4) Do step 3 above but don't cat the mouse anymore.
Instead do modprobe usbcore and modprobe usb-ohci. The
keyboard is NOT blocked. Do cat /dev/mouse. The mouse
works (yee). Do mount -t usbdevfs none /proc/bus/usb. The
USB filesystem is initialised and the USB works
beautifully (tested with a digital camera and a scanner).
So, does any1 have a similar problem and a real solution
on this thing? Do I do something wrong? Is this a kernel
bug?
Virgil
-------------------------------------------------
Search for pictures with Euroseek Image Search
http://euroseek.com/image_search/
Euroseek Translation
http://www.euroseek.com/translator/
next reply other threads:[~2003-04-25 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:56 Virgil [this message]
[not found] <20030425111159.GB660@erdbeere.net>
2003-04-27 17:28 ` Kernel problems with HP ze4145 Virgil
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=web-3290494@euroseek.com \
--to=yyz001@euroseek.com \
--cc=linux-laptop@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).