LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-31-2004, 03:52 AM   #1
beejayzed
Member
 
Registered: Jan 2004
Location: Auckland, New Zealand
Distribution: Ubuntu
Posts: 686

Rep: Reputation: 30
About using make install with the kernel


I read somewhere that if I use Lilo as the boot manager I can just type make install after i've compiled and installed the modules and compiled the kernel image. If I do this will it overwrite my current kernel? What order do I need to do the commands in?

Thanks and bye
 
Old 01-31-2004, 04:46 AM   #2
dalek
Senior Member
 
Registered: Jul 2003
Location: Mississippi USA
Distribution: Gentoo
Posts: 2,058
Blog Entries: 2

Rep: Reputation: 79
The commands depend on the version of the kernel. Make install will overwrite your old kernel from what I have read. I like to keep my old one, in case the new makes my rig smoke or something, to go back to. I have had it come in handy a few times.

I copy using this command, make sure /boot is mounted:

cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage-<kernelversion>-test<version>

That will let you name the kernel something different.

If you plan to mess with that kernel a lot, may I suggest you switch to grub. If the kernel fails, which happens even to a guru, you can then edit the line and boot the old kernel in about oh 20 seconds or so. Much better than after to get to a point where you can run lilo and all.

What version of kernel are you using? I'll list the commands. They are also listed in the READ.ME in the kernel directory, ya know, /usr/src/linux<whatever version>. Makes for good reading anyway.

Later

 
Old 01-31-2004, 04:52 AM   #3
codedv
Member
 
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146

Rep: Reputation: 15
I don't know......

I've never used it. When I've compiled my kernel I install it using the following commands.

I have Lilo set up so that it points to an old image of the kernel called bzImage.old so if the kernel fails to load for any reason I can go back:
Code:
/boot # cp bzImage bzImage.old
/boot # cp /usr/src/linux/arch/i386/boot/bzImage bzImage
/boot # lilo
Make sure you run lilo before rebooting otherwise your system won't boot at all and you'll have to use your rescue floppy disk.
 
Old 01-31-2004, 04:55 AM   #4
beejayzed
Member
 
Registered: Jan 2004
Location: Auckland, New Zealand
Distribution: Ubuntu
Posts: 686

Original Poster
Rep: Reputation: 30
Thanks for the help. I am currently using 2.4.something and want to compile to 2.6.1.
I will read the readme file and see what is says.
 
Old 01-31-2004, 04:59 AM   #5
dalek
Senior Member
 
Registered: Jul 2003
Location: Mississippi USA
Distribution: Gentoo
Posts: 2,058
Blog Entries: 2

Rep: Reputation: 79
For 2.6 kernels, this is the commands:

make all
make modules_install

Then copy the kernel over. The new kernel has a lot less commands.

I would suggest since you are doing this the first time for this kernel that you type in

make clean

before doing anything including make menuconfig. That will clear out any old clutter left over from the testing and such. I read that somewhere on Gentoo forums. We compile a lot in Gentoo.

Hope that helps.

Later

 
Old 01-31-2004, 05:06 AM   #6
beejayzed
Member
 
Registered: Jan 2004
Location: Auckland, New Zealand
Distribution: Ubuntu
Posts: 686

Original Poster
Rep: Reputation: 30
Thanks for the help guys.
 
Old 01-31-2004, 05:57 AM   #7
dalek
Senior Member
 
Registered: Jul 2003
Location: Mississippi USA
Distribution: Gentoo
Posts: 2,058
Blog Entries: 2

Rep: Reputation: 79
Your welcome. Glad to help.

 
Old 01-31-2004, 09:15 AM   #8
maestro52
Member
 
Registered: Aug 2003
Location: Texas
Distribution: Fedora 9
Posts: 177

Rep: Reputation: 30
Question Guru, are you still there??

I wrote you your e-mail, but haven't been able to go to sleep yet and have just kept trying to compile this damn thing. 2.4.22-21mm.1mdk just will not compile!!

I am forver getting the same error when I "make modules" and cannot figure the problem at all. I have an ASROCK K7VM2 Athlon XP1800 with an entire VIA Chipset and the USB driver is VIA UHCI and whether I choose the first UHCI or the second UHCI or BOTH of them as modules it always gives me this error (I am shortening it so it isn't overwhelming);

________________________________________________________________________________
usr/src/linux-2.4.22-21mm.1mdk/include/linux/modversions.h -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=usb -c usb.c -o usb.o
In file included from usb.c:195:
unusual_devs.h:251: error: `US_PR_ZIOCF' undeclared here (not in a function)
unusual_devs.h:251: error: initializer element is not constant
unusual_devs.h:251: error: (near initialization for `us_unusual_dev_list[26].useTransport')
unusual_devs.h:251: error: `init_ziocf' undeclared here (not in a function)
unusual_devs.h:251: error: initializer element is not constant
unusual_devs.h:251: error: (near initialization for `us_unusual_dev_list[26].initFunction')
unusual_devs.h:251: error: initializer element is not constant
unusual_devs.h:251: error: (near initialization for `us_unusual_dev_list[26]')
unusual_devs.h:258: error: initializer element is not constant
unusual_devs.h:258: error: (near initialization for `us_unusual_dev_list[27]')
unusual_devs.h:268: error: initializer element is not constant
unusual_devs.h:268: error: (near initialization for `us_unusual_dev_list[28]')
unusual_devs.h:275: error: initializer element is not constant
unusual_devs.h:275: error: (near initialization for `us_unusual_dev_list[29]')
unusual_devs.h:282: error: initializer element is not constant
unusual_devs.h:282: error: (near initialization for `us_unusual_dev_list[30]')
unusual_devs.h:289: error: initializer element is not constant
unusual_devs.h:289: error: (near initialization for `us_unusual_dev_list[31]')
unusual_devs.h:296: error: initializer element is not constant
unusual_devs.h:296: error: (near initialization for `us_unusual_dev_list[32]')
unusual_devs.h:303: error: initializer element is not constant
unusual_devs.h:303: error: (near initialization for `us_unusual_dev_list[33]')
unusual_devs.h:310: error: initializer element is not constant
unusual_devs.h:310: error: (near initialization for `us_unusual_dev_list[34]')
unusual_devs.h:316: error: initializer element is not constant
unusual_devs.h:316: error: (near initialization for `us_unusual_dev_list[35]')
unusual_devs.h:322: error: initializer element is not constant

and it just repeats forever until it gets to;

usb.c:231: error: initializer element is not constant
usb.c:231: error: (near initialization for `us_unusual_dev_list[99]')
usb.c:233: error: initializer element is not constant
usb.c:233: error: (near initialization for `us_unusual_dev_list[100]')
usb.c:235: error: initializer element is not constant
usb.c:235: error: (near initialization for `us_unusual_dev_list[101]')
usb.c:237: error: initializer element is not constant
usb.c:237: error: (near initialization for `us_unusual_dev_list[102]')
usb.c:240: error: initializer element is not constant
usb.c:240: error: (near initialization for `us_unusual_dev_list[103]')
make[3]: *** [usb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.22-21mm.1mdk/drivers/usb/storage'
make[2]: *** [_modsubdir_storage] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.22-21mm.1mdk/drivers/usb'
make[1]: *** [_modsubdir_usb] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.22-21mm.1mdk/drivers'
make: *** [_mod_drivers] Error 2
______________________________________________________________________________

I am not choosing any other drivers everythig else is either moduled or not chosen at all. I really do not understand the problem. I considered just not choosing any USB at all but my internet ADSL is USB connected. I am kind of stuck here.

Would it perhaps be much simpler to just go directly to the 2.6 kernel and compile it. Since this kernel has not been compiled successfully yet and has not been placed into the boot my .config is still the install kernel of 2.4.22-10 although it is not a source kernel so I am not sure how to switch unless I can just delete the uncopiled source and go to that new source. Do you have any suggestions as to what is my best route. Of course, if I must stay with thi sone I need ot know what is wrong.

I hope you can help.

Thanks!


Last edited by maestro52; 01-31-2004 at 09:18 AM.
 
Old 01-31-2004, 09:56 AM   #9
codedv
Member
 
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146

Rep: Reputation: 15
Try re-downloading the kernel sources and patching it up to 2.4.24.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Howto: Make a bootable install CD with kernel 2.6 lemmy_kilmister Slackware 5 04-01-2006 03:45 AM
make install errors during kernel compile tharris Slackware 1 02-16-2004 11:11 AM
Slack 9.1 kernel 2.6.1 make install fails LoungeLizard Slackware 2 01-31-2004 06:39 PM
error during make install with kernel 2.4.23 Bruce Hill Slackware 9 12-26-2003 08:47 PM
make install errors on kernel harrycrumb11 Linux - General 5 10-06-2003 09:31 PM


All times are GMT -5. The time now is 01:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration