Maxime Henrion wrote: > Franz Klammer wrote: > >>Rossam Souza da Silva wrote: >> >>>I have the same problem with VMWare3 kernel modules... >>>no one is loaded, with error messages about symbols. >>> >>>Rossam. >>> >>>------------------------------------------------------ >>>"Das Leben auf Erden ist ein gemeiner Krieg. >>>Wir spielen, wir k?mpfen, wir setzen alles auf Sieg." >>> >>>Megaherz >>>------------------------------------------------------ >>> >>>On Tue, 3 Aug 2004, Toxa wrote: >>> >>> >>>>today kernel biuld, when trying to load radeon.ko for my ATI >>>>Mobility M6: >>>> >>>># kldload radeon.ko: >>>> >>>>link_elf: symbol mem_range_attr_set undefined >>>>kldload: can't load radeon.ko: No such file or directory >> >>same here with matrox mga.ko. after i compiled the >>devices agp, mem, null and io into the kernel it loads normaly. > > > Can you try to remove mem from your kernel config and try this patch? > The DRM drivers are missing a dependency to mem(4) since mem(4) was > made a kernel module. The DRM drivers need mem(4) because they use > mem_range_attr_set(). With this patch, you should be able to load > your DRM driver without errors, even if mem(4) isn't compiled in the > kernel. You must of course have it as a module though. > was faster than expected :-) the patch works! i removed the devices mem and mgadrm vom kernel config and build the new kernel with -DNOCLEAN. hopefully this was correct enough for testing. franz. > Cheers, > Maxime >Received on Wed Aug 04 2004 - 14:14:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:04 UTC