"Mikkel L. Ellertson" wrote:
> On Sat, 7 Oct 2000, Bret Hughes wrote:
> [SNIP]
> >
> > Thanks Mikkel, That appears to be the fix. As I have only done this a few
> > times, I have another question. I selected PPro as the cpu type in
> > menuconfig but I notice that in all the lines I have seen scroll by, the
> > -m486 flag is set.. Is this correct?
> >
> >
> >
> > There are two pentium II 333 MHz processors in the machine
> >
> > Any help appreciated.
> >
> > Bret
> >
> Hi Bret,
> Yes, the -m486 flag is the correct one. For this flag, when
> compiling the kernel, the only choices are -m386 and -m486. I am not sure
> of all the details, but I think the flags handle how data structures are
> alligned. The 486 allignment will sometimes wast space, but allows faster
> accessing. There is some other optimizing done for the newer processors,
> but this is done using other flags, as well as some stuff done in the
> source code. I am not sure if it still applies, but I know with the 2.0.x
> kernels, you also had to make sure you used the correct version of the
> compiler because the latest version would break some things...
>
> Mikkel
> --
Thanks to everyone for the info. Everything appeared to go well with the
compile.
The problem is now that the system hangs at "Finding Module Dependencies"
during booting the new kernel. I did make modules and make module_install.
The new modules were built and put into /lib/modules/2.2.16-3 and the kernel is
named vmlinuz-2.2.16-3 with a symlink from vmlinuz to it. Here is lilo.conf
[bhughes@compaq2 /boot]$ cat /etc/lilo.conf
boot=/dev/ida/c0d0p1
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
image=/boot/vmlinuz-2.2.5-22smp
label=linux-686
root=/dev/ida/c0d0p6
initrd=/boot/initrd-2.2.5-22smp.img
read-only
image=/boot/vmlinuz <-- this is the new entry
label=linux
root=/dev/ida/c0d0p6
read-only
image=/boot/vmlinuz-2.2.5-15
label=linux-up
root=/dev/ida/c0d0p6
initrd=/boot/initrd-2.2.5-15.img
read-only
BTW I compiled the scsi stuff into the kernel so the initrd is not needed,
right? I tried it both ways but I feel that I would not have gotten this far
if the scsi or raid5 stuff was the issue since all drives are mounted ok.
What have I missed? All help appreciated.
Bret
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list