Re: strange error compiling kernel 4.19.0-6-amd64
John Covici wrote: > I am trying to do something very simple, with the config file supplied > from Debian, I need to do a make bzImage and possible a make modules, > how can dI do this? Do I need to change the config in some way in > order to do this? be patient and start reading - free means free to understand and this means read a lot. see my other answer below
Re: strange error compiling kernel 4.19.0-6-amd64
On Mon, 30 Sep 2019 16:47:29 -0400, deloptes wrote: > > John Covici wrote: > > > Google did not give me that at all. I am not trying to build a Debian > > package,just trying to compile the kernel. > > Then just do > > make deb-pkg > > You could read more about the make system used by the kernel > > https://www.kernel.org/doc/html/latest/ > > or in the directory > > $ less README > > so according Documentation/kbuild/kbuild.txt > > KBUILD_DEBARCH > -- > For the deb-pkg target, allows overriding the normal heuristics deployed by > deb-pkg. Normally deb-pkg attempts to guess the right architecture based on > the UTS_MACHINE variable, and on some architectures also the kernel config. > The value of KBUILD_DEBARCH is assumed (not checked) to be a valid Debian > architecture. I am trying to do something very simple, with the config file supplied from Debian, I need to do a make bzImage and possible a make modules, how can dI do this? Do I need to change the config in some way in order to do this? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: strange error compiling kernel 4.19.0-6-amd64
John Covici wrote: > I am doing a straight makebzImage not trying to build a deb package. > In Debian 9, I could do this with no problem. Obviously you are trying to build the kernel from debian source. You have to use the original source, without the debian directory. IF there is debian directory, it means you decided to use the Debian way. I do not know how this code is set up, but if you download the kernel from kernel.org, you should not be getting this message. Otherwise the link I posted before gives a solution to the problem -quote- Using your current Debian kernel configuration as a starting point Alternatively, you can use the configuration from a Debian-built kernel that you already have installed by copying the /boot/config-* file to .config and then running make oldconfig to only answer new questions. If you do this, ensure that you modify the configuration to set: CONFIG_SYSTEM_TRUSTED_KEYS = "" -quote-
Re: strange error compiling kernel 4.19.0-6-amd64
John Covici wrote: > Google did not give me that at all. I am not trying to build a Debian > package,just trying to compile the kernel. Then just do make deb-pkg You could read more about the make system used by the kernel https://www.kernel.org/doc/html/latest/ or in the directory $ less README so according Documentation/kbuild/kbuild.txt KBUILD_DEBARCH -- For the deb-pkg target, allows overriding the normal heuristics deployed by deb-pkg. Normally deb-pkg attempts to guess the right architecture based on the UTS_MACHINE variable, and on some architectures also the kernel config. The value of KBUILD_DEBARCH is assumed (not checked) to be a valid Debian architecture.
Re: strange error compiling kernel 4.19.0-6-amd64
On Mon, Sep 30, 2019 at 04:20:53PM -0400, John Covici wrote: > > On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote: > > > So, how do I turn this off so I can compile the thing? > > > > "dpkg-buildpackage -b" considers it a warning and skips it. > > At least it does so for me. > > I am doing a straight makebzImage not trying to build a deb package. > In Debian 9, I could do this with no problem. Two choices here: 1) Do it Debian way, which works. Different version, different rules, and all that. 2) Persisting in your current way, which does not. I leave a final choice to you. Reco
Re: strange error compiling kernel 4.19.0-6-amd64
On Mon, 30 Sep 2019 16:05:16 -0400, deloptes wrote: > > John Covici wrote: > > > debian/certs/debian-uefi-certs.pem > > https://wiki.debian.org/BuildADebianKernelPackage > > I hope you can read - also find a good search engine - first hit > > Google did not give me that at all. I am not trying to build a Debian package,just trying to compile the kernel. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: strange error compiling kernel 4.19.0-6-amd64
On Mon, 30 Sep 2019 16:15:38 -0400, Reco wrote: > > Please do not top post. > > On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote: > > So, how do I turn this off so I can compile the thing? > > "dpkg-buildpackage -b" considers it a warning and skips it. > At least it does so for me. I am doing a straight makebzImage not trying to build a deb package. In Debian 9, I could do this with no problem. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: strange error compiling kernel 4.19.0-6-amd64
Please do not top post. On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote: > So, how do I turn this off so I can compile the thing? "dpkg-buildpackage -b" considers it a warning and skips it. At least it does so for me. Reco
Re: strange error compiling kernel 4.19.0-6-amd64
So, how do I turn this off so I can compile the thing? On Mon, 30 Sep 2019 16:02:02 -0400, Reco wrote: > > Hi. > > On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote: > > Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64. > > > > CC kernel/rseq.o > > AR kernel/built-in.a > > make[1]: *** No rule to make target > > 'debian/certs/debian-uefi-certs.pem', needed by > > 'certs/x509_certificate_list'. Stop. > > > > What package do I need to fix this problem? > > It fails at signing your kernel by Debian CA key. They don't provide it > by any package as it would beat the primary purpose of Restricted Boot > (Secure Boot in M$ speak). > > > > Thanks in advance for any suggestions. > > Follow [1]. > > Reco > > [1] > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: strange error compiling kernel 4.19.0-6-amd64
John Covici wrote: > debian/certs/debian-uefi-certs.pem https://wiki.debian.org/BuildADebianKernelPackage I hope you can read - also find a good search engine - first hit
Re: strange error compiling kernel 4.19.0-6-amd64
On 2019-09-30 15:46 -0400, John Covici wrote: > Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64. > > CC kernel/rseq.o > AR kernel/built-in.a > make[1]: *** No rule to make target > 'debian/certs/debian-uefi-certs.pem', needed by > 'certs/x509_certificate_list'. Stop. > > What package do I need to fix this problem? The linux-config-4.19 package[1], it "contains the configuration files used to build the official Debian kernel files, but without references to Debian's signing certificates." HTH, Sven 1. https://packages.debian.org/buster/linux-config-4.19
Re: strange error compiling kernel 4.19.0-6-amd64
Hi. On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote: > Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64. > > CC kernel/rseq.o > AR kernel/built-in.a > make[1]: *** No rule to make target > 'debian/certs/debian-uefi-certs.pem', needed by > 'certs/x509_certificate_list'. Stop. > > What package do I need to fix this problem? It fails at signing your kernel by Debian CA key. They don't provide it by any package as it would beat the primary purpose of Restricted Boot (Secure Boot in M$ speak). > Thanks in advance for any suggestions. Follow [1]. Reco [1] https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
strange error compiling kernel 4.19.0-6-amd64
Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64. CC kernel/rseq.o AR kernel/built-in.a make[1]: *** No rule to make target 'debian/certs/debian-uefi-certs.pem', needed by 'certs/x509_certificate_list'. Stop. What package do I need to fix this problem? Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: Jessie, problem compiling kernel 4.3
I spoke too soon, someone in the ubuntu forums had the same problem, installed libssl-dev and it worked. Sorry to trouble y'all. Curt- On Fri, Nov 6, 2015 at 3:06 PM, Curt Howlandwrote: > So, there I was, doing a compile of the new kernel, 4.3 > > I get the following interesting error: > > === > scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file > or directory > #include > ^ > compilation terminated. > === > > I'm accustomed to getting compile time errors that "You have no > certs!", this is the first time this has failed. (4.2.5 compiled just > fine, for example) > > Searching has turned nothing up, am I the only person having this problem? > > Curt- > > > -- > The secret of happiness is freedom, > and the secret of freedom is courage. > - Thucydides -- The secret of happiness is freedom, and the secret of freedom is courage. - Thucydides
Jessie, problem compiling kernel 4.3
So, there I was, doing a compile of the new kernel, 4.3 I get the following interesting error: === scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory #include ^ compilation terminated. === I'm accustomed to getting compile time errors that "You have no certs!", this is the first time this has failed. (4.2.5 compiled just fine, for example) Searching has turned nothing up, am I the only person having this problem? Curt- -- The secret of happiness is freedom, and the secret of freedom is courage. - Thucydides
Re: Compiling kernel from Github - Howto?
csanyi...@gmail.com writes: Gary Dale garyd...@torfree.net writes: On 17/01/15 10:19 AM, csanyi...@gmail.com wrote: I have a headless powerpc box and run on it Debian Wheezy with kernel Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux . But this kernel doesn't have support for the rtl8192cu kernel-module. One can to get the kernel source from here: https://github.com/Excito/community-b3-kernel . I did so with the command: git clone https://github.com/Excito/community-b3-kernel.git I get the community-b3-kernel/ directory with a lot of subdirectories, so I actually don't know where to find the directory with the 3.2.62-1 kernel source? I think so so one can run int the root directory ( in this case it is community-b3-kernel/ directory ) the following command: make menuconfig but then I get the menuconfig with the header: .config - Linux/powerpc 3.2.63 Kernel Configuration This is not the right kernel source for me, what I want. If I run the command: git tag -l I get: debian/1%3.2.62-1 upstream/3.2.62 upstream/3.2.63 I think what I want is compiling the debian/1%3.2.62-1 kernel. In this case what should I do to get the right debian-3.2.62-1 kernel? -- Regards, from Pál -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87r3unum8e@gmail.com
Re: Compiling kernel from Github - Howto?
On 17/01/15 10:19 AM, csanyi...@gmail.com wrote: Hi, I have a headless powerpc box and run on it Debian Wheezy with kernel Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux . But this kernel doesn't have support for the rtl8192cu kernel-module. One can to get the kernel source from here: https://github.com/Excito/community-b3-kernel . I did so with the command: git clone https://github.com/Excito/community-b3-kernel.git I get the community-b3-kernel/ dorectory with a lot of subdirectories, so I actually don't know where to find the directory with the 3.2.62-1 kernel source? If I can find it, from there I can compile the kernel with the wnated module. Any advices will be appreciated! -- Regards, from Pál Before compiling a custom kernel, I'd check with RealTek to see if they have a package for Debian that you can install. I note that https://packages.debian.org/squeeze-backports/firmware-realtek has realtek 8192 support back to Squeeze. Are you really lacking the driver or just the (non-free) firmware? Realtek have a driver at http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=48PFid=48Level=5Conn=4DownTypeID=3GetDown=falseDownloads=true#RTL8192CU but again, that seems to be for really old kernels. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54baaeef.4080...@torfree.net
Re: Compiling kernel from Github - Howto?
Gary Dale garyd...@torfree.net writes: On 17/01/15 10:19 AM, csanyi...@gmail.com wrote: I have a headless powerpc box and run on it Debian Wheezy with kernel Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux . But this kernel doesn't have support for the rtl8192cu kernel-module. One can to get the kernel source from here: https://github.com/Excito/community-b3-kernel . I did so with the command: git clone https://github.com/Excito/community-b3-kernel.git I get the community-b3-kernel/ dorectory with a lot of subdirectories, so I actually don't know where to find the directory with the 3.2.62-1 kernel source? If I can find it, from there I can compile the kernel with the wnated module. Any advices will be appreciated! Before compiling a custom kernel, I'd check with RealTek to see if they have a package for Debian that you can install. On my headless powrpc box with Wheezy system when I run: aptitude search firmware-realtek I get: i firmware-realtek So for my ZyXEL NWD2205 Wireless adapter I have installed the proper driver, right? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87egqswopg@gmail.com
Compiling kernel from Github - Howto?
Hi, I have a headless powerpc box and run on it Debian Wheezy with kernel Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux . But this kernel doesn't have support for the rtl8192cu kernel-module. One can to get the kernel source from here: https://github.com/Excito/community-b3-kernel . I did so with the command: git clone https://github.com/Excito/community-b3-kernel.git I get the community-b3-kernel/ dorectory with a lot of subdirectories, so I actually don't know where to find the directory with the 3.2.62-1 kernel source? If I can find it, from there I can compile the kernel with the wnated module. Any advices will be appreciated! -- Regards, from Pál -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87iog5v3ic@gmail.com
Re: Compiling kernel: problem!
The same problem, with kernel 3.10, was present with Wheezy 486 on same computer. Thanks Regards -- 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/1383828867.28226.yahoomail...@web133001.mail.ir2.yahoo.com
Re: Compiling kernel: problem!
The same problem, with kernel 3.10, was present with Wheezy 486 on same computer. Thanks Regards -- 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/1383829602.35782.yahoomail...@web133001.mail.ir2.yahoo.com
Compiling kernel: problem!
Hi all I try compiling kernel 3.10 on Squeeze 6.0.7. with cpu Intel Centrino1 32bit. Unpack source in /usr/src, and: adduser user src chown -R root:src /usr/src chmod -R g+w /usr/src cp /boot/config-`uname -r` ./.config make menuconfig, but don't change any! make deb-pkg After finishid, 4 file.deb is present: linux-image-3.10.0_3.10.0-1_i386.deb linux-headers-3.10.0_3.10.0-1_i386.deb linux-firmware-image_3.10.0-1_i386.deb linux-libc-dev_3.10.0-1_i386.deb After installed file.deb and reboot, the hard disk change letters! from sda1 to hda1. From console, the command: fdisk -l, blkid and mount, is very slow! What could be the problem? Thanks Regards -- 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/02B29CDA5B7B41CFABD6277BC9F3F856@CentrinoDuo
Re: Compiling kernel: problem!
On Wed, 06 Nov 2013 15:07:58 -0500 (EST), Antispammbox-debian wrote: Hi all I try compiling kernel 3.10 on Squeeze 6.0.7. with cpu Intel Centrino1 32bit. Unpack source in /usr/src, and: adduser user src chown -R root:src /usr/src chmod -R g+w /usr/src cp /boot/config-`uname -r` ./.config make menuconfig, but don't change any! make deb-pkg After finishid, 4 file.deb is present: linux-image-3.10.0_3.10.0-1_i386.deb linux-headers-3.10.0_3.10.0-1_i386.deb linux-firmware-image_3.10.0-1_i386.deb linux-libc-dev_3.10.0-1_i386.deb After installed file.deb and reboot, the hard disk change letters! from sda1 to hda1. From console, the command: fdisk -l, blkid and mount, is very slow! What could be the problem? Thanks Regards You're not having a problem compiling the kernel, you're having a problem running the kernel. It sounds to me like the compiling went just fine. Your subject line is misleading. I know a few things about compiling kernels, but I've never heard of these specific usage problems. I am currently using a custom 3.10 kernel on an up-to-date jessie system with no problems. Perhaps the new kernel requires a newer release of other software, such as udev or initramfs-tools, than you currently have on your squeeze system. -- .''`. 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/1192128197.242564.1383778158749.javamail.r...@md01.wow.synacor.com
Re: Compiling kernel took a lot of disk space.
Sorry, my mistake, nothing about 64 bit. I compiled the 32bit kernel in xfs. On Tue, Jun 29, 2010 at 9:17 AM, Magicloud Magiclouds magicloud.magiclo...@gmail.com wrote: I am using debian unstable 64 bit with lvm and ext3. All options are default. How did I find out? This OS is a VM. And the disk data is in a non-fixed size file, not compressed. Sorry I forgot how to say this in English, by non-fixed size, I mean the VM software just allocate the actual disk space that has data to write. And I think this is not just about ext3, but ext3 64bit. Because with the same environment, 32bit works fine for this process. On Mon, Jun 28, 2010 at 10:54 PM, H.S. hs.sa...@gmail.com wrote: On 27/06/10 10:51 PM, Magicloud Magiclouds wrote: Thank you guys. I have not follow Stephen's guide, but I figured the reason out. It seems like an ext3's fault. The space (i-node wise) was used 5.x GB, but the actual space (data wise) was used only 1 GB. So a lot of space was just empty and wasted. I experience the same thing some weeks ago (had to use a different machine with a larger hard disk to get the job done). It is interesting to note that you think that ext3 is at fault here. How did you find that out? I would like to know whether it is a problem with ext3 at this time in Unstable. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- 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/i0ad2n$of...@dough.gmane.org -- 竹密岂妨流水过 山高哪阻野云飞 -- 竹密岂妨流水过 山高哪阻野云飞 -- 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/aanlktilhsqtbguejpemtn3sqz6dylmpewwkog0pzh...@mail.gmail.com
Re: Compiling kernel took a lot of disk space.
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote: PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. That doesn't stop me from using my real name ;) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Compiling kernel took a lot of disk space.
On Monday 28 June 2010 08:44:15 Andrei Popescu wrote: On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote: PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. That doesn't stop me from using my real name ;) Nor me :-) (I am in fact from England - but my name isn't.) 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/201006281020.13426.lisi.re...@gmail.com
Re: Compiling kernel took a lot of disk space.
On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote: On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote: PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. That doesn't stop me from using my real name ;) Though English people have no problem pronouncing your name. So I guess we're still looking for an example of a non-English name that can't be pronounced right. Can't think of any. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- 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/20100628111214.gm17...@pear.tzafrir.org.il
Re: Compiling kernel took a lot of disk space.
Op 28-06-10 13:12, Tzafrir Cohen schreef: On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote: On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote: PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. That doesn't stop me from using my real name ;) Though English people have no problem pronouncing your name. So I guess we're still looking for an example of a non-English name that can't be pronounced right. Can't think of any. Well, each name *can* in principle be pronounced right. Yet, non-Dutch people have a hard time with my name. Sjoerd (pronounced a bit like 'should' with an r instead of an l. Somehow that's very difficult) signature.asc Description: OpenPGP digital signature
Re: Compiling kernel took a lot of disk space.
On Mon, 28 Jun 2010 07:20:05 -0400 (EDT), Sjoerd Hardeman wrote: Op 28-06-10 13:12, Tzafrir Cohen schreef: On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote: On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote: PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. That doesn't stop me from using my real name ;) Though English people have no problem pronouncing your name. So I guess we're still looking for an example of a non-English name that can't be pronounced right. Can't think of any. Well, each name *can* in principle be pronounced right. Yet, non-Dutch people have a hard time with my name. Sjoerd (pronounced a bit like 'should' with an r instead of an l. Somehow that's very difficult) These are all interesting points, but they are all irrelevant to e-mail. In an e-mail, one doesn't need to be able to pronounce a name. One only needs to be able to copy and paste. Thus, the justification of the use of a pseudonym on the grounds that other people can't pronounce it right is not a valid one for the e-mail media. My own name, Stephen, though an English name in an English-speaking country, and a name that appears in the Holy Bible, has often been mispronounced as Steffan instead of Steven. But I still use my real name in e-mails. -- .''`. 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/595260604.3985.1277731775384.javamail.r...@md01.wow.synacor.com
Re: Compiling kernel took a lot of disk space.
On Monday 28 June 2010 12:12:23 Tzafrir Cohen wrote: So I guess we're still looking for an example of a non-English name that can't be pronounced right. Can't think of any. It isn't a case of whether it can be correctly pronounced, but of whether it is. 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/201006281437.24877.lisi.re...@gmail.com
Re: Compiling kernel took a lot of disk space.
On 27/06/10 10:51 PM, Magicloud Magiclouds wrote: Thank you guys. I have not follow Stephen's guide, but I figured the reason out. It seems like an ext3's fault. The space (i-node wise) was used 5.x GB, but the actual space (data wise) was used only 1 GB. So a lot of space was just empty and wasted. I experience the same thing some weeks ago (had to use a different machine with a larger hard disk to get the job done). It is interesting to note that you think that ext3 is at fault here. How did you find that out? I would like to know whether it is a problem with ext3 at this time in Unstable. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- 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/i0ad2n$of...@dough.gmane.org
Re: Compiling kernel took a lot of disk space.
I am using debian unstable 64 bit with lvm and ext3. All options are default. How did I find out? This OS is a VM. And the disk data is in a non-fixed size file, not compressed. Sorry I forgot how to say this in English, by non-fixed size, I mean the VM software just allocate the actual disk space that has data to write. And I think this is not just about ext3, but ext3 64bit. Because with the same environment, 32bit works fine for this process. On Mon, Jun 28, 2010 at 10:54 PM, H.S. hs.sa...@gmail.com wrote: On 27/06/10 10:51 PM, Magicloud Magiclouds wrote: Thank you guys. I have not follow Stephen's guide, but I figured the reason out. It seems like an ext3's fault. The space (i-node wise) was used 5.x GB, but the actual space (data wise) was used only 1 GB. So a lot of space was just empty and wasted. I experience the same thing some weeks ago (had to use a different machine with a larger hard disk to get the job done). It is interesting to note that you think that ext3 is at fault here. How did you find that out? I would like to know whether it is a problem with ext3 at this time in Unstable. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- 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/i0ad2n$of...@dough.gmane.org -- 竹密岂妨流水过 山高哪阻野云飞 -- 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/aanlktimntolmfuaihy24esxdiqhcwv8ruue19taqo...@mail.gmail.com
Re: Compiling kernel took a lot of disk space.
Thank you guys. I have not follow Stephen's guide, but I figured the reason out. It seems like an ext3's fault. The space (i-node wise) was used 5.x GB, but the actual space (data wise) was used only 1 GB. So a lot of space was just empty and wasted. I attached another disk to get the job done. PS: Certainly this is not my real name. 8-) I am not from an English country. Some people cannot pronounce my name right. So I use this pseudonym. On Fri, Jun 25, 2010 at 10:02 PM, Stephen Powell zlinux...@wowway.com wrote: On Fri, 25 Jun 2010 09:34:29 -0400 (EDT), Jordan Metzmeier wrote: On 06/25/2010 09:10 AM, Stephen Powell wrote: That is not the correct command syntax. I suggest that you read http://www.wowway.com/~zlinuxman/Kernel.htm Kernel building in Debian is a complex task fraught with many perils, and this web page will help you avoid most of them. It's long and detailed, but if you follow this procedure you should do well. Looks like an excellent guide. Thanks for the work! You're welcome. The Debian kernel team doesn't particularly care for it, and if you you read it all the way through, particularly step 10, you can probably guess why. But Manoj Srivastava, author and maintainer of kernel-package, liked it well enough to include an earlier version of this web page in kernel-package itself. The above link, however, will always be the most current and up-to-date version of the document. I will probably update it again next week if the fix for Debian bug number 505609 is included in the stable point release for Lenny which is scheduled for this weekend. -- .''`. 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/182056374.282512.1277474554176.javamail.r...@md01.wow.synacor.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/aanlktimqrfiawrh_3lkn2z7a3s27gbhpmdwsztsjy...@mail.gmail.com
Compiling kernel took a lot of disk space.
Hi, I am using debian unstable 64. Recently I wanted to compile a 2.6.34 kernel. Well, the source package is 64MB. Before `make-kpkg linux-image linux-headers --initrd` finished, the source directory took 6GB space, made the volume full. Tried a few times, the problem is still there, and always the same. What should I do? Thanks. -- 竹密岂妨流水过 山高哪阻野云飞 -- 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/aanlktina_w71b1qu-kpkz8i4jtuez8he02hnsfe-i...@mail.gmail.com
Re: Compiling kernel took a lot of disk space.
On Fri, Jun 25, 2010 at 18:25, Magicloud Magiclouds magicloud.magiclo...@gmail.com wrote: Hi, I am using debian unstable 64. Recently I wanted to compile a 2.6.34 kernel. Well, the source package is 64MB. Before `make-kpkg linux-image linux-headers --initrd` finished, the source directory took 6GB space, made the volume full. Tried a few times, the problem is still there, and always the same. What should I do? Thanks. -- 竹密岂妨流水过 山高哪阻野云飞 -- 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/aanlktina_w71b1qu-kpkz8i4jtuez8he02hnsfe-i...@mail.gmail.com Where did you take your .config from? Normally if you did not take anything, it tries to take the running kernels configuration. The default configuration of debian contains nearly all supported hardware. You only require a very few portion of that tailored for your hardware. So use menuconfig/xconfig etc and fine tune the configuration before building.
Re: Compiling kernel took a lot of disk space.
On Fri, 25 Jun 2010 08:55:41 -0400 (EDT), Magicloud Magiclouds wrote: I am using debian unstable 64. Recently I wanted to compile a 2.6.34 kernel. Well, the source package is 64MB. Before `make-kpkg linux-image linux-headers --initrd` finished, the source directory took 6GB space, made the volume full. Tried a few times, the problem is still there, and always the same. What should I do? Thanks. Magicloud Magiclouds? That can't be your real name! Can't you give us your real name? At least a first name? That is not the correct command syntax. I suggest that you read http://www.wowway.com/~zlinuxman/Kernel.htm Kernel building in Debian is a complex task fraught with many perils, and this web page will help you avoid most of them. It's long and detailed, but if you follow this procedure you should do well. -- .''`. 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/1268464148.281075.1277471409102.javamail.r...@md01.wow.synacor.com
Re: Compiling kernel took a lot of disk space.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/25/2010 09:10 AM, Stephen Powell wrote: Magicloud Magiclouds? That can't be your real name! Can't you give us your real name? At least a first name? That is not the correct command syntax. I suggest that you read http://www.wowway.com/~zlinuxman/Kernel.htm Kernel building in Debian is a complex task fraught with many perils, and this web page will help you avoid most of them. It's long and detailed, but if you follow this procedure you should do well. Looks like an excellent guide. Thanks for the work! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJMJLBlAAoJEKj/C3qNthmTqc8QALJOM6eXWbeaK8SNpOggHHD0 v0tOMd8F6OYAAZXvGl5etJYEkQcEDyA4Y4oJYCfVWspLSiRP3jzQqzuoNE2vWZ4b 5eTypse830Owe61uzy2aGqqNHA9tueIONe2p5ThxRO8Do612paqtKYs6mQ7/7j0c S1ziPSWUy1rFhRxQJayM+1dJqyGoWxhPSO/Ud1TFRMsWU+n0VFHHm+No71aW/f5D SD7N6SULGA7wRTAU2KwRtHCLVum4DTKqsAYXReq3BuKZiSF2XjiObTNN55GIjgU2 BGPYpSyJCF21M0aki5RZnMYrpkrJbUnBtwUVupzxpeC29HqBmxmC7ZmnDEF40W7M wgW9FCX46TM59Vukr7ECGiLX+vhmWCgHxQJTLQkrzBvm2AG9d7v1DBQX1Cp15kuK IpGA310l2B/NzizBqZZB6im8wktqQteta7p7iAON7YfcEtMk6Loy9nxtOkTkrxUE BFqY8hyC54vn6LbcpiPqOvpUI281iBi8iw6vbFkzIlLpiSYzN6w13honzfTMx+gy Y9gklDsgNMovPud7T9greJRZ5U3NiwN7CLILLtvFwHHZD+fFSdcsnF6457+D/tAo pwR+qBGBquwkziv2dUf+nQmhBpa2Gh4Nxi7euUdkEGjjT3GNU1HitLVIlM3lyejN bvBfOcHaqJm9YIk95q16 =pRVV -END PGP SIGNATURE- -- 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/4c24b065.9070...@gmail.com
Re: Compiling kernel took a lot of disk space.
On Fri, 25 Jun 2010 09:34:29 -0400 (EDT), Jordan Metzmeier wrote: On 06/25/2010 09:10 AM, Stephen Powell wrote: That is not the correct command syntax. I suggest that you read http://www.wowway.com/~zlinuxman/Kernel.htm Kernel building in Debian is a complex task fraught with many perils, and this web page will help you avoid most of them. It's long and detailed, but if you follow this procedure you should do well. Looks like an excellent guide. Thanks for the work! You're welcome. The Debian kernel team doesn't particularly care for it, and if you you read it all the way through, particularly step 10, you can probably guess why. But Manoj Srivastava, author and maintainer of kernel-package, liked it well enough to include an earlier version of this web page in kernel-package itself. The above link, however, will always be the most current and up-to-date version of the document. I will probably update it again next week if the fix for Debian bug number 505609 is included in the stable point release for Lenny which is scheduled for this weekend. -- .''`. 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/182056374.282512.1277474554176.javamail.r...@md01.wow.synacor.com
Compiling kernel
Hello I have a doubt about kernel compilation. Two days ago I compiled by hand 2.6.31.6 and it crashed during the boot process. The configuration was made by hand, starting from the default configuration and perhaps I missed something. Since I had to restore my old slackware bakcup to recover some files and information, I got a copy of the already running (at slack) 2.6.31.6 kernel configuration that is finely tuned for my desktop... my question is: can I simply load such kernel configuration in the 'make xconfig' that is working (same desktop and cpu configuration) and compile it with debian? I mean, it is the same computer and hardware, the same kernel version, etc. More specific: Does Debian require a special kernel configuration due to its libraries/configuration or am I able just to load the kernel config and install it now on Debian? In theory it should work with any distribution, as far as I know it should match only the hardware... Thanks, Miguel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Compiling kernel
On Sat, Dec 05, 2009 at 06:59:48AM -0700, deb...@toursbymexico.com wrote: I have a doubt about kernel compilation. Two days ago I compiled by hand 2.6.31.6 and it crashed during the boot process. The configuration was made by hand, starting from the default configuration and perhaps I missed something. Since I had to restore my old slackware bakcup to recover some files and information, I got a copy of the already running (at slack) 2.6.31.6 kernel configuration that is finely tuned for my desktop... my question is: can I simply load such kernel configuration in the 'make xconfig' that is working (same desktop and cpu configuration) and compile it with debian? I mean, it is the same computer and hardware, the same kernel version, etc. Yes. In addition, I would highly recommend using kernel-package to compile your kernel to generate a deb. Here's a nice primer: http://newbiedoc.sourceforge.net/system/kernel-pkg.html More specific: Does Debian require a special kernel configuration due to its libraries/configuration or am I able just to load the kernel config and install it now on Debian? In theory it should work with any distribution, as far as I know it should match only the hardware... No. I use vanilla kernels with not problems. But I use kernel-package to build a deb and install it, so that it does grub installation etc. automagically. HTH. Kumar -- The chat program is in public domain. This is not the GNU public license. If it breaks then you get to keep both pieces. (Copyright notice for the chat program) signature.asc Description: Digital signature
Re: Compiling kernel
Kumar Appaiah wrote: On Sat, Dec 05, 2009 at 06:59:48AM -0700, deb...@toursbymexico.com wrote: I have a doubt about kernel compilation. Two days ago I compiled by hand 2.6.31.6 and it crashed during the boot process. The configuration was made by hand, starting from the default configuration and perhaps I missed something. Since I had to restore my old slackware bakcup to recover some files and information, I got a copy of the already running (at slack) 2.6.31.6 kernel configuration that is finely tuned for my desktop... my question is: can I simply load such kernel configuration in the 'make xconfig' that is working (same desktop and cpu configuration) and compile it with debian? I mean, it is the same computer and hardware, the same kernel version, etc. Yes. In addition, I would highly recommend using kernel-package to compile your kernel to generate a deb. Here's a nice primer: http://newbiedoc.sourceforge.net/system/kernel-pkg.html I would recommend using the 'make-kpkg' command from the kernel-package package as well. But I would not recommend following this old web page document -- it is WAY out of date. Read the documentation in /usr/share/doc/kernel-package after installing it, or Google for a tutorial that is more recent. Dave W. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Compiling kernel
On Sat, Dec 05, 2009 at 11:11:08AM -0500, Dave Witbrodt wrote: Yes. In addition, I would highly recommend using kernel-package to compile your kernel to generate a deb. Here's a nice primer: http://newbiedoc.sourceforge.net/system/kernel-pkg.html I would recommend using the 'make-kpkg' command from the kernel-package package as well. But I would not recommend following this old web page document -- it is WAY out of date. Read the documentation in /usr/share/doc/kernel-package after installing it, or Google for a tutorial that is more recent. Thanks for pointing this out. Kumar -- Old MacLinus had a stack/l-i-n-u-x/and on this stack he had a trace/l-i-n-u-x with an Oops-Oops here and an Oops-Oops there here an Oops, there an Oops, everywhere an Oops-Oops. -- tjime...@site.gmu.edu, linux.dev.kernel signature.asc Description: Digital signature
Problems compiling kernel 2.6.31
I am getting some problems while compiling kernel 2.6.31 using Debian Lenny make-kpkg The messages are - make[3]: Entering directory `/root/linux-2.6.31' CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm - include/asm-x86 CALLscripts/checksyscalls.sh Building modules, stage 2. MODPOST 1713 modules make[3]: Leaving directory `/root/linux-2.6.31' /usr/bin/makeARCH=i386 \ -C Documentation/lguest make[3]: Entering directory `/root/linux-2.6.31/Documentation/lguest' cc -m32 -Wall -Wmissing-declarations -Wmissing-prototypes -O3 -I../../include -I../../arch/x86/include -U_FORTIFY_SOURCElguest.c -o lguest lguest.c:21:25: error: sys/eventfd.h: No such file or directory lguest.c: In function ‘create_thread’: lguest.c:1021: warning: implicit declaration of function ‘eventfd’ make[3]: *** [lguest] Error 1 make[3]: Leaving directory `/root/linux-2.6.31/Documentation/lguest' make[2]: *** [debian/stamp/build/kernel] Error 2 make[2]: Leaving directory `/root/linux-2.6.31' make[1]: *** [debian/stamp/do-build-arch] Error 2 make[1]: Leaving directory `/root/linux-2.6.31' dpkg-buildpackage: failure: debian/rules build gave error exit status 2 make: *** [debian/stamp/build/buildpackage] Error 2 r...@indiaforce:~/linux-2.6.31# make install sh /root/linux-2.6.31/arch/x86/boot/install.sh 2.6.31 arch/x86/boot/bzImage \ System.map /boot Please help. -- Harshad Joshi
Re: Problems compiling kernel 2.6.31
On 29.10.09 1311 (+0530), surreal wrote: I am getting some problems while compiling kernel 2.6.31 using Debian Lenny make-kpkg The messages are - make[3]: Entering directory `/root/linux-2.6.31' CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm - include/asm-x86 CALLscripts/checksyscalls.sh Building modules, stage 2. MODPOST 1713 modules make[3]: Leaving directory `/root/linux-2.6.31' /usr/bin/makeARCH=i386 \ -C Documentation/lguest make[3]: Entering directory `/root/linux-2.6.31/Documentation/lguest' cc -m32 -Wall -Wmissing-declarations -Wmissing-prototypes -O3 -I../../include -I../../arch/x86/include -U_FORTIFY_SOURCElguest.c -o lguest Google this error message: lguest.c:21:25: error: sys/eventfd.h: No such file or directory and the first link [1] has a solution: Below “Virtualization” unselect “Linux hypervisor example code” or if you need lguest you can also fix the compilation error by removing “#include sys /eventfd.h” (line 21) from lguest.c. [1]: http://cakebox.homeunix.net/wordpress/?p=100 -- Best regards, Vasily Ivanov mailto:cae...@academ.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: compiling kernel
[snip] Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut maintenant utilisé make deb-pkg [1] [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html Thomas Preud'homme Salut, petit question à propos de ce make deb-pkg : je compile depuis qqs années de la manière suivante : make-kpkg --rootcmd fakeroot --append-to-version=-1 --revision=`date +%y%m%d` kernel-image Aurais tu de la doc sur ce make deb-pkg pour obtenir un résulat similaire ? Et autre question ce make deb-pkg est intégré direct dans le makefile du noyau ? Merci d'avance Guillaume -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Le mercredi 21 octobre 2009 09:30:06, mess-mate a écrit : Bonjour, j'ai un petit problème pour compiler mon noau: voici le message d'erreur: make-kpkg --initrd --append-to-version=-amd64-mm kernel-image kernel-headers kernel-doc exec make kpkg_version=12.021 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-amd64-mm INITRD=YES .config:1: *** missing separator. Stop. Visiblement un problème dans ton .config Peux-tu repartir du config dans /boot/ ? Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 971. il y a pas de .debian en effet puisque c'est un noyau source (non debian). C'est un noyau que j'avais compilé dans le temps sans problème mais maintenant avec cette erreur udev au boot il faut que je recompile. Evidemment j'ai déjà fait un 'make clean', donc plus question de rebooter sur ce noyau. Je pense qu'il me faudra un .debian de quelqu'un ou une autre astuce. Soit recompiler à la main comme dans le temps. merci d'avance pour l'aide. Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut maintenant utilisé make deb-pkg [1] [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html Thomas Preud'homme -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Bonsoir, Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit : Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut maintenant utilisé make deb-pkg [1] [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html Merci pour cette info. Pour voir, j'ai essayé sur un linux-source-2.6.31 (préalablement buildé avec make-kpkg) et ca a produit deux paquets: linux-firmware-image_2.6.31-2_all.deb linux-image-2.6.31_2.6.31-2_i386.deb Quelles sont les règles make pour produire les paquets pour les headers et les modules ? Merci, Jean-Damien. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Le jeudi 22 octobre 2009 22:35:47, Jean-Damien Durand a écrit : Bonsoir, Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit : Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut maintenant utilisé make deb-pkg [1] [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html Merci pour cette info. Pour voir, j'ai essayé sur un linux-source-2.6.31 (préalablement buildé avec make-kpkg) et ca a produit deux paquets: linux-firmware-image_2.6.31-2_all.deb linux-image-2.6.31_2.6.31-2_i386.deb Quelles sont les règles make pour produire les paquets pour les headers et les modules ? Je n'ai pas encore testé pour être honnête mais d'après ce que j'ai lu dans le fichier builddeb qui se trouve dans le sous-répertoire scripts/package des sources du noyau il suffit de positionner CONFIG_MODULES dans le .config pour que ce soit inclus dans le paquet. La ligne qui me fait penser cela est : if grep -q '^CONFIG_MODULES=y' .config ; then INSTALL_MOD_PATH=$tmpdir make KBUILD_SRC= modules_install if [ $ARCH == um ] ; then mv $tmpdir/lib/modules/$version/* $tmpdir/usr/lib/uml/modules/$version/ rmdir $tmpdir/lib/modules/$version fi fi Par contre le fichier n'est clairement pas prévu pour créer des paquets autre que les deux que tu cites. J'aurais tendance à dire que pour les headers et les modules tu dois continuer à utiliser make-kpkg. Merci, Jean-Damien. Thomas Preud'homme -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Le jeudi 22 octobre 2009 23:40:50, Thomas Preud'homme a écrit : Le jeudi 22 octobre 2009 22:35:47, Jean-Damien Durand a écrit : Bonsoir, Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit : Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut maintenant utilisé make deb-pkg [1] [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html Merci pour cette info. Pour voir, j'ai essayé sur un linux-source-2.6.31 (préalablement buildé avec make-kpkg) et ca a produit deux paquets: linux-firmware-image_2.6.31-2_all.deb linux-image-2.6.31_2.6.31-2_i386.deb Quelles sont les règles make pour produire les paquets pour les headers et les modules ? Je n'ai pas encore testé pour être honnête mais d'après ce que j'ai lu dans le fichier builddeb qui se trouve dans le sous-répertoire scripts/package des sources du noyau il suffit de positionner CONFIG_MODULES dans le .config pour que ce soit inclus dans le paquet. La ligne qui me fait penser cela est : if grep -q '^CONFIG_MODULES=y' .config ; then INSTALL_MOD_PATH=$tmpdir make KBUILD_SRC= modules_install if [ $ARCH == um ] ; then mv $tmpdir/lib/modules/$version/* $tmpdir/usr/lib/uml/modules/$version/ rmdir $tmpdir/lib/modules/$version fi fi Par contre le fichier n'est clairement pas prévu pour créer des paquets autre que les deux que tu cites. J'aurais tendance à dire que pour les headers et les modules tu dois continuer à utiliser make-kpkg. J'ai parcouru les réponses au lien que j'ai donné et j'ai fini par tomber sur ceci : http://lists.debian.org/debian-kernel/2009/10/msg00734.html Pour les non anglophones cela dit que le support des headers est prévu pour le noyau 2.6.33 et qu'on peut déjà trouver le code dans la branche linux-next du repository git de Linux. Pour remplacer le comportement de --revision et et --append-to-version il faut positionner la variable d'environnement KDEB_PKGVERSION qui gère les deux à la fois. La revision debian (le --revision) peut être contrôlé avec le fichier .version La doc n'existe pas encore car make deb-pkg est assez simple mais elle est en cours de rédaction. Merci, Jean-Damien. Thomas Preud'homme Thomas Preud'homme -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
compiling kernel
Bonjour, j'ai un petit problème pour compiler mon noau: voici le message d'erreur: make-kpkg --initrd --append-to-version=-amd64-mm kernel-image kernel-headers kernel-doc exec make kpkg_version=12.021 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-amd64-mm INITRD=YES .config:1: *** missing separator. Stop. Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 971. il y a pas de .debian en effet puisque c'est un noyau source (non debian). C'est un noyau que j'avais compilé dans le temps sans problème mais maintenant avec cette erreur udev au boot il faut que je recompile. Evidemment j'ai déjà fait un 'make clean', donc plus question de rebooter sur ce noyau. Je pense qu'il me faudra un .debian de quelqu'un ou une autre astuce. Soit recompiler à la main comme dans le temps. merci d'avance pour l'aide. -- mess-mate May you do Good Magic with Perl. -- Larry Wall's blessing -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Le 21-10-2009, à 09:30:06 +0200, mess-mate (mess-m...@orange.fr) a écrit : Bonjour, Salut, j'ai un petit problème pour compiler mon noau: voici le message d'erreur: make-kpkg --initrd --append-to-version=-amd64-mm kernel-image kernel-headers kernel-doc exec make kpkg_version=12.021 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-amd64-mm INITRD=YES .config:1: *** missing separator. Stop. Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 971. D'après http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407097 Tu dois cp /boot/config* /dans_ton_arbo_source/ make oldconfig puis refaire ton make-kpkg. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Salut, mess-mate a écrit : j'ai un petit problème pour compiler mon noau: voici le message d'erreur: make-kpkg --initrd --append-to-version=-amd64-mm kernel-image kernel-headers kernel-doc exec make kpkg_version=12.021 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-amd64-mm INITRD=YES .config:1: *** missing separator. Stop. Regarde ce que contient le fichier .config, ça ne doit pas être bon. Soit tu en génères un nouveau avec make config|menuconfig|xconfig, soit tu en copie un à partir d'un fichier de configuration d'un autre noyau existant dans /boot/ que tu adaptes avec make oldconfig|silentoldconfig. Tu peux aussi faire les deux, reprendre un fichier existant et le fignoler ensuite. Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 971. Ça se résoudra tout seul quand le .config sera correct. Evidemment j'ai déjà fait un 'make clean', donc plus question de rebooter sur ce noyau. Il vaut mieux faire make-kpkg clean quand on construit avec la méthode Debian. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: compiling kernel
Pascal Hambourg wrote: Salut, mess-mate a écrit : j'ai un petit problème pour compiler mon noau: voici le message d'erreur: make-kpkg --initrd --append-to-version=-amd64-mm kernel-image kernel-headers kernel-doc exec make kpkg_version=12.021 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-amd64-mm INITRD=YES .config:1: *** missing separator. Stop. Regarde ce que contient le fichier .config, ça ne doit pas être bon. Soit tu en génères un nouveau avec make config|menuconfig|xconfig, soit tu en copie un à partir d'un fichier de configuration d'un autre noyau existant dans /boot/ que tu adaptes avec make oldconfig|silentoldconfig. Tu peux aussi faire les deux, reprendre un fichier existant et le fignoler ensuite. Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 971. Ça se résoudra tout seul quand le .config sera correct. Evidemment j'ai déjà fait un 'make clean', donc plus question de rebooter sur ce noyau. Il vaut mieux faire make-kpkg clean quand on construit avec la méthode Debian. Merci pour les réponses. J'ai finalement trouvé ce qui cloche (si cela peut aider qualqu'un). Avec cette erreur de udev au boot miantenant, j'avais tout simplement mis 'n' à CONFIG_SYSFS_DEPRECATED=n dans ma .config à la main. CE QU'IL NE FAUT PAS FAIRE ! Il est nécessaire de l'annuler avec un make menuconfig ou make xconfig. Voyons maintenant si ça marche. amicalement -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Re: problem compiling kernel
On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote: - snip -- The initrd.img that I have on my working system, as well as those initrd.img that 'mkinitrd' generates when requested, are not compressed files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz behind. I still tried to gunzip one, just in case that would still be a compressed file without usual extension, but no, it is not handled by gunzip or zcat. I tried cpio on that file as is, but I got : 'cpio: premature end of file'. a 'vi filename' shows that this is a binary file. No point to edit then. So, at this point, I don't have a clue of how to build an initrd.img file that would allow my newly compiled 2.6.30.4 kernel to boot on my system. then edit init to match my needs i.e. depmod, modprobe, cryptsetup etc and finally put a line to run the real init. I then zip it find . ! -name *~ | cpio -H newc --create | gzip -9 ../test-initrd.gz I can install then the new initrd (cp ../test-initrd.gz /boot/initrdgz) Once you've done it it's very simple and easy ... before it was a big trouble for me too. Just look positive as way to learn something new about your operating system. reagrds Sorry if I'm misunderstanding, but are you saying that although you've included 'make --initrd . . ' in your compile command sequence, you are still not getting an appropriate initrd.img? This appears to be some kind of bug in the 2.6.30 kernel I've managed to solve this by using the update-initramfs -c -k linux-2.6.30-x-custom command. After doing this, check your /boot to see if there is, in fact, a new 'initrd.img-2.6.30-x-custom' file. If there is, update your grub or lilo reboot. I've compiled 5 different versions of the 2.6.30-x kernel had to do this in each one. The developers know about this but so far haven't done squat about it - maybe they consider it a low priority or something. Hope this helps . . . ~A~ -- A person needs only two tools: WD-40 and duct tape. If it doesn't move and it should, use WD-40. If it moves and shouldn't, use the tape. -- Red Green Registered Linux User No. 306834 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Amax wrote: On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote: - snip -- The initrd.img that I have on my working system, as well as those initrd.img that 'mkinitrd' generates when requested, are not compressed files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz behind. I still tried to gunzip one, just in case that would still be a compressed file without usual extension, but no, it is not handled by gunzip or zcat. I tried cpio on that file as is, but I got : 'cpio: premature end of file'. a 'vi filename' shows that this is a binary file. No point to edit then. So, at this point, I don't have a clue of how to build an initrd.img file that would allow my newly compiled 2.6.30.4 kernel to boot on my system. then edit init to match my needs i.e. depmod, modprobe, cryptsetup etc and finally put a line to run the real init. I then zip it find . ! -name *~ | cpio -H newc --create | gzip -9 ../test-initrd.gz I can install then the new initrd (cp ../test-initrd.gz /boot/initrdgz) Once you've done it it's very simple and easy ... before it was a big trouble for me too. Just look positive as way to learn something new about your operating system. reagrds Sorry if I'm misunderstanding, but are you saying that although you've included 'make --initrd . . ' in your compile command sequence, you are still not getting an appropriate initrd.img? This appears to be some kind of bug in the 2.6.30 kernel I've managed to solve this by using the update-initramfs -c -k linux-2.6.30-x-custom command. After doing this, check your /boot to see if there is, in fact, a new 'initrd.img-2.6.30-x-custom' file. If there is, update your grub or lilo reboot. I've compiled 5 different versions of the 2.6.30-x kernel had to do this in each one. The developers know about this but so far haven't done squat about it - maybe they consider it a low priority or something. Hope this helps . . . ~A~ Thanks for your input. Ever since I wrote about those late problems, things have changed a lot here. I got convinced that I would go no further with my old Sarge distro : old kernels could no longer get compiled with newer tools, and, as far as building newer kernels, the initrd image that I got using mkinitrd did not fit my system and wouldn't allow boot. So, I decided to get a more recent distro. Since there was 'Etch' in between Sarge and Lenny, I figured that I could not just upgrade, maybe I was wrong, in any case, I just saved whatever had to be kept, and I installed Lenny from scratch. This was about 6 days ago. On my new Lenny, I was able to recompile my kernel, but it has not been so easy. I could not get the official process to work here, using make-kpkg with --initrd. It did compile indeed, and gave a kernel image and an initrd image, but that did not boot either. However, using plain old 'make', then make_install, then make_modules_install, then, not mkinitrd, but initramfs, I got what I needed, and my new kernel boots all right. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Bernard wrote: You really could use the recent 2.6.30.4. There were different problems with 2.6.20 to 2.6.30. I find 2.6.30.4 the best I've had since 2.6.20. I tried 2.6.30.4. Same result as with 2.6.26.2 : compiles without errors, but crashes on boot. so you are missing some essential part of it So, what I would do (if I were you) is that I would download latest 2.6.30.4, and compile all I need to access my boot partition (as you already did with md in the kernel), I just did that again You sure you picked up _all_ you need to boot? then compile and rebuild or build by hand initramfs. Build by hand I pretty simple- it's actually hacking the one used. I do unzip it cd /tmp; mkdir test; cd test zcat /boot/initrdgz | cpio -Hnewc -i The initrd.img that I have on my working system, as well as those initrd.img that 'mkinitrd' generates when requested, are not compressed files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz behind. I still tried to gunzip one, just in case that would still be a compressed file without usual extension, but no, it is not handled by gunzip or zcat. I tried cpio on that file as is, but I got : 'cpio: premature end of file'. a 'vi filename' shows that this is a binary file. No point to edit then. Did you try bzip? So, at this point, I don't have a clue of how to build an initrd.img file that would allow my newly compiled 2.6.30.4 kernel to boot on my system. You know pretty much already. You can do it yourself. What about using a already working image like I've suggested. You can take i.e. ubuntu knoppix or debian live - boot with it and copy the relevant parts from /boot/ and /lib/modules to your hard drive I now had also another idea. Is your boot partition may be full, so initrd can not be written completely when generated? it happens more often then you can imagine regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: Bernard wrote: Emanoil Kotsev wrote: Bernard wrote: Compiling md in the kernel is the right approach to boot from raided root without initrd. You can try this just skipping (deleteing the line in grub temporary) I just tried that. Raid compiled into the kernel instead of modules. No initrd. Still crashes at boot. most probably you are missing other modules (like ide/ata lvm etc) You said your boot is on md but not on lvm. you can build a working initrd easily - this is actually all you need. Also done another test: in the /boot/grub/menu.lst file, replaced root=/dev/mapper/vg00-root by /dev/sda2. Still crashed : cannot open root device 'sda2' or unknown block(0,0). this can not work as your root is on lvm. what did you expect? try passing the kernel option init=/bin/sh There is another test that I would like to run, but I need help for this, since I don't know the whole package list: apt-get purge kernel-building gcc make kernel-utils etc... then edit my /etc/apt/sources.list and comment out lines that refer to package directories that are too recent, uncomment old lines referring to debian sarge packages only, excluding 'testing' etc.. then apt-get install kernel-building gcc make kernel-utils etc... and, from there on, trying to recompile, not newer kernels, but my good old running kernel 2.6.20-16-386 into a custom version without any sound options in it. What I need is the list of all packages that I should purge and re-install in their former version. regards You really could use the recent 2.6.30.4. There were different problems with 2.6.20 to 2.6.30. I find 2.6.30.4 the best I've had since 2.6.20. I tried 2.6.30.4. Same result as with 2.6.26.2 : compiles without errors, but crashes on boot. So, what I would do (if I were you) is that I would download latest 2.6.30.4, and compile all I need to access my boot partition (as you already did with md in the kernel), I just did that again then compile and rebuild or build by hand initramfs. Build by hand I pretty simple- it's actually hacking the one used. I do unzip it cd /tmp; mkdir test; cd test zcat /boot/initrdgz | cpio -Hnewc -i The initrd.img that I have on my working system, as well as those initrd.img that 'mkinitrd' generates when requested, are not compressed files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz behind. I still tried to gunzip one, just in case that would still be a compressed file without usual extension, but no, it is not handled by gunzip or zcat. I tried cpio on that file as is, but I got : 'cpio: premature end of file'. a 'vi filename' shows that this is a binary file. No point to edit then. So, at this point, I don't have a clue of how to build an initrd.img file that would allow my newly compiled 2.6.30.4 kernel to boot on my system. then edit init to match my needs i.e. depmod, modprobe, cryptsetup etc and finally put a line to run the real init. I then zip it find . ! -name *~ | cpio -H newc --create | gzip -9 ../test-initrd.gz I can install then the new initrd (cp ../test-initrd.gz /boot/initrdgz) Once you've done it it's very simple and easy ... before it was a big trouble for me too. Just look positive as way to learn something new about your operating system. reagrds -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: Bernard wrote: Compiling md in the kernel is the right approach to boot from raided root without initrd. You can try this just skipping (deleteing the line in grub temporary) I just tried that. Raid compiled into the kernel instead of modules. No initrd. Still crashes at boot. Also done another test: in the /boot/grub/menu.lst file, replaced root=/dev/mapper/vg00-root by /dev/sda2. Still crashed : cannot open root device 'sda2' or unknown block(0,0). There is another test that I would like to run, but I need help for this, since I don't know the whole package list: apt-get purge kernel-building gcc make kernel-utils etc... then edit my /etc/apt/sources.list and comment out lines that refer to package directories that are too recent, uncomment old lines referring to debian sarge packages only, excluding 'testing' etc.. then apt-get install kernel-building gcc make kernel-utils etc... and, from there on, trying to recompile, not newer kernels, but my good old running kernel 2.6.20-16-386 into a custom version without any sound options in it. What I need is the list of all packages that I should purge and re-install in their former version. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Bernard wrote: Emanoil Kotsev wrote: Bernard wrote: Compiling md in the kernel is the right approach to boot from raided root without initrd. You can try this just skipping (deleteing the line in grub temporary) I just tried that. Raid compiled into the kernel instead of modules. No initrd. Still crashes at boot. most probably you are missing other modules (like ide/ata lvm etc) You said your boot is on md but not on lvm. you can build a working initrd easily - this is actually all you need. Also done another test: in the /boot/grub/menu.lst file, replaced root=/dev/mapper/vg00-root by /dev/sda2. Still crashed : cannot open root device 'sda2' or unknown block(0,0). this can not work as your root is on lvm. what did you expect? try passing the kernel option init=/bin/sh There is another test that I would like to run, but I need help for this, since I don't know the whole package list: apt-get purge kernel-building gcc make kernel-utils etc... then edit my /etc/apt/sources.list and comment out lines that refer to package directories that are too recent, uncomment old lines referring to debian sarge packages only, excluding 'testing' etc.. then apt-get install kernel-building gcc make kernel-utils etc... and, from there on, trying to recompile, not newer kernels, but my good old running kernel 2.6.20-16-386 into a custom version without any sound options in it. What I need is the list of all packages that I should purge and re-install in their former version. regards You really could use the recent 2.6.30.4. There were different problems with 2.6.20 to 2.6.30. I find 2.6.30.4 the best I've had since 2.6.20. I was also very sad when I found out I can not compile 2.6.20 anymore. Put let's believe it's for the sake of the progress. So, what I would do (if I were you) is that I would download latest 2.6.30.4, and compile all I need to access my boot partition (as you already did with md in the kernel), then compile and rebuild or build by hand initramfs. Build by hand I pretty simple- it's actually hacking the one used. I do unzip it cd /tmp; mkdir test; cd test zcat /boot/initrdgz | cpio -Hnewc -i then edit init to match my needs i.e. depmod, modprobe, cryptsetup etc and finally put a line to run the real init. I then zip it find . ! -name *~ | cpio -H newc --create | gzip -9 ../test-initrd.gz I can install then the new initrd (cp ../test-initrd.gz /boot/initrdgz) Once you've done it it's very simple and easy ... before it was a big trouble for me too. Just look positive as way to learn something new about your operating system. reagrds -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: Emanoil Kotsev wrote: Sorry forgot to write Yes there is problem compiling the 2.6.20 with recent gcc The problem is the compiler. If you are compiling just grab the last version from kernel.org. 2.6.30.4 seems to be working fine Just to be objective the gnu compiler people said kernel people are wrong and vice versa. I didn't follow the discussion. I'm glad next kernels compile regards 2.6.30.4 does compile all right, so does 2.6.26, but 2.6.20 does not. Problem is that I still can't boot those I compiled, i.e. 2.6.26. because the initrd.img is buggy. I did find something, still it is not enough to get the process to work. In my /etc/mkinitrd/mkinitrd.conf file, I found a modified line : # Command to generate the initrd image. # MKIMAGE='mkcramfs %s %s /dev/null' this has been changed august 19, 2009 MKIMAGE='genromfs -d %s -f %s' The change date has not been written by me, so this must be a conf file that came with a recent package upgrade that I did. I tried uncommenting the old line, commenting the new one instead. MKIMAGE='mkcramfs... became active. What gave me this idea, is that in those error messages that I could see at crash, it was matter of cramfs. Well that change made mkinitrd to produce smaller images. I tried installing them in the grub boot menu, and then, now, the boot crashes do not happen at the same time as before... but it still crashes ! I could do nothing else than catch photos of my screen, since no log file are recorded in such cases. http://www.teaser.fr/~bdebreil/bootcrash1.jpg and http://www.teaser.fr/~bdebreil/bootcrash2.jpg will show you what I got The first crash screen is not very informative : could not load '/lib/modules... no such files (these files exist, but at this point in time it is not in the /boot partition, therefore not mounted as yet). This crash came from a kernel which I had configure to have RAID inside, not as modules. While watching the boot logs of my working kernel, I could see that RAID was as modules. So, I recompiled a new kernel with modules for RAID, and then boot went a little bit further, as can be seen in the screen picture at crash : 'raid1 set md1 active with 2 out of 2 mirrors mdadm : /dev/md1 has been started with 2 drives' but then : 'mkdir cannot create directory '/devfs/vg00' : read only filesystem .. failure to communicate to kernel device mapper driver incompatible libdevmapper 1.01.00-ioctl (2005-01-17) (compat) and kernel driver' I think that this last quoted line does most explain that the tools I am using are not appropriate. I have good grounds to think that the problems are in my initrd.img file... but there may also be something wrong in the compiled kernel image. Could someone please tell me what tool packages to purge and what to install instead so that I can recompile a 2.6.26 or 2.6.30 kernel that will boot on my Debian 3.1 system with raid 1 ? Thanks in advance for your help -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Bernard wrote: 2.6.30.4 does compile all right, so does 2.6.26, but 2.6.20 does not. you find out why in the archives Problem is that I still can't boot those I compiled, i.e. 2.6.26. because the initrd.img is buggy. I did find something, still it is not enough to get the process to work. In my /etc/mkinitrd/mkinitrd.conf file, I found a modified line : # Command to generate the initrd image. # MKIMAGE='mkcramfs %s %s /dev/null' this has been changed august 19, # 2009 MKIMAGE='genromfs -d %s -f %s' The change date has not been written by me, so this must be a conf file that came with a recent package upgrade that I did. I tried uncommenting the old line, commenting the new one instead. MKIMAGE='mkcramfs... became active. What gave me this idea, is that in those error messages that I could see at crash, it was matter of cramfs. Well that change made mkinitrd to produce smaller images. I tried installing them in the grub boot menu, and then, now, the boot crashes do not happen at the same time as before... but it still crashes ! I could do nothing else than catch photos of my screen, since no log file are recorded in such cases. http://www.teaser.fr/~bdebreil/bootcrash1.jpg so this is the old error, and you don't need a fix for it and http://www.teaser.fr/~bdebreil/bootcrash2.jpg will show you what I got The first crash screen is not very informative : could not load '/lib/modules... no such files I don't think so it's as informative as it should be. It can not mount sdb2 (is it your root?) (these files exist, but at this point in time it is not in the /boot partition, therefore not mounted as yet). This crash came from a kernel which I had configure to have RAID inside, not as modules. While watching the boot logs of my working kernel, I could see that RAID was as modules. So, I recompiled a new kernel with modules for RAID, and then boot went a little bit further, as can be seen in the screen picture at crash : 'raid1 set md1 active with 2 out of 2 mirrors mdadm : /dev/md1 has been started with 2 drives' but then : 'mkdir cannot create directory '/devfs/vg00' : read only filesystem .. failure to communicate to kernel device mapper driver incompatible libdevmapper 1.01.00-ioctl (2005-01-17) (compat) and kernel driver' The problem is as far as I remember that devfs was given up ... was it something that worked with hotplug ... I really don't remember right now, but there was a change affecting devmapper. I think you have to read about it, perhaps replace it and recreate initrd. Compiling md in the kernel is the right approach to boot from raided root without initrd. You can try this just skipping (deleteing the line in grub temporary) I think that this last quoted line does most explain that the tools I am using are not appropriate. I have good grounds to think that the problems are in my initrd.img file... but there may also be something wrong in the compiled kernel image. try without initrd (with custom kernel, you can put everything you need inside it (i.e filesystem support ide/ata etc) you then can access your root partition and the boot process will continue from there. The initrd is only needed to load drivers which helps you do the above. Because you are using lvm, if not using initrd you need to compile also lvm inside the kernel. Could someone please tell me what tool packages to purge and what to install instead so that I can recompile a 2.6.26 or 2.6.30 kernel that will boot on my Debian 3.1 system with raid 1 ? There are good howtos for upgrading from sarg - etch and etch - lenny. You definitely better use udev ... devmapper is not needed anymore as far as I know. I did it last year ... and yes there were some troubles with the initrds ... I could send you my scripts for building your own initrd ( I have used them to build initrd for crypted root - before it started working in debian), though I've already posted a 5step howto fix broken boot initrd - try init=/bin/sh option ;-) and fix the boot by hand - you'll see what you are missing You could just copy over a working image and initrd (from some live cd/dvd) edit grub and reboot - this should work. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
problem compiling kernel
Hi to Everyone, I need to re-compile my kernel so that it does not include sound support inside. I am running Debian 3.1 (Sarge). My system is on RAID1. My /boot partition is from /dev/sda1 (mirror on /dev/sdb1) installed on /dev/md0 (ext3), while my '/' partition is from /dev/sda2 and /dev/sdb2 installed on /dev/md1 mounted on /dev/mapper/vg00-root (LVM2). It's been working OK for several years. The easiest way would be to try re-compiling from /boot/config-2.6.20-16-386 using make oldconfig. But this repeatedly fails. 'make' soon returns error messages saying that such and such function have not been declared. Since the process works with more recent kernels, I suppose that the Makefile that I have in /usr/src/linux-2.6.20-16-386 is buggy, or else, maybe the version of gcc/make that I get is no longer compatible with said Makefile : I must admit that I have sometimes ran 'apt-get install' on various packages with a /etc/apt/sources.list that contained lines referring to testing directories. So, upon my failures to recompile kernel 2.6.20-16-386, I tried downloading 2.6.20-17-386, but I got the same results. However, with 2.6.26.2, it did compile without errors... but in the end the image won't boot ! My compiling process does not generate initrd.img, so I did generate one using 'mkinitrd', and I wrote its path in /boot/grub/menu.lst with the kernel image. Here is what I get on booting trials : boot starts, as usual text displays very fast and you cannot read until it stops. When this happen, I can read this : md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 device mapper . no filesystem could mount root. Tried: cramfs kernel panic - not syncing: VFS unable to mount root fs on unknown block(0,0) So, I re-tried compiling after de-activating raid0 in the config, leaving only raid1... to the same end result. Could someone tell me what options I should select in the config so as to obtain a new kernel that will boot my RAID architecture ? I know that there are other ways to compile Debian kernels, using 'make-kpkg', but this does not work here, likely because this tool version is too old or too new for my system : it keeps saying that parameters are missing, while the howtos that I saw did not mention any such parameters for make-kpkg. By the way, I noticed that the initrd.img that I obtain using mkinitrd are about 5 times bigger than that which is used to boot my usual kernel. I am not sure that I am using mkinitrd correctly. mkinitrd -o initrd.img-2.6.26.2 2.6.26 done from /boot issues an error messages saying that this image will not take raid into account, and that therefore it won't boot, unless the main image contains what is missing here. In any case, it doesn't boot. The same command issued in /usr/src/linux-2.6.26.2 does not send any error message, but in the end the image doesn't boot either. Thanks in advance for your help -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Bernard wrote: Hi to Everyone, I need to re-compile my kernel so that it does not include sound support inside. I am running Debian 3.1 (Sarge). My system is on RAID1. My /boot partition is from /dev/sda1 (mirror on /dev/sdb1) installed on /dev/md0 (ext3), while my '/' partition is from /dev/sda2 and /dev/sdb2 installed on /dev/md1 mounted on /dev/mapper/vg00-root (LVM2). It's been working OK for several years. The easiest way would be to try re-compiling from /boot/config-2.6.20-16-386 using make oldconfig. But this repeatedly fails. 'make' soon returns error messages saying that such and such function have not been declared. Since the process works with more recent kernels, I suppose that the Makefile that I have in /usr/src/linux-2.6.20-16-386 is buggy, or else, maybe the version of gcc/make that I get is no longer compatible with said Makefile : I must admit that I have sometimes ran 'apt-get install' on various packages with a /etc/apt/sources.list that contained lines referring to testing directories. So, upon my failures to recompile kernel 2.6.20-16-386, I tried downloading 2.6.20-17-386, but I got the same results. However, with 2.6.26.2, it did compile without errors... but in the end the image won't boot ! My compiling process does not generate initrd.img, so I did generate one using 'mkinitrd', and I wrote its path in /boot/grub/menu.lst with the kernel image. Here is what I get on booting trials : boot starts, as usual text displays very fast and you cannot read until it stops. When this happen, I can read this : md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 device mapper . no filesystem could mount root. Tried: cramfs kernel panic - not syncing: VFS unable to mount root fs on unknown block(0,0) So, I re-tried compiling after de-activating raid0 in the config, leaving only raid1... to the same end result. Could someone tell me what options I should select in the config so as to obtain a new kernel that will boot my RAID architecture ? I know that there are other ways to compile Debian kernels, using 'make-kpkg', but this does not work here, likely because this tool version is too old or too new for my system : it keeps saying that parameters are missing, while the howtos that I saw did not mention any such parameters for make-kpkg. By the way, I noticed that the initrd.img that I obtain using mkinitrd are about 5 times bigger than that which is used to boot my usual kernel. I am not sure that I am using mkinitrd correctly. mkinitrd -o initrd.img-2.6.26.2 2.6.26 done from /boot issues an error messages saying that this image will not take raid into account, and that therefore it won't boot, unless the main image contains what is missing here. In any case, it doesn't boot. The same command issued in /usr/src/linux-2.6.26.2 does not send any error message, but in the end the image doesn't boot either. Thanks in advance for your help why not just compile it on your notebook (or copy a compiled kernel) ?! you also can just disable the loading of the sound modules to make it more simple. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Sorry forgot to write Yes there is problem compiling the 2.6.20 with recent gcc The problem is the compiler. If you are compiling just grab the last version from kernel.org. 2.6.30.4 seems to be working fine So, upon my failures to recompile kernel 2.6.20-16-386, I tried downloading 2.6.20-17-386, but I got the same results. However, with 2.6.26.2, it did compile without errors... but in the end the image won't boot ! My compiling process does not generate initrd.img, so I did generate one using 'mkinitrd', and I wrote its path in /boot/grub/menu.lst with the kernel image. Here is what I get on booting trials : boot starts, as usual text displays very fast and you cannot read until it stops. When this happen, I can read this : md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 device mapper . no filesystem could mount root. Tried: cramfs kernel panic - not syncing: VFS unable to mount root fs on unknown block(0,0) try compiling the necessary modules _in_ the kernel. So, I re-tried compiling after de-activating raid0 in the config, leaving only raid1... to the same end result. In the config it should be [*] not [M] if booting from raid - do the same for LVM make make install make modules_install - do you really need kpkg ? mkinitrd -o initrd.img-2.6.26.2 2.6.26 done from /boot issues an error messages saying that this image will not take raid into account, and that therefore it won't boot, unless the main image contains what is missing here. In any case, it doesn't boot. The same command issued in /usr/src/linux-2.6.26.2 does not send any error message, but in the end the image doesn't boot either. do you have a not raid boot partition, where you can put the initrd image? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: Sorry forgot to write Yes there is problem compiling the 2.6.20 with recent gcc The problem is the compiler. If you are compiling just grab the last version from kernel.org. 2.6.30.4 seems to be working fine Just to be objective the gnu compiler people said kernel people are wrong and vice versa. I didn't follow the discussion. I'm glad next kernels compile regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: Bernard wrote: why not just compile it on your notebook (or copy a compiled kernel) ?! you also can just disable the loading of the sound modules to make it more simple. Things would be easy if all sound support were in modules. But some functions are part of the kernel and load with it. Because of this, I cannot compile a new sound system (OSS) without errors : it says that I have conflicting problems, even though I have blacklisted all sound modules. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: do you have a not raid boot partition, where you can put the initrd image? My boot partition is not raid, or, at least, even though it is mirrored, it remains in ext2fs, while the rest is in LVM2. So, the initrd image that I am trying is available at start, same with the one that works at every boot. If, for instance, I boot my system using a rescue disc or CD, I can't mount my '/' partition, but I mount '/boot' without problem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Emanoil Kotsev wrote: try compiling the necessary modules _in_ the kernel. This is the way it has been done. So, I re-tried compiling after de-activating raid0 in the config, leaving only raid1... to the same end result. In the config it should be [*] not [M] if booting from raid - do the same for LVM make make install make modules_install - do you really need kpkg ? No, except if it generates an initrd image easier than with mkinitrd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: problem compiling kernel
Bernard wrote: Emanoil Kotsev wrote: Bernard wrote: why not just compile it on your notebook (or copy a compiled kernel) ?! you also can just disable the loading of the sound modules to make it more simple. Things would be easy if all sound support were in modules. But some functions are part of the kernel and load with it. Because of this, I cannot compile a new sound system (OSS) without errors : it says that I have conflicting problems, even though I have blacklisted all sound modules. ah, I understand right now what you're trying to do - you need basic OSS/ALSA removed completely. which compiler versions do you have installed? On sarge the 2.6.20 should compile as far as I remember. You might have to set the right compiler I'm not sure I think 4.X is the one with the problem, so I would try with something older. The other thing would be to compile on another machine (you need to check options/Makefile for this) and move the images and drivers over (because the new OSS driver will probably fail with the old compiler ;) that would compile the older kernel ) regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: problem compiling kernel
From: news [mailto:n...@ger.gmane.org] On Behalf Of Emanoil Kotsev Sent: Friday, August 21, 2009 1:55 PM Bernard wrote: Emanoil Kotsev wrote: Bernard wrote: why not just compile it on your notebook (or copy a compiled kernel) ?! you also can just disable the loading of the sound modules to make it more simple. Things would be easy if all sound support were in modules. But some functions are part of the kernel and load with it. Because of this, I cannot compile a new sound system (OSS) without errors : it says that I have conflicting problems, even though I have blacklisted all sound modules. ah, I understand right now what you're trying to do - you need basic OSS/ALSA removed completely. which compiler versions do you have installed? On sarge the 2.6.20 should compile as far as I remember. You might have to set the right compiler I'm not sure I think 4.X is the one with the problem, so I would try with something older. The other thing would be to compile on another machine (you need to check options/Makefile for this) and move the images and drivers over (because the new OSS driver will probably fail with the old compiler ;) that would compile the older kernel ) regards The kernel in Lenny is compiled with the gcc-4.1 version. You should compile with whatever version the stock kernel was compiled with. If you're using something older than Lenny, the way I check is, open any module under /lib/modules/`uname -r` with vi, and search for GCC. You will see the version used. There might be an easier way, but I don't know it. -- Kevin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
About Compiling Kernel
Hi all, My box is on debian/testing, and I have compiled kernel by the debian way. Because it's testing and kernel-patches are often provided, I wonder whether I have to compile the kernel again after retrieving a kernel patch or even a new kernel via aptitude full-upgrade operation. Thanks for your suggestions. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problem with compiling kernel
On Tue, 08 May 2007 17:29:38 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: On Tue, 8 May 2007 16:11:54 -0400, Celejar [EMAIL PROTECTED] said: On Tue, 08 May 2007 12:47:28 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli [EMAIL PROTECTED] said: That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. Thanks for the vote of confidence, but you know, you should not have to do this. make-kpkg --rootcmd fakeroot kernel_image should work perfectly well. When I'm not being lazy, I often do it that way, largely because you suggest it in the docs. From /usr/share/doc/kernel-package/README.gz: With the addition of fakeroot ( a really nice program, I recommend it). Steps 1 to 4 can be carried out as a non root user. Step 5 does require root privileges. Hmm. I should amend that to say: Step 5 does require (fake)root privileges. Huh? Here's a longer excerpt: ---Begin Quote--- Phase ONE: Getting and configuring the kernel 1% cd kernel source tree (make sure you have write permission there) 2% make config # or make menuconfig or make xconfig (or, for 2.6.x kernels, make gconfig) and configure Phase TWO: Create a portable kernel image .deb file 3% make-kpkg clean 4% $Get_Root make-kpkg --revision=custom.1.0 kernel_image (Get_Root is whatever you need to become root -- fakeroot or sudo are examples that come to mind). NOTE: if you have instructed your boot loader to expect initrd kernels (which is the norm for recent official kernel image packages) you need to add --initrd to the line above. % $Get_Root make-kpkg --initrd --revision=custom.1.0 kernel_image Personally, I prefer non initrd images for my personal machines, since then adding third party modules to the machine has fewer gotchas Phase THREE: Install the kernel image on one or more machines 5# dpkg -i ../kernel-image-X.XXX_1.0_arch.deb 6# shutdown -r now # If and only if LILO/SILO/QUIK/PALO/VMELILO/ZIPL/yaboot/.. # worked or you have a means of # booting the new kernel. YOU HAVE BEEN WARNED!! With the addition of fakeroot ( a really nice program, I recommend it). Steps 1 to 4 can be carried out as a non root user. Step 5 does require root privileges. ---End quote--- So step 5 requires *real* root privileges, and it's step 4 that can be done with fakeroot, while steps 1-3 don't require any sort of root (provided you have write privileges in the appropriate directory. I did not mean it to be a suggestion; I only meant it was possible. Which it is. You wrote a really nice program, I recommend it. manoj -- Youth is such a wonderful thing. What a crime to waste it on children. George Bernard Shaw I see lots of web sites attributing this to Shaw, but they don't provide a source, and I've seen some people wondering aout the source. Do you know? Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Wed, 9 May 2007 15:32:08 -0400, Celejar [EMAIL PROTECTED] said: On Tue, 08 May 2007 17:29:38 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: Hmm. I should amend that to say: Step 5 does require (fake)root privileges. Huh? Here's a longer excerpt: Oops. I think I misrememberred step 4 as step 5. manoj -- Youth is such a wonderful thing. What a crime to waste it on children. George Bernard Shaw I see lots of web sites attributing this to Shaw, but they don't provide a source, and I've seen some people wondering aout the source. Do you know? Actually, I don't know offhand, and google is not being very helpful. manoj -- We don't care how they do it in New York. Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
pizzapie_linuxanchovies wrote: I was following a tutorial (http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for compiling a custom kernel, and got to the stage where it said to run this: fakeroot make-kpkg clean However, this command generated a bunch of errors saying this: dpkg-architecture: failure: dpkg --print-installation-architecture filed: Permission denied Now it's easy enough to see that only root has execute permission for dpkg on my machine. I guess I'm just wondering what a reasonable way to fix this problem is in Debian: 1. Create a new group for people allowed to run dpkg? 2. Run the command as sudo fakeroot make-kpkg clean? (sort of makes the whole fakeroot thing redundant?) 3. Something else? The list ethicist is going to get me for this but I always compile my kernels logged in as root. Never gives problems. So if you just now got the source ball then there is no need to run: make-kpkg clean because there are no drivers as of yet compiled at all, so nothing to clean. You do that if you run the compile a second time and changed loadable modules. Just go on with make-kpkg --append-to-version=.030320 kernel_image But what is the reason this is not: make-kpkg --initrd --append-to-version=.030320 kernel_image to also generate the initrd? What did you change in the make menuconfig? Or how did you change the config? I just changed: 1. Processor type and features - Paravirtualization support (EXPERIMENTAL) OFF 2. Processor type and features - Timer frequency (1000 HZ) 3. Processor type and features - Preemption Model (Preemptible Kernel (Low-Latency Desktop)) 4. Device Drivers - Graphics support - Logo configuration - Bootup logo ON 5. Kernel hacking - Show timing information on printks ON And the reasons: 1. This eliminates problems with nvidia drivers, which won't compile without this change on some architectures. 2. Makes the system more responsive 3. Makes the system more responsive 4. Gives me the duck at boot time ;-) 5. Shows kernel timing info. Let us know how you make out! Hugo Please someone who rolls their own kernel give me an idea about this? Thanks, Pizzapie P.S. I'm still using the venerable Sarge release. That should make no diff. (TM) I think. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
I just changed: 1. Processor type and features - Paravirtualization support (EXPERIMENTAL) OFF 2. Processor type and features - Timer frequency (1000 HZ) 3. Processor type and features - Preemption Model (Preemptible Kernel (Low-Latency Desktop)) 4. Device Drivers - Graphics support - Logo configuration - Bootup logo ON 5. Kernel hacking - Show timing information on printks ON And the reasons: 1. This eliminates problems with nvidia drivers, which won't compile without this change on some architectures. 2. Makes the system more responsive 3. Makes the system more responsive 4. Gives me the duck at boot time ;-) a duck? Wow, what a hack!! ;-) Hugo Me too compile kernels as root and really would like to know why it is considered such a bad habit. cheers raffaele
Re: Problem with compiling kernel
Raffaele Morelli wrote: I just changed: 1. Processor type and features - Paravirtualization support (EXPERIMENTAL) OFF 2. Processor type and features - Timer frequency (1000 HZ) 3. Processor type and features - Preemption Model (Preemptible Kernel (Low-Latency Desktop)) 4. Device Drivers - Graphics support - Logo configuration - Bootup logo ON 5. Kernel hacking - Show timing information on printks ON And the reasons: 1. This eliminates problems with nvidia drivers, which won't compile without this change on some architectures. 2. Makes the system more responsive 3. Makes the system more responsive 4. Gives me the duck at boot time ;-) a duck? Wow, what a hack!! ;-) Sorry, it was a joke... ;-) It's just the same Linux Logo. But with: kernel-patch-debianlogo it should be possible to create a duck... Hugo Me too compile kernels as root and really would like to know why it is considered such a bad habit. cheers raffaele -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, 8 May 2007 12:12:22 +0200 Raffaele Morelli [EMAIL PROTECTED] wrote: [snip] Me too compile kernels as root and really would like to know why it is considered such a bad habit. It's generally considered a bad idea to do anything as root unless it's absolutely necessary. I suppose it's one of those rules that's meant to be broken if you know what you're doing, but it's kind of a slippery slope; it's likely that sooner or later you'll do something that you'd regret less if you hadn't done it as root :). cheers raffaele Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
2007/5/8, Celejar [EMAIL PROTECTED]: On Tue, 8 May 2007 12:12:22 +0200 Raffaele Morelli [EMAIL PROTECTED] wrote: [snip] Me too compile kernels as root and really would like to know why it is considered such a bad habit. It's generally considered a bad idea to do anything as root unless it's absolutely necessary. I suppose it's one of those rules that's meant to be broken if you know what you're doing, but it's kind of a slippery slope; it's likely that sooner or later you'll do something that you'd regret less if you hadn't done it as root :). That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. Anyway I hope not to fall in the slippery slope. :-) As someone said: to err is human, but for a real disgrace you need the root password cheers raffaele Celejar raffaele
Re: Problem with compiling kernel
On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli [EMAIL PROTECTED] said: That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. Thanks for the vote of confidence, but you know, you should not have to do this. make-kpkg --rootcmd fakeroot kernel_image should work perfectly well. manoj -- The only way to learn a new programming language is by writing programs in it. Brian Kernighan Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, May 08, 2007 at 04:10:29PM +0200, Raffaele Morelli wrote: 2007/5/8, Celejar [EMAIL PROTECTED]: On Tue, 8 May 2007 12:12:22 +0200 Raffaele Morelli [EMAIL PROTECTED] wrote: [snip] Me too compile kernels as root and really would like to know why it is considered such a bad habit. It's generally considered a bad idea to do anything as root unless it's absolutely necessary. I suppose it's one of those rules that's meant to be broken if you know what you're doing, but it's kind of a slippery slope; it's likely that sooner or later you'll do something that you'd regret less if you hadn't done it as root :). That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. usually you only need root for make-install as that's what writes to various root-writable-only directories. A signature.asc Description: Digital signature
Problem with compiling kernel
Thanks to everyone who replied with ideas about my post. Let me give quick replies to the questions you asked me: Manoj--yes, dpkg is in /usr/bin, and is in the user's path, but no normal user has execute access to dpkg: $ ls -l /usr/bin/dpkg -rwxr-x--- 1 root root 174040 May 26 2005 /usr/bin/dpkg I temporarily removed bastille from my system, thinking maybe that changed permissions on dpkg, but that didn't help. Also, I tried dpkg-statoverride --list, but found no overrides on the permissions of dpkg. So I'm now reasonably sure Debian comes with only root having access to dpkg, despite it being in /usr/bin. John--yes I'm sure I have write access to the kernel source directory. Hugo--I think the initrd flag isn't necessary IF your kernel includes everything needed to read your boot sector. As for why I'm compiling the kernel/what changes I've made: the main thing I trying to do is get ACPI (sleep mode) working on my desktop, so I twiddling the ACPI-related flags and unchecking everything for APM in my kernel configure. Apart from that, just eliminating lots of modules for devices and filesystem types that I don't need, to make my kernel as small as possible (ASAP). The duck sounds nice ;-), but I already have a picture of some water or something at boot time, done using a framebuffer hack, IIRC. Andrew (and anyone else who can do a make-kpkg under a non-root account)--what permissions do YOU see when you say ls -l /usr/bin/root? Thanks again, Pizzapie Linux A. Wannabe PizzaPie [EMAIL PROTECTED] To email me please hold the anchovies and the .invalid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, 08 May 2007 12:47:28 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli [EMAIL PROTECTED] said: That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. Thanks for the vote of confidence, but you know, you should not have to do this. make-kpkg --rootcmd fakeroot kernel_image should work perfectly well. When I'm not being lazy, I often do it that way, largely because you suggest it in the docs. From /usr/share/doc/kernel-package/README.gz: With the addition of fakeroot ( a really nice program, I recommend it). Steps 1 to 4 can be carried out as a non root user. Step 5 does require root privileges. manoj -- The only way to learn a new programming language is by writing programs in it. Brian Kernighan Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, May 08, 2007 at 08:50:13PM +0200, pizzapie_linuxanchovies wrote: Andrew (and anyone else who can do a make-kpkg under a non-root account)--what permissions do YOU see when you say ls -l /usr/bin/root? I was referring to the general case of compiling source as a user and installing as root instead of doing the whole process as root. I'm not currently setup to make-kpkg under anything, much less a user. sorry A signature.asc Description: Digital signature
Re: Problem with compiling kernel
On Tue, 8 May 2007 20:50:13 +0200 (CEST), pizzapie linuxanchovies [EMAIL PROTECTED] said: Thanks to everyone who replied with ideas about my post. Let me give quick replies to the questions you asked me: Manoj--yes, dpkg is in /usr/bin, and is in the user's path, but no normal user has execute access to dpkg: $ ls -l /usr/bin/dpkg -rwxr-x--- 1 root root 174040 May 26 2005 /usr/bin/dpkg I temporarily removed bastille from my system, thinking maybe that changed permissions on dpkg, but that didn't help. Also, I tried dpkg-statoverride --list, but found no overrides on the permissions of dpkg. So I'm now reasonably sure Debian comes with only root having access to dpkg, despite it being in /usr/bin. Nope. However, it is reasonably easy to get reasonably sure: __ ll /usr/bin/dpkg 332 -rwxr-xr-x 1 root root 332556 2007-05-08 10:39 /usr/bin/dpkg __ dpkg-deb --contents dpkg_1.14.1_i386.deb | grep /usr/bin drwxr-xr-x root/root 0 2007-05-08 10:39 ./usr/bin/ -rwxr-xr-x root/root332556 2007-05-08 10:39 ./usr/bin/dpkg -rwxr-xr-x root/root 73252 2007-05-08 10:39 ./usr/bin/dpkg-query -rwxr-xr-x root/root192332 2007-05-08 10:39 ./usr/bin/dpkg-deb -rwxr-xr-x root/root 36556 2007-05-08 10:39 ./usr/bin/dpkg-split Andrew (and anyone else who can do a make-kpkg under a non-root account)--what permissions do YOU see when you say ls -l /usr/bin/root? __ ll /usr/bin/root ls: /usr/bin/root: No such file or directory I have never ever run make-kpkg as root. I don't think you should either. Unless you know something I don't? manoj -- Careful amidst the careless, amongst the sleeping wide-awake, the intelligent man leaves them all behind, like a race-horse does a mere hack. 29 Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, 8 May 2007 16:11:54 -0400, Celejar [EMAIL PROTECTED] said: On Tue, 08 May 2007 12:47:28 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli [EMAIL PROTECTED] said: That's ok, I follow the general (healthy) rule and do not log as root if unnecessary, but for kernel (and program) compile I can not picture 'make-kpkg' or 'configure make' doing something regrettable. Thanks for the vote of confidence, but you know, you should not have to do this. make-kpkg --rootcmd fakeroot kernel_image should work perfectly well. When I'm not being lazy, I often do it that way, largely because you suggest it in the docs. From /usr/share/doc/kernel-package/README.gz: With the addition of fakeroot ( a really nice program, I recommend it). Steps 1 to 4 can be carried out as a non root user. Step 5 does require root privileges. Hmm. I should amend that to say: Step 5 does require (fake)root privileges. I did not mean it to be a suggestion; I only meant it was possible. Which it is. manoj -- Youth is such a wonderful thing. What a crime to waste it on children. George Bernard Shaw Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with compiling kernel
I was following a tutorial (http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for compiling a custom kernel, and got to the stage where it said to run this: fakeroot make-kpkg clean However, this command generated a bunch of errors saying this: dpkg-architecture: failure: dpkg --print-installation-architecture filed: Permission denied Now it's easy enough to see that only root has execute permission for dpkg on my machine. I guess I'm just wondering what a reasonable way to fix this problem is in Debian: 1. Create a new group for people allowed to run dpkg? 2. Run the command as sudo fakeroot make-kpkg clean? (sort of makes the whole fakeroot thing redundant?) 3. Something else? Please someone who rolls their own kernel give me an idea about this? Thanks, Pizzapie P.S. I'm still using the venerable Sarge release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
On Tue, 8 May 2007 05:37:58 +0200 (CEST), pizzapie linuxanchovies [EMAIL PROTECTED] said: I was following a tutorial (http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for compiling a custom kernel, and got to the stage where it said to run this: fakeroot make-kpkg clean However, this command generated a bunch of errors saying this: dpkg-architecture: failure: dpkg --print-installation-architecture filed: Permission denied Now it's easy enough to see that only root has execute permission for dpkg on my machine. I guess I'm just wondering what a reasonable way to fix this problem is in Debian: Why is it only possible to run dpkg as root on your machine? __ dpkg --print-installation-architecture i386 That worked just fine as an ordinary user (and, dpkg is in /usr/bin -- which ought to be in the users path). So, the default in Debian is to allow ordinary users to run dpkg (well, some actions, like installing packages, require more privileges) manoj -- Acting is an art which consists of keeping the audience from coughing. Manoj Srivastava [EMAIL PROTECTED] http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with compiling kernel
pizzapie_linuxanchovies [EMAIL PROTECTED] writes: I was following a tutorial (http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for compiling a custom kernel, and got to the stage where it said to run this: fakeroot make-kpkg clean However, this command generated a bunch of errors saying this: dpkg-architecture: failure: dpkg --print-installation-architecture filed: Permission denied Are you sure that the user you are running under has write access to the kernel source directory? fakeroot doesn't actually give you root access, just merely pretend to give you access. -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel 2.6.16 or higher under Sarge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Aug 15, 2006 at 01:23:20PM -0700, shahim essaid.com wrote: Hi all, I am somewhat new to Debian and Iam not sure if this is possible. I want to compile a 2.6.16 from source but the minimum requirement listed under Documentation/Changes are not satisfied under Sarge. udev, for example, has to be 071 or higher. I did try backports.org but there were too many other dependencies and I didn't want to make all the changes without getting some advice first. Can I compile 2.6.16 from source under Sarge? I am assuming that even if I compile a kernel under unstable or testing, I will still need to meet the kernel requirements to be able to install it under Sarge. Am I correct? well, compiling is not a problem. i have 2 systems running a 2.6.17 kernel under sarge (2.6.17.3 and 2.6.17.6). there are a few things to be considered though: 1. if you want a modular kernel, you have to upgrade module-init-tools 2. if you want to use hotplug, you have to either upgrade to the new udev or switch to usbmgr 3. if you want to use initrd, you have to switch to initramfs-tools or yaird (for me yaird works better) 4. i think, i upgraded kernel-package from backports.org, don't know at the moment though... that said, everything you need you will find on backports.org (i hope i have not forgotten something imporant, the machine i'm currently sitting on is running sid) In case you are wondering why I am doing this, I would like to setup an IPSec firewall/router and my understanding is that for kernels below 2.6.16 I will have to apply netfilter/iptables patches to be able to use Policy Match and other features with Shorewall. Is this correct? I thought it was going to be easier to compile a recent kernel instead of figuring out the patches but it looks like this is just as difficult to follow. i don't know if you have to apply patches for the kernel below 2.6.16, though i belive there should also be newer kernel packages on backports.org ... yours Albert - -- Albert Dengg [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4uf0hrtSwvbWj0kRAlroAJ0YjxOorIK6lD04IMtz8SR1X8XTRACeOwYi tN9gSLIxVGpi7kf43slWgvc= =zAUH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Compiling kernel 2.6.17.4 or higher
Hi everyone! I'm trying to upgrade my 2.6.14.2 kernel in my server to a 2.6.17.4 or higher using my current .config. There isn't any problem in compiling time and in grub i put the same config but with different vmlinuz file, but when i reboot i get a kernel panic error like that Kernel panic: VFS: Unable to mount sda5 fs on unknown-block(0,0) Have anyone any idea? i'm using the same fstab and i'm using the same config only change the kernel. Maybe it can't detects SCSI drives? Thank you for your help and sorry for my poor english. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel 2.6.16 or higher under Sarge
shahim essaid.com wrote: Hi all, I am somewhat new to Debian and Iam not sure if this is possible. I want to compile a 2.6.16 from source but the minimum requirement listed under Documentation/Changes are not satisfied under Sarge. udev, for example, has to be 071 or higher. I've never followed the Current Minimal Requirements list, and have used the latest kernels for many years on all versions of Debian stable. I am currently running stock Sarge with linux 2.6.17.7. I did try backports.org but there were too many other dependencies and I didn't want to make all the changes without getting some advice first. Can I compile 2.6.16 from source under Sarge? I've done it, but would recommend the latest from kernel.org to get the newest security patches. The only problem with running the latest kernels is the occasional lemon. If that's a concern, you can hang back a few revs and follow the kernal lists and web sites. I am assuming that even if I compile a kernel under unstable or testing, I will still need to meet the kernel requirements to be able to install it under Sarge. Am I correct? All I can say is that I've not had any problems though I did not upgrade for server usage, but for mulimedia drivers. I use only stable Debian kernels for servers. In case you are wondering why I am doing this, I would like to setup an IPSec firewall/router and my understanding is that for kernels below 2.6.16 I will have to apply netfilter/iptables patches to be able to use Policy Match and other features with Shorewall. Is this correct? This patches business sounds like a nightmare. Instead you might download the latest stable kernel from kernel.org (currently 2.6.17.8). I thought it was going to be easier to compile a recent kernel instead of figuring out the patches but it looks like this is just as difficult to follow. More like nearly impossible, and what's the point since you give up stability anyway? Other distros feature the latest and greatest if that's what you need and Testing and Sid are for latest apps at the cost of stability. Thanks Shahim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel 2.6.17.4 or higher
Mario de Frutos wrote: I'm trying to upgrade my 2.6.14.2 kernel in my server to a 2.6.17.4 or higher using my current .config. There isn't any problem in compiling time and in grub i put the same config but with different vmlinuz file, but when i reboot i get a kernel panic error like that Kernel panic: VFS: Unable to mount sda5 fs on unknown-block(0,0) Did you create a ramdisk? (e.g. using make-kpkg with the --initrd option?) -- George Borisov DXSolutions Ltd signature.asc Description: OpenPGP digital signature
Compiling kernel 2.6.16 or higher under Sarge
Hi all, I am somewhat new to Debian and Iam not sure if this is possible. I want to compile a 2.6.16 from source but the minimum requirement listed under Documentation/Changes are not satisfied under Sarge. udev, for example, has to be 071 or higher. I did try backports.org but there were too many other dependencies and I didn't want to make all the changes without getting some advice first. Can I compile 2.6.16 from source under Sarge? I am assuming that even if I compile a kernel under unstable or testing, I will still need to meet the kernel requirements to be able to install it under Sarge. Am I correct? In case you are wondering why I am doing this, I would like to setup an IPSec firewall/router and my understanding is that for kernels below 2.6.16 I will have to apply netfilter/iptables patches to be able to use Policy Match and other features with Shorewall. Is this correct? I thought it was going to be easier to compile a recent kernel instead of figuring out the patches but it looks like this is just as difficult to follow. Thanks Shahim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem compiling kernel-headers-2.6.8-2-smp
Hello everybody. I am trying to install anbd on a PIII cluster, and for that I have to compile the module that they provide. But unfortunately, I am not being capable of compile this module agaist the kernel-headers-2.6.8-2-686-smp. make menuconfig works nicely, but when I try to make or make modules, I have this two messages: make make[1]: *** No rule to make target `init/main.o', needed by `init/built-in.o'. Stop. make: *** [init] Error 2 or make modules make[1]: *** No rule to make target `arch/i386/kernel/msr.c', needed by `arch/i386/kernel/msr.o'. Stop. make: *** [arch/i386/kernel] Error 2 ++ I have made make mrproper, make oldconfig, make menuconfig and configured everything, make clean to be sure that nothing is hanging, but with no luck. I have copied the nbd.h and nbd.c to the right places (include and drivers/block). So, what can be happening? Is there other way to compile this module? When I try to compile standalone, I have tons of error messages of missing libraries and dependencies. Thanks in advance. Ivan Marin -- --- Ivan S. P. Marin Laboratório de Física Computacional lfc.ifsc.usp.br Instituto de Física de São Carlos - USP --
Re: compiling kernel module question
On Sat, Nov 26, 2005 at 12:51:55AM -0500, Amish Rughoonundon wrote: lemme see if I understand what you meant: The kernel-source files that I downloaded is common to all linux distribution while the kernel-header files is particular to a certain version and distribution. ...not so much the distribution, but rather the _configuration_, i.e. the specific combination of switches that were selected while running one of make menuconfig, make xconfig (or even make config -- for those die-hards, who don't mind wading through hundreds of questions). This leaves behind a customized kernel source/header tree describing the specific kernel that will be (or has been) built from these sources. Think of it this way: when you buy a new PC, you make decisions as to which CPU, mobo, network- and graphics-card, etc. you want or need. Out of all conceivable combinations, you create a personalised configuration. Now, if you want to add another of piece hardware (a 'module') later, it's important (or at least useful) to know what your specific PC looks like. For example, if you were to ask here whether your favorite new geek gadget would work, and all you say is I have a computer, you'd get nothing more than one of those you'll need to tell us which ... replies :) (Of course, analogies don't ever match 100%, but this is about the idea...) When you build a custom kernel yourself, you'll automatically be left behind with configured kernel sources, but when you use a stock kernel, someone else has done this step for you. So, rather than starting with the pristine kernel sources and having to reproduce the exact settings that were used, it's easier to just get the preconfigured header packages. Cheers, Almut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
compiling kernel module question
Hi, I have been trying to compile and insert a simple kernel module but without luck. This is what I did. Since the freshly installed debian sarge 3.1 distro did not have any source files under /usr/src, I di uname -a to make sure of the kernel version that is installed: Linux test 2.4.27-2-386 #1 Mon May 16 16:47:51 JST 2005 i686 GNU/Linux and then I downloaded the kernel-source-2.4.27.tar.bz2, unziped and untarred it. I then copied this program from a book into example.c: #include linux/kernel.h#include linux/module.h#include linux/init.hstatic char __initdata hellomessage[] = KERN_NOTICE "Hello, world!\n";static char __exitdata byemessage[] = KERN_NOTICE "Goodbye, cruel world.\n";static int __init start_hello_world(void){printk(hellomessage);return 0;}static void __exit go_away(void){printk(byemessage);}module_init(start_hello_world);module_exit(go_away); I then compiled it using gcc -DMODULE -D__KERNEL__ -I/usr/src/kernel-source-2.4.27/include -c example.c I tried inserting it into the kernel using /sbin/insmod example.o but this is the message I got back: example.o: kernel-module version mismatch example.o was compiled for kernel version 2.6.0 while this kernel is version 2.4.27-2-386.example.o: cannot create /var/log/ksymoops/20051125172050.ksyms Permission denied I don't understand how it could have been compiled for a version of the kernel that I did not use. Thanks in advance. Amish
Re: compiling kernel module question
On Fri, Nov 25, 2005 at 05:36:26PM -0500, Amish Rughoonundon wrote: Hi, I have been trying to compile and insert a simple kernel module but without luck. This is what I did. Since the freshly installed debian sarge 3.1 distro did not have any source files under /usr/src, I di uname -a to make sure of the kernel version that is installed: Linux test 2.4.27-2-386 #1 Mon May 16 16:47:51 JST 2005 i686 GNU/Linux and then I downloaded the kernel-source-2.4.27.tar.bz2, unziped and untarred it. I then copied this program from a book into example.c: #include linux/kernel.h #include linux/module.h #include linux/init.h static char __initdata hellomessage[] = KERN_NOTICE Hello, world!\n; static char __exitdata byemessage[] = KERN_NOTICE Goodbye, cruel world.\n; static int __init start_hello_world(void) { printk(hellomessage); return 0; } static void __exit go_away(void) { printk(byemessage); } module_init(start_hello_world); module_exit(go_away); I then compiled it using gcc -DMODULE -D__KERNEL__ -I/usr/src/kernel-source-2.4.27/include -c example.c I tried inserting it into the kernel using /sbin/insmod example.o but this is the message I got back: example.o: kernel-module version mismatch example.o was compiled for kernel version 2.6.0 while this kernel is version 2.4.27-2-386. If you want to build kernel modules, you need to use the kernel headers _as configured for your current kernel_. The generic header files which come with the original kernel sources won't work... For a stock debian kernel such as 2.4.27-2-386, it's probably easiest to just install the respective packages * kernel-headers-2.4.27-2-386 (or kernel-headers-2.4-386 for that matter, which depends on kernel-headers-2.4.27-2-386), and * kernel-headers-2.4.27-2 (containing the header files common to all architectures, referenced via symlinks from within the -386 package). Then set your include path to -I/usr/src/kernel-headers-2.4.27-2-386/include. I'm not entirely sure how you got that 2.6.0 version into your module, but I guess the following happened: as there's no version.h in the unconfigured kernel sources, the file /usr/include/linux/version.h probably got pulled in instead (because it's on the standard include path)... However, these include files (though they're kernel headers, too) belong to libc, and must not necessarily match the current kernel version (in fact, I believe those in sarge are version 2.6.0 -- btw, this is the package linux-kernel-headers). If you're interested in what went wrong in your original attempt, you could run just the preprocessor (-E), and grep for version.h in its output gcc -DMODULE -D__KERNEL__ -I/usr/src/kernel-source-2.4.27/include -E example.c | grep version.h I'd think you see something like # 1 /usr/include/linux/version.h 1 3... Cheers, Almut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel module question
Thanks you were right on target with your answer, lemme see if I understand what you meant: The kernel-source files that I downloaded is common to all linux distribution while the kernel-header files is particular to a certain version and distribution. Thanks a lot for taking the time to help me out, Amish - Original Message - From: Almut Behrens [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Friday, November 25, 2005 9:43 PM Subject: Re: compiling kernel module question On Fri, Nov 25, 2005 at 05:36:26PM -0500, Amish Rughoonundon wrote: Hi, I have been trying to compile and insert a simple kernel module but without luck. This is what I did. Since the freshly installed debian sarge 3.1 distro did not have any source files under /usr/src, I di uname -a to make sure of the kernel version that is installed: Linux test 2.4.27-2-386 #1 Mon May 16 16:47:51 JST 2005 i686 GNU/Linux and then I downloaded the kernel-source-2.4.27.tar.bz2, unziped and untarred it. I then copied this program from a book into example.c: #include linux/kernel.h #include linux/module.h #include linux/init.h static char __initdata hellomessage[] = KERN_NOTICE Hello, world!\n; static char __exitdata byemessage[] = KERN_NOTICE Goodbye, cruel world.\n; static int __init start_hello_world(void) { printk(hellomessage); return 0; } static void __exit go_away(void) { printk(byemessage); } module_init(start_hello_world); module_exit(go_away); I then compiled it using gcc -DMODULE -D__KERNEL__ -I/usr/src/kernel-source-2.4.27/include -c example.c I tried inserting it into the kernel using /sbin/insmod example.o but this is the message I got back: example.o: kernel-module version mismatch example.o was compiled for kernel version 2.6.0 while this kernel is version 2.4.27-2-386. If you want to build kernel modules, you need to use the kernel headers _as configured for your current kernel_. The generic header files which come with the original kernel sources won't work... For a stock debian kernel such as 2.4.27-2-386, it's probably easiest to just install the respective packages * kernel-headers-2.4.27-2-386 (or kernel-headers-2.4-386 for that matter, which depends on kernel-headers-2.4.27-2-386), and * kernel-headers-2.4.27-2 (containing the header files common to all architectures, referenced via symlinks from within the -386 package). Then set your include path to -I/usr/src/kernel-headers-2.4.27-2-386/include. I'm not entirely sure how you got that 2.6.0 version into your module, but I guess the following happened: as there's no version.h in the unconfigured kernel sources, the file /usr/include/linux/version.h probably got pulled in instead (because it's on the standard include path)... However, these include files (though they're kernel headers, too) belong to libc, and must not necessarily match the current kernel version (in fact, I believe those in sarge are version 2.6.0 -- btw, this is the package linux-kernel-headers). If you're interested in what went wrong in your original attempt, you could run just the preprocessor (-E), and grep for version.h in its output gcc -DMODULE -D__KERNEL__ -I/usr/src/kernel-source-2.4.27/include -E example.c | grep version.h I'd think you see something like # 1 /usr/include/linux/version.h 1 3... Cheers, Almut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On 9/22/05, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE-Hash: SHA1L.V.Gandhi on Monday 19 Sep 2005 12:46 wrote: I have found the problem with debian apt-get kernel which contains debian patches.Debian shipped kernels don't come with with bootsplash patch included. Instead bootsplash patch is provided as a separate package which you candownload and patch to your Debian shipped kernels.As I have mentioned in my earlier post, I tried to patch stock debian kernel source with bootsplash patch. Then I got error msg. However with kernel org 2.6.13.1 kernel didn't give me error.-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 L.V.Gandhi on Monday 19 Sep 2005 12:46 wrote: On 9/17/05, Kumar Appaiah [EMAIL PROTECTED] wrote: I don't know whether this is a stupid doubt, but are you using `pristine' kernel sources or Debian patched kernel sources (apt-got ones)? I generally have had no problems applying the bootsplash patches to pristine kernel sources. I have found the problem with debian apt-get kernel which contains debian patches. Debian shipped kernels don't come with with bootsplash patch included. Instead bootsplash patch is provided as a separate package which you can download and patch to your Debian shipped kernels. rrs - -- Ritesh Raj Sarraf RESEARCHUT -- http://www.researchut.com Gnupg Key ID: 04F130BC Stealing logic from one person is plagiarism, stealing from many is research. Necessity is the mother of invention. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDMbdR4Rhi6gTxMLwRAmoAAKC1EVOQl5+uCgarLH5twKd7bzHnoQCdHEf8 i5oEfDji9rzKLTfhuj9RlM8= =8tTM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]