mike@vort.uucp (Mike Nemeth) (01/05/91)
the following will probably only be of interest to people using a Logitech Bus mouse and ISC 3.2.2. if you can't get both your modem and your mouse to work at the same time, read on... hardware: IPC 25Mhz 386, Future Domain SCSI controller, Logitech Bus mouse, USR Courier v.32 modem software: ISC 3.2.2 upgrade from 3.2.0.2, FAS 2.05 or 2.07 mouse interrupt: 3 (because FD SCSI controller uses 5 and cannot be remapped) serial port #0 interrupt: 4 (only 1 serial port configured) under 3.2.0.2, uugetty sucks like a chest wound, so i configure in FAS 2.07 (displacing "asy"), modem now works, mouse won't work. ie. % cat < /dev/logi produces nothing. dead like dinner. remove FAS driver, mouse works, but then i'm stuck with uugetty (ugh!) under 3.2.0.2. so i live without a mouse for awhile. modem works fine. eventually upgrade to 3.2.2, which has support for a bi-directional port. toss uugetty, can run straight /etc/getty on new device /dev/tty0d. build a kernel using ISC asy driver, reboot system, mouse works BUT now something else is broken! modem answers phone, but getty ignores it. i can picture extremely irritated user at other end of serial link beating on keys and cursing the air blue. play with modem, it's fine. read manual, check inittab, check gettydefs, check configuration, check board interrupts, and discover nothing supposedly wrong. okay, so maybe the 3.2.2 asy driver is ill. build another kernel with FAS 2.07 and no asy driver, reboot, modem now works but mouse is deceased again. eventually i found the following solution: change mouse configuration (/etc/conf/sdevice.d/asy) interrupt to "9", change Logitech Bus mouse board jumper to "2". build another kernel leaving asy out and FAS 2.07 in. power off and reboot, modem works and mouse works too, and nothing else seems to have broken (yet). -- Vort Computing is a non-profit organization, but i didn't plan it that way... Mike Nemeth Vort Computing ...calgary!vort!mike Witt's End BBS (403) 237-0501 2400/9600bps 9,N,1,"bbs"
gemini@geminix.in-berlin.de (Uwe Doering) (01/07/91)
mike@vort.uucp (Mike Nemeth) writes: > [ a report about FAS 2.07 and a Logitech bus mouse on IRQ3 not > working together ] This sounds to me like a classical interrupt conflict. Are you sure you configured both `s_fas' _and_ `space.c' for only one port (COM1)? I think that `s_fas' is set up properly because the kernel config program doesn't complain, but that in `space.c' there still might be two ports configured. FAS would then enable COM2, too, and would therefor block the IRQ3 line. This would result in the problems you've experienced. If my assumption is right you simply need to set the number of ports in `space.c' to `1' (`NUM_PHYSICAL_UNITS') and reduce all the initializer parts of the arrays indexed by `NUM_PHYSICAL_UNITS' to only one member. Please tell us if you could (really) fix the problem. Uwe -- Uwe Doering | INET : gemini@geminix.in-berlin.de Berlin |---------------------------------------------------------------- Germany | UUCP : ...!unido!fub!geminix.in-berlin.de!gemini