I'm trying to test a SOM made by Variscite (VAR-SOM-6UL). On their website they have a precompiled Debian buster image. Unfortunately the cp210x module is not present on this image. This library automatically transforms a USB into UART channel. I use this library when I connect a sensor to the SoM so that they can both communicate via UART through USB.
I never had this problem before because the cp210x is preinstalled since kernel v3.x. For an unknown reason the cp210x module is not installed on the Debian buster image even tho the kernel version is v4.14.
$ uname -ar
Linux imx6ul-var-dart 4.14.78-g8e54a4b #1 SMP PREEMPT Tue Nov 19 16:42:38 PST 2019 armv7l GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
This makes absolutely no sense but I have verified that there is indeed no cp210x on this image.
I'm stuck. I can't compile the cp210x module. I can't find another Linux library that does the same thing. I can't find the right linux-headers to compile the cp210x on my SoM.
I know that I should directly contact Variscite, but I cant even make an account it takes time to approve my account before I can post a question.
What I have tried so far:
installed the Linux-header
compiled the cp210x module from source to get a .ko file
put the .ko file in the right place and modprobe it
Did not work because the used Linux headers kernel version was higher than the running kernel. I can't find the right Linux headers version because the minimum version using apt get is v4.19.
I tried to use the https://snapshot.debian.org/ repository to download an older version of the Linux headers but it doesn't work because when I use the apt search linux-headers command the oldest Linux kernel is v4.19 (did not change).
Related
I'm using ubuntu 18.04 and trying to boot kernel 2.6.34.7 compiled from source. I tried to boot from ubuntu but it says "kernel too old", then I came up with the idea of using qemu, but I got the same problem... The version of my QEMU emulator is 2.11.1, the error code is:
...
FATAL: kernel too old
[ 5.299747] Kernel panic - not syncing: Attempted to kill init!
[ 5.300415] Pid: 1, comm: init Not tainted 2.6.34.7 #1
...
This is not a problem with QEMU. The "FATAL: kernel too old" message comes from your guest's userspace, specifically its glibc. Your guest's userspace binaries were built to require a newer kernel than the one you're trying to boot, so the two are not compatible. You need to either use a set of userspace binaries (ie a disk image) which was built to work with that old kernel, or you need to use a newer kernel that will work with the binaries you're using.
I've installed Android Things on my Raspberry Pi 3.
When I'm on the shell of my RPi3,
I note that there are not all commands of Linux, especially :
sudo
apt-get
Here is my OS :
1|rpi3:/ # uname -a
Linux localhost 4.4.19-v7+ #1 SMP PREEMPT Fri Aug 18 02:59:59 UTC 2017 armv7l
Can we install these commands ?
Android Things is an operating system based on Linux, with the same underlying kernel. However, it does not necessarily support every tool that is part of desktop Linux operating systems.
Some tools like apt-get are only on a few Linux variants. Macs, which use the same Linux kernel, do not have apt-get installed either.
Some binary files may run on Android, and many may not. Software that use certain types of drivers may not be supported due to changes in permission models and hardware configurations.
On the Raspberry Pi, it may have a traditional desktop interface in Raspbian. However, when running Android Things many of the traditional Linux components may not run, instead being replaced by tools that may make more sense for Android like the Package Manager and Activity Manager.
I try to link my program with libboost_thread-mt on a Debian machine. It worked well on Debian 7 (wheezy) but it fails on Debian 8 (Jessie). On Wheezy the library version was 1.49, and on Jessie it is 1.55. The package is now using multi-arch scheme, which means that it used to be under /usr/lib and now it is under /usr/lib/i386-linux-gnu. What do I need to do in order to link it properly without using -L?
I want to cross-compile my own kernel module for a BeagleBone Black using my desktop PC which has AMD-64bit architecture, and is running debian. The BeagleBone Black is also running debain, but the two machines have different kernels.
I just want to install the kernel headers for the ARM on my desktop PC, but I can't figure out which deb(s) need to be installed. I have the arm-linux-gnueabi-* version of gcc installed.
The kernel on the BeagleBone Black is this:
Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux
What kernel-headers deb do I need for this?
These are the ones that I already have installed:
linux-headers-3.2.0-4-all
linux-headers-3.2.0-4-all-amd64
linux-headers-3.2.0-4-amd64
linux-headers-3.2.0-4-common
linux-headers-3.2.0-4-common-rt
linux-headers-3.2.0-4-rt-amd64
Apparently this is not possible yet - there don't seem to be any Linux header packages in Debian later than 3.2.*
I am running Fedora 12 that runs on 2.6.31 linux kernel.
and have to compile some code run the binary on 2.6.11 kernel(supported by FC4).
Is there a way to do the same, without having to install FC4 or have a virtual machine running FC4?
Also, When you print file info of an elf image using file command, why does the part 'for GNU/Linux ', show an older kernel version?
For example, for me, on 2.6.31 kernel, it says compiled for 2.6.18, on 2.6.11 it says compiled for 2.2.5. This is the kernel version its talking about I suppose.
Thanks