*** Error ***

*** Error ***

[Luis Carlos Moreira da Costa]

[-- Attachment #1.1: Type: text/plain, Size: 2123 bytes --]


Could someone help me, goatees to know why this error happens?

Regards,
LuisCM

=========================================================

package com.alog.xenapi.luis;

import java.net.URL;

import com.xensource.xenapi.APIVersion;
import com.xensource.xenapi.Connection;
import com.xensource.xenapi.Session;

public final class TCon {

     private final static String HOSTNAME = "http://187.33.17.4:9363";
     private final static String USERNAME = "root";
     private final static String PASSWORD = "xyz#!232";

     protected static Connection connection;
     private static String connectionName;

     protected static void connect() throws Exception {
         connection = new Connection( new URL( HOSTNAME ) );
         System.out.println( String.format( "logging in to '%s' as '%s' 
with password '%s'...", HOSTNAME, USERNAME, PASSWORD ) );
         System.out.println( "connection.getSessionReference() " + 
connection.getSessionReference() );
         Session.loginWithPassword( connection, USERNAME, PASSWORD, 
APIVersion.latest().toString() );
         System.out.println( "Success" );
         connectionName = HOSTNAME;
     }

     protected static void disconnect() throws Exception {
         System.out.println( "disposing connection for " + connectionName );
         Session.logout( connection );
     }

     public static void main( final String[] args ) throws Exception {
         TCon.connect();
         TCon.disconnect();
     }

}

/**

logging in to 'http://187.33.17.4:9363' as 'root' with password 
'xyz#!232'...
connection.getSessionReference() null
Exception in thread "main" You tried to call a method with the incorrect 
number of parameters.  The fully-qualified method name that you used, 
and the number of received and expected parameters are returned.
     at com.xensource.xenapi.Types.checkResponse(Types.java:1291)
     at com.xensource.xenapi.Connection.dispatch(Connection.java:367)
     at com.xensource.xenapi.Session.loginWithPassword(Session.java:490)
     at com.alog.xenapi.luis.TCon.connect(TCon.java:22)
     at com.alog.xenapi.luis.TCon.main(TCon.java:33)

*/



[-- Attachment #1.2: Type: text/html, Size: 3550 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: *** Error ***

[Ian Campbell]

This sort of question is better asked on the xen-api mailing list.

My apologies for misdirecting you here in private mail, it wasn't clear
which sort of "xen development" you were referring to in your mail.

Ian.


On Tue, 2010-08-03 at 15:48 +0100, Luis Carlos Moreira da Costa wrote:
> 
> Could someone help me, goatees to know why this error happens?
> 
> Regards,
> LuisCM
> 
> =========================================================
> 
> package com.alog.xenapi.luis;
> 
> import java.net.URL;
> 
> import com.xensource.xenapi.APIVersion;
> import com.xensource.xenapi.Connection;
> import com.xensource.xenapi.Session;
> 
> public final class TCon {
> 
>     private final static String HOSTNAME = "http://187.33.17.4:9363";
>     private final static String USERNAME = "root";
>     private final static String PASSWORD = "xyz#!232";
>    
>     protected static Connection connection;
>     private static String connectionName;
>    
>     protected static void connect() throws Exception {
>         connection = new Connection( new URL( HOSTNAME ) );
>         System.out.println( String.format( "logging in to '%s' as '%s'
> with password '%s'...", HOSTNAME, USERNAME, PASSWORD ) );
>         System.out.println( "connection.getSessionReference() " +
> connection.getSessionReference() );
>         Session.loginWithPassword( connection, USERNAME, PASSWORD,
> APIVersion.latest().toString() );
>         System.out.println( "Success" );
>         connectionName = HOSTNAME;
>     }
> 
>     protected static void disconnect() throws Exception {
>         System.out.println( "disposing connection for " +
> connectionName );
>         Session.logout( connection );
>     }
> 
>     public static void main( final String[] args ) throws Exception {
>         TCon.connect();
>         TCon.disconnect();
>     }
>    
> }
> 
> /**
> 
> logging in to 'http://187.33.17.4:9363' as 'root' with password 'xyz#!
> 232'...
> connection.getSessionReference() null
> Exception in thread "main" You tried to call a method with the
> incorrect number of parameters.  The fully-qualified method name that
> you used, and the number of received and expected parameters are
> returned.
>     at com.xensource.xenapi.Types.checkResponse(Types.java:1291)
>     at com.xensource.xenapi.Connection.dispatch(Connection.java:367)
>     at
> com.xensource.xenapi.Session.loginWithPassword(Session.java:490)
>     at com.alog.xenapi.luis.TCon.connect(TCon.java:22)
>     at com.alog.xenapi.luis.TCon.main(TCon.java:33)
> 
> */
> 
> 

[Error]

[Isoken Ibizugbe]

while cloning the Linux kernel repo, I had this error, please I need
help in resolving it;
git clone -b staging-testing
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
Cloning into 'staging'...
remote: Enumerating objects: 9716192, done.
remote: Counting objects: 100% (32/32), done.
remote: Compressing objects: 100% (2/2), done.
Receiving objects:  26% (2602687/9716192), 1.26 GiB | 452.00 KiB/s

error: index-pack died of signal 9716192), 2.10 GiB | 302.00 KiB/s
fatal: index-pack failed

Re: [Error]

[Deepak R Varma]

On Tue, Oct 03, 2023 at 06:50:52PM +0100, Isoken Ibizugbe wrote:
> while cloning the Linux kernel repo, I had this error, please I need
> help in resolving it;
> git clone -b staging-testing
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> Cloning into 'staging'...
> remote: Enumerating objects: 9716192, done.
> remote: Counting objects: 100% (32/32), done.
> remote: Compressing objects: 100% (2/2), done.
> Receiving objects:  26% (2602687/9716192), 1.26 GiB | 452.00 KiB/s
> 
> error: index-pack died of signal 9716192), 2.10 GiB | 302.00 KiB/s
> fatal: index-pack failed

Hi Isoken,
This may be related to the directory permission or memory available. Check this
[0] previous discussion on similar issue:

[0] https://forum.linuxfoundation.org/discussion/858596/index-pack-died-of-signal-9

regards,
deepak.

> 

Re: [Error]

[Andi Shyti]

> while cloning the Linux kernel repo, I had this error, please I need
> help in resolving it;
> git clone -b staging-testing
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git

try with https instead of git:

git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git

Andi

Re: [Error]

[Isoken Ibizugbe]

Thanks for helping me resolve the former issue, but I have an issue
when running make in the "building kernel step" of the tutorial. Here
is the error message:
make[3]: *** No rule to make target 'debian/canonical-certs.pem',
needed by 'certs/x509_certificate_list'.  Stop.
make[2]: *** [scripts/Makefile.build:480: certs] Error 2
make[1]: *** [/home/vagrant/git/staging/Makefile:1913: .] Error 2
make: *** [Makefile:234: __sub-make] Error 2

On Tue, Oct 3, 2023 at 11:18 PM Andi Shyti <andi.shyti@linux.intel.com> wrote:
>
> > while cloning the Linux kernel repo, I had this error, please I need
> > help in resolving it;
> > git clone -b staging-testing
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
>
> try with https instead of git:
>
> git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git
>
> Andi

Re: [Error]

[Julia Lawall]

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



On Wed, 4 Oct 2023, Isoken Ibizugbe wrote:

> Thanks for helping me resolve the former issue, but I have an issue
> when running make in the "building kernel step" of the tutorial. Here
> is the error message:
> make[3]: *** No rule to make target 'debian/canonical-certs.pem',
> needed by 'certs/x509_certificate_list'.  Stop.
> make[2]: *** [scripts/Makefile.build:480: certs] Error 2
> make[1]: *** [/home/vagrant/git/staging/Makefile:1913: .] Error 2
> make: *** [Makefile:234: __sub-make] Error 2

This is discussed here:

https://stackoverflow.com/questions/67670169/compiling-kernel-gives-error-no-rule-to-make-target-debian-certs-debian-uefi-ce

You can just follow the instructions about removing the whole key thing:

This thread might help you :
lists.debian.org/debian-kernel/2016/04/msg00579.html. In the .config file
copied from /boot find and comment out the lines CONFIG_SYSTEM_TRUSTED_KEY
and CONFIG_MODULE_SIG_KEY. –
Altaf
May 24, 2021 at 11:17

Then you can run make olddefconfig before trying again to compile.

julia


>
> On Tue, Oct 3, 2023 at 11:18 PM Andi Shyti <andi.shyti@linux.intel.com> wrote:
> >
> > > while cloning the Linux kernel repo, I had this error, please I need
> > > help in resolving it;
> > > git clone -b staging-testing
> > > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> >
> > try with https instead of git:
> >
> > git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git
> >
> > Andi
>
>

Re: [Error]

[Isoken Ibizugbe]

Yes I copied the .config file of the currently running kernel and I'm
using Ubuntu 20.04LTS on a virtual box, I renamed the
CONFIG_LOCALVERSION in the .config and commented out these lines
CONFIG_SYSTEM_TRUSTED_KEY
and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
compiling for 10 hours now. please is this normal?

Re: [Error]

[Isoken Ibizugbe]

Thank you for the clarification.

On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
>
>
>
> On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
> Yes I copied the .config file of the currently running kernel and I'm
> using Ubuntu 20.04LTS on a virtual box, I renamed the
> CONFIG_LOCALVERSION in the .config and commented out these lines
> CONFIG_SYSTEM_TRUSTED_KEY
> and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
> compiling for 10 hours now. please is this normal?
>
> Hello Isoken,
>
> Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
>
> Regards
> Sumitra

Re: [Error]

[Julia Lawall]

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



On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:

> Thank you for the clarification.

I think your configuration is too big.  You can try make localmodconfig
and see if you get a smaller configuration.

Does your VM actually have 4 cores?

julia


>
> On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
> >
> >
> >
> > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
> > Yes I copied the .config file of the currently running kernel and I'm
> > using Ubuntu 20.04LTS on a virtual box, I renamed the
> > CONFIG_LOCALVERSION in the .config and commented out these lines
> > CONFIG_SYSTEM_TRUSTED_KEY
> > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
> > compiling for 10 hours now. please is this normal?
> >
> > Hello Isoken,
> >
> > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
> >
> > Regards
> > Sumitra
>
>

Re: [Error]

[Julia Lawall]

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



On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:

> Thanks for the help, I set the .config to default and commented out the former instructions like before and ran make. It compiled successful.

I'm not sure to understand.  You mean that after 10 hours it finally
completed?  Or that you started over and it became faster?

julia


>
> On Thu, 5 Oct 2023 at 9:56 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>
>       > I just checked and the virtual machine has 4 CPUs but is set to 2, should I end the building process and use make localmodconfig?
>
>       I think you can run make localmodconfig from another directory, to have
>       the generated files be put in that other directory.  You could do:
>
>       make O=/path/to/mydir localmodconfig
>
>       https://stackoverflow.com/questions/15969694/make-o-files-in-separate-folder-in-linux-kernel-compilation
>
>       I have not tried this though.  Copy your .config file to some other file
>       first for easy reference.
>
>       In this way, maybe you can keep your current compilation running and see
>       if make localmodconfig would be beneficial.
>
>       julia
>
>       >
>       > On Thu, 5 Oct 2023 at 9:24 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >
>       >
>       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >
>       >       > Thank you for the clarification.
>       >
>       >       I think your configuration is too big.  You can try make localmodconfig
>       >       and see if you get a smaller configuration.
>       >
>       >       Does your VM actually have 4 cores?
>       >
>       >       julia
>       >
>       >
>       >       >
>       >       > On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
>       >       > >
>       >       > >
>       >       > >
>       >       > > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
>       >       > > Yes I copied the .config file of the currently running kernel and I'm
>       >       > > using Ubuntu 20.04LTS on a virtual box, I renamed the
>       >       > > CONFIG_LOCALVERSION in the .config and commented out these lines
>       >       > > CONFIG_SYSTEM_TRUSTED_KEY
>       >       > > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
>       >       > > compiling for 10 hours now. please is this normal?
>       >       > >
>       >       > > Hello Isoken,
>       >       > >
>       >       > > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
>       >       > >
>       >       > > Regards
>       >       > > Sumitra
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>

Re: [Error]

[Julia Lawall]

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



On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:

> The .config file was a copy from my running kernel using this commmand cp /boot/config- name -r * .config.  Then I generated a new default configuration using ‘make defconfig’. I had followed this from another resource before you suggested using
> ‘make localmodconfig’

OK, make defconfig will indeed result in a much smaller configuration.  I
don't know if it will boot on your machine.  But if it does, then that's
fine.

julia

>
> On Thu, 5 Oct 2023 at 11:03 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>
>       > I started by setting .config to default and started over it again
>
>       What do you mean by "setting .config to default"?  And what was the
>       .config file before?
>
>       julia
>
>       >
>       > On Thu, 5 Oct 2023 at 10:44 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >
>       >
>       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >
>       >       > Thanks for the help, I set the .config to default and commented out the former instructions like before and ran make. It compiled successful.
>       >
>       >       I'm not sure to understand.  You mean that after 10 hours it finally
>       >       completed?  Or that you started over and it became faster?
>       >
>       >       julia
>       >
>       >
>       >       >
>       >       > On Thu, 5 Oct 2023 at 9:56 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       >
>       >       >
>       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       >
>       >       >       > I just checked and the virtual machine has 4 CPUs but is set to 2, should I end the building process and use make localmodconfig?
>       >       >
>       >       >       I think you can run make localmodconfig from another directory, to have
>       >       >       the generated files be put in that other directory.  You could do:
>       >       >
>       >       >       make O=/path/to/mydir localmodconfig
>       >       >
>       >       >       https://stackoverflow.com/questions/15969694/make-o-files-in-separate-folder-in-linux-kernel-compilation
>       >       >
>       >       >       I have not tried this though.  Copy your .config file to some other file
>       >       >       first for easy reference.
>       >       >
>       >       >       In this way, maybe you can keep your current compilation running and see
>       >       >       if make localmodconfig would be beneficial.
>       >       >
>       >       >       julia
>       >       >
>       >       >       >
>       >       >       > On Thu, 5 Oct 2023 at 9:24 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       >       >
>       >       >       >
>       >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       >       >
>       >       >       >       > Thank you for the clarification.
>       >       >       >
>       >       >       >       I think your configuration is too big.  You can try make localmodconfig
>       >       >       >       and see if you get a smaller configuration.
>       >       >       >
>       >       >       >       Does your VM actually have 4 cores?
>       >       >       >
>       >       >       >       julia
>       >       >       >
>       >       >       >
>       >       >       >       >
>       >       >       >       > On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
>       >       >       >       > >
>       >       >       >       > >
>       >       >       >       > >
>       >       >       >       > > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
>       >       >       >       > > Yes I copied the .config file of the currently running kernel and I'm
>       >       >       >       > > using Ubuntu 20.04LTS on a virtual box, I renamed the
>       >       >       >       > > CONFIG_LOCALVERSION in the .config and commented out these lines
>       >       >       >       > > CONFIG_SYSTEM_TRUSTED_KEY
>       >       >       >       > > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
>       >       >       >       > > compiling for 10 hours now. please is this normal?
>       >       >       >       > >
>       >       >       >       > > Hello Isoken,
>       >       >       >       > >
>       >       >       >       > > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
>       >       >       >       > >
>       >       >       >       > > Regards
>       >       >       >       > > Sumitra
>       >       >       >       >
>       >       >       >       >
>       >       >       >
>       >       >       >
>       >       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>

Re: [Error]

[Isoken Ibizugbe]

Thanks for the help. I made changes to the probe function by adding
the printk line to it 'printk(KERN_DEBUG "I can modify the Linux
kernel!\n");' , compiled and installed the changes , rebooted my VM
and ran 'dmesg | less' test the changes, but can not  find the
changes. please what should I do?

On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>
> On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>
> > The .config file was a copy from my running kernel using this commmand cp /boot/config- name -r * .config.  Then I generated a new default configuration using ‘make defconfig’. I had followed this from another resource before you suggested using
> > ‘make localmodconfig’
>
> OK, make defconfig will indeed result in a much smaller configuration.  I
> don't know if it will boot on your machine.  But if it does, then that's
> fine.
>
> julia
>
> >
> > On Thu, 5 Oct 2023 at 11:03 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> >
> >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >
> >       > I started by setting .config to default and started over it again
> >
> >       What do you mean by "setting .config to default"?  And what was the
> >       .config file before?
> >
> >       julia
> >
> >       >
> >       > On Thu, 5 Oct 2023 at 10:44 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >       >
> >       >
> >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >
> >       >       > Thanks for the help, I set the .config to default and commented out the former instructions like before and ran make. It compiled successful.
> >       >
> >       >       I'm not sure to understand.  You mean that after 10 hours it finally
> >       >       completed?  Or that you started over and it became faster?
> >       >
> >       >       julia
> >       >
> >       >
> >       >       >
> >       >       > On Thu, 5 Oct 2023 at 9:56 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >       >       >
> >       >       >
> >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >       >
> >       >       >       > I just checked and the virtual machine has 4 CPUs but is set to 2, should I end the building process and use make localmodconfig?
> >       >       >
> >       >       >       I think you can run make localmodconfig from another directory, to have
> >       >       >       the generated files be put in that other directory.  You could do:
> >       >       >
> >       >       >       make O=/path/to/mydir localmodconfig
> >       >       >
> >       >       >       https://stackoverflow.com/questions/15969694/make-o-files-in-separate-folder-in-linux-kernel-compilation
> >       >       >
> >       >       >       I have not tried this though.  Copy your .config file to some other file
> >       >       >       first for easy reference.
> >       >       >
> >       >       >       In this way, maybe you can keep your current compilation running and see
> >       >       >       if make localmodconfig would be beneficial.
> >       >       >
> >       >       >       julia
> >       >       >
> >       >       >       >
> >       >       >       > On Thu, 5 Oct 2023 at 9:24 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >       >       >       >
> >       >       >       >
> >       >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >       >       >
> >       >       >       >       > Thank you for the clarification.
> >       >       >       >
> >       >       >       >       I think your configuration is too big.  You can try make localmodconfig
> >       >       >       >       and see if you get a smaller configuration.
> >       >       >       >
> >       >       >       >       Does your VM actually have 4 cores?
> >       >       >       >
> >       >       >       >       julia
> >       >       >       >
> >       >       >       >
> >       >       >       >       >
> >       >       >       >       > On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
> >       >       >       >       > >
> >       >       >       >       > >
> >       >       >       >       > >
> >       >       >       >       > > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
> >       >       >       >       > > Yes I copied the .config file of the currently running kernel and I'm
> >       >       >       >       > > using Ubuntu 20.04LTS on a virtual box, I renamed the
> >       >       >       >       > > CONFIG_LOCALVERSION in the .config and commented out these lines
> >       >       >       >       > > CONFIG_SYSTEM_TRUSTED_KEY
> >       >       >       >       > > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
> >       >       >       >       > > compiling for 10 hours now. please is this normal?
> >       >       >       >       > >
> >       >       >       >       > > Hello Isoken,
> >       >       >       >       > >
> >       >       >       >       > > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
> >       >       >       >       > >
> >       >       >       >       > > Regards
> >       >       >       >       > > Sumitra
> >       >       >       >       >
> >       >       >       >       >
> >       >       >       >
> >       >       >       >
> >       >       >       >
> >       >       >
> >       >       >
> >       >       >
> >       >
> >       >
> >       >
> >
> >
> >

Re: [Error]

[Julia Lawall]

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



On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:

> Thanks for the help. I made changes to the probe function by adding
> the printk line to it 'printk(KERN_DEBUG "I can modify the Linux
> kernel!\n");' , compiled and installed the changes , rebooted my VM
> and ran 'dmesg | less' test the changes, but can not  find the
> changes. please what should I do?

What driver did you change?  Did you compile the affected file?  Do you
have the corresponding device?

julia

>
> On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> >
> >
> > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >
> > > The .config file was a copy from my running kernel using this commmand cp /boot/config- name -r * .config.  Then I generated a new default configuration using ‘make defconfig’. I had followed this from another resource before you suggested using
> > > ‘make localmodconfig’
> >
> > OK, make defconfig will indeed result in a much smaller configuration.  I
> > don't know if it will boot on your machine.  But if it does, then that's
> > fine.
> >
> > julia
> >
> > >
> > > On Thu, 5 Oct 2023 at 11:03 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >
> > >
> > >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >
> > >       > I started by setting .config to default and started over it again
> > >
> > >       What do you mean by "setting .config to default"?  And what was the
> > >       .config file before?
> > >
> > >       julia
> > >
> > >       >
> > >       > On Thu, 5 Oct 2023 at 10:44 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >       >
> > >       >
> > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >
> > >       >       > Thanks for the help, I set the .config to default and commented out the former instructions like before and ran make. It compiled successful.
> > >       >
> > >       >       I'm not sure to understand.  You mean that after 10 hours it finally
> > >       >       completed?  Or that you started over and it became faster?
> > >       >
> > >       >       julia
> > >       >
> > >       >
> > >       >       >
> > >       >       > On Thu, 5 Oct 2023 at 9:56 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >       >       >
> > >       >       >
> > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >       >
> > >       >       >       > I just checked and the virtual machine has 4 CPUs but is set to 2, should I end the building process and use make localmodconfig?
> > >       >       >
> > >       >       >       I think you can run make localmodconfig from another directory, to have
> > >       >       >       the generated files be put in that other directory.  You could do:
> > >       >       >
> > >       >       >       make O=/path/to/mydir localmodconfig
> > >       >       >
> > >       >       >       https://stackoverflow.com/questions/15969694/make-o-files-in-separate-folder-in-linux-kernel-compilation
> > >       >       >
> > >       >       >       I have not tried this though.  Copy your .config file to some other file
> > >       >       >       first for easy reference.
> > >       >       >
> > >       >       >       In this way, maybe you can keep your current compilation running and see
> > >       >       >       if make localmodconfig would be beneficial.
> > >       >       >
> > >       >       >       julia
> > >       >       >
> > >       >       >       >
> > >       >       >       > On Thu, 5 Oct 2023 at 9:24 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >       >       >       >
> > >       >       >       >
> > >       >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >       >       >
> > >       >       >       >       > Thank you for the clarification.
> > >       >       >       >
> > >       >       >       >       I think your configuration is too big.  You can try make localmodconfig
> > >       >       >       >       and see if you get a smaller configuration.
> > >       >       >       >
> > >       >       >       >       Does your VM actually have 4 cores?
> > >       >       >       >
> > >       >       >       >       julia
> > >       >       >       >
> > >       >       >       >
> > >       >       >       >       >
> > >       >       >       >       > On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
> > >       >       >       >       > >
> > >       >       >       >       > >
> > >       >       >       >       > >
> > >       >       >       >       > > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
> > >       >       >       >       > > Yes I copied the .config file of the currently running kernel and I'm
> > >       >       >       >       > > using Ubuntu 20.04LTS on a virtual box, I renamed the
> > >       >       >       >       > > CONFIG_LOCALVERSION in the .config and commented out these lines
> > >       >       >       >       > > CONFIG_SYSTEM_TRUSTED_KEY
> > >       >       >       >       > > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
> > >       >       >       >       > > compiling for 10 hours now. please is this normal?
> > >       >       >       >       > >
> > >       >       >       >       > > Hello Isoken,
> > >       >       >       >       > >
> > >       >       >       >       > > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
> > >       >       >       >       > >
> > >       >       >       >       > > Regards
> > >       >       >       >       > > Sumitra
> > >       >       >       >       >
> > >       >       >       >       >
> > >       >       >       >
> > >       >       >       >
> > >       >       >       >
> > >       >       >
> > >       >       >
> > >       >       >
> > >       >
> > >       >
> > >       >
> > >
> > >
> > >
>

Re: [Error]

[Julia Lawall]

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



On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:

> I modified the e1000 driver and compiled with -j2 according to the tutorial.

Whether a file gets compiled depends on your configuration.  Do you have a
.o file or .ko file for the .c file that you changed?

Please remember to keep the list in CC.  Other people may have better
answers than I do :)

julia

>
> On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>
>       > Thanks for the help. I made changes to the probe function by adding
>       > the printk line to it 'printk(KERN_DEBUG "I can modify the Linux
>       > kernel!\n");' , compiled and installed the changes , rebooted my VM
>       > and ran 'dmesg | less' test the changes, but can not  find the
>       > changes. please what should I do?
>
>       What driver did you change?  Did you compile the affected file?  Do you
>       have the corresponding device?
>
>       julia
>
>       >
>       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall <julia.lawall@inria.fr> wrote:
>       > >
>       > >
>       > >
>       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       > >
>       > > > The .config file was a copy from my running kernel using this commmand cp /boot/config- name -r * .config.  Then I generated a new default configuration using ‘make defconfig’. I had followed this from another resource before you
>       suggested using
>       > > > ‘make localmodconfig’
>       > >
>       > > OK, make defconfig will indeed result in a much smaller configuration.  I
>       > > don't know if it will boot on your machine.  But if it does, then that's
>       > > fine.
>       > >
>       > > julia
>       > >
>       > > >
>       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       > > >
>       > > >
>       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       > > >
>       > > >       > I started by setting .config to default and started over it again
>       > > >
>       > > >       What do you mean by "setting .config to default"?  And what was the
>       > > >       .config file before?
>       > > >
>       > > >       julia
>       > > >
>       > > >       >
>       > > >       > On Thu, 5 Oct 2023 at 10:44 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       > > >       >
>       > > >       >
>       > > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       > > >       >
>       > > >       >       > Thanks for the help, I set the .config to default and commented out the former instructions like before and ran make. It compiled successful.
>       > > >       >
>       > > >       >       I'm not sure to understand.  You mean that after 10 hours it finally
>       > > >       >       completed?  Or that you started over and it became faster?
>       > > >       >
>       > > >       >       julia
>       > > >       >
>       > > >       >
>       > > >       >       >
>       > > >       >       > On Thu, 5 Oct 2023 at 9:56 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       > > >       >       >
>       > > >       >       >
>       > > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       > > >       >       >
>       > > >       >       >       > I just checked and the virtual machine has 4 CPUs but is set to 2, should I end the building process and use make localmodconfig?
>       > > >       >       >
>       > > >       >       >       I think you can run make localmodconfig from another directory, to have
>       > > >       >       >       the generated files be put in that other directory.  You could do:
>       > > >       >       >
>       > > >       >       >       make O=/path/to/mydir localmodconfig
>       > > >       >       >
>       > > >       >       >       https://stackoverflow.com/questions/15969694/make-o-files-in-separate-folder-in-linux-kernel-compilation
>       > > >       >       >
>       > > >       >       >       I have not tried this though.  Copy your .config file to some other file
>       > > >       >       >       first for easy reference.
>       > > >       >       >
>       > > >       >       >       In this way, maybe you can keep your current compilation running and see
>       > > >       >       >       if make localmodconfig would be beneficial.
>       > > >       >       >
>       > > >       >       >       julia
>       > > >       >       >
>       > > >       >       >       >
>       > > >       >       >       > On Thu, 5 Oct 2023 at 9:24 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       > > >       >       >       >
>       > > >       >       >       >
>       > > >       >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       > > >       >       >       >
>       > > >       >       >       >       > Thank you for the clarification.
>       > > >       >       >       >
>       > > >       >       >       >       I think your configuration is too big.  You can try make localmodconfig
>       > > >       >       >       >       and see if you get a smaller configuration.
>       > > >       >       >       >
>       > > >       >       >       >       Does your VM actually have 4 cores?
>       > > >       >       >       >
>       > > >       >       >       >       julia
>       > > >       >       >       >
>       > > >       >       >       >
>       > > >       >       >       >       >
>       > > >       >       >       >       > On Thu, Oct 5, 2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
>       > > >       >       >       >       > >
>       > > >       >       >       >       > >
>       > > >       >       >       >       > >
>       > > >       >       >       >       > > On Thu, 5 Oct, 2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
>       > > >       >       >       >       > > Yes I copied the .config file of the currently running kernel and I'm
>       > > >       >       >       >       > > using Ubuntu 20.04LTS on a virtual box, I renamed the
>       > > >       >       >       >       > > CONFIG_LOCALVERSION in the .config and commented out these lines
>       > > >       >       >       >       > > CONFIG_SYSTEM_TRUSTED_KEY
>       > > >       >       >       >       > > and CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has been
>       > > >       >       >       >       > > compiling for 10 hours now. please is this normal?
>       > > >       >       >       >       > >
>       > > >       >       >       >       > > Hello Isoken,
>       > > >       >       >       >       > >
>       > > >       >       >       >       > > Yes, it is normal. The compilation time depends upon how much RAM you have allocated to your virtual machine. I still use virtual machines and sometimes the kernel building takes two days  :)
>       > > >       >       >       >       > >
>       > > >       >       >       >       > > Regards
>       > > >       >       >       >       > > Sumitra
>       > > >       >       >       >       >
>       > > >       >       >       >       >
>       > > >       >       >       >
>       > > >       >       >       >
>       > > >       >       >       >
>       > > >       >       >
>       > > >       >       >
>       > > >       >       >
>       > > >       >
>       > > >       >
>       > > >       >
>       > > >
>       > > >
>       > > >
>       >
>
>
>

Re: [Error]

[Julia Lawall]

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



On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:

> I cannot boot into my Virtual machine using vagrant after reloading it to
> switch to the new kernel. It gives a warning that there was an error. Do I
> really need to boot into the new kernel to work? . I cannot seem to fix the
> issue, do I need to reinstall the virtual machine and start all over?

Didn't you already get to the point of booting a virtual machine, and the
problem was just that you didn't see the effect of the code that you
changed?

julia


> On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>
>       > I modified the e1000 driver and compiled with -j2 according to
>       the tutorial.
>
>       Whether a file gets compiled depends on your configuration.  Do
>       you have a
>       .o file or .ko file for the .c file that you changed?
>
>       Please remember to keep the list in CC.  Other people may have
>       better
>       answers than I do :)
>
>       julia
>
>       >
>       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
>       <julia.lawall@inria.fr> wrote:
>       >
>       >
>       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >
>       >       > Thanks for the help. I made changes to the probe
>       function by adding
>       >       > the printk line to it 'printk(KERN_DEBUG "I can modify
>       the Linux
>       >       > kernel!\n");' , compiled and installed the changes ,
>       rebooted my VM
>       >       > and ran 'dmesg | less' test the changes, but can not 
>       find the
>       >       > changes. please what should I do?
>       >
>       >       What driver did you change?  Did you compile the
>       affected file?  Do you
>       >       have the corresponding device?
>       >
>       >       julia
>       >
>       >       >
>       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
>       <julia.lawall@inria.fr> wrote:
>       >       > >
>       >       > >
>       >       > >
>       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       > >
>       >       > > > The .config file was a copy from my running kernel
>       using this commmand cp /boot/config- name -r * .config.  Then I
>       generated a new default configuration using ‘make defconfig’. I
>       had followed this from another resource before you
>       >       suggested using
>       >       > > > ‘make localmodconfig’
>       >       > >
>       >       > > OK, make defconfig will indeed result in a much
>       smaller configuration.  I
>       >       > > don't know if it will boot on your machine.  But if
>       it does, then that's
>       >       > > fine.
>       >       > >
>       >       > > julia
>       >       > >
>       >       > > >
>       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia Lawall
>       <julia.lawall@inria.fr> wrote:
>       >       > > >
>       >       > > >
>       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       > > >
>       >       > > >       > I started by setting .config to default
>       and started over it again
>       >       > > >
>       >       > > >       What do you mean by "setting .config to
>       default"?  And what was the
>       >       > > >       .config file before?
>       >       > > >
>       >       > > >       julia
>       >       > > >
>       >       > > >       >
>       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM, Julia
>       Lawall <julia.lawall@inria.fr> wrote:
>       >       > > >       >
>       >       > > >       >
>       >       > > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe
>       wrote:
>       >       > > >       >
>       >       > > >       >       > Thanks for the help, I set the
>       .config to default and commented out the former instructions
>       like before and ran make. It compiled successful.
>       >       > > >       >
>       >       > > >       >       I'm not sure to understand.  You
>       mean that after 10 hours it finally
>       >       > > >       >       completed?  Or that you started over
>       and it became faster?
>       >       > > >       >
>       >       > > >       >       julia
>       >       > > >       >
>       >       > > >       >
>       >       > > >       >       >
>       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56 AM,
>       Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       > > >       >       >
>       >       > > >       >       >
>       >       > > >       >       >       On Thu, 5 Oct 2023, Isoken
>       Ibizugbe wrote:
>       >       > > >       >       >
>       >       > > >       >       >       > I just checked and the
>       virtual machine has 4 CPUs but is set to 2, should I end the
>       building process and use make localmodconfig?
>       >       > > >       >       >
>       >       > > >       >       >       I think you can run make
>       localmodconfig from another directory, to have
>       >       > > >       >       >       the generated files be put
>       in that other directory.  You could do:
>       >       > > >       >       >
>       >       > > >       >       >       make O=/path/to/mydir
>       localmodconfig
>       >       > > >       >       >
>       >       > > >       >       >      https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fold
>       er-in-linux-kernel-compilation
>       >       > > >       >       >
>       >       > > >       >       >       I have not tried this
>       though.  Copy your .config file to some other file
>       >       > > >       >       >       first for easy reference.
>       >       > > >       >       >
>       >       > > >       >       >       In this way, maybe you can
>       keep your current compilation running and see
>       >       > > >       >       >       if make localmodconfig would
>       be beneficial.
>       >       > > >       >       >
>       >       > > >       >       >       julia
>       >       > > >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >       > On Thu, 5 Oct 2023 at 9:24
>       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       > > >       >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >       >       On Thu, 5 Oct 2023,
>       Isoken Ibizugbe wrote:
>       >       > > >       >       >       >
>       >       > > >       >       >       >       > Thank you for the
>       clarification.
>       >       > > >       >       >       >
>       >       > > >       >       >       >       I think your
>       configuration is too big.  You can try make localmodconfig
>       >       > > >       >       >       >       and see if you get a
>       smaller configuration.
>       >       > > >       >       >       >
>       >       > > >       >       >       >       Does your VM
>       actually have 4 cores?
>       >       > > >       >       >       >
>       >       > > >       >       >       >       julia
>       >       > > >       >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >       >       >
>       >       > > >       >       >       >       > On Thu, Oct 5,
>       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com> wrote:
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > > On Thu, 5 Oct,
>       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com> wrote:
>       >       > > >       >       >       >       > > Yes I copied the
>       .config file of the currently running kernel and I'm
>       >       > > >       >       >       >       > > using Ubuntu
>       20.04LTS on a virtual box, I renamed the
>       >       > > >       >       >       >       > >
>       CONFIG_LOCALVERSION in the .config and commented out these lines
>       >       > > >       >       >       >       > >
>       CONFIG_SYSTEM_TRUSTED_KEY
>       >       > > >       >       >       >       > > and
>       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel has
>       been
>       >       > > >       >       >       >       > > compiling for 10
>       hours now. please is this normal?
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > > Hello Isoken,
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > > Yes, it is
>       normal. The compilation time depends upon how much RAM you have
>       allocated to your virtual machine. I still use virtual machines
>       and sometimes the kernel building takes two days  :)
>       >       > > >       >       >       >       > >
>       >       > > >       >       >       >       > > Regards
>       >       > > >       >       >       >       > > Sumitra
>       >       > > >       >       >       >       >
>       >       > > >       >       >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >       >
>       >       > > >       >       >
>       >       > > >       >       >
>       >       > > >       >       >
>       >       > > >       >
>       >       > > >       >
>       >       > > >       >
>       >       > > >
>       >       > > >
>       >       > > >
>       >       >
>       >
>       >
>       >
>
>
>

Re: [Error]

[Julia Lawall]

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



On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:

> I skipped that part, so I went back to edit the grub file.

Not sure what you mean here.

I mean, that I thought you had a working solution for the first step, so I
wonder why you seem to have discarded that and taken another solution?

julia

>
> On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
>
>       > I cannot boot into my Virtual machine using vagrant after
>       reloading it to
>       > switch to the new kernel. It gives a warning that there was an
>       error. Do I
>       > really need to boot into the new kernel to work? . I cannot
>       seem to fix the
>       > issue, do I need to reinstall the virtual machine and start
>       all over?
>
>       Didn't you already get to the point of booting a virtual
>       machine, and the
>       problem was just that you didn't see the effect of the code that
>       you
>       changed?
>
>       julia
>
>
>       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
>       <julia.lawall@inria.fr> wrote:
>       >
>       >
>       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >
>       >       > I modified the e1000 driver and compiled with -j2
>       according to
>       >       the tutorial.
>       >
>       >       Whether a file gets compiled depends on your
>       configuration.  Do
>       >       you have a
>       >       .o file or .ko file for the .c file that you changed?
>       >
>       >       Please remember to keep the list in CC.  Other people
>       may have
>       >       better
>       >       answers than I do :)
>       >
>       >       julia
>       >
>       >       >
>       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
>       >       <julia.lawall@inria.fr> wrote:
>       >       >
>       >       >
>       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       >
>       >       >       > Thanks for the help. I made changes to the
>       probe
>       >       function by adding
>       >       >       > the printk line to it 'printk(KERN_DEBUG "I
>       can modify
>       >       the Linux
>       >       >       > kernel!\n");' , compiled and installed the
>       changes ,
>       >       rebooted my VM
>       >       >       > and ran 'dmesg | less' test the changes, but
>       can not 
>       >       find the
>       >       >       > changes. please what should I do?
>       >       >
>       >       >       What driver did you change?  Did you compile the
>       >       affected file?  Do you
>       >       >       have the corresponding device?
>       >       >
>       >       >       julia
>       >       >
>       >       >       >
>       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
>       >       <julia.lawall@inria.fr> wrote:
>       >       >       > >
>       >       >       > >
>       >       >       > >
>       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>       >       >       > >
>       >       >       > > > The .config file was a copy from my
>       running kernel
>       >       using this commmand cp /boot/config- name -r * .config. 
>       Then I
>       >       generated a new default configuration using ‘make
>       defconfig’. I
>       >       had followed this from another resource before you
>       >       >       suggested using
>       >       >       > > > ‘make localmodconfig’
>       >       >       > >
>       >       >       > > OK, make defconfig will indeed result in a
>       much
>       >       smaller configuration.  I
>       >       >       > > don't know if it will boot on your machine. 
>       But if
>       >       it does, then that's
>       >       >       > > fine.
>       >       >       > >
>       >       >       > > julia
>       >       >       > >
>       >       >       > > >
>       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
>       Lawall
>       >       <julia.lawall@inria.fr> wrote:
>       >       >       > > >
>       >       >       > > >
>       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
>       wrote:
>       >       >       > > >
>       >       >       > > >       > I started by setting .config to
>       default
>       >       and started over it again
>       >       >       > > >
>       >       >       > > >       What do you mean by "setting .config
>       to
>       >       default"?  And what was the
>       >       >       > > >       .config file before?
>       >       >       > > >
>       >       >       > > >       julia
>       >       >       > > >
>       >       >       > > >       >
>       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
>       Julia
>       >       Lawall <julia.lawall@inria.fr> wrote:
>       >       >       > > >       >
>       >       >       > > >       >
>       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
>       Ibizugbe
>       >       wrote:
>       >       >       > > >       >
>       >       >       > > >       >       > Thanks for the help, I set
>       the
>       >       .config to default and commented out the former
>       instructions
>       >       like before and ran make. It compiled successful.
>       >       >       > > >       >
>       >       >       > > >       >       I'm not sure to understand. 
>       You
>       >       mean that after 10 hours it finally
>       >       >       > > >       >       completed?  Or that you
>       started over
>       >       and it became faster?
>       >       >       > > >       >
>       >       >       > > >       >       julia
>       >       >       > > >       >
>       >       >       > > >       >
>       >       >       > > >       >       >
>       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
>       AM,
>       >       Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       >       > > >       >       >
>       >       >       > > >       >       >
>       >       >       > > >       >       >       On Thu, 5 Oct 2023,
>       Isoken
>       >       Ibizugbe wrote:
>       >       >       > > >       >       >
>       >       >       > > >       >       >       > I just checked and
>       the
>       >       virtual machine has 4 CPUs but is set to 2, should I end
>       the
>       >       building process and use make localmodconfig?
>       >       >       > > >       >       >
>       >       >       > > >       >       >       I think you can run
>       make
>       >       localmodconfig from another directory, to have
>       >       >       > > >       >       >       the generated files
>       be put
>       >       in that other directory.  You could do:
>       >       >       > > >       >       >
>       >       >       > > >       >       >       make
>       O=/path/to/mydir
>       >       localmodconfig
>       >       >       > > >       >       >
>       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
>       d
>       >       er-in-linux-kernel-compilation
>       >       >       > > >       >       >
>       >       >       > > >       >       >       I have not tried
>       this
>       >       though.  Copy your .config file to some other file
>       >       >       > > >       >       >       first for easy
>       reference.
>       >       >       > > >       >       >
>       >       >       > > >       >       >       In this way, maybe
>       you can
>       >       keep your current compilation running and see
>       >       >       > > >       >       >       if make
>       localmodconfig would
>       >       be beneficial.
>       >       >       > > >       >       >
>       >       >       > > >       >       >       julia
>       >       >       > > >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       > On Thu, 5 Oct 2023
>       at 9:24
>       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       On Thu, 5
>       Oct 2023,
>       >       Isoken Ibizugbe wrote:
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       > Thank you
>       for the
>       >       clarification.
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       I think your
>       >       configuration is too big.  You can try make
>       localmodconfig
>       >       >       > > >       >       >       >       and see if
>       you get a
>       >       smaller configuration.
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       Does your VM
>       >       actually have 4 cores?
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       julia
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >       >
>       >       >       > > >       >       >       >       > On Thu,
>       Oct 5,
>       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
>       wrote:
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > > On Thu,
>       5 Oct,
>       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
>       wrote:
>       >       >       > > >       >       >       >       > > Yes I
>       copied the
>       >       .config file of the currently running kernel and I'm
>       >       >       > > >       >       >       >       > > using
>       Ubuntu
>       >       20.04LTS on a virtual box, I renamed the
>       >       >       > > >       >       >       >       > >
>       >       CONFIG_LOCALVERSION in the .config and commented out
>       these lines
>       >       >       > > >       >       >       >       > >
>       >       CONFIG_SYSTEM_TRUSTED_KEY
>       >       >       > > >       >       >       >       > > and
>       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
>       has
>       >       been
>       >       >       > > >       >       >       >       > >
>       compiling for 10
>       >       hours now. please is this normal?
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > > Hello
>       Isoken,
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > > Yes, it
>       is
>       >       normal. The compilation time depends upon how much RAM
>       you have
>       >       allocated to your virtual machine. I still use virtual
>       machines
>       >       and sometimes the kernel building takes two days  :)
>       >       >       > > >       >       >       >       > >
>       >       >       > > >       >       >       >       > > Regards
>       >       >       > > >       >       >       >       > > Sumitra
>       >       >       > > >       >       >       >       >
>       >       >       > > >       >       >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >       >
>       >       >       > > >       >       >
>       >       >       > > >       >       >
>       >       >       > > >       >       >
>       >       >       > > >       >
>       >       >       > > >       >
>       >       >       > > >       >
>       >       >       > > >
>       >       >       > > >
>       >       >       > > >
>       >       >       >
>       >       >
>       >       >
>       >       >
>       >
>       >
>       >
>
>
>

Re: [Error]

[Isoken Ibizugbe]

I am sorry for the confusion. After building and installing the kernel
successfully I didn't edit the grub file, so I didn't see my new
kernel after boot, so I went to do that and reboot, but my VM couldn't
load any kernel at all, I don't know if its because I was using
Vagrant, so I downloaded and installed Ubuntu on the VM to start
afresh, but I have been able to finish the first instruction on
compiling and installing, but my compiled kernel doesn't work, can I
work on it from just the directory?

On Sun, Oct 8, 2023 at 7:07 AM Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>
> On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:
>
> > I skipped that part, so I went back to edit the grub file.
>
> Not sure what you mean here.
>
> I mean, that I thought you had a working solution for the first step, so I
> wonder why you seem to have discarded that and taken another solution?
>
> julia
>
> >
> > On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> >
> >       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
> >
> >       > I cannot boot into my Virtual machine using vagrant after
> >       reloading it to
> >       > switch to the new kernel. It gives a warning that there was an
> >       error. Do I
> >       > really need to boot into the new kernel to work? . I cannot
> >       seem to fix the
> >       > issue, do I need to reinstall the virtual machine and start
> >       all over?
> >
> >       Didn't you already get to the point of booting a virtual
> >       machine, and the
> >       problem was just that you didn't see the effect of the code that
> >       you
> >       changed?
> >
> >       julia
> >
> >
> >       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
> >       <julia.lawall@inria.fr> wrote:
> >       >
> >       >
> >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >
> >       >       > I modified the e1000 driver and compiled with -j2
> >       according to
> >       >       the tutorial.
> >       >
> >       >       Whether a file gets compiled depends on your
> >       configuration.  Do
> >       >       you have a
> >       >       .o file or .ko file for the .c file that you changed?
> >       >
> >       >       Please remember to keep the list in CC.  Other people
> >       may have
> >       >       better
> >       >       answers than I do :)
> >       >
> >       >       julia
> >       >
> >       >       >
> >       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
> >       >       <julia.lawall@inria.fr> wrote:
> >       >       >
> >       >       >
> >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >       >
> >       >       >       > Thanks for the help. I made changes to the
> >       probe
> >       >       function by adding
> >       >       >       > the printk line to it 'printk(KERN_DEBUG "I
> >       can modify
> >       >       the Linux
> >       >       >       > kernel!\n");' , compiled and installed the
> >       changes ,
> >       >       rebooted my VM
> >       >       >       > and ran 'dmesg | less' test the changes, but
> >       can not
> >       >       find the
> >       >       >       > changes. please what should I do?
> >       >       >
> >       >       >       What driver did you change?  Did you compile the
> >       >       affected file?  Do you
> >       >       >       have the corresponding device?
> >       >       >
> >       >       >       julia
> >       >       >
> >       >       >       >
> >       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
> >       >       <julia.lawall@inria.fr> wrote:
> >       >       >       > >
> >       >       >       > >
> >       >       >       > >
> >       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >       >       >       > >
> >       >       >       > > > The .config file was a copy from my
> >       running kernel
> >       >       using this commmand cp /boot/config- name -r * .config.
> >       Then I
> >       >       generated a new default configuration using ‘make
> >       defconfig’. I
> >       >       had followed this from another resource before you
> >       >       >       suggested using
> >       >       >       > > > ‘make localmodconfig’
> >       >       >       > >
> >       >       >       > > OK, make defconfig will indeed result in a
> >       much
> >       >       smaller configuration.  I
> >       >       >       > > don't know if it will boot on your machine.
> >       But if
> >       >       it does, then that's
> >       >       >       > > fine.
> >       >       >       > >
> >       >       >       > > julia
> >       >       >       > >
> >       >       >       > > >
> >       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
> >       Lawall
> >       >       <julia.lawall@inria.fr> wrote:
> >       >       >       > > >
> >       >       >       > > >
> >       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
> >       wrote:
> >       >       >       > > >
> >       >       >       > > >       > I started by setting .config to
> >       default
> >       >       and started over it again
> >       >       >       > > >
> >       >       >       > > >       What do you mean by "setting .config
> >       to
> >       >       default"?  And what was the
> >       >       >       > > >       .config file before?
> >       >       >       > > >
> >       >       >       > > >       julia
> >       >       >       > > >
> >       >       >       > > >       >
> >       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
> >       Julia
> >       >       Lawall <julia.lawall@inria.fr> wrote:
> >       >       >       > > >       >
> >       >       >       > > >       >
> >       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
> >       Ibizugbe
> >       >       wrote:
> >       >       >       > > >       >
> >       >       >       > > >       >       > Thanks for the help, I set
> >       the
> >       >       .config to default and commented out the former
> >       instructions
> >       >       like before and ran make. It compiled successful.
> >       >       >       > > >       >
> >       >       >       > > >       >       I'm not sure to understand.
> >       You
> >       >       mean that after 10 hours it finally
> >       >       >       > > >       >       completed?  Or that you
> >       started over
> >       >       and it became faster?
> >       >       >       > > >       >
> >       >       >       > > >       >       julia
> >       >       >       > > >       >
> >       >       >       > > >       >
> >       >       >       > > >       >       >
> >       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
> >       AM,
> >       >       Julia Lawall <julia.lawall@inria.fr> wrote:
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       On Thu, 5 Oct 2023,
> >       Isoken
> >       >       Ibizugbe wrote:
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       > I just checked and
> >       the
> >       >       virtual machine has 4 CPUs but is set to 2, should I end
> >       the
> >       >       building process and use make localmodconfig?
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       I think you can run
> >       make
> >       >       localmodconfig from another directory, to have
> >       >       >       > > >       >       >       the generated files
> >       be put
> >       >       in that other directory.  You could do:
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       make
> >       O=/path/to/mydir
> >       >       localmodconfig
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
> >       d
> >       >       er-in-linux-kernel-compilation
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       I have not tried
> >       this
> >       >       though.  Copy your .config file to some other file
> >       >       >       > > >       >       >       first for easy
> >       reference.
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       In this way, maybe
> >       you can
> >       >       keep your current compilation running and see
> >       >       >       > > >       >       >       if make
> >       localmodconfig would
> >       >       be beneficial.
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       julia
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       > On Thu, 5 Oct 2023
> >       at 9:24
> >       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       On Thu, 5
> >       Oct 2023,
> >       >       Isoken Ibizugbe wrote:
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       > Thank you
> >       for the
> >       >       clarification.
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       I think your
> >       >       configuration is too big.  You can try make
> >       localmodconfig
> >       >       >       > > >       >       >       >       and see if
> >       you get a
> >       >       smaller configuration.
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       Does your VM
> >       >       actually have 4 cores?
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       julia
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >       >
> >       >       >       > > >       >       >       >       > On Thu,
> >       Oct 5,
> >       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
> >       wrote:
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > > On Thu,
> >       5 Oct,
> >       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
> >       wrote:
> >       >       >       > > >       >       >       >       > > Yes I
> >       copied the
> >       >       .config file of the currently running kernel and I'm
> >       >       >       > > >       >       >       >       > > using
> >       Ubuntu
> >       >       20.04LTS on a virtual box, I renamed the
> >       >       >       > > >       >       >       >       > >
> >       >       CONFIG_LOCALVERSION in the .config and commented out
> >       these lines
> >       >       >       > > >       >       >       >       > >
> >       >       CONFIG_SYSTEM_TRUSTED_KEY
> >       >       >       > > >       >       >       >       > > and
> >       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
> >       has
> >       >       been
> >       >       >       > > >       >       >       >       > >
> >       compiling for 10
> >       >       hours now. please is this normal?
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > > Hello
> >       Isoken,
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > > Yes, it
> >       is
> >       >       normal. The compilation time depends upon how much RAM
> >       you have
> >       >       allocated to your virtual machine. I still use virtual
> >       machines
> >       >       and sometimes the kernel building takes two days  :)
> >       >       >       > > >       >       >       >       > >
> >       >       >       > > >       >       >       >       > > Regards
> >       >       >       > > >       >       >       >       > > Sumitra
> >       >       >       > > >       >       >       >       >
> >       >       >       > > >       >       >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >       >
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >
> >       >       >       > > >       >       >
> >       >       >       > > >       >
> >       >       >       > > >       >
> >       >       >       > > >       >
> >       >       >       > > >
> >       >       >       > > >
> >       >       >       > > >
> >       >       >       >
> >       >       >
> >       >       >
> >       >       >
> >       >
> >       >
> >       >
> >
> >
> >

Re: [Error]

[Julia Lawall]

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



On Mon, 9 Oct 2023, Isoken Ibizugbe wrote:

> I am sorry for the confusion. After building and installing the kernel
> successfully I didn't edit the grub file, so I didn't see my new
> kernel after boot, so I went to do that and reboot, but my VM couldn't
> load any kernel at all, I don't know if its because I was using
> Vagrant, so I downloaded and installed Ubuntu on the VM to start
> afresh, but I have been able to finish the first instruction on
> compiling and installing, but my compiled kernel doesn't work, can I
> work on it from just the directory?

I think you should check with the mentor(s) for the project(s) that you
are interested in.  In some sense it is time to move on, since the
contribution period is not very long.  But if you need to be able to
obtain a running kernel for your project, then you need to be able to do
that.

Maybe you can use kexec: https://wiki.archlinux.org/title/kexec
The following arguments: /boot/vmlinuz-linux --initrd=/boot/initramfs-linux.img
both correspond to the kernel you want to boot.

julia

>
> On Sun, Oct 8, 2023 at 7:07 AM Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> >
> >
> > On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:
> >
> > > I skipped that part, so I went back to edit the grub file.
> >
> > Not sure what you mean here.
> >
> > I mean, that I thought you had a working solution for the first step, so I
> > wonder why you seem to have discarded that and taken another solution?
> >
> > julia
> >
> > >
> > > On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >
> > >
> > >       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
> > >
> > >       > I cannot boot into my Virtual machine using vagrant after
> > >       reloading it to
> > >       > switch to the new kernel. It gives a warning that there was an
> > >       error. Do I
> > >       > really need to boot into the new kernel to work? . I cannot
> > >       seem to fix the
> > >       > issue, do I need to reinstall the virtual machine and start
> > >       all over?
> > >
> > >       Didn't you already get to the point of booting a virtual
> > >       machine, and the
> > >       problem was just that you didn't see the effect of the code that
> > >       you
> > >       changed?
> > >
> > >       julia
> > >
> > >
> > >       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
> > >       <julia.lawall@inria.fr> wrote:
> > >       >
> > >       >
> > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >
> > >       >       > I modified the e1000 driver and compiled with -j2
> > >       according to
> > >       >       the tutorial.
> > >       >
> > >       >       Whether a file gets compiled depends on your
> > >       configuration.  Do
> > >       >       you have a
> > >       >       .o file or .ko file for the .c file that you changed?
> > >       >
> > >       >       Please remember to keep the list in CC.  Other people
> > >       may have
> > >       >       better
> > >       >       answers than I do :)
> > >       >
> > >       >       julia
> > >       >
> > >       >       >
> > >       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
> > >       >       <julia.lawall@inria.fr> wrote:
> > >       >       >
> > >       >       >
> > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >       >
> > >       >       >       > Thanks for the help. I made changes to the
> > >       probe
> > >       >       function by adding
> > >       >       >       > the printk line to it 'printk(KERN_DEBUG "I
> > >       can modify
> > >       >       the Linux
> > >       >       >       > kernel!\n");' , compiled and installed the
> > >       changes ,
> > >       >       rebooted my VM
> > >       >       >       > and ran 'dmesg | less' test the changes, but
> > >       can not
> > >       >       find the
> > >       >       >       > changes. please what should I do?
> > >       >       >
> > >       >       >       What driver did you change?  Did you compile the
> > >       >       affected file?  Do you
> > >       >       >       have the corresponding device?
> > >       >       >
> > >       >       >       julia
> > >       >       >
> > >       >       >       >
> > >       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
> > >       >       <julia.lawall@inria.fr> wrote:
> > >       >       >       > >
> > >       >       >       > >
> > >       >       >       > >
> > >       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> > >       >       >       > >
> > >       >       >       > > > The .config file was a copy from my
> > >       running kernel
> > >       >       using this commmand cp /boot/config- name -r * .config.
> > >       Then I
> > >       >       generated a new default configuration using ‘make
> > >       defconfig’. I
> > >       >       had followed this from another resource before you
> > >       >       >       suggested using
> > >       >       >       > > > ‘make localmodconfig’
> > >       >       >       > >
> > >       >       >       > > OK, make defconfig will indeed result in a
> > >       much
> > >       >       smaller configuration.  I
> > >       >       >       > > don't know if it will boot on your machine.
> > >       But if
> > >       >       it does, then that's
> > >       >       >       > > fine.
> > >       >       >       > >
> > >       >       >       > > julia
> > >       >       >       > >
> > >       >       >       > > >
> > >       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
> > >       Lawall
> > >       >       <julia.lawall@inria.fr> wrote:
> > >       >       >       > > >
> > >       >       >       > > >
> > >       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
> > >       wrote:
> > >       >       >       > > >
> > >       >       >       > > >       > I started by setting .config to
> > >       default
> > >       >       and started over it again
> > >       >       >       > > >
> > >       >       >       > > >       What do you mean by "setting .config
> > >       to
> > >       >       default"?  And what was the
> > >       >       >       > > >       .config file before?
> > >       >       >       > > >
> > >       >       >       > > >       julia
> > >       >       >       > > >
> > >       >       >       > > >       >
> > >       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
> > >       Julia
> > >       >       Lawall <julia.lawall@inria.fr> wrote:
> > >       >       >       > > >       >
> > >       >       >       > > >       >
> > >       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
> > >       Ibizugbe
> > >       >       wrote:
> > >       >       >       > > >       >
> > >       >       >       > > >       >       > Thanks for the help, I set
> > >       the
> > >       >       .config to default and commented out the former
> > >       instructions
> > >       >       like before and ran make. It compiled successful.
> > >       >       >       > > >       >
> > >       >       >       > > >       >       I'm not sure to understand.
> > >       You
> > >       >       mean that after 10 hours it finally
> > >       >       >       > > >       >       completed?  Or that you
> > >       started over
> > >       >       and it became faster?
> > >       >       >       > > >       >
> > >       >       >       > > >       >       julia
> > >       >       >       > > >       >
> > >       >       >       > > >       >
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
> > >       AM,
> > >       >       Julia Lawall <julia.lawall@inria.fr> wrote:
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       On Thu, 5 Oct 2023,
> > >       Isoken
> > >       >       Ibizugbe wrote:
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       > I just checked and
> > >       the
> > >       >       virtual machine has 4 CPUs but is set to 2, should I end
> > >       the
> > >       >       building process and use make localmodconfig?
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       I think you can run
> > >       make
> > >       >       localmodconfig from another directory, to have
> > >       >       >       > > >       >       >       the generated files
> > >       be put
> > >       >       in that other directory.  You could do:
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       make
> > >       O=/path/to/mydir
> > >       >       localmodconfig
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
> > >       d
> > >       >       er-in-linux-kernel-compilation
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       I have not tried
> > >       this
> > >       >       though.  Copy your .config file to some other file
> > >       >       >       > > >       >       >       first for easy
> > >       reference.
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       In this way, maybe
> > >       you can
> > >       >       keep your current compilation running and see
> > >       >       >       > > >       >       >       if make
> > >       localmodconfig would
> > >       >       be beneficial.
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       julia
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       > On Thu, 5 Oct 2023
> > >       at 9:24
> > >       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       On Thu, 5
> > >       Oct 2023,
> > >       >       Isoken Ibizugbe wrote:
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       > Thank you
> > >       for the
> > >       >       clarification.
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       I think your
> > >       >       configuration is too big.  You can try make
> > >       localmodconfig
> > >       >       >       > > >       >       >       >       and see if
> > >       you get a
> > >       >       smaller configuration.
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       Does your VM
> > >       >       actually have 4 cores?
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       julia
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >       >
> > >       >       >       > > >       >       >       >       > On Thu,
> > >       Oct 5,
> > >       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
> > >       wrote:
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > > On Thu,
> > >       5 Oct,
> > >       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
> > >       wrote:
> > >       >       >       > > >       >       >       >       > > Yes I
> > >       copied the
> > >       >       .config file of the currently running kernel and I'm
> > >       >       >       > > >       >       >       >       > > using
> > >       Ubuntu
> > >       >       20.04LTS on a virtual box, I renamed the
> > >       >       >       > > >       >       >       >       > >
> > >       >       CONFIG_LOCALVERSION in the .config and commented out
> > >       these lines
> > >       >       >       > > >       >       >       >       > >
> > >       >       CONFIG_SYSTEM_TRUSTED_KEY
> > >       >       >       > > >       >       >       >       > > and
> > >       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
> > >       has
> > >       >       been
> > >       >       >       > > >       >       >       >       > >
> > >       compiling for 10
> > >       >       hours now. please is this normal?
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > > Hello
> > >       Isoken,
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > > Yes, it
> > >       is
> > >       >       normal. The compilation time depends upon how much RAM
> > >       you have
> > >       >       allocated to your virtual machine. I still use virtual
> > >       machines
> > >       >       and sometimes the kernel building takes two days  :)
> > >       >       >       > > >       >       >       >       > >
> > >       >       >       > > >       >       >       >       > > Regards
> > >       >       >       > > >       >       >       >       > > Sumitra
> > >       >       >       > > >       >       >       >       >
> > >       >       >       > > >       >       >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >       >
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >       >
> > >       >       >       > > >       >
> > >       >       >       > > >       >
> > >       >       >       > > >       >
> > >       >       >       > > >
> > >       >       >       > > >
> > >       >       >       > > >
> > >       >       >       >
> > >       >       >
> > >       >       >
> > >       >       >
> > >       >
> > >       >
> > >       >
> > >
> > >
> > >
>
>

Re: [Error]

[Isoken Ibizugbe]

On Mon, Oct 9, 2023 at 7:57 AM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Thanks, I'll check it out.
I cannot enable the driver that I changed. I fixed coding errors for a
file in drivers/staging, but the staging drivers option in the
menuconfig has this symbol '---staging divers', so I cannot open it to
make the driver a module. Please what do I do?
>
> On Mon, 9 Oct 2023 at 7:52 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>>
>>
>>
>> On Mon, 9 Oct 2023, Isoken Ibizugbe wrote:
>>
>> > I am sorry for the confusion. After building and installing the kernel
>> > successfully I didn't edit the grub file, so I didn't see my new
>> > kernel after boot, so I went to do that and reboot, but my VM couldn't
>> > load any kernel at all, I don't know if its because I was using
>> > Vagrant, so I downloaded and installed Ubuntu on the VM to start
>> > afresh, but I have been able to finish the first instruction on
>> > compiling and installing, but my compiled kernel doesn't work, can I
>> > work on it from just the directory?
>>
>> I think you should check with the mentor(s) for the project(s) that you
>> are interested in.  In some sense it is time to move on, since the
>> contribution period is not very long.  But if you need to be able to
>> obtain a running kernel for your project, then you need to be able to do
>> that.
>>
>> Maybe you can use kexec: https://wiki.archlinux.org/title/kexec
>> The following arguments: /boot/vmlinuz-linux --initrd=/boot/initramfs-linux.img
>> both correspond to the kernel you want to boot.
>>
>> julia
>>
>> >
>> > On Sun, Oct 8, 2023 at 7:07 AM Julia Lawall <julia.lawall@inria.fr> wrote:
>> > >
>> > >
>> > >
>> > > On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:
>> > >
>> > > > I skipped that part, so I went back to edit the grub file.
>> > >
>> > > Not sure what you mean here.
>> > >
>> > > I mean, that I thought you had a working solution for the first step, so I
>> > > wonder why you seem to have discarded that and taken another solution?
>> > >
>> > > julia
>> > >
>> > > >
>> > > > On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>> > > >
>> > > >
>> > > >       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
>> > > >
>> > > >       > I cannot boot into my Virtual machine using vagrant after
>> > > >       reloading it to
>> > > >       > switch to the new kernel. It gives a warning that there was an
>> > > >       error. Do I
>> > > >       > really need to boot into the new kernel to work? . I cannot
>> > > >       seem to fix the
>> > > >       > issue, do I need to reinstall the virtual machine and start
>> > > >       all over?
>> > > >
>> > > >       Didn't you already get to the point of booting a virtual
>> > > >       machine, and the
>> > > >       problem was just that you didn't see the effect of the code that
>> > > >       you
>> > > >       changed?
>> > > >
>> > > >       julia
>> > > >
>> > > >
>> > > >       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
>> > > >       <julia.lawall@inria.fr> wrote:
>> > > >       >
>> > > >       >
>> > > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>> > > >       >
>> > > >       >       > I modified the e1000 driver and compiled with -j2
>> > > >       according to
>> > > >       >       the tutorial.
>> > > >       >
>> > > >       >       Whether a file gets compiled depends on your
>> > > >       configuration.  Do
>> > > >       >       you have a
>> > > >       >       .o file or .ko file for the .c file that you changed?
>> > > >       >
>> > > >       >       Please remember to keep the list in CC.  Other people
>> > > >       may have
>> > > >       >       better
>> > > >       >       answers than I do :)
>> > > >       >
>> > > >       >       julia
>> > > >       >
>> > > >       >       >
>> > > >       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
>> > > >       >       <julia.lawall@inria.fr> wrote:
>> > > >       >       >
>> > > >       >       >
>> > > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>> > > >       >       >
>> > > >       >       >       > Thanks for the help. I made changes to the
>> > > >       probe
>> > > >       >       function by adding
>> > > >       >       >       > the printk line to it 'printk(KERN_DEBUG "I
>> > > >       can modify
>> > > >       >       the Linux
>> > > >       >       >       > kernel!\n");' , compiled and installed the
>> > > >       changes ,
>> > > >       >       rebooted my VM
>> > > >       >       >       > and ran 'dmesg | less' test the changes, but
>> > > >       can not
>> > > >       >       find the
>> > > >       >       >       > changes. please what should I do?
>> > > >       >       >
>> > > >       >       >       What driver did you change?  Did you compile the
>> > > >       >       affected file?  Do you
>> > > >       >       >       have the corresponding device?
>> > > >       >       >
>> > > >       >       >       julia
>> > > >       >       >
>> > > >       >       >       >
>> > > >       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
>> > > >       >       <julia.lawall@inria.fr> wrote:
>> > > >       >       >       > >
>> > > >       >       >       > >
>> > > >       >       >       > >
>> > > >       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
>> > > >       >       >       > >
>> > > >       >       >       > > > The .config file was a copy from my
>> > > >       running kernel
>> > > >       >       using this commmand cp /boot/config- name -r * .config.
>> > > >       Then I
>> > > >       >       generated a new default configuration using ‘make
>> > > >       defconfig’. I
>> > > >       >       had followed this from another resource before you
>> > > >       >       >       suggested using
>> > > >       >       >       > > > ‘make localmodconfig’
>> > > >       >       >       > >
>> > > >       >       >       > > OK, make defconfig will indeed result in a
>> > > >       much
>> > > >       >       smaller configuration.  I
>> > > >       >       >       > > don't know if it will boot on your machine.
>> > > >       But if
>> > > >       >       it does, then that's
>> > > >       >       >       > > fine.
>> > > >       >       >       > >
>> > > >       >       >       > > julia
>> > > >       >       >       > >
>> > > >       >       >       > > >
>> > > >       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
>> > > >       Lawall
>> > > >       >       <julia.lawall@inria.fr> wrote:
>> > > >       >       >       > > >
>> > > >       >       >       > > >
>> > > >       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
>> > > >       wrote:
>> > > >       >       >       > > >
>> > > >       >       >       > > >       > I started by setting .config to
>> > > >       default
>> > > >       >       and started over it again
>> > > >       >       >       > > >
>> > > >       >       >       > > >       What do you mean by "setting .config
>> > > >       to
>> > > >       >       default"?  And what was the
>> > > >       >       >       > > >       .config file before?
>> > > >       >       >       > > >
>> > > >       >       >       > > >       julia
>> > > >       >       >       > > >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
>> > > >       Julia
>> > > >       >       Lawall <julia.lawall@inria.fr> wrote:
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
>> > > >       Ibizugbe
>> > > >       >       wrote:
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >       > Thanks for the help, I set
>> > > >       the
>> > > >       >       .config to default and commented out the former
>> > > >       instructions
>> > > >       >       like before and ran make. It compiled successful.
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >       I'm not sure to understand.
>> > > >       You
>> > > >       >       mean that after 10 hours it finally
>> > > >       >       >       > > >       >       completed?  Or that you
>> > > >       started over
>> > > >       >       and it became faster?
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >       julia
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
>> > > >       AM,
>> > > >       >       Julia Lawall <julia.lawall@inria.fr> wrote:
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       On Thu, 5 Oct 2023,
>> > > >       Isoken
>> > > >       >       Ibizugbe wrote:
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       > I just checked and
>> > > >       the
>> > > >       >       virtual machine has 4 CPUs but is set to 2, should I end
>> > > >       the
>> > > >       >       building process and use make localmodconfig?
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       I think you can run
>> > > >       make
>> > > >       >       localmodconfig from another directory, to have
>> > > >       >       >       > > >       >       >       the generated files
>> > > >       be put
>> > > >       >       in that other directory.  You could do:
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       make
>> > > >       O=/path/to/mydir
>> > > >       >       localmodconfig
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
>> > > >       d
>> > > >       >       er-in-linux-kernel-compilation
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       I have not tried
>> > > >       this
>> > > >       >       though.  Copy your .config file to some other file
>> > > >       >       >       > > >       >       >       first for easy
>> > > >       reference.
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       In this way, maybe
>> > > >       you can
>> > > >       >       keep your current compilation running and see
>> > > >       >       >       > > >       >       >       if make
>> > > >       localmodconfig would
>> > > >       >       be beneficial.
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       julia
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       > On Thu, 5 Oct 2023
>> > > >       at 9:24
>> > > >       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       On Thu, 5
>> > > >       Oct 2023,
>> > > >       >       Isoken Ibizugbe wrote:
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       > Thank you
>> > > >       for the
>> > > >       >       clarification.
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       I think your
>> > > >       >       configuration is too big.  You can try make
>> > > >       localmodconfig
>> > > >       >       >       > > >       >       >       >       and see if
>> > > >       you get a
>> > > >       >       smaller configuration.
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       Does your VM
>> > > >       >       actually have 4 cores?
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       julia
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >       >
>> > > >       >       >       > > >       >       >       >       > On Thu,
>> > > >       Oct 5,
>> > > >       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
>> > > >       wrote:
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > > On Thu,
>> > > >       5 Oct,
>> > > >       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
>> > > >       wrote:
>> > > >       >       >       > > >       >       >       >       > > Yes I
>> > > >       copied the
>> > > >       >       .config file of the currently running kernel and I'm
>> > > >       >       >       > > >       >       >       >       > > using
>> > > >       Ubuntu
>> > > >       >       20.04LTS on a virtual box, I renamed the
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       CONFIG_LOCALVERSION in the .config and commented out
>> > > >       these lines
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       CONFIG_SYSTEM_TRUSTED_KEY
>> > > >       >       >       > > >       >       >       >       > > and
>> > > >       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
>> > > >       has
>> > > >       >       been
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       compiling for 10
>> > > >       >       hours now. please is this normal?
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > > Hello
>> > > >       Isoken,
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > > Yes, it
>> > > >       is
>> > > >       >       normal. The compilation time depends upon how much RAM
>> > > >       you have
>> > > >       >       allocated to your virtual machine. I still use virtual
>> > > >       machines
>> > > >       >       and sometimes the kernel building takes two days  :)
>> > > >       >       >       > > >       >       >       >       > >
>> > > >       >       >       > > >       >       >       >       > > Regards
>> > > >       >       >       > > >       >       >       >       > > Sumitra
>> > > >       >       >       > > >       >       >       >       >
>> > > >       >       >       > > >       >       >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >       >
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >       >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >       >
>> > > >       >       >       > > >
>> > > >       >       >       > > >
>> > > >       >       >       > > >
>> > > >       >       >       >
>> > > >       >       >
>> > > >       >       >
>> > > >       >       >
>> > > >       >
>> > > >       >
>> > > >       >
>> > > >
>> > > >
>> > > >
>> >
>> >

Re: [Error]

[Julia Lawall]

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



On Wed, 11 Oct 2023, Isoken Ibizugbe wrote:

> On Mon, Oct 9, 2023 at 7:57 AM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
> >
> > Thanks, I'll check it out.
> I cannot enable the driver that I changed. I fixed coding errors for a
> file in drivers/staging, but the staging drivers option in the
> menuconfig has this symbol '---staging divers', so I cannot open it to
> make the driver a module. Please what do I do?

Maybe try /staging.  Then it should show you what the status is.

julia

> >
> > On Mon, 9 Oct 2023 at 7:52 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >>
> >>
> >>
> >> On Mon, 9 Oct 2023, Isoken Ibizugbe wrote:
> >>
> >> > I am sorry for the confusion. After building and installing the kernel
> >> > successfully I didn't edit the grub file, so I didn't see my new
> >> > kernel after boot, so I went to do that and reboot, but my VM couldn't
> >> > load any kernel at all, I don't know if its because I was using
> >> > Vagrant, so I downloaded and installed Ubuntu on the VM to start
> >> > afresh, but I have been able to finish the first instruction on
> >> > compiling and installing, but my compiled kernel doesn't work, can I
> >> > work on it from just the directory?
> >>
> >> I think you should check with the mentor(s) for the project(s) that you
> >> are interested in.  In some sense it is time to move on, since the
> >> contribution period is not very long.  But if you need to be able to
> >> obtain a running kernel for your project, then you need to be able to do
> >> that.
> >>
> >> Maybe you can use kexec: https://wiki.archlinux.org/title/kexec
> >> The following arguments: /boot/vmlinuz-linux --initrd=/boot/initramfs-linux.img
> >> both correspond to the kernel you want to boot.
> >>
> >> julia
> >>
> >> >
> >> > On Sun, Oct 8, 2023 at 7:07 AM Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > >
> >> > >
> >> > >
> >> > > On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:
> >> > >
> >> > > > I skipped that part, so I went back to edit the grub file.
> >> > >
> >> > > Not sure what you mean here.
> >> > >
> >> > > I mean, that I thought you had a working solution for the first step, so I
> >> > > wonder why you seem to have discarded that and taken another solution?
> >> > >
> >> > > julia
> >> > >
> >> > > >
> >> > > > On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >
> >> > > >
> >> > > >       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >
> >> > > >       > I cannot boot into my Virtual machine using vagrant after
> >> > > >       reloading it to
> >> > > >       > switch to the new kernel. It gives a warning that there was an
> >> > > >       error. Do I
> >> > > >       > really need to boot into the new kernel to work? . I cannot
> >> > > >       seem to fix the
> >> > > >       > issue, do I need to reinstall the virtual machine and start
> >> > > >       all over?
> >> > > >
> >> > > >       Didn't you already get to the point of booting a virtual
> >> > > >       machine, and the
> >> > > >       problem was just that you didn't see the effect of the code that
> >> > > >       you
> >> > > >       changed?
> >> > > >
> >> > > >       julia
> >> > > >
> >> > > >
> >> > > >       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
> >> > > >       <julia.lawall@inria.fr> wrote:
> >> > > >       >
> >> > > >       >
> >> > > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >
> >> > > >       >       > I modified the e1000 driver and compiled with -j2
> >> > > >       according to
> >> > > >       >       the tutorial.
> >> > > >       >
> >> > > >       >       Whether a file gets compiled depends on your
> >> > > >       configuration.  Do
> >> > > >       >       you have a
> >> > > >       >       .o file or .ko file for the .c file that you changed?
> >> > > >       >
> >> > > >       >       Please remember to keep the list in CC.  Other people
> >> > > >       may have
> >> > > >       >       better
> >> > > >       >       answers than I do :)
> >> > > >       >
> >> > > >       >       julia
> >> > > >       >
> >> > > >       >       >
> >> > > >       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >       >
> >> > > >       >       >       > Thanks for the help. I made changes to the
> >> > > >       probe
> >> > > >       >       function by adding
> >> > > >       >       >       > the printk line to it 'printk(KERN_DEBUG "I
> >> > > >       can modify
> >> > > >       >       the Linux
> >> > > >       >       >       > kernel!\n");' , compiled and installed the
> >> > > >       changes ,
> >> > > >       >       rebooted my VM
> >> > > >       >       >       > and ran 'dmesg | less' test the changes, but
> >> > > >       can not
> >> > > >       >       find the
> >> > > >       >       >       > changes. please what should I do?
> >> > > >       >       >
> >> > > >       >       >       What driver did you change?  Did you compile the
> >> > > >       >       affected file?  Do you
> >> > > >       >       >       have the corresponding device?
> >> > > >       >       >
> >> > > >       >       >       julia
> >> > > >       >       >
> >> > > >       >       >       >
> >> > > >       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > >
> >> > > >       >       >       > >
> >> > > >       >       >       > >
> >> > > >       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >       >       > >
> >> > > >       >       >       > > > The .config file was a copy from my
> >> > > >       running kernel
> >> > > >       >       using this commmand cp /boot/config- name -r * .config.
> >> > > >       Then I
> >> > > >       >       generated a new default configuration using ‘make
> >> > > >       defconfig’. I
> >> > > >       >       had followed this from another resource before you
> >> > > >       >       >       suggested using
> >> > > >       >       >       > > > ‘make localmodconfig’
> >> > > >       >       >       > >
> >> > > >       >       >       > > OK, make defconfig will indeed result in a
> >> > > >       much
> >> > > >       >       smaller configuration.  I
> >> > > >       >       >       > > don't know if it will boot on your machine.
> >> > > >       But if
> >> > > >       >       it does, then that's
> >> > > >       >       >       > > fine.
> >> > > >       >       >       > >
> >> > > >       >       >       > > julia
> >> > > >       >       >       > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
> >> > > >       Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
> >> > > >       wrote:
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       > I started by setting .config to
> >> > > >       default
> >> > > >       >       and started over it again
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       What do you mean by "setting .config
> >> > > >       to
> >> > > >       >       default"?  And what was the
> >> > > >       >       >       > > >       .config file before?
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       julia
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
> >> > > >       Julia
> >> > > >       >       Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
> >> > > >       Ibizugbe
> >> > > >       >       wrote:
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       > Thanks for the help, I set
> >> > > >       the
> >> > > >       >       .config to default and commented out the former
> >> > > >       instructions
> >> > > >       >       like before and ran make. It compiled successful.
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       I'm not sure to understand.
> >> > > >       You
> >> > > >       >       mean that after 10 hours it finally
> >> > > >       >       >       > > >       >       completed?  Or that you
> >> > > >       started over
> >> > > >       >       and it became faster?
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       julia
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
> >> > > >       AM,
> >> > > >       >       Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       On Thu, 5 Oct 2023,
> >> > > >       Isoken
> >> > > >       >       Ibizugbe wrote:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       > I just checked and
> >> > > >       the
> >> > > >       >       virtual machine has 4 CPUs but is set to 2, should I end
> >> > > >       the
> >> > > >       >       building process and use make localmodconfig?
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       I think you can run
> >> > > >       make
> >> > > >       >       localmodconfig from another directory, to have
> >> > > >       >       >       > > >       >       >       the generated files
> >> > > >       be put
> >> > > >       >       in that other directory.  You could do:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       make
> >> > > >       O=/path/to/mydir
> >> > > >       >       localmodconfig
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
> >> > > >       d
> >> > > >       >       er-in-linux-kernel-compilation
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       I have not tried
> >> > > >       this
> >> > > >       >       though.  Copy your .config file to some other file
> >> > > >       >       >       > > >       >       >       first for easy
> >> > > >       reference.
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       In this way, maybe
> >> > > >       you can
> >> > > >       >       keep your current compilation running and see
> >> > > >       >       >       > > >       >       >       if make
> >> > > >       localmodconfig would
> >> > > >       >       be beneficial.
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       julia
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       > On Thu, 5 Oct 2023
> >> > > >       at 9:24
> >> > > >       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       On Thu, 5
> >> > > >       Oct 2023,
> >> > > >       >       Isoken Ibizugbe wrote:
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       > Thank you
> >> > > >       for the
> >> > > >       >       clarification.
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       I think your
> >> > > >       >       configuration is too big.  You can try make
> >> > > >       localmodconfig
> >> > > >       >       >       > > >       >       >       >       and see if
> >> > > >       you get a
> >> > > >       >       smaller configuration.
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       Does your VM
> >> > > >       >       actually have 4 cores?
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       julia
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >       > On Thu,
> >> > > >       Oct 5,
> >> > > >       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
> >> > > >       wrote:
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > On Thu,
> >> > > >       5 Oct,
> >> > > >       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
> >> > > >       wrote:
> >> > > >       >       >       > > >       >       >       >       > > Yes I
> >> > > >       copied the
> >> > > >       >       .config file of the currently running kernel and I'm
> >> > > >       >       >       > > >       >       >       >       > > using
> >> > > >       Ubuntu
> >> > > >       >       20.04LTS on a virtual box, I renamed the
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       CONFIG_LOCALVERSION in the .config and commented out
> >> > > >       these lines
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       CONFIG_SYSTEM_TRUSTED_KEY
> >> > > >       >       >       > > >       >       >       >       > > and
> >> > > >       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
> >> > > >       has
> >> > > >       >       been
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       compiling for 10
> >> > > >       >       hours now. please is this normal?
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Hello
> >> > > >       Isoken,
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Yes, it
> >> > > >       is
> >> > > >       >       normal. The compilation time depends upon how much RAM
> >> > > >       you have
> >> > > >       >       allocated to your virtual machine. I still use virtual
> >> > > >       machines
> >> > > >       >       and sometimes the kernel building takes two days  :)
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Regards
> >> > > >       >       >       > > >       >       >       >       > > Sumitra
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       >
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >
> >> > > >       >
> >> > > >       >
> >> > > >
> >> > > >
> >> > > >
> >> >
> >> >
>

Re: [Error]

[Julia Lawall]

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



On Wed, 11 Oct 2023, Isoken Ibizugbe wrote:

> On Mon, Oct 9, 2023 at 7:57 AM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
> >
> > Thanks, I'll check it out.
> I cannot enable the driver that I changed. I fixed coding errors for a
> file in drivers/staging, but the staging drivers option in the
> menuconfig has this symbol '---staging divers', so I cannot open it to
> make the driver a module. Please what do I do?

If you changed a staging driver, it seems thta you will not want to boot
that code, because you don't have the relevant device.

So you can do make allyesconfig and then it will have as much selected as
possible.  The you should be able to make the driver you changed.  See the
tutorial for how to compile and single file and how to a compile a
complete driver.

julia

> >
> > On Mon, 9 Oct 2023 at 7:52 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >>
> >>
> >>
> >> On Mon, 9 Oct 2023, Isoken Ibizugbe wrote:
> >>
> >> > I am sorry for the confusion. After building and installing the kernel
> >> > successfully I didn't edit the grub file, so I didn't see my new
> >> > kernel after boot, so I went to do that and reboot, but my VM couldn't
> >> > load any kernel at all, I don't know if its because I was using
> >> > Vagrant, so I downloaded and installed Ubuntu on the VM to start
> >> > afresh, but I have been able to finish the first instruction on
> >> > compiling and installing, but my compiled kernel doesn't work, can I
> >> > work on it from just the directory?
> >>
> >> I think you should check with the mentor(s) for the project(s) that you
> >> are interested in.  In some sense it is time to move on, since the
> >> contribution period is not very long.  But if you need to be able to
> >> obtain a running kernel for your project, then you need to be able to do
> >> that.
> >>
> >> Maybe you can use kexec: https://wiki.archlinux.org/title/kexec
> >> The following arguments: /boot/vmlinuz-linux --initrd=/boot/initramfs-linux.img
> >> both correspond to the kernel you want to boot.
> >>
> >> julia
> >>
> >> >
> >> > On Sun, Oct 8, 2023 at 7:07 AM Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > >
> >> > >
> >> > >
> >> > > On Sun, 8 Oct 2023, Isoken Ibizugbe wrote:
> >> > >
> >> > > > I skipped that part, so I went back to edit the grub file.
> >> > >
> >> > > Not sure what you mean here.
> >> > >
> >> > > I mean, that I thought you had a working solution for the first step, so I
> >> > > wonder why you seem to have discarded that and taken another solution?
> >> > >
> >> > > julia
> >> > >
> >> > > >
> >> > > > On Sun, 8 Oct 2023 at 7:02 AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >
> >> > > >
> >> > > >       On Sat, 7 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >
> >> > > >       > I cannot boot into my Virtual machine using vagrant after
> >> > > >       reloading it to
> >> > > >       > switch to the new kernel. It gives a warning that there was an
> >> > > >       error. Do I
> >> > > >       > really need to boot into the new kernel to work? . I cannot
> >> > > >       seem to fix the
> >> > > >       > issue, do I need to reinstall the virtual machine and start
> >> > > >       all over?
> >> > > >
> >> > > >       Didn't you already get to the point of booting a virtual
> >> > > >       machine, and the
> >> > > >       problem was just that you didn't see the effect of the code that
> >> > > >       you
> >> > > >       changed?
> >> > > >
> >> > > >       julia
> >> > > >
> >> > > >
> >> > > >       > On Thu, 5 Oct 2023 at 6:09 PM, Julia Lawall
> >> > > >       <julia.lawall@inria.fr> wrote:
> >> > > >       >
> >> > > >       >
> >> > > >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >
> >> > > >       >       > I modified the e1000 driver and compiled with -j2
> >> > > >       according to
> >> > > >       >       the tutorial.
> >> > > >       >
> >> > > >       >       Whether a file gets compiled depends on your
> >> > > >       configuration.  Do
> >> > > >       >       you have a
> >> > > >       >       .o file or .ko file for the .c file that you changed?
> >> > > >       >
> >> > > >       >       Please remember to keep the list in CC.  Other people
> >> > > >       may have
> >> > > >       >       better
> >> > > >       >       answers than I do :)
> >> > > >       >
> >> > > >       >       julia
> >> > > >       >
> >> > > >       >       >
> >> > > >       >       > On Thu, 5 Oct 2023 at 5:58 PM, Julia Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >       >       On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >       >
> >> > > >       >       >       > Thanks for the help. I made changes to the
> >> > > >       probe
> >> > > >       >       function by adding
> >> > > >       >       >       > the printk line to it 'printk(KERN_DEBUG "I
> >> > > >       can modify
> >> > > >       >       the Linux
> >> > > >       >       >       > kernel!\n");' , compiled and installed the
> >> > > >       changes ,
> >> > > >       >       rebooted my VM
> >> > > >       >       >       > and ran 'dmesg | less' test the changes, but
> >> > > >       can not
> >> > > >       >       find the
> >> > > >       >       >       > changes. please what should I do?
> >> > > >       >       >
> >> > > >       >       >       What driver did you change?  Did you compile the
> >> > > >       >       affected file?  Do you
> >> > > >       >       >       have the corresponding device?
> >> > > >       >       >
> >> > > >       >       >       julia
> >> > > >       >       >
> >> > > >       >       >       >
> >> > > >       >       >       > On Thu, Oct 5, 2023 at 12:10 PM Julia Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > >
> >> > > >       >       >       > >
> >> > > >       >       >       > >
> >> > > >       >       >       > > On Thu, 5 Oct 2023, Isoken Ibizugbe wrote:
> >> > > >       >       >       > >
> >> > > >       >       >       > > > The .config file was a copy from my
> >> > > >       running kernel
> >> > > >       >       using this commmand cp /boot/config- name -r * .config.
> >> > > >       Then I
> >> > > >       >       generated a new default configuration using ‘make
> >> > > >       defconfig’. I
> >> > > >       >       had followed this from another resource before you
> >> > > >       >       >       suggested using
> >> > > >       >       >       > > > ‘make localmodconfig’
> >> > > >       >       >       > >
> >> > > >       >       >       > > OK, make defconfig will indeed result in a
> >> > > >       much
> >> > > >       >       smaller configuration.  I
> >> > > >       >       >       > > don't know if it will boot on your machine.
> >> > > >       But if
> >> > > >       >       it does, then that's
> >> > > >       >       >       > > fine.
> >> > > >       >       >       > >
> >> > > >       >       >       > > julia
> >> > > >       >       >       > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > > On Thu, 5 Oct 2023 at 11:03 AM, Julia
> >> > > >       Lawall
> >> > > >       >       <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       On Thu, 5 Oct 2023, Isoken Ibizugbe
> >> > > >       wrote:
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       > I started by setting .config to
> >> > > >       default
> >> > > >       >       and started over it again
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       What do you mean by "setting .config
> >> > > >       to
> >> > > >       >       default"?  And what was the
> >> > > >       >       >       > > >       .config file before?
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       julia
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       > On Thu, 5 Oct 2023 at 10:44 AM,
> >> > > >       Julia
> >> > > >       >       Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       On Thu, 5 Oct 2023, Isoken
> >> > > >       Ibizugbe
> >> > > >       >       wrote:
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       > Thanks for the help, I set
> >> > > >       the
> >> > > >       >       .config to default and commented out the former
> >> > > >       instructions
> >> > > >       >       like before and ran make. It compiled successful.
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       I'm not sure to understand.
> >> > > >       You
> >> > > >       >       mean that after 10 hours it finally
> >> > > >       >       >       > > >       >       completed?  Or that you
> >> > > >       started over
> >> > > >       >       and it became faster?
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       julia
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       > On Thu, 5 Oct 2023 at 9:56
> >> > > >       AM,
> >> > > >       >       Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       On Thu, 5 Oct 2023,
> >> > > >       Isoken
> >> > > >       >       Ibizugbe wrote:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       > I just checked and
> >> > > >       the
> >> > > >       >       virtual machine has 4 CPUs but is set to 2, should I end
> >> > > >       the
> >> > > >       >       building process and use make localmodconfig?
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       I think you can run
> >> > > >       make
> >> > > >       >       localmodconfig from another directory, to have
> >> > > >       >       >       > > >       >       >       the generated files
> >> > > >       be put
> >> > > >       >       in that other directory.  You could do:
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       make
> >> > > >       O=/path/to/mydir
> >> > > >       >       localmodconfig
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >     https://stackoverflow.com/questions/15969694/make-o-files-in-separate-fol
> >> > > >       d
> >> > > >       >       er-in-linux-kernel-compilation
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       I have not tried
> >> > > >       this
> >> > > >       >       though.  Copy your .config file to some other file
> >> > > >       >       >       > > >       >       >       first for easy
> >> > > >       reference.
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       In this way, maybe
> >> > > >       you can
> >> > > >       >       keep your current compilation running and see
> >> > > >       >       >       > > >       >       >       if make
> >> > > >       localmodconfig would
> >> > > >       >       be beneficial.
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       julia
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       > On Thu, 5 Oct 2023
> >> > > >       at 9:24
> >> > > >       >       AM, Julia Lawall <julia.lawall@inria.fr> wrote:
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       On Thu, 5
> >> > > >       Oct 2023,
> >> > > >       >       Isoken Ibizugbe wrote:
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       > Thank you
> >> > > >       for the
> >> > > >       >       clarification.
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       I think your
> >> > > >       >       configuration is too big.  You can try make
> >> > > >       localmodconfig
> >> > > >       >       >       > > >       >       >       >       and see if
> >> > > >       you get a
> >> > > >       >       smaller configuration.
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       Does your VM
> >> > > >       >       actually have 4 cores?
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       julia
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >       > On Thu,
> >> > > >       Oct 5,
> >> > > >       >       2023 at 8:01 AM sumitra sharma <sumitraartsy@gmail.com>
> >> > > >       wrote:
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > On Thu,
> >> > > >       5 Oct,
> >> > > >       >       2023, 12:24 pm Isoken Ibizugbe, <isokenjune@gmail.com>
> >> > > >       wrote:
> >> > > >       >       >       > > >       >       >       >       > > Yes I
> >> > > >       copied the
> >> > > >       >       .config file of the currently running kernel and I'm
> >> > > >       >       >       > > >       >       >       >       > > using
> >> > > >       Ubuntu
> >> > > >       >       20.04LTS on a virtual box, I renamed the
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       CONFIG_LOCALVERSION in the .config and commented out
> >> > > >       these lines
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       CONFIG_SYSTEM_TRUSTED_KEY
> >> > > >       >       >       > > >       >       >       >       > > and
> >> > > >       >       CONFIG_MODULE_SIG_KEY, then ran make -j4, but the kernel
> >> > > >       has
> >> > > >       >       been
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       compiling for 10
> >> > > >       >       hours now. please is this normal?
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Hello
> >> > > >       Isoken,
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Yes, it
> >> > > >       is
> >> > > >       >       normal. The compilation time depends upon how much RAM
> >> > > >       you have
> >> > > >       >       allocated to your virtual machine. I still use virtual
> >> > > >       machines
> >> > > >       >       and sometimes the kernel building takes two days  :)
> >> > > >       >       >       > > >       >       >       >       > >
> >> > > >       >       >       > > >       >       >       >       > > Regards
> >> > > >       >       >       > > >       >       >       >       > > Sumitra
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >       >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       > > >
> >> > > >       >       >       >
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >       >
> >> > > >       >
> >> > > >       >
> >> > > >       >
> >> > > >
> >> > > >
> >> > > >
> >> >
> >> >
>