This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Modprobe errors in RH 6.1 (intel, 2.2.12-20) From: Justin Oelgoetz <oelgoetz.1@osu.edu> Date: Sat, 20 Nov 1999 21:24:44 -0500 (EST) I've been getting the following, and haven't been able to figure out how to correct them: Nov 20 19:03:31 router modprobe: can't locate module char-major-108 Nov 20 16:10:49 one modprobe: can't locate module parport_lowlevel with the exception of the parallel port on 'one' everything seems to work fine. I would appreciate any suggestions, along with the resources you used to get them. (I seem to get a modprobe error everytime I upgrade RH versions, or kernels. And would like to be able to fix these w/o harrassing y'all in the future.) === Subject: Re: Modprobe errors in RH 6.1 (intel, 2.2.12-20) From: Joe Brenner <doom@kzsu.Stanford.EDU> Date: Sun, 21 Nov 1999 01:10:24 -0800 Justin Oelgoetz <oelgoetz.1@osu.edu> wrote: > I've been getting the following, and haven't been able to figure out how > to correct them: > Nov 20 16:10:49 one modprobe: can't locate module parport_lowlevel I have the same problem with my RedHat 6.1 box (recently upgraded from RedHat 5.2). I just took a look around using altavista, and I cam across this remark: http://www.torque.net/parport/archive/current/0680.html > I could fix the problem by adding the following lines to > /etc/conf.modules: > alias parport_lowlevel parport_pc > options parport_pc io=0x378,0x278 irq=7,auto This makes some sense to me, because in /lib/modules/2.2.12-20/misc/ there is a parport_pc.o, but no parport_lowlevel.o. I haven't gotten this to work yet, but I wouldn't be surprised if this is a big part of the solution. === Subject: modprobe can't loacate module char-major-108 From: Terry Eck <eck@hex.net> Date: Sat, 20 Nov 1999 17:34:09 -0600 I've installed RH 6.1 using stock kernel and modules. I'm getting a warning in /var/log/messages stating: modprobe: can't locate module char-major-108 tail end of /var/log/messages: .... Nov 20 16:54:26 localhost modprobe: can't locate module char-major-108 Nov 20 16:54:26 localhost pppd[12420]: pppd 2.3.10 started by root, uid 0 Nov 20 16:54:26 localhost pppd[12420]: Using interface ppp0 [SNIP] Nov 20 17:01:54 localhost pppd[12420]: Sent 51622 bytes, received 351687 bytes. Nov 20 17:01:54 localhost pppd[12420]: Exit. I think it is associated with loading ppp module(s) but I don't know if it is a problem. Can anyone help? === Subject: Re: modprobe can't loacate module char-major-108 From: Joe Brenner <doom@kzsu.Stanford.EDU> Date: Sun, 21 Nov 1999 13:36:53 -0800 Terry Eck <eck@hex.net> wrote: > I've installed RH 6.1 using stock kernel and modules. > I'm getting a warning in /var/log/messages stating: > modprobe: can't locate module char-major-108 > tail end of /var/log/messages: > .... > Nov 20 16:54:26 localhost modprobe: can't locate module char-major-108 > Nov 20 16:54:26 localhost pppd[12420]: pppd 2.3.10 started by root, uid 0 > Nov 20 16:54:26 localhost pppd[12420]: Using interface ppp0 > [SNIP] > Nov 20 17:01:54 localhost pppd[12420]: Sent 51622 bytes, received 351687 bytes. > Nov 20 17:01:54 localhost pppd[12420]: Exit. > > I think it is associated with loading ppp module(s) but I > don't know if it is a problem. Can anyone help? Okay, as I said before, I've had similar problems, and now I'm convinced that the solution really is to add the correct "alias" lines to /etc/conf.modules. I definitely needed this line to get my parallel port printer to work: alias parport_lowlevel parport_pc And these lines to get ppp to work: alias tty-ldisc-3 ppp_deflate alias char-major-108 ppp The procedure seems to be, when linux complains it can't find a module, you have to alias that module to some *.o file that actually exists in the /lib/modules/2.2.12-20 tree. Figuring out which module you should be using is the trick. If you can't find any documentation to tell you what to use, you can sometimes get it by making some educated guesses based on the module names. I'm not certain, but it does seem that you need to reboot in order to get changes to the /etc/conf.modules file to take (I haven't had any luck with just doing modprobes or whatever). And it isn't at all clear to me why RedHat hasn't been able to hack some way of doing this automagically (we're up to a *.1 release now... I'd expect a *.0 to be a little rough, but by now I'd really like to have a few less stupid setup problems like this.) Particulars of my system: I'm running RedHat 6.1, upgraded from RedHat 5.2, on an Intel architecture machine. I've also installed the revised RPM for lpr. It's out on the redhat site under security errata. (And buried in the notes about it is a hint about the change you need to make to conf.modules. Nice of them to say something about it, eh?). And here's the current state of my /etc/conf.modules file: alias parport_lowlevel parport_pc options parport_pc io=0x378,0x278 irq=7,auto alias sound sb options opl3 io=0x388 alias midi awe_wave post-install awe_wave /usr/bin/sfxload /etc/midi/GU11-ROM.SF2 options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x300 alias eth0 tulip alias scsi_hostadapter initio alias tty-ldisc-3 ppp_deflate alias char-major-108 ppp (Note: my sound card still isn't working on my system, so I wouldn't assume that "alias sound sb" is the correct line to use.) ===