Go to /etc and look at lilo.conf and see what it is using for a boot
image. Then go to /boot and examine things there. IE it is quite
common in redhat for lilo and "make" to not be on the same page ine the
book, so that make builds a system image and names it one thing, and then
running lilo continues to boot the old system image. Which means your
shiney new SMP=1 kernel never gets booted. Make your lilo.conf boot
/boot/vmlinuz and I'll bet the problem gets solved. Everytime we install
a new linux box here I get burned by this myself...
Robert Hyatt Computer and Information Sciences
[EMAIL PROTECTED] University of Alabama at Birmingham
(205) 934-2213 115A Campbell Hall, UAB Station
(205) 934-5473 FAX Birmingham, AL 35294-1170
On Thu, 21 Jan 1999, Peter Rivera wrote:
> I just recently purchased the tyan tiger 100
> i have 2 350mhz PII's
> 128m pc 100
> 2 cdroms
> 8.4 gig hd
> matrox mill II
>
> after installing red hat 5.2
> I immedialy cd /usr/src/linux
> and uncomment # SMP = 1
> then exit save and try make modules
> but it tells me that I have two first make my kernal with modules support
> so I then make xconfig
> then i make modules
> and lastly make modules_install
> reboot
> and my /proc/cpuinfo reports only one processor
>
> please help i totally beat
>
> Im sure i even enabled rtc support
>
> please help!!!
>
>
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
