[Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

Hello Andi and Julia,

Thank you so much for your responses.

I need some help with moving forward in the tutorial.

I am at the "Make a driver change" step of the first patch tutorial. The tutorial made the look like finding the _main.c file of the driver and locating its probe function was quite easy.

I ran lsmod as instructed and picked e1000e. I used git grep e1000e -- '*Makefile' to search for its subdirectory in the kernel tree. This is where it got tricky for me, I thought I would find a .c file like e1000e.c or e1000e_main.c as was shown in the VM example(I'm using native Linux) but I can see in the subdirectory are .o files that I can't modify. And I don't what to do or how to find the probe function I'm supposed to modify

I tried the above process for a couple more names in the list returned by lsmod and it is the same issue.

Please advise

Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Deepak R Varma]

On Tue, Oct 10, 2023 at 05:20:33AM +0100, Gilbert Adikankwu wrote:
> Hello Andi and Julia,
>
> Thank you so much for your responses.
>
> I need some help with moving forward in the tutorial.
>
> I am at the "Make a driver change" step of the first patch tutorial. The tutorial made the look like finding the _main.c file of the driver and locating its probe function was quite easy.
>
> I ran lsmod as instructed and picked e1000e. I used git grep e1000e -- '*Makefile' to search for its subdirectory in the kernel tree. This is where it got tricky for me, I thought I would find a .c file like e1000e.c or e1000e_main.c as was shown in the VM example(I'm using native Linux) but I can see in the subdirectory are .o files that I can't modify. And I don't what to do or how to find the probe function I'm supposed to modify
>

Hello,
Are you saying you do not have any .c files under the
drivers/net/ethernet/intel/e1000e/ directory?

On my machine, I see the following on trying to locate the probe function of
this driver:

	drv@runicha:~/git/kernels/linux-next$ grep 'probe(' drivers/net/ethernet/intel/e1000e/*.c
	drivers/net/ethernet/intel/e1000e/netdev.c:static int e1000_probe(struct pci_dev *pdev, const struct pci_device_id *ent)

Can you check if you see something similar?

Thanks,
Deepak.

> I tried the above process for a couple more names in the list returned by lsmod and it is the same issue.
>
> Please advise
>
> Thanks
> Gilbert
>
>

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

Hello Deepak, 

Thank you for your response. Yes I realised that my message was worded
as though I couldn't find any .c files in the
drivers/net/ethernet/intel/e1000e/ directory. But your reply made me
realise that what I really needed was a way to search all files in the
subdirectory for the probe function. And your grep syntax provided the perfect
solution.

Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

Hello Deepak,

Thank you for your response. Yes I realised that my message was worded
as though I couldn't find any .c files in the
drivers/net/ethernet/intel/e1000e/ directory. But your reply made me
realise that what I really needed was a way to search all files in the
subdirectory for the probe function. And your grep syntax provided the perfect
solution.

Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Andi Shyti]

Hi Gilbert,

On Tue, Oct 10, 2023 at 05:20:33AM +0100, Gilbert Adikankwu wrote:
> Hello Andi and Julia,
> 
> Thank you so much for your responses.
> 
> I need some help with moving forward in the tutorial.
> 
> I am at the "Make a driver change" step of the first patch tutorial. The tutorial made the look like finding the _main.c file of the driver and locating its probe function was quite easy.
> 
> I ran lsmod as instructed and picked e1000e. I used git grep e1000e -- '*Makefile' to search for its subdirectory in the kernel tree. This is where it got tricky for me, I thought I would find a .c file like e1000e.c or e1000e_main.c as was shown in the VM example(I'm using native Linux) but I can see in the subdirectory are .o files that I can't modify. And I don't what to do or how to find the probe function I'm supposed to modify

Long story short: the .o files are object binary files that are
not supposed to be edited. The object files are then linked
together in a single file that will be your final driver's
object.

Check the file drivers/net/ethernet/intel/e1000e/Makefile:

obj-$(CONFIG_E1000E) += e1000e.o

e1000e-objs := 82571.o ich8lan.o 80003es2lan.o \
               mac.o manage.o nvm.o phy.o \
               param.o ethtool.o netdev.o ptp.o

This means that the compilation process will produce the objects
in the second group of .o files. At the end an e1000e.o file
will contain all of them.

It doesn't mean that you will necessarily have a e1000e.c file.

As Deepak recommended, you could find the probe file with the
grep command. You found it in netdev.c. As you can see from the
Makefile, you will also have a netdev.o that will end up inside
the e1000e.o.

This means that not always the driver is called the same way as
its directory or the final .o file.

This is true also you end up working for the i915 sysfs project.
Indeed the big set of files in the drivers/gpu/drm/i915/ with all
the subdirectories, will, at the end, create one single object,
called i915.o, even though there is no i915.c file in it.

I hope this cleared a bit things as in this list I have often
seen people looking for source code in .o files.

Andi

> I tried the above process for a couple more names in the list returned by lsmod and it is the same issue.
> 
> Please advise
> 
> Thanks
> Gilbert
> 

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Julia Lawall]

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



On Tue, 10 Oct 2023, Gilbert Adikankwu wrote:

>
>
> On Tuesday, October 10, 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
>       Hi Gilbert,
>
>       On Tue, Oct 10, 2023 at 05:20:33AM +0100, Gilbert Adikankwu
>       wrote:
>       > Hello Andi and Julia,
>       >
>       > Thank you so much for your responses.
>       >
>       > I need some help with moving forward in the tutorial.
>       >
>       > I am at the "Make a driver change" step of the first patch
>       tutorial. The tutorial made the look like finding the _main.c
>       file of the driver and locating its probe function was quite
>       easy.
>       >
>       > I ran lsmod as instructed and picked e1000e. I used git grep
>       e1000e -- '*Makefile' to search for its subdirectory in the
>       kernel tree. This is where it got tricky for me, I thought I
>       would find a .c file like e1000e.c or e1000e_main.c as was shown
>       in the VM example(I'm using native Linux) but I can see in the
>       subdirectory are .o files that I can't modify. And I don't what
>       to do or how to find the probe function I'm supposed to modify
>
>       Long story short: the .o files are object binary files that are
>       not supposed to be edited. The object files are then linked
>       together in a single file that will be your final driver's
>       object.
>
>       Check the file drivers/net/ethernet/intel/e1000e/Makefile:
>
>       obj-$(CONFIG_E1000E) += e1000e.o
>
>       e1000e-objs := 82571.o ich8lan.o 80003es2lan.o \
>                      mac.o manage.o nvm.o phy.o \
>                      param.o ethtool.o netdev.o ptp.o
>
>       This means that the compilation process will produce the objects
>       in the second group of .o files. At the end an e1000e.o file
>       will contain all of them.
>
>       It doesn't mean that you will necessarily have a e1000e.c file.
>
>       As Deepak recommended, you could find the probe file with the
>       grep command. You found it in netdev.c. As you can see from the
>       Makefile, you will also have a netdev.o that will end up inside
>       the e1000e.o.
>
>       This means that not always the driver is called the same way as
>       its directory or the final .o file.
>
>       This is true also you end up working for the i915 sysfs project.
>       Indeed the big set of files in the drivers/gpu/drm/i915/ with
>       all
>       the subdirectories, will, at the end, create one single object,
>       called i915.o, even though there is no i915.c file in it.
>
>       I hope this cleared a bit things as in this list I have often
>       seen people looking for source code in .o files.
>
>       Andi
>
>       > I tried the above process for a couple more names in the list
>       returned by lsmod and it is the same issue.
>       >
>       > Please advise
>       >
>       > Thanks
>       > Gilbert
>       >
>
>
> Hello Andi,
>
> Thank you for the explanation. It has helped my understanding. 
>
> I have another issue, I tried compiling after modifying and it compiled
> successfully. But when I tried to install so I can reboot, I got this
> error: 
>
> zstd: error 25 : Write error : No space left on device (cannot write
> compressed block) 
> E: mkinitramfs failure zstd -q -1 -T0 25
> update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> make[2]: *** [arch/x86/Makefile:292: install] Error 1
> make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> __build_one_by_one] Error 2
> make: *** [Makefile:234: __sub-make] Error 2

You have too little space in the partition that contains /boot?

julia

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

On Tue, Oct 10, 2023 at 5:36 PM Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>
> On Tue, 10 Oct 2023, Gilbert Adikankwu wrote:
>
> >
> >
> > On Tuesday, October 10, 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> >       Hi Gilbert,
> >
> >       On Tue, Oct 10, 2023 at 05:20:33AM +0100, Gilbert Adikankwu
> >       wrote:
> >       > Hello Andi and Julia,
> >       >
> >       > Thank you so much for your responses.
> >       >
> >       > I need some help with moving forward in the tutorial.
> >       >
> >       > I am at the "Make a driver change" step of the first patch
> >       tutorial. The tutorial made the look like finding the _main.c
> >       file of the driver and locating its probe function was quite
> >       easy.
> >       >
> >       > I ran lsmod as instructed and picked e1000e. I used git grep
> >       e1000e -- '*Makefile' to search for its subdirectory in the
> >       kernel tree. This is where it got tricky for me, I thought I
> >       would find a .c file like e1000e.c or e1000e_main.c as was shown
> >       in the VM example(I'm using native Linux) but I can see in the
> >       subdirectory are .o files that I can't modify. And I don't what
> >       to do or how to find the probe function I'm supposed to modify
> >
> >       Long story short: the .o files are object binary files that are
> >       not supposed to be edited. The object files are then linked
> >       together in a single file that will be your final driver's
> >       object.
> >
> >       Check the file drivers/net/ethernet/intel/e1000e/Makefile:
> >
> >       obj-$(CONFIG_E1000E) += e1000e.o
> >
> >       e1000e-objs := 82571.o ich8lan.o 80003es2lan.o \
> >                      mac.o manage.o nvm.o phy.o \
> >                      param.o ethtool.o netdev.o ptp.o
> >
> >       This means that the compilation process will produce the objects
> >       in the second group of .o files. At the end an e1000e.o file
> >       will contain all of them.
> >
> >       It doesn't mean that you will necessarily have a e1000e.c file.
> >
> >       As Deepak recommended, you could find the probe file with the
> >       grep command. You found it in netdev.c. As you can see from the
> >       Makefile, you will also have a netdev.o that will end up inside
> >       the e1000e.o.
> >
> >       This means that not always the driver is called the same way as
> >       its directory or the final .o file.
> >
> >       This is true also you end up working for the i915 sysfs project.
> >       Indeed the big set of files in the drivers/gpu/drm/i915/ with
> >       all
> >       the subdirectories, will, at the end, create one single object,
> >       called i915.o, even though there is no i915.c file in it.
> >
> >       I hope this cleared a bit things as in this list I have often
> >       seen people looking for source code in .o files.
> >
> >       Andi
> >
> >       > I tried the above process for a couple more names in the list
> >       returned by lsmod and it is the same issue.
> >       >
> >       > Please advise
> >       >
> >       > Thanks
> >       > Gilbert
> >       >
> >
> >
> > Hello Andi,
> >
> > Thank you for the explanation. It has helped my understanding.
> >
> > I have another issue, I tried compiling after modifying and it compiled
> > successfully. But when I tried to install so I can reboot, I got this
> > error:
> >
> > zstd: error 25 : Write error : No space left on device (cannot write
> > compressed block)
> > E: mkinitramfs failure zstd -q -1 -T0 25
> > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > __build_one_by_one] Error 2
> > make: *** [Makefile:234: __sub-make] Error 2
>
> You have too little space in the partition that contains /boot?
>
> julia

The tutorial that guided me through the installation process just told
me to allocate 1GB for boot, is that too small? Do I need to wipe the
installation and redo it?

Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Andi Shyti]

Hi Gilbert,

> > I have another issue, I tried compiling after modifying and it compiled
> > successfully. But when I tried to install so I can reboot, I got this
> > error: 
> >
> > zstd: error 25 : Write error : No space left on device (cannot write
> > compressed block) 
> > E: mkinitramfs failure zstd -q -1 -T0 25
> > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > __build_one_by_one] Error 2
> > make: *** [Makefile:234: __sub-make] Error 2
> 
> You have too little space in the partition that contains /boot?

What does "df -h" say?

Andi

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

On Tue, Oct 10, 2023 at 5:43 PM Andi Shyti <andi.shyti@linux.intel.com> wrote:
>
> Hi Gilbert,
>
> > > I have another issue, I tried compiling after modifying and it compiled
> > > successfully. But when I tried to install so I can reboot, I got this
> > > error:
> > >
> > > zstd: error 25 : Write error : No space left on device (cannot write
> > > compressed block)
> > > E: mkinitramfs failure zstd -q -1 -T0 25
> > > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > > __build_one_by_one] Error 2
> > > make: *** [Makefile:234: __sub-make] Error 2
> >
> > You have too little space in the partition that contains /boot?
>
> What does "df -h" say?
>
> Andi

This is what df -h returned:

Filesystem      Size  Used Avail Use% Mounted on
tmpfs           784M  2.0M  782M   1% /run
/dev/sda9        23G   17G  5.6G  75% /
tmpfs           3.9G   45M  3.8G   2% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sda7       944M  761M  119M  87% /boot
/dev/sda11       60G   28G   30G  49% /home
/dev/sda2        96M   32M   65M  33% /boot/efi
tmpfs           784M  120K  784M   1% /run/user/1000

Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Andi Shyti]

Hi Gilbert,

first of all... good to see that your good e-mail style :-)

> > > > I have another issue, I tried compiling after modifying and it compiled
> > > > successfully. But when I tried to install so I can reboot, I got this
> > > > error:
> > > >
> > > > zstd: error 25 : Write error : No space left on device (cannot write
> > > > compressed block)
> > > > E: mkinitramfs failure zstd -q -1 -T0 25
> > > > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > > > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > > > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > > > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > > > __build_one_by_one] Error 2
> > > > make: *** [Makefile:234: __sub-make] Error 2
> > >
> > > You have too little space in the partition that contains /boot?
> >
> > What does "df -h" say?
> >
> > Andi
> 
> This is what df -h returned:
> 
> Filesystem      Size  Used Avail Use% Mounted on
> tmpfs           784M  2.0M  782M   1% /run
> /dev/sda9        23G   17G  5.6G  75% /
> tmpfs           3.9G   45M  3.8G   2% /dev/shm
> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> /dev/sda7       944M  761M  119M  87% /boot

I wonder why your boot directory is so packed, even though 119M
should be enough.

You could try to reove some older kernels.

> /dev/sda11       60G   28G   30G  49% /home

BTW, are you working in your home directory?

Andi

> /dev/sda2        96M   32M   65M  33% /boot/efi
> tmpfs           784M  120K  784M   1% /run/user/1000

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

Hello Andi,

Thank you for your response. I think I'm finally understanding good e-mail style
thanks to you and everyone else who has responded to emails
On Tue, Oct 10, 2023 at 6:03 PM Andi Shyti <andi.shyti@linux.intel.com> wrote:
>
> Hi Gilbert,
>
> first of all... good to see that your good e-mail style :-)
>
> > > > > I have another issue, I tried compiling after modifying and it compiled
> > > > > successfully. But when I tried to install so I can reboot, I got this
> > > > > error:
> > > > >
> > > > > zstd: error 25 : Write error : No space left on device (cannot write
> > > > > compressed block)
> > > > > E: mkinitramfs failure zstd -q -1 -T0 25
> > > > > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > > > > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > > > > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > > > > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > > > > __build_one_by_one] Error 2
> > > > > make: *** [Makefile:234: __sub-make] Error 2
> > > >
> > > > You have too little space in the partition that contains /boot?
> > >
> > > What does "df -h" say?
> > >
> > > Andi
> >
> > This is what df -h returned:
> >
> > Filesystem      Size  Used Avail Use% Mounted on
> > tmpfs           784M  2.0M  782M   1% /run
> > /dev/sda9        23G   17G  5.6G  75% /
> > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > /dev/sda7       944M  761M  119M  87% /boot
>
> I wonder why your boot directory is so packed, even though 119M
> should be enough.
>
I don't why it is so packed either. I ran du -ah /boot/ and it returned:
272K /boot/config-6.2.0-34-generic
14M /boot/vmlinuz-6.6.0-rc1gilbert+
0 /boot/initrd.img
276K /boot/config-6.6.0-rc1gilbert+
14M /boot/vmlinuz-6.2.0-34-generic
184K /boot/memtest86+_multiboot.bin
7.6M /boot/System.map-6.2.0-26-generic
180K /boot/memtest86+.bin
184K /boot/memtest86+.elf
67M /boot/initrd.img-6.2.0-34-generic
7.7M /boot/System.map-6.2.0-34-generic
du: cannot read directory '/boot/efi': Permission denied
1.0K /boot/efi
0 /boot/vmlinuz
7.6M /boot/System.map-6.6.0-rc1gilbert+
du: cannot read directory '/boot/lost+found': Permission denied
16K /boot/lost+found
14M /boot/vmlinuz-6.2.0-26-generic
4.0K /boot/grub/x86_64-efi/lsefimmap.mod
4.0K /boot/grub/x86_64-efi/setjmp.mod
12K /boot/grub/x86_64-efi/loadenv.mod
4.0K /boot/grub/x86_64-efi/mdraid09_be.mod
60K /boot/grub/x86_64-efi/gfxmenu.mod
4.0K /boot/grub/x86_64-efi/efifwsetup.mod
12K /boot/grub/x86_64-efi/efinet.mod
4.0K /boot/grub/x86_64-efi/wrmsr.mod
28K /boot/grub/x86_64-efi/file.mod
12K /boot/grub/x86_64-efi/ata.mod
8.0K /boot/grub/x86_64-efi/minix2.mod
8.0K /boot/grub/x86_64-efi/videotest.mod
16K /boot/grub/x86_64-efi/reiserfs.mod
8.0K /boot/grub/x86_64-efi/videoinfo.mod
8.0K /boot/grub/x86_64-efi/test.mod
4.0K /boot/grub/x86_64-efi/read.mod
16K /boot/grub/x86_64-efi/gzio.mod
4.0K /boot/grub/x86_64-efi/mdraid1x.mod
20K /boot/grub/x86_64-efi/gcry_serpent.mod
8.0K /boot/grub/x86_64-efi/lspci.mod
4.0K /boot/grub/x86_64-efi/date.mod
20K /boot/grub/x86_64-efi/font.mod
4.0K /boot/grub/x86_64-efi/crypto.lst
8.0K /boot/grub/x86_64-efi/minix3_be.mod
24K /boot/grub/x86_64-efi/multiboot2.mod
8.0K /boot/grub/x86_64-efi/part_bsd.mod
4.0K /boot/grub/x86_64-efi/msdospart.mod
8.0K /boot/grub/x86_64-efi/tar.mod
8.0K /boot/grub/x86_64-efi/cmdline_cat_test.mod
8.0K /boot/grub/x86_64-efi/affs.mod
4.0K /boot/grub/x86_64-efi/gcry_rsa.mod
8.0K /boot/grub/x86_64-efi/efi_uga.mod
4.0K /boot/grub/x86_64-efi/shift_test.mod
4.0K /boot/grub/x86_64-efi/usbserial_usbdebug.mod
8.0K /boot/grub/x86_64-efi/tpm.mod
4.0K /boot/grub/x86_64-efi/trig.mod
4.0K /boot/grub/x86_64-efi/mul_test.mod
4.0K /boot/grub/x86_64-efi/usbserial_pl2303.mod
44K /boot/grub/x86_64-efi/xnu.mod
20K /boot/grub/x86_64-efi/xzio.mod
4.0K /boot/grub/x86_64-efi/configfile.mod
4.0K /boot/grub/x86_64-efi/parttool.lst
4.0K /boot/grub/x86_64-efi/hello.mod
20K /boot/grub/x86_64-efi/cryptodisk.mod
8.0K /boot/grub/x86_64-efi/macbless.mod
12K /boot/grub/x86_64-efi/zfscrypt.mod
4.0K /boot/grub/x86_64-efi/setjmp_test.mod
4.0K /boot/grub/x86_64-efi/dm_nv.mod
12K /boot/grub/x86_64-efi/zfsinfo.mod
12K /boot/grub/x86_64-efi/squash4.mod
60K /boot/grub/x86_64-efi/zfs.mod
8.0K /boot/grub/x86_64-efi/gcry_sha1.mod
20K /boot/grub/x86_64-efi/chain.mod
4.0K /boot/grub/x86_64-efi/cbtable.mod
4.0K /boot/grub/x86_64-efi/sleep_test.mod
36K /boot/grub/x86_64-efi/gcry_twofish.mod
8.0K /boot/grub/x86_64-efi/cbtime.mod
12K /boot/grub/x86_64-efi/jpeg.mod
12K /boot/grub/x86_64-efi/macho.mod
4.0K /boot/grub/x86_64-efi/part_amiga.mod
8.0K /boot/grub/x86_64-efi/ntfscomp.mod
8.0K /boot/grub/x86_64-efi/gcry_sha256.mod
12K /boot/grub/x86_64-efi/hfs.mod
4.0K /boot/grub/x86_64-efi/mdraid09.mod
24K /boot/grub/x86_64-efi/gcry_whirlpool.mod
4.0K /boot/grub/x86_64-efi/part_gpt.mod
4.0K /boot/grub/x86_64-efi/part_dfly.mod
12K /boot/grub/x86_64-efi/ext2.mod
4.0K /boot/grub/x86_64-efi/exfctest.mod
16K /boot/grub/x86_64-efi/efi_gop.mod
4.0K /boot/grub/x86_64-efi/fixvideo.mod
8.0K /boot/grub/x86_64-efi/password_pbkdf2.mod
8.0K /boot/grub/x86_64-efi/bitmap_scale.mod
4.0K /boot/grub/x86_64-efi/testload.mod
8.0K /boot/grub/x86_64-efi/at_keyboard.mod
24K /boot/grub/x86_64-efi/ahci.mod
4.0K /boot/grub/x86_64-efi/pbkdf2.mod
176K /boot/grub/x86_64-efi/normal.mod
4.0K /boot/grub/x86_64-efi/echo.mod
4.0K /boot/grub/x86_64-efi/cbmemc.mod
12K /boot/grub/x86_64-efi/gettext.mod
4.0K /boot/grub/x86_64-efi/blocklist.mod
4.0K /boot/grub/x86_64-efi/sleep.mod
4.0K /boot/grub/x86_64-efi/random.mod
12K /boot/grub/x86_64-efi/hashsum.mod
8.0K /boot/grub/x86_64-efi/scsi.mod
24K /boot/grub/x86_64-efi/multiboot.mod
4.0K /boot/grub/x86_64-efi/gcry_arcfour.mod
8.0K /boot/grub/x86_64-efi/minix2_be.mod
8.0K /boot/grub/x86_64-efi/hfspluscomp.mod
4.0K /boot/grub/x86_64-efi/morse.mod
12K /boot/grub/x86_64-efi/lvm.mod
8.0K /boot/grub/x86_64-efi/crypto.mod
4.0K /boot/grub/x86_64-efi/terminal.lst
12K /boot/grub/x86_64-efi/nilfs2.mod
4.0K /boot/grub/x86_64-efi/datehook.mod
8.0K /boot/grub/x86_64-efi/hexdump.mod
4.0K /boot/grub/x86_64-efi/div.mod
8.0K /boot/grub/x86_64-efi/gcry_rmd160.mod
12K /boot/grub/x86_64-efi/png.mod
12K /boot/grub/x86_64-efi/linux16.mod
16K /boot/grub/x86_64-efi/iso9660.mod
4.0K /boot/grub/x86_64-efi/boot.mod
4.0K /boot/grub/x86_64-efi/bswap_test.mod
4.0K /boot/grub/x86_64-efi/procfs.mod
8.0K /boot/grub/x86_64-efi/minix_be.mod
8.0K /boot/grub/x86_64-efi/search_label.mod
20K /boot/grub/x86_64-efi/gfxterm.mod
8.0K /boot/grub/x86_64-efi/memrw.mod
144K /boot/grub/x86_64-efi/grub.efi
4.0K /boot/grub/x86_64-efi/lssal.mod
20K /boot/grub/x86_64-efi/pgp.mod
12K /boot/grub/x86_64-efi/hfsplus.mod
16K /boot/grub/x86_64-efi/ohci.mod
16K /boot/grub/x86_64-efi/gcry_cast5.mod
4.0K /boot/grub/x86_64-efi/backtrace.mod
8.0K /boot/grub/x86_64-efi/cpio_be.mod
8.0K /boot/grub/x86_64-efi/gcry_sha512.mod
12K /boot/grub/x86_64-efi/fat.mod
4.0K /boot/grub/x86_64-efi/password.mod
4.0K /boot/grub/x86_64-efi/lsmmap.mod
8.0K /boot/grub/x86_64-efi/pata.mod
8.0K /boot/grub/x86_64-efi/cpio.mod
4.0K /boot/grub/x86_64-efi/xnu_uuid.mod
8.0K /boot/grub/x86_64-efi/cbls.mod
8.0K /boot/grub/x86_64-efi/newc.mod
8.0K /boot/grub/x86_64-efi/halt.mod
8.0K /boot/grub/x86_64-efi/sfs.mod
4.0K /boot/grub/x86_64-efi/bufio.mod
16K /boot/grub/x86_64-efi/ntfs.mod
48K /boot/grub/x86_64-efi/functional_test.mod
4.0K /boot/grub/x86_64-efi/load.cfg
4.0K /boot/grub/x86_64-efi/videotest_checksum.mod
48K /boot/grub/x86_64-efi/bsd.mod
4.0K /boot/grub/x86_64-efi/usbserial_ftdi.mod
44K /boot/grub/x86_64-efi/mpi.mod
4.0K /boot/grub/x86_64-efi/spkmodem.mod
48K /boot/grub/x86_64-efi/legacycfg.mod
4.0K /boot/grub/x86_64-efi/gcry_rfc2268.mod
12K /boot/grub/x86_64-efi/video_colors.mod
4.0K /boot/grub/x86_64-efi/true.mod
12K /boot/grub/x86_64-efi/exfat.mod
8.0K /boot/grub/x86_64-efi/elf.mod
8.0K /boot/grub/x86_64-efi/search_fs_file.mod
8.0K /boot/grub/x86_64-efi/gcry_md4.mod
12K /boot/grub/x86_64-efi/video_bochs.mod
8.0K /boot/grub/x86_64-efi/gptsync.mod
4.0K /boot/grub/x86_64-efi/strtoull_test.mod
4.0K /boot/grub/x86_64-efi/gcry_idea.mod
4.0K /boot/grub/x86_64-efi/part_sunpc.mod
24K /boot/grub/x86_64-efi/gcry_rijndael.mod
132K /boot/grub/x86_64-efi/net.mod
28K /boot/grub/x86_64-efi/ehci.mod
4.0K /boot/grub/x86_64-efi/raid6rec.mod
8.0K /boot/grub/x86_64-efi/cmp_test.mod
8.0K /boot/grub/x86_64-efi/extcmd.mod
12K /boot/grub/x86_64-efi/mmap.mod
12K /boot/grub/x86_64-efi/smbios.mod
8.0K /boot/grub/x86_64-efi/odc.mod
4.0K /boot/grub/x86_64-efi/aout.mod
8.0K /boot/grub/x86_64-efi/minix.mod
8.0K /boot/grub/x86_64-efi/gfxterm_background.mod
8.0K /boot/grub/x86_64-efi/lsacpi.mod
4.0K /boot/grub/x86_64-efi/testspeed.mod
28K /boot/grub/x86_64-efi/gcry_camellia.mod
8.0K /boot/grub/x86_64-efi/lzopio.mod
16K /boot/grub/x86_64-efi/udf.mod
12K /boot/grub/x86_64-efi/usbms.mod
4.0K /boot/grub/x86_64-efi/command.lst
4.0K /boot/grub/x86_64-efi/bitmap.mod
4.0K /boot/grub/x86_64-efi/cs5536.mod
28K /boot/grub/x86_64-efi/btrfs.mod
4.0K /boot/grub/x86_64-efi/part_plan.mod
4.0K /boot/grub/x86_64-efi/datetime.mod
8.0K /boot/grub/x86_64-efi/probe.mod
8.0K /boot/grub/x86_64-efi/minix3.mod
16K /boot/grub/x86_64-efi/diskfilter.mod
4.0K /boot/grub/x86_64-efi/reboot.mod
8.0K /boot/grub/x86_64-efi/nativedisk.mod
144K /boot/grub/x86_64-efi/core.efi
80K /boot/grub/x86_64-efi/zstd.mod
8.0K /boot/grub/x86_64-efi/archelp.mod
4.0K /boot/grub/x86_64-efi/cpuid.mod
80K /boot/grub/x86_64-efi/regexp.mod
8.0K /boot/grub/x86_64-efi/ufs1.mod
8.0K /boot/grub/x86_64-efi/lsefisystab.mod
12K /boot/grub/x86_64-efi/jfs.mod
4.0K /boot/grub/x86_64-efi/memdisk.mod
12K /boot/grub/x86_64-efi/ldm.mod
4.0K /boot/grub/x86_64-efi/video.lst
12K /boot/grub/x86_64-efi/http.mod
8.0K /boot/grub/x86_64-efi/ufs1_be.mod
4.0K /boot/grub/x86_64-efi/gcry_dsa.mod
28K /boot/grub/x86_64-efi/video_fb.mod
4.0K /boot/grub/x86_64-efi/part_dvh.mod
4.0K /boot/grub/x86_64-efi/priority_queue.mod
4.0K /boot/grub/x86_64-efi/crc64.mod
8.0K /boot/grub/x86_64-efi/gfxterm_menu.mod
4.0K /boot/grub/x86_64-efi/keystatus.mod
8.0K /boot/grub/x86_64-efi/search.mod
12K /boot/grub/x86_64-efi/hdparm.mod
4.0K /boot/grub/x86_64-efi/play.mod
20K /boot/grub/x86_64-efi/gcry_des.mod
8.0K /boot/grub/x86_64-efi/div_test.mod
8.0K /boot/grub/x86_64-efi/lsefi.mod
4.0K /boot/grub/x86_64-efi/time.mod
12K /boot/grub/x86_64-efi/video_cirrus.mod
8.0K /boot/grub/x86_64-efi/romfs.mod
12K /boot/grub/x86_64-efi/gcry_crc.mod
4.0K /boot/grub/x86_64-efi/raid5rec.mod
4.0K /boot/grub/x86_64-efi/usbserial_common.mod
4.0K /boot/grub/x86_64-efi/progress.mod
16K /boot/grub/x86_64-efi/gcry_seed.mod
8.0K /boot/grub/x86_64-efi/ufs2.mod
12K /boot/grub/x86_64-efi/afs.mod
4.0K /boot/grub/x86_64-efi/help.mod
16K /boot/grub/x86_64-efi/acpi.mod
4.0K /boot/grub/x86_64-efi/pbkdf2_test.mod
4.0K /boot/grub/x86_64-efi/afsplitter.mod
24K /boot/grub/x86_64-efi/terminfo.mod
12K /boot/grub/x86_64-efi/xfs.mod
4.0K /boot/grub/x86_64-efi/pcidump.mod
8.0K /boot/grub/x86_64-efi/moddep.lst
4.0K /boot/grub/x86_64-efi/rdmsr.mod
8.0K /boot/grub/x86_64-efi/tftp.mod
16K /boot/grub/x86_64-efi/usb.mod
4.0K /boot/grub/x86_64-efi/part_msdos.mod
4.0K /boot/grub/x86_64-efi/eval.mod
8.0K /boot/grub/x86_64-efi/ls.mod
8.0K /boot/grub/x86_64-efi/usb_keyboard.mod
4.0K /boot/grub/x86_64-efi/part_apple.mod
8.0K /boot/grub/x86_64-efi/tga.mod
24K /boot/grub/x86_64-efi/luks2.mod
8.0K /boot/grub/x86_64-efi/usbtest.mod
12K /boot/grub/x86_64-efi/gcry_blowfish.mod
8.0K /boot/grub/x86_64-efi/terminal.mod
8.0K /boot/grub/x86_64-efi/appleldr.mod
12K /boot/grub/x86_64-efi/uhci.mod
12K /boot/grub/x86_64-efi/f2fs.mod
16K /boot/grub/x86_64-efi/serial.mod
8.0K /boot/grub/x86_64-efi/luks.mod
24K /boot/grub/x86_64-efi/linux.mod
8.0K /boot/grub/x86_64-efi/parttool.mod
4.0K /boot/grub/x86_64-efi/fs.lst
8.0K /boot/grub/x86_64-efi/gcry_md5.mod
4.0K /boot/grub/x86_64-efi/partmap.lst
8.0K /boot/grub/x86_64-efi/cat.mod
8.0K /boot/grub/x86_64-efi/cbfs.mod
8.0K /boot/grub/x86_64-efi/json.mod
12K /boot/grub/x86_64-efi/video.mod
8.0K /boot/grub/x86_64-efi/loadbios.mod
4.0K /boot/grub/x86_64-efi/all_video.mod
4.0K /boot/grub/x86_64-efi/adler32.mod
4.0K /boot/grub/x86_64-efi/offsetio.mod
4.0K /boot/grub/x86_64-efi/modinfo.sh
16K /boot/grub/x86_64-efi/gcry_tiger.mod
8.0K /boot/grub/x86_64-efi/minicmd.mod
4.0K /boot/grub/x86_64-efi/part_acorn.mod
8.0K /boot/grub/x86_64-efi/fshelp.mod
4.0K /boot/grub/x86_64-efi/part_sun.mod
4.0K /boot/grub/x86_64-efi/xnu_uuid_test.mod
4.0K /boot/grub/x86_64-efi/cmp.mod
12K /boot/grub/x86_64-efi/bfs.mod
12K /boot/grub/x86_64-efi/geli.mod
32K /boot/grub/x86_64-efi/syslinuxcfg.mod
8.0K /boot/grub/x86_64-efi/iorw.mod
12K /boot/grub/x86_64-efi/setpci.mod
16K /boot/grub/x86_64-efi/legacy_password_test.mod
8.0K /boot/grub/x86_64-efi/loopback.mod
4.0K /boot/grub/x86_64-efi/ctz_test.mod
16K /boot/grub/x86_64-efi/linuxefi.mod
12K /boot/grub/x86_64-efi/signature_test.mod
8.0K /boot/grub/x86_64-efi/keylayouts.mod
4.0K /boot/grub/x86_64-efi/test_blockarg.mod
4.0K /boot/grub/x86_64-efi/tr.mod
4.0K /boot/grub/x86_64-efi/disk.mod
28K /boot/grub/x86_64-efi/relocator.mod
8.0K /boot/grub/x86_64-efi/search_fs_uuid.mod
3.5M /boot/grub/x86_64-efi
2.3M /boot/grub/fonts/unicode.pf2
2.3M /boot/grub/fonts
4.0K /boot/grub/gfxblacklist.txt
4.0K /boot/grub/locale/en_CA.mo
116K /boot/grub/locale/en@quot.mo
4.0K /boot/grub/locale/en_GB.mo
4.0K /boot/grub/locale/en_AU.mo
132K /boot/grub/locale
12K /boot/grub/grub.cfg
4.0K /boot/grub/grubenv
2.3M /boot/grub/unicode.pf2
4.0K /boot/grub/i386-pc/setjmp.mod
8.0K /boot/grub/i386-pc/loadenv.mod
4.0K /boot/grub/i386-pc/mdraid09_be.mod
40K /boot/grub/i386-pc/gfxmenu.mod
4.0K /boot/grub/i386-pc/wrmsr.mod
20K /boot/grub/i386-pc/file.mod
8.0K /boot/grub/i386-pc/ata.mod
8.0K /boot/grub/i386-pc/efiemu32.o
4.0K /boot/grub/i386-pc/minix2.mod
8.0K /boot/grub/i386-pc/videotest.mod
12K /boot/grub/i386-pc/reiserfs.mod
4.0K /boot/grub/i386-pc/videoinfo.mod
8.0K /boot/grub/i386-pc/test.mod
4.0K /boot/grub/i386-pc/read.mod
12K /boot/grub/i386-pc/gzio.mod
4.0K /boot/grub/i386-pc/mdraid1x.mod
20K /boot/grub/i386-pc/gcry_serpent.mod
8.0K /boot/grub/i386-pc/lspci.mod
4.0K /boot/grub/i386-pc/date.mod
16K /boot/grub/i386-pc/font.mod
4.0K /boot/grub/i386-pc/crypto.lst
4.0K /boot/grub/i386-pc/minix3_be.mod
16K /boot/grub/i386-pc/multiboot2.mod
4.0K /boot/grub/i386-pc/part_bsd.mod
4.0K /boot/grub/i386-pc/msdospart.mod
4.0K /boot/grub/i386-pc/tar.mod
4.0K /boot/grub/i386-pc/cmdline_cat_test.mod
4.0K /boot/grub/i386-pc/cmosdump.mod
8.0K /boot/grub/i386-pc/affs.mod
4.0K /boot/grub/i386-pc/gcry_rsa.mod
4.0K /boot/grub/i386-pc/shift_test.mod
4.0K /boot/grub/i386-pc/usbserial_usbdebug.mod
4.0K /boot/grub/i386-pc/vga_text.mod
4.0K /boot/grub/i386-pc/trig.mod
4.0K /boot/grub/i386-pc/mul_test.mod
4.0K /boot/grub/i386-pc/usbserial_pl2303.mod
4.0K /boot/grub/i386-pc/ntldr.mod
28K /boot/grub/i386-pc/xnu.mod
16K /boot/grub/i386-pc/xzio.mod
4.0K /boot/grub/i386-pc/configfile.mod
4.0K /boot/grub/i386-pc/parttool.lst
4.0K /boot/grub/i386-pc/hello.mod
12K /boot/grub/i386-pc/cryptodisk.mod
4.0K /boot/grub/i386-pc/macbless.mod
8.0K /boot/grub/i386-pc/zfscrypt.mod
4.0K /boot/grub/i386-pc/setjmp_test.mod
4.0K /boot/grub/i386-pc/truecrypt.mod
4.0K /boot/grub/i386-pc/dm_nv.mod
8.0K /boot/grub/i386-pc/zfsinfo.mod
8.0K /boot/grub/i386-pc/squash4.mod
40K /boot/grub/i386-pc/zfs.mod
28K /boot/grub/i386-pc/core.img
8.0K /boot/grub/i386-pc/gcry_sha1.mod
4.0K /boot/grub/i386-pc/chain.mod
4.0K /boot/grub/i386-pc/cbtable.mod
4.0K /boot/grub/i386-pc/sleep_test.mod
36K /boot/grub/i386-pc/gcry_twofish.mod
4.0K /boot/grub/i386-pc/cbtime.mod
8.0K /boot/grub/i386-pc/jpeg.mod
8.0K /boot/grub/i386-pc/macho.mod
4.0K /boot/grub/i386-pc/freedos.mod
4.0K /boot/grub/i386-pc/part_amiga.mod
8.0K /boot/grub/i386-pc/ntfscomp.mod
8.0K /boot/grub/i386-pc/gcry_sha256.mod
8.0K /boot/grub/i386-pc/hfs.mod
4.0K /boot/grub/i386-pc/boot.img
4.0K /boot/grub/i386-pc/mdraid09.mod
24K /boot/grub/i386-pc/gcry_whirlpool.mod
4.0K /boot/grub/i386-pc/part_gpt.mod
4.0K /boot/grub/i386-pc/part_dfly.mod
8.0K /boot/grub/i386-pc/ext2.mod
4.0K /boot/grub/i386-pc/exfctest.mod
4.0K /boot/grub/i386-pc/password_pbkdf2.mod
4.0K /boot/grub/i386-pc/pxechain.mod
4.0K /boot/grub/i386-pc/bitmap_scale.mod
4.0K /boot/grub/i386-pc/testload.mod
4.0K /boot/grub/i386-pc/at_keyboard.mod
16K /boot/grub/i386-pc/ahci.mod
4.0K /boot/grub/i386-pc/pbkdf2.mod
116K /boot/grub/i386-pc/normal.mod
4.0K /boot/grub/i386-pc/echo.mod
4.0K /boot/grub/i386-pc/cbmemc.mod
8.0K /boot/grub/i386-pc/gettext.mod
4.0K /boot/grub/i386-pc/blocklist.mod
4.0K /boot/grub/i386-pc/hwmatch.mod
4.0K /boot/grub/i386-pc/sleep.mod
4.0K /boot/grub/i386-pc/random.mod
8.0K /boot/grub/i386-pc/hashsum.mod
8.0K /boot/grub/i386-pc/scsi.mod
16K /boot/grub/i386-pc/multiboot.mod
4.0K /boot/grub/i386-pc/gcry_arcfour.mod
4.0K /boot/grub/i386-pc/minix2_be.mod
4.0K /boot/grub/i386-pc/hfspluscomp.mod
4.0K /boot/grub/i386-pc/morse.mod
12K /boot/grub/i386-pc/lvm.mod
8.0K /boot/grub/i386-pc/crypto.mod
4.0K /boot/grub/i386-pc/terminal.lst
8.0K /boot/grub/i386-pc/nilfs2.mod
4.0K /boot/grub/i386-pc/datehook.mod
4.0K /boot/grub/i386-pc/hexdump.mod
4.0K /boot/grub/i386-pc/div.mod
8.0K /boot/grub/i386-pc/gcry_rmd160.mod
8.0K /boot/grub/i386-pc/png.mod
8.0K /boot/grub/i386-pc/linux16.mod
12K /boot/grub/i386-pc/iso9660.mod
4.0K /boot/grub/i386-pc/boot.mod
4.0K /boot/grub/i386-pc/bswap_test.mod
4.0K /boot/grub/i386-pc/procfs.mod
4.0K /boot/grub/i386-pc/minix_be.mod
4.0K /boot/grub/i386-pc/search_label.mod
12K /boot/grub/i386-pc/gfxterm.mod
4.0K /boot/grub/i386-pc/memrw.mod
12K /boot/grub/i386-pc/pgp.mod
8.0K /boot/grub/i386-pc/915resolution.mod
8.0K /boot/grub/i386-pc/hfsplus.mod
12K /boot/grub/i386-pc/ohci.mod
8.0K /boot/grub/i386-pc/vga.mod
16K /boot/grub/i386-pc/gcry_cast5.mod
4.0K /boot/grub/i386-pc/backtrace.mod
4.0K /boot/grub/i386-pc/cpio_be.mod
12K /boot/grub/i386-pc/gcry_sha512.mod
8.0K /boot/grub/i386-pc/fat.mod
4.0K /boot/grub/i386-pc/password.mod
4.0K /boot/grub/i386-pc/lsmmap.mod
8.0K /boot/grub/i386-pc/pata.mod
4.0K /boot/grub/i386-pc/cpio.mod
4.0K /boot/grub/i386-pc/xnu_uuid.mod
4.0K /boot/grub/i386-pc/cbls.mod
4.0K /boot/grub/i386-pc/newc.mod
8.0K /boot/grub/i386-pc/halt.mod
8.0K /boot/grub/i386-pc/sfs.mod
4.0K /boot/grub/i386-pc/bufio.mod
12K /boot/grub/i386-pc/ntfs.mod
36K /boot/grub/i386-pc/functional_test.mod
4.0K /boot/grub/i386-pc/videotest_checksum.mod
32K /boot/grub/i386-pc/bsd.mod
4.0K /boot/grub/i386-pc/usbserial_ftdi.mod
28K /boot/grub/i386-pc/mpi.mod
4.0K /boot/grub/i386-pc/spkmodem.mod
32K /boot/grub/i386-pc/legacycfg.mod
4.0K /boot/grub/i386-pc/gcry_rfc2268.mod
8.0K /boot/grub/i386-pc/video_colors.mod
4.0K /boot/grub/i386-pc/true.mod
8.0K /boot/grub/i386-pc/exfat.mod
4.0K /boot/grub/i386-pc/elf.mod
4.0K /boot/grub/i386-pc/search_fs_file.mod
4.0K /boot/grub/i386-pc/gcry_md4.mod
8.0K /boot/grub/i386-pc/video_bochs.mod
4.0K /boot/grub/i386-pc/gptsync.mod
8.0K /boot/grub/i386-pc/plan9.mod
4.0K /boot/grub/i386-pc/strtoull_test.mod
4.0K /boot/grub/i386-pc/gcry_idea.mod
4.0K /boot/grub/i386-pc/part_sunpc.mod
20K /boot/grub/i386-pc/gcry_rijndael.mod
60K /boot/grub/i386-pc/net.mod
16K /boot/grub/i386-pc/ehci.mod
4.0K /boot/grub/i386-pc/raid6rec.mod
8.0K /boot/grub/i386-pc/cmp_test.mod
8.0K /boot/grub/i386-pc/extcmd.mod
12K /boot/grub/i386-pc/mmap.mod
8.0K /boot/grub/i386-pc/smbios.mod
4.0K /boot/grub/i386-pc/odc.mod
4.0K /boot/grub/i386-pc/aout.mod
4.0K /boot/grub/i386-pc/minix.mod
4.0K /boot/grub/i386-pc/gfxterm_background.mod
8.0K /boot/grub/i386-pc/lsacpi.mod
4.0K /boot/grub/i386-pc/testspeed.mod
36K /boot/grub/i386-pc/gcry_camellia.mod
8.0K /boot/grub/i386-pc/lzopio.mod
12K /boot/grub/i386-pc/udf.mod
8.0K /boot/grub/i386-pc/usbms.mod
4.0K /boot/grub/i386-pc/command.lst
4.0K /boot/grub/i386-pc/bitmap.mod
4.0K /boot/grub/i386-pc/cs5536.mod
20K /boot/grub/i386-pc/btrfs.mod
4.0K /boot/grub/i386-pc/part_plan.mod
4.0K /boot/grub/i386-pc/datetime.mod
4.0K /boot/grub/i386-pc/probe.mod
4.0K /boot/grub/i386-pc/minix3.mod
12K /boot/grub/i386-pc/diskfilter.mod
4.0K /boot/grub/i386-pc/reboot.mod
8.0K /boot/grub/i386-pc/nativedisk.mod
48K /boot/grub/i386-pc/zstd.mod
4.0K /boot/grub/i386-pc/archelp.mod
4.0K /boot/grub/i386-pc/cpuid.mod
52K /boot/grub/i386-pc/regexp.mod
8.0K /boot/grub/i386-pc/ufs1.mod
8.0K /boot/grub/i386-pc/jfs.mod
4.0K /boot/grub/i386-pc/memdisk.mod
8.0K /boot/grub/i386-pc/ldm.mod
4.0K /boot/grub/i386-pc/video.lst
8.0K /boot/grub/i386-pc/http.mod
8.0K /boot/grub/i386-pc/ufs1_be.mod
4.0K /boot/grub/i386-pc/gcry_dsa.mod
24K /boot/grub/i386-pc/video_fb.mod
4.0K /boot/grub/i386-pc/pci.mod
4.0K /boot/grub/i386-pc/part_dvh.mod
4.0K /boot/grub/i386-pc/priority_queue.mod
4.0K /boot/grub/i386-pc/crc64.mod
4.0K /boot/grub/i386-pc/mda_text.mod
8.0K /boot/grub/i386-pc/gfxterm_menu.mod
4.0K /boot/grub/i386-pc/keystatus.mod
4.0K /boot/grub/i386-pc/search.mod
8.0K /boot/grub/i386-pc/hdparm.mod
4.0K /boot/grub/i386-pc/play.mod
20K /boot/grub/i386-pc/gcry_des.mod
8.0K /boot/grub/i386-pc/div_test.mod
4.0K /boot/grub/i386-pc/lsapm.mod
4.0K /boot/grub/i386-pc/time.mod
8.0K /boot/grub/i386-pc/sendkey.mod
8.0K /boot/grub/i386-pc/video_cirrus.mod
8.0K /boot/grub/i386-pc/romfs.mod
12K /boot/grub/i386-pc/gcry_crc.mod
4.0K /boot/grub/i386-pc/raid5rec.mod
8.0K /boot/grub/i386-pc/drivemap.mod
4.0K /boot/grub/i386-pc/usbserial_common.mod
4.0K /boot/grub/i386-pc/progress.mod
16K /boot/grub/i386-pc/gcry_seed.mod
12K /boot/grub/i386-pc/efiemu64.o
8.0K /boot/grub/i386-pc/ufs2.mod
8.0K /boot/grub/i386-pc/afs.mod
4.0K /boot/grub/i386-pc/help.mod
12K /boot/grub/i386-pc/acpi.mod
4.0K /boot/grub/i386-pc/pbkdf2_test.mod
4.0K /boot/grub/i386-pc/afsplitter.mod
16K /boot/grub/i386-pc/terminfo.mod
8.0K /boot/grub/i386-pc/xfs.mod
4.0K /boot/grub/i386-pc/pcidump.mod
8.0K /boot/grub/i386-pc/moddep.lst
4.0K /boot/grub/i386-pc/rdmsr.mod
8.0K /boot/grub/i386-pc/tftp.mod
12K /boot/grub/i386-pc/usb.mod
4.0K /boot/grub/i386-pc/part_msdos.mod
4.0K /boot/grub/i386-pc/eval.mod
4.0K /boot/grub/i386-pc/ls.mod
4.0K /boot/grub/i386-pc/usb_keyboard.mod
4.0K /boot/grub/i386-pc/part_apple.mod
8.0K /boot/grub/i386-pc/tga.mod
16K /boot/grub/i386-pc/luks2.mod
4.0K /boot/grub/i386-pc/verifiers.mod
4.0K /boot/grub/i386-pc/usbtest.mod
8.0K /boot/grub/i386-pc/gcry_blowfish.mod
8.0K /boot/grub/i386-pc/terminal.mod
8.0K /boot/grub/i386-pc/uhci.mod
8.0K /boot/grub/i386-pc/f2fs.mod
4.0K /boot/grub/i386-pc/cmostest.mod
8.0K /boot/grub/i386-pc/serial.mod
8.0K /boot/grub/i386-pc/luks.mod
16K /boot/grub/i386-pc/linux.mod
8.0K /boot/grub/i386-pc/parttool.mod
4.0K /boot/grub/i386-pc/fs.lst
4.0K /boot/grub/i386-pc/gcry_md5.mod
4.0K /boot/grub/i386-pc/partmap.lst
4.0K /boot/grub/i386-pc/cat.mod
4.0K /boot/grub/i386-pc/cbfs.mod
4.0K /boot/grub/i386-pc/json.mod
8.0K /boot/grub/i386-pc/video.mod
4.0K /boot/grub/i386-pc/all_video.mod
12K /boot/grub/i386-pc/vbe.mod
4.0K /boot/grub/i386-pc/adler32.mod
4.0K /boot/grub/i386-pc/offsetio.mod
4.0K /boot/grub/i386-pc/modinfo.sh
12K /boot/grub/i386-pc/gcry_tiger.mod
4.0K /boot/grub/i386-pc/minicmd.mod
4.0K /boot/grub/i386-pc/part_acorn.mod
4.0K /boot/grub/i386-pc/fshelp.mod
4.0K /boot/grub/i386-pc/part_sun.mod
4.0K /boot/grub/i386-pc/xnu_uuid_test.mod
4.0K /boot/grub/i386-pc/cmp.mod
8.0K /boot/grub/i386-pc/bfs.mod
8.0K /boot/grub/i386-pc/geli.mod
20K /boot/grub/i386-pc/syslinuxcfg.mod
28K /boot/grub/i386-pc/gdb.mod
8.0K /boot/grub/i386-pc/biosdisk.mod
4.0K /boot/grub/i386-pc/iorw.mod
8.0K /boot/grub/i386-pc/setpci.mod
16K /boot/grub/i386-pc/legacy_password_test.mod
4.0K /boot/grub/i386-pc/loopback.mod
4.0K /boot/grub/i386-pc/ctz_test.mod
24K /boot/grub/i386-pc/efiemu.mod
8.0K /boot/grub/i386-pc/signature_test.mod
8.0K /boot/grub/i386-pc/keylayouts.mod
4.0K /boot/grub/i386-pc/test_blockarg.mod
4.0K /boot/grub/i386-pc/pxe.mod
4.0K /boot/grub/i386-pc/tr.mod
4.0K /boot/grub/i386-pc/disk.mod
16K /boot/grub/i386-pc/relocator.mod
4.0K /boot/grub/i386-pc/search_fs_uuid.mod
2.5M /boot/grub/i386-pc
11M /boot/grub
547M /boot/initrd.img-6.6.0-rc1gilbert+
74M /boot/initrd.img-6.2.0-26-generic
272K /boot/config-6.2.0-26-generic

I apologize for the overly long list

> You could try to reove some older kernels.
>
How do I remove old kernels? I have tried a lot of commands that I
could find online and I didn't get the desired result
> > /dev/sda11       60G   28G   30G  49% /home
>
> BTW, are you working in your home directory?
>
No, I'm not working in the home directory
> Andi
>
> > /dev/sda2        96M   32M   65M  33% /boot/efi
> > tmpfs           784M  120K  784M   1% /run/user/1000


Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Andi Shyti]

Hi Gilbert,

> Thank you for your response. I think I'm finally understanding good e-mail style
> thanks to you and everyone else who has responded to emails

glad to hear! :-)

> > > > > You have too little space in the partition that contains /boot?
> > > >
> > > > What does "df -h" say?
> > > >
> > > > Andi
> > >
> > > This is what df -h returned:
> > >
> > > Filesystem      Size  Used Avail Use% Mounted on
> > > tmpfs           784M  2.0M  782M   1% /run
> > > /dev/sda9        23G   17G  5.6G  75% /
> > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > /dev/sda7       944M  761M  119M  87% /boot
> >
> > I wonder why your boot directory is so packed, even though 119M
> > should be enough.
> >

> I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> 272K /boot/config-6.2.0-34-generic
> 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> 0 /boot/initrd.img
> 276K /boot/config-6.6.0-rc1gilbert+
> 14M /boot/vmlinuz-6.2.0-34-generic
> 184K /boot/memtest86+_multiboot.bin
> 7.6M /boot/System.map-6.2.0-26-generic
> 180K /boot/memtest86+.bin
> 184K /boot/memtest86+.elf
> 67M /boot/initrd.img-6.2.0-34-generic
> 7.7M /boot/System.map-6.2.0-34-generic
> du: cannot read directory '/boot/efi': Permission denied
> 1.0K /boot/efi
> 0 /boot/vmlinuz
> 7.6M /boot/System.map-6.6.0-rc1gilbert+
> du: cannot read directory '/boot/lost+found': Permission denied
> 16K /boot/lost+found
> 14M /boot/vmlinuz-6.2.0-26-generic
> 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> 4.0K /boot/grub/x86_64-efi/setjmp.mod
> 12K /boot/grub/x86_64-efi/loadenv.mod

...

> 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> 2.5M /boot/grub/i386-pc
> 11M /boot/grub
> 547M /boot/initrd.img-6.6.0-rc1gilbert+
> 74M /boot/initrd.img-6.2.0-26-generic
> 272K /boot/config-6.2.0-26-generic
> 
> I apologize for the overly long list

that's a long list indeed. I don't know what all those files are,
but I don't think they are an issue.

> > > /dev/sda11       60G   28G   30G  49% /home
> >
> > BTW, are you working in your home directory?
> >
> No, I'm not working in the home directory

then I think this is the main issue. You have lots of free space
in your home directory, you should work there. I only work in my
home directory.

I believe you weren't able to complete the compilation because
you were working in the root partition where you have less
space available.

Andi

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

On Tue, Oct 10, 2023 at 10:54:19PM +0200, Andi Shyti wrote:
> Hi Gilbert,
> 
> > Thank you for your response. I think I'm finally understanding good e-mail style
> > thanks to you and everyone else who has responded to emails
> 
> glad to hear! :-)
> 
> > > > > > You have too little space in the partition that contains /boot?
> > > > >
> > > > > What does "df -h" say?
> > > > >
> > > > > Andi
> > > >
> > > > This is what df -h returned:
> > > >
> > > > Filesystem      Size  Used Avail Use% Mounted on
> > > > tmpfs           784M  2.0M  782M   1% /run
> > > > /dev/sda9        23G   17G  5.6G  75% /
> > > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > > /dev/sda7       944M  761M  119M  87% /boot
> > >
> > > I wonder why your boot directory is so packed, even though 119M
> > > should be enough.
> > >
> 
> > I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> > 272K /boot/config-6.2.0-34-generic
> > 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> > 0 /boot/initrd.img
> > 276K /boot/config-6.6.0-rc1gilbert+
> > 14M /boot/vmlinuz-6.2.0-34-generic
> > 184K /boot/memtest86+_multiboot.bin
> > 7.6M /boot/System.map-6.2.0-26-generic
> > 180K /boot/memtest86+.bin
> > 184K /boot/memtest86+.elf
> > 67M /boot/initrd.img-6.2.0-34-generic
> > 7.7M /boot/System.map-6.2.0-34-generic
> > du: cannot read directory '/boot/efi': Permission denied
> > 1.0K /boot/efi
> > 0 /boot/vmlinuz
> > 7.6M /boot/System.map-6.6.0-rc1gilbert+
> > du: cannot read directory '/boot/lost+found': Permission denied
> > 16K /boot/lost+found
> > 14M /boot/vmlinuz-6.2.0-26-generic
> > 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> > 4.0K /boot/grub/x86_64-efi/setjmp.mod
> > 12K /boot/grub/x86_64-efi/loadenv.mod
> 
> ...
> 
> > 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> > 2.5M /boot/grub/i386-pc
> > 11M /boot/grub
> > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > 74M /boot/initrd.img-6.2.0-26-generic
> > 272K /boot/config-6.2.0-26-generic
> > 
> > I apologize for the overly long list
> 
> that's a long list indeed. I don't know what all those files are,
> but I don't think they are an issue.
> 
> > > > /dev/sda11       60G   28G   30G  49% /home
> > >
> > > BTW, are you working in your home directory?
> > >
> > No, I'm not working in the home directory
> 
> then I think this is the main issue. You have lots of free space
> in your home directory, you should work there. I only work in my
> home directory.
> 
> I believe you weren't able to complete the compilation because
> you were working in the root partition where you have less
> space available.
> 
> Andi
>
Hello Andi,

Thank you for your response. So I'm not sure I understand what you mean
by do all you work in the home directory so I will explain how I work
now to see if that is what you mean.

I have the staging respository in my home directory and I usually
do all my compilation from inside the directory of the staging
repository that is saved in my home directory. 

Is this what you mean by working from the home directory? or is there other setups I should be doing my home directory?

Also I deleted the offending file in my /boot :

547M /boot/initrd.img-6.6.0-rc1gilbert+

and deleted its module directory in usr/lib/modules

I realised it was too large compared to the other kernels and assumed
that probably I didn't do its .config file properly which might have enabled
more modules than is needed for it to run on my machine. 

this is the result of df -h after the deletion:
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           784M  2.0M  782M   1% /run
/dev/sda9        23G   11G   12G  47% /
tmpfs           3.9G  193M  3.7G   5% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sda7       944M  201M  678M  23% /boot
/dev/sda11       60G   28G   30G  49% /home
/dev/sda2        96M   32M   65M  33% /boot/efi
tmpfs           784M  144K  784M   1% /run/user/1000

I want to generate a new .config file and recompile. I also realised
that the staging repository I have on my machine is 28GB large is this
normal?

Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Julia Lawall]

On Wed, 11 Oct 2023, Gilbert Adikankwu wrote:

> On Tue, Oct 10, 2023 at 10:54:19PM +0200, Andi Shyti wrote:
> > Hi Gilbert,
> >
> > > Thank you for your response. I think I'm finally understanding good e-mail style
> > > thanks to you and everyone else who has responded to emails
> >
> > glad to hear! :-)
> >
> > > > > > > You have too little space in the partition that contains /boot?
> > > > > >
> > > > > > What does "df -h" say?
> > > > > >
> > > > > > Andi
> > > > >
> > > > > This is what df -h returned:
> > > > >
> > > > > Filesystem      Size  Used Avail Use% Mounted on
> > > > > tmpfs           784M  2.0M  782M   1% /run
> > > > > /dev/sda9        23G   17G  5.6G  75% /
> > > > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > > > /dev/sda7       944M  761M  119M  87% /boot
> > > >
> > > > I wonder why your boot directory is so packed, even though 119M
> > > > should be enough.
> > > >
> >
> > > I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> > > 272K /boot/config-6.2.0-34-generic
> > > 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> > > 0 /boot/initrd.img
> > > 276K /boot/config-6.6.0-rc1gilbert+
> > > 14M /boot/vmlinuz-6.2.0-34-generic
> > > 184K /boot/memtest86+_multiboot.bin
> > > 7.6M /boot/System.map-6.2.0-26-generic
> > > 180K /boot/memtest86+.bin
> > > 184K /boot/memtest86+.elf
> > > 67M /boot/initrd.img-6.2.0-34-generic
> > > 7.7M /boot/System.map-6.2.0-34-generic
> > > du: cannot read directory '/boot/efi': Permission denied
> > > 1.0K /boot/efi
> > > 0 /boot/vmlinuz
> > > 7.6M /boot/System.map-6.6.0-rc1gilbert+
> > > du: cannot read directory '/boot/lost+found': Permission denied
> > > 16K /boot/lost+found
> > > 14M /boot/vmlinuz-6.2.0-26-generic
> > > 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> > > 4.0K /boot/grub/x86_64-efi/setjmp.mod
> > > 12K /boot/grub/x86_64-efi/loadenv.mod
> >
> > ...
> >
> > > 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> > > 2.5M /boot/grub/i386-pc
> > > 11M /boot/grub
> > > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > > 74M /boot/initrd.img-6.2.0-26-generic
> > > 272K /boot/config-6.2.0-26-generic
> > >
> > > I apologize for the overly long list
> >
> > that's a long list indeed. I don't know what all those files are,
> > but I don't think they are an issue.
> >
> > > > > /dev/sda11       60G   28G   30G  49% /home
> > > >
> > > > BTW, are you working in your home directory?
> > > >
> > > No, I'm not working in the home directory
> >
> > then I think this is the main issue. You have lots of free space
> > in your home directory, you should work there. I only work in my
> > home directory.
> >
> > I believe you weren't able to complete the compilation because
> > you were working in the root partition where you have less
> > space available.
> >
> > Andi
> >
> Hello Andi,
>
> Thank you for your response. So I'm not sure I understand what you mean
> by do all you work in the home directory so I will explain how I work
> now to see if that is what you mean.
>
> I have the staging respository in my home directory and I usually
> do all my compilation from inside the directory of the staging
> repository that is saved in my home directory.
>
> Is this what you mean by working from the home directory? or is there other setups I should be doing my home directory?
>
> Also I deleted the offending file in my /boot :
>
> 547M /boot/initrd.img-6.6.0-rc1gilbert+
>
> and deleted its module directory in usr/lib/modules
>
> I realised it was too large compared to the other kernels and assumed
> that probably I didn't do its .config file properly which might have enabled
> more modules than is needed for it to run on my machine.
>
> this is the result of df -h after the deletion:
> Filesystem      Size  Used Avail Use% Mounted on
> tmpfs           784M  2.0M  782M   1% /run
> /dev/sda9        23G   11G   12G  47% /
> tmpfs           3.9G  193M  3.7G   5% /dev/shm
> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> /dev/sda7       944M  201M  678M  23% /boot
> /dev/sda11       60G   28G   30G  49% /home
> /dev/sda2        96M   32M   65M  33% /boot/efi
> tmpfs           784M  144K  784M   1% /run/user/1000
>
> I want to generate a new .config file and recompile. I also realised
> that the staging repository I have on my machine is 28GB large is this
> normal?

When you start compiling the Linux kernel it gets very big.  But maybe you
reduced your config at some point, but didn't delete the no longer needed
.o files?  You could try make clean and then recompile.

julia

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

On Wed, Oct 11, 2023 at 08:26:15AM +0200, Julia Lawall wrote:
> 
> 
> On Wed, 11 Oct 2023, Gilbert Adikankwu wrote:
> 
> > On Tue, Oct 10, 2023 at 10:54:19PM +0200, Andi Shyti wrote:
> > > Hi Gilbert,
> > >
> > > > Thank you for your response. I think I'm finally understanding good e-mail style
> > > > thanks to you and everyone else who has responded to emails
> > >
> > > glad to hear! :-)
> > >
> > > > > > > > You have too little space in the partition that contains /boot?
> > > > > > >
> > > > > > > What does "df -h" say?
> > > > > > >
> > > > > > > Andi
> > > > > >
> > > > > > This is what df -h returned:
> > > > > >
> > > > > > Filesystem      Size  Used Avail Use% Mounted on
> > > > > > tmpfs           784M  2.0M  782M   1% /run
> > > > > > /dev/sda9        23G   17G  5.6G  75% /
> > > > > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > > > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > > > > /dev/sda7       944M  761M  119M  87% /boot
> > > > >
> > > > > I wonder why your boot directory is so packed, even though 119M
> > > > > should be enough.
> > > > >
> > >
> > > > I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> > > > 272K /boot/config-6.2.0-34-generic
> > > > 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> > > > 0 /boot/initrd.img
> > > > 276K /boot/config-6.6.0-rc1gilbert+
> > > > 14M /boot/vmlinuz-6.2.0-34-generic
> > > > 184K /boot/memtest86+_multiboot.bin
> > > > 7.6M /boot/System.map-6.2.0-26-generic
> > > > 180K /boot/memtest86+.bin
> > > > 184K /boot/memtest86+.elf
> > > > 67M /boot/initrd.img-6.2.0-34-generic
> > > > 7.7M /boot/System.map-6.2.0-34-generic
> > > > du: cannot read directory '/boot/efi': Permission denied
> > > > 1.0K /boot/efi
> > > > 0 /boot/vmlinuz
> > > > 7.6M /boot/System.map-6.6.0-rc1gilbert+
> > > > du: cannot read directory '/boot/lost+found': Permission denied
> > > > 16K /boot/lost+found
> > > > 14M /boot/vmlinuz-6.2.0-26-generic
> > > > 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> > > > 4.0K /boot/grub/x86_64-efi/setjmp.mod
> > > > 12K /boot/grub/x86_64-efi/loadenv.mod
> > >
> > > ...
> > >
> > > > 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> > > > 2.5M /boot/grub/i386-pc
> > > > 11M /boot/grub
> > > > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > > > 74M /boot/initrd.img-6.2.0-26-generic
> > > > 272K /boot/config-6.2.0-26-generic
> > > >
> > > > I apologize for the overly long list
> > >
> > > that's a long list indeed. I don't know what all those files are,
> > > but I don't think they are an issue.
> > >
> > > > > > /dev/sda11       60G   28G   30G  49% /home
> > > > >
> > > > > BTW, are you working in your home directory?
> > > > >
> > > > No, I'm not working in the home directory
> > >
> > > then I think this is the main issue. You have lots of free space
> > > in your home directory, you should work there. I only work in my
> > > home directory.
> > >
> > > I believe you weren't able to complete the compilation because
> > > you were working in the root partition where you have less
> > > space available.
> > >
> > > Andi
> > >
> > Hello Andi,
> >
> > Thank you for your response. So I'm not sure I understand what you mean
> > by do all you work in the home directory so I will explain how I work
> > now to see if that is what you mean.
> >
> > I have the staging respository in my home directory and I usually
> > do all my compilation from inside the directory of the staging
> > repository that is saved in my home directory.
> >
> > Is this what you mean by working from the home directory? or is there other setups I should be doing my home directory?
> >
> > Also I deleted the offending file in my /boot :
> >
> > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> >
> > and deleted its module directory in usr/lib/modules
> >
> > I realised it was too large compared to the other kernels and assumed
> > that probably I didn't do its .config file properly which might have enabled
> > more modules than is needed for it to run on my machine.
> >
> > this is the result of df -h after the deletion:
> > Filesystem      Size  Used Avail Use% Mounted on
> > tmpfs           784M  2.0M  782M   1% /run
> > /dev/sda9        23G   11G   12G  47% /
> > tmpfs           3.9G  193M  3.7G   5% /dev/shm
> > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > /dev/sda7       944M  201M  678M  23% /boot
> > /dev/sda11       60G   28G   30G  49% /home
> > /dev/sda2        96M   32M   65M  33% /boot/efi
> > tmpfs           784M  144K  784M   1% /run/user/1000
> >
> > I want to generate a new .config file and recompile. I also realised
> > that the staging repository I have on my machine is 28GB large is this
> > normal?
> 
> When you start compiling the Linux kernel it gets very big.  But maybe you
> reduced your config at some point, but didn't delete the no longer needed
> .o files?  You could try make clean and then recompile.
> 
> julia

Hello Julia,

Thank you for your response, I will do as you have suggested.

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Andi Shyti]

Hi Gilbert,

> > > > > > > > You have too little space in the partition that contains /boot?
> > > > > > >
> > > > > > > What does "df -h" say?
> > > > > > >
> > > > > > > Andi
> > > > > >
> > > > > > This is what df -h returned:
> > > > > >
> > > > > > Filesystem      Size  Used Avail Use% Mounted on
> > > > > > tmpfs           784M  2.0M  782M   1% /run
> > > > > > /dev/sda9        23G   17G  5.6G  75% /
> > > > > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > > > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > > > > /dev/sda7       944M  761M  119M  87% /boot
> > > > >
> > > > > I wonder why your boot directory is so packed, even though 119M
> > > > > should be enough.
> > > > >
> > >
> > > > I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> > > > 272K /boot/config-6.2.0-34-generic
> > > > 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> > > > 0 /boot/initrd.img
> > > > 276K /boot/config-6.6.0-rc1gilbert+
> > > > 14M /boot/vmlinuz-6.2.0-34-generic
> > > > 184K /boot/memtest86+_multiboot.bin
> > > > 7.6M /boot/System.map-6.2.0-26-generic
> > > > 180K /boot/memtest86+.bin
> > > > 184K /boot/memtest86+.elf
> > > > 67M /boot/initrd.img-6.2.0-34-generic
> > > > 7.7M /boot/System.map-6.2.0-34-generic
> > > > du: cannot read directory '/boot/efi': Permission denied
> > > > 1.0K /boot/efi
> > > > 0 /boot/vmlinuz
> > > > 7.6M /boot/System.map-6.6.0-rc1gilbert+
> > > > du: cannot read directory '/boot/lost+found': Permission denied
> > > > 16K /boot/lost+found
> > > > 14M /boot/vmlinuz-6.2.0-26-generic
> > > > 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> > > > 4.0K /boot/grub/x86_64-efi/setjmp.mod
> > > > 12K /boot/grub/x86_64-efi/loadenv.mod
> > >
> > > ...
> > >
> > > > 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> > > > 2.5M /boot/grub/i386-pc
> > > > 11M /boot/grub
> > > > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > > > 74M /boot/initrd.img-6.2.0-26-generic
> > > > 272K /boot/config-6.2.0-26-generic
> > > >
> > > > I apologize for the overly long list
> > >
> > > that's a long list indeed. I don't know what all those files are,
> > > but I don't think they are an issue.
> > >
> > > > > > /dev/sda11       60G   28G   30G  49% /home
> > > > >
> > > > > BTW, are you working in your home directory?
> > > > >
> > > > No, I'm not working in the home directory
> > >
> > > then I think this is the main issue. You have lots of free space
> > > in your home directory, you should work there. I only work in my
> > > home directory.
> > >
> > > I believe you weren't able to complete the compilation because
> > > you were working in the root partition where you have less
> > > space available.
> > >
> > > Andi
> > >
> > Hello Andi,
> >
> > Thank you for your response. So I'm not sure I understand what you mean
> > by do all you work in the home directory so I will explain how I work
> > now to see if that is what you mean.
> >
> > I have the staging respository in my home directory and I usually
> > do all my compilation from inside the directory of the staging
> > repository that is saved in my home directory.
> >
> > Is this what you mean by working from the home directory? or is there other setups I should be doing my home directory?

yes, I mean the directory where you clone and build the kernel.
If you do that in your home directory, then it's fine.

> > Also I deleted the offending file in my /boot :
> >
> > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> >
> > and deleted its module directory in usr/lib/modules
> >
> > I realised it was too large compared to the other kernels and assumed
> > that probably I didn't do its .config file properly which might have enabled
> > more modules than is needed for it to run on my machine.
> >
> > this is the result of df -h after the deletion:
> > Filesystem      Size  Used Avail Use% Mounted on
> > tmpfs           784M  2.0M  782M   1% /run
> > /dev/sda9        23G   11G   12G  47% /
> > tmpfs           3.9G  193M  3.7G   5% /dev/shm
> > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > /dev/sda7       944M  201M  678M  23% /boot
> > /dev/sda11       60G   28G   30G  49% /home
> > /dev/sda2        96M   32M   65M  33% /boot/efi
> > tmpfs           784M  144K  784M   1% /run/user/1000
> >
> > I want to generate a new .config file and recompile. I also realised
> > that the staging repository I have on my machine is 28GB large is this
> > normal?

Yes, it's normaly. 28GB is a lot though, I guess you are using a
big config.

> When you start compiling the Linux kernel it gets very big.  But maybe you
> reduced your config at some point, but didn't delete the no longer needed
> .o files?  You could try make clean and then recompile.

You could try with a "make distclean", before doing again
everything, to cut some bytes down. This way you would start
afresh.

Andi

PS my working machine has 110GB, not far from yours :-)

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Gilbert Adikankwu]

Hello Andi, 

On Wed, Oct 11, 2023 at 09:10:54AM +0200, Andi Shyti wrote:
> Hi Gilbert,
> 
> > > > > > > > > You have too little space in the partition that contains /boot?
> > > > > > > >
> > > > > > > > What does "df -h" say?
> > > > > > > >
> > > > > > > > Andi
> > > > > > >
> > > > > > > This is what df -h returned:
> > > > > > >
> > > > > > > Filesystem      Size  Used Avail Use% Mounted on
> > > > > > > tmpfs           784M  2.0M  782M   1% /run
> > > > > > > /dev/sda9        23G   17G  5.6G  75% /
> > > > > > > tmpfs           3.9G   45M  3.8G   2% /dev/shm
> > > > > > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > > > > > /dev/sda7       944M  761M  119M  87% /boot
> > > > > >
> > > > > > I wonder why your boot directory is so packed, even though 119M
> > > > > > should be enough.
> > > > > >
> > > >
> > > > > I don't why it is so packed either. I ran du -ah /boot/ and it returned:
> > > > > 272K /boot/config-6.2.0-34-generic
> > > > > 14M /boot/vmlinuz-6.6.0-rc1gilbert+
> > > > > 0 /boot/initrd.img
> > > > > 276K /boot/config-6.6.0-rc1gilbert+
> > > > > 14M /boot/vmlinuz-6.2.0-34-generic
> > > > > 184K /boot/memtest86+_multiboot.bin
> > > > > 7.6M /boot/System.map-6.2.0-26-generic
> > > > > 180K /boot/memtest86+.bin
> > > > > 184K /boot/memtest86+.elf
> > > > > 67M /boot/initrd.img-6.2.0-34-generic
> > > > > 7.7M /boot/System.map-6.2.0-34-generic
> > > > > du: cannot read directory '/boot/efi': Permission denied
> > > > > 1.0K /boot/efi
> > > > > 0 /boot/vmlinuz
> > > > > 7.6M /boot/System.map-6.6.0-rc1gilbert+
> > > > > du: cannot read directory '/boot/lost+found': Permission denied
> > > > > 16K /boot/lost+found
> > > > > 14M /boot/vmlinuz-6.2.0-26-generic
> > > > > 4.0K /boot/grub/x86_64-efi/lsefimmap.mod
> > > > > 4.0K /boot/grub/x86_64-efi/setjmp.mod
> > > > > 12K /boot/grub/x86_64-efi/loadenv.mod
> > > >
> > > > ...
> > > >
> > > > > 4.0K /boot/grub/i386-pc/search_fs_uuid.mod
> > > > > 2.5M /boot/grub/i386-pc
> > > > > 11M /boot/grub
> > > > > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > > > > 74M /boot/initrd.img-6.2.0-26-generic
> > > > > 272K /boot/config-6.2.0-26-generic
> > > > >
> > > > > I apologize for the overly long list
> > > >
> > > > that's a long list indeed. I don't know what all those files are,
> > > > but I don't think they are an issue.
> > > >
> > > > > > > /dev/sda11       60G   28G   30G  49% /home
> > > > > >
> > > > > > BTW, are you working in your home directory?
> > > > > >
> > > > > No, I'm not working in the home directory
> > > >
> > > > then I think this is the main issue. You have lots of free space
> > > > in your home directory, you should work there. I only work in my
> > > > home directory.
> > > >
> > > > I believe you weren't able to complete the compilation because
> > > > you were working in the root partition where you have less
> > > > space available.
> > > >
> > > > Andi
> > > >
> > > Hello Andi,
> > >
> > > Thank you for your response. So I'm not sure I understand what you mean
> > > by do all you work in the home directory so I will explain how I work
> > > now to see if that is what you mean.
> > >
> > > I have the staging respository in my home directory and I usually
> > > do all my compilation from inside the directory of the staging
> > > repository that is saved in my home directory.
> > >
> > > Is this what you mean by working from the home directory? or is there other setups I should be doing my home directory?
> 
> yes, I mean the directory where you clone and build the kernel.
> If you do that in your home directory, then it's fine.
> 
> > > Also I deleted the offending file in my /boot :
> > >
> > > 547M /boot/initrd.img-6.6.0-rc1gilbert+
> > >
> > > and deleted its module directory in usr/lib/modules
> > >
> > > I realised it was too large compared to the other kernels and assumed
> > > that probably I didn't do its .config file properly which might have enabled
> > > more modules than is needed for it to run on my machine.
> > >
> > > this is the result of df -h after the deletion:
> > > Filesystem      Size  Used Avail Use% Mounted on
> > > tmpfs           784M  2.0M  782M   1% /run
> > > /dev/sda9        23G   11G   12G  47% /
> > > tmpfs           3.9G  193M  3.7G   5% /dev/shm
> > > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > > /dev/sda7       944M  201M  678M  23% /boot
> > > /dev/sda11       60G   28G   30G  49% /home
> > > /dev/sda2        96M   32M   65M  33% /boot/efi
> > > tmpfs           784M  144K  784M   1% /run/user/1000
> > >
> > > I want to generate a new .config file and recompile. I also realised
> > > that the staging repository I have on my machine is 28GB large is this
> > > normal?
> 
> Yes, it's normaly. 28GB is a lot though, I guess you are using a
> big config.
> 
> > When you start compiling the Linux kernel it gets very big.  But maybe you
> > reduced your config at some point, but didn't delete the no longer needed
> > .o files?  You could try make clean and then recompile.
> 
I found the cause of the oversize memory problem. It turns out to be
debugging symbols after all. I found out that originally installed modules are 
stripped (don't know what that means yet). from 
Documentation/kbuild/makefile.txt:
	INSTALL_MOD_STRIP

	If this variable is specified, will cause modules to be stripped
	after they are installed.  If INSTALL_MOD_STRIP is '1', then the
	default option --strip-debug will be used.  Otherwise,
	INSTALL_MOD_STRIP will used as the option(s) to the strip command.

So I recompiled the modules like this:

$ make modules_install INSTALL_MOD_STRIP=1

then ran df -h: 

Filesystem      Size  Used Avail Use% Mounted on
tmpfs           786M  2.1M  784M   1% /run
/dev/sda9        23G   11G   11G  50% /
tmpfs           3.9G   73M  3.8G   2% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
efivarfs        128K   88K   36K  71% /sys/firmware/efi/efivars
/dev/sda7       944M  282M  598M  33% /boot
/dev/sda11       60G   27G   31G  48% /home
/dev/sda2        96M   32M   65M  33% /boot/efi
tmpfs           786M  124K  785M   1% /run/user/1000

> You could try with a "make distclean", before doing again
> everything, to cut some bytes down. This way you would start
> afresh.
> 
> Andi
> 
> PS my working machine has 110GB, not far from yours :-)

Hahaha, thank you for sharing... I'm inspired!

Thanks
Gilbert

Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS

[Julia Lawall]

> I found the cause of the oversize memory problem. It turns out to be
> debugging symbols after all. I found out that originally installed modules are
> stripped (don't know what that means yet). from
> Documentation/kbuild/makefile.txt:
> 	INSTALL_MOD_STRIP

Yes!  Not sure why the tutorial doens't mention this.  You should do:

INSTALL_MOD_STRIP=1 make modules_install

julia