Hi,
On Wednesday 10 of August 2005 14:43, Vladimir Dergachev wrote:
> > Here is dmesg output:
> >
> > [drm] Initialized drm 1.0.0 20040925
> > PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device
> > :01:00.0 [drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI
> > Technologie
Here is dmesg output:
[drm] Initialized drm 1.0.0 20040925
PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :01:00.0
[drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI Technologies Inc
RV350 AS [Radeon 9600 AS]
[drm] Used old pci detect: framebuffer loaded
mtrr: 0xb0
Hi,
Thanks for the hint.
On Wednesday 10 of August 2005 13:43, you wrote:
> Hi,
>
> What is the dmesg output after X is terminated by the SIGKILL? I also
> am seeing X get killed the same way, and in dmesg it shows that the
> kernel killed it (see the messages with the subject "r300 DRI killing
Hi,
On Wednesday 10 of August 2005 11:53, you wrote:
> > I suggest testing a 2.6.12 not a 2.6.13, i think something might be wrong
> > with 2.6.13 (IIRC i see people complaining on lkml or on dri user) a
> > change in API a regression somewhere... But it could also be a 64bits
> > issue not seen
>
> I suggest testing a 2.6.12 not a 2.6.13, i think something might be wrong with
> 2.6.13 (IIRC i see people complaining on lkml or on dri user) a change in API
> a regression somewhere... But it could also be a 64bits issue not
> seen before :)
>
I'd appreciate if someone could test with 2.6.
On 8/10/05, Michał Pytasz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks for information,
> Unfortunately yesterday I built "vanilla" kernel 2.6.12.4 and 2.6.13-rc6 from
> kernel.org - I got same results as with gentoo patched kernel.
I suggest testing a 2.6.12 not a 2.6.13, i think something might
Hi,
On Wednesday 10 of August 2005 10:28, you wrote:
> On 8/9/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > Hi Michal,
> >
> > > (II) RADEON(0): [drm] DRM interface version 1.2
> > > (II) RADEON(0): [drm] created "radeon" driver at busid
> > > "pci::01:00.0" (II) RADEON(0): [drm] added
On 8/9/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
>
> Hi Michal,
>
> >
> > (II) RADEON(0): [drm] DRM interface version 1.2
> > (II) RADEON(0): [drm] created "radeon" driver at busid "pci::01:00.0"
> > (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc2bfc000
> >
> > Program ter
Hi,
On Monday 08 of August 2005 16:37, Vladimir Dergachev wrote:
> >> module loads fine, e-mail us any kernel messages it produces
> >> (should be at least a few)
> >
> > [drm] Initialized drm 1.0.0 20040925
> > PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device
Hi Michal,
(II) RADEON(0): [drm] DRM interface version 1.2
(II) RADEON(0): [drm] created "radeon" driver at busid "pci::01:00.0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xc2bfc000
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) bt
No stac
Hi,
On Tuesday 09 of August 2005 18:04, Vladimir Dergachev wrote:
> > Version of my kernel is gentoo-2.6.12-r7, which is based on 2.6.12.3
> > (exact list of applied patches is here:
> > http://dev.gentoo.org/~dsd/genpatches/trunk/2.6.12/ )
> > I am attaching my kernel configuration.
> > I could b
On Tue, 9 Aug 2005, [iso-8859-2] Micha³ Pytasz wrote:
Hi,
On Tuesday 09 of August 2005 18:04, Vladimir Dergachev wrote:
Version of my kernel is gentoo-2.6.12-r7, which is based on 2.6.12.3
(exact list of applied patches is here:
http://dev.gentoo.org/~dsd/genpatches/trunk/2.6.12/ )
I am atta
Hi, thanks for Your prompt reply
I (just) built and tested cvs xorg, results are below:
On Monday 08 of August 2005 00:01, Vladimir Dergachev wrote:
> Hi Michal,
>
> The first thing to would be to separate Mesa driver issues from drm
> issues.
>
> Could you do the following:
>
> *
module loads fine, e-mail us any kernel messages it produces
(should be at least a few)
[drm] Initialized drm 1.0.0 20040925
PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :01:00.0
[drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI Technologies In
On Mon, 8 Aug 2005, [iso-8859-2] Micha? Pytasz wrote:
* get DRM from DRI CVS (i.e. freedesktop CVS) and check that the
module loads fine, e-mail us any kernel messages it produces
(should be at least a few)
[drm] Initialized drm 1.0.0 20040925
PCI: Unable to reser
15 matches
Mail list logo
