by jik- » Tue, 16 Mar 1999 04:00:00
Always leave your old kernel at like /vmlinuz.old and add anotherQuote:> BIOS hardware startup. At this point the only thing I could do was boot
> from the distribution CD and copy my original 2.0.35 kernel back in (backup
> copy always saves you in cases like this).
by MokeKahun » Wed, 17 Mar 1999 04:00:00
I've read or at least think I've read (and understood) all the HOWTOs on
multiple ethernet cards, configuring, compiling, firewalling, and ip
masquerading.
Once I installed Slackware 3.6 from scratch, on a freshly formatted hard
disk partition, I proceeded to configure all my .conf and rc.<whatever>
files to establish my Linux box as a firewall between my local network and
my ISP. That all worked fine including recompiling my RoadRunner dhcp
client daemon and login daemon programs.
After confirming everything worked fine using ifconfig, netstat, and
ipfwadm, I proceeded to 'make mrproper', 'make config', 'make dep ; make
clean', and finally 'make modules' and 'make modules_install'. When I
rebooted, however, it just went into a loop starting lilo then going back to
BIOS hardware startup. At this point the only thing I could do was boot
from the distribution CD and copy my original 2.0.35 kernel back in (backup
copy always saves you in cases like this).
For the most part I left all kernel selection default except for those
mentioned in the ip masquerading HOWTO (latest is 7 Feb 99 by Ambrose Au).
Any ideas what I missed? patches? compiler version? header files? ????
Help...
by MokeKahun » Wed, 17 Mar 1999 04:00:00
>Always leave your old kernel at like /vmlinuz.old and add another
>section to lilo.conf for the old kernel, then rerun lilo (of
>course)....then you always have your good copy in case the new one
>doesn't boot.
by Larry Min » Wed, 17 Mar 1999 04:00:00
When did you actually build the kernel. None of the make steps above compile
the kernel. You need to run make zImage, or make zlilo, etc in order to
build a kernel.
Larry
by Christophe » Sat, 20 Mar 1999 04:00:00
> Larry,
> Sorry did that step too but I forgot to mention it. That was the last
> step, updated my lilo.conf, then rebooted. After that point it just looped
> in a reboot or just hung.
> This happened when I had 3.5 as well.
Did you run lilo?
Chris
1. kerneld/module problems with Slackware 3.6 and kernel 2.0.36
I recently installed Linux Slackware 3.6. I've previously used
Slackware 3.2. I noticed after installation, and after configuring my
first kernel that loadable modules weren't working. After going
through my /etc/rc.d scripts, I noticed that kerneld was commented out
in both rc.S and rc.modules. I reviewed the rc.d scripts on a
Slackware 3.2 machine, and noticed that kerneld was commented out in
rc.modules, but was active in rc.S.
After some reading (HOW-Tos and README files in modules-2.0.0, I
uncommented the kerneld line in my rc.S file and rebooted my machine.
Everything works fine with the exception of mounting my ms-dos drive
during startup - instead I get a 'mount: /dev/hda1 has wrong device
number ot fs type vfat not supported' error message. I realize that
this occurs when rc.S tries to execute the 'mount -avt nonfs' command
to mount all of the file systems in my fstab directory, What I don't
understand is why it's failing to load the vfat module. After this
point in rc.S, rc.modules in loaded, where depmod -a is being called.
After I log in to linux I can execute the 'mount -avt nonfs' command
and everything is fine.
I've run 'make modules' and 'make modules-install' from
/usr/src/linux. I've tried 'depmod -a' and modprobe. One interesting
thing: 'modprobe -c' yields duplicate lines for the majority of items
that I see. Is this a symptom of what's happening?
Why does my new system fail to load the vfat module during start up,
and how can I correct this?
Is there a reason why Slackware no longer uses kerneld in their
default installation rc.d scripts?
Please help me with this issue.
2. HELP- w2k format overlaps linux fs
3. 3c509b not found in slackware 3.6 kernel 2.2.5
4. mounting a fs in two places at once?
5. Netscape 4.07 kills keyboard Slackware 3.6 kernel 2.0.36
6. FS: Cisco 2503 ISDN Router NEW!! at $2,990
7. Can I get a module for IP Forwarding (or do I have to recompile the kernel?)
8. Compiling Kernel 2.0.34 to Kernel 2.2.7
9. Problems recompiling tcl/tk for Sicstus 3.6 on a RH 5.2
10. Recompiled to 2.0.35 now my X will not work at all.
11. Upgrade Xfree86 on Slackware 3.6