Red Hat Bugzilla – Bug 43504
(ISAPNP IRQ_ROUTING)ps/2 mouse not detected
Last modified: 2007-04-18 12:33:34 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.73C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC) Description of problem: During the fresh installation, the mouse and X worked just fine. Now, when using the 2.4.2-2 kernel supplied, any attempt to go to run level 5 fails because the ps/2 mouse is not detected. on startup gpm reports: gpm[819]: oops() invoked from gpm.c(978) gpm[819]: /dev/mouse: Device or resource busy a 'cat /proc/interrupts' reveals that IRQ 12 is being used by the sound card. The mouse is not detected. greping dmesg also shows that the PS/2 mouse has not been detected. Without that mouse, x fails with a: Cannot open mouse (Device or resource busy) How reproducible: Always Steps to Reproduce: 1. boot Redhat Linux 7.1 2. 3. Actual Results: the ps/2 mouse was not detected Expected Results: the ps/2 mouse should have been detected, and gpm & X run normally. Additional info: lspci shows; 00:00:0 Host bridge: Intel Corp 430TX - 82439TX MTXC (rev 01) Onboard VGA, Ethernet controller, ISA Bridge, IDE nterface, USB Controller and Bridge are detected.
If you disable the loading of the sound-module (eg edit /etc/modules.conf and comment the sound module otu), does it work then ?
I found a /etc/modules.conf~ which only loaded the parport and ethernet, so after reciprocating the name of this and the active modules.conf file I restarted and found that the ps/2 mouse had been detected. after editing the other modules.conf file so that the sound card used IRQ 5 & 11 instead of 5 & 12 both the ps/2 mouse and sound worked normally: options cs4232 io=0x534 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=11 cat /proc/interrupts now shows: CPU0 0: 330407 XT-PIC timer 1: 7 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 1 XT-PIC Crystal audio controller 8: 1 XT-PIC rtc 10: 5360 XT-PIC usb-uhci, PCnet/FAST 79C971 11: 0 XT-PIC MPU-401 UART 12: 24 XT-PIC PS/2 Mouse 14: 5767 XT-PIC ide0 15: 0 XT-PIC ide1 Why is it that and interrupt of 12 was given to the sound card when an active PS/ 2 mouse was part of the system? Will the USB controller and the ethernet controller interfere with each other sharing IRQ 10? Thanks for the prompt assistance.
IRQ's _should_ be able to be shared. Unfortionatly, some hardware seems to cheat and object to that... it seems to happen with soundcards more than with other hardware. I've changed the kernel (for future versions) to make it use IRQ 12 less for other hardware, although sometimes the BIOS makes the choice and Linux just trusts the bios.
I have a similar problem, but it's more insidious: Even if I change modules.conf the way marco did, when I reboot IT GETS CHANGED BACK. In fact, these files, which all reference the sound card, get changed at EVERY boot: /etc/modules.conf /etc/sysconfig/hwconfig /etc/sysconfig/soundcard So no matter what I do, I still can't run X. BTW, the biggest common factor I have with marco is that I also have a Crystal audio controller that worked fine under RedHat 6.2.
This problem continues on with the roswell beta release also, as said criglerj@acm.org , even if I change the /etc/modules.conf to not load the sound module, or specify the sound card options, it gets changed on reboot. Again the common factors are that I have a cs4232 and a ps2 mouse. Can we pls pls pls find a workaround on this one. Regards Harman
I, too, have the same problem as criglerj@acm.org. On reboot the /etc/modules.conf is changed back so the cs4232 is set to use IRQ's 5 and 12. -Leon
I had the same problem on my machine. Setup: Dell Dimension XPS R450, BIOS: 4S4EBOX1.10A.0019.P09 version A09, MS IntelliMouse on PS/2, Crystal Audio controller. I have been trying to install 7.1 with the same problem with mouse detection for the past week. As a last resort I tried a BIOS upgrade and it worked! I'm on BIOS version A13. I dont know if this is relevant to the problems you all are having, but I had exactly the same symptoms.
My solution was also in the BIOS. I have an Award BIOS and was able to find a section for setting up PCI/PNP settings. In my case I had to set IRQ 5 and IRQ 9 to the setting of "Legacy ISA" the other available setting was "PCI/PNP" and this setting caused the problems. Of course now I have new problems and while I get a GUI screen, I cannot log so have to begin at the console, log in, and then startx.
I too had the same problem. I have an E-machines etower 333 with a crystal audio 423x chipset. This system worked fine with 6.0, 6.1, 6.2 and 7.0. When I upgraded to 7.1, no mouse. The uart on the audio ended up with interrupt 12, which disabled the mouse. I tried overriding the /etc/modules.conf settings with my own, only to discover that they get written at boot time. I disabled sound which enabled the mouse, but that wasn't a satisfactory setup. So, I started troubleshooting and here is what I found... /etc/modules.conf is written at boot time under the control of the /etc/rc.d/rc.sysinit script. rc.sysinit calls /sbin/sndconfig with the (undocumented) --mungepnp option to generate the /etc/modules.conf. /sbin/sndconfig gets its PnP information from /sbin/pnpdump, which shows IRQ 12 as a valid choice for the sound card MPU. I tried installing the isapnptools to override the sound card configuration. I marked IRQ 12 as used in the /etc/isapnp.gone file, but this had no effect. I next went to the kernel source to figure out how the kernel does hardware detection. While looking through the documentation I came across a description of how the PCI card slot interrupts are allocated and how to override them in /usr/src/linux-2.4/Documentation/i386/IO-APIC.txt. I checked my /proc/interrupts and figured out which IRQs the cards in the PCI slots were using and specified them with 'append="pirq=10,8"' in the /etc/lilo.conf. I ran /sbin/lilo, then rebooted and the MPU had moved to IRQ 11 and the mouse was on 12. It would seem that when the kernel (2.4.x) does hardware detection, it reserves certain IRQs for the PCI slots. When it runs short of IRQs, it attempts to share(?) and thus IRQ 12 ends up assigned to a sound card. It also appears that sound cards don't play well with others, therefore the mouse doesn't get detected. I did find one more interesting item. I removed the append from the /etc/lilo.conf and rebooted and everything is still fine. It appears that once the system boots in the reconfigured mode it retains those settings and the hardware detection rediscovers them.
I also have a CS4232 and PS/2 mouse (HP Pavilion 6355), and made the following two changes to get things to work: 1. Edit the "options cs4232" line in /etc/modules.conf to include "mpuirq=11" 2. Pass "nopnp" on the kernel command line. This prevents "sndconfig --mungepnp" from being executed in /etc/rc.d/rc.sysinit; yet the sound configuration has already been generated in /etc/modules.conf What's interesting is that "cat /proc/isapnp" showed the MPU as "active" before I added the "mpuirq=11" option; maybe since I didn't specify "mpuio", it got set as "not active"... -Greg
Resolved by making ISAPnP favour keeping away from IRQ 12 (PS/2)