Just moving the module to the correct dir then module folder will allow you to run it. This will break your dpkg entries for the fglrx module though. Durring my install I had to mess around with different variations of the kernel naming scheme to get it to install into the right folder via dpkg. Look at the folder that dpkg put it in and the folder that it should be in, the difference should tell you how you need to remake your deb. -John On 7/28/05, Kalle Westerman <thekalle at gmail dot com> wrote:
Ooook, I checked the lib/modules/ and found the fglrx.ko in the wrong #kernel version# folder(not the one I got when typing uname -r). I'm not quite sure bout this but I suppose I've must've made a mistake somewhere when installing the module. Any ideas on where I should troubleshoot? On 7/28/05, John Baab <john dot baab at gmail dot com> wrote:Check your /lib/modules/ dir. I have had problems with the kernel naming convention before where my deb package installed to a different location than where my kernel modules were living. The module should be living under /lib/modules/#kernel version#/misc/. If all else fails: find / -name fglrx.ko and see where the module found its way to. -John On 7/28/05, Kalle Westerman <thekalle at gmail dot com> wrote:On 7/25/05, Flavio Stanchina <flavio at stanchina dot net> wrote:Kalle Westerman wrote: Sorry for the late answer, been busy.I'm just glad someone helps :)I managed to get the kernel module installed [...] [...] [drm] failed to load kernel module "fglrx" (II) fglrx(0): [drm] drmOpen failed (EE) fglrx(0): DRIScreenInit failed! (WW) fglrx(0): *********************************************** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available * (WW) fglrx(0): ********************************************* *As the log says: "maybe driver kernel module missing or bad". If the module is actually installed, this means that it couldn't be loaded. Shut down X, or even better reboot your system into single user mode to make sure that X was never loaded. Then go to a text console and type modprobe fglrx and report what it says.modprobe: Can't locate fglrx. I suppose that means there's something I didn't do right and you have a hunch what part I should redo? (Was so long since I first tried installing so I can't really relate)-- Ciao, Flavio