problem compiling new kernel
Hi to Everyone, With my old SARGE system, as stated here last week, I was unable to boot newly compiled kernels, most likely because of the faulty initrd.img that I got using 'mkinitrd'. For this reason, I decided to install Lenny. Now, with Lenny, I haven't so far been able to go any further in recompiling usable kernels. 2.6.30.4 did compile without errors, but then I found that I had no 'mkinitrd' on my new system. How am I to generate an initrd.img ? I was unable to find any package that I could install using apt-get with the name 'mkinitrd', there is no such thing either in the cache base. However, when I installed Lenny (72 hours ago), the install program did generate an initrd.img-2.6.26-2-686 that is now installed in my /boot directory, and my /boot/grub/menu.lst file does specify this file in the boot menu. Thanks in advance for your help P.S. I did find a doc about some related subjects in the /Documentation directory of the downloaded kernel... but it was so old and obsolete that it was useless, dated 1998 and mentioning only lilo, not grub... this in a recent kernel doc (2008-2009) ! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling new kernel
bdebreil 写道: Hi to Everyone, With my old SARGE system, as stated here last week, I was unable to boot newly compiled kernels, most likely because of the faulty initrd.img that I got using 'mkinitrd'. For this reason, I decided to install Lenny. Now, with Lenny, I haven't so far been able to go any further in recompiling usable kernels. 2.6.30.4 did compile without errors, but then I found that I had no 'mkinitrd' on my new system. How am I to generate an initrd.img ? I was unable to find any package that I could install using apt-get with the name 'mkinitrd', there is no such thing either in the cache base. However, when I installed Lenny (72 hours ago), the install program did generate an initrd.img-2.6.26-2-686 that is now installed in my /boot directory, and my /boot/grub/menu.lst file does specify this file in the boot menu. Thanks in advance for your help P.S. I did find a doc about some related subjects in the /Documentation directory of the downloaded kernel... but it was so old and obsolete that it was useless, dated 1998 and mentioning only lilo, not grub... this in a recent kernel doc (2008-2009) ! update-initramfs maybe the tool you are after. Google it or man it. It should be installed on your system. Or you can install it with initramfs-tools. Good luck. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling new kernel
On Fri, 28 Aug 2009 19:07:45 +0800 Niu Kun haoniu...@gmail.com wrote: bdebreil 写道: ... Now, with Lenny, I haven't so far been able to go any further in recompiling usable kernels. 2.6.30.4 did compile without errors, but then I found that I had no 'mkinitrd' on my new system. How am I to generate an initrd.img ? I was unable to find any package that I could install using apt-get with the name 'mkinitrd', there is no such thing either in the cache base. However, when I installed Lenny (72 hours ago), the install program did generate an initrd.img-2.6.26-2-686 that is now installed in my /boot directory, and my /boot/grub/menu.lst file does specify this file in the boot menu. ... update-initramfs maybe the tool you are after. Google it or man it. It should be installed on your system. Or you can install it with initramfs-tools. Assuming that you're building kernel packages with kernel-package, you may be being hit by this: The image postinst no longer runs the initramfs creation commands. Instead, there are example scripts provided that will perform the task. These scripts will work for official kernel images as well. /usr/share/doc/NEWS.Debian.gz Basically, the short version of what you need to do is: cp /usr/share/doc/kernel-package/examples/etc/kernel/postinst.d/initramfs /etc/kernel/postinst.d/ [This really needs to be in a faq somewhere, if it isn't already. It comes up frequently on the list.] Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling new kernel
On Fri, Aug 28 2009, Celejar wrote: Assuming that you're building kernel packages with kernel-package, you may be being hit by this: The image postinst no longer runs the initramfs creation commands. Instead, there are example scripts provided that will perform the task. These scripts will work for official kernel images as well. /usr/share/doc/NEWS.Debian.gz Basically, the short version of what you need to do is: cp /usr/share/doc/kernel-package/examples/etc/kernel/postinst.d/initramfs /etc/kernel/postinst.d/ You might also want to clean things up: cp /usr/share/doc/kernel-package/examples/etc/kernel/postrm.d/initramfs \ /etc/kernel/postrm.d/ This clean up files created in the postinst. manoj -- Now here's something you're really going to like! Rocket J. Squirrel Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Help on compiling new kernel
Hi list, there is one thing I never did before and that is compiling a kernel. I've got an old 266er dual board and would like to compile the kernel that it will also use the second cpu, in addition to that I'd like to use lvm-mod and the LVM10, so that I can build logical volume groups. I've searched the net a little bit with google and also tried to get more info out of the readme's, but I don't get what "they" aretalking about. Does somebody know a really good Howto, which explains how to compile a kernel step by step? Thanks a lot for your help, Jens head_int.gif
Re: Help on compiling new kernel
Jens Simmoleit wrote: Hi list, there is one thing I never did before and that is compiling a kernel. I've got an old 266er dual board and would like to compile the kernel that it will also use the second cpu, in addition to that I'd like to use lvm-mod and the LVM10, so that I can build logical volume groups. I've searched the net a little bit with google and also tried to get more info out of the readme's, but I don't get what they are talking about. Does somebody know a *really good* Howto, which explains how to compile a kernel *step by step*? Thanks a lot for your help, Jens hi jens baking a new kernel for your debian box is not too hard, if you use the tools in kernel-package. as the name suggests, kernel-package will produce a .deb package that you can install/remove with dpkg. so the tricky part for you will be the configuration, which in turn depends mostly on your hardware components (you should know what's in your box). read the debian reference for instructions: http://www.debian.org/doc/manuals/reference/ch-kernel.en.html hth #!michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help on compiling new kernel
Thanks Mate, worked fine! I now have Volume Groups and I see the second penguin @ boot time :-) Love it!! Problem solved, Jens - Original Message - From: Michael Rauch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 12:55 PM Subject: Re: Help on compiling new kernel Jens Simmoleit wrote: Hi list, there is one thing I never did before and that is compiling a kernel. I've got an old 266er dual board and would like to compile the kernel that it will also use the second cpu, in addition to that I'd like to use lvm-mod and the LVM10, so that I can build logical volume groups. I've searched the net a little bit with google and also tried to get more info out of the readme's, but I don't get what they are talking about. Does somebody know a *really good* Howto, which explains how to compile a kernel *step by step*? Thanks a lot for your help, Jens hi jens baking a new kernel for your debian box is not too hard, if you use the tools in kernel-package. as the name suggests, kernel-package will produce a .deb package that you can install/remove with dpkg. so the tricky part for you will be the configuration, which in turn depends mostly on your hardware components (you should know what's in your box). read the debian reference for instructions: http://www.debian.org/doc/manuals/reference/ch-kernel.en.html hth #!michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help on compiling new kernel
Jens Simmoleit simmel at anymotion.de writes: Does somebody know a really good Howto, which explains how to compile a kernel step by step? Yes, check the Kernel Compiling How-to at the Newbiedoc project: http://newbiedoc.sourceforge.net --M. Kirchhoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
Travis Crump wrote: As I wrote above, some instructions suggest deleting it and recreating it to my new kernel directory. So if I do not have it, I was wondering if I should create it (of course I cannot recreate it). In any case, I was also expecting someone who says I *should* have that link to also be able to give a reason why. regards, -HS To compile the kernel itself, it is unnecessary, but some third-party modules expect the source to be in /usr/src/linux in order to compile . Ah! I didn't know that. So in this case, I guess I should make that link whenever I compile a kernel. I just compiled it again and figured out what were the problems. I will list what I did to solve them in a separate message. Thanks for you input, I appreciate it. -HS -- (Remove all underscores,_if any_, from my email address to get the correct one. Apologies for the inconvenience, but this is to reduce spam.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
sön 2003-12-07 klockan 00.11 skrev H. S.: Hi, While doing a google search to read pages on who to compile a new Linux kernel the Debian way, I see some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? . . . Thanks, -HS This is a good document to read when building your first Debian kernel: http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en /Markku Kellberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
Markku Kellberg wrote: sön 2003-12-07 klockan 00.11 skrev H. S.: Hi, While doing a google search to read pages on who to compile a new Linux kernel the Debian way, I see some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? This is a good document to read when building your first Debian kernel: http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en /Markku Kellberg Thanks. I did read it. But I couldn't find where it says why I *should* have that link. I do see why I shouldn't leave it there though. If it does mention ... well, maybe it was late, I was tired with compiling the kernel multiple times or a mixture of all the fact and I missed tha info :) But as the other poster has suggested, some third party programs may need that link. regards, -HS -- (Remove all underscores,_if any_, from my email address to get the correct one. Apologies for the inconvenience, but this is to reduce spam.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is symlink linu necessary while compiling new kernel?
Hi,
While doing a google search to read pages on who to compile a new Linux
kernel the Debian way, I see some of them mentioning that I should first
delete a symlink linux in /usr/src if it exists before I untar and
unzip a download kernel file, and then recreate it. Some pages do not
suggest this. Is this a step crucial?
I have a file:
--
(Remove all underscores,_if any_, from my email address to get the
correct one. Apologies for the inconvenience, but this is to reduce spam.)
{src} ls -1
kernel-headers-2.4.22-1
kernel-headers-2.4.22-1-686
kernel-image-2.4.22-nvidia_10.00.Custom_i386.deb
kernel-source-2.4.22
kernel-source-2.4.22-hs1
kernel-source-2.4.22.tar.bz2
modules
nvidia-kernel-2.4.22-nvidia_1.0.4496-2+10.00.Custom_i386.deb
nvidia-kernel-source.tar.gz
rpm
and I have extracted kernel-source-2.4.22.tar.bz2 and renamed the
resulting directory to kernel-source-2.4.22-hs1. Then I enter this
directory and continue the process of compiling the kernel (make-pgk
clean, then menuconfig, then make step). I don't have the linux link.
Will this be a problem?
Thanks,
-HS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu: some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? [...] clean, then menuconfig, then make step). I don't have the linux link. Will this be a problem? If it is not there, why should you delete it?!? -- Leandro Guimares Faria Corsetti Dutra [EMAIL PROTECTED] Belo Horizonte, Londrina, So Paulo +55 (11) 5686 9607 http://br.geocities.com./lgcdutra/ +55 (11) 5685 2219 Soli Deo Gloria!+55 (11) 9406 7191 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
Leandro Guimares Faria Corsetti Dutra wrote: Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu: some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? [...] clean, then menuconfig, then make step). I don't have the linux link. Will this be a problem? If it is not there, why should you delete it?!? As I wrote above, some instructions suggest deleting it and recreating it to my new kernel directory. So if I do not have it, I was wondering if I should create it (of course I cannot recreate it). In any case, I was also expecting someone who says I *should* have that link to also be able to give a reason why. regards, -HS -- (Remove all underscores,_if any_, from my email address to get the correct one. Apologies for the inconvenience, but this is to reduce spam.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
H. S. [EMAIL PROTECTED] writes: While doing a google search to read pages on who to compile a new Linux kernel the Debian way, I see some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? Yes. You might have noticed that the root directory in the kernel tarball is called linux. Thus, if you have a symlink to another kernel source called that, it would untar the files into the other kernel source's directory. -- Björn Lindström [EMAIL PROTECTED] http://bkhl.elektrubadur.se/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
Björn Lindström wrote:
H. S. [EMAIL PROTECTED] writes:
While doing a google search to read pages on who to compile a new
Linux kernel the Debian way, I see some of them mentioning that I
should first delete a symlink linux in /usr/src if it exists before
I untar and unzip a download kernel file, and then recreate it. Some
pages do not suggest this. Is this a step crucial?
Yes. You might have noticed that the root directory in the kernel
tarball is called linux. Thus, if you have a symlink to another kernel
source called that, it would untar the files into the other kernel
source's directory.
I guess I am missing something here. I have a file
kernel-source-2.4.22.tar.bz2 in /usr/src, and when I do:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
I get the listing as:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
kernel-source-2.4.22/
kernel-source-2.4.22/COPYING
kernel-source-2.4.22/CREDITS
kernel-source-2.4.22/Documentation/
kernel-source-2.4.22/Documentation/arm/
kernel-source-2.4.22/Documentation/arm/Booting
kernel-source-2.4.22/Documentation/arm/ConfigVars
kernel-source-2.4.22/Documentation/arm/MEMC
kernel-source-2.4.22/Documentation/arm/Netwinder
kernel-source-2.4.22/Documentation/arm/README
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is symlink linu necessary while compiling new kernel?
H. S. wrote: Leandro Guimares Faria Corsetti Dutra wrote: Em Sat, 06 Dec 2003 18:11:13 -0500, H. S. escreveu: some of them mentioning that I should first delete a symlink linux in /usr/src if it exists before I untar and unzip a download kernel file, and then recreate it. Some pages do not suggest this. Is this a step crucial? [...] clean, then menuconfig, then make step). I don't have the linux link. Will this be a problem? If it is not there, why should you delete it?!? As I wrote above, some instructions suggest deleting it and recreating it to my new kernel directory. So if I do not have it, I was wondering if I should create it (of course I cannot recreate it). In any case, I was also expecting someone who says I *should* have that link to also be able to give a reason why. regards, -HS To compile the kernel itself, it is unnecessary, but some third-party modules expect the source to be in /usr/src/linux in order to compile. pgp0.pgp Description: PGP signature
Re: is symlink linu necessary while compiling new kernel?
H. S. [EMAIL PROTECTED] writes:
I guess I am missing something here. I have a file
kernel-source-2.4.22.tar.bz2 in /usr/src, and when I do:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
I get the listing as:
{src} tar -jtf kernel-source-2.4.22.tar.bz2
kernel-source-2.4.22/
kernel-source-2.4.22/COPYING
kernel-source-2.4.22/CREDITS
In that case it wouldn't be necessary. However, if you were to get the
vanilla Linux source, the directory is just called linux.
Also, you would still have to rm the linux link before making the new
link, since if you have a symlink to a directory called linux and to
for example:
$ ln -sf kernel-source-2.4.22 linux
You would create a link called kernel-source-2.4.22 in the directory
linked to by linux.
--
Björn Lindström [EMAIL PROTECTED]
http://bkhl.elektrubadur.se/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling new kernel modules
Alex Malinovich [EMAIL PROTECTED] writes: I've been rolling my own kernel using make-kpkg and the other wonderful tools we Debianites have at our disposal for over a year now, yet something just occured to me. Is it possible to compile individual kernel modules outside of the actual kernel compilation? Is this extra modules (e.g. lm-sensors, ALSA, OpenAFS)? If so, it's easy enough to unpack the modules into /usr/src/modules (or $MODULE_LOC), and then run 'make-kpkg modules-image --added-modules=foo' from the top of your kernel source tree. If it's things in the kernel, you probably do wind up wanting to completely rebuild the whole thing. The last couple of times I've built kernels, I've blindly selected every possible USB device driver as a module; I figure sometime I might want to use something, and all it costs me is a little disk space and a little compile time. (The other suggestion of running 'make modules' and 'make modules_install' is only somewhat faster, I think, and makes the installed files disagree with what the make-kpkg-generated package has; mostly this means you'll have extra files left over if you remove the kernel-image package, but it also means that if you every try to use debsums it'll tell you the package is corrupted.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Compiling new kernel modules
I've been rolling my own kernel using make-kpkg and the other wonderful tools we Debianites have at our disposal for over a year now, yet something just occured to me. Is it possible to compile individual kernel modules outside of the actual kernel compilation? I still have the full source directory of my latest kernel build in its entirety in /usr/src, and I'd really like to compile a few modules without a) having to sit through a full recompile and, more importantly b) give up my ~40 day uptime? (I know that 40 days probably isn't much to most people here, but I'm never gonna make it to 360 days if I can't even go 40! :) Considering that I still have the source directory, I'd IMAGINE that it would be possible to do this, but I have no idea how I might go about it. Any suggestions are greatly appreciated. -Alex signature.asc Description: This is a digitally signed message part
Re: Compiling new kernel modules
Alex Malinovich wrote: I've been rolling my own kernel using make-kpkg and the other wonderful tools we Debianites have at our disposal for over a year now, yet something just occured to me. Is it possible to compile individual kernel modules outside of the actual kernel compilation? I still have the full source directory of my latest kernel build in its entirety in /usr/src, and I'd really like to compile a few modules without a) having to sit through a full recompile and, more importantly b) give up my ~40 day uptime? (I know that 40 days probably isn't much to most people here, but I'm never gonna make it to 360 days if I can't even go 40! :) Considering that I still have the source directory, I'd IMAGINE that it would be possible to do this, but I have no idea how I might go about it. Any suggestions are greatly appreciated. I think you could do 'make oldconfig', select the modules you want, exit, then 'make modules', then 'make modules_install'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird problem with init after compiling new kernel
Yup. I found the solution. I seem to have been creating an incompatibility problem using the base files (the kernel) from a CD distribution but all GNU files from the internet. Since the kernel is a modular one it will boot initially but after compilation (using the hence incompatible GNU compiler libs) it won't boot any more. It seems that even the original modular kernel is affected in some way, or rather the init.d is, because even that won't boot from the point where init is loaded. I solved the issue by reïnstalling the whole box from scratch. First I tried a full CD installation (all files came from the same distribution) but since the occurence I have also successfully installed systems completely from the ftp-sites. (which runs smoothly with a cable-connection and downloads of 250 to 300 kB/s :) ) Hope this helps you out! If your cause is not the same, you probably just have to recompile and see very carefully that you didn't miss a thing somewhere; I once tried running a 686 kernel on a 486. I missed the processor type option somewhere. That didn't work greetz, Wouter. - Original Message - From: Peter Kahle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 12, 2001 4:22 AM Subject: Re: weird problem with init after compiling new kernel Did you ever find a solution to this problem? I'm having a similar problem with a Pentium system. If you did find a solution, could you please let me know what it was? Thanks, Peter
Re: weird problem with init after compiling new kernel
On Mon, Jun 11, 2001 at 12:45:03AM +0200, Mythiq wrote: hello everyone, I have compiled a new kernel for an 486 which was going to be a filtering firewall. Not for a while I'm afraid, because it won't boot up anymore. (btw: I started with a clean freshly installed system with debian 2.2.18pre21) Lilo works fine; it boots the kernel; after the kernel has started booting, there is a step where the ext2 fs root is mounted read-only (as usual); the next step is my problem: kernel-panic, no init found. try to pass init= to the kernel. and there it halts. No problem I thought, reboot, hold shift at startup and inform lilo to pass init=/sbin/init to the kernel (which is a stupid thing to do since that is the default, this part ought to go by itself!) right: that did'nt work. Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) Would be nice if anyone can help. baking a kernel on this machine takes about half a day... Did you change your /etc/lilo.conf to reflect the new kernel changes? Did you run /sbin/lilo after installing the new kernel? If not that could be why you can't access your kernels. At the boot prompt try linux init=/bin/sh or linux single That may get you in so you can fix your problem. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: weird problem with init after compiling new kernel
Thnx but I've already tried ALL of your suggestions (it's there all written down, isn't it ;) ?, I might have missed something?) ~ My main question still stands unanswered: Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) to try and make things a little more clear: the kernel boots! Lilo works fine! it is the init part where all activity halts at the point where normally the supplementary hardware (sound, network, mice, special CD-romplayers, etc) would be initialized after which the daemons would be started. At the moment of halt the memory is filled with kernel but not yet with system configuration. ??que?? I'm confused of this. Help! Mythiq. - Original Message - From: ktb [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Monday, June 11, 2001 8:58 AM Subject: Re: weird problem with init after compiling new kernel On Mon, Jun 11, 2001 at 12:45:03AM +0200, Mythiq wrote: hello everyone, I have compiled a new kernel for an 486 which was going to be a filtering firewall. Not for a while I'm afraid, because it won't boot up anymore. (btw: I started with a clean freshly installed system with debian 2.2.18pre21) Lilo works fine; it boots the kernel; after the kernel has started booting, there is a step where the ext2 fs root is mounted read-only (as usual); the next step is my problem: kernel-panic, no init found. try to pass init= to the kernel. and there it halts. No problem I thought, reboot, hold shift at startup and inform lilo to pass init=/sbin/init to the kernel (which is a stupid thing to do since that is the default, this part ought to go by itself!) right: that did'nt work. Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) Would be nice if anyone can help. baking a kernel on this machine takes about half a day... Did you change your /etc/lilo.conf to reflect the new kernel changes? Did you run /sbin/lilo after installing the new kernel? If not that could be why you can't access your kernels. At the boot prompt try linux init=/bin/sh or linux single That may get you in so you can fix your problem. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird problem with init after compiling new kernel
Wouter == Wouter Bakker [EMAIL PROTECTED] writes: Wouter to try and make things a little more clear: the kernel boots! Wouter Lilo works fine! it is the init part where all activity halts Wouter at the point where normally the supplementary hardware (sound, Wouter network, mice, special CD-romplayers, etc) would be Wouter initialized after which the daemons would be started. At the Wouter moment of halt the memory is filled with kernel but not yet Wouter with system configuration. Check the root filesystem in /etc/lilo.conf . Does it point to the right device? Another possibility: you have not compiled in the drivers needed to mount the root partition. - If you have a SCSI disk, did you select your card? - If you have an IDE disk, you should have selected IDE disk support. - Did you select the ext2 file system? Note that you have to have the relevant option compiled in the kernel, and not as a module (i.e., select `Y' in the configure process). (As a side note: can you still boot the old kernel? - type linuxOLD at the LILO prompt.) -- G. ``Iggy'' Geens - ICQ: #64109250 Home: [EMAIL PROTECTED] - Work: [EMAIL PROTECTED] WWW: http://users.pandora.be/guy.geens/ ``I was thinking about how everyone was dying and maybe it's time to live.'' - Eels
weird problem with init after compiling new kernel
hello everyone, I have compiled a new kernel for an 486 which was going to be a filtering firewall. Not for a while I'm afraid, because it won't boot up anymore. (btw: I started with a clean freshly installed system with debian 2.2.18pre21) Lilo works fine; it boots the kernel; after the kernel has started booting, there is a step where the ext2 fs root is mounted read-only (as usual); the next step is my problem: "kernel-panic, no init found. try to pass init= to the kernel." and there it halts. No problem I thought, reboot, hold shift at startup and inform lilo to pass init=/sbin/init to the kernel (which is a stupid thing to do since that is the default, this part ought to go by itself!) right: that did'nt work. Euhm... corrupt init? (all of a sudden??); used Loadlin with a kernel-image from the debian-1 CD and mounted my freshly installed system as root (/dev/hda2) (another funny thing: my swap is /dev/hda1, I seem to have made it a primary partition; is that a bad thing anyone?) an annoying modprobe-loop as a result but I can enter the system (in single mode only) and find a perfectly normal init, and a perfectly normal /bin/sh and /etc/init (which I also have tried) Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) Would be nice if anyone can help. baking a kernel on this machine takes about half a day... greetz, Mythiq
SOLVED :) Re: how do I enable dmfe when compiling new kernel
hi it worked thanks Yes I had to enable CONFIG_EKSPERIMENTAL /jens On Wed, 13 Dec 2000, Erik Steffl wrote: seach for dmfe.c in dirver/net/Makefile, you'll find that it is compiled if CONFIG_DM9102 is set. Then (in kernel source root): find . -name Makefile -print|xargs grep CONFIG_DM9102 and you'll find that ./drivers/net/Config.in says: if [ $CONFIG_EXPERIMENTAL = y ]; then tristate 'DM9102 PCI Fast Ethernet Adapter support (EXPERIMENTAL)' CONFIG_DM9102 fi I guess that means that you need to enable experimental drivers in kernel (it's another option in make menuconfig) to be offered this module. erik Jens Lauterbach wrote: I'm using make menuconfig and thats working fine, but I cant find dmfe under the netcard drivers, all though I can find the file /usr/src/kernel-source-2.2.17/drivers/net/dmfe.c So its there, so how do I include it, when I'm compiling. with potato, 2.2.17-compact it works fine! what is wrong?? /jens On Wed, 13 Dec 2000, Erik Steffl wrote: use make-kpkg, read the docs (it's quite simple). at one point it asks you to configure kernel - do it by run make config (command line), make menuconfig (ncurses required, text based gui), make xconfig (x windows interface, I think you need tk and wish for this). there you have a chance to decide what you want to include. erik Jens Lauterbach wrote: hi I'm about to recompile my potato 2.2.17 kernel. But how do I include dmfe (netcard driver) so I can load it as a module??? thanks in advance --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University
how do I enable dmfe when compiling new kernel
hi I'm about to recompile my potato 2.2.17 kernel. But how do I include dmfe (netcard driver) so I can load it as a module??? thanks in advance --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University
Re: how do I enable dmfe when compiling new kernel
use make-kpkg, read the docs (it's quite simple). at one point it asks you to configure kernel - do it by run make config (command line), make menuconfig (ncurses required, text based gui), make xconfig (x windows interface, I think you need tk and wish for this). there you have a chance to decide what you want to include. erik Jens Lauterbach wrote: hi I'm about to recompile my potato 2.2.17 kernel. But how do I include dmfe (netcard driver) so I can load it as a module??? thanks in advance --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how do I enable dmfe when compiling new kernel
I'm using make menuconfig and thats working fine, but I cant find dmfe under the netcard drivers, all though I can find the file /usr/src/kernel-source-2.2.17/drivers/net/dmfe.c So its there, so how do I include it, when I'm compiling. with potato, 2.2.17-compact it works fine! what is wrong?? /jens On Wed, 13 Dec 2000, Erik Steffl wrote: use make-kpkg, read the docs (it's quite simple). at one point it asks you to configure kernel - do it by run make config (command line), make menuconfig (ncurses required, text based gui), make xconfig (x windows interface, I think you need tk and wish for this). there you have a chance to decide what you want to include. erik Jens Lauterbach wrote: hi I'm about to recompile my potato 2.2.17 kernel. But how do I include dmfe (netcard driver) so I can load it as a module??? thanks in advance --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University
Re: how do I enable dmfe when compiling new kernel
seach for dmfe.c in dirver/net/Makefile, you'll find that it is compiled if CONFIG_DM9102 is set. Then (in kernel source root): find . -name Makefile -print|xargs grep CONFIG_DM9102 and you'll find that ./drivers/net/Config.in says: if [ $CONFIG_EXPERIMENTAL = y ]; then tristate 'DM9102 PCI Fast Ethernet Adapter support (EXPERIMENTAL)' CONFIG_DM9102 fi I guess that means that you need to enable experimental drivers in kernel (it's another option in make menuconfig) to be offered this module. erik Jens Lauterbach wrote: I'm using make menuconfig and thats working fine, but I cant find dmfe under the netcard drivers, all though I can find the file /usr/src/kernel-source-2.2.17/drivers/net/dmfe.c So its there, so how do I include it, when I'm compiling. with potato, 2.2.17-compact it works fine! what is wrong?? /jens On Wed, 13 Dec 2000, Erik Steffl wrote: use make-kpkg, read the docs (it's quite simple). at one point it asks you to configure kernel - do it by run make config (command line), make menuconfig (ncurses required, text based gui), make xconfig (x windows interface, I think you need tk and wish for this). there you have a chance to decide what you want to include. erik Jens Lauterbach wrote: hi I'm about to recompile my potato 2.2.17 kernel. But how do I include dmfe (netcard driver) so I can load it as a module??? thanks in advance --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Jens Lauterbach [EMAIL PROTECTED] Roskilde University
Compiling New Kernel
I have just installed Debian GNU/Linux 2.1 with kernel 2.0.36 and wanted to update the kernel to 2.2 I downloaded the source code for the Linux kernel 2.2.15 I was reading the Documentation/Changes document to make sure I had the necessary versions of the various software packages. I found that the recommended versions for a couple of packages are newer than the versions available through dselect. These are: package dselect version recommended version == == Procps 1.2.9-3 2.0.3 Util-linux 2.9g-6 2.9z I have updated my dselect packages list, and it appears that no newer versions are available. Do I need to change my access URL's for dselect? If so, which are recommended? Also, the Documentation/Changes document requires procinfo version 16. As far as I can tell, I do not even have procinfo on my system. It is also not listed (as far as I can see) in dselect. Is this package important? Thanks. = A. Scott White - Director, Information Systems Affiliated Computer Services - Healthcare Solutions Group
RE: Compiling New Kernel
package dselect version recommended version == == Procps 1.2.9-3 2.0.3 Util-linux 2.9g-6 2.9z I have updated my dselect packages list, and it appears that no newer versions are available. Do I need to change my access URL's for dselect? If so, which are recommended? Also, the Documentation/Changes document requires procinfo version 16. As far as I can tell, I do not even have procinfo on my system. It is also not listed (as far as I can see) in dselect. Is this package important? procps has what you need. To get the versions 2.2.15 wants, you need to upgrade your system to debian 2.2 (potato). potato is currently frozen and in testing for release. So it should be safe for you to move up. Just realize that you will likely have to update most packages on your system. If you compile something like 2.2.13 I think it can be done on slink.
Re: Compiling New Kernel
Sean 'Shaleh' Perry wrote: procps has what you need. To get the versions 2.2.15 wants, you need to upgrade your system to debian 2.2 (potato). potato is currently frozen and in not necessarily. on my system: ii procps 2.0.6-6The /proc file system utilities. ii util-linux 2.10f-3Miscellaneous system utilities. ii libc6 2.0.7.19981211 GNU C Library: shared libraries Linux p166 2.2.15 #1 Fri May 5 05:00:33 CEST 2000 i586 unknown cu -- hafi
IDE/DMA/VIA chipset question (compiling new kernel)
Hello, Before anything else, I'd like to thank the people who have helped me before. This has been really nice... And so far, support here in this list has been really efficient. Thank you all. Ok - now, to my little problem: I have a Pentium II 400Mh with 64Mb RAM; my motherboard and HD both support DMA/66, the CD-rom drive also supports DMA/33. I'm running potato now, and I've compiled a new kernel (2.3.47), optimized for my box... But at a certain point when running make xconfig I had one doubt... According to the help box, I shouldn't choose to use DMA by default when available is I have a VIA VP2 chipset. Well, I have a VIA 693/596 chipset in my motherboard (which has 2 PCI IDE interfaces on-board)... And I don't know if my chipset would be somehow related or derived from the VP2, or whatever... In short, I don't know if it's safe to use DMA by default... So I've compiled it without it. Now... My questions are: 1) How much difference would that option make? 2) Would it be safe to compile the kernel with that option? Thanks a lot! J. -- Jeronimo Pellegrini Institute of Computing - Unicamp - Brazil http://www.dcc.unicamp.br/~jeronimo mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]
Re: bin86 missing (was Re: compiling new kernel)
well, some people ( myself included ) rarely if ever use dselect and should not be bound to do so just get this standard package installed. i've compiled enough kernels and done enough installs and could argue that i myself would install this package by rote but that has yet to be the case and build a new kernel is often the first thing i do after each install ( unless i have a custom kernel deb at hand ) it would be nice if there was a conditional depends that selected bin86 whenever a kernel source package was selected for install and the arch = iX86 since it is basically pointless to try to build a new kernel without it. thx, m* .I can't understand how so many people seem to lose bin86. It's .standard, therefore it is selected by default during the first pass .of dselect when installing a new system. Where/when does it fade away? . .Cheers, . -- and the ultimate cruelty of loves' pinions beset his appearance
Fw: compiling new kernel
ok, so we everyone is clear i am trying to get the make bzImage command to write this /usr/src/linux-2.2.x/arch/i386/boot/bzImage but it doesn't, it gives me an error make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 and doesn't create the bzImage file why? - Original Message - From: John Leget [EMAIL PROTECTED] To: Beavis [EMAIL PROTECTED]; debian-user@lists.debian.org Sent: Monday, March 06, 2000 9:10 PM Subject: Re: compiling new kernel Ughh, just run an additional command ( after youve installed bin86 re previous email) make install does the work of copying and running lilo at the end. Id suggest you modify /etc/lilo.conf to also point to a known working kernel and have a resue disk and maybe even a boot disk handy. They come in handy when things dont work out as expected Ummm, speaking from personal experience of course cheers Beavis wrote: i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: compiling new kernel
ok first off, it is 'I heard Beavis say' not said u nerd! second, translate this into english please: #dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz pretend I am a newbie, which i am.please don't tell anybody! how would you explain this? Once upon a time, I heard Beavis said as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 #dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz -- ,--- --. | Chanop Silpa-Anan [EMAIL PROTECTED] | | Australian National University | | Tel. +61 2 6279 8826, +61 2 6279 8837 (office hour) | | +61 2 6249 5240 (home +voice mail) | | Debian GNU/BSD GPG key on request | `--- --'
Re: compiling new kernel
Once upon a time, I heard Nick Barron say ok first off, it is 'I heard Beavis say' not said u nerd! Terribly sorry for my bad English, I hope that I get it right this time! second, translate this into english please: I'm not sure whether I could translate this into a good English or not. #dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz briefly, it means that as86 belongs to package 'bin86'. pretend I am a newbie, which i am.please don't tell anybody! how would you explain this? Once upon a time, I heard Beavis said as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found Does this mean that you don't have 'as86'? Chanop
Re: compiling new kernel
Nick Barron wrote: ok first off, it is 'I heard Beavis say' not said u nerd! second, translate this into english please: #dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz pretend I am a newbie, which i am.please don't tell anybody! how would you explain this? apt-get install bin86 , the package you need. Alternatively, http://www.debian.org/Packages/frozen/devel/bin86.html has the package you need too: download, then dpkg -i bin86*deb where you downloaded it. -- mindlace - [EMAIL PROTECTED] good design is as close as I want to get to ideology.
Re: compiling new kernel
He means: Nick Barron wrote: second, translate this into english please: #dpkg -S as86 as the root user (# prompt) run the command 'dpkg -S as86' bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz This is the output of the dpkg command from above. Looks as though it lists all files with 'as86' in the filename that are on the system, and the package they came from (bin86 in this case). Matthew
Re: Fw: compiling new kernel
Once upon a time, I heard Nick Barron say ok, so we everyone is clear i am trying to get the make bzImage command to write this /usr/src/linux-2.2.x/arch/i386/boot/bzImage but it doesn't, it gives me an error make[1]: as86: Command not found Is this clear enough? make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 and doesn't create the bzImage file why? You need as86 which is in bin86 package. -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GE d? s+: a- C++ UL++ P+ L+++ E- W++ N++ o-- K- w--- O- M+ V-- PS PE++ Y PGP++ t+ 5++ X+ R tv+++ b++ DI+ D- G e+++ h* r+ y+ --END GEEK CODE BLOCK-- pgpdul60fEjSR.pgp Description: PGP signature
bin86 missing (was Re: compiling new kernel)
Quoting Nick Barron ([EMAIL PROTECTED]): ok, so we everyone is clear i am trying to get the make bzImage command to write this /usr/src/linux-2.2.x/arch/i386/boot/bzImage but it doesn't, it gives me an error make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 and doesn't create the bzImage file why? It looks as if you don't have the as86 command. This is a fairly common problem. The kernel source only suggests the bin86 package (which contains as86) but does not depend on it. This is because only intel users need it. I can't understand how so many people seem to lose bin86. It's standard, therefore it is selected by default during the first pass of dselect when installing a new system. Where/when does it fade away? Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
RE: bin86 missing (was Re: compiling new kernel)
First thing I did after my install was remove all unused packages that didn't cause dselect to have kittens. bin86 was one of them. found that out quick enough. The second thing I tried to do after install was recompile he kernel. Bryan I can't understand how so many people seem to lose bin86. It's standard, therefore it is selected by default during the first pass of dselect when installing a new system. Where/when does it fade away?
compiling new kernel
this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas?
compiling new kernel
i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas?
Re: compiling new kernel
i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 Get bin86 package. Andrew - Andrei S. Ivanov [EMAIL PROTECTED] [EMAIL PROTECTED] http://scorpio.dynodns.net -| http://scorpio.myip.org-| --All the pages bundled together. http://arshes.dyndns.org -| If one does not work, try another :) UIN 12402354 To get my GnuPG public key, go to scorpio.dynodns.net/GnuPG scorpio.myip.org/GnuPG arshes.dyndns.org/GnuPG -
Re: compiling new kernel
Youre missing a package on your system ( Well what do you know im actually learning this stuff ) did a dpkg -S as86 you need to install the bin86 package cheers Beavis wrote: i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: compiling new kernel
Ughh, just run an additional command ( after youve installed bin86 re previous email) make install does the work of copying and running lilo at the end. Id suggest you modify /etc/lilo.conf to also point to a known working kernel and have a resue disk and maybe even a boot disk handy. They come in handy when things dont work out as expected Ummm, speaking from personal experience of course cheers Beavis wrote: i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: compiling new kernel
Beavis == Beavis [EMAIL PROTECTED] writes: i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 ul:/etc/dhcpc# dpkg -S /usr/bin/as86 bin86: /usr/bin/as86 Which means that you need to install the bin86 package. If I may inquire, why are you trying to compile a 2.2.x kernel for a i386? That's going to hurt. I compiled a 2.0.x kernel on my old 486 and it took over 5 hours! Well, hope this helps. why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing:Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Marshal Wong (Yes, that is my first name. Not a title.) Bitter? I'm not bitter, just battle-hardened.
Re: compiling new kernel
On Mon, Mar 06, 2000 at 03:18:52PM -0800, Beavis wrote: this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? Install the kernel-package .deb and use make-kpkg. It will handle all of the above for you and create a kernel-image package which you can then install. -- Bob Nielsen, N7XY (RN2)[EMAIL PROTECTED] Tucson, AZ DM42nh QRP-L #1985 SOC #77http://www.primenet.com/~nielsen
Re: compiling new kernel
You are missing the assembler. Install bin86. On Mon, Mar 06, 2000 at 03:55:08PM -0800, Beavis wrote: i am trying to compile the kernel 2.2.14 on to my i386 machine please help if u can, thnakx update: after doing make bzImage, it starts to compile, which takes about 10 mins or so right. then at the end it says: as86 -0 -a -o bbootsect.o bbootsect.s make[1]: as86: Command not found make[1]: *** [bbootsect.o] Error 127 make[1]: Leaving directory '/usr/src/linux-2.2.14/arch/i386/boot' make: *** [bzImage] Error 2 why is this happening? i went over a redid the make menuconfig and even checked to make sure it saved properly .config in /usr/src/linux-2.2.14 this is what i am doing: Once that is all done and you choose Exit and save your config file, you must run make dep followed by make clean. And now the fun begins, type make bzImage to build your kernel. This will take awhile (15mins+) so go browse our site a little and send us some feedback ;). Instead of make bzImage, you can also do make zdisk which will write your kernel to a floppy disk instead. Now that it's done, you have to do make modules followed by make modules_install and that should be it for the Kernel if all goes well. Now it's time to set up LILO. First you have to move the newly created Kernel to your /boot directory. Do this by typing cp /usr/src/linux-2.2.x/arch/i386/boot/bzImage /boot/vmlinuz-2.2.x. Next would be to move the System.map file to your /boot directory. Do that by typing cp /usr/src/linux-2.2.x/System.map /boot/System.map-2.2.x. ..but i get cp: /usr/src/linux-2.2.14/arch/i386/boot/bzImage: No such file or directory any ideas? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Bob Nielsen, N7XY (RN2)[EMAIL PROTECTED] Tucson, AZ DM42nh QRP-L #1985 SOC #77http://www.primenet.com/~nielsen
Re: compiling new kernel
Hello there, On 7 Mar 2000, Marshal Wong wrote: If I may inquire, why are you trying to compile a 2.2.x kernel for a i386? That's going to hurt. I compiled a 2.0.x kernel on my old 486 and it took over 5 hours! What kind of kernel did you compile, and on what kind of machine? I compiled a 2.0.36 kernel twice on 486 machines: One on a machine with Intel 486DX2 @ 75 MHz with 8MB RAM: This took about 55 Minutes. The second on a machine with Cyrix 486SX @ 66MHz with 24 MB RAM. This took about 25 Minutes, though the kernel was a bit larger, with more networking drivers included. Greetings, Daniel
Re: compiling new kernel
486/33 8MB 2.0.36 Daniel == Daniel Reuter [EMAIL PROTECTED] writes: Hello there, On 7 Mar 2000, Marshal Wong wrote: If I may inquire, why are you trying to compile a 2.2.x kernel for a i386? That's going to hurt. I compiled a 2.0.x kernel on my old 486 and it took over 5 hours! What kind of kernel did you compile, and on what kind of machine? I compiled a 2.0.36 kernel twice on 486 machines: One on a machine with Intel 486DX2 @ 75 MHz with 8MB RAM: This took about 55 Minutes. The second on a machine with Cyrix 486SX @ 66MHz with 24 MB RAM. This took about 25 Minutes, though the kernel was a bit larger, with more networking drivers included. Greetings, Daniel -- Marshal Wong (Yes, that is my first name. Not a title.) Bitter? I'm not bitter, just battle-hardened.
Re: problems after compiling new kernel
On Sat, 19 Jun 1999, Pollywog wrote:
After compiling kernel 2.2.10 and trying to install new software, I got:
make all-recursive
make[1]: Entering directory `/home/pollywog/ksnuffle-0.2'
Making all in libpcap-0.4
make[2]: Entering directory `/home/pollywog/ksnuffle-0.2/libpcap-0.4'
gcc -g -I. -Ilinux-include -DHAVE_MALLOC_H=1 -DHAVE_ETHER_HOSTTON=1
-DHAVE_STRERROR=1 -DHAVE_NET_IF_ARP_H=1 -c ./pcap-linux.c
./pcap-linux.c:31: net/if.h: No such file or directory
./pcap-linux.c:33: net/if_arp.h: No such file or directory
make[2]: *** [pcap-linux.o] Error 1
Why does this happen? Am I doing something wrong? It seems I frequently
lose if.h
if.h and if_arp.h are in the libc6-dev package. Is that package properly
installed?
On Sun, 20 Jun 1999, Remco van de Meent wrote:
In the 2.2.x kernels, if.h is in include/linux/, so instead of #include
net/if.h, you should use #include linux/if.h.
Unless you're compiling a kernel or linking explicitly against the kernel
headers (a -I/usr/src/linux/include flag?), this shouldn't make the
difference. Note that in Debian, /usr/include/{linux,asm} shouldn't be
symlinks into a kernel source tree at all; see the README included in a
kernel-headers package (aka /usr/lib/kernel-package/README.headers from
the kernel-package package) for a detailed explanation.
problems after compiling new kernel
After compiling kernel 2.2.10 and trying to install new software, I got: make all-recursive make[1]: Entering directory `/home/pollywog/ksnuffle-0.2' Making all in libpcap-0.4 make[2]: Entering directory `/home/pollywog/ksnuffle-0.2/libpcap-0.4' gcc -g -I. -Ilinux-include -DHAVE_MALLOC_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_NET_IF_ARP_H=1 -c ./pcap-linux.c ./pcap-linux.c:31: net/if.h: No such file or directory ./pcap-linux.c:33: net/if_arp.h: No such file or directory make[2]: *** [pcap-linux.o] Error 1 Why does this happen? Am I doing something wrong? It seems I frequently lose if.h -- Andrew
Re: problems after compiling new kernel
Pollywog wrote: After compiling kernel 2.2.10 and trying to install new software, I got: ... ./pcap-linux.c:31: net/if.h: No such file or directory ... Why does this happen? Am I doing something wrong? It seems I frequently lose if.h In the 2.2.x kernels, if.h is in include/linux/, so instead of #include net/if.h, you should use #include linux/if.h. HTH, -Remco
