05-04-2015 10:50 AM
05-04-2015 03:01 PM
05-04-2015 06:15 PM - edited 05-05-2015 01:51 AM
Debian is unsupported OS and we have not tested Vivado on Debian.
Try using supported OS.
Microsoft Windows Support
• Windows 7 and 7 SP1 Professional (64-bit), English/Japanese.
• Windows 8.1 Professional (64-bit), English/Japanese.
• Vivado® Lab Edition is the only Xilinx toolset that supports Windows 7 SP1
Professional, 32-bit Operating System. Lab Edition also supports the 64-bit systems.
• Red Hat Enterprise Workstation 7.0 (64-bit)
• Red Hat Enterprise Workstation 6.4-6.6 (64-bit)
• SUSE Linux Enterprise 12.0 (64-bit)
• Cent OS 7.0 (64-bit)
• Ubuntu Linux 14.04 LTS (64-bit)
• Vivado Lab Edition is the only Xilinx toolset that supports the Red Hat Enterprise
05-05-2015 01:48 AM
This might be an unsupported OS, but uname -m is the right command to check the architecture ;).
05-05-2015 10:45 AM
I am running Arch Linux too. Solved the problem by:
1\ starting the installer with the --confirm parameter , path to the xsetup file got displayed
2\ finding and modifying the xsetup file (uname -m).
3\ confirmed the execution of xsetup in the installer shell.
05-05-2015 07:46 PM
05-05-2015 10:58 PM
Nobody said that someone installs Vivado 2015.1 on 32-bit platform. However, the usage of 'uname -i' in xsetup is wrong and should be replaced by 'uname -m'. The first one returns the hardware platform (e.g. GenuineIntel, AuthenticAMD, ...) and the latter one returns the machine hardware name (e.g. i386, i686, x86_64, ...).
12-07-2015 04:20 AM
I had the same issue to install Vivado or to install SDK separatly. A colleague from software staff found a solution. In Debians, their is an uname working well (at least for "-i" otpion):
$ /usr/lib/klibc/bin/uname -i
$ sudo dpkg-divert --add --rename --divert /bin/uname.orig /bin/uname $ sudo ln -s /usr/lib/klibc/bin/uname /bin/uname
To go back :
$ sudo dpkg-divert --rename --remove /bin/uname
12-17-2015 01:57 PM
I have downloaded the Linux 64 bit installer (.bin). I am running on a supported 64 bit Linux (Ubuntu 14.04). I am getting this same error. Is there a workaround? I saw mention of a command line option, but I haven't found documentation for that. (Not really sure where to look.) I am running a VMware Ubuntu 14.04.3 (Trusty Tahr).
12-18-2015 02:32 AM
Have you this /usr/lib/klibc/bin/uname version on your system ? If yes, does the command answer like this :
/usr/lib/klibc/bin/uname -i x86_64
In this case and if you have root permissions , you can apply the solution posted on 12-07-2015. After that, execute again the Vivado Linux 64 bit installer. It should work.
Hope this will help you
12-18-2015 08:47 AM
Turns out that I was wrong? The vmdk for Trusty Tahr at osboxes seems to have a 32 bit kernel. It is identified as "VMware (VMDK) 64bit Size: 760.2MB", but identifies as i686. I'm required to run Ubuntu 14.04, so I'm going to see if I have the same problem on VirtualBox VM. Thanks for the reply.
12-20-2015 03:49 AM
01-13-2016 02:24 PM
Xilinx still needs to fix that script. Come on guys - it's not even one line of code and the fix has been known for months...
01-13-2016 07:52 PM
I created a change request CR#930032 to address this issue.
06-08-2016 03:50 PM
Not fixed yet in 2016.2... this is such an easy fix for Xilinx to make, and probably wastes an hour or two for every user that encounters it for the first time.
07-11-2020 01:32 AM
I am getting the same error for 2020.1. Has this ever been fixed?
07-14-2020 02:03 AM
Hello @binupr ,
This issue was fixed and addressed in 2016.3 and newer versions of Vivado.
Can you please confirm what OS are you seeing this issue on? Thanks
07-20-2020 06:14 AM
Hello @binupr ,
Can you please send us your .log file for examination?
Log file location, e.g.: C:\Users\anatoli\.Xilinx\xinstall\xinstall_1573577270354.log