Figuring I messed something up I reinstalled SuSE 6.1 and then pulled
2.2.9. I configured the kernel, and edited arch/i386/Makefile and changed
the -m486 to -mpentiumpro in the 686 section. I compiled the new kernel
and modules, installed them, and booted. Everything came up just fine.
This tells me I corrupted something seriously in my previous attempt.
Rather than just letting things go, I really want to understand WHAT
happened so if I am presented with it in the future, I can cut right to
the chase. Is anyone familiar with the neighbour table problem I reported
in my previous message. That's the only clue.
Secondly, and probably most importantly at this point, what are the
possible ramifications of changing the -m486 to -mpentiumpro. I figure it
was left at -m486 intentionally, so there must have been a logical
reason.
Thanks,
Greg
On Sat, 22 May 1999, greg wrote:
> I'm having a problem with a Tyan Tahoe II motherboard with dual PPro 200
> CPUs (on riser cards) and 128 meg RAM.
[snip]
> The kernel builds properly, though I did have to use bzImage instead of
> zImage, but that's not unusual. Then I build all the modules I wanted and
> install them.
[snip]
> Eventually I pulled 2.2.9 and tried it. I generally build a minimal
> kernel with what I need compiled in the kernel, and the few things I
> think I might want later compiled as modules. I don't go through and make
> everything possible as modules. Only what I need. I figure it is better
> to err on the side of caution.
>
> When I got the same problems with 2.2.5 and 2.2.9 I figure it is
> something I'm doing.
>
> I think I'm missing something here. Something I need to have compiled
> in. And knowing me, it is something really stupid and simple.
[snip]
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
