Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17267 Discussions

Quartus 12.1 issue with modelSim 64bit Linux system

Altera_Forum
Honored Contributor II
1,800 Views

Hi Guys 

 

I have just installed the Quartus 12.1 64-bit Linux on my laptop. I downloaded the modelSim starter version 10.1b that is compatible with the quartus 12.1 from the altera downloads. 

 

I went through all the installation guides to set up modelsim and when i go to run the RTL_simulation i get this error; 

 

Can't launch modelSim-altera simulation software-- make sure the software is properly install and the environment variables LM_LICENSE_FILE or MGLS_LICENSE_FILE are set. 

 

I have noticed that in my directories where i installed the modelsim i don't have a license.dat file.  

 

As far as i was aware from reading and some post the modelsim starter shouldn't need licenses. I need to use this to simulate for my final year project so if any one has any ideas that might help me get over this obstacle i would much appreciate it. 

 

Is this an issue with me using a 64bit operating system?
0 Kudos
8 Replies
Altera_Forum
Honored Contributor II
834 Views

You need to be more explicit wrt your linux distribution. 64 bit linux works fine, but some distributions have quirks that must be dealt with. 

 

 

--- Quote Start ---  

Hi Guys 

 

I have just installed the Quartus 12.1 64-bit Linux on my laptop. I downloaded the modelSim starter version 10.1b that is compatible with the quartus 12.1 from the altera downloads. 

 

I went through all the installation guides to set up modelsim and when i go to run the RTL_simulation i get this error; 

 

Can't launch modelSim-altera simulation software-- make sure the software is properly install and the environment variables LM_LICENSE_FILE or MGLS_LICENSE_FILE are set. 

 

I have noticed that in my directories where i installed the modelsim i don't have a license.dat file.  

 

As far as i was aware from reading and some post the modelsim starter shouldn't need licenses. I need to use this to simulate for my final year project so if any one has any ideas that might help me get over this obstacle i would much appreciate it. 

 

Is this an issue with me using a 64bit operating system? 

--- Quote End ---  

0 Kudos
Altera_Forum
Honored Contributor II
834 Views

Sorry about that, i am using Fedora 17

0 Kudos
Altera_Forum
Honored Contributor II
834 Views

 

--- Quote Start ---  

Sorry about that, i am using Fedora 17 

--- Quote End ---  

 

 

Well, in that case you problem is that fedora 17 and forward changed the naming scheme for ethernet devices from eth to em. The consequence being that the tools and licensing do not find the ethernet device and can not verify your license. To solve this you need to rename the ethernet device.
0 Kudos
Altera_Forum
Honored Contributor II
834 Views

Ok but if i am using wireless there shouldn't be a problem right?

0 Kudos
Altera_Forum
Honored Contributor II
834 Views

 

--- Quote Start ---  

Ok but if i am using wireless there shouldn't be a problem right? 

--- Quote End ---  

 

 

It should work fine.
0 Kudos
Altera_Forum
Honored Contributor II
834 Views

Well thats the issue that i have, its not working. Could this be a factor that the modelSim is looking for 32 bit libraries instead of the 64 bit?

0 Kudos
Altera_Forum
Honored Contributor II
834 Views

I thought i would post some more error message that i get from the .rtp file that gets generated 

 

Error: NativeLink simulation flow was NOT successful 

 

 

Nativelink TCL script failed with errorCode: issued_nl_message 

Nativelink TCL script failed with errorInfo: Can't launch ModelSim-Altera Simulation software -- make sure the software is properly installed and the environment variable LM_LICENSE_FILE or MGLS_LICENSE_FILE points to the correct license file. 

 

I have even deleted and tried to install again but with no luck.
0 Kudos
Altera_Forum
Honored Contributor II
834 Views

Ok so i have solved the problem..... after it being a relatively new install of fedora 17 i must not have installed the ncursers-devel.i686 i think it was.... installed that and it seemed to work

0 Kudos
Reply