On Mon, 26 Jul 2004 11:45:59 +0800
Bill Gou <[EMAIL PROTECTED]> wrote:
[snip]
>
> And I also find out why glxinfo fails. I set the LIBGL_DEBUG env variable and run
> glxinfo,
> this is the output:
>
> --
> $ glxinfo
> name of display: :0.0
> libGL error:
> Can't open configuration file
Bill Gou wrote:
> Dave Airlie wrote:
>
>>The intricacies of inter module registration were not at first apparant..
>>the latest fix only does an inter module get/put for the first device in
>>each driver...
>>
>>let me know how this one gets on ..
>>
>
>
> Yes, this one works :) Thanks.
>
> An
Dave Airlie wrote:
> The intricacies of inter module registration were not at first apparant..
> the latest fix only does an inter module get/put for the first device in
> each driver...
>
> let me know how this one gets on ..
>
Yes, this one works :) Thanks.
And I also find out why glxinfo fa
The intricacies of inter module registration were not at first apparant..
the latest fix only does an inter module get/put for the first device in
each driver...
let me know how this one gets on ..
Dave.
>
> Still can't unload it. It seems the problem is that the kernel thought the driver is
>
Dave Airlie wrote:
> again please, found another error in the logic, this is like programming
> by numbers!!! thanks be to God you found these issues before I submitted
> this for the kernel :-)
>
>
Still can't unload it. It seems the problem is that the kernel thought the driver is in
use, and
again please, found another error in the logic, this is like programming
by numbers!!! thanks be to God you found these issues before I submitted
this for the kernel :-)
>
> Still the same. This is the debug msg:
>
> [drm] Debug messages ON
> [drm:drm_probe]
> [drm:i830_stub_register]
> [drm:i830
Dave Airlie wrote:
>>The module couldn't be unloaded. I tried to unload it right after loading, rmmod
>>complains
>> "i830: Device or resource busy". lsmod shows:
>>
>>Module Size Used byTainted: PF
>>i830 66620 1
>>
>
>
> jeez this is annoying me :-),
>
> The module couldn't be unloaded. I tried to unload it right after loading, rmmod
> complains
> "i830: Device or resource busy". lsmod shows:
>
> Module Size Used byTainted: PF
> i830 66620 1
>
jeez this is annoying me :-), there was a bug with my ++
Dave Airlie wrote:
> Okay my final attempt :-) is now checked in...
>
> the last issue that register_chrdev returns a 0 when the fops is the same
> caused your last problem.. hopefully this work..
>
> if you can load/unload this module and see if it works... then I'll add
> the couple of lines to
Okay my final attempt :-) is now checked in...
the last issue that register_chrdev returns a 0 when the fops is the same
caused your last problem.. hopefully this work..
if you can load/unload this module and see if it works... then I'll add
the couple of lines to hopefully avoid using the secon
Dave Airlie wrote:
>
> I've checked in a fix for this load/unload it probably won't help your
> main situation yet but I'd appreciate if you could check it the module
> load and unload, if that works I'll try and fix your specific problem or
> at least rule out the DRM.
>
oops again, seems t
> [drm:i830_ctxbitmap_init] drm_ctxbitmap_init : 0
> [drm] Initialized i830 1.3.2 20021108 on minor 1: Intel Corp. 82852/855GM Integrated
> Graphics Device (#2)
> [drm:drm_cleanup]
> [drm:i830_takedown]
> [drm:i830_stub_unregister] 0
> inter_module_unregister: no entry for 'drm'kernel BUG at modul
Dave Airlie wrote:
> okay there is something wrong with the unload but I can't see it straight
> away, can you insmod the i830 from the snapshot with drm_opts=debug and
> then rmmod it and send me the dmesg output I'd like to track that one
> down... I'll then make the fix I think is needed to stop
Dave Airlie wrote:
>>First I built the i830 module from 2.4.24. Then I tried to unload the
>>current module which was built from dri cvs, the kernel gave me an oops.
>>See attachment for the decoded oops.
>
>
> okay there is something wrong with the unload but I can't see it straight
> away, can
> First I built the i830 module from 2.4.24. Then I tried to unload the
> current module which was built from dri cvs, the kernel gave me an oops.
> See attachment for the decoded oops.
okay there is something wrong with the unload but I can't see it straight
away, can you insmod the i830 from th
Can you load the original i830 module from 2.4.24? and let me know if
direct rendering gets enabled, (send the Xorg.0.log ...) I'm try to narrow
down if this is totally the drm's fault :-)
Dave.
> [drm] Initialized i830 1.3.2 20021108 on minor 0: Intel Corp. 82852/855GM Integrated
> Graphics Dev
Dave Airlie wrote:
> On Thu, 8 Jul 2004, Bill Gou wrote:
>
>
>>Hi there,
>>
>>I'm running X.org 6.7, kernel 2.4.24. Whenever I load the i830 module compiled from
>>dri
>>snapshot, I get a kernel oops. Below is the ksymoops and 'lspci -v'output.
>>
>>
>
>
> I can see the issue, I just have to
On Thu, 8 Jul 2004, Bill Gou wrote:
> Hi there,
>
> I'm running X.org 6.7, kernel 2.4.24. Whenever I load the i830 module compiled from
> dri
> snapshot, I get a kernel oops. Below is the ksymoops and 'lspci -v'output.
>
>
I can see the issue, I just have to think of a clean way to fix it ...
I'
On Thu, 8 Jul 2004 05:34:27 +0100 (IST), Dave Airlie <[EMAIL PROTECTED]> wrote:
> On Thu, 8 Jul 2004, Bill Gou wrote:
>
> > Hi there,
> >
> > I'm running X.org 6.7, kernel 2.4.24. Whenever I load the i830 module compiled
> > from dri
> > snapshot, I get a kernel oops. Below is the ksymoops and 'l
On Thu, 8 Jul 2004, Bill Gou wrote:
> Hi there,
>
> I'm running X.org 6.7, kernel 2.4.24. Whenever I load the i830 module compiled from
> dri
> snapshot, I get a kernel oops. Below is the ksymoops and 'lspci -v'output.
>
that's interesting, looks like something wierd with the two PCI devices
bei
Hi there,
I'm running X.org 6.7, kernel 2.4.24. Whenever I load the i830 module compiled from dri
snapshot, I get a kernel oops. Below is the ksymoops and 'lspci -v'output.
ksymoops 2.4.9 on i686 2.4.24-1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/mo
21 matches
Mail list logo
