Stas Oskin wrote:
Hi again.
Strange - I restored the hardware.lst, and now it worked.
Good.
I guess it's because I'm mixing AMD and Intel servers, so these
additional modules sometimes required, and sometimes not (even not
wanted, as they stall the installation).
As I said in a previous
Hi.
Will try to do as instructed.
I got another missing module error again - pata_amd. Now I
double-checked that there is no hardware.lst present.
Question is - what can be done in this situation?
Regards,
Stas.
-
This
Hi again.
Strange - I restored the hardware.lst, and now it worked.
I guess it's because I'm mixing AMD and Intel servers, so these
additional modules sometimes required, and sometimes not (even not
wanted, as they stall the installation).
Regards.
2008/5/5, Stas Oskin [EMAIL PROTECTED]:
Hi.
Stas Oskin wrote:
Hi.
In SystemImager 4.1.x the hardware.lst is always re-generated at end of
imaging, so this problem should be already fixed in recent versions
(i.e. 4.1.6).
I guess, time to update to latest unstable :).
Or better time for us to release a new stable version.. :-)
Stas Oskin wrote:
-- Forwarded message --
From: Stas Oskin [EMAIL PROTECTED]
Date: 28/04/2008 20:03
Subject: Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read
superblock CentOS5 and Perc5i
To: [EMAIL PROTECTED]
Hi.
I managed to solve the issue.
Stas,
thanks
Hi.
In SystemImager 4.1.x the hardware.lst is always re-generated at end of
imaging, so this problem should be already fixed in recent versions
(i.e. 4.1.6).
I guess, time to update to latest unstable :).
It's used by systemconfigurator to know which modules must be included
in the
-- Forwarded message --
From: Stas Oskin [EMAIL PROTECTED]
Date: 28/04/2008 20:03
Subject: Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read
superblock CentOS5 and Perc5i
To: [EMAIL PROTECTED]
Hi.
I managed to solve the issue.
The whole point was that I actually made
