Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] pcg-c1mrx / pcg-c1mv
- To: tlug@example.com
- Subject: Re: [tlug] pcg-c1mrx / pcg-c1mv
- From: Christopher SEKIYA <wileyc@example.com>
- Date: Wed, 30 Jan 2002 20:50:04 +0900
- Content-disposition: inline
- Content-type: text/plain; charset=us-ascii
- In-reply-to: <E16VoxU-0001Ic-00@example.com>
- References: <E16VoxU-0001Ic-00@example.com>
- User-agent: Mutt/1.3.25i-ja.1
On Wed, Jan 30, 2002 at 04:15:32PM +0900, bhoward@example.com wrote: > PCI: No IRQ known for interrupt pin A of device 00:10.0 PCI BIOS is not assigning interrupts to its devices -- it expects the OS to do so. Laptops are notorious for this behavior, with Sony being the worst of the lot. Linux's PCI init code seems to have varying levels of success with PCI fixups. Compile a kernel with every PCI option available and see what happens. > As an aside, I tried OpenBSD 3.0 to see if it had the same problem -- > it did seem to have better luck recognizing devices but I haven't Ah! You're not averse to *BSD! This works for NetBSD and possibly OpenBSD -- compile a kernel with: options PCIBIOS_ADDR_FIXUP # fixup PCI I/O addresses options PCIBIOS_BUS_FIXUP # fixup PCI bus numbering options PCIBIOS_INTR_FIXUP # fixup PCI interrupt routing options PCIBIOS_INTR_FIXUP_FORCE ... and see what happens. I'll be willing to bet that things will look a LOT better. -- Chris
- References:
- [tlug] pcg-c1mrx / pcg-c1mv
- From: bhoward
Home | Main Index | Thread Index
- Prev by Date: [tlug] kernel compiling problem
- Next by Date: [tlug] multiple line traffic balance
- Previous by thread: [tlug] kernel compiling problem
- Next by thread: Re:[tlug] pcg-c1mrx / pcg-c1mv
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links