SPONSORED LINKS
Back when I thought my CD-ROM might be EIDE or SCSI, and I tried the pre-built kernels with support for those kinds of CD-ROMs, it (of course) didn't work. After I was told my nipple was a "ps/2", I relinked /dev/mouse and changed my boot scripts to gpm -t ps2 and XF86Config likewise. The mouse worked fine, on both the console and X... Then, I hear that the CD-ROM is an "ATAPI". Trivial! Just take the ATAPI pre-built kernel! It didn't auto-detect, but *did* find it for the next boot. - - - - - And the mouse stopped working. "Cannot open mouse (Device or resource busy)" says both startx and gpm. There is not a gpm running in the background. Ahh, the pre-built ATAPI kernel had no ps2 support, I guessed. I compiled a new kernel with both ATAPI and ps2 support. Run it, still see the CD, still can't talk to mouse. Boot with old boot disk. No more CD, hello mouse.... - - - - - When I boot the custom kernel with the CD player installed, the mouse is always "busy". Same kernel booted with floppy drive in lets the mouse work, but CD-ROM isn't recognized even if I hot-swap it. I took the floppy mount out of my fstab, thinking the failed probing for it when its not installed was related. I get the CD-ROM, but still lose the mouse this way. - - - - - In summary: if I boot a kernel that can recognize my CD-ROM, when it is installed, I am mouse-less. If I boot a kernel that can't recognize my CD-ROM, or my CD_ROM player is physically gone, then I have a mouse. I've got to admit, this isn't the worst problem to have, but... What the flock is going on here? Frank