missing kernel headers for aarch64

Open
#6,002 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux

Research direction

Start by reproducing the reported steps on a Raspberry Pi 4 running Raspberry Pi OS Bookworm with the 6.6.18-v8+ kernel, then inspect the raspberrypi-kernel-headers package and /lib/modules/$(uname -r)/build symlink. Done means the aarch64 headers directory exists and a kernel driver can build against it.

Written by the indexing model from the issue text.

Description

Describe the bug

Missing kernel headers directory for aarch64 v8 kernel, /lib/modules/$(uname -r)/build is a symlink for non existing folder.

Steps to reproduce the behaviour
  1. Install raspi os bookworm aarch64
  2. rpi-update rpi-6.6.y
  3. sudo apt install raspberrypi-kernel-headers
  4. ls /lib/modules/$(uname -r)/build

Expected result: kernel headers directory is present

Actual result: missing folder, /lib/modules/$(uname -r)/build is a symlink for non existing folder.

Device (s)

Raspberry Pi 4 Mod. B

System

$ cat /etc/rpi-issue
Raspberry Pi reference 2023-09-22
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 40f37458ae7cadea1aec913ae10b5e7008ebce0a, stage4

$ vcgencmd version
Dec 8 2023 12:36:15
Copyright (c) 2012 Broadcom
version e02d33b3122450accf9dea471a177d3b5623f5ad (clean) (release) (start)

$ uname -a
Linux raspi 6.6.18-v8+ #1 SMP PREEMPT Thu Feb 29 13:37:10 UTC 2024 aarch64 GNU/Linux

Logs

No response

Additional context

I need to build kernel driver, for armhf it compiles ok. Any idea on how to get kernel headers for aarch64?

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.