I've installed Quartus II 64-Bit on my PC under LinuxMint 17.3 OS. I don't have any problem with it. But I cann't run simulation with ModelSim-Altera. I get the message "ModelSim-Altera was not found...". There is the detailed instruction for installing ModelSim-Altera which I've performed. But it hasn't helped me. I've also tried to set "/" at end of path to ModelSim-Altera. Now I don't now what I have to do to make it able to run.
Additional information:
I also have the following error when running vsim:
** Fatal: Read failure in vlm process (0,0)
Segmentation fault (core dumped)
I've tried to perform the instructions under link (problem number two), but I have the mentioned error yet.
After performing all instruction under the link above (problem number one and then problem number two) I got a well running vsim. But unfortunatly I cann't run ModelSim from Quartus II.
I know it's an old thread, but I came here looking for the answer and ended up everywhere else.
Adding this to .bashrc appears to have worked:
export PATH=$PATH:~/altera/13.0sp1/modelsim_ase/bin:~/altera/13.0sp1/quartus/bin
It may also be worth noting that I re-downloaded modelsim-altera, even though it said I already had it. I was not able to run modelsim_ase/linuxaloem/vsim (libXext.so.6 not found, although it too was installed) but it now appears to work. 64 bit Ubuntu 16.04.
Hopefully this helps someone else.
Edit: also export QUARTUS_64BIT=1 in .bashrc
Related
Alright, just a disclaimer: I've been using some version of Unix or Linux for 30 years, I have good working knowledge, but when it comes to administration I'm enthusiastically dangerous :)
Every time I do the automated OS upgrade in Pop!_OS something bad happens. And I am not talking about apt update / apt dist-upgrade. I do mean going into the settings GUI and in the last item on the list clicking "Upgrade".
Last machine I did it on failed and I couldn't recover the system, not even from a bootable stick. That machine was on it's last leg, I just let it go and built a new box, it was time. Well here we are again, time for an upgrade to 20.10.
I hit "upgrade os" (maybe it's "update os" I don't remember exactly
It did some stuff, and said it needed to restart - Okay so now we're windows? Not thrilled
Restart and end up at a gray screen where it sat at 0% progress bar for the update
I let it sit a good long while, maybe 45 minutes, I was worried this mid-low range machine was just taking a while, nothing
Cringe.. hit the reset button, the system rebooted and did "something" and then came up seemingly okay
Now here's the problem list:
Did the upgrade happen fully, completely, and successfully? How can I tell? This feels like I'm running windows and just rolling in the blind mystery..
VMWare Workstation wont launch. Nothing happens with icon click, from command line I get this error:
/usr/bin/vmware: line 105: 159580 Segmentation fault (core dumped) "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"
Searching online a bunch there was a lot of talk that there may be permission problems after upgrade and running it as root would help. This did not work. I read that upgrading to VMWare 16.x will help. I'm open to it, but on principle WHY does this have to be the case?
I use another app that is installed from source, it's called MakeMKV. I've had no trouble with it until the Pop upgrade. Again, it doesn't launch from the icon. I rebuilt and reinstalled it. No go. Launching from command line returns:
/snap/makemkv/217/bin/desktop-launch: line 51: /home/ritchie/.config/user-dirs.dirs: Permission denied
qt.qpa.screen: QXcbConnection: Could not connect to display :1
Could not connect to any X display.
Launching from the command line with sudo worked though! So wtf?
This feels like a key piece of the puzzle, that bit about not being able to connect to the display.
Since this post is so long I wont list the hardware, but am happy to if it helps diagnose.
Any help is appreciated!
got the same with other snap packages...
tried to figure out what's wrong...
looks like some ENV variable is not set properly causing the error:
.config/user-dirs.dirs: Permission denied
but simply reinstalling the package resolves the issue:
sudo snap remove %package%
sudo snap install %package%
The Ubuntu 16.04 freeze by itself especially when 2-3 instance of Pycharm is actively running.I wanted to know the exact cause of the OS freeze and found linux-crashdump.
The linux-crashdump was installed using the link [kernel-crash-dump][1]
[1]: https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html "kernel-crash-dump"
It states that after installation and rebooting the system
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-17-server root=/dev/mapper/PreciseS-root ro
crashkernel=384M-2G:64M,2G-:128M
But cat /proc/cmdline is not showing the parameter crashkernel added to it.
I am not able to edit the /proc/cmdline in anyway.
If I add crashkernel=384M-2G:64M,2G-:128M then the error appears.
"/proc/cmdline" E667: Fsync failed
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!
I am not able to move further, as per the documentation of kernel-crash-dump after the installation, I rebooted the system, but still the crashkernel parameter in the /proc/cmdline is not appearing.
I didn't get completely what the problem was but as far as I understood you had problems with crashkernel. I think that it would help if you just remove it completely and reinstall it again, because you have lost some of the files of crashkernel and that's why it's not responding. Hope it helps :)
I am a linux noob trying to setup openbox on an arch linux base. I am trying to get it as lightweight as possible in terms of resources used.
My final plan is to use openbox, with tint1 and conky.
however I am having an issue getting openbox to start. I have followed numerous guides and am struggling to figure out the problem.
I have so far installed the following (and done this config)
openbox (installed default option with the extras asked for)
create ~/.conifg/openbox
copied, rc.xml, menu.xml, autostart, environment to the above location
pyxdg
xorg-xinit
xorg-server
this didn't work so I the installed the full
xorg
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
I have had a look at the attached log file, but I don't know enough to be able to interpret it properly.
log file: https://www.dropbox.com/s/r76fowkooi822y9/Xorg.log?dl=0
I would appreciate any assistance.
Thanks
Steve
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
what is it saying?
There is only one error: (EE) open /dev/fb0: Permission denied, try starting your environment with the same configuration as root - just to see if it works. Maybe its a problem related to rootless X.
Have you configured/checked your installation (xserver, graphics driver, xinit config) using the following guides?
https://wiki.archlinux.org/index.php/xorg
https://wiki.archlinux.org/index.php/xinitrc
Try to start a minimal X (As described in the xinitrc article) to see if your xserver and graphics driver is working correctly.
Currently running: Arch linux 4.0.7-2
I've worked with X11 for a while without any trouble. Until recently after a reboot the following error came up: No screens found. I looked up similar questions but none of them had the answer required. I tried to remake my configuration file but that wasn't possible either due to Number of created screens does not match number of detected devices. Configuration failed.
I spend hours trying to find a fix but nothing worked, I tried re-installing every single package I had and removed everything to bare. Unfortunately no luck.
I then went and reinstalled entire Arch linux but to my surprise the first error to appear when trying to make a configuration file was No devices to configure. Running startx however gives me a set of floating terminals but freezes entirely.
lspci -vvv http://ix.io/juQ
/var/log/Xorg.0.log http://ix.io/juR
I'm kind of clueless right now. Any help would be much appreciated.
I think that the problem is located in that line of your log:
[ 355.070] (II) Loading /usr/lib/xorg/modules/drivers/i740_drv.so
[ 355.079] (EE) Failed to load /usr/lib/xorg/modules/drivers/i740_drv.so: /usr/lib/xorg/modules/drivers/i740_drv.so: undefined symbol: I740_Sync
It seems that this file is missing, googling a little i found that archlinux forum post, that probably will help you:
https://bbs.archlinux.org/viewtopic.php?id=176555
What you need to do, is simply run that command:
pacman -Sf `pacman -Qqet`
And maybe it solve the problem (there are no more answers to that post, so i'm not sure if it works)
I am trying to install Xen on Centos6.5 based on this tutorial (http://wiki.centos.org/HowTos/Xen/Xen4QuickStart), however after installing xen and running the script to edit the grub.conf, i am not able to boot into the new kernel.
I get an error stating -
invalid magic number: 9090
Error 13: Invalid or unsupported executable format
Can someone help me please?
Current suspicion: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart definitely not a 10 minute install for all platforms???
History: there is a Centos Bug on this: centos.org/print_bug_page.php?bug_id=6503
I repeated a similar process:
(1) Install Centos 6.6 (Centos kernel: 2.6.32-504.el6.x86_84) from DVD1, DVD2 with Install using only the CENTOS Repo
(2) Installed Xen (Xen4CentOS kernel:3.10.56-11.el6.centos.alt.X86_64) Issuing the following commands from the centos command line (as root, warnings from readers accepted as correct from a security standpoint) To abate the security concern, no network connection existed as an offline repo would have been used but was not actually needed for the Centos minimal install.
yum install centos-release-xen
yum install xen
/usr/bin/grub-bootxen.sh
from the Xen/Centos reference: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart
I noticed that the /boot/grub/grub.conf file was non-existent and tried to reboot without it. The reference above suggests it should be there, so I am proposing that your grub.conf file was missing or incorrect because my results were similar:
'invalid magic number: 9090
Error 13: Invalid or unsupported executable format
Press any key to continue...'
So as of now I can reproduce the problem. I will be updating this as I discover what will solve it for my solution, post it with hope it fixes it for yours or others who share similar issues.
I noticed something odd, I was using a Combo USB hub and tried to reboot using the other kernel (2.6) and there were considerable failures which were squawking on the startup screen and it would not permit me to start. When I removed it I could not boot into the 3.10, but only into 2.6.
Ok, a quick find on grub.conf revealed a similar version to that shown on the reference link above in /etc. So I copied the grub.conf from /etc to /boot/grub and rebooted. But I too see similar results. The USB hub is off the system and will not be reattached, so there is something else here that needs review. I'm digging into the grub.conf file at this time...
(update) I see that there is a grub.conf file under /boot/efi/EFI/redhat. Oddly in the Centos 'bug archives' there appears to be a related resolved bug for Centos 7: bugs.centos.org/view.php?id=7242 (cannot post this as a link as my reputation is less than 10, my apologies)
Also, as this relates to magic number here are results for my type of files and magic numbers, but I have done this with vi and have some assumptions here about what I saw, so I am retrying this with the help of the other stackoverflow article which uses file-devel package LibMagic... here are the intermittent results.
File.x86_64 Magic number (if two bytes, just use first 2)
vmlinuz-2.6.32.504.el6.x86_64 /0x8c/0x8e/0x8e/0x8e
vmlinuz-3.10.56-11.el6.centos.alt.x86_64 /0x8c/0x8e/0x8e/0x8e
Note: A search of '9090' on centos.org using the provided search engine for words on the site yielded no response on 12/22/14: #wiki.centos.org/Search
There is no mention of installation problems with SELinux, even though I have set:
SELINUX=disabled
in the /etc/sysconfig/selinux file and
yum uninstall xen
yum install xen
/usr/bin/grub-bootxen.sh
No results, and no new grub file in any of the three locations listed above. /etc /boot or /boot/efi/EFI/redhat.
Comparison of the grub.conf files with other sources, show that it is reasonable. Same for the grub-bootxen.sh file based on what I could decipher from bash.
Changing the timeout in grub.conf (all I found) to 15 and removing the hiddenmenu command by #hiddenmenu, did not eliminate the '9090' error. Using: wiki.xen.org/wiki/RHEL6_Xen4_Tutorial which shows the 'kernel' modifier instead of the 'module' and changing the 'module' in front of the .img file to initrd, did not change the results.
OK. Reload.
1) reinstall minmum Centos
2) disable SE Linux
3) reboot
4) correct ifcfg-eth0 (remove NM and allow boot on startup) and service network restart
5) yum import centos-release-xen (accept import of GPG key)
6) yum install xen
7) investigate what occurs with "grub-install hd0" which produces '9090' error!
Ok, I would have to say that the question was not well defined. It is now well defined and can be posed as a question. I will convert this info and my trials to a reasonable question to see if anyone can assist with pointers...