> > No, the /dev/kmem is there. 2.0.36 boots fine (if I use modutils 2.1.85,
> > otherwise everything screws up there too). Here are the problems:
> > "cannot load module st" (referring to my tape drive)
> > "cannot load module midi" (for the sound card... which I can live
> > without for now)
> > "Error network aliasing not supported in kernel" (I have network and IP
> > aliasing compiled into the kernel)
> > I used linuxconf to add the IP aliases to the box. If I don't manually
> > remove sendmail, httpd and smbd before it boots, it will hang. At which
> > point I can log in and look around. The network card is found and eth0 is
> > there with the correct primary IP bound to it, but you cannot ping anything
> > or go anywhere. And nobody can ping me.
> > This error is the one that concerns me:
> > Feb 3 21:26:54 bert kernel: Error seeking in /dev/kmem
> > Feb 3 21:26:54 bert kernel: Error adding kernel module table entry.
> > Is there something in /etc/lilo.conf that could be throwing it off? My
> > lilo.conf is just the dist RH with an extra line added:
> > boot=/dev/sda
> > map=/boot/map
> > install=/boot/boot.b
> > prompt
> > timeout=50
> > image=/boot/vmlinuz-2.0.36-0.7
> > label=linux
> > root=/dev/sda1
> > initrd=/boot/initrd-2.0.36-0.7.img
> > read-only
> > image=/boot/vmlinuz-2.2.1
> > label=linux22
> > root=/dev/sda1
> > read-only
> > I don't know what to do next... or what to post in here. Here's the
> > checklist:
> > Upgraded modutils to 2.1.121 (no difference)
> > Upgraded net-tools to 1.50.
> > Upgraded ipchains
> > Is there something I'm missing on how to build a kernel for Red Hat? I'm
> > going to try to build a 2.1.x just to see what's up....
> > >yes it seems like your missing /dev/kmem kmem is a kernel device for your
> > >kernels memory managment. I have no idea why that is gone. you could try
> > a
> > >MAKEDEV
> > >in your /dev dir but Im not sure if that would help or hinder. Sorry. It
> > seems
> > >like linux is getting less stable the further we move with it. duno why.
> > I had
> > >a problem one time with my network config just blowing up on me for no
> > reason,
> > >as in I havent touched it for weeks and just let it do its thing. one
> > morning
> > >bam its network config just decided to blow up on me. then I rebooted and
> > it
> > >started saying delaying eth2 initialization. This is starting to bother me
> > a
> > >little.
> > >Later Again,
> > >RayW
> > >> Done it all... in exactly that order. This is the only other error I get
> > on
> > >> boot.
> > >> Feb 3 21:45:24 bert kernel: Error seeking in /dev/kmem
> > >> Feb 3 21:45:24 bert kernel: Error adding kernel module table entry.
> > >> The network claims it's there, but I can't ping anything. Modules that
> > I've
> > >> compiled into the kernel cannot be found as if they were modules that
> > were
> > >> deleted. I had to disable all services (sendmail, named, httpd) just to
> > get
> > >> it to boot cause they cause the system to hang. I get the same error
> > with
> > >> the sound driver and midi modules (cannot load module midi) even though
> > they
> > >> aren't modules... they're compiled into the kernel!
> > >> I'm at a loss...
> > >> >ok, have you compiled the kernel in this order?
> > >> >make menuconfig
> > >> ><configure the kernel>
> > >> >make dep
> > >> >make clean
> > >> >make install
> > >> >make modules
> > >> >make modules_install
> > >> >then edit /etc/lilo.conf
> > >> >and add the kernel vmlinuz for a boot image.
> > >> >do not remove the lilo.conf lines that you are currently booting
> > >> >then do a lilo
> > >> >that should solve a few problems. :)
> > >> >later,
> > >> >RayW
> > >> >> I'm trying to upgrade my 1 month old RH 5.2 system to 2.2.1... and
> > I'm
> > >> >> having no luck! Pretty simple box, P166, 2940U SCSI, 64MB SDRAM, 3Com
> > >> >> 3C509B NIC. Anyway, nothing seems to work right. I've upgraded
> > >> net-tools,
> > >> >> modutils, ipchains, etc. And nothing. I get errors about modules
> > cannot
> > >> be
> > >> >> located, but most of them were things I linked right into the kernel!
> > >> >> Anyway, nothing starts because the network is so funky. I'm using IP
> > >> >> aliasing and it gives me errors about aliasing not supported in the
> > >> kernel
> > >> >> even though I compiled it in (not as a module). Also get errors that
> > the
> > >> >> module st cannot be loaded (even though I compiled it into the
> > kernel).
> > >> >> Anyway, I can't even boot the kernel to figure out what's going on
> > since
> > >> all
> > >> >> the services hang...
> > >> >> Feb 3 20:33:36 bert kernel: Cannot find map file.
> > >> >> Feb 3 20:33:36 bert kernel: Error seeking in /dev/kmem
> > >> >> Feb 3 20:33:36 bert kernel: Error adding kernel module table entry.
> > >> >> I get this error in the boot logs, but I know I've put the System.map
> > >> file
> > >> >> in the correct place... /boot/System.map... right? I've never build a
> > >> >> kernel under RH before... I've build a million kernels under other
> > dists,
> > >> >> and never once had a problem. (I just build 2.2.1 on my Slackware 95
> > >> >> machine that's approaching 4 years old... no problems at all).
> > >> >> Any help with RH kernel building would be very appreciated! Thanks!
> > >> >> --
> > >> >> ------------------------------------------
> I think I see what your problem is, but I'm not sure exactly the steps required
> to fix it as I'm not personally a SCSI user.
> You're booting off a scsi drive, and your 2.0.36 setup uses initrd. What seems
> to be happening is that you don't have access to your hard disk at the point
> where linux is looking into /dev (to get at /dev/kmem). This is hosing up all
> sorts of things. initrd (the Initial RAM Disk) driver is supposed to help get
> around such problems.
> I don't know if you're running scsi as a module, if so don't. Otherwise you
> should set up the initrd stuff for 2.2.1 and that should probably fix your
> Incidentally, I'm running 2.2.1 on a RH 5.1 system with no problems, so you
> should be able to get it working also.
> Hope this helps,
your problem. Have a look at that.