Sorry, you need to enable JavaScript to visit this website.

Running Vivado in Ubuntu

Unsolved
1 post / 0 new
narrucmot's picture
narrucmot
Moderator(1)
Running Vivado in Ubuntu

Hi Everyone,

I have noticed in Ubuntu v16.04.LTS that the Ethertnet interface is named "enp0s3" instead of the expected "eth0".  This breaks the Vivado license manager, which only expects to see Ethernet interfaces named "eth<n>".  Hopefully this thread will help others that have also discovered this and need to fix it.

Because of this issue, the Vivado License Manager reports the Ubuntu HostID (the Ethernet MAC address) as "000000000000" The Vivado License Manager will not create a license for this bogus HostID.

This is identified in this Xilinx forum thread here:

https://forums.xilinx.com/t5/Installation-and-Licensing/vivado-don-t-fin...

And a solution (for CentOS, I believe) is also described in this Xilinx Answer Record:

https://www.xilinx.com/support/answers/60510.html

To solve this, I followed some simple instructions which disabled the naming of the Ethernet interface to "enp0s3" and instead allows it to be named "eth0" (which is what Vivado License Manager expects to see) so the MAC address can be read from this interface as the HostID:

http://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html

In short, follow these instructions:

  1. Edit the /etc/default/grub configuration file.  You need to be root user or use sudo to do this.  BE VERY CAREFUL WHEN EDITING THIS FILE!  An incorrect edit here can cause your Ubuntu OS not to boot.  Look for the "GRUB_CMDLINE_LINUX" line and add  "net.ifnames=0 biosdevname=0" (with quotes)
  2. Generate a new grub file using the following command:
    $ sudo grub-mkconfig -o /boot/grub/grub.cfg
  3. Reboot Ubuntu and verify there is a new, correct, MAC address by looking through ifconfig output.
  4. Go to the Xilinx Licencing site and generate a new license for a host with the MAC ID that now appears in the Vivado License Manager dialog.
  5. Load the license file and make sure that the desired Vivado features are now available.

For CentOS users, the same problem is described, and can be solved, by following the instructions in this forum post:

http://zedboard.org/content/running-vivado-centos-7-virtual-machine

I hope this helps!

Regards,

Tom