> On Mon, Feb 23, 2009 at 3:40 AM, Saifi Khan <saifik...@gmail.com> wrote: >> Hi all: >> >> i'm facing keyboard access issue when trying to install OpenBSD 4.4 on >> Intel, Compaq laptop.
>> Both FreeBSD 7.1 and Gentoo Linux 2008.0r2 work fine on the system. >> >> Here is the information that i culled from the Linux environment (if >> that helps). >> >> listing of all the PCI devices >> >> 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML >> and 945GT Express Memory Controller Hub (rev 03) >> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, >> 943/940GML Express Integrated Graphics Controller (rev 03) >> 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, >> 943/940GML Express Integrated Graphics Controller (rev 03) >> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High >> Definition Audio Controller (rev 01) >> 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express >> Port 1 (rev 01) >> 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express >> Port 3 (rev 01) >> 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB >> UHCI Controller #1 (rev 01) >> 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB >> UHCI Controller #2 (rev 01) >> 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB >> UHCI Controller #3 (rev 01) >> 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 >> EHCI Controller (rev 01) >> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) >> 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface >> Bridge (rev 01) >> 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE >> Controller (rev 01) >> 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) >> SATA AHCI Controller (rev 01) >> 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev >> 01) >> 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan >> mini-PCI (rev 01) >> 08:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. >> RTL-8139/8139C/8139C+ (rev 10) >> >> cat /proc/interrupts >> CPU0 >> 0: 486923 IO-APIC-edge timer >> 1: 8375 IO-APIC-edge i8042 >> 8: 52 IO-APIC-edge rtc >> 9: 2490 IO-APIC-fasteoi acpi >> 12: 158589 IO-APIC-edge i8042 >> 14: 35 IO-APIC-edge ide0 >> 17: 57795 IO-APIC-fasteoi uhci_hcd:usb4, bcm43xx >> 18: 0 IO-APIC-fasteoi uhci_hcd:usb3 >> 19: 382 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2 >> 20: 79159 IO-APIC-fasteoi HDA Intel >> 221: 8440 PCI-MSI-edge ahci >> NMI: 0 Non-maskable interrupts >> LOC: 83471 Local timer interrupts >> TRM: 0 Thermal event interrupts >> SPU: 0 Spurious interrupts >> ERR: 0 >> MIS: 0 >> >> Any pointers or suggestions as to how i can make the keyboard >> functional with openBSD 4.4 >> >> -- >> thanks >> Saifi. 2009/2/25 Saifi Khan <saifik...@gmail.com>: > > Here is the link to the openbsd dmesg output image. > http://tinypic.com/view.php?pic=30b0bvl&s=5 > > -- > thanks > Saifi. 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. ;-)
