> On Mon, Feb 23, 2009 at 3:40 AM, Saifi Khan <saifikhan@gmail.com> wrote:
2009/2/25 Saifi Khan <saifikhan@gmail.com>:
I see. Now that picture ( http://s5.tinypic.com/30b0bvl.jpg )
obviously only shows partial lines of a small part of the entire dmesg
output. You appear to have captured the part of the dmesg that is
relevant to the keyboard; to wit:
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: unable to establish interrupt for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
However, a full dmesg would really be required to properly
troubleshoot this, in order to know what devices may be interfering
(what's denying the keyboard slot its interrupt?), and to know the
precise version of OpenBSD 4.4 you are running (GENERIC? The version
from an official CD-ROM? Or a self-compiled kernel (which is frowned
upon)? Or an old 4.4 -CURRENT version? Etc., etc.).
Also, you didn't mention the exact make/model of your PC, you only
mentioned that it was an Intel, Compaq laptop. Again, this is where a
full dmesg would be helpful. A full dmesg also allows you to start
googling excerpts from it, and figure out if someone has bumped into
the same issue before.
Does OpenBSD ever finish booting? And once booted up, are you at all
able to access the machine at all? If the main keyboard does not work
once you've booted, you could try redirecting console I/O to a serial
console ( http://openbsd.org/faq/faq7.html#SerCon ). After doing that,
can you access the full dmesg (@ /var/run/dmesg.boot , cf.
http://www.openbsd.org/cgi-bin/man.cgi?query=dmesg ) and maybe make a
copy of that and send it to this list?
Also, some cursory googling revealed this:
http://kerneltrap.org/mailarchive/openbsd-misc/2008/6/12/2104294
Your laptop wouldn't be a Compaq Presario C300, would it?
If you disable acpi/acpiprt via boot -c (cf.
http://www.openbsd.org/cgi-bin/man.cgi?query=boot_config ,
http://www.openbsd.org/cgi-bin/man.cgi?query=boot ), does the keyboard
get its interrupt and work then? (Cf.
http://kerneltrap.org/mailarchive/openbsd-misc/2008/6/24/2211174 )
See also http://www.nabble.com/bug-report-tt20394469.html#a20406968 ,
http://www.google.ie/search?hl=en&safe=off&q="unable+to+establish+interrupt+for+kbd+slot"
.
You could also not just try booting the GENERIC.MP kernel, but also
try booting from one of the three floppy images, and see if you can
get the keyboard to work that way.
Now let me admit here that I'm not an actual developer myself, and I
probably can't ultimately resolve your problem -- but if you're trying
to get the attention of more competent people here, possibly including
developers (if applicable), then taking the above on board definitely
can't hurt. ;-)
By the way, on a machine that I use and that works (but still runs
4.3), the keyboard dmesg lines are:
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
Again, I'm not a developer, but I'm guessing that this sort of does this:
- detect pckbc0, which seems to be the keyboard controller
- detect pckbd0, which seems to be the keyboard slot of that controller
- have the keyboard controller assign IRQ 1 to the keyboard slot
- bring up the console keyboard wskbd0 at the keyboard slot
But maybe that's just crazy-talk.
Again, there are probably dozens of folks here who can tell you in
much more detail what's really going on.
Have fun, and good luck with getting your machine to play ball. :)
kind regards,
--ropers
PS: Your job descriptions scares me:
http://www.linkedin.com/pub/0/825/502 Please don't hurt me. ;-)
