Hi Gyepi,
Never checked the logs. Would it be /var/log/mesasges by any chance?
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
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
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
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
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
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
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
>
> On Tue, Jul 20, 1999 at 03:52:14PM -0700, Anthony Ewell wrote:
> > Hi Gyepi,
> >
> > Unfortunately, most of the time I am in Xwindows (gnome or another level)
> > and I all it does is freeze up Dead keyboard and mouse. The network freezes
> > too - no telnet'ing in to kill pid's. ping is dead too.
> >
> > The one time I was not, I got some stuff about something being unresolved
> > and "Ieeee" and kernel panic. I did not have the foresight to write everything
>down.
> >
> > Changing the phone number to the modem's number to generate a guaranteed
> > busy signal is a good idea. I will try it.
> >
> > Thank you so much,
> >
> > --Tony
> > [EMAIL PROTECTED]
> >
> [big snip]
> --
> Gyepi Sam --+-- Designer/Programmer --+-- Network/System Administrator
> [EMAIL PROTECTED] --+-- http://www.praxis-sw.com/gyepi
>
> Those who can, do; those who can't, simulate.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
