SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyway, installed slack 9.1, updated kernel to 2.6.4, works nice, but with couple of issues... so far.
modprobe: FATAL: Module via_agp already in kernel.
modprobe: FATAL: Module ne2k_pci already in kernel.
and it repeats... dunno, 6-7 times! annoying, slows down booting a bit, confuzing
and another thing... ctrl+alt+F2-6 dont give me text consoles?! just blank screens... ideas?
Probably one of init scripts tries to load these packets and expects them to be compiled as modules, but you inserted them directly into kernel. You have to compile them as modules or add to hotplug "black list" (or comment in rc.modules, if you have uncommented them) to get rid of error statements. Nevertheless, it shouldn't harm you in any way.
well, i blacklisted it, but still get errors. oh and i also blacklisted ipv6 that i dont need, but it still gets loaded. like blacklisting it had no effect.
modules are not mentioned in rc.modules.
i have both blacklist and blacklist.new. tried blacklisting it in both, with no effect.
So the best you can do is compile your kernel again, marking suitable parts as modules. Or modify init scripts (it is rather risky) to not try to load these parts, as they are already included in kernel.
From my experience it is simpler to mark as many parts as possible as modules, because init scripts are made for stock kernels, which are always prepared in "modular" way.
Originally posted by Waldi Sorry, but "kernel-modules-2.4.25-i486-2" are modules for 2.4.25 kernel and for sure cannot be used with 2.6.x series.
i am using 2.6.4 with kernel-modules-2.4.25-i486-2+ modules for 2.4.25 and they are working fine. FYI, before this i am using 2.6.4 with kernel-modules+module-init-tools for 2.4.X series and giving a lot of module error. the problems solve after i install those packages.
Nazmin, I think you have both kernels installed, than booting with kernel 2.4.25 you use modules for 2.4.25 (have a look at /lib/modules), but when booting with 2.6.x, you must use modules compiled with 2.6.x kernel.
anyway, solved my problem, by simply upgrading only module-init-tools-3.0-i486-1.tgz. worked like a charm.
to quote myself...
> modprobe: FATAL: Module via_agp already in kernel.
error gone. booting faster. me happy!
> modprobe: FATAL: Module ne2k_pci already in kernel.
actually, i changed this network card (rtl 8029as based) since it wasnt really working, in win2000, slackware or knoppix
>and it repeats... dunno, 6-7 times! annoying, slows down booting a bit, confuzing
gooone. goood. mmmm.
>and another thing... ctrl+alt+F2-6 dont give me text consoles?! just blank screens... ideas?
solved. with minor irritation... no blinking cursor, working only at console 1. but i guess thats another story...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.