Re: Can't Build Linux Kernel from Tutorial
Richard Akintola <[email protected]> Sun, 30 Mar 2025 18:40:23 +0100
| Newsgroups | dev.linux.lists.outreachy |
|---|---|
| Message-ID | <CAMyr_bL-rAZRfPjEWMKHJNApUySeP_Jgkj_iDH+7EK_hCS-Bmg@mail.gmail.com> |
Hi Julia, Having reviewed previous messages on the mailing list, and running the command: perl scripts/checkpatch.pl --strict -f drivers/staging/sm750fb/* | less I found: ------------------------------------ drivers/staging/sm750fb/ddk750_dvi.c ------------------------------------ CHECK: Avoid CamelCase: <sii164GetDeviceID> #19: FILE: drivers/staging/sm750fb/ddk750_dvi.c:19: + .get_device_id = sii164GetDeviceID, CHECK: Avoid CamelCase: <sii164ResetChip> #21: FILE: drivers/staging/sm750fb/ddk750_dvi.c:21: + .reset_chip = sii164ResetChip, CHECK: Avoid CamelCase: <sii164GetChipString> #22: FILE: drivers/staging/sm750fb/ddk750_dvi.c:22: + .get_chip_string = sii164GetChipString, CHECK: Avoid CamelCase: <sii164SetPower> #23: FILE: drivers/staging/sm750fb/ddk750_dvi.c:23: + .set_power = sii164SetPower, CHECK: Avoid CamelCase: <sii164EnableHotPlugDetection> #24: FILE: drivers/staging/sm750fb/ddk750_dvi.c:24: + .enable_hot_plug_detection = sii164EnableHotPlugDetection, CHECK: Avoid CamelCase: <sii164IsConnected> #25: FILE: drivers/staging/sm750fb/ddk750_dvi.c:25: + .is_connected = sii164IsConnected, CHECK: Avoid CamelCase: <sii164CheckInterrupt> #26: FILE: drivers/staging/sm750fb/ddk750_dvi.c:26: + .check_interrupt = sii164CheckInterrupt, CHECK: Avoid CamelCase: <sii164ClearInterrupt> #27: FILE: drivers/staging/sm750fb/ddk750_dvi.c:27: + .clear_interrupt = sii164ClearInterrupt, total: 0 errors, 0 warnings, 8 checks, 62 lines checked I would love to have all the 8 checks done, although I learnt it is one check at a time. Please how do I go about sending the patches, given the fact that same definitions are found in file: drivers/staging/sm750fb/ddk750_dvi.c and file: drivers/staging/sm750fb/ddk750_sii164.h and I don't know which other files they are defined. Richard Akintola On Sat, Mar 29, 2025 at 11:30 AM Julia Lawall <[email protected]> wrote: > > > > On Sat, 29 Mar 2025, Richard Akintola wrote: > > > Hi Julia, > > > > I want to inform you that I have successfully built the kernel. > > After building successfully, I could not install, I searched on how to > > build Linux kernel on Debian, so I found the command "make -jN > > bindeb-pkg" which created a debian packages for easy installation in > > the parent directory which I installed with the command "sudo apt > > install ./*.deb". > > > > Thank you for the support so far, I really appreciate, now nothing is > > standing in the way of sending my patches. > > OK, sounds good. > > It could be good to review the previous messages on the mailing list to > get suggestions of what to focus on and to see what others have done. I > will post some more suggestions this weekend. > > julia > > > > > > Richard Akintola > > > > > > On Wed, Mar 26, 2025 at 11:50 AM Richard Akintola > > <[email protected]> wrote: > > > > > > Thank you Julia, do expect my patches. > > > > > > Richard > > > > > > > > > On Tue, 25 Mar 2025, 21:25 Julia Lawall, <[email protected]> wrote: > > >> > > >> > > >> > > >> On Tue, 25 Mar 2025, Richard Akintola wrote: > > >> > > >> > Hi Julia, > > >> > The reason I haven't sent feedback is that the kernel I built and installed resulted in kernel panic which I am trying to recover from and if I am not able to, I will install a new Os and try again (until I successfully build the kernel). > > >> > > >> OK, thanks for the update. If you can't make it work in th short term, > > >> you could start working on some patches while continuing to try to get the > > >> build to work. > > >> > > >> julia > > >> > > >> > > >> > > >> > > > >> > Thank you for the support so far. > > >> > > > >> > Richard Akintola > > >> > > > >> > On Monday, March 24, 2025, Richard Akintola <[email protected]> wrote: > > >> > > > >> > Thank you Julia, I will go about resolving it as recommended > > >> > > > >> > Richard Akintola > > >> > > > >> > > > >> > On Mon, 24 Mar 2025, 16:06 Julia Lawall, <[email protected]> wrote: > > >> > > > >> > > > >> > On Mon, 24 Mar 2025, Richard Akintola wrote: > > >> > > > >> > > Good to hear from you Julia, > > >> > > > > >> > > For the first question: No, I am not using a VM, I am building the kernel on > > >> > > my machine's Os which is Parrot Linux Os. > > >> > > > > >> > > And as for the configuration: yes, I am reusing the the configuration of my > > >> > > host machine - I copied my machine's configuration to the repository as > > >> > > shown in the tutorial. > > >> > > > >> > > > >> > OK, try to find something related to signatures in your configuration. > > >> > Distro configurations often have this issue. For Debian there is some PEM > > >> > thing. > > >> > > > >> > julia > > >> > > > >> > > > > >> > > Richard Akintola > > >> > > > > >> > > On Mon, 24 Mar 2025, 14:57 Julia Lawall, <[email protected]> wrote: > > >> > > > > >> > > > > >> > > On Mon, 24 Mar 2025, Richard Akintola wrote: > > >> > > > > >> > > > Hello Julia, > > >> > > > > > >> > > > I have been trying to build the Linux Kernel via the tutorial > > >> > > on my > > >> > > > machine to no avail. > > >> > > > > > >> > > > This has prevented me from making a PATCH. > > >> > > > > > >> > > > This is the Os and Kernel version of my machine > > >> > > > OS: Parrot Security 6.3 (lorikeet) x86_64 > > >> > > > Kernel: 6.5.0-13parrot1-amd64 > > >> > > > > >> > > Sort of basic questions are whether you are using a VM and how > > >> > > much memory > > >> > > you have. > > >> > > > > >> > > Afterwards, maybe it is a configuration problems? Are you > > >> > > reusing the > > >> > > configuration of your host machine? Here are some old posts on > > >> > > disabling > > >> > > module signing: > > >> > > > > >> > > https://stackoverflow.com/questions/29806414/how-to-disable-kernel-module-s > > >> > > igning-in-linux > > >> > > https://kernelnewbies.kernelnewbies.narkive.com/kKXLBu8C/how-to-disable-mod > > >> > > ule-verification-failed-signature-and-or-required-key-missing-tainting-ker > > >> > > nel > > >> > > > > >> > > If you change the configuration file, do make olddefconfig > > >> > > afterwards to > > >> > > make sure your changes are take into account. > > >> > > > > >> > > Let me know how it goes. > > >> > > > > >> > > julia > > >> > > > > >> > > > > >> > > > > > >> > > > Below is the error I got while installing the kernel build > > >> > > > > > >> > > > ... > > >> > > > > > >> > > > INSTALL /lib/modules/6.14.0-rc1custom- > > >> > > > ola+/kernel/net/vmw_vsock/vmw_vsock_virtio_transport_common.ko > > >> > > > INSTALL /lib/modules/6.14.0-rc1custom- > > >> > > > ola+/kernel/net/vmw_vsock/hv_sock.ko > > >> > > > INSTALL /lib/modules/6.14.0-rc1custom- > > >> > > > ola+/kernel/net/vmw_vsock/vsock_loopback.ko > > >> > > > INSTALL > > >> > > /lib/modules/6.14.0-rc1custom-ola+/kernel/net/nsh/nsh.ko > > >> > > > INSTALL > > >> > > /lib/modules/6.14.0-rc1custom-ola+/kernel/net/hsr/hsr.ko > > >> > > > INSTALL > > >> > > /lib/modules/6.14.0-rc1custom-ola+/kernel/net/qrtr/qrtr.ko > > >> > > > INSTALL > > >> > > /lib/modules/6.14.0-rc1custom-ola+/kernel/net/qrtr/qrtr- > > >> > > > mhi.ko > > >> > > > DEPMOD /lib/modules/6.14.0-rc1custom-ola+ > > >> > > > INSTALL /boot > > >> > > > run-parts: executing /etc/kernel/postinst.d/dkms > > >> > > 6.14.0-rc1custom-ola+ > > >> > > > /boot/vmlinuz-6.14.0-rc1custom-ola+ > > >> > > > dkms: running auto installation service for kernel > > >> > > 6.14.0-rc1custom- > > >> > > > ola+. > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > readelf: Error: Not an ELF file - it has the wrong magic bytes > > >> > > at the > > >> > > > start > > >> > > > Sign command: > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign- > > >> > > > file > > >> > > > Binary > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign-file not > > >> > > > found, modules won't be signed > > >> > > > > > >> > > > Building module: > > >> > > > Cleaning build area... > > >> > > > make -j4 KERNELRELEASE=6.14.0-rc1custom-ola+ > > >> > > KVER=6.14.0-rc1custom- > > >> > > > ola+........(bad exit status: 2) > > >> > > > Error! Bad return status for module build on kernel: > > >> > > 6.14.0-rc1custom- > > >> > > > ola+ (x86_64) > > >> > > > Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log > > >> > > for more > > >> > > > information. > > >> > > > Sign command: > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign- > > >> > > > file > > >> > > > Binary > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign-file not > > >> > > > found, modules won't be signed > > >> > > > > > >> > > > Building module: > > >> > > > Cleaning build area...(bad exit status: 2) > > >> > > > kernelver=6.14.0-rc1custom-ola+ ./dkms-make.sh...(bad exit > > >> > > status: 2) > > >> > > > Error! Bad return status for module build on kernel: > > >> > > 6.14.0-rc1custom- > > >> > > > ola+ (x86_64) > > >> > > > Consult /var/lib/dkms/realtek- > > >> > > > rtl8814au/5.8.5.1~git20240527.d8208c8/build/make.log for more > > >> > > > information. > > >> > > > Sign command: > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign- > > >> > > > file > > >> > > > Binary > > >> > > /lib/modules/6.14.0-rc1custom-ola+/build/scripts/sign-file not > > >> > > > found, modules won't be signed > > >> > > > > > >> > > > Building module: > > >> > > > Cleaning build area...(bad exit status: 2) > > >> > > > 'make' -j4 KVER=6.14.0-rc1custom-ola+ > > >> > > KSRC=/lib/modules/6.14.0- > > >> > > > rc1custom-ola+/build...(bad exit status: 2) > > >> > > > Error! Bad return status for module build on kernel: > > >> > > 6.14.0-rc1custom- > > >> > > > ola+ (x86_64) > > >> > > > Consult /var/lib/dkms/realtek- > > >> > > > rtl88xxau/5.6.4.2~git20240510.b44d288/build/make.log for more > > >> > > > information. > > >> > > > Error! One or more modules failed to install during > > >> > > autoinstall. > > >> > > > Refer to previous errors for more information. > > >> > > > dkms: autoinstall for kernel: 6.14.0-rc1custom-ola+ failed! > > >> > > > run-parts: /etc/kernel/postinst.d/dkms exited with return code > > >> > > 11 > > >> > > > make[2]: *** [arch/x86/Makefile:321: install] Error 1 > > >> > > > make[1]: *** > > >> > > [/home/laolu/Desktop/Outreachy_Contributions/Linux- > > >> > > > Kernel/git/kernels/staging/Makefile:372: __build_one_by_one] > > >> > > Error 2 > > >> > > > make[1]: Target 'modules_install' not remade because of > > >> > > errors. > > >> > > > make[1]: Target 'install' not remade because of errors. > > >> > > > make: *** [Makefile:251: __sub-make] Error 2 > > >> > > > make: Target 'modules_install' not remade because of errors. > > >> > > > make: Target 'install' not remade because of errors. > > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > > >> > > > > >