End compilation error message:
Error: Illegal parameter: -CpCORTEXM3
Windows CE requires an MMU, which Cortex-M3 does not have.
Related
Iḿ trying to get vulkan to work but I get the following error:
vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED
Following command dumps:
lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410]
Kernel driver in use: i915
I have added the following to my grub config and initialized it
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0"
followed by a reboot. The result is the same error :(
what am I doing wrong, can anyone help me?
Before I forget I installed vukan and mesa vulkan drivers and am running Ubuntu 20.04 LTS on a Dell Latitude E4310. Please help, I just want to play some windows (directX11) games with Wine.
This kind of cryptic error message can happen because vulkaninfo doesn't find any supported GPU.
It is likely that your GPU is not supported by Vulkan (too old), and so you won't be able to use DXVK (DirectX to Vulkan). You still may be able to run games without Vulkan by forcing Wine to use WineD3D (DirectX to OpenGl) instead. See Xaero_Vincent's answer in this reddit thread:
In Lutris you can easily disable DXVK as a option and on steam you can
force OpenGL-based WineD3D:
PROTON_USE_WINED3D=1 %command%
You'll notice though that DirectX 10/11 games will generally run
slower under OpenGL and some games will likely have graphics
artifacts, since DXVK is more mature and further developed.
The following error occurs when running my virtual box 5.1 from terminal in Debian 8 and this error when I close virtualbox:
Qt WARNING: QObject::disconnect: No such signal QApplication::screenRemoved(QScreen *)
What should I do?
The "screenRemoved" is a singnal from "QGuiApplication".
And "QApplication" iherits "QGuiApplication".
It is all good. But this method is there from Qt5.4 version.
http://doc.qt.io/qt-5/qguiapplication.html#screenRemoved
Please check your QT version. May be it is bit older.
I can't use Quartus 14.1.0 with Linux Debian (wheezy and Jessie) on my 64 bits computer.
If I launch it on console I've got this message :
user#fpgaformation:/opt/altera/14.1/quartus/bin$ ./quartus
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion `map->l_init_called' failed!
And the GUI is launched correctly.
But, after some minutes of using it, quartus disappear suddenly without message on terminal but with an altera problem-window.
In this window, we can get the following report :
Problem Details
Error:
*** Fatal Error: Segment Violation at (nil)
Module: quartus
Stack Trace:
0x68cd4: fwrite + 0x34 (c.so.6)
0x1205b: showit + 0x5b (curl.so.4)
0x12388: Curl_debug + 0xe8 (curl.so.4)
0x125ff: Curl_failf + 0xdf (curl.so.4)
0x910f: Curl_resolv_timeout + 0x12f (curl.so.4)
End-trace
Executable: quartus
Comment:
None
System Information
Platform: linux64
OS name: Debian GNU/Linux
OS version: 7
Quartus II Information
Address bits: 64
Version: 14.1.0
Build: 186
Edition: Web Edition
I use also QuartusII 14.0.0 which work well on the same computer.
I know that Altera does'nt support Debian officially (only RedHat) but if somebody has a clue ?
It's a known bug in Altera. They provided me a patch to correct it :
quartusii-14.1-0.19-linux.run
The patch can be found on altera support website :
rd01272015_37
I applied it and quartus work well now. I think they will publish this correction soon.
Is is possible to load a .ko file (kernel object file) which was compiled in 64-bit processor system into 32 bit processor system?
Actually I am getting following error when I issue the insmod command in my system:
insmod: error inserting 'be2net.ko': -1 Invalid module format
It is not possible to run 64-bit code in a 32-bit system. Depending on the requirements, the reverse can be true (running 32-bit software or libraries in a 64-bit system), but a 32-bit architecture cannot understand 64-bit code. You will need to compile the module on your system.
First download the kernel source from kernel.org. Then extract, and cd into
linux/drivers/net/benet
Once there, type (as your regular user)
make
and then
sudo insmod be2net.ko
That should work for you.
No, it is not possible to load 64-bit modules to a 32-bit kernel, and that is why you are getting an error. The reason is that 64 and 32-bit program have an incompatible ABI (e.g. different calling conventions). That is also the reason 64-bit applications can't be linked with 32-bit libraries, for example.
Note that insmod generally gives vague error message. For a more detailed message look at the output of dmesg.
The processor where it was compiled matters not at all. The compiler and compiler options do matter. If it was compiled FOR a 64-bit processor, it cannot run on a 32-bit processor, because it uses a different instruction set.
However, a 64-bit processor can run a cross-compiler and create 32-bit binaries. It is unlikely that you've done this.
The following Fortran code is giving me a bus error on my Mac but no errors when I run it on my Linux machine:
PROGRAM TINY
WRITE(UNIT=*, FMT=*) 'Hello, world!'
END
My understanding is that a bus error occurs when the program attempts to access impossible memory but I do not understand where such an attempt has been made in this program. My MacBook has GCC 4.4.0 and my Linux machine has GCC 4.3.2. Any ideas as to why this error occurs?
No ideas at all, just thought I'd let you know that I have no problems compiling and running the program on my Mac Pro. I compiled with G95 (GCC 4.0.4 (g95 0.91!) Dec 11 2008). Like you, I think a bus error is usually an attempt to address memory which doesn't exist.
The program runs fine on my Mac with gfortran 4.4.2. Do other Fortran programs run on your MacBook, or do they all have this problem?