RE: Forcing i686, ignore Athlon for Install of RHES 3.0

["Bryla, Bob J." <Bob Bryla landsend com>]

OK, a bit more detail... since I'm only slightly dangerous with 'make' -- and would just as soon walk over hot coals most days --

When I do an 'insmod' (either auto at startup or manually in a terminal window) the module in question
DOES NOT load, because several symbols are undefined, and don't match symbols in the kernel, and does not load. Mostly networking symbols.

The developer of the .o says that it's because of Athlon recognition in the kernel... and says I should build an i686 kernel.

SOOOO... maybe it IS as easy as telling the boot loader that I'm an i686? Then the right kernel symbols will be available when the .o tries to load??

BB


-----Original Message-----
From: redhat-install-list-admin redhat com
[mailto:redhat-install-list-admin redhat com]On Behalf Of Rick Stevens
Sent: Friday, December 05, 2003 11:38 AM
To: redhat-install-list redhat com
Subject: Re: Forcing i686, ignore Athlon for Install of RHES 3.0


Bryla, Bob J. wrote:
> Because some mods I'm using aren't Athlon aware, I need to TURN OFF the 
> Athlon recognition at either install time, or boot time -- just plain 
> old i686.
>  
> I've tried rebuilding the kernel, using RH's instructions in the ref 
> guide, but I still get kernel panics, and I'm still not sure if I've 
> really turned off Athlon support!
>  
> But I don't think that just setting a switch at boot time will help, 
> because the libs are still on the system and when I try to do 'insmod', 
> it will still see the kernel parameters related to Athlon that conflict 
> with the .o I'm using.

There are no Athlon-specific libraries in Linux.  There are only some
differences in glibc and openssl between i386 and i686.

> It's not obvious from the installer dialogue to tell the installer not 
> to include any Athlon libs, only i686 libs...

The only thing that is Athlon-specific is the kernel itself.  There is
no way to tell the installer to install a different kernel than the one
it probes.  You could install a different kernel after install, but I
really don't think it would make a big difference.

> So unless someone has a magical way to get my 'make' to work, I'd just 
> as soon do a re-install and somehow make the installer unaware of Athlon 
> XP...

Since there is no was we can debug your Makefile without seeing it,
you'll need to publish it.  If you're building an application from
source and you claim that the app panics the kernel (which should NOT
happen unless the app goes into kernel-land and screws with things), you
really contact the program's maintainers and ask them to fix it.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens vitalstream com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-         The Navy's a bunch of wimps!  MY job's an adventure!       -
----------------------------------------------------------------------


_______________________________________________
Redhat-install-list mailing list
Redhat-install-list redhat com
https://www.redhat.com/mailman/listinfo/redhat-install-list
To Unsubscribe Go To ABOVE URL or send a message to:
redhat-install-list-request redhat com
Subject: unsubscribe