Re: kernel building question
On Mon, 2005-10-31 at 07:53 +0100, Lionel Elie Mamane wrote: On Mon, Oct 31, 2005 at 02:23:06AM +0200, Aaron wrote: fakeroot make-kpkg --append-to-version -vanilla --revision 0.1 kernel_image Tzafrir mentioned: make-kpkg --rootcmd fakeroot Yes, use make-kpkg --rootcmd fakeroot instead of fakeroot make-kpkg. It will give fakeroot less work, because it will be used only where (pseudo-)root privileges are needed. ah the last build I su's to root and things went quicker and took less system load. Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Sun, Oct 30, 2005 at 12:11:15AM +0200, Yedidyah Bar-David wrote: On Sun, Oct 30, 2005 at 01:16:53AM +0200, Aaron wrote: I have been building for 2 days and am wondering why, I see that a process called faked-sysv is using 80% of my processor, anyone know what that is? faked is used by fakeroot, which is probably used when building debian packages. Should not be used by vanilla kernel compiles. However on Debian it is generally preffered to build kernels using make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when building a vanilla kernel. faked should take that much CPU time, though. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Sun, 30 Oct 2005, Aaron wrote: However on Debian it is generally preffered to build kernels using make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when building a vanilla kernel. faked should take that much CPU time, though. So it has been building for two days already, I have do simple tasks but no serious work while it builds,It is up to: just out of curiousity - what kind of hardware are you running this compilation on? compiling a kernel should certainly not take more then 1-2 hours on a machine from the last few years - no matter which kernel features you're using. somthing is fishy here... sounds as if you managed to get the build process to go into a loop ;) -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
I have a pIII with 300mg ram. I am also thinking maybe its a loop Aaron On Sun, 2005-10-30 at 18:37 +0200, guy keren wrote: On Sun, 30 Oct 2005, Aaron wrote: However on Debian it is generally preffered to build kernels using make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when building a vanilla kernel. faked should take that much CPU time, though. So it has been building for two days already, I have do simple tasks but no serious work while it builds,It is up to: just out of curiousity - what kind of hardware are you running this compilation on? compiling a kernel should certainly not take more then 1-2 hours on a machine from the last few years - no matter which kernel features you're using. somthing is fishy here... sounds as if you managed to get the build process to go into a loop ;) = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
No I scrolled up I don't think its a loop. I didn't make clean before I started and a previous build was interupted by a kid. could this make things go so slow? Aaron On Sun, 2005-10-30 at 18:37 +0200, guy keren wrote: On Sun, 30 Oct 2005, Aaron wrote: However on Debian it is generally preffered to build kernels using make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when building a vanilla kernel. faked should take that much CPU time, though. So it has been building for two days already, I have do simple tasks but no serious work while it builds,It is up to: just out of curiousity - what kind of hardware are you running this compilation on? compiling a kernel should certainly not take more then 1-2 hours on a machine from the last few years - no matter which kernel features you're using. somthing is fishy here... sounds as if you managed to get the build process to go into a loop ;) = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Sun, 30 Oct 2005, Aaron wrote: No I scrolled up I don't think its a loop. I didn't make clean before I started and a previous build was interupted by a kid. could this make things go so slow? no - but it could explain why it's in such a loop. if i were you, i'd start afresh - if it's still compiling now, it means it is running for 3 days in a row - which is un-natural --guy Aaron On Sun, 2005-10-30 at 18:37 +0200, guy keren wrote: On Sun, 30 Oct 2005, Aaron wrote: However on Debian it is generally preffered to build kernels using make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when building a vanilla kernel. faked should take that much CPU time, though. So it has been building for two days already, I have do simple tasks but no serious work while it builds,It is up to: just out of curiousity - what kind of hardware are you running this compilation on? compiling a kernel should certainly not take more then 1-2 hours on a machine from the last few years - no matter which kernel features you're using. somthing is fishy here... sounds as if you managed to get the build process to go into a loop ;) -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On 10/30/05, Aaron [EMAIL PROTECTED] wrote: O faked should take that much CPU time, though. if that means anything, but I remember kernel building only taking a few hours?? I think he forgot to type the not - a kernel build should *not* take that long on any kind of hardware (not even on a 386). --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
ok I just killed it. Ignoring the instructions I got from googling. how should I proceed now. what I did was copy the config from my running kernel and the remove a few obvious things and then fakeroot make-kpkg --append-to-version -vanilla --revision 0.1 kernel_image btw the kernel_image should that be there? is that supposed to be substitued for something else? Tzafrir mentioned: make-kpkg --rootcmd fakeroot Thanks Aaron On Mon, 2005-10-31 at 09:30 +1100, Amos Shapira wrote: On 10/30/05, Aaron [EMAIL PROTECTED] wrote: O faked should take that much CPU time, though. if that means anything, but I remember kernel building only taking a few hours?? I think he forgot to type the not - a kernel build should *not* take that long on any kind of hardware (not even on a 386). --Amos = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
Hi all I am starting again and noticed that in building my kernel the processor type was pentium pro. I have a PIII, should this be Pentium MMX? Thanks Aaron On Sun, 2005-10-30 at 01:45 +0200, Aaron wrote: Ok some background. I am running demudi which has custom lowlatency kernels. This is for proaudio, which I sometimes play with.. But with the latest kernels from demudi the smp kernels won't boot on my system. Why do you think your kernel won't boot? If it contains all the options then it would usually pick the right driver. Youre right if I keep everything it should boot. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? It depends mostly on your hardware but also on what you want to do with your system. Do homework. I am not trying to get to involved just a multimedia smp kernel that boots for me. Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On 10/31/05, Aaron [EMAIL PROTECTED] wrote: ok I just killed it. Ignoring the instructions I got from googling. how should I proceed now. There are pretty clear instrcutions under /usr/share/doc/kernel-package/README.gz, read the entire document and decide which route you want to take BEFORE you begin the process. I recommand also studying make-kpkg(1) so you get a better understanding of the instructions in the README file. Remember that as long as you don't dpkg -i your-kernel-package.deb no irreversible harm should happen (and even when you DO install your-kernel-package.deb, there are 99% chances that you won't loose the current working kernel). I use a script to wrap make-kpkg with my favourite command line parameters. what I did was copy the config from my running kernel and the remove a few obvious things and then Note that if you just want to use an existing config then use make oldconfig in stage 2%. Always start the kernel-building process with make clean. fakeroot make-kpkg --append-to-version -vanilla --revision 0.1 kernel_image btw the kernel_image should that be there? is that supposed to be substitued for something else? kernel_image should usually be there. Read make-kpkg(1). Tzafrir mentioned: make-kpkg --rootcmd fakeroot I usually just su to root when I do these things, but it's just an ancient habbit. Thanks You are welcome. Aaron --Amos PS - I'm on the mailing list so no need to CC me separatly. To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
Strange how miopic I get, for things I am familiar with I run to /usr/share/doc/* to learn new things but just don't think to look there for the obvious... On Mon, 2005-10-31 at 11:44 +1100, Amos Shapira wrote: /usr/share/doc/kernel-package/README.gz As for ccing I am to my dismay back to using evolution after using mutt which only give me the choice of reply or reply to all... mutt was better Anyways I will read the docs and I hope ask less stupid questions. thanks Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Mon, Oct 31, 2005 at 02:23:06AM +0200, Aaron wrote: fakeroot make-kpkg --append-to-version -vanilla --revision 0.1 kernel_image Tzafrir mentioned: make-kpkg --rootcmd fakeroot Yes, use make-kpkg --rootcmd fakeroot instead of fakeroot make-kpkg. It will give fakeroot less work, because it will be used only where (pseudo-)root privileges are needed. -- Lionel = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Mon, Oct 31, 2005 at 03:06:03AM +0200, Aaron wrote: Hi all I am starting again and noticed that in building my kernel the processor type was pentium pro. I have a PIII, should this be Pentium MMX? Well, no, it should be Pentium III. (Config option CONFIG_MPENTIUMIII, labelled Pentium-III/Celeron(Coppermine)/Pentium-III Xeon) -- Lionel = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
kernel building question
Hi all, I am trying to build a custom kernel for debian and as I am building I see a ton of scsi drivers, go by. There is no way I need all these drivers, but how do I determine which ones I need? I see that usb storage devices are treated as scsi devices, I also have one plextor scsi cdrom and two onboard controllers. I am not sure what else would use scsi, but since I have a good chance that the kernel I am compiling now may not boot, I would like the next time I do this to remove as much unneeded things as I can. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? Thanks Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
Hello Aaron, If you did not play too much with the kernel configuration, then you probably left all those SCSI device drivers configured as M (modules). This means that thosee drivers would be loaded only if the corresponding SCSI device is detected when peripherals are being probed. Therefore, all those modules would be harmless. The only damage you'll incur is with extra compilation time (few minutes if your computer is not too slow). --- Omer On Sat, 2005-10-29 at 21:09 +0200, Aaron wrote: Hi all, I am trying to build a custom kernel for debian and as I am building I see a ton of scsi drivers, go by. There is no way I need all these drivers, but how do I determine which ones I need? I see that usb storage devices are treated as scsi devices, I also have one plextor scsi cdrom and two onboard controllers. I am not sure what else would use scsi, but since I have a good chance that the kernel I am compiling now may not boot, I would like the next time I do this to remove as much unneeded things as I can. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? Thanks Aaron -- Jara Cimrman. A name to remember. My own blog is at http://www.livejournal.com/users/tddpirate/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
Beware, though, that if the hard drive you boot from is a SCSI / SATA one too, you should take a special precaution -- either don't build the 'SCSI disk (sd) driver' nor your SCSI / SATA controller's driver built as modules (but rather compile them into the kernel) or use the initrd feature. Otherwise you'll have a chicken-and-egg problem. Same warning goes about compiling your IDE drivers as modules, with the difference that IDE drives usually don't have a custom IDE Controller module. initrd is how distros (RedHat, Debian and everyone else) make their kernel packages support all possible SCSI controllers without infinitely bloating the kernel with tons of drivers compiled inside. Look up initrd for more info. If you decide to make your own initrd image with mkinitrd (it's easy -- but, as with all those kernel-compiling games, one mistake can make you rush for your rescue CD so have one handy), make sure your /etc/modprobe.conf contains: alias scsi_hostadapter yourscsicontrollermodule For example, my SATA hard drive sitting on an nForce 3 SATA controller, required: alias scsi_hostadapter sata_nv This alias line is how modern versions of mkinitrd determine what SCSI driver to pack into the initrd image they create. On ש', 2005-10-29 at 20:27 +0200, Omer Zak wrote: Hello Aaron, If you did not play too much with the kernel configuration, then you probably left all those SCSI device drivers configured as M (modules). This means that thosee drivers would be loaded only if the corresponding SCSI device is detected when peripherals are being probed. Therefore, all those modules would be harmless. The only damage you'll incur is with extra compilation time (few minutes if your computer is not too slow). --- Omer On Sat, 2005-10-29 at 21:09 +0200, Aaron wrote: Hi all, I am trying to build a custom kernel for debian and as I am building I see a ton of scsi drivers, go by. There is no way I need all these drivers, but how do I determine which ones I need? I see that usb storage devices are treated as scsi devices, I also have one plextor scsi cdrom and two onboard controllers. I am not sure what else would use scsi, but since I have a good chance that the kernel I am compiling now may not boot, I would like the next time I do this to remove as much unneeded things as I can. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? Thanks Aaron To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On Sat, Oct 29, 2005 at 09:09:59PM +0200, Aaron wrote: Hi all, I am trying to build a custom kernel for debian and as I am building I see a ton of scsi drivers, go by. There is no way I need all these drivers, but how do I determine which ones I need? A recent issue of kernel traffic mentioned a project to do this automatically. I did not try it myself. http://www.kerneltraffic.org/kernel-traffic/kt20050926_329.html#4 -- Didi = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
On 10/30/05, Aaron [EMAIL PROTECTED] wrote: Hi all, I am trying to build a custom kernel for debian and as I am building I see a ton of scsi drivers, go by. There is no way I need all these drivers, but how do I determine which ones I need? In addition to Omer's explenation about modules, to answer you question specifically: 1. Consider why you are compiling your own kernel - debian's default kernel is supposed to come with extra security patches and to be tracked by Debian's security team - when you compile your own kernel, unless you are tracking kernel issues daily and know what you are doing, you may loose these security enhancements. 2. Install kernel-package and use it to create debian packages, these are then easier to track using debian's package management tools. 3. Read the documentation that comes with the kernel source tree, start with the README file in the root directory, and there are tons of docs under Documentation. 4. Run one of make menuconfig/xconfig/gconfig or somesuch in the root of the kernel source tree in order to start an interactive kernel configuration interface where you can pick which drivers you want. (make sure that root can start X clients if you use one of the graphic options, test by running xlogo as root). I see that usb storage devices are treated as scsi devices, I also have one plextor scsi cdrom and two onboard controllers. I am not sure what else would use scsi, but since I have a good chance that the kernel I am compiling now may not boot, I would like the next time I do this to remove as much unneeded things as I can. Why do you think your kernel won't boot? If it contains all the options then it would usually pick the right driver. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? It depends mostly on your hardware but also on what you want to do with your system. Do homework. Cheers, --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: kernel building question
Ok some background. I am running demudi which has custom lowlatency kernels. This is for proaudio, which I sometimes play with.. But with the latest kernels from demudi the smp kernels won't boot on my system. Why do you think your kernel won't boot? If it contains all the options then it would usually pick the right driver. Youre right if I keep everything it should boot. In fact is there link to some place that lists what extra uneeded stuff is put in the vanilla kernel, which I can safely exclude? It depends mostly on your hardware but also on what you want to do with your system. Do homework. I am not trying to get to involved just a multimedia smp kernel that boots for me. Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
