Clan x86
Technical (Development, Security, etc.) => Unix / Linux Discussion => Topic started by: Ergot on February 18, 2006, 02:34:31 am
-
At boot I get
lsmod: QM_MODULES: not implemented. I googled it and it said it was an issue with mod-init-utils but I already have that. The other problem is that without the modules I can't mount my FAT drives? Which would help me get the other packages to fix other problems.
For future reference, doing slapt-get --install-set diskset after doing a --upgrade or --dist-upgrade seems like a really good idea. I should read before I do things :P
-
Haha, maybe that's why my slackware install kept dying when I ran slapt-get.
I'd recommend re-installing slackware to the same disk/partition from the CD's. That's what I did when slapt-get broke my computer! :)
-
It appears that the problem does lie with module-init-tools. I currently have 3.1; I tried 3.2.2 and made some progress. The problem I had was with 'make install' because it would produce an error saying 'too many symbolic links' or something like that. I manually copied over lsmod to /sbin/ and it fixed the whole lsmod error. However when I moved the rest of the files to /sbin/, I would get a new error saying either insmod or modprobe does not recognize the -c variable or something like that. I forgot to do ./generate-modprobe.conf so I hope that will fix it. Currently tired right now, I'll tell you how it goes tomorrow or when I have time.
-
Making progress! System now boots without any crippling errors! This might go away next time I boot, but I hope not. I went through a lot of trouble. X won't start though :(! Maybe it's just Fluxbox... I should have tried a different WM, but oh well. Hopefully, there will be an updated stable Slackware soon.
-
HELLO FROM LINUX! I think I gave enough details above about what I did, so if anyone else has this problem they can reference it. Really annoying to fix though :\.