Forwarded From: Craig Foster <[EMAIL PROTECTED]>
> For your info the SMP e100 module worked great. I'll now have to check
> my source, header, and development packages I have.
Thanks for the feedback. To share with everyone I'm posting this reply to
devinfo so every
e gets detected as SMP capable when it isn't.
> At least two people have mentioned that they had the same problem with a same
> spec machine (1.6 Ghz P-IV). How does the SMP capability get detected and why
> does this go wrong with this machine?
There is magic in the installer whic
every few seconds:
>
> hda: lost interrupt
>
>
>
> When, as I said before, I select esmith-up it all works.
>
> Anyone knows what is going wrong here?
>
>
> Kees
Thank you every one who replied to this, I have now changed the lilo default
to esmith-up and this works
I seem to have run into a problem I cannot find any information on in the
forums or the mailing list archive:
I am installing SME 5.1 on a new machine (1.6 GHz P-IV) it only contains one
processor, but the machine shows up as multi-processor capable, so in LILO
there are two entries, esmith an
Perfect. I imagine my SME 5.1 upgrade will be alot smoother now that I
don't have to move a bunch of files off the server!!!
Thanks again for all your contributions!!!
- Original Message -
From: "Darrell May" <[EMAIL PROTECTED]>
To: "Steve Bush" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 02, 2001 12:34 AM
Subject: FreeS/WAN 1.91 SMP broken (was Re: FW: [e-smith-devinfo] Samba add
user fragment)
> Please respect list threading ... I'm breaking the reply out of this
thread
> as it is not related to the Samba thread.
&g
t; latest version, so I tried the i586 version. The upgrade worked on a single
> processor SME5, but on an SMP CPU I received this smp kernel error.
> [...]
> ipsec_setup:/lib/modules/2.2.19-7.0.8smp/misc/ipsec.o was compiled for
> kernel version 2.2.19-7.0.8
> ipsec_setup:whi
Not sure what I may be doing wrong, but I updated as per Charlie's advice, and still
no luck.
Is this fixed in 4.1.1? Should I use 4.1.1 anyway?
Thanks
Charles
Has anyone been having problems with the smp kernal for 4.1 or 4.1.1 with the
pptp not working. It looks like it is working for single processes. I am not
able to upgrade from 4.1 to 4.1.1. The question is the ver 4.1.1 have the fix
fo the pptp and smp kernal and if so will a backup of 4.1 and
t;entry for e-smith-up"? Ah, I have a guess, that is "esmith-up",
not "e-smith-up", and that is put there by the RedHat installer as a
fallback. The "up" would stand for uni-processor.
> default (e-smith) caused kernel panic
> e-smith-up worked fin
On Sun, 25 Feb 2001, Charles Chambers wrote:
> Not sure what I may be doing wrong, but I updated as per Charlie's
> advice, and still no luck. Is this fixed in 4.1.1? Should I use 4.1.1
> anyway?
It is fixed in 4.1.1, but the fix is *exactly* the same.
After you install the updated ppp rpm, yo
thanks
---
Mathias Houngbo
[EMAIL PROTECTED]
Salut Orville,
Le mardi 20 mars 2001, à 12:48:06, tu as écris ceci:
OC> YES! My servers as Dual-PII's running E-Smith 4.1.1.
OC> e-smith server and gateway release 4.1.1
OC> Kernel 2.2.16-22smp on a 2-processor i686
OC> login:
OC> Orvi
On Tue, Mar 20, 2001 at 10:01:08AM +, Mathias Houngbo
<[EMAIL PROTECTED]> wrote:
> I want to know if e-smith gateway and server manage two pr more processor ?
Yes. If your hardware is supported for SMP under RedHat 7.0, it will
work with SMP on e-smith. You need to install 4.
YES! My servers as Dual-PII's running E-Smith 4.1.1.
e-smith server and gateway release 4.1.1
Kernel 2.2.16-22smp on a 2-processor i686
login:
Orville Carter
NYC
- Original Message -
From: "Mathias Houngbo"
<[EMAIL PROTECTED]>
> I want to know if e-smith gateway and server manage two
I want to know if e-smith gateway and server manage two pr more processor ?
---
Mathias Houngbo
[EMAIL PROTECTED]
15 matches
Mail list logo