A few questions


Recommended Posts

I'm using Slackware 9.1 and I just compiled kernel 2.6.3 but after that I get fatal errors on startup. I think they're due to the fact my old kernel used modules for some stuff but I told the new kernel to just have them built in. So how do I stop it trying to load these modules? Thought it was in /etc/modules.conf but that file is empty?

Unrelated to the new kernel I also have run into a couple of problems. How do I configure the network? I ran netconfig and it asks about servers etc and all I want to do is share files with a win98 machine and access the internet through that machine?

Common enough question but how do you get the scroll wheel on the mouse to work? Tried adding Option "ZAxisMapping" "4 5" into the XF86Config file like someone told me to do but that didn't work..

Thanks

Link to comment
Share on other sites

1) most of your modules are loaded in the rc.module file. you can find it in /etc/rc.d

2)you probably should visit here http://www.linuxquestions.org/ and see if someone has worked it out in the forums. if not you start a new topic. there are many very experienced users there that are very good at helping with your problem.

3) after adding the option you need to change the protocol to "ExplorerPS/2" . with 2.6.3 imps/2 is automatically converted by the kernel to ExplorerPS/2 use which ever one you wish.

hope this helps.

Link to comment
Share on other sites

I still can't get rid of these startup errors so any input would be appreciated..

Here are the errors:

[drm: drm_init] *ERROR* Cannot initialize the agpgart module.

FATAL: snd_pcm_oss module not found

FATAL: snd_mixer_oss not found

FATAL: ide_scsi not found

Link to comment
Share on other sites

most modules in slackware are loaded from the script in /etc/rc.d/rc.modules not modules.conf. Since you are using kernel 2.6.3 the modules or link are located in your /lib/modules/2.6.3,l while in the older kernel they were located in /lib/modules/2.4.22 (or whatever kernel you had). since the rc.modules was not changed and the kernel uses it to load the modules and since you don't have the modules in the newer module directory they won't be loaded. however I do not thing you need them since they are not in your module directory. These errors don't mess anything up, but you can probably get rid of them by deleting or putting a # sign in front of these modules if they are listed as being loaded in the rc.modules file.

What I would do is try to get everything to work without worrying about the errors from these modules. after you get it all to work, then if you want to you can go back and edit your rc.modules file.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.