On Sun, Sep 22, 2002 at 10:29:08PM -0400, Felix Miata wrote: > I wouldn't know about changing resources allocated to a mouse port. I > thought that was standardized a zillion PC years ago. I'm open to > suggestions about what to change in sound card resource assignments. In > OS/2, the sound card uses the following: > > IRQ 9 > IRQ 15 > port 0x534-537 > port 0x120-127 > port 0x220-22F > port 0x388-38B > port 0x330-331 > port 0x200-201 > > Given that PCI ETH0, USB, and ACPI are all on IRQ 5, I should think > irq=5 should be changed, but I can't see how that would kill psaux, > unless Linux is pushing ETH0, USB, and/or ACPI onto IRQ 12. io=0x530 > appears to be a mismatch with one of the allocations made running OS/2, > but it isn't anything close to the resource allocations OS/2 shows for > the mouse port.
Whatever OS/2 is using probably will work right under Linux. No guarantees though. Experiment. Sooner or later you'll find the right setting. My bet is that it's the io port that is conflicting. The mouse should be using IRQ 12. > To me it looks like a bug that sndconfig can produce a resource conflict > with so basic a device as a mouse port. Be that as it may, thank you > very much for your gracious help that has allowed me to learn a little > about /etc/modules.conf, and to get use of my mouse back. Well first off sndconfig is a redhat app... Mandrake doesn't really maintain it. I think the only reason the installer suggests it for isa sound cards is because I'm not sure that draksound supports them. Perhaps someone can clarify this. But at any rate I'm not sure how much sndconfig can know about your device settings in your system. ISA Plug and Play really was a joke. And so many times it just flat out doesn't work. So for sndconfig to get a resource setting wrong isn't terribly surprising to me... -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org Never take no as an answer from someone who isn't authorized to say yes.
