On Fri, Oct 15, 2004 at 11:40:30AM -0400, Jon Smirl wrote: > On Fri, 15 Oct 2004 15:19:41 +0100, José Fonseca > <[EMAIL PROTECTED]> wrote: > > It doesn't say nothing and I found (partially) why: the dynamic lynking > > is failing, so the call to "drm_init(&pci_driver, pciidlist, &driver)" > > never reaches a single line of code there (no debug message, *nothing*). > > Could it be symbol versioning?
I've diffed my two machines kernel config files and symbol versioning was one of the suspicious differences indeed, but I only managed to get everything working as expected after disabling some of those "kernel hacking" options too. > Things behave weirdly if you have an old drm module loaded and load > the new ones too. > > You should at least get a sign on: > [drm] Initialized drm 1.0.0 20040925 Yes, this message always appeared when loading drm.ko. > That the very first thing the drm module does. > > If you sync from CVS you need to use... > insmod ./drm.ko drm_debug=1 Thanks for your help. This issue is finally closed. Regards, José Fonseca ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
