On Tue, Jul 20, 1999 at 04:43:45PM -0700, Anthony Ewell wrote:
> Hi Gyepi,
>
> Never checked the logs. Would it be /var/log/mesasges by any chance?
Most likely, unless you have changed the settings in /etc/syslog.conf
just do
egrep 'kernel|resolve' /var/log/messages
>
> Also, I compiled everything into the kernel. I have never been
> able to figure out why I can not get modules to ever work. I wrote
What happens when you try and use modules?
> myself a note on how to compile kernels. Would you mind looking it over
> to see if you see my error?
>
> Many thanks,
> --Tony
> [EMAIL PROTECTED]
>
>
> Tony note on compiling a kernel:
>
>
> 1) login as root
If you (as a user) have proper permissions in /usr/src, there's no need
to become root at this point.
>
> 2) cd /usr/src/linux
>
> 3) startx
>
> 4) Note: Red Hat 5.2 and lower: If you are compiling an SMP (multiple processors)
>kernel,
> edit "Makefile" and set SMP=1 (note that "1" stands for true not the number of
>processors)
>
> 5) make xconfig
> Make desired changes
>
This section probably requires some more notes. you have to know what
kinds of changes to make...
> Red Hat 6.0 and higher: for SMP support is enabled in "Processor Type and Features".
> You
> also must turn off APM support in "General" AND enable "Advanced Real Time Support"
> in Character Devices
>
> 6) make dep; make clean
>
> 7) "make zImage" or make "bzImage" if the kernel is large
>
> 8) make modules
>
> Then rename the old modules direcory, example:
> mv /lib/modules/2.2.5-15 /lib/modules/2.2.5-15-old
See my notes on adding to the makefile. You could automate this process
too.
>
> make modules_install
>
> 9) cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz.smp
> or
> cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz.smp
>
> Note: change vmlinuz.smp's name as needed. NEVER overwrite the
> original kernel.
>
> 10) edit /etc/lilo.conf as needed. Example:
>
> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> default=linux.smp
> #default=linux
> prompt
> timeout=150
> image=/boot/vmlinuz.smp
> label=linux.smp
> image=/boot/vmlinuz-2.0.32
> label=linux
> root=/dev/sda3
> initrd=/boot/initrd-2.0.32.img
> read-only
> other=/dev/sda1
> label=dos
> table=/dev/sda
>
You can combine steps 9 and 10 with the command make zlilo which
installs the kernel in the correct location ( edit INSTALL_PATH in the
top level Makefile ). Also, you don't need to edit lilo.conf every time
you build a new kernel. I have at least 3 entries in lilo.conf: the
kernel I just built (vmlinuz), the kernel I am replacing (install will
rename it to vmlinuz.old) and a standby kernel, I call mine
vmlinuz.boot. As long as the names in lilo are consistent with names of
your kernel, you rarely have to edit lilo.conf
> 11) fix initrd image
> run the following command to creat a new initrd in the boot
> directory. Make sure that the lilo.conf entry points to it.
> /sbin/mkinitrd /boot/newinitrd-image 2.2.5-15
> Where newinitrd-image is the name of the image in lilo.conf
> and 2.2.5-15 is the current version of the modules you are
> using (see "ls -alg /lib/modules")
>
> 12) lilo
See notes above. Since you need to run 11 before this, just add a
dependency line to the make file to fix initrd <image> after the kernel
is built. Add it just before lilo is run.
/usr/src/linux/arch/i386/boot/Makefile
> Fix any error that pop up with 10 & 11
>
> 13) shutdown -r now
>
>
>
> Gyepi SAM wrote:
>
> > Hi Tony,
> >
> > Did you check the kernel logs after you restarted the machine?
> > There should be something there.
> > Since you mention unresolved symbols, grep for the word 'resolve' in the
> > kernel logs. Also, when you built your kernel, did you include all the
> > required modules, and did you also rebuild the modules?
> >
> > Is the serial driver built as a module or built into the kernel.
> > What happens when you use minicom to dial a busy number?
> >
> > -Gyepi
>
[big snip]
--
Gyepi Sam --+-- Designer/Programmer --+-- Network/System Administrator
[EMAIL PROTECTED] --+-- http://www.praxis-sw.com/gyepi
I use technology in order to hate it more properly. -- Nam June Paik
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
