LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-23-2004, 02:09 AM   #1
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Rep: Reputation: 15
make: **** No rule to make target 'bzImage


Hello,
I am trying to compile a new kernel (2.6.5) for the first time using Slackware. I have followed to the letter the suggestions mapped out in the two hot threads in this forum (this is how I do it & Kernel compiling...newbie). Using both methods I get snagged at the same point: make bzlmage....no rule to make target 'bzlmage'.

Make gives the same relative error. Make configure runs but nothing seems to get updated including lilo.
Does anyone have a clue as to why this is happening? Thanks in advance for any help.

tsw
 
Old 06-23-2004, 06:05 AM   #2
drowstar
Member
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware, Gentoo, Fedora
Posts: 205

Rep: Reputation: 30
Hi tsw,
starting with 2.5 (the development version of kernel 2.6) there has not been a target bzImage in the Makefile anymore.
All you have to do now, is type "make" (and possibly "make modules_install" if you so desire). This will compile the kernel and place the kernel in arch/<yourarch>/boot/bzImage. Copy that to your /boot directory and set up the boot manager.

Hope this helps,
- drowstar
 
Old 06-23-2004, 01:00 PM   #3
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
No, you can indeed use bzImage as a target, but it appears that you didn't really configure the kernel -- which is the most important part.

You need to

make menuconfig before doing
make bzImage

--Shade
 
Old 06-23-2004, 01:28 PM   #4
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Thanks for the responses,

I used gconfig to configure the kernel, sorry should have mentioned that in first post. I now have a bit of another problem. I receive a kernel panic when booting into the old linux, which is the only linux label on lilo. Am not sure why this happened. Perhaps a partially configured kernel?

This is my first go around with Slackware and I am not sure where to start looking. I was able to boot "in a pinch" with the first cd and can access the the drive no problem. I suppose I am going to have to learn how to use vi.

I have nothing invested on this Slack install except time so I could reinstall. However, if someone could point me in the right direction as far as this kernel panic goes that would be cool. Really, this is the reason why I started with Slack, learning Linux. Thanks again for any help and suggestions.

tsw
 
Old 06-23-2004, 01:40 PM   #5
lupin_the_3rd
Member
 
Registered: Oct 2003
Location: Memphis, TN
Distribution: Slackware current
Posts: 485

Rep: Reputation: 30
edit the /usr/src/(kernel-version)/Makefile

look for the part about "#export kernel install path to /boot" (not exact wording)... if you do it graphically just do a find for /boot with gedit/kedit

you need to uncomment this...

don't forget to make install your kernel

right now it's installing to / by default.

Last edited by lupin_the_3rd; 06-23-2004 at 01:42 PM.
 
Old 06-23-2004, 02:14 PM   #6
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Thanks for the response,

OK, first question. When you say uncomment line xxx, does that mean to simply remove the "#" symbol from the front of the line? If so, I did this to the line you mentioned above and as far as I can tell lilo still points to kernel 2.4.22 or linux.old. The only change I made to lilo was to rename the 2.4xx image to old linux and after doing so ran lilo -v from the command line. I don't see how that could fubar the operation, but do you think that it did?

Because of the kernel panic I cannot initiate Slackware except through the use of the install CD. As we know I can mount hda9, where slack / lives. Of course I can also mount hda9 with my Mandrake system. Second question (or third, but who's counting), can I run commands, such as "lilo" etc, from my Mandrake drive that will effect and configure the Slcak drive? I am thinking that I cd to /home/mnt/dev/hda9 and tinker around. I just figure this would be easier for me to try to fix this from a terminal rather than from a bash screen. Thanks for the assist.

tsw

Last edited by tsw; 06-23-2004 at 02:15 PM.
 
Old 06-23-2004, 02:52 PM   #7
lupin_the_3rd
Member
 
Registered: Oct 2003
Location: Memphis, TN
Distribution: Slackware current
Posts: 485

Rep: Reputation: 30
Quote:
Originally posted by tsw
Thanks for the response,

OK, first question. When you say uncomment line xxx, does that mean to simply remove the "#" symbol from the front of the line? If so, I did this to the line you mentioned above and as far as I can tell lilo still points to kernel 2.4.22 or linux.old. The only change I made to lilo was to rename the 2.4xx image to old linux and after doing so ran lilo -v from the command line. I don't see how that could fubar the operation, but do you think that it did?

Because of the kernel panic I cannot initiate Slackware except through the use of the install CD. As we know I can mount hda9, where slack / lives. Of course I can also mount hda9 with my Mandrake system. Second question (or third, but who's counting), can I run commands, such as "lilo" etc, from my Mandrake drive that will effect and configure the Slcak drive? I am thinking that I cd to /home/mnt/dev/hda9 and tinker around. I just figure this would be easier for me to try to fix this from a terminal rather than from a bash screen. Thanks for the assist.

tsw
Yeah, you just remove the #... you can chroot your slack installation from mandrake but I've never done it personally (except for a gentoo install) but ther's plenty of documentation on the web for doing a chroot. The kernel created by "make install" will be vmlinuz, and will move the current vmlinuz to vmlinuz.old. Have you tried recompiling the kernel using the cd to get into your installation?
 
Old 06-23-2004, 03:59 PM   #8
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Yeah, I just tried to reconfig, remake, remenuconfig, etc...with the install CD. No dice, it appears that the correct gcc complier, or applet is not present. And then a whole mess of errors on the screen.
scripts/basic/fixdep.c:331........360, error: A mess. Maybe I can try with the qtparted/partimage rescue cd or Knoppix. I think the key is gettting lilo to load the 2.4.22 kernel again. No clue.

I don't know...with all that jumping around with live CDs and the like I could just as easily wimp out and reinstall....that would be the easy way out, but what would I have learned? I already know how to put CDs in the cdrom. Ya' know what I mean? Oh well, I have so few ideas about Linux I have already run out of them. Thank you again for lending a hand.

tsw
 
Old 06-23-2004, 04:00 PM   #9
drowstar
Member
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware, Gentoo, Fedora
Posts: 205

Rep: Reputation: 30
Hi tsw,
I stand corrected on the make bzImage issue. (Thanks for pointing that out lupin_the_3rd.) Judging from your previous posts, you're past that stage now.

If so, I did this to the line you mentioned above and as far as I can tell lilo still points to kernel 2.4.22 or linux.old. The only change I made to lilo was to rename the 2.4xx image to old linux and after doing so ran lilo -v from the command line.
If running lilo did not result in errors, your lilo configuration file should be fine (i.e. the kernel you are pointing at exists).
I would advise that you go over the installation procedure yourself. I personally find letting the kernel installation set the boot loader up more complicated than doing it myself (because in my experience there is always something that doesnt work).
What you need to do is move the bzImage to the location you want it (if you dont have a separate boot-partition you want to use, you can even leave it where it is. Not advisable though.) and configure your boot loader to use this file (plus adjust any parameters you may want to use). It is always a good idea to add an entry to your boot menu instead of replacing the old one before you are certain everything is working.

Can I run commands, such as "lilo" etc, from my Mandrake drive that will effect and configure the Slcak drive? I am thinking that I cd to /home/mnt/dev/hda9 and tinker around. I just figure this would be easier for me to try to fix this from a terminal rather than from a bash screen.
As lupin_the_3rd mentioned, a chroot jail would be one good way to go here. This procedure is complicated if you do it the first time though, because to get a really working system running from another, you need to have a quite thorough understanding of how a linux system works.
For this reason I would advise against this in your particular case, since all you seem to want to do is configure lilo. You can instead call lilo with the -C option to specify a different config file. (e.g.: /home/mnt/dev/hda9/usr/sbin/lilo -C /home/mnt/dev/hda9/etc/lilo.conf - this is a weird mount point you got there .)
Another thing you could try is using the Mandrake setup tools to configure your booting. This wont help you much with learning linux though. (plus it would not make use of your slackware lilo configuration)

Hope some of this helped,
- drowstar

edit:
I just finished this post when I saw your newest one
Anyways, to get your lilo configuration working again, I suggest you do the following:
1) Find the bzImage of the 2.4 kernel (it probably still is somewhere in your /boot directory. Sorry, I dont have a real idea of what the script does to the old kernels)
2) modify the lilo.conf file: add an entry which looks exactly like the one that is currently not working, but substitute the path to the 2.6 kernel in the "image=/..." line for the 2.4 one you just found (hopefully)
3) run lilo using the -C command pointing to the file you modified (as I described above)

Last edited by drowstar; 06-23-2004 at 04:14 PM.
 
Old 06-23-2004, 04:25 PM   #10
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Great. Thank you both for hanging in there with me. Some good news here. I almost forgot that I had made a boot floppy. Yes, sometimes I am a big dummy. I found it and booted up without a hitch. I have my Slack system up and running--newbie friendly GUIs and all. From a terminal I ran uname -r and the origional 2.4.22 is running. Must be a lilo problem. It will be easier (I hope) to fix this little snag from here rather than jumping all over the place.

drowstar, I am going to give your suggestions a try and we will see what happens. Thanks again.

tsw
 
Old 06-23-2004, 04:35 PM   #11
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Ok, I looked in /boot and do not seem to have a bzImage or initrd.img of any kind. Neither is there one in /usr/src. This seems very courious to me. Any suggestions?

Thank You,
tsw

bash-2.05b# ls -l
total 11225
-rw------- 1 root root 1185529 Jun 23 02:35 System.map
-rw-r--r-- 1 root root 609166 Sep 2 2003 System.map-ide-2.4.22
-rw------- 1 root root 1185529 Jun 23 02:30 System.old
-rw-r--r-- 1 root root 512 Jun 21 11:20 boot.0309
lrwxrwxrwx 1 root root 17 Jun 21 10:36 config -> config-ide-2.4.22
-rw-r--r-- 1 root root 38645 Sep 2 2003 config-ide-2.4.22
-rw------- 1 root root 49152 Jun 23 15:24 map
-rw-r--r-- 1 root root 3590171 Jun 23 02:35 vmlinuz
-rw-r--r-- 1 root root 1226706 Sep 2 2003 vmlinuz-ide-2.4.22
-rw-r--r-- 1 root root 3590171 Jun 23 02:30 vmlinuz.old
 
Old 06-23-2004, 04:43 PM   #12
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,340

Rep: Reputation: 73
vmlinuz and bzImage are the same file but different name, usually when you install kernel by hand you do :
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz
cp /usr/src/linux/System.map /boot/

For initrd.img I don't know I never used that.
 
Old 06-23-2004, 06:14 PM   #13
lupin_the_3rd
Member
 
Registered: Oct 2003
Location: Memphis, TN
Distribution: Slackware current
Posts: 485

Rep: Reputation: 30
I don't think slack uses initrd images by default... at least I don't have any... the bzImage is renamed to vmlinuz as keefaz suggests... look in /usr/src/linux/arch/i386/boot/bzImage for vmlinuz.

A quick note... you're running 2.4.22 b/c that is what is one your boot floppy more than likely... it may or may not be one of the kernels in boot... though on a "vanilla" slack install there is a vmlinuz-ide-2.4.22 kernel in /boot. You could point Lilo to this kernel to have a working kernel until you get the 2.6 straightened out. Worth a shot... also, hang in there before reinstalling... I've totally hosed my system several times since installing slack which wasn't that long ago and I've recovered from all of them so far after being tempted to just reinstall... and as you said... you learn more that way!
 
Old 06-23-2004, 06:45 PM   #14
tsw
Member
 
Registered: May 2004
Location: Colorado
Distribution: Mandrake 10 power-pack
Posts: 74

Original Poster
Rep: Reputation: 15
Thanks everyone for the help. I am currently make installing the 2.6.5 kernel. I started from stratch and am hoping for better reseults. As for the kernel panic I believe it was caused by lilo not being able to find the ./config file for 2.4.22. I copied it to over to /usr/src/linux. Again, hoping for better results.

Very good idea to point lilo towards the ide-2.4.22. I will add that to lilo once the kernel is finished. I had a similiar thought. One last question concerning the new kernel. It is my understanding that lilo will automatically get updated with the new info: 1. Is this true? 2. If not, can a person simply add a new stanza in lilo.config, run lilo from the command line, and if no errors be satified it will work? Thanks again to you all.

tsw
 
Old 06-23-2004, 07:05 PM   #15
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,340

Rep: Reputation: 73
A kernel panic may be caused by various reasons but not by lilo not able to find ./config because lilo is really not able to find it

You need to do run lilo after the changes in the lilo config, then lilo write the changes in the MBR section of your drive.

With another bootloader like GRUB it is different because it reads its config at boot so you don't have to run grub after changes in menu.

Last edited by keefaz; 06-23-2004 at 07:07 PM.
 
  


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
make: *** No rule to make target 'menuconfig' yussef Debian 10 12-22-2005 09:23 AM
make: *** No rule to make target `menuconfig' Ezzy Linux - Newbie 3 04-21-2005 09:21 AM
lopster v1.2.2 make error: No rule to make target `m4/glibc21.m4' Kropotkin Fedora 0 10-31-2004 11:19 AM
make: *** No rule to make target 'gconfig'. Stop. cswake Slackware 4 10-10-2004 12:13 PM
make: **** No rule to make target 'bzImage' qingjuan Linux - General 5 04-02-2002 04:04 PM


All times are GMT -5. The time now is 12:27 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration