From: Dave Airlie <airlied@gmail.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3-mm2/mm1 breaks DRI
Date: Sat, 30 Jul 2005 14:03:52 +1000 [thread overview]
Message-ID: <21d7e997050729210379e221c3@mail.gmail.com> (raw)
In-Reply-To: <200507290652.44418.tomlins@cam.org>
Okay I'm still having trouble from reading back these e-mails on what
is broken and what isn't..
The most important question is if mainline 2.6.13-rc3 or -rc4 is okay?
If so then it is the -mm only that breaks it, if -mm only can you
modprobe drm debug=1
modprobe radeon
then start X and send me the log... try commenting out the in
radeon_drv.c line 79,
.presetup = radeon_presetup
to see if it makes it okay...
I've just booted 32-bit debian-stable and it works okay for me ..
Dave.
next prev parent reply other threads:[~2005-07-30 4:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 9:43 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 10:08 ` 2.6.13-rc3-mm2 Sam Ravnborg
2005-07-27 10:14 ` 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 12:08 ` 2.6.13-rc3-mm2 (kbuild broken for external modules) Miklos Szeredi
2005-07-27 12:31 ` Brice Goglin
2005-07-27 19:16 ` Sam Ravnborg
2005-07-28 11:11 ` Miklos Szeredi
2005-07-27 20:35 ` 2.6.13-rc3-mm2 doesn't boot Adrian Bunk
2005-07-27 21:16 ` Andrew Morton
2005-07-27 22:20 ` Adrian Bunk
2005-07-27 20:48 ` 2.6.13-rc3-mm2 Andrew James Wade
2005-07-27 21:11 ` 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 21:27 ` 2.6.13-rc3-mm2 David S. Miller
2005-07-27 21:58 ` 2.6.13-rc3-mm2/mm1 breaks DRI Ed Tomlinson
2005-07-29 0:37 ` Ed Tomlinson
2005-07-29 0:41 ` Dave Airlie
2005-07-29 10:52 ` Ed Tomlinson
2005-07-30 4:03 ` Dave Airlie [this message]
2005-08-17 12:33 ` Dave Airlie
2005-07-28 10:06 ` 2.6.13-rc3-mm2 Borislav Petkov
2005-07-28 15:01 ` 2.6.13-rc3-mm2 Martin J. Bligh
2005-07-28 17:41 ` 2.6.13-rc3-mm2 Andrew Morton
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=21d7e997050729210379e221c3@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.