On Sun, 11 Jun 2000, Tom Rauschenbach wrote: > As I reported earlier, when I installed a new kernel I went from not > having 16 bit sound to not having any sound. Several people suggested a > conflict on IRQ7. Very likely. What specifically is happening? Driver loads but doesn't work? Driver doesn't load? Driver hangs? Any error messages or other diagnostics? > Reading /proc/interupts is not helpful. /proc/interrupts only tells you about IRQs the kernel *knows* about. Interrupt conflicts usually occur because you've got something using an IRQ that you don't know about. Thus, listing the kernel's IRQ table can help, but generally won't answer any questions on it's own. Does the kernel think *anything* is using IRQ7? The "standard" for LPT1 (the first parallel port, lp0, parport0) is IRQ7, base address 0x0378, if that helps any. You may find clues in the kernel's boot messages, /proc/ entries, Win95/98's "Device Manager", your BIOS's boot or setup screens, hardware-specific diagnostic programs, generic programs like Norton Utilities, looking at physical card settings, looking at BIOS settings, and the average local airspeed of an unlaiden Swallow. > How do other folks diagnose interupt conflicts ? Trial and error, mainly. Resource conflicts are one of the reasons I hate the ISA bus so much. Typical procedure is to disable and/or physically remove as much hardware as possible. Boot the system and see what works. If everything does, shutdown, add a component, boot up and see if it works and/or what else broke. Repeat until you've found the problem or smashed everything into its component elements. On Mon, 12 Jun 2000, Farrell Woods wrote: > IRQ7 I think is usually taken by the parallel port, but the kernel probed > it as "polled"... Note that, even if a device using an IRQ isn't recognized by the software, it can still cause conflicts by preventing other devices from pulling the line high when needed. > Some mobos allow you to assign IRQ's to PCI slots and/or mark certain > IRQ's as "in use by a non-PnP device". See if you can (re)arrange things > so that the SB isn't sharing an IRQ. This is something often over-looked by many people. If you have any PnP or PCI cards in a system (read: if you have a computer built after 1994), and you also have older, non-PnP, ISA cards using fixed IRQs (many sound and modem cards), you *MUST* tell your BIOS about them, or System Instability(TM) may result. The reason is that PCI and ISA PnP cards are assigned resources dynamically by the BIOS. If it doesn't know about an old ISA card using a resource, it may assign that resource to another card. The resulting conflicts can cause anything from head-scratching on your part to refusal to boot on the PC's part. Even "PnP aware" OSes fall victim to this, because all OSes need the BIOS to boot. So be sure you've got your BIOS configured properly. The options will usually be under a heading like "PNP and PCI Configuration". Common settings to choose are "Plug and Play OS" to "NO" and "Configure Resource Usage" to "MANUAL". Then look for a list of resources to reserve. After you've made any changes, look for "Reset PNP Data" and set it to "YES" for the next boot. This forces the BIOS to re-enumerate system devices and their resource assignments. Aren't PCs fun? :-) -- Ben Scott <[EMAIL PROTECTED]> | Brooks's Law: "Adding manpower to a late software project makes it later." | ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
