[parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Andy Walker]

I've a B132L running Gentoo. With 2.4 I had the PS/2 keyboard working fine
throught a Raritan Compuswitch KVM, but the mouse (wireless Intellimouse
clone - 2 buttons pluss roller/middle) was dead. Decided to try out 2.6
partly to excercise udev, but mostly in the hope that all the input layer
work and PS/2 changes would bring the mouse to life. I should probably add
that there are two PCs on the KVM - one running 2.6.3 and one running
2.4.24. Both run the mouse and keyboard flawlessly.

To the point. I grabbed 2.6.3-pa0 from Gentoo hppa-dev-kernel, configured
and compiled it. The keyboard and mouse are both dead. I downloaded
2.6.4-rc1-pa2 from cvs.parisc-linux.org but the result is exactly the same.
Some info below. Clues anybody?

Why is 8/12 (0x00089) reported as unknown in the device table and in
proc/interrupts? Its the Zalon HVD SCSI.

What about the SDC failed transactions. Is that an artifact of having HIL
compiled in but unused?

regards,
-Andy

weasel drivers # uname -a
Linux weasel 2.6.4-rc1-pa2 #2 Sun Mar 7 17:49:32 CET 2004 parisc PA7300LC
(PCX-L2) 9000/778/B132L GNU/Linux

weasel drivers # dmesg
Linux version 2.6.4-rc1-pa2 (root@weasel) (gcc version 3.3.2) #2 Sun Mar 7
17:49:32 CET 2004
FP[0] enabled: Rev 1 Model 15
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 00005010 00000481 00000000 02020202 77f85570 100000f0 00000004
000000ba 000000ba
vers  00000008
CPUID vers 15 rev 8 (0x000001e8)
capabilities 0x2
model 9000/778/B132L
Total Memory: 384 Mb
On node 0 totalpages: 98304
  DMA zone: 98304 pages, LIFO batch:16
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
LED display at f0190001 registered
Built 1 zonelists
Kernel command line: root=/dev/sda2 HOME=/ console=tty0 sti=8/8
sti_font=VGA8x16 TERM=linux palo_kernel=2/boot/vmlinux
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Memory: 385388k available
Calibrating delay loop... 87.85 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. Merlin+ 132 Dino PS/2 Port at 0xfff81000 [1] { 10, 0x0, 0x022, 0x00096
} 2. Merlin+ 132 Dino RS-232 at 0xfff83000 [3] { 10, 0x0, 0x022, 0x0008c }
3. Phantom PseudoBC GSC+ Port at 0xffc00000 [8] { 7, 0x0, 0x504, 0x00000 }
4. Dino PCI Bridge at 0xfff80000 [8/0] { 13, 0x1, 0x680, 0x0000a } 5.
Coral SGC Graphics at 0xf4000000 [8/8] { 10, 0x0, 0x004, 0x00077 } 6.
unknown device at 0xfff8c000 [8/12] { 4, 0x0, 0x03c, 0x00089 }
7. Merlin 132 Core BA at 0xffd00000 [8/16] { 11, 0x0, 0x03c, 0x00081 }, 
additional addresses: 0xffd0c000 0xffc00000
8. Merlin 132 Core Centronics at 0xffd02000 [8/16/0] { 10, 0x0, 0x03c,
0x00074 },  additional addresses: 0xffd01000 0xffd03000
9. Merlin 132 Core Audio at 0xffd04000 [8/16/1] { 10, 0x4, 0x03c, 0x0007b
} 10. Merlin 132 Core RS-232 at 0xffd05000 [8/16/4] { 10, 0x0, 0x03c,
0x0008c } 11. Merlin 132 Core SCSI at 0xffd06000 [8/16/5] { 10, 0x0,
0x03c, 0x00082 } 12. Merlin 132 Core LAN (802.3) at 0xffd07000 [8/16/6] {
10, 0x0, 0x03c, 0x0008a }
13. Merlin 132 Core PS/2 Port at 0xffd08000 [8/16/7] { 10, 0x0, 0x03c,
0x00084 }
14. Merlin 132 Core PS/2 Port at 0xffd08100 [8/16/8] { 10, 0x0, 0x03c,
0x00084 }
15. Merlin 132 Wax BA at 0xffe00000 [8/20] { 11, 0x0, 0x040, 0x0008e } 16.
Merlin 132 Wax HIL at 0xffe01000 [8/20/1] { 10, 0x0, 0x040, 0x00073 } 17.
Merlin 132 Wax RS-232 at 0xffe02000 [8/20/2] { 10, 0x0, 0x040, 0x0008c }
18. Merlin 132 Wax EISA BA at 0xfc000000 [8/20/5] { 11, 0x0, 0x040,
0x00090 },  additional addresses: 0xf0184000
19. Gecko GSC Core Graphics at 0xf8000000 [8/24] { 10, 0x0, 0x016, 0x00085
},  additional addresses: 0xf0011000
20. Merlin L2 132 (9000/778/B132L) at 0xfffbe000 [62] { 0, 0x0, 0x501,
0x00004 }
21. Memory at 0xfffbf000 [63] { 1, 0x0, 0x060, 0x00009 }
CPU(s): 1 x PA7300LC (PCX-L2) at 132.000000 MHz
Lasi version 0 at 0xffd00000 found.
Wax at 0xffe00000 found.
Wax EISA Adapter found at 0xfc000000
EISA EEPROM at 0xf0184000
Enumerating EISA bus
EISA: Probing bus 0 at parisc8:20:5
EISA: Mainboard HWPC000 detected.
EISA: Detected 0 cards.
Dino parisc8:0 version 2.1 found at 0xfff80000
The GSCtoPCI (Dino hrev 1) bus converter found may exhibit
data corruption.  See Service Note Numbers: A4190A-01, A4191A-01.
Systems shipped after Aug 20, 1997 will not exhibit this problem.
Models affected: C180, C160, C160L, B160L, and B132L workstations.

Dino parisc8:0: No PCI devices enabled.
SCSI subsystem initialized
STI GSC/PCI core graphics driver Version 0.9a
    id 2bcb015a-9a02587, conforms to spec rev. 8.04
    graphics card name: HPA4071B_LZ
    id 2d08c0a7-9a02587, conforms to spec rev. 8.07
    graphics card name: INTERNAL_EG_1280
fb0: stifb 1280x1024-8 frame buffer device, HPA4071B_LZ, id: 2bcb015a,
mmio: 0xf4100000
fb1: stifb 1280x1024-8 frame buffer device, INTERNAL_EG_1280, id:
2d08c0a7, mmio: 0xf8100000
ikconfig 0.7 with /proc/config*
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
Soft power switch enabled, polling @ 0xf0140000.
Console: switching to colour frame buffer device 160x64
lp: driver loaded but no devices found
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports, IRQ sharing enabled
ttyS0 at MMIO 0xffd05800 (irq = 90) is a 16550A
Serial: device 0xfff83000 not configured.
Enable support for Wax, Lasi, Asp or Dino.
ttyS1 at MMIO 0xffe02800 (irq = 121) is a 16550A
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xffd02800, irq 88 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Found i82596 at 0xffd07000, IRQ 87
eth%d: 82596 at 0xffd07000, 00 60 B0 07 1C 2C IRQ 87.
82596.c $Revision: 1.29 $
airo:  Probing for PCI adapters
airo:  Finished probing for PCI adapters
zalon_probe: Zalon vers field is 0x1, IRQ 35
ncr53c720-0: rev 0xf irq 35
ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
scsi0 : ncr53c8xx-3.4.3e
Using anticipatory io scheduler
  Vendor: SEAGATE   Model: ST39173WD         Rev: 5764
  Type:   Direct-Access                      ANSI SCSI revision: 02
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi1: 53c710 rev 2
scsi1 : LASI SCSI 53c700
scsi1: (2:0) Synchronous at offset 8, period 236ns
  Vendor: TOSHIBA   Model: CD-ROM XM-5401TA  Rev: 1036
  Type:   CD-ROM                             ANSI SCSI revision: 02
st: Version 20040213, fixed bufsize 32768, s/g segs 256
ncr53c720-0-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 8)
SCSI device sda: 17783240 512-byte hdwr sectors (9105 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 2, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
Attached scsi generic sg1 at scsi1, channel 0, id 2, lun 0,  type 5
Console: switching to colour frame buffer device 160x64
mice: PS/2 mouse device common for all mice
serio: GSC PS2 keyboard port at 0xffd08000 irq 69 @ parisc8:16:7
serio: GSC PS2 mouse port at 0xffd08100 irq 69 @ parisc8:16:8
HP SDC: HP SDC reports successful PUP.
HP SDC: HP SDC at 0xffe01000, IRQ 126 (NMI IRQ 125)
HP SDC: New style SDC
HP SDC: Revision: 1820-4784
HP SDC: TI SN76494 beeper present
HP SDC: OKI MSM-58321 BBRTC present
HP SDC: Spunking the self test register to force PUP on next firmware
reset. HP SDC MLC: Registering the System Domain Controller's HIL MLC.
oprofile: using timer interrupt.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 332k freed
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: Transaction add failed: transaction already queued?
HP SDC: read timeout (1537786us)!
Adding 525304k swap on /dev/sda3.  Priority:-1 extents:1
EXT3 FS on sda2, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth0: link ok.
weasel drivers #
weasel drivers # cat /proc/interrupts
           CPU00
  2:          0            EISA  cascade
 32:    5268327      PARISC-CPU  timer
 33:      11276      PARISC-CPU  lasi
 34:          0      PARISC-CPU  Dino parisc8:0
 35:      49026      PARISC-CPU  parisc8:12
 39:        433      PARISC-CPU  wax
 69:         50            Lasi  GSC PS2 keyboard, GSC PS2 mouse
 86:         15            Lasi  parisc8:16:5
 87:      11201            Lasi  i82596
 88:          0            Lasi  parport0
 90:         10            Lasi  serial
117:          0             Wax  EISA
125:          0             Wax  HP SDC NMI
126:        433             Wax  HP SDC

weasel drivers # zcat /proc/config.gz

#
# Automatically generated make config: don't edit
#
CONFIG_PARISC=y
CONFIG_MMU=y
CONFIG_STACK_GROWSUP=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODULE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_PA7000 is not set
CONFIG_PA7100LC=y
# CONFIG_PA7200 is not set
# CONFIG_PA8X00 is not set
CONFIG_PA11=y
# CONFIG_64BIT is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_HPUX is not set

#
# Bus options (PCI, PCMCIA, EISA, GSC, ISA)
#
CONFIG_GSC=y
CONFIG_HPPB=y
CONFIG_IOMMU_CCIO=y
CONFIG_GSC_LASI=y
CONFIG_GSC_WAX=y
CONFIG_EISA=y
CONFIG_EISA_NAMES=y
# CONFIG_ISA is not set
CONFIG_PCI=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_GSC_DINO=y
CONFIG_PCI_LBA=y
CONFIG_IOSAPIC=y
CONFIG_IOMMU_SBA=y
CONFIG_SUPERIO=y
CONFIG_CHASSIS_LCD_LED=y
CONFIG_PDC_CHASSIS=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_GSC=y
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_DCSSBLK is not set

#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
CONFIG_SCSI_LASI700=y
CONFIG_53C700_MEM_MAPPED=y
CONFIG_53C700_LE_ON_BE=y
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
CONFIG_SCSI_ZALON=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
CONFIG_LASI_82596=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_SMC is not set

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
CONFIG_DL2K=y
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set

#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_AIRO=y
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
CONFIG_NET_WIRELESS=y
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_GSCPS2=y
CONFIG_HP_SDC=y
CONFIG_HIL_MLC=y
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ATKBD is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_KEYBOARD_HIL=y
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_PS2 is not set
# CONFIG_MOUSE_SERIAL is not set
CONFIG_MOUSE_HIL=y
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_INPUT_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set
CONFIG_HP_SDC_RTC=y

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MUX is not set
# CONFIG_PDC_CONSOLE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
CONFIG_GEN_RTC=y
# CONFIG_GEN_RTC_X is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_RAW_DRIVER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_STI=y
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
# CONFIG_MDA_CONSOLE is not set
CONFIG_STI_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=160
CONFIG_DUMMY_CONSOLE_ROWS=64
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_LOGO_PARISC_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_SOUND_HARMONY=m

#
# USB support
#
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_FAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set

# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SLAB is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_FRAME_POINTER=y
# CONFIG_DEBUG_INFO is not set

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC32=y

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Grant Grundler]

On Mon, Mar 08, 2004 at 12:28:37PM +0100, Andy Walker wrote:
> Why is 8/12 (0x00089) reported as unknown in the device table and in
> proc/interrupts? Its the Zalon HVD SCSI.
...
> 6. unknown device at 0xfff8c000 [8/12] { 4, 0x0, 0x03c, 0x00089 }

It means we don't have an entry for Zalon in arch/parisc/kernel/hardware.c
Can you submit a patch for that?

(I confess: I'm being very lazy tonight and don't want to figure
what needs to go into the hardware.c array)

> zalon_probe: Zalon vers field is 0x1, IRQ 35
> ncr53c720-0: rev 0xf irq 35
> ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
> scsi0 : ncr53c8xx-3.4.3e
> Using anticipatory io scheduler
>   Vendor: SEAGATE   Model: ST39173WD         Rev: 5764
>   Type:   Direct-Access                      ANSI SCSI revision: 02

Zalon is obviously recognized and seems to be working.

...
> weasel drivers # cat /proc/interrupts
>            CPU00
>   2:          0            EISA  cascade
>  32:    5268327      PARISC-CPU  timer
>  33:      11276      PARISC-CPU  lasi
>  34:          0      PARISC-CPU  Dino parisc8:0
>  35:      49026      PARISC-CPU  parisc8:12

hrm...good question. Oic.  RTFC. :^)
In drivers/scsi/zalon.c:
        if (request_irq(irq, ncr53c8xx_intr, SA_SHIRQ, dev->dev.bus_id, host)) {
                printk(KERN_ERR "%s: irq problem with %d, detaching\n ",
                        dev->dev.bus_id, irq);
                goto fail;
        }

sorry, can't help with the keyboard/mouse problems...

hth,
grant

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Andy Walker]

> On Mon, Mar 08, 2004 at 12:28:37PM +0100, Andy Walker wrote:
>> Why is 8/12 (0x00089) reported as unknown in the device table and in
proc/interrupts? Its the Zalon HVD SCSI.
> ...
>> 6. unknown device at 0xfff8c000 [8/12] { 4, 0x0, 0x03c, 0x00089 }
>
> It means we don't have an entry for Zalon in
arch/parisc/kernel/hardware.c
> Can you submit a patch for that?
> (I confess: I'm being very lazy tonight and don't want to figure what
needs to go into the hardware.c array)

Try this then. I just followed the pattern for B160L, C110 et. al.

--- linux-2.6.4-rc1-pa3.bak/arch/parisc/kernel/hardware.c	Tue Mar  9
10:05:25 2004
+++ linux-2.6.4-rc1-pa3/arch/parisc/kernel/hardware.c	Tue Mar  9 10:27:23
2004
@@ -334,6 +334,7 @@
 	{HPHW_A_DMA, 0x027, 0x00089, 0x80, "Piranha 100 FW-SCSI"},
 	{HPHW_A_DMA, 0x032, 0x00089, 0x80, "Raven T' Core FW-SCSI"},
 	{HPHW_A_DMA, 0x03b, 0x00089, 0x80, "Raven U/L2 Core FW-SCSI"},
+	{HPHW_A_DMA, 0x03c, 0x00089, 0x80, "Merlin 132 Core FW-SCSI"},
 	{HPHW_A_DMA, 0x03d, 0x00089, 0x80, "Merlin 160 Core FW-SCSI"},
 	{HPHW_A_DMA, 0x044, 0x00089, 0x80, "Mohawk Core FW-SCSI"},
 	{HPHW_A_DMA, 0x051, 0x00089, 0x80, "Firehawk FW-SCSI"},

There are other issues with the hardware.c array though. I guess they're
not critical, and I've no idea how to resolve them as they seem to
indicate duplication on HP's part. I guess this is old news:

1. Merlin+ 132 Dino PS/2 Port at 0xfff81000 [1] { 10, 0x0, 0x022, 0x00096 }
2. Merlin+ 132 Dino RS-232 at 0xfff83000 [3] { 10, 0x0, 0x022, 0x0008c }
5. Coral SGC Graphics at 0xf4000000 [8/8] { 10, 0x0, 0x004, 0x00077 }
19. Gecko GSC Core Graphics at 0xf8000000 [8/24] { 10, 0x0, 0x016, 0x00085},
   additional addresses: 0xf0011000

- Merlin+ 132 is B132L+, as far as I know. But this machine is
  a plain Merlin/B132L. The Dino ports are marked Merlin+. Weird.
  Could this imply mean Dino was upgraded to a non-broken rev. using
  Merlin+ parts? There are separate items in hardware.c for 'Merlin
  132 Dino PS/2 Port', and 'Merlin 132 Dino RS-232' but these don't
  match.

- what's listed as 'Coral SGC Graphics' is actually an A4071B_LZ GSC
  card, aka. HCRX-24 with hardware acceleration board. No separate items
  in hardware.c for any of A407[01][AB] or H?CRX-(8|24).

- what's listed as 'Gecko GSC Core Graphics' on my machine is actually
  the 'Merlin 132 Core Graphics' i.e. the builtin Vis-EG. There is a
  separate item in hardware.c for 'Merlin 132 Core Graphics' but it
  doesn't match.

BTW: Firmware rev. is 6.1 (i.e. latest available)

cheers,
-Andy

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Matthew Wilcox]

On Tue, Mar 09, 2004 at 12:27:31PM +0100, Andy Walker wrote:
> Try this then. I just followed the pattern for B160L, C110 et. al.

Thanks, committed.

> There are other issues with the hardware.c array though. I guess they're
> not critical, and I've no idea how to resolve them as they seem to
> indicate duplication on HP's part. I guess this is old news:
> 
> 1. Merlin+ 132 Dino PS/2 Port at 0xfff81000 [1] { 10, 0x0, 0x022, 0x00096 }
> 2. Merlin+ 132 Dino RS-232 at 0xfff83000 [3] { 10, 0x0, 0x022, 0x0008c }
> 5. Coral SGC Graphics at 0xf4000000 [8/8] { 10, 0x0, 0x004, 0x00077 }
> 19. Gecko GSC Core Graphics at 0xf8000000 [8/24] { 10, 0x0, 0x016, 0x00085},
>    additional addresses: 0xf0011000
> 
> - Merlin+ 132 is B132L+, as far as I know. But this machine is
>   a plain Merlin/B132L. The Dino ports are marked Merlin+. Weird.
>   Could this imply mean Dino was upgraded to a non-broken rev. using
>   Merlin+ parts? There are separate items in hardware.c for 'Merlin
>   132 Dino PS/2 Port', and 'Merlin 132 Dino RS-232' but these don't
>   match.

Dunno about that one.  It doesn't seem terribly important really ;-)

> - what's listed as 'Coral SGC Graphics' is actually an A4071B_LZ GSC
>   card, aka. HCRX-24 with hardware acceleration board. No separate items
>   in hardware.c for any of A407[01][AB] or H?CRX-(8|24).
> 
> - what's listed as 'Gecko GSC Core Graphics' on my machine is actually
>   the 'Merlin 132 Core Graphics' i.e. the builtin Vis-EG. There is a
>   separate item in hardware.c for 'Merlin 132 Core Graphics' but it
>   doesn't match.

Yeah, the Graphics lab were pretty slap-dash about using the correct
versions on things.  This is something we've been living with since
the earliest days of the port.  Someone who was motivated might want to
collect information from a bunch of machines and fix it up.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Matthew Wilcox]

On Mon, Mar 08, 2004 at 10:36:15PM -0700, Grant Grundler wrote:
> On Mon, Mar 08, 2004 at 12:28:37PM +0100, Andy Walker wrote:
> > Why is 8/12 (0x00089) reported as unknown in the device table and in
> > proc/interrupts? Its the Zalon HVD SCSI.
> ...
> > 6. unknown device at 0xfff8c000 [8/12] { 4, 0x0, 0x03c, 0x00089 }
> 
> It means we don't have an entry for Zalon in arch/parisc/kernel/hardware.c
> Can you submit a patch for that?
> 
> (I confess: I'm being very lazy tonight and don't want to figure
> what needs to go into the hardware.c array)

*grumble*.  I changed the output format so you could simply copy and paste
it into hardware.c!  That's exceptionally lazy of you :-P

(you can tell boot logs that predate this change because they don't use 
{ } around the numbers).

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Grant Grundler]

On Tue, Mar 09, 2004 at 09:04:00PM +0000, Matthew Wilcox wrote:
> > (I confess: I'm being very lazy tonight and don't want to figure
> > what needs to go into the hardware.c array)
> 
> *grumble*.  I changed the output format so you could simply copy and paste
> it into hardware.c!  That's exceptionally lazy of you :-P

/me points at garfield

Isn't nice to know there's always someone better at something
than one's self? :^P

> (you can tell boot logs that predate this change because they don't use 
> { } around the numbers).

Yup - I remember you making the change and knew it should be fairly easy...
thus I was confident someone else could do it.
(was that a good excuse or what? Just made that one up :^)

thanks,
grant

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Montag, 8. März 2004 12:28, Andy Walker wrote:
> I've a B132L running Gentoo. With 2.4 I had the PS/2 keyboard working fine
> throught a Raritan Compuswitch KVM, but the mouse (wireless Intellimouse
> clone - 2 buttons pluss roller/middle) was dead. Decided to try out 2.6
> partly to excercise udev, but mostly in the hope that all the input layer
> work and PS/2 changes would bring the mouse to life. I should probably add
> that there are two PCs on the KVM - one running 2.6.3 and one running
> 2.4.24. Both run the mouse and keyboard flawlessly.
> 
> To the point. I grabbed 2.6.3-pa0 from Gentoo hppa-dev-kernel, configured
> and compiled it. The keyboard and mouse are both dead. I downloaded
> 2.6.4-rc1-pa2 from cvs.parisc-linux.org but the result is exactly the same.
> Some info below. Clues anybody?
....
> # Input Device Drivers
> #
> CONFIG_INPUT_KEYBOARD=y
> # CONFIG_KEYBOARD_ATKBD is not set

Please enable this one (CONFIG_KEYBOARD_ATKBD), and....

> # CONFIG_KEYBOARD_SUNKBD is not set
> # CONFIG_KEYBOARD_XTKBD is not set
> # CONFIG_KEYBOARD_NEWTON is not set
> CONFIG_KEYBOARD_HIL=y
> CONFIG_INPUT_MOUSE=y
> # CONFIG_MOUSE_PS2 is not set

this one too.

In the latest 2.6 kernel series, we switched from a parisc-only
PS/2 mouse/keyboard driver to the standard linux kernel PS/2
mouse keyboard drivers.

Helge

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Dienstag, 9. März 2004 11:33, Andy Walker wrote:
> I'm just about to give this a try. The reason these weren't enabled is
> that menuconfig was a bit non-intuitive (to me at least). Maybe I was
> just being paranoid, but when I selected ATKBD or MOUSE_PS2 then the GSC
> PS/2 item got closed up and I didn't know whether it was on or off. That
> scared me and I assumed that selecting GSC PS/2 support would enable
> everything else I needed. Compiling now, but I won't be able to test
> until I get home from work and actually get my hands on the keyboard/mouse.

Hi Andy,

I agree, that this behaviour seems somehow little strange. Thibaut Varene
complained too.
But on the other side without this auto-enablement of the GSC PS/2 controller
users maybe enable PS/2 mouse and/or PS/2 keyboard and miss enabling the
GSC PS/2 controller too - with the result, that neither keyboard or mouse would
work when the kernel is booted....

Personally I prefer the automatic enablement. Even on iA32 this is the default now.

Best regards,
Helge

Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]

[Andy Walker]

> On Dienstag, 9. März 2004 11:33, Andy Walker wrote:
> Hi Andy,
>
> I agree, that this behaviour seems somehow little strange. Thibaut Varene
> complained too.
> But on the other side without this auto-enablement of the GSC PS/2
> controller
> users maybe enable PS/2 mouse and/or PS/2 keyboard and miss enabling the
> GSC PS/2 controller too - with the result, that neither keyboard or mouse
> would
> work when the kernel is booted....
>
> Personally I prefer the automatic enablement. Even on iA32 this is the
> default now.
>
> Best regards,
> Helge
>

Helge,

Glad to report that the keyboard is now working. No mouse yet, but I
need to try it without the KVM in the way as that's likely to be the
problem. Perhaps I need .proto=bare or .proto=imps2.
At the moment I get:

serio: GSC PS2 keyboard port at 0xffd08000 irq 69 @ parisc8:16:7
input: AT Raw Set 2 keyboard on parisc8:16:7
serio: GSC PS2 mouse port at 0xffd08100 irq 69 @ parisc8:16:8
gscps2.c: timeout - could not write byte 0xed
gscps2.c: sending byte 0xed failed.

cat /dev/misc/psaux and wobbling the mouse gives nothing.

cheers,
-Andy

[parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Helge Deller wrote:
> > I've a B132L running Gentoo. With 2.4 I had the PS/2 keyboard working fine
> > throught a Raritan Compuswitch KVM, but the mouse (wireless Intellimouse
> > clone - 2 buttons pluss roller/middle) was dead. Decided to try out 2.6
> > partly to excercise udev, but mostly in the hope that all the input layer
> > work and PS/2 changes would bring the mouse to life. I should probably add
> > that there are two PCs on the KVM - one running 2.6.3 and one running
> > 2.4.24. Both run the mouse and keyboard flawlessly.
> > 
> > To the point. I grabbed 2.6.3-pa0 from Gentoo hppa-dev-kernel, configured
> > and compiled it. The keyboard and mouse are both dead. I downloaded
> > 2.6.4-rc1-pa2 from cvs.parisc-linux.org but the result is exactly the same.
> > Some info below. Clues anybody?
> .....
> > # Input Device Drivers
> > #
> > CONFIG_INPUT_KEYBOARD=y
> > # CONFIG_KEYBOARD_ATKBD is not set
> 
> Please enable this one (CONFIG_KEYBOARD_ATKBD), and....
> 
> > # CONFIG_KEYBOARD_SUNKBD is not set
> > # CONFIG_KEYBOARD_XTKBD is not set
> > # CONFIG_KEYBOARD_NEWTON is not set
> > CONFIG_KEYBOARD_HIL=y
> > CONFIG_INPUT_MOUSE=y
> > # CONFIG_MOUSE_PS2 is not set
> 
> this one too.
> 

For what it's worth, these settings don't activate my keyboard,
but... tadam...  the mouse is recognised, finally.  However, if
I have to choose to use either keyboard or mouse, I'd choose the
keyboard.

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_KEYBOARD_HIL=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=y
CONFIG_MOUSE_HIL=y
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_HP_SDC_RTC is not set

Any idea how to get the keyboard detected again?
(This is a 725/100)

If it helps to provide more information, please let me know and I'll
dig them out.

> In the latest 2.6 kernel series, we switched from a parisc-only
> PS/2 mouse/keyboard driver to the standard linux kernel PS/2
> mouse keyboard drivers.

Makes sense.  However, would it be useful to add this to the config
help texts?  Same for the dependency of a HIL mouse to the MOUSE_PS2,
if HIL always takes PS/2 mice.  I know this is not the case in general,
since my 425 uses HIL but doesn't use PS/2, but then again, it's m68k
and not parisc.  However, it may be the case on PA-RISC, I don't know.
In that case it may make sense to rearrange the ordering and move
MOUSE_HIL up so it can pre-select MOUSE_PS2.

Anyway, here's a short improvement for the MOUSE_PS2 help text:

--- Kconfig.orig	Sun Mar 14 08:27:51 2004
+++ Kconfig	Sun Mar 14 08:31:18 2004
@@ -22,7 +22,8 @@
 	  Say Y here if you have a PS/2 mouse connected to your system. This
 	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
 	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
-	  compatible.
+	  compatible. This also includes a PS/2 mouse connected to your HIL
+	  hub on PA-RISC.
 
 	  Synaptics TouchPad users might be interested in a specialized
 	  XFree86 driver at:

Regards,

	Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Please always Cc to me when replying to me on the lists.

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[M. Grabert]

On Sun, 14 Mar 2004, Martin Schulze wrote:

> For what it's worth, these settings don't activate my keyboard,
> but... tadam...  the mouse is recognised, finally.  However, if
> I have to choose to use either keyboard or mouse, I'd choose the
> keyboard.
>
> CONFIG_INPUT_KEYBOARD=y
> CONFIG_KEYBOARD_ATKBD=y
> # CONFIG_KEYBOARD_SUNKBD is not set
> # CONFIG_KEYBOARD_XTKBD is not set
> # CONFIG_KEYBOARD_NEWTON is not set
> CONFIG_KEYBOARD_HIL=y

Why do you include HIL keyboard support?

> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y
> CONFIG_MOUSE_SERIAL=y

do you need serial mouse support?

> CONFIG_MOUSE_HIL=y

and why do you include HIL mouse support?

[...]

> Any idea how to get the keyboard detected again?
> (This is a 725/100)

I don't know the 725, but from what I understand it uses (GSC) PS/2, so you
attach keyboard and mouse directly, without any converters. Is that correct?

If this is the cause, get rid of all HIL drivers and use PS/2 exclusively.
I think using a combination of HIL and PS/2 drivers might cause some
sort of driver confusion in your case.

> If it helps to provide more information, please let me know and I'll
> dig them out.
>
>  	  Say Y here if you have a PS/2 mouse connected to your system. This
>  	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
>  	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
> -	  compatible.
> +	  compatible. This also includes a PS/2 mouse connected to your HIL
> +	  hub on PA-RISC.

I'm confused here!

AFAIK if you are using HIL, you ONLY have to use the HIL keyboard/mouse
drivers, PS/2 is a different thing and is not involved at all.
(I hope I don't say anything stupid here).

So far I thought that you cannot attach a PS/2 mouse to a HIL adapter,
you can only attach HIL devices ... (at least this is the case for my 730)


Greetings,
 Max

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

M. Grabert wrote:
> > For what it's worth, these settings don't activate my keyboard,
> > but... tadam...  the mouse is recognised, finally.  However, if
> > I have to choose to use either keyboard or mouse, I'd choose the
> > keyboard.
> >
> > CONFIG_INPUT_KEYBOARD=y
> > CONFIG_KEYBOARD_ATKBD=y
> > # CONFIG_KEYBOARD_SUNKBD is not set
> > # CONFIG_KEYBOARD_XTKBD is not set
> > # CONFIG_KEYBOARD_NEWTON is not set
> > CONFIG_KEYBOARD_HIL=y
> 
> Why do you include HIL keyboard support?

Because the keyboad is connected to a HIL hub and it's also a
reminiscent of the time before I learned that the keyboard and mouse
are not handled entirely separate anymore.  I still have to strip some
config options from the configuration.

> > CONFIG_INPUT_MOUSE=y
> > CONFIG_MOUSE_PS2=y
> > CONFIG_MOUSE_SERIAL=y
> 
> do you need serial mouse support?

Well, at one time I tried to fix the mouse problem by connecting a
serial mouse to ttyS0/ttyS1 but it didn't work either, even though a
getty on that port worked and I could log in, hence the port works at
least and is supported in the kernel.

> > CONFIG_MOUSE_HIL=y
> 
> and why do you include HIL mouse support?

Same as above, because the mouse is connected to a HIL hub and it's a
reminiscent from the time before I learned that the keyboard and mouse
are not handled entirely separate anymore for parisc.

> > Any idea how to get the keyboard detected again?
> > (This is a 725/100)
> 
> I don't know the 725, but from what I understand it uses (GSC) PS/2, so you
> attach keyboard and mouse directly, without any converters. Is that correct?

No it isn't.  That's the case for 712, not this one.  There's a HIL
hub where I can connect one keyboard, one mouse and another HIL hub.
The case doesn't have any PS/2 socket.

> If this is the cause, get rid of all HIL drivers and use PS/2 exclusively.
> I think using a combination of HIL and PS/2 drivers might cause some
> sort of driver confusion in your case.

Might well be.  I'm still working on stripping the stuff and testing
various combinations.

> > If it helps to provide more information, please let me know and I'll
> > dig them out.
> >
> >  	  Say Y here if you have a PS/2 mouse connected to your system. This
> >  	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
> >  	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
> > -	  compatible.
> > +	  compatible. This also includes a PS/2 mouse connected to your HIL
> > +	  hub on PA-RISC.
> 
> I'm confused here!
>
> AFAIK if you are using HIL, you ONLY have to use the HIL keyboard/mouse
> drivers, PS/2 is a different thing and is not involved at all.
> (I hope I don't say anything stupid here).

Aha.  I thought it was different.  Maybe I misread Helges mail.

> So far I thought that you cannot attach a PS/2 mouse to a HIL adapter,
> you can only attach HIL devices ... (at least this is the case for my 730)

Well, at least physically this is possible.  I haven't tried to use
that combination, though, since I have the original mouse and
keyboard as well.  However, I could give it a try once I find a
working config combination.

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Please always Cc to me when replying to me on the lists.

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Sunday 14 March 2004 19:12, Martin Schulze wrote:
> > > For what it's worth, these settings don't activate my keyboard,
> > > but... tadam...  the mouse is recognised, finally.  

Cool.

> > > However, if 
> > > I have to choose to use either keyboard or mouse, I'd choose the
> > > keyboard.

Of course.

> > > CONFIG_INPUT_KEYBOARD=y
> > > CONFIG_KEYBOARD_ATKBD=y
> > > # CONFIG_KEYBOARD_SUNKBD is not set
> > > # CONFIG_KEYBOARD_XTKBD is not set
> > > # CONFIG_KEYBOARD_NEWTON is not set
> > > CONFIG_KEYBOARD_HIL=y
> > 
> > Why do you include HIL keyboard support?
> 
> Because the keyboad is connected to a HIL hub and it's also a
> reminiscent of the time before I learned that the keyboard and mouse
> are not handled entirely separate anymore.  I still have to strip some
> config options from the configuration.

I think the main question here is which type of keyboard you have.
Either it's a HIL keyboard (with the special HIL connector), or it's a 
PS/2 keyboard.
My 715/64 for example has a HIL HUB too, and here the mouse and
keyboard are 100% HIL only devices.
AFAIK, there are other HIL Hubs too, which provides original PS/2
ports and HIL ports. So, which kind of connector does your keyboard has ?

> > > CONFIG_INPUT_MOUSE=y
> > > CONFIG_MOUSE_PS2=y
> > > CONFIG_MOUSE_SERIAL=y
> > 
> > do you need serial mouse support?
> 
> Well, at one time I tried to fix the mouse problem by connecting a
> serial mouse to ttyS0/ttyS1 but it didn't work either, even though a
> getty on that port worked and I could log in, hence the port works at
> least and is supported in the kernel.

Serial mice should work. I didn't tested it for some time now, but if
it's broken I would like to know.

> > > CONFIG_MOUSE_HIL=y
> > 
> > and why do you include HIL mouse support?
> 
> Same as above, because the mouse is connected to a HIL hub and it's a
> reminiscent from the time before I learned that the keyboard and mouse
> are not handled entirely separate anymore for parisc.
> 
> > > Any idea how to get the keyboard detected again?
> > > (This is a 725/100)
> > 
> > I don't know the 725, but from what I understand it uses (GSC) PS/2, so you
> > attach keyboard and mouse directly, without any converters. Is that correct?
> 
> No it isn't.  That's the case for 712, not this one.  There's a HIL
> hub where I can connect one keyboard, one mouse and another HIL hub.
> The case doesn't have any PS/2 socket.

Ok. So your keyboard seem to be a HIL keyboard ?
But it's strange, that your PS/2 mouse works then... I'm confused.

> > If this is the cause, get rid of all HIL drivers and use PS/2 exclusively.
> > I think using a combination of HIL and PS/2 drivers might cause some
> > sort of driver confusion in your case.
> 
> Might well be.  I'm still working on stripping the stuff and testing
> various combinations.

Ok.
> > > If it helps to provide more information, please let me know and I'll
> > > dig them out.
> > >
> > >  	  Say Y here if you have a PS/2 mouse connected to your system. This
> > >  	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
> > >  	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
> > > -	  compatible.
> > > +	  compatible. This also includes a PS/2 mouse connected to your HIL
> > > +	  hub on PA-RISC.
> > 
> > I'm confused here!
> >
> > AFAIK if you are using HIL, you ONLY have to use the HIL keyboard/mouse
> > drivers, PS/2 is a different thing and is not involved at all.
> > (I hope I don't say anything stupid here).
> 
> Aha.  I thought it was different.  Maybe I misread Helges mail.

I'm not sure right now about the status of the HIL keyboard/mouse driver, e.g.
if it works or not in the 2.6 kernel series...
 
> > So far I thought that you cannot attach a PS/2 mouse to a HIL adapter,
> > you can only attach HIL devices ... (at least this is the case for my 730)
> 
> Well, at least physically this is possible.  I haven't tried to use
> that combination, though, since I have the original mouse and
> keyboard as well.  However, I could give it a try once I find a
> working config combination.

Yes, please.

Regards,
Helge

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Helge Deller wrote:
> On Sunday 14 March 2004 19:12, Martin Schulze wrote:
> > > > For what it's worth, these settings don't activate my keyboard,
> > > > but... tadam...  the mouse is recognised, finally.  
> 
> Cool.

Well, not anymore, but more on that later.

> > > > CONFIG_INPUT_KEYBOARD=y
> > > > CONFIG_KEYBOARD_ATKBD=y
> > > > # CONFIG_KEYBOARD_SUNKBD is not set
> > > > # CONFIG_KEYBOARD_XTKBD is not set
> > > > # CONFIG_KEYBOARD_NEWTON is not set
> > > > CONFIG_KEYBOARD_HIL=y
> > > 
> > > Why do you include HIL keyboard support?
> > 
> > Because the keyboad is connected to a HIL hub and it's also a
> > reminiscent of the time before I learned that the keyboard and mouse
> > are not handled entirely separate anymore.  I still have to strip some
> > config options from the configuration.
> 
> I think the main question here is which type of keyboard you have.
> Either it's a HIL keyboard (with the special HIL connector), or it's a 
> PS/2 keyboard.

It's HP A2840-60201 (according to the plate on the bottom).  It's
connected to a HIL hub with a PS/2 like connector.  The HIL hub is
connected to the machine with an RJ45 (like) connector.

The keyboard onlyworks with these three set:

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_HIL=y

> My 715/64 for example has a HIL HUB too, and here the mouse and
> keyboard are 100% HIL only devices.

I can connect a regular PC PS/2 keyboard to the HIL hub and it'll
work.  I have an obscure PS/2 keyboard as well, which produces
'failure initializing keyboard' or something alike.  Now that I look
at the keyboard more closely, it's really a strange one, dunno where I
got *that* one from.  Anyway, regular PS/2 works fine.  HP keyboard
works fine as well.

> AFAIK, there are other HIL Hubs too, which provides original PS/2
> ports and HIL ports. So, which kind of connector does your keyboard has ?

Looks like I need to take picture.  Ah, found one:
<http://www.schrotthal.de/hp/hp_hil_ps2_hub.jpg> That's the HIL hub,
named HIL PS/2 hub, well.  I also have a very old HIL hub without PS/2
(like) jacks, but that's for an entirely different machine and
generation.

> Serial mice should work. I didn't tested it for some time now, but if
> it's broken I would like to know.

I'll have to retry that as well.

> Ok. So your keyboard seem to be a HIL keyboard ?

Since a regular PS/2 keyboard works as well, I guess it's a PS/2
keyboard actually.

> But it's strange, that your PS/2 mouse works then... I'm confused.

Don't be confused, it doesn't work anymore.

> I'm not sure right now about the status of the HIL keyboard/mouse driver, e.g.
> if it works or not in the 2.6 kernel series...

FWIW: I had mouse support and I had keyboard support.  Just not at the
same time unfortunately.  So in general it works at least.  The
configuration is a bit non-intuitive since you'll have to enable
HIL_KBD and AT_KBD.  However, logically it makes sense.

> > > So far I thought that you cannot attach a PS/2 mouse to a HIL adapter,
> > > you can only attach HIL devices ... (at least this is the case for my 730)
> > 
> > Well, at least physically this is possible.  I haven't tried to use
> > that combination, though, since I have the original mouse and
> > keyboard as well.  However, I could give it a try once I find a
> > working config combination.
> 
> Yes, please.

I'll connect a regular PC PS/2 mouse once I have mouse support again.
PS/2 keyboard works fine.

Regards,

	Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

Hi Martin,

On Sunday 14 March 2004 21:28, Martin Schulze wrote:
> > I think the main question here is which type of keyboard you have.
> > Either it's a HIL keyboard (with the special HIL connector), or it's a 
> > PS/2 keyboard.
> 
> It's HP A2840-60201 (according to the plate on the bottom).  It's
> connected to a HIL hub with a PS/2 like connector.  The HIL hub is
> connected to the machine with an RJ45 (like) connector.
> 
> The keyboard onlyworks with these three set:
> 
> CONFIG_INPUT_KEYBOARD=y
> CONFIG_KEYBOARD_ATKBD=y
> CONFIG_KEYBOARD_HIL=y

CONFIG_KEYBOARD_ATKBD and CONFIG_KEYBOARD_HIL
have nothing to do with each other. Reading your reply below,
it seems, that you will only need CONFIG_KEYBOARD_ATKBD.
I think, the HUB is only used to "transport" the PS/2 signals to your computer,
and uses some cables inside the HIL cable.

> > My 715/64 for example has a HIL HUB too, and here the mouse and
> > keyboard are 100% HIL only devices.
> 
> I can connect a regular PC PS/2 keyboard to the HIL hub and it'll
> work.  I have an obscure PS/2 keyboard as well, which produces
> 'failure initializing keyboard' or something alike.  Now that I look
> at the keyboard more closely, it's really a strange one, dunno where I
> got *that* one from.  Anyway, regular PS/2 works fine.  HP keyboard
> works fine as well.

Yup, then it's definitively a PS/2 keyboard.

> > AFAIK, there are other HIL Hubs too, which provides original PS/2
> > ports and HIL ports. So, which kind of connector does your keyboard has ?
> 
> Looks like I need to take picture.  Ah, found one:
> <http://www.schrotthal.de/hp/hp_hil_ps2_hub.jpg> That's the HIL hub,
> named HIL PS/2 hub, well.  I also have a very old HIL hub without PS/2
> (like) jacks, but that's for an entirely different machine and
> generation.

Yes. My HUB has only HIL connectors and is for a 715/64.
 
> > Serial mice should work. I didn't tested it for some time now, but if
> > it's broken I would like to know.
> 
> I'll have to retry that as well.

Ok.

> > But it's strange, that your PS/2 mouse works then... I'm confused.
> 
> Don't be confused, it doesn't work anymore.

I would be interested in your dmesg log.
Mine (HIL only!) looks like this:

mice: PS/2 mouse device common for all mice
serio: GSC PS2 keyboard port at 0xf0108000 irq 69 @ parisc2:0:11
gscps2.c: timeout - could not write byte 0xed
gscps2.c: sending byte 0xed failed.

-> OK, since I only have a HIL keyboard.

serio: GSC PS2 mouse port at 0xf0108100 irq 69 @ parisc2:0:12
gscps2.c: timeout - could not write byte 0xed
gscps2.c: sending byte 0xed failed.

-> OK, since I only have a HIL mouse.

HP SDC: HP SDC reports successful PUP.
HP SDC: HP SDC at 0xf0201000, IRQ 126 (NMI IRQ 125)
HP SDC: New style SDC
HP SDC: Revision: 1820-4784
HP SDC: TI SN76494 beeper present
HP SDC: OKI MSM-58321 BBRTC present
HP SDC: Spunking the self test register to force PUP on next firmware reset.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.

-> OK, the HIL stuff is detected. (BTW, test this after power-cycling the machine!)

and then nearly at the end of dmesg:
HIL KEYB: HIL keyboard found (did = 0xcf, lang = german)
input: HIL keyboard, ID: 207
HIL PTR: HIL pointer device found (did: 0x68, axis: relative)
HIL PTR: HIL pointer has 3 buttons and 1 sets of 2 axes
input: HIL pointer device (HIL mouse), ID: 104

This is now HIL keyboard and HIL mouse.
So my HIL mouse is detected, but doesn't seem to work yet.... :-( 
 
> > I'm not sure right now about the status of the HIL keyboard/mouse driver, e.g.
> > if it works or not in the 2.6 kernel series...
> 
> FWIW: I had mouse support and I had keyboard support.  Just not at the
> same time unfortunately.  So in general it works at least.  The
> configuration is a bit non-intuitive since you'll have to enable
> HIL_KBD and AT_KBD.  However, logically it makes sense.

No. You should disable HIL_KBD (but it doesn't hurt either).

> > > > So far I thought that you cannot attach a PS/2 mouse to a HIL adapter,
> > > > you can only attach HIL devices ... (at least this is the case for my 730)
> > > 
> > > Well, at least physically this is possible.  I haven't tried to use
> > > that combination, though, since I have the original mouse and
> > > keyboard as well.  However, I could give it a try once I find a
> > > working config combination.
> > 
> > Yes, please.
> 
> I'll connect a regular PC PS/2 mouse once I have mouse support again.
> PS/2 keyboard works fine.

As said above: Hard Power-cycle the machine before each test!
Furthermore you might try to increase the value of mdelay(6); in line 168
in file linux-2.6/drivers/input/serio/gscps2.c...
Maybe it's a timing issue ?

This is what you should have in your .config:
CONFIG_SERIO_GSCPS2=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y

Helge

[parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Helge Deller wrote:
> > Don't be confused, it doesn't work anymore.
> 
> I would be interested in your dmesg log.

It's at http://luonnotar.infodrom.org/~joey/dmesg.txt

> Mine (HIL only!) looks like this:
> 
> mice: PS/2 mouse device common for all mice
> serio: GSC PS2 keyboard port at 0xf0108000 irq 69 @ parisc2:0:11
> gscps2.c: timeout - could not write byte 0xed
> gscps2.c: sending byte 0xed failed.

mice: PS/2 mouse device common for all mice
serio: GSC PS2 keyboard port at 0xf0108000 irq 69 @ parisc2:0:11
input: AT Raw Set 2 keyboard on parisc2:0:11
serio: GSC PS2 mouse port at 0xf0108100 irq 69 @ parisc2:0:12

> HP SDC: HP SDC reports successful PUP.
> HP SDC: HP SDC at 0xf0201000, IRQ 126 (NMI IRQ 125)
> HP SDC: New style SDC
> HP SDC: Revision: 1820-4784
> HP SDC: TI SN76494 beeper present
> HP SDC: OKI MSM-58321 BBRTC present
> HP SDC: Spunking the self test register to force PUP on next firmware reset.
> HP SDC MLC: Registering the System Domain Controller's HIL MLC.
> 
> -> OK, the HIL stuff is detected. (BTW, test this after power-cycling the machine!)

HP SDC: HP SDC at 0xf0201000, IRQ 126 (NMI IRQ 125)
HP SDC: New style SDC
HP SDC: Revision: 1820-4784
HP SDC: TI SN76494 beeper present
HP SDC: OKI MSM-58321 BBRTC present
HP SDC: Spunking the self test register to force PUP on next firmware reset.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.

> and then nearly at the end of dmesg:
> HIL KEYB: HIL keyboard found (did = 0xcf, lang = german)
> input: HIL keyboard, ID: 207

Not found here, of course.

> HIL PTR: HIL pointer device found (did: 0x68, axis: relative)
> HIL PTR: HIL pointer has 3 buttons and 1 sets of 2 axes
> input: HIL pointer device (HIL mouse), ID: 104

Not found here as well.

> This is now HIL keyboard and HIL mouse.
> So my HIL mouse is detected, but doesn't seem to work yet.... :-( 

*sigh*

> > FWIW: I had mouse support and I had keyboard support.  Just not at the
> > same time unfortunately.  So in general it works at least.  The
> > configuration is a bit non-intuitive since you'll have to enable
> > HIL_KBD and AT_KBD.  However, logically it makes sense.
> 
> No. You should disable HIL_KBD (but it doesn't hurt either).

Done.  Keyboard still works.

> As said above: Hard Power-cycle the machine before each test!

Of course.  I'll have to turn it off for keyboard / mouse changes
or the machine will drop support for what I changed.

> Furthermore you might try to increase the value of mdelay(6); in line 168
> in file linux-2.6/drivers/input/serio/gscps2.c...
> Maybe it's a timing issue ?

Apparently, it was.  I now have keyboard and mouse support.
I set the delay to 12.

> This is what you should have in your .config:
> CONFIG_SERIO_GSCPS2=y
> CONFIG_INPUT_KEYBOARD=y
> CONFIG_KEYBOARD_ATKBD=y
> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y

All there.

Everything's working fine now, btw.

Regards,

	Joey

-- 
Whenever you meet yourself you're in a time loop or in front of a mirror.

Please always Cc to me when replying to me on the lists.

[parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Monday 15 March 2004 18:14, Martin Schulze wrote:
> > Furthermore you might try to increase the value of mdelay(6); in line 168
> > in file linux-2.6/drivers/input/serio/gscps2.c...
> > Maybe it's a timing issue ?
> 
> Apparently, it was.  I now have keyboard and mouse support.
> I set the delay to 12.

Did you tried any other values between 6 and 12 ?
If a lower value works for you, I would like to put this one in the source....

> > This is what you should have in your .config:
> > CONFIG_SERIO_GSCPS2=y
> > CONFIG_INPUT_KEYBOARD=y
> > CONFIG_KEYBOARD_ATKBD=y
> > CONFIG_INPUT_MOUSE=y
> > CONFIG_MOUSE_PS2=y
> 
> All there.
> 
> Everything's working fine now, btw.

Cool. 

Regards,
Helge

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Andy Walker]

----- Original Message ----- 
From: "Helge Deller" <deller@gmx.de>
> > > Maybe it's a timing issue ?
> >
> > Apparently, it was.  I now have keyboard and mouse support.
> > I set the delay to 12.
>
> Did you tried any other values between 6 and 12 ?
> If a lower value works for you, I would like to put this one in the
source....
>

Helge,

I'll try playing with the delay on the B132L as well and report back. Time
to
compile....

-Andy

[parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Helge Deller wrote:
> On Monday 15 March 2004 18:14, Martin Schulze wrote:
> > > Furthermore you might try to increase the value of mdelay(6); in line 168
> > > in file linux-2.6/drivers/input/serio/gscps2.c...
> > > Maybe it's a timing issue ?
> > 
> > Apparently, it was.  I now have keyboard and mouse support.
> > I set the delay to 12.
> 
> Did you tried any other values between 6 and 12 ?
> If a lower value works for you, I would like to put this one in the source....

mdelay(8) contains the lowest value with which the mouse starts to work.

In order to have proper/normal responses you'd have to increase the
responsiveness with gpm, though, but with X the mouse curser runs fast
as usual.

Regards,

	Joey

-- 
The MS-DOS filesystem is nice for removable media.  -- H. Peter Anvin

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Sunday 14 March 2004 08:37, Martin Schulze wrote:
> > In the latest 2.6 kernel series, we switched from a parisc-only
> > PS/2 mouse/keyboard driver to the standard linux kernel PS/2
> > mouse keyboard drivers.
> 
> Makes sense.  However, would it be useful to add this to the config
> help texts?  Same for the dependency of a HIL mouse to the MOUSE_PS2,
> if HIL always takes PS/2 mice.  I know this is not the case in general,
> since my 425 uses HIL but doesn't use PS/2, but then again, it's m68k
> and not parisc.  However, it may be the case on PA-RISC, I don't know.
> In that case it may make sense to rearrange the ordering and move
> MOUSE_HIL up so it can pre-select MOUSE_PS2.
> 
> Anyway, here's a short improvement for the MOUSE_PS2 help text:
> 
> --- Kconfig.orig	Sun Mar 14 08:27:51 2004
> +++ Kconfig	Sun Mar 14 08:31:18 2004
> @@ -22,7 +22,8 @@
>  	  Say Y here if you have a PS/2 mouse connected to your system. This
>  	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
>  	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
> -	  compatible.
> +	  compatible. This also includes a PS/2 mouse connected to your HIL
> +	  hub on PA-RISC.
>  
>  	  Synaptics TouchPad users might be interested in a specialized
>  	  XFree86 driver at:

Hi Joey

I don't know if this makes sense to be too verbose here....
"...a PS/2 mouse connected to your system..." looks pretty ok, independed
if it is connected to a HIL hub or not.

Helge

[parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Helge Deller wrote:
> On Sunday 14 March 2004 08:37, Martin Schulze wrote:
> > > In the latest 2.6 kernel series, we switched from a parisc-only
> > > PS/2 mouse/keyboard driver to the standard linux kernel PS/2
> > > mouse keyboard drivers.
> > 
> > Makes sense.  However, would it be useful to add this to the config
> > help texts?  Same for the dependency of a HIL mouse to the MOUSE_PS2,
> > if HIL always takes PS/2 mice.  I know this is not the case in general,
> > since my 425 uses HIL but doesn't use PS/2, but then again, it's m68k
> > and not parisc.  However, it may be the case on PA-RISC, I don't know.
> > In that case it may make sense to rearrange the ordering and move
> > MOUSE_HIL up so it can pre-select MOUSE_PS2.
> > 
> > Anyway, here's a short improvement for the MOUSE_PS2 help text:
> > 
> > --- Kconfig.orig	Sun Mar 14 08:27:51 2004
> > +++ Kconfig	Sun Mar 14 08:31:18 2004
> > @@ -22,7 +22,8 @@
> >  	  Say Y here if you have a PS/2 mouse connected to your system. This
> >  	  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
> >  	  mice with wheels and extra buttons, Microsoft, Logitech or Genius
> > -	  compatible.
> > +	  compatible. This also includes a PS/2 mouse connected to your HIL
> > +	  hub on PA-RISC.
> >  
> >  	  Synaptics TouchPad users might be interested in a specialized
> >  	  XFree86 driver at:
> 
> Hi Joey
> 
> I don't know if this makes sense to be too verbose here....
> "...a PS/2 mouse connected to your system..." looks pretty ok, independed
> if it is connected to a HIL hub or not.

Well, if you *know* that it's a PS/2 mouse and PS/2 keyboard, you're
correct.  However, does everybody know that who gets hold of a PARISC
machine fully equipped with HIL hub and stuff?  Maybe it's just me
who hasn't expected that since the old (really old) machines didn't
use pc standard equipment and since PA machines usually use different
parts.  You choose since you're more familiar with the port.

Regards,

	Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Re: [parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Grant Grundler]

> Well, if you *know* that it's a PS/2 mouse and PS/2 keyboard, you're
> correct.  However, does everybody know that who gets hold of a PARISC
> machine fully equipped with HIL hub and stuff?  Maybe it's just me
> who hasn't expected that since the old (really old) machines didn't
> use pc standard equipment and since PA machines usually use different
> parts.  You choose since you're more familiar with the port.

Well, maybe it would be better to make this a FAQ on the parisc-linux
web site?

grant

Re: [parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Grant Grundler wrote:
> > Well, if you *know* that it's a PS/2 mouse and PS/2 keyboard, you're
> > correct.  However, does everybody know that who gets hold of a PARISC
> > machine fully equipped with HIL hub and stuff?  Maybe it's just me
> > who hasn't expected that since the old (really old) machines didn't
> > use pc standard equipment and since PA machines usually use different
> > parts.  You choose since you're more familiar with the port.
> 
> Well, maybe it would be better to make this a FAQ on the parisc-linux
> web site?

Aye!

--- /tmp/work/faq.html.orig	2004-03-15 09:36:25.000000000 +0100
+++ /tmp/work/faq.html	2004-03-15 09:41:54.000000000 +0100
@@ -8,6 +8,23 @@
   <li>First of all, your kernel has to be 2.4.18-pa45 or higher.<br>
       Earlier kernel versions will not work !
   </li>
+
+  <li>In the latest 2.6 kernel series, we switched from a PA-RISC-only
+      PS/2 mouse/keyboard driver to the standard Linux kernel PS/2
+      mouse and keyboard drivers.  Hence, in order to get your PS/2
+      mouse/keyboard connected via HIL work you'll have to enable
+      <ul>
+      <li> CONFIG_KEYBOARD_ATKBD
+      <li> CONFIG_MOUSE_PS2
+      </ul>
+      in addition to
+      <ul>
+      <li> CONFIG_INPUT_KEYBOARD
+      <li> CONFIG_KEYBOARD_HIL
+      <li> CONFIG_INPUT_MOUSE
+      <li> CONFIG_MOUSE_HIL
+      </ul>
+  </li>
   <li>On the bash prompt enter as root the following comand:<br>
       <code>cd /dev && ./MAKEDEV input</code><br>
       This command creates the standard input device nodes in the /dev/input/

-- 
Whenever you meet yourself you're in a time loop or in front of a mirror.

Re: [parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Martin Schulze wrote:
> Grant Grundler wrote:
> > > Well, if you *know* that it's a PS/2 mouse and PS/2 keyboard, you're
> > > correct.  However, does everybody know that who gets hold of a PARISC
> > > machine fully equipped with HIL hub and stuff?  Maybe it's just me
> > > who hasn't expected that since the old (really old) machines didn't
> > > use pc standard equipment and since PA machines usually use different
> > > parts.  You choose since you're more familiar with the port.
> > 
> > Well, maybe it would be better to make this a FAQ on the parisc-linux
> > web site?
> 
> Aye!

Maybe this one is better since CONFIG_KEYBOARD_HIL and CONFIG_HIL_MLC
aren't required.  I'm not sure about the mouse part since mine doesn't
yet work again.

--- /tmp/work/faq.html.orig	2004-03-15 09:36:25.000000000 +0100
+++ /tmp/work/faq.html	2004-03-15 10:44:59.000000000 +0100
@@ -8,6 +8,27 @@
   <li>First of all, your kernel has to be 2.4.18-pa45 or higher.<br>
       Earlier kernel versions will not work !
   </li>
+
+  <li>In the latest 2.6 kernel series, we switched from a PA-RISC-only
+      PS/2 mouse/keyboard driver to the standard Linux kernel PS/2
+      mouse and keyboard drivers.  Hence, in order to get your PS/2
+      mouse/keyboard connected via HIL work you'll have to enable
+      <ul>
+      <li> CONFIG_KEYBOARD_ATKBD
+      <li> CONFIG_MOUSE_PS2
+      </ul>
+      in addition to
+      <ul>
+      <li> CONFIG_INPUT_KEYBOARD
+      <li> CONFIG_INPUT_MOUSE
+      <li> CONFIG_MOUSE_HIL
+      </ul>
+      You don't need these options anymore:
+      <ul>
+      <li> CONFIG_KEYBOARD_HIL
+      <li> CONFIG_HIL_MLC
+      </ul>
+  </li>
   <li>On the bash prompt enter as root the following comand:<br>
       <code>cd /dev && ./MAKEDEV input</code><br>
       This command creates the standard input device nodes in the /dev/input/


Regards,

	Joey

-- 
Whenever you meet yourself you're in a time loop or in front of a mirror.

Please always Cc to me when replying to me on the lists.

Re: [parisc-linux] Re: Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

Thanks !

I added a new FAQ entry based on your input.

Helge

On Monday 15 March 2004 16:05, Martin Schulze wrote:
> Martin Schulze wrote:
> > Grant Grundler wrote:
> > > > Well, if you *know* that it's a PS/2 mouse and PS/2 keyboard, you're
> > > > correct.  However, does everybody know that who gets hold of a PARISC
> > > > machine fully equipped with HIL hub and stuff?  Maybe it's just me
> > > > who hasn't expected that since the old (really old) machines didn't
> > > > use pc standard equipment and since PA machines usually use different
> > > > parts.  You choose since you're more familiar with the port.
> > > 
> > > Well, maybe it would be better to make this a FAQ on the parisc-linux
> > > web site?
> > 
> > Aye!
> 
> Maybe this one is better since CONFIG_KEYBOARD_HIL and CONFIG_HIL_MLC
> aren't required.  I'm not sure about the mouse part since mine doesn't
> yet work again.
> 
> --- /tmp/work/faq.html.orig	2004-03-15 09:36:25.000000000 +0100
> +++ /tmp/work/faq.html	2004-03-15 10:44:59.000000000 +0100
> @@ -8,6 +8,27 @@
>    <li>First of all, your kernel has to be 2.4.18-pa45 or higher.<br>
>        Earlier kernel versions will not work !
>    </li>
> +
> +  <li>In the latest 2.6 kernel series, we switched from a PA-RISC-only
> +      PS/2 mouse/keyboard driver to the standard Linux kernel PS/2
> +      mouse and keyboard drivers.  Hence, in order to get your PS/2
> +      mouse/keyboard connected via HIL work you'll have to enable
> +      <ul>
> +      <li> CONFIG_KEYBOARD_ATKBD
> +      <li> CONFIG_MOUSE_PS2
> +      </ul>
> +      in addition to
> +      <ul>
> +      <li> CONFIG_INPUT_KEYBOARD
> +      <li> CONFIG_INPUT_MOUSE
> +      <li> CONFIG_MOUSE_HIL
> +      </ul>
> +      You don't need these options anymore:
> +      <ul>
> +      <li> CONFIG_KEYBOARD_HIL
> +      <li> CONFIG_HIL_MLC
> +      </ul>
> +  </li>
>    <li>On the bash prompt enter as root the following comand:<br>
>        <code>cd /dev && ./MAKEDEV input</code><br>
>        This command creates the standard input device nodes in the /dev/input/
> 
> 
> Regards,
> 
> 	Joey
> 
> -- 
> Whenever you meet yourself you're in a time loop or in front of a mirror.
> 
> Please always Cc to me when replying to me on the lists.
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> 

[parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Martin Schulze]

Martin Schulze wrote:
> > > # Input Device Drivers
> > > #
> > > CONFIG_INPUT_KEYBOARD=y
> > > # CONFIG_KEYBOARD_ATKBD is not set
> > 
> > Please enable this one (CONFIG_KEYBOARD_ATKBD), and....
> > 
> > > # CONFIG_KEYBOARD_SUNKBD is not set
> > > # CONFIG_KEYBOARD_XTKBD is not set
> > > # CONFIG_KEYBOARD_NEWTON is not set
> > > CONFIG_KEYBOARD_HIL=y
> > > CONFIG_INPUT_MOUSE=y
> > > # CONFIG_MOUSE_PS2 is not set
> > 
> > this one too.
> > 
> 
> For what it's worth, these settings don't activate my keyboard,
> but... tadam...  the mouse is recognised, finally.  However, if

That must have been a strange accidential coincidence, since I haven't
been able to use the mouse again but the keyboard worked as expected.
I'm totally puzzled at the moment.

Keyboard: yes
Mouse: no

CONFIG_INPUT=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_HIL=y
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_GSCPS2=y

Anything missing?

If anybody is interested, here's the kernel config
http://luonnotar.infodrom.org/~joey/config

FWIW, without CONFIG_KEYBOARD_ATKBD (in connection to CONFIG_KEYBOARD_HIL)
the keyboard is dead as a doornail, hint-thanks go to Helge.

Here's what the kernel says during boot:

mice: PS/2 mouse device common for all mice
serio: GSC PS2 keyboard port at 0xf0108000 irq 69 @ parisc2:0:11
input: AT Raw Set 2 keyboard on parisc2:0:11
serio: GSC PS2 mouse port at 0xf0108100 irq 69 @ parisc2:0:12

That would make me think that the mouse is detected, though.

It also says lots of:
HP SDC: Transaction add failed: transaction already queued?
I guess this has nothing to do with the mouse problem.

Regards,

	Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Re: [parisc-linux] Re: No PS2 keyboard/mouse on B132L, 2.6.[34]

[Helge Deller]

On Sunday 14 March 2004 21:47, Martin Schulze wrote:
> That must have been a strange accidential coincidence, since I haven't
> been able to use the mouse again but the keyboard worked as expected.
> I'm totally puzzled at the moment.
> 
> Keyboard: yes
> Mouse: no
> 
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y
> CONFIG_MOUSE_HIL=y
> CONFIG_SERIO=y
> CONFIG_SERIO_SERPORT=y
> CONFIG_SERIO_GSCPS2=y
> 
> Anything missing?

CONFIG_INPUT_KEYBOARD=y, but it seems you just forgot to add it to this list.

> Here's what the kernel says during boot:
> 
> mice: PS/2 mouse device common for all mice
> serio: GSC PS2 keyboard port at 0xf0108000 irq 69 @ parisc2:0:11
> input: AT Raw Set 2 keyboard on parisc2:0:11
> serio: GSC PS2 mouse port at 0xf0108100 irq 69 @ parisc2:0:12
> 
> That would make me think that the mouse is detected, though.

No, it's not.
I'm missing something like:
"input: Logitech mouse on parisc2:0:12".....

> It also says lots of:
> HP SDC: Transaction add failed: transaction already queued?
> I guess this has nothing to do with the mouse problem.

Disable all HIL/SDC stuff.

Helge