From: Meelis Roos <mroos@linux.ee>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Jerome Glisse <j.glisse@gmail.com>,
Alex Deucher <alexander.deucher@amd.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: Radeon RV100 init fails with specific card+mobo - IRQ problem
Date: Fri, 1 Feb 2013 21:54:34 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1302012153260.3031@math.ut.ee> (raw)
In-Reply-To: <CADnq5_Ny9_OVqyahSN9WOuwt=PxbT48=NbWr0-r1A5y0yhHKhA@mail.gmail.com>
> >> > Adding some printks reveals it calls
> >> > r100_init() -> radeon_irq_kms_init() -> drm_irq_install() ->
> >> > drm_dev_to_irq() and that fails. So no IRQ, no KMS.
> >> >
> >> > lspci does not show Interrupt like on some other PCI devices.
> >> > /proc/interrupts obviously does not contain the irq since we do not
> >> > register any yet.
> >> >
> >> > There is no BIOS option of "Enable IRQ for VGA" or similar (BIOS is
> >> > latest). Could this be the problem?
> >> >
> >> > What can I do to get KMS working on this computer?
> >> >
> >> > --
> >> > Meelis Roos (mroos@linux.ee)
> >>
> >> Try booting with radeon.agp_mode=-1
> >
> > radeon: `-1' invalid for parameter `agp_mode'
>
> radeon.agpmode=-1
Still fails in the same place as in the beginning - finding IRQ.
> However, I think there are a number of places where we require
> interrupts that would need to be worked around (fences, display
> hotplug, pageflipping) if not interrupt is available.
OK.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2013-02-01 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 12:24 Meelis Roos
2013-02-01 15:01 ` Jerome Glisse
2013-02-01 15:26 ` Meelis Roos
2013-02-01 15:41 ` Alex Deucher
2013-02-01 19:54 ` Meelis Roos [this message]
2013-02-04 16:32 ` Meelis Roos
2013-02-04 16:42 ` Alex Deucher
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.SOC.1.00.1302012153260.3031@math.ut.ee \
--to=mroos@linux.ee \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
all inboxes | Powered by JetHome®