-
Notifications
You must be signed in to change notification settings - Fork 38
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
Bookworm Support #25
Comments
@XECDesign How can we determine the head commit for the kernel (even if we omit the Debian patches)? Which package installs the kernel? |
You could do something along the lines of For that dpkg command, the equivalent would be something like |
Thanks - that gets me further:
The second of these hashes is a recognised kernel commit in rpi-6.1.y, one that matches the rpi-firmware stable release of Oct 24, but the first isn't. |
I think because it was built from a PR. raspberrypi/linux@ccf1586 |
Hi @XECDesign , |
Can you let me know which module you're building and I can see if I can write some instructions? |
That's great! I'm using Pi5 and Pi4. |
I mean which linux driver are you building as a module, not which pi model you're using. |
I'll just leave links containing the answers regardless of what you're doing. To get the exact source the kernel was built from (you'd need to know a little about debian packages): To build external modules, everything you need is already provided int he headers package, so you can just do this: EDIT: An example to build the wireguard module...
|
Sorry I misunderstood, I was thinking it doesn't seem to make a difference which kernel module is used |
Thank you very much, I will give it a try! |
Hi @XECDesign Is there a way to build it from kernel source using cross compilation? The method I used before: |
Not without downloading the relevant .deb file and extracting the necessary files from it. |
Thank you for your reply. |
Hi @XECDesign |
It might be a factor, but there are many other reasons. Taking build artifacts from two completely different build environments and different sources is a non-starter altogether.
The 'upstream' part of the source comes straight from kernel.org. You can take a look at the debian source package to see how everything is generated. The tarball you get from the linux-source-* package may or may not have some additional patches applied. I didn't look too closely, since I only used it as an example. It's probably to take further questions like that to the forum. |
Got it! |
The content of this issue has drifted from the original post. Is it expected that rpi-source will be fixed? |
It's underway. |
Thank you. I will await hearing that it's ready for use. |
rpi-source always succeeds on Bullseye but fails on Bookworm if rpi-update has not previously been run (which creates /boot/firmware/.firmware_revision):
*** SoC: BCM2711
ERROR:
Can't find a source for this kernel
Linux raspberrypi 6.1.0-rpi4-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64 GNU/Linux
The text was updated successfully, but these errors were encountered: