I've been having trouble shutting down my PC, and I found online that someone said something like 'load the acpi module', and I thought that meant 'depmod acpi' (I think I meant to say 'modprobe acpi', I just got errors, so I didn't think it was important, then, after rebooting, it gave me an error saying, "Cannot find module fglrx"
I tryed typing lsmod, but it just gives me a line saying
"Module Size Used by"
and nothing after it.
Help? Nothing works now...

well if you can get into a terminal at start up (ctrl-F6) then you could try modprobe acpi to get it back and restart.

Define 'nothing works', that's a little vague.

It sounds like X is trying to load fglrx (the proprietary ATI video driver module), but it cannot find it. Try rerunning the ati installer (ctrl-alt-f6 will bring you to a text console).

EDIT:
Which kernel are you using? If you're using the huge kernel, then 'lsmod' may not show you much, as most things are built into the kernel. Also, acpi is built in to the huge kernel I believe, so running 'depmod acpi' would have done nothing (since there is no acpi module)

After reading `man depmod`, it appears you've screwed up your /lib/module/$(uname -r)/ directory (I'm assuming you're using the standard 2.6.21.5-smp kernel, in which case it would be /lib/modules/2.6.21.5-smp). Your modules.dep files (and possibly some map files in the same directory) are probably only pointing to acpi, which prevents other modules from loading, therefore making your system a brick. I think you could fix it by reinstalling the kernel-modules-smp-2.6.21.5_smp-i686-2.tgz package (available here: http://slackware.osuosl.org/slackwar...smp-i686-2.tgz or from your install CD/DVD [on disc 1, in the slackware/a/ directory] or another Slackware mirror). Try `upgradepkg --reinstall kernel-modules-smp-2.6.21.5_smp-i686-2.tgz`.

You'll probably have to reinstall your ATI drivers after reinstalling that package, but I'm not sure. Also, if you're using a non-smp kernel, you should use the kernel-modules-2.6.21.5-i486-2.tgz package instead, available from the same places. If you compiled your own kernel, I would recommend switching back temporarily to the huge kernel and rebuilding your custom kernel. It *may* be possible to compile your kernel again and perform a `make modules_install` in the source directory without switching to the huge kernel first, but I'm not sure.

Good luck.