Re: Re: how are you kids compiling kernels these days?
That is amazing. What is the difference in the results of the two methods? ray -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120620182037.1753ead7c2b35a7d15c5b99498690bcc.1aabcba3c6@email11.secureserver.net
Re: how are you kids compiling kernels these days?
On Thu, May 31, 2012 at 10:30 PM, Stephen Powell zlinux...@wowway.com wrote: On Thu, 31 May 2012 06:18:06 -0400 (EDT), Tom H wrote: One of this list's regulars has a very good page: http://users.wowway.com/~zlinuxman/Kernel.htm Thanks for the vote of confidence, Tom. By the way, I think a lot of the confusion in this thread comes from the fact that a linux kernel source package in Debian is classified as a *binary* package. Therefore, it is not installed with apt-get source, and you must be root to install it. For example, # aptitude install linux-source-3.2 There is a corresponding Debian source package for this binary package, of course, and it is called, believe it or not, linux-2.6! You can install this Debian source package, if you want, by means of $ apt-get --only-source source linux-2.6 At the time of this writing, the version of this source package in the Wheezy archive is 3.2.18-1, which contains kernel source code from upstream kernel version 3.2.18. This issue, and many other gotchas, are documented on the above- mentioned web page. If you plan to use make-kpkg or make deb-pkg to build the kernel, the binary package is the one you want to install. You're welcome; it's very good. The difference between aptitude install linux-source-3.2 and apt-get source linux-2.6 is that the first downloads one tar file to /usr/src and the second downloads two tar files (orig and diff; as well as one dsc file) to the current directory, expands the orig and applies the diff to the expanded orig. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szvy-hleud9pl-q+passdzk76r7mywx1rs3tf6cmas...@mail.gmail.com
Re: how are you kids compiling kernels these days?
Response coming from the Show Me State. ;) On 5/30/2012 10:43 PM, Paul Johnson wrote: http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 Please note Pradeep's last remark after the to-do list: Please let know if you need help. He has far more experience with what he's instructing you to do than likely everyone on the debian-users list combined, as he does it every day. And keep in mind he's the one asking you to do all this in the first place. Thus it makes sense to lean on him. This is a pretty serious request, I'm willing to try, but I wish somebody who has done this recently would share the experience. Many of us build our own kernels. But likely few build in out-of-tree or experimental patches, which is what's being requested of you. I found this: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage That's a good reference, as is this: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html But neither provide a perfect step-by-step guide for precisely what you need to do here. And as you've seen both were written assuming the reader is using a standard (old) 2.6.x Debian kernel, not the much newer 3.2 testing kernel you're using. And each was written many years ago, and updated over time, which is why you'll see references to 2.6.18 and 2.6.26 as well as 2.6.32. its about rebuilding kernels in the 2.6 era. Are there problems in translating this to 3.2? I can't even get out of the starting gate. How to apt-get the kernel source? The steps will be mostly the same. The file names, maybe some paths, and make commands may be different. I'm running Debian testing. Ok, good to know. How to get the kernel source? First find what's available in your repo: ~$ aptitude search linux-source ... p linux-source-3.2 - Linux kernel source for version 3.2 with Debian patches That's from a Squeeze box w/backports repo. You should see something similar with testing. Here's what I've got now: $ uname -r 3.2.0-2-amd64 $ dpkg -l | grep linux-image ii linux-image-3.0.0-1-amd643.0.0-3 Linux 3.0.0 for 64-bit PCs ii linux-image-3.2.0-2-amd643.2.17-1 Linux 3.2 for 64-bit PCs ii linux-image-amd643.2+44 Linux for 64-bit PCs (meta-package) So you'll probably want to do this: ~$ aptitude install linux-source-3.2 That should get you the latest testing (Wheezy) kernel source, 3.2.18-1. You're at 3.2.17-1, not far behind. I'd first ask Pradeep which kernel version he wants you to apply his patch to, because you currently have no kernel source on your machine. It may be worth noting that this level of testing/debugging isn't typically undertaken by anyone but software developers (kernel or otherwise), or those non-dev users who spend a good deal of time frequently building their own kernels. I build my own stripped down server kernels from vanilla source about 2-3 times a year and am familiar with the process, and even I would need some hand holding during this endeavor, mainly because I don't use modules. Also note these debugging exercises can turn into excessive time burners. My advice, given your lack of recent experience with kernel building, and the potential for time burn simply trying to learn what's needed to get up to speed, would be to simply move back to the 3.0.1 kernel with which your wireless apparently worked ok according to your bug report entry, and leave the debugging of the more recent Intel driver code to others. If you understand what lay ahead of you and are comfortable with that, soldier on. If you do, it would be polite to inform Pradeep of your limited experience in this area, so he understands what will be required of him while moving forward on this with you. Best of luck Paul. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fc70dbd.5040...@hardwarefreak.com
Re: how are you kids compiling kernels these days?
On 5/31/2012 12:37 AM, Paul Johnson wrote: $ apt-get source linux-??? apt-get downloads files from repositories. apt-cache search looks through your downloaded package lists to find matches to your search criteria. Put simply, you're using the wrong command. Search, find the one you want, then install. I'm typing every conceivable combination of those package names and still get nothing. $ apt-get source linux-image-amd64 finds me some downloads, but they are for kernel 2.6. That should return an error, such as this, on Squeeze: ~$ apt-get source linux-image-amd64 Reading package lists... Done Building dependency tree Reading state information... Done E: You must put some 'source' URIs in your sources.list This one is really frustrating. Spend some time with man aptitude. Stop using the deprecated (mostly) apt-get and related commands. The problems you're experiencing right now, confusing searching command with install commands, are one of the reasons aptitude was created: one package management command with options and switches, instead of multiple commands for different functions. Is there a way to view which SOURCE packages are available in a Debian system? Yes, as mentioned in my previous message, aptitude search linux-source On a RedHat style system, I'd go google the SRPM directory and know what to look for. In Debian, I still can't quite understand where the source packages are. Because you're not yet familiar with the tools. Again, man aptitude. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fc710cb.9010...@hardwarefreak.com
Re: how are you kids compiling kernels these days?
Why don't you use the config of your Debian, but get the source from
kernel.org?
From a script I used with Debian/AVLinux:
#!/bin/sh
# sh rt4debian-av
[snip]
apt-get update
apt-get install fakeroot build-essential crash kexec-tools makedumpfile
kernel-package kernel-wedge
apt-get install libncurses5 libncurses5-dev libelf-dev asciidoc
binutils-dev
[snip]
export CONCURRENCY_LEVEL=2
[snip]
# config
cp /boot/config-$(uname -r) .config
[snip]
make oldconfig
[snip]
# Building the kernel
make-kpkg clean
make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers
[snip]
# Installing new packages
make-kpkg clean
dpkg -i ../linux-image-${KERNEL_UNAME}_
${KERNEL_UNAME}-10.00.Custom_*.deb
dpkg -i ../linux-headers-${KERNEL_UNAME}_
${KERNEL_UNAME}-10.00.Custom_*.deb
[snip]
You manually need to check if /lib/modules/[...]/build
and /lib/modules/[...]/source link to the headers.
- Ralf
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1338446126.2572.17.camel@precise
Re: how are you kids compiling kernels these days?
Hi Paul, Paul Johnson wrote: Now I've got a laptop with an Intel Centrino Ultimate 6300 wireless device and it has been very unstable when joining wireless networks. I complained about it in the intel wireless support page and today a technician answered me back with a kernel patch. http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 This is a pretty serious request, I'm willing to try, but I wish somebody who has done this recently would share the experience. I know two ways to do it. One is to build from the official Debian packaging, as described at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html. That page is pretty thorough, so I'll let it cover that itself. Another way is to build the kernel from kernel.org, like so: 0. prerequisites apt-get install build-essential ketchup 1. get the kernel mkdir linux cd linux ketchup 3-rc 2. configure and test cp /boot/config-$(uname -r) .config; # current configuration # optional: disable debugging symbols for a smaller build tree. # This is almost always a good choice, unless you use systemtap # or you use perf to profile the kernel. scripts/config --disable DEBUG_INFO # optional: minimize configuration by only including currently # loaded modules. Most modules that are not loaded are drivers # for hardware you don't have. Make sure your wireless driver # is loaded if you've unloaded it. make localmodconfig make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot ... test test test ... Hopefully it reproduces the bug. So: 3. try the patch cd linux patch -p1 /path/to/the/patch make deb-pkg; # maybe with -j2 dpkg -i ../name of package; # as root reboot ... test test test ... Thanks for your work, and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120531072501.GA16461@burratino
Re: how are you kids compiling kernels these days?
On Wed, May 30, 2012 at 11:43 PM, Paul Johnson pauljoh...@gmail.com wrote: How to get the kernel source? $ apt-get source linux-3.2.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.0 Seems like that ought to work. Or this: $ apt-get source linux-3.2.17 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.17 apt-cache search linux-source aptitude search linux-source -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxdxkoyymmsbtdxzo3ngc6efobch5qrgwxk5bajvzz...@mail.gmail.com
Re: how are you kids compiling kernels these days?
On Thursday 31 May 2012 09:58:22 Tom H wrote: On Wed, May 30, 2012 at 11:43 PM, Paul Johnson pauljoh...@gmail.com wrote: How to get the kernel source? $ apt-get source linux-3.2.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.0 Seems like that ought to work. Or this: $ apt-get source linux-3.2.17 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.17 apt-cache search linux-source aptitude search linux-source I have seen no mention of Paul's sources.list. Surely it is not impossible for there to be an error there, even just a typo? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205311016.43436.lisi.re...@gmail.com
Re: how are you kids compiling kernels these days?
On Thu, May 31, 2012 at 5:16 AM, Lisi lisi.re...@gmail.com wrote: I have seen no mention of Paul's sources.list. Surely it is not impossible for there to be an error there, even just a typo? not without apt spitting out an error with a 'run -f install to fix this'. also, per a prior comment about grabbing the upstream - i'd only do that after you find what all patches are applied to the debian kernel (or at least know the reason behind debian putting them in). this will make tracking down issues simpler. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cah_obicscny42cwebognb6vk2kcwnrn_fws6_qondwyqpd7...@mail.gmail.com
Re: how are you kids compiling kernels these days?
I had the same problem. I had not built the kernel for about a decade. I found the Debian kernel docs lacking. Linux Documentation Project does not have a current guide. So I went back to the vanilla way of building and started writing my own guide ... http://stargate.djbarney.org/freelinking/Compiling%20the%20Linux%20Kernel Barney Holmes I've not built LInux kernels since, well, 1999, when I ran RedHat linux (before EL existed). I've compiled separate modules for the touchpad many times lately, but never a whole kernel. And never on a Debian system. Now I've got a laptop with an Intel Centrino Ultimate 6300 wireless device and it has been very unstable when joining wireless networks. I complained about it in the intel wireless support page and today a technician answered me back with a kernel patch. http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 This is a pretty serious request, I'm willing to try, but I wish somebody who has done this recently would share the experience. I found this: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage its about rebuilding kernels in the 2.6 era. Are there problems in translating this to 3.2? I can't even get out of the starting gate. How to apt-get the kernel source? I'm running Debian testing. How to get the kernel source? $ apt-get source linux-3.2.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.0 Seems like that ought to work. Or this: $ apt-get source linux-3.2.17 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.17 I've tried every variation I can think of. Here's what I've got now: $ uname -r 3.2.0-2-amd64 $ dpkg -l | grep linux-image ii linux-image-3.0.0-1-amd643.0.0-3 Linux 3.0.0 for 64-bit PCs ii linux-image-3.2.0-2-amd643.2.17-1 Linux 3.2 for 64-bit PCs ii linux-image-amd643.2+44 Linux for 64-bit PCs (meta-package) pj -- Paul E. Johnson Professor, Political Science Assoc. Director 1541 Lilac Lane, Room 504 Center for Research Methods University of Kansas University of Kansas http://pj.freefaculty.org http://quant.ku.edu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAErODj80yuiWQZkk8h=zrc43wkuithmhkyc29gwhfeb-mdm...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1b760abd6467a28f7522c39f400b2245.squir...@djbarney.org
Re: how are you kids compiling kernels these days?
On Thu, May 31, 2012 at 5:16 AM, Lisi lisi.re...@gmail.com wrote: On Thursday 31 May 2012 09:58:22 Tom H wrote: On Wed, May 30, 2012 at 11:43 PM, Paul Johnson pauljoh...@gmail.com wrote: How to get the kernel source? $ apt-get source linux-3.2.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.0 Seems like that ought to work. Or this: $ apt-get source linux-3.2.17 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.17 apt-cache search linux-source aptitude search linux-source I have seen no mention of Paul's sources.list. Surely it is not impossible for there to be an error there, even just a typo? A good reminder to check the basics! :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=swbt05gedma-hnqw_mcgmbvpetnrrrzxxfstk8g6jy...@mail.gmail.com
Re: how are you kids compiling kernels these days?
On Thu, May 31, 2012 at 5:19 AM, djbar...@djbarney.org wrote: I had the same problem. I had not built the kernel for about a decade. I found the Debian kernel docs lacking. Linux Documentation Project does not have a current guide. So I went back to the vanilla way of building and started writing my own guide ... http://stargate.djbarney.org/freelinking/Compiling%20the%20Linux%20Kernel One of this list's regulars has a very good page: http://users.wowway.com/~zlinuxman/Kernel.htm -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SzeQUtM4E7YU=ibppic6r4n8hd_uejpgsuwvj7ycuw...@mail.gmail.com
Re: how are you kids compiling kernels these days?
On Thu, May 31, 2012 at 00:37 -0500, Paul Johnson wrote: [...] but they are for kernel 2.6. This one is really frustrating. $ apt-get source linux-image-3.2.0-2-amd64 [...] Picking 'linux-2.6' as source package instead of 'linux-image-3.2.0-2-amd64' [...] Get:1 http://ftp.debian.org/debian/ testing/main linux-2.6 3.2.18-1 (dsc) [94.2 kB] That is expected as the source package for 3.* kernels is, in fact, linux-2.6. In addition to the wiki page you found already there is also a chapter in the wonderful new book on Debian system administration on kernel compilation [0] and a slightly older chapter in the kernel handbook [1]. The latter also discusses the application of patches [2]. It is typically also a good idea to read the README.source in the source package. I am not entirely sure which procedure to recommend as I had the impression that make-kpkg wasn't the recommended way to build a kernel these days. [0] http://debian-handbook.info/browse/stable/sect.kernel-compilation.html [1] http://kernel-handbook.alioth.debian.org/ [2] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.3 -- Wolodja deb...@babilen5.org 4096R/CAF14EFC 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC signature.asc Description: Digital signature
Re: how are you kids compiling kernels these days?
Thanks ! Looks good. I have to add the part about make config to my guide. I'm writing it as I proceed with my own kernel compile. My aim is to make a guide that is accessible to Linux newbies while allowing them access to the full advantages of building a custom kernel. The clearest guide I have found so far that explains very well some of the complex issues involved is ... Linux Kernel in a Nutshell O'Reilly book by Greg Kroah-Hartman (well known Kernel developer) ... http://www.kroah.com/lkn/ ... it can be downloaded for free off that page (Creative Commons license), and it comes highly recommended. Barney Holmes On Thu, May 31, 2012 at 5:19 AM, djbar...@djbarney.org wrote: I had the same problem. I had not built the kernel for about a decade. I found the Debian kernel docs lacking. Linux Documentation Project does not have a current guide. So I went back to the vanilla way of building and started writing my own guide ... http://stargate.djbarney.org/freelinking/Compiling%20the%20Linux%20Kernel One of this list's regulars has a very good page: http://users.wowway.com/~zlinuxman/Kernel.htm -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SzeQUtM4E7YU=ibppic6r4n8hd_uejpgsuwvj7ycuw...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f8146f64f45bebb2e38e05039840d385.squir...@djbarney.org
Re: how are you kids compiling kernels these days?
On Wed, 30 May 2012 22:43:21 -0500, Paul Johnson wrote: I've not built LInux kernels since, well, 1999, when I ran RedHat linux (before EL existed). I've compiled separate modules for the touchpad many times lately, but never a whole kernel. And never on a Debian system. Now I've got a laptop with an Intel Centrino Ultimate 6300 wireless device and it has been very unstable when joining wireless networks. I complained about it in the intel wireless support page and today a technician answered me back with a kernel patch. http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 This is a pretty serious request, I'm willing to try, but I wish somebody who has done this recently would share the experience. (...) What I do is getting the kernel source from Debian (or upstream www.kernel.org) and then apply the patches (patch -p1 file.patch), then run make to build the modules (make /net/wireless/) or if that fails, you can compile the full kernel with a minimal set of modules by using localmodconfig to generate the .config file. I found this: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage I used to follow this one: http://www.debian.org/releases/stable/i386/ch08s06.html.en Although it needs some tweaks but basically works pretty well. its about rebuilding kernels in the 2.6 era. Are there problems in translating this to 3.2? I can't even get out of the starting gate. How to apt-get the kernel source? I'm running Debian testing. How to get the kernel source? (...) You can also grab it manually: http://ftp.de.debian.org/debian/pool/main/l/linux-2.6/linux-2.6_3.2.18.orig.tar.gz Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.05.31.14.25...@gmail.com
Re: how are you kids compiling kernels these days?
On Thu, 31 May 2012 06:18:06 -0400 (EDT), Tom H wrote: One of this list's regulars has a very good page: http://users.wowway.com/~zlinuxman/Kernel.htm Thanks for the vote of confidence, Tom. By the way, I think a lot of the confusion in this thread comes from the fact that a linux kernel source package in Debian is classified as a *binary* package. Therefore, it is not installed with apt-get source, and you must be root to install it. For example, # aptitude install linux-source-3.2 There is a corresponding Debian source package for this binary package, of course, and it is called, believe it or not, linux-2.6! You can install this Debian source package, if you want, by means of $ apt-get --only-source source linux-2.6 At the time of this writing, the version of this source package in the Wheezy archive is 3.2.18-1, which contains kernel source code from upstream kernel version 3.2.18. This issue, and many other gotchas, are documented on the above- mentioned web page. If you plan to use make-kpkg or make deb-pkg to build the kernel, the binary package is the one you want to install. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/820519640.1495507.1338517826421.javamail.r...@md01.wow.synacor.com
how are you kids compiling kernels these days?
I've not built LInux kernels since, well, 1999, when I ran RedHat linux (before EL existed). I've compiled separate modules for the touchpad many times lately, but never a whole kernel. And never on a Debian system. Now I've got a laptop with an Intel Centrino Ultimate 6300 wireless device and it has been very unstable when joining wireless networks. I complained about it in the intel wireless support page and today a technician answered me back with a kernel patch. http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 This is a pretty serious request, I'm willing to try, but I wish somebody who has done this recently would share the experience. I found this: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage its about rebuilding kernels in the 2.6 era. Are there problems in translating this to 3.2? I can't even get out of the starting gate. How to apt-get the kernel source? I'm running Debian testing. How to get the kernel source? $ apt-get source linux-3.2.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.0 Seems like that ought to work. Or this: $ apt-get source linux-3.2.17 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-3.2.17 I've tried every variation I can think of. Here's what I've got now: $ uname -r 3.2.0-2-amd64 $ dpkg -l | grep linux-image ii linux-image-3.0.0-1-amd643.0.0-3 Linux 3.0.0 for 64-bit PCs ii linux-image-3.2.0-2-amd643.2.17-1 Linux 3.2 for 64-bit PCs ii linux-image-amd643.2+44 Linux for 64-bit PCs (meta-package) pj -- Paul E. Johnson Professor, Political Science Assoc. Director 1541 Lilac Lane, Room 504 Center for Research Methods University of Kansas University of Kansas http://pj.freefaculty.org http://quant.ku.edu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAErODj80yuiWQZkk8h=zrc43wkuithmhkyc29gwhfeb-mdm...@mail.gmail.com
Re: how are you kids compiling kernels these days?
On 31/05/12 04:43, Paul Johnson wrote: I've tried every variation I can think of. Have you tried apt-cache search? a0z@kit:~$ apt-cache search linux 3.2 amd64 linux-headers-3.2.0-2-all-amd64 - All header files for Linux 3.2 (meta-package) linux-headers-3.2.0-2-amd64 - Header files for Linux 3.2.0-2-amd64 linux-headers-3.2.0-2-rt-amd64 - Header files for Linux 3.2.0-2-rt-amd64 linux-image-3.2.0-2-amd64 - Linux 3.2 for 64-bit PCs linux-image-3.2.0-2-amd64-dbg - Debugging infos for Linux 3.2.0-2-amd64 linux-image-3.2.0-2-rt-amd64 - Linux 3.2 for 64-bit PCs, PREEMPT_RT linux-image-3.2.0-2-rt-amd64-dbg - Debugging infos for Linux 3.2.0-2-rt-amd64 xen-linux-system-3.2.0-2-amd64 - Xen system with Linux 3.2 on 64-bit PCs (meta-package) linux-image-amd64 - Linux for 64-bit PCs (meta-package) linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT a0z@kit:~$ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fc6edb2.8030...@a0z.eu
Re: how are you kids compiling kernels these days?
On Wed, May 30, 2012 at 11:04 PM, a0z n...@a0z.eu wrote: On 31/05/12 04:43, Paul Johnson wrote: I've tried every variation I can think of. Have you tried apt-cache search? a0z@kit:~$ apt-cache search linux 3.2 amd64 linux-headers-3.2.0-2-all-amd64 - All header files for Linux 3.2 (meta-package) linux-headers-3.2.0-2-amd64 - Header files for Linux 3.2.0-2-amd64 linux-headers-3.2.0-2-rt-amd64 - Header files for Linux 3.2.0-2-rt-amd64 linux-image-3.2.0-2-amd64 - Linux 3.2 for 64-bit PCs linux-image-3.2.0-2-amd64-dbg - Debugging infos for Linux 3.2.0-2-amd64 linux-image-3.2.0-2-rt-amd64 - Linux 3.2 for 64-bit PCs, PREEMPT_RT linux-image-3.2.0-2-rt-amd64-dbg - Debugging infos for Linux Thanks, I see same. Doesn't help, though. What are you typing to get the source for the particular packages you see? I mean literally, what is at the end of $ apt-get source linux-??? I'm typing every conceivable combination of those package names and still get nothing. $ apt-get source linux-image-amd64 finds me some downloads, but they are for kernel 2.6. This one is really frustrating. $ apt-get source linux-image-3.2.0-2-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Picking 'linux-2.6' as source package instead of 'linux-image-3.2.0-2-amd64' NOTICE: 'linux-2.6' packaging is maintained in the 'Svn' version control system at: svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6/ Need to get 105 MB of source archives. Get:1 http://ftp.debian.org/debian/ testing/main linux-2.6 3.2.18-1 (dsc) [94.2 kB] Get:2 http://ftp.debian.org/debian/ testing/main linux-2.6 3.2.18-1 (tar) [98.5 MB] Is there a way to view which SOURCE packages are available in a Debian system? On a RedHat style system, I'd go google the SRPM directory and know what to look for. In Debian, I still can't quite understand where the source packages are. pj -- Paul E. Johnson Professor, Political Science Assoc. Director 1541 Lilac Lane, Room 504 Center for Research Methods University of Kansas University of Kansas http://pj.freefaculty.org http://quant.ku.edu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAErODj9x+-6n6mSRYfFkSoUQV97tVg_HnA9RKwXyPv6s=tq...@mail.gmail.com
Re: how are you kids compiling kernels these days?
On 31/05/12 17:37, Paul Johnson wrote: On Wed, May 30, 2012 at 11:04 PM, a0z n...@a0z.eu wrote: On 31/05/12 04:43, Paul Johnson wrote: I've tried every variation I can think of. Have you tried apt-cache search? a0z@kit:~$ apt-cache search linux 3.2 amd64 linux-headers-3.2.0-2-all-amd64 - All header files for Linux 3.2 (meta-package) linux-headers-3.2.0-2-amd64 - Header files for Linux 3.2.0-2-amd64 linux-headers-3.2.0-2-rt-amd64 - Header files for Linux 3.2.0-2-rt-amd64 linux-image-3.2.0-2-amd64 - Linux 3.2 for 64-bit PCs linux-image-3.2.0-2-amd64-dbg - Debugging infos for Linux 3.2.0-2-amd64 linux-image-3.2.0-2-rt-amd64 - Linux 3.2 for 64-bit PCs, PREEMPT_RT linux-image-3.2.0-2-rt-amd64-dbg - Debugging infos for Linux Thanks, I see same. Doesn't help, though. What are you typing to get the source for the particular packages you see? I mean literally, what is at the end of $ apt-get source linux-??? It's a while for me too, but IIRC kernel sources are different - you download the _binary_ package that has the source in it: linux-source-3.2 Then you can get kernel-package, which has tools to build you a deb from that source (after you've patched it). Anything with package with 'amd64' in the name is presumably compiled for that platform. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fc705e9.2080...@walnut.gen.nz
Re: debian on imac - compiling kernels
On Mon, May 31, 2004 at 08:48:16 +1000, Mal Beaton wrote: I copied the old 2.4 config to the source of the 2.6.6 and did make oldconfig There have been many changes between 2.4 and 2.6 in how config options are named, how they depend on eachother, what the defaults are etc. A copied 2.4 config is unlikely to do the right thing with 2.6. Try taking the time to do a full, proper configuration of 2.6. HTH, Ray -- Pinky, Are You Pondering What I'm Pondering? I think so Brain, but if they called them sad meals, kids wouldn't buy them. Pinky and the Brain in Brain Meets Brawn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian on imac - compiling kernels
J.H.M. Dassen (Ray) wrote: On Mon, May 31, 2004 at 08:48:16 +1000, Mal Beaton wrote: I copied the old 2.4 config to the source of the 2.6.6 and did make oldconfig There have been many changes between 2.4 and 2.6 in how config options are named, how they depend on eachother, what the defaults are etc. A copied 2.4 config is unlikely to do the right thing with 2.6. Try taking the time to do a full, proper configuration of 2.6. HTH, Ray thanks we downloaded the rc2 ? version of linuxppc-2.5-benh linux-2.6.6 and it still had issues. Re rsynced to a later version a day later and all our issues disappeared. Yeh understand the recommendation for full look at 2.6 config 2 of us must have gone through it 50 times was getting frustrated but ended up being an issue with the released kernel (we think) cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian on imac - compiling kernels
I have just been playing with installing debian on an imac computer i just got hold of. The standard installation went fine. All boots and kde works I decided to compile a 2.6.6 kernel to see how it would go I copied the old 2.4 config to the source of the 2.6.6 and did make oldconfig answered all the new questions After a few goes the kernel compiled and installed ok updated yaboot and rebooted on the 2.6.6 kernel i get the following message VFS: cannot open root device hda3 or unknown-block(0,0) Kernel panic: VFS: Unable ot mount root fs on unknown-block(0,0) I have check all the block settings in the 2.6.6 config I have googled away found similar errors but couldnt see a solutions if I boot from linux.old (original) it works has anyone seen this or can give me some pointers of where I should be looking cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Compiling kernels - choosing options
Hi all, Whenever I have compiled a kernel - twice so far on Debian, many times on Slackware - I've struck this issue. There are several features of a kernel that are expected to be configured a particular way for a particular distribution. For example, proc fs support, UNIX98 ptys or whatever they're called, whether parallel printer support should be a module or not. Does Debian (or any distro for that matter) have documents on this? Is the config file in the kernel source package preconfigured with these defaults? Or do I just have to do lots of research myself before I start to make sure I get a kernel that will function properly with my system? Thanks, Richard
Re: Compiling kernels - choosing options
On Mon, Sep 17, 2001 at 01:38:09PM +1200, Richard Hector wrote: | Hi all, | | Whenever I have compiled a kernel - twice so far on Debian, many times | on Slackware - I've struck this issue. | | There are several features of a kernel that are expected to be | configured a particular way for a particular distribution. | | For example, proc fs support, UNIX98 ptys or whatever they're called, | whether parallel printer support should be a module or not. | | Does Debian (or any distro for that matter) have documents on this? Is | the config file in the kernel source package preconfigured with these | defaults? The kernel-image packages for Debian include the config file used to build them as /boot/config-version. | Or do I just have to do lots of research myself before I start to make | sure I get a kernel that will function properly with my system? You have to do that anyways if you are going to know which features you do and don't want. Building a kernel and trying it out is a part of that research. Nothing beats experience :-). -D
Re: problem compiling kernels
On Sat, 20 Jan 2001 21:57:52 -0500, Jonathan D. Proulx said:
Package fails to spend adequate time reading documentation :)
I'm sure there's bugs since it's software, but that's not the problem
I'm having just to lazy to RTFM, as I have another way to do what I
need.
I have just picked up on this thread, so excuse me if I am not answering your
question!
The Debian way of compiling the kernel is *so* easy. What I do is this:
Unpack the kernel source into /usr/src
Change the name of the dir (if necessary) to something like 'kernel-2.4.0' then
symlink it to /usr/src/linux ('ln -s /usr/src/linux-2.4.0 /usr/src/linux'
Cd into /usr/src/linux and do the usual 'make xconfig' as root.
Save the configuration.
Enter 'make-kpkg kernel_image -revision=custom.1.0'
When this has finished you will have a Debian package of your kernel in
/usr/src.
Simply install the package 'dpkg -i
kernel-image-2.4.1-pre8_custom.1.0_i386.deb'
You may need to rename /lib/modules/whatever - but kernel-package will halt and
prompt you to do this if necessary. It will even set up lilo and offer to make
you a boot disk.
It is very handy to have a .deb of the kernel you have rolled - makes it so
easy to have different versions available, and to roll back if you need to.
--
Phillip Deackes
Using Storm Linux 2000
Re: problem compiling kernels
On Sun, Jan 21, 2001 at 12:10:03PM +, Phillip Deackes wrote:
:I have just picked up on this thread, so excuse me if I am not answering your
:question!
:
:The Debian way of compiling the kernel is *so* easy. What I do is this:
:
:Unpack the kernel source into /usr/src
:Change the name of the dir (if necessary) to something like 'kernel-2.4.0' then
:symlink it to /usr/src/linux ('ln -s /usr/src/linux-2.4.0 /usr/src/linux'
:Cd into /usr/src/linux and do the usual 'make xconfig' as root.
:Save the configuration.
:Enter 'make-kpkg kernel_image -revision=custom.1.0'
Wasn't originally my question, but if everyone is so set on me
learning kpkg, well it can only help me, so I have my current kernel
source 2.4.0-test10 all configured from my last build...
cd /usr/src/linux
sudo make-kpkg clean
sudo make-kpkg kernel_image -revision=custom.1.0
complains about arch=i386-none in many ways
sudo make-kpkg -arch=i386 -revision=custom.1.0
and now it bombs near the end of what seems to be make dep with
make[1]: i386-linux-gcc: Command not found
make[1]: *** [init/main.o] Error 127
make[1]: Leaving directory `/usr/src/linux-2.4.0-test10'
make: *** [stamp-build] Error 2
for context the last non-error output is:
make[1]: Leaving directory `/usr/src/linux-2.4.0-test10'
test -f stamp-configure || /usr/bin/make -f
/usr/share/kernel-package/rules configure
/usr/bin/make ARCH=i386 \
CROSS_COMPILE=i386-linux- bzImage
make[1]: Entering directory `/usr/src/linux-2.4.0-test10'
scripts/split-include include/linux/autoconf.h include/config
i386-linux-gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-pipe -march=i686 -c -o init/main.o init/main.c
Why is CROSS_COMPILE defined? The .config builds fine with generic
make dep make bzImage the rest, I know this as this is what
I'm running.
This kpkg Version: $Revision: 1.39.2.1 $, Debian unstable, though I've
had similar trouble (not sure if it the same errors or not), over the
past 2 years or so and always just go back to vanila make
-Jon
Re: problem compiling kernels
On Sun, Jan 21, 2001 at 12:08:43PM -0500, Jonathan D. Proulx wrote: cd /usr/src/linux sudo make-kpkg clean sudo make-kpkg kernel_image -revision=custom.1.0 complains about arch=i386-none in many ways sudo make-kpkg -arch=i386 -revision=custom.1.0 The difference is very subtle, but what I always do is sudo make-kpkg --revision custom.1.0 kernel_image ^^^ I am not sure this makes a big difference but try it out. You don't need the arch flag if you are compiling on i386 for i386. Why is CROSS_COMPILE defined? The .config builds fine with generic I assume because you set arch to any value. Try my suggestion and repost your results. Diego Biurrun
Re: problem compiling kernels
Ok, now I feel a bit of a fool, this does seem to be a bug either in the kernel source (non-debian), or in the way kernel-package parses v2.4 info. I looked at my last mail and realized I was builing a test kernel on an unstable system. I logged into my workstation running stable with 2.2.17 kernel sources, and make-kpkg worked just as it should. This is very similar to my first kernel build, for months I kept getting weird compile errors that I couldn't understand, being very new to linux at the time. One day it worked, and has since, never did figure out what I was doing wrong. To clarify some questions asked: On Sun, Jan 21, 2001 at 07:03:14PM +0100, Diego Biurrun wrote: :On Sun, Jan 21, 2001 at 12:08:43PM -0500, Jonathan D. Proulx wrote: :The difference is very subtle, but what I always do is : :sudo make-kpkg --revision custom.1.0 kernel_image : ^^^ Doesn't make a difference. :I am not sure this makes a big difference but try it out. You don't need :the arch flag if you are compiling on i386 for i386. Shouldn't but for some reason this variable was defaulting to i386-none which is invalid (there's no linux/arch/i386-none directory) : : Why is CROSS_COMPILE defined? The .config builds fine with generic : :I assume because you set arch to any value. Yes, that's exactly it. Thanks, -Jon
problem compiling kernels
Hi, I'm new to Debian and fairly new to Linux. I compiled some kernels (I'm using kernel 2.2.17) for terminals in a network (so I removed everything they don't need from the kernel except the network stuff, etc.) I compiled them on my laptop b/c it's a lot faster. Anyway I did the following after I made the configuration with menuconfig: 'make dep make clean make bzImage make modules make modules_install' Well then I moved the kernels to these machines and everything worked out fine!! But now, when I boot the original kernel on my laptop I get these errors while booting: depmod: *** unresolved symbols in /lib/modules/2.2.17/net/ppp.o depmod: *** unresolved symbols in /lib/modules/2.2.17/net/dummy.o ... now I can't use my modem using ppp anymore b/c when I start 'pon' I get this: ioctl(TIOCSETD(PPP)): Invalid argument(22) /usr/sbin/pppd: This system lacks kernel support for PPP. This could be because the PPP kernel module could not be loaded, or because PPP was not included in the kernel configuration. If PPP was included as a module, try '/sbin/modprobe -v ppp' --'modprobe -v ppp' fails too. I don't know why this is happening b/c everything was working fine before I started compiling kernels. I don't know if 'make modules_install' is the cause for this but I guess it is. (I don't have a lot of experience in compiling kernels) Can anybody tell what causes this and how I can avoid this in the future? TIA Philipp
Re: problem compiling kernels
your problem is that you ran make modules_install on your laptop, which installs your newly built modules over your laptops modules. You may also notice that there are no modules on your terminals. -Casey On Sat, 20 Jan 2001, Philipp Bliedung wrote: Hi, I'm new to Debian and fairly new to Linux. I compiled some kernels (I'm using kernel 2.2.17) for terminals in a network (so I removed everything they don't need from the kernel except the network stuff, etc.) I compiled them on my laptop b/c it's a lot faster. Anyway I did the following after I made the configuration with menuconfig: 'make dep make clean make bzImage make modules make modules_install' Well then I moved the kernels to these machines and everything worked out fine!! But now, when I boot the original kernel on my laptop I get these errors while booting: depmod: *** unresolved symbols in /lib/modules/2.2.17/net/ppp.o depmod: *** unresolved symbols in /lib/modules/2.2.17/net/dummy.o ... now I can't use my modem using ppp anymore b/c when I start 'pon' I get this: ioctl(TIOCSETD(PPP)): Invalid argument(22) /usr/sbin/pppd: This system lacks kernel support for PPP. This could be because the PPP kernel module could not be loaded, or because PPP was not included in the kernel configuration. If PPP was included as a module, try '/sbin/modprobe -v ppp' --'modprobe -v ppp' fails too. I don't know why this is happening b/c everything was working fine before I started compiling kernels. I don't know if 'make modules_install' is the cause for this but I guess it is. (I don't have a lot of experience in compiling kernels) Can anybody tell what causes this and how I can avoid this in the future? TIA Philipp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem compiling kernels
Hi, The easies (though perhaps not most elegant) way to prevent this in the future is to move your modules directory befor the make modules_install, tar up the modules directory from the build then move your old modules back. Your probably going to need to either use the kernel you build or if that's not possible rebuild the kernel on your laptop. The official Debian way is to use make-kpkg to do the kernel build which will create a .deb of the new kernel and modules. Very cool and works well for lots of folks. Personally I've built alot of kernels, but have never got kpkg to behave. Probably because I can build a kernel without it and thus haven't spent the time to really learn how to use this tool. -Jon
Re: problem compiling kernels
Jonathan == Jonathan D Proulx [EMAIL PROTECTED] writes: Jonathan Personally I've built alot of kernels, but have never got kpkg to Jonathan behave. Probably because I can build a kernel without it and thus Jonathan haven't spent the time to really learn how to use this tool. The next time you try, could you please capture the problems you are having in a bug report on kernel-package, please? We can only get improvements in the code if such feedback is available. Thanks, manoj -- I thing you're missing the capability of Makefiles. It takes several _hours_ to do `make' a second time on my machine with the latest glibc sources (and no files are recompiled a second time). I think I'll remove `build' after changing one file if I want to recompile it. Juan Cespedes [EMAIL PROTECTED] Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: problem compiling kernels
On Sat, Jan 20, 2001 at 07:45:18PM -0600, Manoj Srivastava wrote: :Jonathan == Jonathan D Proulx [EMAIL PROTECTED] writes: : : Jonathan Personally I've built alot of kernels, but have never got kpkg to : Jonathan behave. Probably because I can build a kernel without it and thus : Jonathan haven't spent the time to really learn how to use this tool. : : The next time you try, could you please capture the problems : you are having in a bug report on kernel-package, please? We can only : get improvements in the code if such feedback is available. Package: [EMAIL PROTECTED] Version: 19710827 Severity: Wishlist Package fails to spend adequate time reading documentation :) I'm sure there's bugs since it's software, but that's not the problem I'm having just to lazy to RTFM, as I have another way to do what I need. -Jon
Re: Compiling kernels
On 6 Nov 2000, David Z. Maze wrote: Timo Benk [EMAIL PROTECTED] writes: TB Hi, TB On Mon, 6 Nov 2000, Matthew Sackman wrote: MS The problem is that my kernels refuse to install. I have [snip -- non-deb kernel compile sequence -- ] David M. answers: It's far easier and cleaner to install the Debian kernel-package package, untar the kernel source tarball, configure it with your favorite variant on 'make config', and then run 'make-kpkg buildpackage' to build Debian source, headers, documentation, and kernel image packages from the source tree. Installing the image package will prompt you to run lilo. If you decide you want a new/different/better kernel, you can just install a different package. If you decide you don't want the one you've installed, you can remove it as you would any other Debian package. Having got good answers here to other less-than-knowledgable questions before, I proceed to ask a horribly newbie question: You say that installing the kernel package will ... prompt you to run lilo... Do I assume correctly: I have to modify /etc/lilo.conf, that is, the installation does not do this for me? (It has been a while since I built a kernel.) --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I hope this is all of the above.)
Re: Compiling kernels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Nov 2000, David Teague wrote: You say that installing the kernel package will ... prompt you to run lilo... Do I assume correctly: I have to modify /etc/lilo.conf, that is, the installation does not do this for me? (It has been a while since I built a kernel.) AFAIK, the installation doesn't really do this indeed. In my case, I don't use a symlinked kernel, so I have to manually edit /etc/lilo.conf each time I change from kernel version (eg from 2.2.16 to 2.2.17), but not when I recompile the same kernel version because I was stupid enough to forget to check some break_all_if_you_forget_this checkbox. - -- Working with Julie Andrews is like getting hit over the head with a valentine. -- Christopher Plummer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Made with pgp4pine iEYEARECAAYFAjoICW8ACgkQjGz8qD1yPRAngQCgyI5HOseY26UUDfmB1G39MULl QJIAn1K2jeI51ClyUyaamLWkJXbKA0LY =mLvr -END PGP SIGNATURE-
Re: Compiling kernels
On Monday 06 November 2000 22:57, Matthew Sackman wrote: snips Thank you so much for this info: /usr/doc/kernel-package/README (and other files) give NO info regarding this 'make-kpkg buildpackage'. The man pages only briefly mention it. I'll let you know whether this works or not! Yeah - it has worked: using a make-kpkg buildpackage, then installing the new kernel source, kernel headers and finally kernel image still produced unresolved symbols, but the reboot (when I think I read a make depmod is run) rebooted properly and there were no kernel panics. However, there does seem to still be a problem with the module: running an 'update-modules' followed by 'modconf' lists NO modules being present. I assume therefore that the module system has altered slightly (though this worked under 2.4.0-test5). I am using the lastest (2.3.19-1) version of modutils, but this problem won't go away. However, the modules are still being loaded properly, but I simply have to edit the /etc/modules file by hand. Does anyone else have this problem? And if so, has anyone managed to resolve it? Oh, and of course, may I thank everyone who responded to my last problem and helped me fix it - thanks are indeed due. Matthew -- Using intelligent power: RISC OS, Be OS, Debian Linux Enjoying computing.
Compiling kernels
Dear all! I've possibly asked this one before but have not got any where, and am still puzzeled as to how to dort this one out! The problem is that my kernels refuse to install. I have downloaded the kernels from ftp.kernel.org, unpacked them. Configured them using menuconfig, and then cleaned using make-kpkg clean. I then compile using make-kpkg --revision-custom.1.0 kernel_image as per the instructions. Then I use dpkg -i kernel-imagedeb When installing, I get unresolved symbols on EVERY module that is to be installed. Upon looking inside the modules I can see nothing that references any files that don't exist and so am left wondering what on earth is going wrong. The last kernel that I was able to compile was 2.4.0-test5, which was available as a .deb in the woody dist, and what I am currently using. I'm therefore wondering whether there is some action I need to perform on the downloaded sources to prepare them for comilation using kpkg. I hope someone somewhere could help me out here. Matthew -- Using intelligent power: RISC OS, Be OS, Debian Linux Enjoying computing.
Re: Compiling kernels
Hi, On Mon, 6 Nov 2000, Matthew Sackman wrote: The problem is that my kernels refuse to install. I have downloaded the kernels from ftp.kernel.org, unpacked them. Configured them using menuconfig, If I understand you right you downloaded a tarball from kernel.org and no deb file. If so you have to do a: make dep mek modules make modules_install make bzImage and then run lilo with the new kernel image or just run make bzlilo instead of make bzImage as the last command. Good Luck, Timo[EMAIL PROTECTED] -- .-'~~~-. .'o oOOOo`. | Timo Benk ;~~~-.oOo o`. | Germany `. \ ~-. oOOo. | Registered Linux User #186431 `.; / ~. OO: | .' ;-- `.o.' | ,' ; ~~--'~ | Fax/Voicemail:+49891488214215 ; ;| _\\;_\\//_
Re: Compiling kernels
Timo Benk [EMAIL PROTECTED] writes: TB Hi, TB On Mon, 6 Nov 2000, Matthew Sackman wrote: MS The problem is that my kernels refuse to install. I have MS downloaded the kernels from ftp.kernel.org, unpacked MS them. Configured them using menuconfig, TB If I understand you right you downloaded a tarball from kernel.org and no TB deb file. If so you have to do a: TB make dep TB mek modules TB make modules_install TB make bzImage It's far easier and cleaner to install the Debian kernel-package package, untar the kernel source tarball, configure it with your favorite variant on 'make config', and then run 'make-kpkg buildpackage' to build Debian source, headers, documentation, and kernel image packages from the source tree. Installing the image package will prompt you to run lilo. If you decide you want a new/different/better kernel, you can just install a different package. If you decide you don't want the one you've installed, you can remove it as you would any other Debian package. -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: Compiling kernels
On Monday 06 November 2000 20:25, David Z. Maze wrote: Timo Benk [EMAIL PROTECTED] writes: TB Hi, TB On Mon, 6 Nov 2000, Matthew Sackman wrote: MS The problem is that my kernels refuse to install. I have MS downloaded the kernels from ftp.kernel.org, unpacked MS them. Configured them using menuconfig, TB If I understand you right you downloaded a tarball from kernel.org and no TB deb file. If so you have to do a: TB make dep TB mek modules TB make modules_install TB make bzImage It's far easier and cleaner to install the Debian kernel-package package, untar the kernel source tarball, configure it with your favorite variant on 'make config', and then run 'make-kpkg buildpackage' to build Debian source, headers, documentation, and kernel image packages from the source tree. Installing the image package will prompt you to run lilo. If you decide you want a new/different/better kernel, you can just install a different package. If you decide you don't want the one you've installed, you can remove it as you would any other Debian package. Thank you so much for this info: /usr/doc/kernel-package/README (and other files) give NO info regarding this 'make-kpkg buildpackage'. The man pages only briefly mention it. I'll let you know whether this works or not! With thanks, Matthew -- Using intelligent power: RISC OS, Be OS, Debian Linux Enjoying computing.
Re: Compiling kernels
On Sun, 11 Jun 2000, Henrique M Holschuh wrote: This seems to work ok - SMP is enabled and the SCSI controller works - but during the load process, immediately after Calculating module dependencies I get a lot of insmod *** unresolved symbols in lib/modules/x.x.x/misc/abcde messages displayed. I haven't been able to This is some crap with the timestamps and limitiations of depmod, I think. Run depmod -a as root to fix. Or just ignore it. I wonder what I was thinking when I wrote that. Bleargh, need more coffee. Of course, the answer is: before installing a new kernel, move the old modules dir somewhere else (or erase it). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
Compiling kernels
Hello list, I need to compile my own kernels to enable SMP and get SCSI support for my card so, after consulting the HOWTO and reading some recent postings about kernel compiling, what I've been doing is: 1. Rename/move my existing (/usr/src/) kernel-source-x.x.x, kernel-headers-x.x.x and linux directories, and kernel-source.x.x.x.tar.bz2 file. 2. Rename/move my existing /boot/bzImage and /boot/System.map 3. Install the kernel-source and kernel-headers packages (currently 2.2.15-2), creating a new /usr/src/kernel-headers-x.x.x directory and a kernel-source-x.x.x.tar.bz2 file 4. Unpack the kernel-source.x.x.x.tar.bz2 using bzcat kern*.bz2 | tar xvf - to create a new kernel-source-x.x.x directory. 5. Copy the new kernel-source-x.x.x directory to a new linux directory - /usr/src/linux 6. cd into /usr/src/linux 7. make clean 8. make xconfig 9. make dep 10. make bzImage 11. make modules 12. make modules_install 13. Copy /usr/src/linux/arch/i386/boot/bzImage to /boot and the DOS partition where I use loadlin. 14. Copy /usr/src/linux/System.map to /boot/System.map This seems to work ok - SMP is enabled and the SCSI controller works - but during the load process, immediately after Calculating module dependencies I get a lot of insmod *** unresolved symbols in lib/modules/x.x.x/misc/abcde messages displayed. I haven't been able to find a log in /var/log/ that shows these messages and they go by pretty quick, but they all appear to refer to stuff that I didn't select when I went through the make xconfig step, like irda and floppy tape. Other than that, the kernel seems stable and works ok, but I'm obviously doing something wrong. Also, I've heard that gcc 2.95 shouldn't be used for compiling kernels - I've got both 2.95 and 2.7.2 installed - how do I specify that gcc 2.7.2 should be used instead of 2.95, which I assume is being used - I can't see any versions displayed when I run the makes so I'm not sure and the HOWTO didn't say anything (I think it was for older kernels anyway and probably out of date for 2.2) TIA LeeE -- http://www.spatial.freeserve.co.uk ...or something
Re: Compiling kernels
Hi Lee! On Mon, 12 Jun 2000, Lee Elliott wrote: Hello list, I need to compile my own kernels to enable SMP and get SCSI support for my card so, after consulting the HOWTO and reading some recent postings about kernel compiling, what I've been doing is: Install fakeroot, kernel-package, any other dependencies... and be happy. It's MUCH easier than the non-Debian way you've been enployoing so far... :-) 1. Rename/move my existing (/usr/src/) kernel-source-x.x.x, kernel-headers-x.x.x and linux directories, and kernel-source.x.x.x.tar.bz2 file. Not needed. 2. Rename/move my existing /boot/bzImage and /boot/System.map Not needed. 3. Install the kernel-source and kernel-headers packages (currently 2.2.15-2), creating a new /usr/src/kernel-headers-x.x.x directory and a kernel-source-x.x.x.tar.bz2 file Not needed, unless you want backup copies or something. You don't need the kernel-headers package either, that's for other uses, not compiling a kernel. 4. Unpack the kernel-source.x.x.x.tar.bz2 using bzcat kern*.bz2 | tar xvf - to create a new kernel-source-x.x.x directory. Ok. 5. Copy the new kernel-source-x.x.x directory to a new linux directory - /usr/src/linux Or just symlink linux - kernel-source-x.x.x 6. cd into /usr/src/linux Ok. 7. make clean make-kpkg clean 8. make xconfig or make menuconfig, or whatever. But ok. 9. make dep 10. make bzImage 11. make modules 12. make modules_install Nope. fakeroot make-kpkg --revision=3:local.kernel.version.1.0 kernel_image fakeroot make-kpkg modules_image (or something to that effect. Read the /usr/share/doc/kernel-package stuff to get the right way) 13. Copy /usr/src/linux/arch/i386/boot/bzImage to /boot and the DOS partition where I use loadlin. Nope. Just dpkg -i the debs generated by make-kpkg in the /usr/src directory. 14. Copy /usr/src/linux/System.map to /boot/System.map Not needed. This seems to work ok - SMP is enabled and the SCSI controller works - but during the load process, immediately after Calculating module dependencies I get a lot of insmod *** unresolved symbols in lib/modules/x.x.x/misc/abcde messages displayed. I haven't been able to This is some crap with the timestamps and limitiations of depmod, I think. Run depmod -a as root to fix. Or just ignore it. Also, I've heard that gcc 2.95 shouldn't be used for compiling kernels - I've got both 2.95 and 2.7.2 installed - how do I specify that gcc 2.7.2 should be used instead of 2.95, which I assume is being used - I can't Edit the kernel main makefile in /usr/src/linux/Makefile, look for CC=, and change gcc to gcc272. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
Re: Compiling kernels
I've compiled umpteen kernels with 2.95, don't know what that fuss is about. As for the errors, I thought the make clean came after the make modules, make modules_install. I was under the impression that the order went: make menuconfig (or xconfig etc) make dep make modules make modules_install make clean make bzImage make bzlilo Funnily enough following this procedure gives me no problems whatsoever, except for the fact that it shows up as #2 even though ive done this process once :) What part of these 'makes' increments the rev. number I wonder. Anyway I suggest do a make clean again, clean is meant to remove the redundant stuff after a make modules, iirc. Cheers, Corey Popelier http://members.dingoblue.net.au/~pancreas Work Email: [EMAIL PROTECTED] On Mon, 12 Jun 2000, Lee Elliott wrote: Hello list, I need to compile my own kernels to enable SMP and get SCSI support for my card so, after consulting the HOWTO and reading some recent postings about kernel compiling, what I've been doing is: 1. Rename/move my existing (/usr/src/) kernel-source-x.x.x, kernel-headers-x.x.x and linux directories, and kernel-source.x.x.x.tar.bz2 file. 2. Rename/move my existing /boot/bzImage and /boot/System.map 3. Install the kernel-source and kernel-headers packages (currently 2.2.15-2), creating a new /usr/src/kernel-headers-x.x.x directory and a kernel-source-x.x.x.tar.bz2 file 4. Unpack the kernel-source.x.x.x.tar.bz2 using bzcat kern*.bz2 | tar xvf - to create a new kernel-source-x.x.x directory. 5. Copy the new kernel-source-x.x.x directory to a new linux directory - /usr/src/linux 6. cd into /usr/src/linux 7. make clean 8. make xconfig 9. make dep 10. make bzImage 11. make modules 12. make modules_install 13. Copy /usr/src/linux/arch/i386/boot/bzImage to /boot and the DOS partition where I use loadlin. 14. Copy /usr/src/linux/System.map to /boot/System.map This seems to work ok - SMP is enabled and the SCSI controller works - but during the load process, immediately after Calculating module dependencies I get a lot of insmod *** unresolved symbols in lib/modules/x.x.x/misc/abcde messages displayed. I haven't been able to find a log in /var/log/ that shows these messages and they go by pretty quick, but they all appear to refer to stuff that I didn't select when I went through the make xconfig step, like irda and floppy tape. Other than that, the kernel seems stable and works ok, but I'm obviously doing something wrong. Also, I've heard that gcc 2.95 shouldn't be used for compiling kernels - I've got both 2.95 and 2.7.2 installed - how do I specify that gcc 2.7.2 should be used instead of 2.95, which I assume is being used - I can't see any versions displayed when I run the makes so I'm not sure and the HOWTO didn't say anything (I think it was for older kernels anyway and probably out of date for 2.2) TIA LeeE -- http://www.spatial.freeserve.co.uk ...or something -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Compiling kernels
On Mon, Jun 12, 2000 at 12:41:21AM +0100, Lee Elliott wrote: This seems to work ok - SMP is enabled and the SCSI controller works - but during the load process, immediately after Calculating module dependencies I get a lot of insmod *** unresolved symbols in lib/modules/x.x.x/misc/abcde messages displayed. I haven't been able to There are probably old modules that you are no longer using lying around in the /lib/modules/x.x.x/ tree. I found that removing (or renaming) the existing directory stops these errors. Apart from this, I would recommend using kernel-package as this allows the package management system to know what's going on. Cheers, Tom -- Please, won't somebody tell me what diddie-wa-diddie means? pgpYNWPbwXzDg.pgp Description: PGP signature
errors in sources while compiling Kernels
Hi,
I just tried to compile a Kernel from source (2.0.34 from my hamm-
distribution) and there were errors in the source code:
/usr/src/linux/arch/i368/kernel/ptrace.c (Line 87):
static unsigned long get_long(struct task_struct * tsk,
struct vm_area_struct * vma, unsigned long addr
{
^
As you'll notice, there's a closing bracket missing.___|
What makes it interesting, the last time I compiled the
kernel was only some days ago, without any error, _and_
it isn't the first time I encountered one-letter-errors
in the sources.
Any ideas what causes this?
Just in case you'll ask, yes, chkdsk found some errors recently,
but I don't remember errors the other times, and the kernel sources
seem to be the only place where I get problems.
thanks in advance,
Ingo
--
Of course, just because we've heard a spine-chilling, blood-curdling
scream of the sort to make your very marrow freeze in your bones doesn't
automatically mean there's anything wrong.
-- (Terry Pratchett, Soul Music)
Compiling kernels
Hello. Is any one here a kernel guru? I posted a problem a couple of times this week that no one seems to be able to help me with. Is there much difference in success and error when using xconfig and the other make options? I tried using xconfig to rebuild my kernel for sound. I'm sure added support for both network and sound and I also compiled the modules but now I no longer have either working. I'm also unsure as to how to bring back the original version of the kernel (I'm currently using my boot disk. TIA Cristov [EMAIL PROTECTED]
Re: Compiling kernels
Cristov Russell hat gesagt: // Cristov Russell wrote: Is any one here a kernel guru? I posted a problem a couple of times this week that no one seems to be able to help me with. Is there much difference in success and error when using xconfig and the other make options? I tried using xconfig to rebuild my kernel for sound. I'm sure added support for both network and sound and I also compiled the modules but now I no longer have either working. I'm also unsure as to how to bring back the original version of the kernel (I'm currently using my boot disk. While I am no kernel guru: To bring back the original kernel try to reinstall the kernel image that came with your distribution with # dpkg --install kernel-image???.deb Did you use make-kpkg from the kernel-package to build your kernel? If not, please do so. Read /usr/doc/kernel-package/README.gz It makes no difference what kind of config method you use. If you have X, use make xconfig. To get sound working you might have to setup your card with isapnp at boot time if it is a plug'n'play card. Refer to the SOUND-Howto for this. -- ____ Frank Barknecht __ __ trip\ \ / /wire __ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / / / / / // // /\ \\ ___\\ \ /_/ /_/ /_/ /_//_// / \ \\_\\_\ /_/\_\
Re: Compiling kernels
On Tue, Nov 10, 1998 at 11:40:42PM -0600, Cristov Russell wrote: Hi Cristov Is any one here a kernel guru? I posted a problem a couple of times this I'm not a kernel guru, maybe I can help You there 2 ways to build a kernel, the traditionell cd /usr/src/linux Steps: 1. make xconfig, ore make menuconfig, or make config 2. make dep 3. make clean 4. make zImage, or make bzImage (if kernel 512 kb) 5. make modules 6. make modules_install 7. depmod -a 8. make zlilo You can combine these steps to one line, e.g. make dep clean zImage modules modules_install zlilo the other, more up-to-date way is using the kernelpackage cd /usr/src/linux Steps(I filled in example building): make xconfig make-kpkg clean moke-kpkg --rootcmd --revision=custom.1.0.kernel_image dpkg -i ../kernel-image-2.0.35_custom.1.0_i386.deb this is more comfortable depmod -a is called automatically and Your kernel is known by the package list But, You must have the kernel-package installed before usage. actually is kernel-package_5_12.deb you can get it from `www.debian.org' by following the download guide to the development package For further use its always a good idea to have one running kernel added in '/etc/lilo.conf' e.g. # Start LILO global Section boot=/dev/sda2 install=/boot/boot.b map=/boot/map vga=normal prompt delay=20 read-only # End LILO global section image=/vmlinuz root=/dev/sda7 append=mem=128M label=Linux # Linux bootable partition config begins image = /vmlinuz.old root = /dev/sda7 label = old # Linux bootable partition config ends # # DOS bootable partition config begins other = /dev/sda1 label = dos table = /dev/sda2 # DOS bootable partition config ends # # end of '/etc/lilo.conf' than You can at boot prompt LILO: LILO: old and the old kernel comes up that makes, for me, installing a new kernel not never can get a 'nightmare' hope it helps, my english is very rudimentary, sorry -- Wis You all the very best Peter
Re: Compiling kernels
Is any one here a kernel guru? I posted a problem a couple of times this week that no one seems to be able to help me with. Is there much difference in success and error when using xconfig and the other make options? I tried I use make menuconfig, xconfig just wouldn't run for me. using xconfig to rebuild my kernel for sound. I'm sure added support for both network and sound and I also compiled the modules but now I no longer have either working. I'm also unsure as to how to bring back the original version of the kernel (I'm currently using my boot disk. You can copy the kernel from bootdisk to /vmlinuz, and re-run lilo. when you made modules - did you run make modules, make modules install and depmod -a ? Try setting up without modules, the modules have some extra steps that could confuse you. Experiment with modules when the other stuff is ok again. Helge Hafting
Error compiling kernels (2.0 and 2.1) with upgraded bo-hamm
Hi, I would like to know if someone knows what can cause the following error in the linker while building a kernel (2.0 or 2.1), but no while building apps Any comment will be greatly appreciated, regards Ulisses make[1]: Leaving directory `/root/kernel/linux/arch/i386/mm' make[1]: Entering directory `/root/kernel/linux/arch/i386/lib' make all_targets make[2]: Entering directory `/root/kernel/linux/arch/i386/lib' make[2]: Nothing to be done for `all_targets'. make[2]: Leaving directory `/root/kernel/linux/arch/i386/lib' make[1]: Leaving directory `/root/kernel/linux/arch/i386/lib' ld -m elf_i386 -Ttext 0x10 -e stext arch/i386/kernel/head.o init/main.o init/version.o \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o net/network.a \ fs/filesystems.a \ drivers/block/block.a drivers/char/char.a drivers/net/net.a drivers/scsi/scsi.a drivers/pci/pci.a \ /root/kernel/linux/arch/i386/lib/lib.a /root/kernel/linux/lib/lib.a /root/kernel/linux/arch/i386/lib/lib.a -o vmlinux init/main.o(.data+0xf8): undefined reference to `ncr53c8xx_setup' arch/i386/kernel/kernel.o(.data+0x70): undefined reference to `sys_fork' arch/i386/kernel/kernel.o(.data+0x94): undefined reference to `sys_execve' arch/i386/kernel/kernel.o(.data+0x248): undefined reference to `sys_clone' arch/i386/kernel/kernel.o(.data+0x930): undefined reference to `dump_thread' arch/i386/kernel/kernel.o(.data+0x938): undefined reference to `dump_fpu' kernel/kernel.o: In function `do_fork': kernel/kernel.o(.text+0x21a6): undefined reference to `copy_thread' kernel/kernel.o: In function `release': kernel/kernel.o(.text+0x4ffd): undefined reference to `release_thread' kernel/kernel.o: In function `do_exit': kernel/kernel.o(.text+0x5834): undefined reference to `exit_thread' fs/fs.o: In function `flush_old_exec': fs/fs.o(.text+0x8689): undefined reference to `flush_thread' fs/fs.o: In function `elf_core_dump': fs/fs.o(.text+0xf544): undefined reference to `dump_fpu' fs/fs.o: In function `aout_core_dump': fs/fs.o(.text+0xfb3b): undefined reference to `dump_thread' drivers/char/char.a(keyboard.o): In function `show_ptregs': keyboard.o(.text+0x683): undefined reference to `show_regs' drivers/scsi/scsi.a(hosts.o)(.data+0x18): undefined reference to `ncr53c8xx_detect' drivers/scsi/scsi.a(hosts.o)(.data+0x28): undefined reference to `ncr53c8xx_queue_command' drivers/scsi/scsi.a(hosts.o)(.data+0x2c): undefined reference to `ncr53c8xx_abort' drivers/scsi/scsi.a(hosts.o)(.data+0x30): undefined reference to `ncr53c8xx_reset' make: *** [vmlinux] Error 1 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
