<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jonny,<br>
Thanks a lot man! <br>
<br>
I managed to install GFS and run it. Actually i used back the
kernel-2.4.21-15.EL for smp. As follow what you said, installed all
kernel-source, kernel-hugemem, kernel-unsupported, kernel-smp and then
recompile from src. Now no more unresolved symbol and able to modprobe
all the modules.<br>
<br>
Need to configure GFS now.<br>
<br>
Thanks again man!<br>
<br>
<br>
Johnny Hughes wrote:<br>
<blockquote cite="mid1090238500.5864.21.camel@Myth.home.local"
type="cite">
<pre wrap="">On Mon, 2004-07-19 at 05:21, chloong wrote:
</pre>
<blockquote type="cite">
<pre wrap="">hi Johnny,
I had tried using your bin, both i386 & i686, but still have the same
problem.
BTW, how could i know what target should i use? i am running on a x86
platform and i compile the kernel myself and i select the cpu type as
386 family with no smp support.
the kernel source i downloaded from rpmfind. The version is
kernel-2.4.21-15.0.3.EL.src.rpm. I used back the kernel config file
provided from this rpm and changed it to no smp support.
</pre>
</blockquote>
<pre wrap=""><!---->OK, did you build a kernel rpm and install it ... if so, what was the
name of the kernel's rpm.
Is this on RHEL or a clone like WBEL/CentOS/TaoLinux?
</pre>
<blockquote type="cite">
<pre wrap="">Everything are fine after reboot using this kernel. Then i compile the
gfs source from your side. The compilation was successful. After
installation, when i do a depmod -a, it still gave me unresolved symbol
for gfs modules....
</pre>
</blockquote>
<pre wrap=""><!---->I installed:
GFS-6.0.0-1.2.i686.rpm
GFS-devel-6.0.0-1.2.i686.rpm
GFS-modules-6.0.0-1.2.i686.rpm
perl-Net-Telnet-3.03-2.noarch.rpm
Then do a:
depmod -a
No errors...
Johnny Hughes
HughesJR.com
</pre>
</blockquote>
<br>
</body>
</html>