Path: csiph.com!1.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: =?UTF-8?B?w4FuZ2VsIE0=?= Newsgroups: linux.debian.kernel Subject: Problem with a custom kernel and my Debian-based distribution Date: Thu, 31 Aug 2023 21:10:01 +0200 Message-ID: X-Mailbox-Line: From debian-kernel-request@lists.debian.org Thu Aug 31 19:00:15 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=0.151 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOJu0YwjtMdNb5qUsfY7adaKVwGP9/9wphpAx3b4+nDhdhIkqzq5l5hS MF7Fl9aHZ+ppgEyY90VJz3s27lHPh6GEZ3H1n3xxwPr2agA= X-Google-SMTP-Source: AGHT+IECseIPNbzsSGk+B4JNg6ONxXYuGZuubDjf49nGd5DtFvwR45l/wxw/lTZBkvQj//S6ag8FpGSLYxtWq+fusY4= X-Received: by 2002:a17:90a:8986:b0:263:5376:b952 with SMTP id v6-20020a17090a898600b002635376b952mr480905pjn.9.1693507432863; Thu, 31 Aug 2023 11:43:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f5de3906043c6c23" X-Mailing-List: archive/latest/139809 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAP0W_m_roitm1xefoNnchc_Pp5j5vhr=8qxXUJFPavt-fA_Z+Q@mail.gmail.com Approved: robomod@news.nic.it Lines: 69 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 31 Aug 2023 14:43:41 -0400 X-Original-Message-ID: Xref: csiph.com linux.debian.kernel:80242 --000000000000f5de3906043c6c23 Content-Type: text/plain; charset="UTF-8" Good afternoon, I send you my best regards. I'm having a problem creating a custom kernel image for my own Debian based distribution, in this case I'm working with version 5.15.124. Let me explain my problem: At the time of making the kernel compilation I take a predefined configuration, it could be from kernel 5.10, that .config file I replace it and then I make some adjustments with make menuconfig, I change the name of the version for the one of my distribution. After that I make a make deb-pkg, to generate the .deb files of the kernel, up to there everything well, it is generated without any problem. Once these packages are generated, I upload them to my own test repository, which basically is the Debian repository, but with modifications of certain packages of the base. Inside that repository is all the kernel 5.10 packages. After that, I build the linux-image-amd64 and linux-headers-amd64 metapackages, with the respective dependencies. When I proceed to generate an ISO image with the livebuild method pointing to my test repositories, the ISO image is generated without problems. When I try to test the ISO image on a computer with strict UEFI I get the following error: *error: invalid file name 'vmlinuz'.error: you need to load the kernel first.Press any key to continue...* When I check the live boot entries I find no problem, as the name matches. This happens only when I want to launch the live system, because if I want to install it, it performs the process and installs the operating system. I hope you can help me with my problem, I appreciate all your support. Greetings and excuse my English. (: --000000000000f5de3906043c6c23 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Good afternoon, I send you my best regards.

I'm= having a problem creating a custom kernel image for my own Debian based di= stribution, in this case I'm working with version 5.15.124.

Let = me explain my problem:
At the time of making the kernel compilation I ta= ke a predefined configuration, it could be from kernel 5.10, that .config f= ile I replace it and then I make some adjustments with make menuconfig, I c= hange the name of the version for the one of my distribution. After that I = make a make deb-pkg, to generate the .deb files of the kernel, up to there = everything well, it is generated without any problem.

Once these pac= kages are generated, I upload them to my own test repository, which basical= ly is the Debian repository, but with modifications of certain packages of = the base. Inside that repository is all the kernel 5.10 packages.

A= fter that, I build the linux-image-amd64 and linux-headers-amd64 metapackag= es, with the respective dependencies. When I proceed to generate an ISO ima= ge with the livebuild method pointing to my test repositories, the ISO imag= e is generated without problems. When I try to test the ISO image on a comp= uter with strict UEFI I get the following error:

error: invalid f= ile name 'vmlinuz'.
error: you need to load the kernel first.
Press any key to continue...

When I check t= he live boot entries I find no problem, as the name matches. This happens o= nly when I want to launch the live system, because if I want to install it,= it performs the process and installs the operating system. I hope you can = help me with my problem, I appreciate all your support. Greetings and excus= e my English. (:
--000000000000f5de3906043c6c23--