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]
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: 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
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
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
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?
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.
