All of lore.kernel.org
 help / color / mirror / Atom feed
* "No kernel modules were found" netboot d-i with custom reiser4 kernel.
@ 2015-07-29 14:52 Jose R R
  2015-07-29 15:00 ` Cyril Brulebois
  0 siblings, 1 reply; 6+ messages in thread
From: Jose R R @ 2015-07-29 14:52 UTC (permalink / raw)
  To: Ben Hutchings, debian-boot, ReiserFS Development List

Niltze, all-

Building kernel the 'Debian way':

Replaced abi string at debian/config/defines (from default value of 2)
to a more descriptive string:

[abi]
abiname: reiser4

(guided by hint that debian devs sometimes set abiname string "trunk")

Everything builds beautifully, especially UDEBs for modules/kernel
like couple shown below:
[...]

3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb

Once kernel build is finished, I place the approxiamately 54 generated
UDEBs at the installer/build/localudebs directory and modify
installer/build/config/amd64.cfg

# The version of the kernel to use.
## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
KERNELVERSION = 4.0.0-reiser4-amd64
## KERNELMAJOR = 2.6
KERNELMAJOR = 4.0
KERNELNAME = vmlinuz

save modifications and execute command:
make build_netboot-gtk

The resulting netboot d-i iso image uses the custom kernel to start
the Debian installation -- as can be verified by executing in an
alternate shell: uname -a:
Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
x86_64 GNU/Linux;

nevertheless stops at 'no kernel modules were found' and thus d-i can
not proceed further to install custom built kernel with reiser4
built-into-the-kernel support -- much less to detect/format a
disk/partition win Reiser4.

https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large

Any insight provided will be appreciated. Thanks in advance.


Best Professional Regards.


-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.
  2015-07-29 14:52 "No kernel modules were found" netboot d-i with custom reiser4 kernel Jose R R
@ 2015-07-29 15:00 ` Cyril Brulebois
  2015-07-31  5:49   ` Jose R R
  0 siblings, 1 reply; 6+ messages in thread
From: Cyril Brulebois @ 2015-07-29 15:00 UTC (permalink / raw)
  To: Jose R R; +Cc: Ben Hutchings, debian-boot, ReiserFS Development List

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

Hi,

Jose R R <Jose.r.r@metztli-it.com> (2015-07-29):
> Niltze, all-
> 
> Building kernel the 'Debian way':
> 
> Replaced abi string at debian/config/defines (from default value of 2)
> to a more descriptive string:
> 
> [abi]
> abiname: reiser4
> 
> (guided by hint that debian devs sometimes set abiname string "trunk")
> 
> Everything builds beautifully, especially UDEBs for modules/kernel
> like couple shown below:
> [...]
> 
> 3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
> 34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb
> 
> Once kernel build is finished, I place the approxiamately 54 generated
> UDEBs at the installer/build/localudebs directory and modify
> installer/build/config/amd64.cfg
> 
> # The version of the kernel to use.
> ## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
> KERNELVERSION = 4.0.0-reiser4-amd64
> ## KERNELMAJOR = 2.6
> KERNELMAJOR = 4.0
> KERNELNAME = vmlinuz
> 
> save modifications and execute command:
> make build_netboot-gtk
> 
> The resulting netboot d-i iso image uses the custom kernel to start
> the Debian installation -- as can be verified by executing in an
> alternate shell: uname -a:
> Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
> x86_64 GNU/Linux;
> 
> nevertheless stops at 'no kernel modules were found' and thus d-i can
> not proceed further to install custom built kernel with reiser4
> built-into-the-kernel support -- much less to detect/format a
> disk/partition win Reiser4.
> 
> https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large
> 
> Any insight provided will be appreciated. Thanks in advance.

Stuff you put under localudebs/ is only used to replace/complement
what's in the archive if something pulls it in. You probably want to
add some packages to some list under build/pkg-lists.

There's also a monolithic target you could use to bundle almost
everything into your image. This is a bigger hammer though.

Mraw,
KiBi.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.
  2015-07-29 15:00 ` Cyril Brulebois
@ 2015-07-31  5:49   ` Jose R R
  2015-08-13  9:45     ` Jose R R
  0 siblings, 1 reply; 6+ messages in thread
From: Jose R R @ 2015-07-31  5:49 UTC (permalink / raw)
  To: Cyril Brulebois; +Cc: Ben Hutchings, debian-boot, ReiserFS Development List

On Wed, Jul 29, 2015 at 8:00 AM, Cyril Brulebois <kibi@debian.org> wrote:
> Hi,
>
> Jose R R <Jose.r.r@metztli-it.com> (2015-07-29):
>> Niltze, all-
>>
>> Building kernel the 'Debian way':
>>
>> Replaced abi string at debian/config/defines (from default value of 2)
>> to a more descriptive string:
>>
>> [abi]
>> abiname: reiser4
>>
>> (guided by hint that debian devs sometimes set abiname string "trunk")
>>
>> Everything builds beautifully, especially UDEBs for modules/kernel
>> like couple shown below:
>> [...]
>>
>> 3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
>> 34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb
>>
>> Once kernel build is finished, I place the approxiamately 54 generated
>> UDEBs at the installer/build/localudebs directory and modify
>> installer/build/config/amd64.cfg
>>
>> # The version of the kernel to use.
>> ## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
>> KERNELVERSION = 4.0.0-reiser4-amd64
>> ## KERNELMAJOR = 2.6
>> KERNELMAJOR = 4.0
>> KERNELNAME = vmlinuz
>>
>> save modifications and execute command:
>> make build_netboot-gtk
>>
>> The resulting netboot d-i iso image uses the custom kernel to start
>> the Debian installation -- as can be verified by executing in an
>> alternate shell: uname -a:
>> Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
>> x86_64 GNU/Linux;
>>
>> nevertheless stops at 'no kernel modules were found' and thus d-i can
>> not proceed further to install custom built kernel with reiser4
>> built-into-the-kernel support -- much less to detect/format a
>> disk/partition win Reiser4.
>>
>> https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large
>>
>> Any insight provided will be appreciated. Thanks in advance.
>
> Stuff you put under localudebs/ is only used to replace/complement
> what's in the archive if something pulls it in. You probably want to
> add some packages to some list under build/pkg-lists.

According to the Debian Installer online reference <
https://wiki.debian.org/DebianInstaller/Modify/CustomKernel > it
suffices to place all the *.udebs at  build/localudebs directory.
There is no other example and/or guidance on how to go about
populating, say (from build/README)

* Anything listed in pkg-lists/local and pkg-lists/*/local is included in
  the image that is built. This is to provide an easy way to add extra
  udebs to a test image.

Thus, there is no indication where the installer will be picking up
the full 34M DEB linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb so
as to be an option during the installation procedure.

>
> There's also a monolithic target you could use to bundle almost
> everything into your image. This is a bigger hammer though.
>

It fails:
fakeroot make build_monolithic
[...]
Makefile:637: recipe for target 'stamps/get_udebs-monolithic-stamp' failed
Makefile:284: recipe for target '_build' failed
Makefile:278: recipe for target 'build_monolithic' failed

> Mraw,
> KiBi.
Appreciate your reply.


Best Professional Regards.


-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.
  2015-07-31  5:49   ` Jose R R
@ 2015-08-13  9:45     ` Jose R R
  2015-08-13 10:20       ` Ben Hutchings
  0 siblings, 1 reply; 6+ messages in thread
From: Jose R R @ 2015-08-13  9:45 UTC (permalink / raw)
  To: Cyril Brulebois; +Cc: Ben Hutchings, debian-boot, ReiserFS Development List

On Thu, Jul 30, 2015 at 10:49 PM, Jose R R <Jose.r.r@metztli-it.com> wrote:
> On Wed, Jul 29, 2015 at 8:00 AM, Cyril Brulebois <kibi@debian.org> wrote:
>> Hi,
>>
>> Jose R R <Jose.r.r@metztli-it.com> (2015-07-29):
>>> Niltze, all-
>>>
>>> Building kernel the 'Debian way':
>>>
>>> Replaced abi string at debian/config/defines (from default value of 2)
>>> to a more descriptive string:
>>>
>>> [abi]
>>> abiname: reiser4
>>>
>>> (guided by hint that debian devs sometimes set abiname string "trunk")
>>>
>>> Everything builds beautifully, especially UDEBs for modules/kernel
>>> like couple shown below:
>>> [...]
>>>
>>> 3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
>>> 34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb
>>>
>>> Once kernel build is finished, I place the approxiamately 54 generated
>>> UDEBs at the installer/build/localudebs directory and modify
>>> installer/build/config/amd64.cfg
>>>
>>> # The version of the kernel to use.
>>> ## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
>>> KERNELVERSION = 4.0.0-reiser4-amd64
>>> ## KERNELMAJOR = 2.6
>>> KERNELMAJOR = 4.0
>>> KERNELNAME = vmlinuz
>>>
>>> save modifications and execute command:
>>> make build_netboot-gtk
>>>
>>> The resulting netboot d-i iso image uses the custom kernel to start
>>> the Debian installation -- as can be verified by executing in an
>>> alternate shell: uname -a:
>>> Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
>>> x86_64 GNU/Linux;
>>>
>>> nevertheless stops at 'no kernel modules were found' and thus d-i can
>>> not proceed further to install custom built kernel with reiser4
>>> built-into-the-kernel support -- much less to detect/format a
>>> disk/partition win Reiser4.
>>>
>>> https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large
>>>
>>> Any insight provided will be appreciated. Thanks in advance.
>>
>> Stuff you put under localudebs/ is only used to replace/complement
>> what's in the archive if something pulls it in. You probably want to
>> add some packages to some list under build/pkg-lists.
>
I am making progress as I have built UDEBs for mkfs.reiser4 and fsck.reiser4:
mkreiser4-udeb_1.0.9-2_amd64.udeb
reiser4progs-udeb_1.0.9-2_amd64.udeb

which in turn I have also placed under build/localudebs.

Prior to d-i's: make build_netboot,

I have also specified at build/pkg-lists/netboot/amd64.cfg

mkreiser4-udeb
reiser4progs-udeb
...
ext4-modules-${kernel:Version}
jfs-modules-${kernel:Version}

the above ext/jfs module UDEBs were generated automatically by
building kernel the 'Debian way', but...

QUESTION:
How do I specify -- prior to building a reiser4-patched kernel the
'debian way' -- a directive to build the *extra* reiser4 module  UDEB?

Before/After specifying reiser4 as a module in .config (i.e., make -C
debian/build/build_amd64_none_amd64 menuconfig ), I have tried adding
the reiser4 directive to the debian/rules.gen inside the kernel tree
source -- still it does not generate a reiser4 module UDEB.

It seems the reiser4 module is needed for the d-i to format and
recognize reiser4. Note that by Ctrl -Alt -Fn I am able to go under
the installer shell and format in reiser4 and subsequently modify the
/etc/fstab from an di-JFS-formatted partition --using nano;
subsequently the installer will continue the installation of Debian
into reiser4-formatted media *unaware* that it was *tricked*.

< https://pbs.twimg.com/media/CMR2xY_UEAAA4M3.png:large >

Thanks in advance for any insight.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.
  2015-08-13  9:45     ` Jose R R
@ 2015-08-13 10:20       ` Ben Hutchings
  2015-08-24  8:15         ` Jose R R
  0 siblings, 1 reply; 6+ messages in thread
From: Ben Hutchings @ 2015-08-13 10:20 UTC (permalink / raw)
  To: Jose R R, Cyril Brulebois; +Cc: debian-boot, ReiserFS Development List

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

On Thu, 2015-08-13 at 02:45 -0700, Jose R R wrote:
[...]
> QUESTION:
> How do I specify -- prior to building a reiser4-patched kernel the
> 'debian way' -- a directive to build the *extra* reiser4 module  UDEB?
> 
> Before/After specifying reiser4 as a module in .config (i.e., make -C
> debian/build/build_amd64_none_amd64 menuconfig ), I have tried adding
> the reiser4 directive to the debian/rules.gen inside the kernel tree
> source -- still it does not generate a reiser4 module UDEB.
[...]

Look under debian/installer in the linux source package and read the
kernel-wedge documentation.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.
  2015-08-13 10:20       ` Ben Hutchings
@ 2015-08-24  8:15         ` Jose R R
  0 siblings, 0 replies; 6+ messages in thread
From: Jose R R @ 2015-08-24  8:15 UTC (permalink / raw)
  To: Ben Hutchings; +Cc: Cyril Brulebois, debian-boot, ReiserFS Development List

Niltze, all!


On Thu, Aug 13, 2015 at 3:20 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Thu, 2015-08-13 at 02:45 -0700, Jose R R wrote:
> [...]
>> QUESTION:
>> How do I specify -- prior to building a reiser4-patched kernel the
>> 'debian way' -- a directive to build the *extra* reiser4 module  UDEB?
>>
>> Before/After specifying reiser4 as a module in .config (i.e., make -C
>> debian/build/build_amd64_none_amd64 menuconfig ), I have tried adding
>> the reiser4 directive to the debian/rules.gen inside the kernel tree
>> source -- still it does not generate a reiser4 module UDEB.
> [...]
>
> Look under debian/installer in the linux source package and read the
> kernel-wedge documentation.
>

After some effort, I was successful in creating the *extra*
reiser4-modules UDEB:
reiser4-modules-4.1.0-2-amd64-di_4.1.5-2_amd64.udeb
for
kernel-image-4.1.0-2-amd64-di_4.1.5-2_amd64.udeb

I included relevant directives in the build/pkg-lists/netboot/amd64.cfg, thus:
[...]
fat-modules-${kernel:Version}
ext4-modules-${kernel:Version}   # Without this, d-i won't know about Ext2/3/4
jfs-modules-${kernel:Version}      # Without this, d-i won't know about JFS
reiser4-modules-${kernel:Version} # Thus I thought this would allow
d-i to *know* about reiser4
mkreiser4-udeb                           # This provides mkfs.reiser4 to d-i
reiser4progs-udeb                        # This provides fsck.reiser4 to d-i
[...]

After "make build_netboot" finished and tested the installation mini.iso:

lsmod: shows reiser4 module (which I loaded manually from the d-i shell utility)
https://pbs.twimg.com/media/CNKHCDyUkAA0lic.png:large

However d-i partman still does not recognize the reiser4-formatted partition:
https://pbs.twimg.com/media/CNKHCDmUcAAc6pT.png:large

Which means, I now should attempt to create a partman-reiser4 udeb for d-i?

Thank you for all your help and I appreciate your hints and suggestions.


Best professional Regards.


-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-08-24  8:15 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-29 14:52 "No kernel modules were found" netboot d-i with custom reiser4 kernel Jose R R
2015-07-29 15:00 ` Cyril Brulebois
2015-07-31  5:49   ` Jose R R
2015-08-13  9:45     ` Jose R R
2015-08-13 10:20       ` Ben Hutchings
2015-08-24  8:15         ` Jose R R

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.