From: David Schwartz <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: atkbd works as module but not linked in, 2.5.5-dj3
Date: Wed, 6 Mar 2002 16:38:06 -0800 [thread overview]
Message-ID: <20020307003808.AAA19282@shell.webmaster.com@whenever> (raw)
This is a strange problem. I have CONFIG_KEYBOARD_AT set, and my System.map
file has the correct entries to show that the atkbd.c file was linked into my
kernel. Yet my AT keyboard is not detected. 'dmesg' shows:
hdc: hdc1 hdc2 < hdc5 hdc6 hdc7 >
mice: PS/2 mouse device common for all mice
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
NET4: Linux TCP/IP 1.0 for NET4.0
Now here's the strange part -- if I manually compile atkbd.c as a module and
'insmod' it, this appears:
input: AT Set 2 keyboard on isa0060/serio0
And then the keyboard works. Am I doing something wrong? Everything worked
fine with 2.5.5-dj1, I have not tested 2.5.5-dj2 but would be glad to do so
if anyone thought it might help.
System is a dual p3-750, 440BX chipset. I'm going to keep looking into it,
checking the code that should initialize the keyboard and also looking at the
diffs closely.
--
David Schwartz
<davids@webmaster.com>
reply other threads:[~2002-03-07 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020307003808.AAA19282@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=linux-kernel@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