View Issue Details

IDProjectCategoryView StatusLast Update
0008657Kali LinuxGeneral Bugpublic2025-03-20 13:02
Reporterpalmieri0884 Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0008657: Raspiberry Pi 4 Kernel and headers
Description

I'm having this error when trying to run LiME forensic to capture de live memory.

┌──(root㉿kali-raspberry-pi)-[/]
└─# git clone https://github.com/504ensicsLabs/LiME.git
Cloning into 'LiME'...
remote: Enumerating objects: 370, done.
remote: Counting objects: 100% (21/21), done.
remote: Compressing objects: 100% (17/17), done.
remote: Total 370 (delta 10), reused 12 (delta 4), pack-reused 349
Receiving objects: 100% (370/370), 1.61 MiB | 607.00 KiB/s, done.
Resolving deltas: 100% (199/199), done.

┌──(root㉿kali-raspberry-pi)-[/]
└─# cd /LiME

┌──(root㉿kali-raspberry-pi)-[/LiME]
└─# cd src

┌──(root㉿kali-raspberry-pi)-[/LiME/src]
└─# make
make -C /lib/modules/5.15.44-Re4son-v8l+/build M="/LiME/src" modules
make[1]: Entering directory '/usr/src/linux-headers-5.15.44-Re4son-v8l+'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (Debian 11.2.0-19) 11.2.0
You are using: gcc (Debian 13.2.0-13) 13.2.0
CC [M] /LiME/src/tcp.o
CC [M] /LiME/src/disk.o
CC [M] /LiME/src/main.o
CC [M] /LiME/src/hash.o
CC [M] /LiME/src/deflate.o
LD [M] /LiME/src/lime.o
MODPOST /LiME/src/Module.symvers
CC [M] /LiME/src/lime.mod.o
LD [M] /LiME/src/lime.ko
make[1]: Leaving directory '/usr/src/linux-headers-5.15.44-Re4son-v8l+'
strip --strip-unneeded lime.ko
mv lime.ko lime-5.15.44-Re4son-v8l+.ko

┌──(root㉿kali-raspberry-pi)-[/LiME/src]
└─# insmod ./lime-5.15.44-Re4son-v8l+ko "path=../RPI4Before.mem format=raw"
insmod: ERROR: could not load module ./lime-5.15.44-Re4son-v8l+ko: No such file or directory

Activities

kali-bugreport

kali-bugreport

2024-03-02 20:50

reporter   ~0018962

Why posting a problem in a 3rdparty software in a bug tracker for Kali?

You should go to the support of that software instead.

palmieri0884

palmieri0884

2024-03-02 23:56

reporter   ~0018964

Because it is not a problem in Lime forensic software, it is a problem in Kali and RPI Kernel and headers. But thanks for you usefull help.

kali-bugreport

kali-bugreport

2024-03-03 07:06

reporter   ~0018965

If a software fails to build it is not a problem of the underlying operating system.

palmieri0884

palmieri0884

2024-03-03 08:45

reporter   ~0018966

is not a software problem I have it working perfect in other RPI, if you can’t help stop saying is a software problem.

kali-bugreport

kali-bugreport

2024-03-03 09:55

reporter   ~0018967

It is not a Kali problem / bug, you are just wrong here.

palmieri0884

palmieri0884

2024-03-03 12:27

reporter   ~0018968

ok mate you are correct, thank you so much �

g0tmi1k

g0tmi1k

2025-03-20 13:02

administrator   ~0020414

This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

Issue History

Date Modified Username Field Change
2024-03-02 18:22 palmieri0884 New Issue
2024-03-02 20:50 kali-bugreport Note Added: 0018962
2024-03-02 23:56 palmieri0884 Note Added: 0018964
2024-03-03 07:06 kali-bugreport Note Added: 0018965
2024-03-03 08:45 palmieri0884 Note Added: 0018966
2024-03-03 09:55 kali-bugreport Note Added: 0018967
2024-03-03 12:27 palmieri0884 Note Added: 0018968
2025-03-20 13:02 g0tmi1k Note Added: 0020414
2025-03-20 13:02 g0tmi1k Status new => closed