LKML Archive on
help / color / mirror / Atom feed
From: "linux-os (Dick Johnson)" <>
To: "Jan Marek" <>
Cc: "lkml" <>
Subject: Re: Is it possible to change IRQ for certain device?
Date: Thu, 10 Jan 2008 09:01:37 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 10 Jan 2008, Jan Marek wrote:

> Hello lkml,
> I have problem with my computer: I have motherboard with AMD690G chipset
> and nVidia VGA card. But I cannot set BIOS, to assign for VGA unique
> IRQ. VGA card is sharing IRQ with two ohci_hcd (USB 1.1 controllers).
> But when I want use for X proprietary nvidia driver, X didn't work with
> this errors:
> In dmesg:
> NVRM: RmInitAdapter failed! (0x23:0xffffffff:678)
> NVRM: rm_init_adapter(0) failed
> and in /var/log/Xorg.0.log:
> (II) Setting vga for screen 0.
> (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
> (==) NVIDIA(0): RGB weight 888
> (==) NVIDIA(0): Default visual is TrueColor
> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
> (**) NVIDIA(0): Enabling RENDER acceleration
> (II) NVIDIA(0): Support for GLX with the Damage and Composite X
> extensions is
> (II) NVIDIA(0):     enabled.
> (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device
> PCI:1:0:0.
> (EE) NVIDIA(0):     Please see the COMMON PROBLEMS section in the
> README for
> (EE) NVIDIA(0):     additional information.
> (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
> (EE) NVIDIA(0):  *** Aborting ***
> (II) UnloadModule: "nvidia"
> (II) UnloadModule: "fb"
> (EE) Screen(s) found, but none have a usable configuration.
> Fatal server error:
> no screens found
> I've found in README for NVIDIA, that VGA has to have unique IRQ. I've
> tried to set INTERRUPT_LINE and INTERRUPT_PIN with setpci tool, set
> pci=routeirq, pci=noacpi as the kernel boot parameters, but IRQ
> is still the same.
> Is there a way to change IRQ for VGA (or for ohci_hcd instead of VGA)
> directly in Linux?
> Thanks a lot.
> Sincerely
> Jan Marek

The interrupt lines are set by the traces on the PC board and
the contents of various "glue" chips and FPGAs. Many lap-tops,
for instance, only have one IRQ serving any PCI devices. If
your screen card can't share the only IRQ you have, it is
broken. Contact the vendor of both your motherboard (they
may have a BIOS upgrade) and the screen card (they may
have a fix).

Dick Johnson
Penguin : Linux version on an i686 machine (5588.29 BogoMips).
My book :

The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

  parent reply	other threads:[~2008-01-10 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 11:05 Is it possible to change IRQ for certain device? Jan Marek
2008-01-10 11:23 ` Andi Kleen
2008-01-10 14:01 ` linux-os (Dick Johnson) [this message]
2008-01-10 23:43   ` Len Brown
2008-01-11 16:57   ` Jan Marek
2008-01-14  3:57     ` Lee Revell
2008-01-14  5:30       ` Bryan Donlan
2008-01-14  6:04         ` Lee Revell
2008-01-15 21:33       ` Folkert van Heusden
     [not found] <fa.LwvfKOhzep/>
2008-01-11  5:18 ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).