vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, Gang. It isn't like I've never compiled a kernel before. I'm asking here because you guys are the best. And yes, I've been a Slackware stalwart since 1996. Last night I patched my kernel source to version 2.6.23 and followed my usually reliable procedure, but something weird is happening. I execute "make bzImage", and at the end of the process, I see the usual message: Kernel: arch/i386/boot/bzImage is ready (#1) But when I go to cp it to /boot, all I find in arch/boot/i386/boot is vmlinux.bin, and no bzImage has been created. *Nothing* has changed on my system since I upgraded from kernel 2.6.15 to 2.6.22 a couple of weeks ago. In fact, I successfully re-compiled 2.6.22 twice in the interim. Any ideas? Thanks! Richard Herbert |
| |||
| On Fri, 12 Oct 2007 19:40:04 -0400, Richard Herbert wrote: > But when I go to cp it to /boot, all I find in arch/boot/i386/boot is > vmlinux.bin, and no bzImage has been created. *Nothing* has changed on my > system since I upgraded from kernel 2.6.15 to 2.6.22 a couple of weeks > ago. In fact, I successfully re-compiled 2.6.22 twice in the interim. OMG! Blame it on the beer. For once I wanted to use mc to copy the kernel image, but I was blinded by the way it helpfully highlights +x files. Slinking away and hoping nobody notices ... sorry! Sheesh! Richard Herbert |
| |||
| ~kurt wrote: > Richard Herbert <rherbert@starbug.dom> wrote: > >>Slinking away and hoping nobody notices ... sorry! Sheesh! > > > BTW, the README says you can just type "make" now - no need for > "make bzImage". > Oh yeah that's a huge help! You still have to go through eight billion options in the configurator, but once that's done you can build it in seven fewer keystrokes... |
| |||
| Chris Sorenson <csoren@isd.net> wrote: > > Oh yeah that's a huge help! You still have to go through eight billion > options in the configurator, but once that's done you can build it in > seven fewer keystrokes... I can never remember what to capitalize for "bzImage".... - Kurt |
| |||
| ~kurt wrote: > I can never remember what to capitalize for "bzImage".... Um ... that would be the 'I' ... ;-) I hope I've helped! -- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems and Network analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ---------------------------------------------------------------------- |
| |||
| ~kurt (actinouranium@earthlink.net) writes: > Sylvain Robitaille <syl@alcor.concordia.ca> wrote: >> >> Um ... that would be the 'I' ... ;-) >> >> I hope I've helped! > > For now. I won't remember tomorrow.... > Doesn't the iPod use a lowercase "i"? If so, that might work. Just remember that it's the reverse. Michael |
| |||
| Richard Herbert wrote: > On Fri, 12 Oct 2007 19:40:04 -0400, Richard Herbert wrote: > >> But when I go to cp it to /boot, all I find in arch/boot/i386/boot is >> vmlinux.bin, and no bzImage has been created. *Nothing* has changed on my >> system since I upgraded from kernel 2.6.15 to 2.6.22 a couple of weeks >> ago. In fact, I successfully re-compiled 2.6.22 twice in the interim. > > OMG! > > Blame it on the beer. For once I wanted to use mc to copy the kernel > image, but I was blinded by the way it helpfully highlights +x files. To avoid another post, your next kernel (2.6.24) will be in arch/x86/boot/ -- Hans |
| ||||
| On Wed, 17 Oct 2007 18:12:19 +0200, Hans wrote: > To avoid another post, your next kernel (2.6.24) will be in > arch/x86/boot/ Thanks for the heads up; I like the change. I can't remember the last time I touched a 386 anyway. I should have just tried 'find . -name bzImage'. Like I said, blame it on the beer. Richard Herbert |
| Thread Tools | |
| Display Modes | |
|
|