Brian and Abu,
Thanks for your replies and for your time for looking into this problem.

On my side, I will try the following:
1. working with an older simics version (2.2.19)
2. switching to fedora
3. trying to compile flexus-3.0.0 as a module under Simics.

I will keep you posted on my progress.
Thanks again,
-Shri

On Fri, Nov 14, 2008 at 12:13 AM, Brian Gold <[email protected]> wrote:
> Hmm... thanks for pointing this out.  Abu, you had previously noted that you
> could use the current version of Flexus with a previous (v2) version of
> Simics.  I will check with Virtutech to see if they have any ideas on what
> causes this error.  We've simply never seen it here.
>
> Thanks,
> Brian
>
>
> On Nov 13, 2008, at 11:32 PM, Abu Saad Papa wrote:
>
>> Hi,
>> I would like to mention that I got the same error in Fedora 8. Just for
>> your information I am the same person who initially got this error and I
>> have already sent a post to this mailing list without much success. But I
>> had used Fedora 8.
>>
>> Regards,
>> Abu Saad Papa
>>
>>> Hi Shri,
>>>
>>> We have tried reproducing this error and cannot.  We downloaded the
>>> latest Simics (3.0.31) and used a personal academic license as you
>>> were.  Following the directions in the Getting Started Guide, we were
>>> unable to reproduce the error and everything worked fine.
>>>
>>> This leaves the OS/distribution as possible problem.  We've never
>>> tried Debian linux 2.6.22; we support SUSE Linux 10.1 and 8.1, and
>>> Fedora Core 5, 7, and 8.
>>>
>>> The shortest term solution for you would be installing one of these
>>> distributions.  We will get to the bottom of this problem, but it may
>>> be up to a month before we can solve this.
>>>
>>> Thanks,
>>> Brian
>>>
>>>
>>> On Nov 8, 2008, at 1:12 PM, Shrirang Yardi wrote:
>>>
>>>> Hello,
>>>> Thanks for your reply.
>>>> Yes - I am able to build, load and run existing simics modules without
>>>> a problem.
>>>>>
>>>>> From some other posts on the Simics forum it seems that loadable
>>>>
>>>> modules need to built within a Simics workspace.
>>>> Is this true for the flexus module also? If so, can you please provide
>>>> any pointers on how this can be done.
>>>>
>>>> Thanks!
>>>> -Shri
>>>>
>>>> -------------
>>>> Hi,
>>>>
>>>> We've had a couple of previous reports of this error, but we were not
>>>> able to reproduce it and I don't think it was resolved.
>>>>
>>>> Can you build and load one of the stock Simics modules, such as
>>>> g_cache (see Simics documentation for info)?
>>>>
>>>> Thanks,
>>>> Brian
>>>> ---------------
>>>>
>>>> On Nov 7, 2008, at 11:59 AM, Shrirang Yardi wrote:
>>>>
>>>>> Hello,
>>>>> I am a first time user of both Flexus and Simics (v3.0.31 on x86
>>>>> Debian linux 2.6.22). I have successfully installed Simics, installed
>>>>> Solaris10 on the abisko target and successfully booted the abisko
>>>>> machine...so I dont think there are any issues with the Simics
>>>>> installation.
>>>>>
>>>>> When I run "./create-initial-flexpoint TraceFlex", Simics complains
>>>>> with the following:
>>>>> --------------
>>>>> Error loading module 'flexus-TraceFlex-v9-iface-gcc':
>>>>> License Error: module not signed.
>>>>> Module 'flexus-TraceFlex-v9-iface-gcc' not loaded.
>>>>> Simics Model Builder license needed to sign modules.
>>>>> ---------------
>>>>>
>>>>> I have the standard academic license file from Simics and it is
>>>>> present in SIMICS_ROOT/licenses path. It has the p_modelbuilder
>>>>> feature included with it.
>>>>>
>>>>> I have followed all the build instructions for Flexus (from the
>>>>> getting-started-guide).
>>>>> libflexus_TraceFlex_v9_iface_gcc.so is present in
>>>>> FLEXUS_ROOT/simulators/TraceFlex/
>>>>> "prepare-test-app" has also run successfully.
>>>>>
>>>>> I found one other post with the same problem, but it didnt seem to be
>>>>> resolved. Replies on the Simics forum ask me to direct this question
>>>>> to the simflex list. Any pointers are really appreciated.
>>>>>
>>>>> Thanks!
>>>>> -Shri
>>>>> _______________________________________________
>>>>> SimFlex mailing list
>>>>> SimFlex at ece.cmu.edu
>>>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>>
>>>> _______________________________________________
>>>> SimFlex mailing list
>>>> [email protected]
>>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>
>>> _______________________________________________
>>> SimFlex mailing list
>>> [email protected]
>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> SimFlex mailing list
>> [email protected]
>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>
> _______________________________________________
> SimFlex mailing list
> [email protected]
> https://sos.ece.cmu.edu/mailman/listinfo/simflex
> SimFlex web page: http://www.ece.cmu.edu/~simflex
>
From bgold at cmu.edu  Fri Nov 14 19:57:54 2008
From: bgold at cmu.edu (Brian Gold)
List-Post: [email protected]
Date: Fri Nov 14 19:58:09 2008
Subject: [Simflex] Simics complains "module not signed" when loading
        flexus module
In-Reply-To: <[email protected]>
References: <[email protected]>
        <[email protected]>
        <[email protected]>
        <[email protected]>
        <[email protected]>
Message-ID: <[email protected]>

OK, I believe we have resolved this issue (Shri has confirmed it  
worked).

We will push out an update to Flexus that resolves this problem in an  
automated way, but in the interim please use the following command  
after building Flexus (e.g., "make TraceFlex").

> $SIMICS/scripts-start-simics  -no-module-cache \
> -P modelbuilder -sign-module \
> $FLEXUS_ROOT/simulators/TraceFlex/libflexus_TraceFlex_v9_iface_gcc.so
>
> substitute your path to simics for $SIMICS and the flexus root  
> directory for
> FLEXUS_ROOT.

If you run into problems please let us know.

Thanks,
Brian


On Nov 14, 2008, at 8:06 AM, Shrirang Yardi wrote:

> Brian and Abu,
> Thanks for your replies and for your time for looking into this  
> problem.
>
> On my side, I will try the following:
> 1. working with an older simics version (2.2.19)
> 2. switching to fedora
> 3. trying to compile flexus-3.0.0 as a module under Simics.
>
> I will keep you posted on my progress.
> Thanks again,
> -Shri
>
> On Fri, Nov 14, 2008 at 12:13 AM, Brian Gold <[email protected]> wrote:
>> Hmm... thanks for pointing this out.  Abu, you had previously noted  
>> that you
>> could use the current version of Flexus with a previous (v2)  
>> version of
>> Simics.  I will check with Virtutech to see if they have any ideas  
>> on what
>> causes this error.  We've simply never seen it here.
>>
>> Thanks,
>> Brian
>>
>>
>> On Nov 13, 2008, at 11:32 PM, Abu Saad Papa wrote:
>>
>>> Hi,
>>> I would like to mention that I got the same error in Fedora 8.  
>>> Just for
>>> your information I am the same person who initially got this error  
>>> and I
>>> have already sent a post to this mailing list without much  
>>> success. But I
>>> had used Fedora 8.
>>>
>>> Regards,
>>> Abu Saad Papa
>>>
>>>> Hi Shri,
>>>>
>>>> We have tried reproducing this error and cannot.  We downloaded the
>>>> latest Simics (3.0.31) and used a personal academic license as you
>>>> were.  Following the directions in the Getting Started Guide, we  
>>>> were
>>>> unable to reproduce the error and everything worked fine.
>>>>
>>>> This leaves the OS/distribution as possible problem.  We've never
>>>> tried Debian linux 2.6.22; we support SUSE Linux 10.1 and 8.1, and
>>>> Fedora Core 5, 7, and 8.
>>>>
>>>> The shortest term solution for you would be installing one of these
>>>> distributions.  We will get to the bottom of this problem, but it  
>>>> may
>>>> be up to a month before we can solve this.
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>>
>>>> On Nov 8, 2008, at 1:12 PM, Shrirang Yardi wrote:
>>>>
>>>>> Hello,
>>>>> Thanks for your reply.
>>>>> Yes - I am able to build, load and run existing simics modules  
>>>>> without
>>>>> a problem.
>>>>>>
>>>>>> From some other posts on the Simics forum it seems that loadable
>>>>>
>>>>> modules need to built within a Simics workspace.
>>>>> Is this true for the flexus module also? If so, can you please  
>>>>> provide
>>>>> any pointers on how this can be done.
>>>>>
>>>>> Thanks!
>>>>> -Shri
>>>>>
>>>>> -------------
>>>>> Hi,
>>>>>
>>>>> We've had a couple of previous reports of this error, but we  
>>>>> were not
>>>>> able to reproduce it and I don't think it was resolved.
>>>>>
>>>>> Can you build and load one of the stock Simics modules, such as
>>>>> g_cache (see Simics documentation for info)?
>>>>>
>>>>> Thanks,
>>>>> Brian
>>>>> ---------------
>>>>>
>>>>> On Nov 7, 2008, at 11:59 AM, Shrirang Yardi wrote:
>>>>>
>>>>>> Hello,
>>>>>> I am a first time user of both Flexus and Simics (v3.0.31 on x86
>>>>>> Debian linux 2.6.22). I have successfully installed Simics,  
>>>>>> installed
>>>>>> Solaris10 on the abisko target and successfully booted the abisko
>>>>>> machine...so I dont think there are any issues with the Simics
>>>>>> installation.
>>>>>>
>>>>>> When I run "./create-initial-flexpoint TraceFlex", Simics  
>>>>>> complains
>>>>>> with the following:
>>>>>> --------------
>>>>>> Error loading module 'flexus-TraceFlex-v9-iface-gcc':
>>>>>> License Error: module not signed.
>>>>>> Module 'flexus-TraceFlex-v9-iface-gcc' not loaded.
>>>>>> Simics Model Builder license needed to sign modules.
>>>>>> ---------------
>>>>>>
>>>>>> I have the standard academic license file from Simics and it is
>>>>>> present in SIMICS_ROOT/licenses path. It has the p_modelbuilder
>>>>>> feature included with it.
>>>>>>
>>>>>> I have followed all the build instructions for Flexus (from the
>>>>>> getting-started-guide).
>>>>>> libflexus_TraceFlex_v9_iface_gcc.so is present in
>>>>>> FLEXUS_ROOT/simulators/TraceFlex/
>>>>>> "prepare-test-app" has also run successfully.
>>>>>>
>>>>>> I found one other post with the same problem, but it didnt seem  
>>>>>> to be
>>>>>> resolved. Replies on the Simics forum ask me to direct this  
>>>>>> question
>>>>>> to the simflex list. Any pointers are really appreciated.
>>>>>>
>>>>>> Thanks!
>>>>>> -Shri
>>>>>> _______________________________________________
>>>>>> SimFlex mailing list
>>>>>> SimFlex at ece.cmu.edu
>>>>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>>>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>>>
>>>>> _______________________________________________
>>>>> SimFlex mailing list
>>>>> [email protected]
>>>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>>
>>>> _______________________________________________
>>>> SimFlex mailing list
>>>> [email protected]
>>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> SimFlex mailing list
>>> [email protected]
>>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>
>> _______________________________________________
>> SimFlex mailing list
>> [email protected]
>> https://sos.ece.cmu.edu/mailman/listinfo/simflex
>> SimFlex web page: http://www.ece.cmu.edu/~simflex
>>
> _______________________________________________
> SimFlex mailing list
> [email protected]
> https://sos.ece.cmu.edu/mailman/listinfo/simflex
> SimFlex web page: http://www.ece.cmu.edu/~simflex

Reply via email to