You are not logged in.
Hello,
I am trying to run Vivado HLS on a 5.9.10 kernel and since kernel 5.9 release it does not work anymore (around 3.11.2020). I tried running it in an LXC with Ubuntu but it seems related to the kernel update. I am periodically checking if any update fixed it but it still does not launch. All I receive is the following log:
****** Vivado(TM) HLS - High-Level Synthesis from C, C++ and SystemC v2020.1 (64-bit)
**** SW Build 2902540 on Wed May 27 19:54:35 MDT 2020
**** IP Build 2902112 on Wed May 27 22:43:36 MDT 2020
** Copyright 1986-2020 Xilinx, Inc. All Rights Reserved.
source /opt/opt-ext/Xilinx/Vivado/Vivado/2020.1/scripts/vivado_hls/hls.tcl -notrace
INFO: [HLS 200-10] Running '/opt/opt-ext/Xilinx/Vivado/Vivado/2020.1/bin/unwrapped/lnx64.o/vivado_hls'
INFO: [HLS 200-10] For user 'jduchniewicz' on host 'archie' (Linux_x86_64 version 5.9.10-arch1-1) on Sun Nov 29 18:32:51 CET 2020
INFO: [HLS 200-10] On os "Arch Linux"
INFO: [HLS 200-10] In directory '/mnt/games/opt-ext/Xilinx/Vivado/Vivado/2020.1/bin'
INFO: [HLS 200-10] Bringing up Vivado HLS GUI ...
@E cannot exec arch command, error: couldn't execute "arch": no such file or directory
INFO: [Common 17-206] Exiting vivado_hls at Sun Nov 29 18:32:52 2020...Interestingly on the containter I get slighlty different logs, but there the app just exits without bringing the GUI.
****** Vivado(TM) HLS - High-Level Synthesis from C, C++ and SystemC v2020.1 (64-bit)
**** SW Build 2902540 on Wed May 27 19:54:35 MDT 2020
**** IP Build 2902112 on Wed May 27 22:43:36 MDT 2020
** Copyright 1986-2020 Xilinx, Inc. All Rights Reserved.
source /opt/xilinx/Vivado/2020.1/scripts/vivado_hls/hls.tcl -notrace
INFO: [HLS 200-10] Running '/opt/xilinx/Vivado/2020.1/bin/unwrapped/lnx64.o/vivado_hls'
INFO: [HLS 200-10] For user 'root' on host 'vivado2020_1' (Linux_x86_64 version 5.9.10-arch1-1) on Sun Nov 29 17:33:54 UTC 2020
INFO: [HLS 200-10] On os Ubuntu 18.04.5 LTS
INFO: [HLS 200-10] In directory '/mnt/games/opt-ext/Xilinx/Vivado/Vivado/2020.1/bin'
INFO: [HLS 200-10] Bringing up Vivado HLS GUI ...
INFO: [Common 17-206] Exiting vivado_hls at Sun Nov 29 17:34:06 2020...
root@vivado2020_1:/mnt/games/opt-ext/Xilinx/Vivado/Vivado/2020.1/bin# exitIs it working for anybody with current kernel? Maybe it is a problem with my installation but I did not change anything between these versions.
Offline
I have the same behavior with vitis_hls 2020.2 on Arch 5.11.1. As a workaround I use the command line interface only (`vitis_hls -f script.tcl`)
Regarding kernel update: I do not have any explanation for why a kernel update could change the behavior the tool.
Searching for "@E cannot exec arch command" seems to be a TCL script related error, but searching for this string in the binaries and files did not return any results.
Did you have additional insights in the last weeks xDinger?
Last edited by leuko (2021-02-28 08:56:08)
Offline
Ubuntu ships their coreutils with the arch binary enabled (https://packages.ubuntu.com/bionic/amd6 … s/filelist), Arch doesn't.
Are you certain that this is solely related to the kernel package (i.e. downgraded just that, rebooted, and it worked again)? In that case Vivado is probably deciding to use `arch` instead of `uname -m` based on the kernel version; if not, some other package probably used to provide an `arch` binary and removed it at around the same time that the kernel updated, causing confusion.
Last edited by xiretza (2021-02-28 09:50:25)
Offline
All I do right now is run it in the Ubuntu VM.
As for the kernel update, I am not positive it was just due to it. Probably some packages were upgraded on the way as well.
Creating the `arch` file in `/usr/local/bin` did not help. So the cause must lie somewhere deeper.
Offline
I've had a lot of trouble with vivado tools over the years on unsupported systems. My best advice is to use a VM or a docker container. There's a way to get the GUI to work with docker too, but I'm not sure how.
Here's my dockerfile (can be used with podman too). You need to generate the install_config.txt and the auth key with the cli tools included in the installer
FROM ubuntu:18.04
RUN dpkg --add-architecture i386
RUN apt-get update && apt-get install -y \
wget \
build-essential \
libglib2.0-0 \
libsm6 \
libxi6 \
libxrender1 \
libxrandr2 \
libfreetype6 \
libfontconfig \
lib32stdc++6 \
libgtk2.0-0:i386 \
libfontconfig1:i386 \
libx11-6:i386 \
libxext6:i386 \
libxrender1:i386 \
libsm6:i386 \
libqtgui4:i386
#RUN adduser --disabled-password --gecos '' vivado
#RUN chown -hR vivado:vivado /home/vivado
#add vivado tools to path
# copy in config file
#WORKDIR /home/vivado
COPY install_config.txt /
# download and run the install
#ARG
COPY Xilinx_Unified_2020.1_0602_1208_Lin64.bin /
COPY wi_authentication_key /root/.Xilinx/
#RUN chmod +x /home/vivado/Xilinx_Unified_2020.1_0602_1208_Lin64.bin
RUN echo "Installing vivado from Xilinx_Unified_2020.1_0602_1208_Lin64.bin" && \
./Xilinx_Unified_2020.1_0602_1208_Lin64.bin --tar xvf --no-same-owner && \
./xsetup --agree 3rdPartyEULA,WebTalkTerms,XilinxEULA --batch Install --config install_config.txt
#make a Vivado user
#add vivado tools to path
ENV PATH "$PATH:/opt/Xilinx/Vivado/2020.1/bin"Offline
I am always having the same troubles with the VM's/Dockers - Nvidia Optimu GPU, so everything requiring heavy GPU usage lags as hell. Not that well-versed in passthroughs, but I heard they are possible.
As mentioned earlier LXC does not launch it either with GUI support (container with just the rootfs of Ubuntu, using the host's kernel).
Offline
I am facing the same issue. Isn't there any package that would simply contain the arch binary?
Offline
dear mkru, why do you think that `arch` binary is the problem? I believe it is just a basic application which prints the architecture you have. You can copy it from Ubuntu or create it yourself by writing a script which prints `x86_64` (see https://aur.archlinux.org/packages/vivado/).
---
On my computer the problem still exists after creating this script as described in AUR.
Things that I also tried:
1. installing Vivado on Ubuntu 20.10 in an nspawn container (machinectl) ❌
2. installing Vivado on Ubuntu 20.10 in Virtualbox ✔️
3. booting Archlinux with linux-lts54 kernel (I could not find linux version 5.8 in AUR, which allegedly should have worked as the original poster mentioned before) ❌
Does someone have other ideas?
Offline
It is a bug of Xilinx Vitis HLS script, although you should alias arch='uname -m'
see:
Offline