these kind of licenses are often tied to mac addresses, so it's possible adding the nic confused the license manager. Does lmutil have a verbose flag? How did you disable the 10gig nic on your windows machine? Did you remove the card?
- andrew sent from a mobile device -----Original Message----- From: Sean <[email protected]> Date: Sun, 21 Mar 2010 18:34:36 To: Andrew Siemion<[email protected]> Cc: <[email protected]> Subject: Re: [casper] XAUI license Hi Andrew, I don't think those funny forward slashes indicate the problem. I've checked the Windows XILINX env variable and it's set to c:\Xilinx \10.1\ISE. I've still got the problem. There's something else that I should have mentioned before since it may be relevant. The machine I'm compiling on is also used for data collection. Therefore, I've installed a Myricom 10Gbe card on it and have a direct connection to my ROACH. At the time I tried to compile, I had a tgtap server running on the ROACH. Is it possible that my Xilinx licensing was disturbed by the presence of this card? I thought it might when I ran "lmutil lmhostid" and saw two MAC addresses. I've temporarily disabled the 10Gbe network card, rebooted, etc. and tried again, but no luck yet. In addition, I've run "lmutil lmstat", which gives [Detecting lmgrd processes...] Error getting status: Cannot find license file. (-1,359:2 "No such file or directory") Sean On Mar 21, 2010, at 1:18 PM, Andrew Siemion wrote: > Hi Sean, > > I’m not certain that this matters, but it looks like your search > paths have mixed backslashes and forward-slashes. Make sure your > XILINX environment variable is set to: > > C:\Xilinx\10.1\ISE\coregen\core_licenses > > Rather than: > > C:/Xilinx/10.1/ISE\coregen\core_licenses > > - Andrew > > > On 3/21/10 10:37 AM, "Sean" <[email protected]> wrote: > >> Hi Mark and Andrew, >> >> Thanks for the help so far. >> >>>> I haven't seen this problem before, but I might try checking 'Use >>>> KAT open XAUI PHY' in the parameters box or using the v2 10gbe >>>> yellow block. >> >> Yep, I'm already using the version 2 10gbe yellow block and still >> have this problem. >> >>> What is the output of: >>> >>> xlicmgr status -c "xaui_v7" -v >> >> Here's the non-verbose output: >> >> C:\Documents and Settings\kids>xlicmgr status -c "xaui_v7" >> Release 10.1.03 - Xilinx License Manager (xlicmgr) K.39 (nt) >> Copyright (c) 1995-2008 Xilinx, Inc. All rights reserved. >> Feature: xaui_v7 >> Status: Invalid - FLEXlm Error: No such feature exists. (-5,21) >> Expiration date: Unknown >> Current host ID: "0060dd46987d 0022683fc41a" >> License type: FLEXlm >> Built in search paths: C:\.Xilinx\Coregen\CoreLicenses;C:\Xilinx >> \10.1\EDK\data\c >> ore_licenses;C:/Xilinx/10.1/ISE\coregen\core_licenses >> FLEXlm license cache locations: C:/Xilinx/10.1/ISE\coregen >> \core_licenses >> >> I've attached the verbose output as a text file. If I'm reading >> this correctly, it seems there's a problem with the license. Why >> do think this is happening when I can see the updated license file >> in C:\Xilinx\10.1\ISE\coregen\core_licenses? >> >> >> Sean >> >> >> >> >> On Mar 21, 2010, at 6:32 AM, Andrew Siemion wrote: >> >>> Hi Sean, >>> >>> What is the output of: >>> >>> xlicmgr status -c "xaui_v7" -v >>> >>> ? >>> >>> - Andrew >>> >>> On 3/21/10 12:32 AM, "Mark Wagner" <[email protected]> >>> wrote: >>> >>> >>>> Hi Sean, >>>> >>>> I haven't seen this problem before, but I might try checking >>>> 'Use KAT open XAUI PHY' in the parameters box or using the v2 >>>> 10gbe yellow block. >>>> >>>> Mark >>>> >>>> >>>> On Sun, Mar 21, 2010 at 3:15 AM, Sean <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Last week I compiled a simple design to test the 10Gbe port for >>>>> the ROACH; no problem. However, I just tried compiling it again >>>>> and an error occurred complaining that I didn't have the XAUI v. >>>>> 7 license. I looked in C:\Xilinx\10.1\ISE\coregen\core_licenses >>>>> and found the license. It is "permanent" so I figure it's not >>>>> expired, but to be sure I requested a new one. I still get the >>>>> same problem. Now I don't think it's actually a license issue >>>>> since I tried compiling it on a collaborators machine at a >>>>> different institution (with a different lisence) and got the >>>>> same error. >>>>> >>>>> Has anyone else experienced anything like this and found their >>>>> way clear? Advice is greatly appreciated. >>>>> >>>>> Thanks, >>>>> >>>>> Sean >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >>
