Jump to content

Recommended Posts

Posted

I'm having a problem installing a driver. Once compiled correctly, the system gives me an error.

Note that I performed the same procedure with :

  • RaspiOS on an arm64 board (RPi4B) with the same kernel version, and it worked.
  • Debian 12 on a PC, and it worked. 
  • Armbian  on an arm64 board (RPi4B) with the same kernel version, and it worked.
  • Armbian  on an armhf board (nanopineocore) with the same kernel version, and it worked.

 

But does not work with Armbian Bookworm on a nanopineocore2 board:

 

epsilonrt@nanopineocore2:~/src/tty0tty/module$ sudo modprobe tty0tty
modprobe: ERROR: could not insert 'tty0tty': Exec format error

epsilonrt@nanopineocore2:~/src/tty0tty/module$ modinfo tty0tty
filename:       /lib/modules/6.12.20-current-sunxi64/updates/dkms/tty0tty.ko
license:        GPL
description:    tty0tty null modem driver
author:         Luis Claudio Gamboa Lopes <lcgamboa@yahoo.com>
depends:
name:           tty0tty
vermagic:       6.12.20-current-sunxi64 SMP mod_unload aarch64

epsilonrt@nanopineocore2:~/src/tty0tty/module$ uname -a
Linux nanopineocore2 6.12.20-current-sunxi64 #1 SMP Sat Mar 22 19:54:28 UTC 2025 aarch64 GNU/Linux

 

The problem does not come from the driver which loads very well on all the systems mentioned at the beginning of the post, for example with Armbian Bookworm on an RPi 4B board:

 

epsilonrt@r14:~/src/tty0tty/module$ sudo modprobe tty0tty
epsilonrt@r14:~/src/tty0tty/module$ dmesg | tail
[   15.046221] bcmgenet fd580000.ethernet end0: Link is Up - 1Gbps/Full - flow control off
[   21.678333] Bluetooth: RFCOMM TTY layer initialized
[   21.678364] Bluetooth: RFCOMM socket layer initialized
[   21.678384] Bluetooth: RFCOMM ver 1.11
[   84.092535] mempolicy: Request by 'ps' to set policy to 5 ignored
[   84.092553] mempolicy: Request by 'ps' to set policy to 3 ignored
[  261.550048] mempolicy: Request by 'ps' to set policy to 5 ignored
[  261.550065] mempolicy: Request by 'ps' to set policy to 3 ignored
[  643.744771] tty0tty: loading out-of-tree module taints kernel.
[  643.750941] tty0tty null modem driver v1.4

epsilonrt@r14:~/src/tty0tty/module$ ls /dev/tnt*
/dev/tnt0  /dev/tnt1  /dev/tnt2  /dev/tnt3  /dev/tnt4  /dev/tnt5  /dev/tnt6  /dev/tnt7

 

Also, the same error occurs with another driver like v4l2loopback:

 

epsilonrt@nanopineocore2:~/src/v4l2loopback$ sudo modprobe v4l2loopback
modprobe: ERROR: could not insert 'v4l2loopback': Exec format error

epsilonrt@nanopineocore2:~/src/v4l2loopback$ modinfo v4l2loopback
filename:       /lib/modules/6.12.20-current-sunxi64/updates/v4l2loopback.ko
alias:          char-major-10-255
license:        GPL
version:        0.14.0-25-g8d806ad
author:         Vasily Levin, IOhannes m zmoelnig <zmoelnig@iem.at>,Stefan Diewald,Anton Novikovet al.
description:    V4L2 loopback video device
srcversion:     FC835C7E0E75B1C90BC5391
depends:        videodev
name:           v4l2loopback
vermagic:       6.12.20-current-sunxi64 SMP mod_unload aarch64
parm:           debug:debugging level (higher values == more verbose) (int)
parm:           max_buffers:how many buffers should be allocated [DEFAULT: 2] (int)
parm:           max_openers:how many users can open the loopback device [DEFAULT: 10] (int)
parm:           devices:how many devices should be created (int)
parm:           video_nr:video device numbers (-1=auto, 0=/dev/video0, etc.) (array of int)
parm:           card_label:card labels for each device (array of charp)
parm:           exclusive_caps:whether to announce OUTPUT/CAPTURE capabilities exclusively or not  [DEFAULT: 0] (array of bool)
parm:           max_width:maximum allowed frame width [DEFAULT: 8192] (int)
parm:           max_height:maximum allowed frame height [DEFAULT: 8192] (int)

epsilonrt@nanopineocore2:~/src/v4l2loopback$ uname -a
Linux nanopineocore2 6.12.20-current-sunxi64 #1 SMP Sat Mar 22 19:54:28 UTC 2025 aarch64 GNU/Linux

epsilonrt@nanopineocore2:~/src/v4l2loopback$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Armbian 25.2.3 bookworm
Release:        12
Codename:       bookworm

 

You can find all the details at  armbian/build#8153

 

For all my tests I use the images available for download on the Armbian site.

 

It appears that the driver compliance checking system is corrupted on Armbian sunxi64.

Could the team look into this issue ?

Thanks.

 

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines