Hitchhiker's Guide to Openbsd

12.7.2 - OpenBSD won't work on my 80386/80386SX/80486SX system!
80386SX/DX
Support for the 80386DX and 80386SX processors was dropped beginning with OpenBSD 4.2. In 
addition to limitations of the 80386 chip, the systems are just too slow and rarely had enough RAM and 
a required FPU to run OpenBSD. 
80486SX
The 80486SX chip was a "low-cost" version of the 80486, which lacked the hardware floating point 
support (like the 80386) OpenBSD requires. Fortunately, full 80486DX chips are fairly available, and is 
an easy upgrade in most systems. 
The 80486DX and newer chips run OpenBSD fine. 
12.7.3 - My dmesg shows multiple devices sharing the same Interrupt (IRQ)!
This is entirely acceptable, and in fact, even desirable for PCI devices. This is a design feature of the 
PCI bus. Some people will say that sharing interrupt requests (IRQs) is bad, however they are either 
confusing the situation with the ISA bus (where IRQ sharing is not permitted), or past experience with 
broken hardware or software. 
ISA devices can not share IRQs. If you find ISA devices sharing IRQs, you must correct this problem. 
12.7.4 - My keyboard/mouse keeps locking up (or goes crazy)!
This is most often seen when using a "switch box" (sometimes called a "KVM switch") to attach 
multiple computers to one keyboard, monitor and mouse. You can experiment with different brand and 
design switch boxes, but OpenBSD seems to be more sensitive to switching the mouse than some other 
operating systems. The problem is usually just the switching of the mouse. If you are not using the 
mouse, the solution is simple: don't attach the mouse cable to the computer. If you are using the mouse, 
http://www.openbsd.org/faq/faq12.html (8 of 12)9/4/2011 10:02:18 AM

---

12 - Hardware and Platform-Specific Questions
an easy solution is "one mouse per computer", and switch just the keyboard and monitor. You may find 
using a PS/2 Mouse -> USB port adapter (so OpenBSD sees a USB mouse) will work around this 
problem. If you just want console access to the machine, you may wish to consider using a 
serial console
 
instead.