"Michel Dänzer" <[EMAIL PROTECTED]> writes:
> > The new log is to be found here :
> > http://fab.rhapsodyk.net/dri/XFree86.0.log
>
> It doesn't work for some people with new iBooks without agpgart. Beware
> that you'll need http://penguinppc.org/~daenzer/DRI/drm-ioremapagp.diff
> (which drm-trunk-
On Die, 2002-12-31 at 00:48, Fabrice Medio wrote:
> "Michel Dänzer" <[EMAIL PROTECTED]> writes:
>
> At least, I've got something new : I compiled drm-modules from
> gatos.sf.net, today's cvs state. I've got exactly the same behavior
> (black screen, X eating 99.99% of CPU), _but_ the X log says
>
"Michel Dänzer" <[EMAIL PROTECTED]> writes:
> What happens here is that the drmSetBusId ioctl, which is definitely
> _inside the kernel_ (in the DRM to be exact), thinks it doesn't have the
> permissions to do what it's supposed to do, even though it's called from
> the X server running as root. T
On Die, 2002-12-31 at 00:07, Jack Howarth wrote:
> Considering that the drm code has changed enough in the past
> that we have two versions in Linux 2.4 (legacy XFree86 4.0 and
> XFree86 4.1), why wouldn't the drm code fork yet again at some
> point in the XFree86 cvs? If one were running Lin
Michel,
Considering that the drm code has changed enough in the past
that we have two versions in Linux 2.4 (legacy XFree86 4.0 and
XFree86 4.1), why wouldn't the drm code fork yet again at some
point in the XFree86 cvs? If one were running Linux 2.5 and it
was sync'd to the drm code in XFree8
On Mon, 2002-12-30 at 23:45, Jack Howarth wrote:
>Well what does Linux 2.5 currently have for building the DRM
> support?
Pretty much the same as my drm-trunk-module-src packages, but what does
that have to do with anything?
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc
Michel,
Well what does Linux 2.5 currently have for building the DRM
support? I know 2.4 has a XFree86 4.0 legacy and a 4.1 drm (which
seems to be compatibe with XFree86 4.2). I would assume at
some point (XFree86 4.3?) there would be the need for a new
version of drm support in the kernel and
On Mon, 2002-12-30 at 16:26, Jack Howarth wrote:
>I would be surprised if it was a gcc mismatch. I run the debian
> sid xfree86 4.2.1 packages built with gcc 2.95.4 against benh kernels
> built with gcc 3.2 all the time and have never had a problem with
> dri loading, This is using agpgart und
On Mon, 30 Dec 2002, Vincent Bernat wrote:
I'm forwarding this to all. I hope I don't piss
anyone off. It's a small file anyway. Hope you
can read it.
> OoO Vers la fin de l'après-midi du lundi 30 décembre 2002, vers 16:40,
> Fred Heitkamp <[EMAIL PROTECTED]> disait:
>
> > I don't know if I'm
OoO Vers la fin de l'après-midi du lundi 30 décembre 2002, vers 16:40,
Fred Heitkamp <[EMAIL PROTECTED]> disait:
> I don't know if I'm helping here. I had the same problem with
> the kernel module not being compatible with xfree86. I downloaded
> the CVS sources from gatos.sf.net and compiled an
On 30 Dec 2002, Michel [ISO-8859-1] Dänzer wrote:
> On Mon, 2002-12-30 at 11:20, Fabrice Medio wrote:
> > Michel Dänzer <[EMAIL PROTECTED]> writes:
> >
> > > > Michel : shall I recompile your tree with the -g option, and put gdb
> > > > to work ?
> > >
> > > What tree? This isn't an X server probl
Fabrice,
I would be surprised if it was a gcc mismatch. I run the debian
sid xfree86 4.2.1 packages built with gcc 2.95.4 against benh kernels
built with gcc 3.2 all the time and have never had a problem with
dri loading, This is using agpgart under debian ppc. Are you sure you
haven't left bits
Michel Dänzer <[EMAIL PROTECTED]> writes:
> > Would there be anything strange in the config I sent you ?
>
> Not really, I suppose the problem also occurs with a saner mode than
> 0777?
Correct.
> I'll say once again though that the most likely cause is some mismatch
> between the kernel and the
On Mon, 2002-12-30 at 11:20, Fabrice Medio wrote:
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > Michel : shall I recompile your tree with the -g option, and put gdb
> > > to work ?
> >
> > What tree? This isn't an X server problem, you'd have to debug your
> > kernel and DRM if anything.
>
Michel Dänzer <[EMAIL PROTECTED]> writes:
> > Michel : shall I recompile your tree with the -g option, and put gdb
> > to work ?
>
> What tree? This isn't an X server problem, you'd have to debug your
> kernel and DRM if anything.
Uh oh... I'm afraid I won't be of any help for this :)
Would ther
On Mon, 2002-12-30 at 01:31, Fabrice Medio wrote:
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > > > note the funny line 440 :
> > > > > (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:0:16:0), Permission
> > > > > denied
> > > >
> > > > This usually happens when the DRM wasn't built with t
Michel Dänzer <[EMAIL PROTECTED]> writes:
> > > > note the funny line 440 :
> > > > (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:0:16:0), Permission
> > > > denied
> > >
> > > This usually happens when the DRM wasn't built with the same compiler as
> > > the kernel, e.g. one with gcc 2.x and
On Son, 2002-12-29 at 20:18, florian wrote:
>
> > > > (EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version
> > > > mismatch.
> > > > [dri] radeon.o kernel module version is 1.1.1 but version 1.2.1 or
> > > > newer is needed.
> > > > [dri] Disabling DRI.
> >
> > The version tell
arg. sorry, just saw that email..
> > > (EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version
> > > mismatch.
> > > [dri] radeon.o kernel module version is 1.1.1 but version 1.2.1 or newer
> > > is needed.
> > > [dri] Disabling DRI.
>
> The version tells another story, you did
On Son, 2002-12-29 at 19:54, Michel Dänzer wrote:
> On Son, 2002-12-29 at 19:39, florian wrote:
> >
> > for some reason i also have problems to get DRI working
> > on debian sid, with the 2.4.20-ben1 and the latest
> > x-windows-dri packages..
> ^
> What's that? ;)
hehe =)
>
> > (
On Son, 2002-12-29 at 19:58, florian wrote:
> forgot something: im 100% sure that its loading
> the radeon.o from the dri package and not from the
> kernel. i copied the file from the dri build over
> the kernel one..
[...]
> > (EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version
On Son, 2002-12-29 at 19:39, florian wrote:
>
> for some reason i also have problems to get DRI working
> on debian sid, with the 2.4.20-ben1 and the latest
> x-windows-dri packages..
^
What's that? ;)
> (EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version
> misma
forgot something: im 100% sure that its loading
the radeon.o from the dri package and not from the
kernel. i copied the file from the dri build over
the kernel one..
On Son, 2002-12-29 at 19:39, florian wrote:
> hi!
>
> for some reason i also have problems to get DRI working
> on debian sid,
hi!
for some reason i also have problems to get DRI working
on debian sid, with the 2.4.20-ben1 and the latest
x-windows-dri packages..
when i book up x everythingn works okay, just DRI
doesnt seem to be enabled.
when i check the XFree86 logfile i see this:
(II) RADEON(0): [drm] loaded kernel m
On Son, 2002-12-29 at 17:42, Fabrice Medio wrote:
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > On Son, 2002-12-29 at 16:23, Fabrice Medio wrote:
> >>
> >> X logfile :
> >> http://fab.rhapsodyk.net/dri/XFree86.0.log
> >>
> >> note the funny line 440 :
> >> (II) RADEON(0): [drm] drmSetBusid f
Michel Dänzer <[EMAIL PROTECTED]> writes:
> On Son, 2002-12-29 at 16:23, Fabrice Medio wrote:
>>
>> X logfile :
>> http://fab.rhapsodyk.net/dri/XFree86.0.log
>>
>> note the funny line 440 :
>> (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:0:16:0), Permission denied
>
> This usually happens wh
On Son, 2002-12-29 at 16:23, Fabrice Medio wrote:
>
> X logfile :
> http://fab.rhapsodyk.net/dri/XFree86.0.log
>
> note the funny line 440 :
> (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:0:16:0), Permission denied
This usually happens when the DRM wasn't built with the same compiler as
the
Michel Dänzer <[EMAIL PROTECTED]> writes:
[snip]
> > When X is launched, the screen just stays blank (i.e, black). When I
> > ssh the iBook from another machine, 'top' says X takes 99.9% of CPU
> > cycles. Killing -9 the 'X' process halts it, but the screen doesn't
> > return to console state, an
On Don, 2002-12-26 at 02:26, Fabrice Medio wrote:
>
> I have an very recent iBook2 here, with the following installed :
> - 2.4.20 + latest benh kernel patches ;
> - latest drm-trunk modules ;
> - latest xserver from drm trunk.
>
> /proc/pci says the video card is :
> Bus 0, device 16, func
Hello !
I have an very recent iBook2 here, with the following installed :
- 2.4.20 + latest benh kernel patches ;
- latest drm-trunk modules ;
- latest xserver from drm trunk.
/proc/pci says the video card is :
Bus 0, device 16, function 0:
VGA compatible controller: ATI Technologies I
30 matches
Mail list logo
