From: Helge Hafting <helgehaf@aitel.hist.no>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
covici@ccs.covici.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 dies when X tries to initialize PCI radeon 9200 SE
Date: Mon, 17 Jan 2005 18:19:40 +0100 [thread overview]
Message-ID: <20050117171940.GA14407@hh.idb.hist.no> (raw)
In-Reply-To: <9e4733910501161408710bbbe2@mail.gmail.com>
On Sun, Jan 16, 2005 at 05:08:12PM -0500, Jon Smirl wrote:
> On Sun, 16 Jan 2005 13:18:23 +0100, Helge Hafting
> <helgehaf@aitel.hist.no> wrote:
> > On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > > you need to check the output from "modprobe drm debug=1" "modprobe
> > > radeon" and see if drm is misidentifying the board as AGP. We don't
> > > want to fix something if it isn't broken.
> > >
> > Stupid question - how do I get a modular drm?
>
> For older radeon drivers "modprobe radeon debug=1" should work. I also
> think you can do it for compiled in ones by adding the kernel
> parameter radeon.debug=1
>
I tried 2.6.11rc1, which has modular drm (and also the crash I'm
struggling with.)
# modprobe drm debug=1
# modprobe radeon
I got this in dmesg (some of it also on the console):
[drm] Initialized drm 1.0.0 20040925
[drm:drm_init]
[drm:drm_probe]
[drm:drm_probe] assigning minor 0
PCI: Enabling device 0000:00:08.0 (0000 -> 0003)
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 19
[drm:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 0
[drm:drm_ctxbitmap_init] drm_ctxbitmap_init : 0
[drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc
RV280 [Radeon 9200 SE]
[drm:drm_probe] new minor assigned 0
I guess it was detected as pci, due to the "PCI: Enabling device..." message.
At least there is no mention of AGP here.
I tried to run X on the radeon after this, and it locked up solid as usual.
I hope this helps. I can try other kernels, but I hope a binary
search will be a last resort. (I will try that if absolutely necessary,
but it will take time. I can't reboot all the time.)
Helge Hafting
next prev parent reply other threads:[~2005-01-17 17:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 10:30 2.6.10 dies when X tries to initialize PCI radeon 9200 SE Helge Hafting
2005-01-13 11:00 ` John covici
2005-01-13 21:06 ` Dave Airlie
2005-01-15 18:57 ` Helge Hafting
2005-01-16 10:08 ` Dave Airlie
2005-01-16 10:33 ` Jon Smirl
2005-01-16 10:37 ` Dave Airlie
2005-01-16 10:35 ` Jon Smirl
2005-01-16 10:50 ` Helge Hafting
2005-01-16 11:04 ` Jon Smirl
2005-01-16 11:07 ` Dave Airlie
2005-01-16 11:34 ` Jon Smirl
2005-01-16 11:41 ` Dave Airlie
2005-01-21 18:26 ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Helge Hafting
2005-01-21 18:49 ` John covici
2005-01-16 12:26 ` 2.6.10 dies when X tries to initialize PCI radeon 9200 SE John covici
2005-01-16 12:18 ` Helge Hafting
2005-01-16 20:25 ` Mike Houston
2005-01-16 22:08 ` Jon Smirl
2005-01-16 22:24 ` Helge Hafting
2005-01-17 17:19 ` Helge Hafting [this message]
2005-01-14 2:20 ` David Lang
2005-01-14 10:35 ` Helge Hafting
2005-01-14 12:41 ` John covici
2005-01-15 8:23 ` Dave Airlie
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=20050117171940.GA14407@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=airlied@gmail.com \
--cc=covici@ccs.covici.com \
--cc=jonsmirl@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;
as well as URLs for NNTP newsgroup(s).