I've posted a mail with the screenshot (waiting for moderation) when I try to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values. I tried using make localmodconfig but It again asks for many config params that I don't know anything about. Saludos, * Abel.* On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot. Instead it displays the error that I've described before (sorry I forgot to attach the screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
* Abel.*
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing
.config file
and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links to the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling I get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
On 29 January 2017 at 16:19, Abel <akronix5@gmail.com> wrote:
I've posted a mail with the screenshot (waiting for moderation) when I try to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values.
I tried using make localmodconfig but It again asks for many config params that I don't know anything about.
Saludos,
Abel.
Hi Abel, The procedure I followed in order to compile, install and boot my custom compiled kernel is: 1. Copy .config from existing distribution to kernel tree. 2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!) 3. Run make -j<N> where N is a good number for your system. 4. Run make modules_install 5. Run make install (This ran update-grub for me at the end, though, which was convenient) That's it. I was able to boot into this newly compiled kernel via grub's selection menu upon rebooting. I think you may have missed doing Step 4 above. Guru Das Srinagesh.
On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot. Instead it displays the error that I've described before (sorry I forgot to attach the screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
Abel.
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing .config file and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links to the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling I get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
Yes, similar procedure I've followed. I didn't forget step 4. I actually always did `sudo make install_modules`. I'm not sure what's going on. Maybe it has sth to do with Ubuntu, that's why specifically mention I was using Ubuntu. Maybe I can try with some other distro. Probably Manjaro has better support for latest kernel releases. It's late here. I'll keep trying and let you know in case I figure out sth. On Jan 30, 2017 1:27 AM, "Guru Das S" <gurooodas@gmail.com> wrote: On 29 January 2017 at 16:19, Abel <akronix5@gmail.com> wrote:
I've posted a mail with the screenshot (waiting for moderation) when I try to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values.
I tried using make localmodconfig but It again asks for many config params that I don't know anything about.
Saludos,
Abel.
Hi Abel, The procedure I followed in order to compile, install and boot my custom compiled kernel is: 1. Copy .config from existing distribution to kernel tree. 2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!) 3. Run make -j<N> where N is a good number for your system. 4. Run make modules_install 5. Run make install (This ran update-grub for me at the end, though, which was convenient) That's it. I was able to boot into this newly compiled kernel via grub's selection menu upon rebooting. I think you may have missed doing Step 4 above. Guru Das Srinagesh.
On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot. Instead it displays the error that I've described before (sorry I forgot to attach
the
screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
Abel.
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing .config file and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it
yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links to the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling
I
get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
On Mon, Jan 30, 2017 at 6:04 AM, Abel <akronix5@gmail.com> wrote:
Yes, similar procedure I've followed. I didn't forget step 4. I actually always did `sudo make install_modules`. I'm not sure what's going on.
Maybe it has sth to do with Ubuntu, that's why specifically mention I was using Ubuntu.
Maybe I can try with some other distro. Probably Manjaro has better support for latest kernel releases.
It's late here. I'll keep trying and let you know in case I figure out sth.
Ok so probably some modules got missed while building your custom kernel. Perhaps you can zcat /boot/config-$(uname -r) and store it as .config to your custom kernel source location? Then probably try and remove what you don't need? and see if it works.
On Jan 30, 2017 1:27 AM, "Guru Das S" <gurooodas@gmail.com> wrote:
On 29 January 2017 at 16:19, Abel <akronix5@gmail.com> wrote:
I've posted a mail with the screenshot (waiting for moderation) when I try to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values.
I tried using make localmodconfig but It again asks for many config params that I don't know anything about.
Saludos,
Abel.
Hi Abel,
The procedure I followed in order to compile, install and boot my custom compiled kernel is:
1. Copy .config from existing distribution to kernel tree.
2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!)
3. Run make -j<N> where N is a good number for your system.
4. Run make modules_install
5. Run make install (This ran update-grub for me at the end, though, which was convenient)
That's it. I was able to boot into this newly compiled kernel via grub's selection menu upon rebooting. I think you may have missed doing Step 4 above.
Guru Das Srinagesh.
On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot. Instead it displays the error that I've described before (sorry I forgot to attach the screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
Abel.
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing .config file and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links to the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling I get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- ---P.K.S
After cloning greg kroah hartman's repository from the tutorial , I am not able to boot into any kernel by default and have to choose from advanced ubuntu options from the grub menu . In the advanced ubuntu options I see generic kernels ,and one rc3+ kernel . I think that's the one I need to boot in . Am I wrong ? Also when I am trying to boot in the rc3+ kernel my computer gets stuck and I am unable to boot . What do I do ? Please help me . On Mon, Jan 30, 2017 at 9:34 AM, Pranay Srivastava <pranjas@gmail.com> wrote:
On Mon, Jan 30, 2017 at 6:04 AM, Abel <akronix5@gmail.com> wrote:
Yes, similar procedure I've followed. I didn't forget step 4. I actually always did `sudo make install_modules`. I'm not sure what's going on.
Maybe it has sth to do with Ubuntu, that's why specifically mention I was using Ubuntu.
Maybe I can try with some other distro. Probably Manjaro has better support for latest kernel releases.
It's late here. I'll keep trying and let you know in case I figure out sth.
Ok so probably some modules got missed while building your custom kernel. Perhaps you can zcat /boot/config-$(uname -r) and store it as .config to your custom kernel source location?
Then probably try and remove what you don't need? and see if it works.
On Jan 30, 2017 1:27 AM, "Guru Das S" <gurooodas@gmail.com> wrote:
On 29 January 2017 at 16:19, Abel <akronix5@gmail.com> wrote:
I've posted a mail with the screenshot (waiting for moderation) when I try to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values.
I tried using make localmodconfig but It again asks for many config params that I don't know anything about.
Saludos,
Abel.
Hi Abel,
The procedure I followed in order to compile, install and boot my custom compiled kernel is:
1. Copy .config from existing distribution to kernel tree.
2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!)
3. Run make -j<N> where N is a good number for your system.
4. Run make modules_install
5. Run make install (This ran update-grub for me at the end, though, which was convenient)
That's it. I was able to boot into this newly compiled kernel via grub's selection menu upon rebooting. I think you may have missed doing Step 4 above.
Guru Das Srinagesh.
On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot. Instead it displays the error that I've described before (sorry I forgot to attach the screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
Abel.
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing .config file and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links to the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling I get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- ---P.K.S
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
I'd start saying that you should open a new thread for this issue, but, doesn't matter... What's that greg kroah repo you're talking about? rc3+ looks like it's the kernel version you've already built, which is likely the default configured kernel that doesn't work for you. Try to boot the most recent generic kernel, they come with your linux distro and they should work. To change the default kernel that boots, search for help/tutorials about grub configuration in Internet. Saludos, * Abel.* On 30 January 2017 at 22:51, srishti sharma <srishtishar@gmail.com> wrote:
After cloning greg kroah hartman's repository from the tutorial , I am not able to boot into any kernel by default and have to choose from advanced ubuntu options from the grub menu . In the advanced ubuntu options I see generic kernels ,and one rc3+ kernel . I think that's the one I need to boot in . Am I wrong ? Also when I am trying to boot in the rc3+ kernel my computer gets stuck and I am unable to boot . What do I do ? Please help me .
On Mon, Jan 30, 2017 at 9:34 AM, Pranay Srivastava <pranjas@gmail.com> wrote:
On Mon, Jan 30, 2017 at 6:04 AM, Abel <akronix5@gmail.com> wrote:
Yes, similar procedure I've followed. I didn't forget step 4. I actually always did `sudo make
install_modules`. I'm not sure what's going on.
Maybe it has sth to do with Ubuntu, that's why specifically mention I
was using Ubuntu.
Maybe I can try with some other distro. Probably Manjaro has better
support for latest kernel releases.
It's late here. I'll keep trying and let you know in case I figure out
sth.
Ok so probably some modules got missed while building your custom kernel. Perhaps you can zcat /boot/config-$(uname -r) and store it as .config to your custom kernel source location?
Then probably try and remove what you don't need? and see if it works.
On Jan 30, 2017 1:27 AM, "Guru Das S" <gurooodas@gmail.com> wrote:
On 29 January 2017 at 16:19, Abel <akronix5@gmail.com> wrote:
I've posted a mail with the screenshot (waiting for moderation) when
I try
to boot from make defconfig built kernel. Basically the kernel doesn't boot because "Missing modules (cat /proc/modules; ls /dev " it says...It's the same screen that appeared when I tried using make oldconfig pressing enter for default values.
I tried using make localmodconfig but It again asks for many config params that I don't know anything about.
Saludos,
Abel.
Hi Abel,
The procedure I followed in order to compile, install and boot my custom compiled kernel is:
1. Copy .config from existing distribution to kernel tree.
2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!)
3. Run make -j<N> where N is a good number for your system.
4. Run make modules_install
5. Run make install (This ran update-grub for me at the end, though, which was convenient)
That's it. I was able to boot into this newly compiled kernel via grub's selection menu upon rebooting. I think you may have missed doing Step 4 above.
Guru Das Srinagesh.
On 30 January 2017 at 01:11, Abel <akronix5@gmail.com> wrote:
Hi.
I just built using make defconfig and it, again, doesn't boot.
Instead it
displays the error that I've described before (sorry I forgot to attach the screenshot, I attach it here).
As I already stated, neither /boot/${uname -r} nor make oldconfig work for me, they both show the screen above.
Saludos,
Abel.
On 30 January 2017 at 01:08, Guru Das S <gurooodas@gmail.com> wrote:
On 29 January 2017 at 15:32, 慕冬亮 <mudongliangabcd@gmail.com> wrote:
Hello, If you want to reuse the config of current kernel, you can use `make oldconfig` to generate config file.
-- My best regards to you.
No System Is Safe! Dongliang Mu
2017-01-29 18:24 GMT-05:00 Ozgur Karatas <mueddib@goosey.org>:
Hello,
you can get .config files in two ways, firstly get the existing .config file and compile to kernel.
$ cp /boot/config-x.x.x /bla/linux/.config
Second, use the generate command:
$ make defconfig
Regards,
~Ozgur
30.01.2017, 01:18, "Abel" <akronix5@gmail.com>:
Hi!
Where do you get the config file from? or do you generate it
yourself?
I'm using xUbuntu 16.04 in a VM inside VMWare, following the instructions described in kernelnewbies wiki. (By the way, the download links
to
the iso images of Ubuntu don't work for me)
If I copy the latest config file in /boot, kernel 4.4.0, it starts to ask me many config parameters that I don't know what to answer. I tried to press always <enter> to set up the default parameters, but after compiling I get an error trying to boot from that kernel (see atachment).
I tried with make menuconfig and that seems to work, but it takes too long because it builds and includes many many drivers modules. Yeah, I know I could navigate through the ncurses window and select the stuff I want and deselect what I don't want, but I'd rather prefer just a simple config file that builds and works and don't waste time in understanding all the stuff that it's in there.
So, isn't there a way to get a simple config file just to develop kernel stuff for an Ubuntu image? I've even gone to the kernel ppa sources for Ubuntu: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/; but it only provides a patch using the debian config files (which don't come from git sources of course).
I just want a config file, copy it to the kernel root code and compile.
Greetings,
Abel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Abel,
To add to what Ozgur said, you may first copy the existing .config file that comes along with your Linux distribution to your kernel tree, and then use:
$ make localmodconfig
instead of defconfig. A quick Google search should tell you the differences between the two - and from what I've read, localmodconfig is preferred to defconfig.
Hope this helps.
Guru Das Srinagesh.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- ---P.K.S
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Mon, Jan 30, 2017 at 2:51 PM, srishti sharma <srishtishar@gmail.com> wrote:
After cloning greg kroah hartman's repository from the tutorial , I am not able to boot into any kernel by default and have to choose from advanced ubuntu options from the grub menu . In the advanced ubuntu options I see generic kernels ,and one rc3+ kernel . I think that's the one I need to boot in . Am I wrong ? Also when I am trying to boot in the rc3+ kernel my computer gets stuck and I am unable to boot . What do I do ? Please help me .
A couple of minor things -- well, maybe not so minor: Top posting, and thread hijacking, won't go over well on most kernel mailing lists. If you're really stuck I'd try to go back to basics and make sure a standard kernel build-n-boot works before trying anything fancier. On an Ubuntu system that could be sudo apt-get install build-essential sudo apt-get install libssl-dev sudo apt-get install git git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-rc cd linux-rc cp `ls -t /boot/config* | head -1` .config # or whatever your latest vendor config file is yes "" | make oldconfig make bindeb-pkg >/tmp/make-bindeb.out 2>/tmp/make-bindeb.err which, if all goes well, will leave a deb file in the parent directory with an unwieldy name like linux-image-4.10.0-rc6+_4.10.0-rc6+-1_i386.deb. If you can't build a kernel with the standard linux source repo and your vendor's latest config file then something needs to be fixed before going any further. If the build worked, running sudo dpkg -i linux-image-whatever-the-name-is.deb in the parent directory, and rebooting, should start the new kernel running, as you can check with uname -r. Actually I ran those commands on a Debian Jessie VM but I think the Ubuntu steps would be virtually identical. It is handy to do all that in a virtual environment -- the cool kids use kvm; I use Virtualbox. -- Jim
On Sun, 29 Jan 2017 16:27:04 -0800, Guru Das S said:
2. Run make localmodconfig (I also got a bunch of prompts for parameters I had no idea about. I just pressed down Enter till the stream of options stopped flowing!)
Remember to insert all your USB/whatever widgets before running this, so their drivers are loaded - localmodconfig uses the output of lsmod, so if the module(s) for the driver aren't loaded, the resulting kernel won't support that widget. (You don't need to have them all plugged in at once, you can unplug each one once they've been noticed by the system. Just make sure each one gets plugged in at least once after boot and before localmodconfig)
participants (6)
-
Abel -
Guru Das S -
Jim Davis -
Pranay Srivastava -
srishti sharma -
valdis.kletnieks＠vt.edu