-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
will not work on Manjaro Linux #28
Comments
ds2k5
changed the title
not found. reading /boot/System.map
will not work on Manjaro Linux
Jan 9, 2018
Worked for me on Manjaro with Kernel 4.15, latest preview. |
Thanks! with kernel 4.14.12 it worked |
Doesn't work on Archlinux32 for the same reason:
|
I get the same result on Arch with both 4.14.15-1-hardened and 4.9.78-1-lts. I assumed it was a kernel hardening issue at first. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
wann try on Manjaro Linux but looks did not work.
$ ./run.sh
looking for linux_proc_banner in /proc/kallsyms
protected. requires root
++ find_linux_proc_banner /proc/kallsyms sudo
++ sudo sed -n -re 's/^([0-9a-f][1-9a-f][0-9a-f]) .* linux_proc_banner$/\1/p' /proc/kallsyms
[sudo] Passwort für user01:
not found. reading /boot/System.map-4.4.109-2-MANJARO
+++ uname -r
++ find_linux_proc_banner /boot/System.map-4.4.109-2-MANJARO sudo
++ sudo sed -n -re 's/^([0-9a-f][1-9a-f][0-9a-f]) .* linux_proc_banner$/\1/p' /boot/System.map-4.4.109-2-MANJARO
sed: /boot/System.map-4.4.109-2-MANJARO kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
not found. reading /boot/System.map
++ find_linux_proc_banner /boot/System.map sudo
++ sudo sed -n -re 's/^([0-9a-f][1-9a-f][0-9a-f]) .* linux_proc_banner$/\1/p' /boot/System.map
sed: /boot/System.map kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
can't find linux_proc_banner, unable to test at all
$ uname -a
Linux spg006936 4.4.109-2-MANJARO #1 SMP PREEMPT Thu Jan 4 03:18:20 UTC 2018 x86_64 GNU/Linux
Here are the files in /boot, there is no .map file
$ ls -la /boot/
insgesamt 45808
drwxr-xr-x 7 root root 1024 9. Jan 06:20 .
drwxr-xr-x 17 root root 4096 4. Dez 07:32 ..
drwxr-xr-x 3 root root 1024 13. Jul 2015 EFI
drwxr-xr-x 6 root root 1024 9. Jan 06:23 grub
-rw-r--r-- 1 root root 28111482 9. Jan 06:23 initramfs-4.4-x86_64-fallback.img
-rw-r--r-- 1 root root 12425312 9. Jan 06:23 initramfs-4.4-x86_64.img
-rw-r--r-- 1 root root 1586688 18. Nov 20:44 intel-ucode.img
-rw-r--r-- 1 root root 22 4. Jan 04:19 linux44-x86_64.kver
drwx------ 2 root root 12288 21. Sep 2015 lost+found
drwxr-xr-x 2 root root 1024 22. Aug 2016 memtest86+
drwxr-xr-x 2 root root 1024 7. Mär 2017 syslinux
-rw-r--r-- 1 root root 4569408 4. Jan 04:19 vmlinuz-4.4-x86_64
The text was updated successfully, but these errors were encountered: