Re: Compiling kernel from Github - Howto?
csanyi...@gmail.com writes: > Gary Dale 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?
Gary Dale 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
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=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=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: 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
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!
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 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. 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.
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. 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.
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.
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 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.
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, 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.
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 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.
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 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
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
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 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.
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
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
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 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 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
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.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]
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]
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:
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
#include
#include
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 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
> #include
> #include
> 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 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]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
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. -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
David R. Litwin wrote: Before I go any further, yes, I need bootsplash: My computer is dual-boot and the other user insists on A: Using Windows and B: Shutting Down every Evening. In addition, I shall be getting a lap-top soon. (By the bye, why doesn't Debian have Bootsplash as a standard?) I know I need to compile a kernel (which I can do with synaptic and kernel-package) and then patch it. I do not know how. I have skimmed through a HOWTO or three. However, they aren't quite answering my questions. So, allow me to elaborate, if you will. Firstly, I need to get linux-source-2.6.12 from the Debian archives (with Synaptic, in my case). Do I need linux-patch-debian-2.6.12 or linux-tree-2.6.12? Next, I need use kernel-package. How do I do this? What of menuconfig or some such thing? Must I 'do' this as well? There is also the matter of Patching. When and how do I do this so that I will have Bootsplash? There is an entry for Sources.list, so I can acquire that which I need from the Bootsplash web-site. But, what do I need? How do I implement this? I know that this makes me sound like a newby; well, I fairly much am. Not so much that I won't know the slightest thing that you're talking of; I'm just really concerned about screwing up me system and making it un-usable. That's the only reason I'm asking, in fact. I'm not adverse to reading HOWTOs, as long as they answer all of the questions that I have asked: I know that some do not mention apt-get, which makes me think that they are not Debian specific; which is what I need. I just got through doing that and I followed this: http://olterman.homelinux.net/?page=fbsplash&dir=Tutorials Found it very useful. It works well. I had to set his --cmd= parm in rc and rcS to "repaint" rather than "paint" because it would not show the background after console-screen.sh runs. Also I adjusted his textscreen to offset 0,0 because it screwed up my vcstimed that displays things in the upper right hand corner. BTW, to the remark: "but we don't boot that often..." that all depends on where you live. In Mexico I have lots of power hits, so you boot a lot, even it is just nervousness... HTH H -- 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 Sat, Sep 17, 2005 at 05:38:03AM +0530, L.V.Gandhi wrote: >I have 2.6.8 kernel source. I tried the following both patches separately >in the same order. ie second time src previous patched source was deleted >and new src was installed. >bootsplash-3.1.6-2.6.8.diff >bootsplash-3.1.4-sp3-2.6.8.1.diff >both patches gave nearly same error. Following error is for second one. >First patch also gave error as Hunk #1 FAILED at 989 instaed of Hunk #1 >FAILED at 988. However bootsplash works. But I want to know the >significance of file n_tty.c and patch to it. [snip] 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. > As side note I found an interesting thing, that I wanted to share with >the list.We can have two screens one for booting and other for shutdown. >First make boot screen, put it in /etc/bootsplash/themes/name>/images and do (as example) [snip] Nice suggestion. It's great! Kumar -- Kumar Appaiah, 462, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 signature.asc Description: Digital signature
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On 9/14/05, Pooly <[EMAIL PROTECTED]> wrote:
2005/9/6, mess-mate <[EMAIL PROTECTED]>:> | Basically, the steps are:> |> | 1. Download the kernel source> |> | 2. Extract it to /usr/src, or wherever you'd prefer
> |> | 3. Download the bootsplash patch from http://www.bootsplash.de/files/> |> | 4. 'cd' into the extracted kernel source directory and run 'patch -p1
> |/path/to/bootsplash.diff'> |> | 5. Run 'make menuconfig', customize as needed, and be sure to set> |CONFIG_BOOTSPLASH=y> |> | 6. Run 'make-kpkg kernel_image'. See /usr/share/doc/kernel-packages for
> |lots more info.> |> | 7. Use 'dpkg -i' to install the newly build kernel package> |> | > Next, I need use kernel-package. How do I do this? What of menuconfig or some> | > such thing? Must I 'do' this as well?
> | >> | > There is also the matter of Patching. When and how do I do this so that I will> | > have Bootsplash? There is an entry for Sources.list, so I can acquire that> | > which I need from the Bootsplash web-site. But, what do I need? How do I
> | > implement this?> |> | Add to the /etc/apt/sources.list:> |> | deb http://debian.bootsplash.de unstable main> |> | And then install:
> |> | bootsplash> | bootsplash-theme-whatever> |> | And probably sysv-rc-bootsplash if you want a working progress bar.> | It looks like they also have some packages for apply the kernel patch,
> | but I've never bothered with those.> |> | I think that's about it...> |> | --> Thanks for the tut..> But after downloading a vanilla linux-2.6.12.6 kernel,> the patch -p1 --verbose
bootsplash-3.1.6-2.6.12.diff> don't work. (nothing happen)> Have to ^c to stop it after 30min.patch was waiting for user input...try that instead (or read the doc ;-) patch -p1 --verbose <
bootsplash-3.1.6-2.6.12.diff>>> mess-mate> --> You have a will that can be influenced by all with whom you come in contact.I
have 2.6.8 kernel source. I tried the following both patches separately
in the same order. ie second time src previous patched source was
deleted and new src was installed.
bootsplash-3.1.6-2.6.8.diff
bootsplash-3.1.4-sp3-2.6.8.1.diff
both patches gave nearly same error. Following error is for second one.
First patch also gave error as Hunk #1 FAILED at 989 instaed of Hunk #1
FAILED at 988. However bootsplash works. But I want to know the
significance of file n_tty.c and patch to it.
Hunk #1 FAILED at 988.
Hunk #2 succeeded at 1322 (offset 242 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/char/n_tty.c.rej
--
lvghomepc:/usr/src/linux# cat drivers/char/n_tty.c.rej
***
*** 988,994
printk("n_tty_read_chan: called with read_buf == NULL?!?\n");
return -EIO;
}
-
/* Job control check -- must be done at start and after
every sleep (POSIX.1 7.1.1.4). */
/* NOTE: not yet done after every sleep pending a thorough
--- 988,993
printk("n_tty_read_chan: called with read_buf == NULL?!?\n");
return -EIO;
}
/* Job control check -- must be done at start and after
every sleep (POSIX.1 7.1.1.4). */
/* NOTE: not yet done after every sleep pending a thorough
--
As side note I found an interesting thing, that I wanted to share
with the list.We can have two screens one for booting and other for
shutdown. First make boot screen, put it in
/etc/bootsplash/themes//images and do (as example)
splash -s -f /etc/bootsplash/themes/debian-sarge/config/bootsplash-1024x768.cfg >>initrd.img-2.6.8.20050916
Then make shutdown screen and replace the boot screen image in
/etc/bootsplash/themes//images. Now boot screen and
shutdown screens will be different.-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Wed, 14 Sep 2005 12:06:10 +0530 "L.V.Gandhi" <[EMAIL PROTECTED]> wrote: > What is this boot-icons package. I don't have in stable repository. Hmmm, I guess boot-icons never made it out of unstable. http://packages.debian.org/cgi-bin/search_packages.pl?keywords=boot-icon&searchon=names&subword=1&version=unstable&release=all "Display boot progress using graphical icons 0.5: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc" It has been quite a while since I installed boot-icons and it has been sitting forgotten on my machine until I recently installed splashy and switched to grub as my boot loader and in the process of getting splashy to work the boot icons started working also. Later, Seeker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
2005/9/6, mess-mate <[EMAIL PROTECTED]>: > Brian Nelson <[EMAIL PROTECTED]> wrote: > | "David R. Litwin" <[EMAIL PROTECTED]> writes: > | > | > Before I go any further, yes, I need bootsplash: My computer is dual-boot > and > | > the other user insists on A: Using Windows and B: Shutting Down every > Evening. > | > In addition, I shall be getting a lap-top soon. (By the bye, why doesn't > | > Debian have Bootsplash as a standard?) > | > > | > I know I need to compile a kernel (which I can do with synaptic and > | > kernel-package) and then patch it. > | > > | > I do not know how. > | > > | > I have skimmed through a HOWTO or three. However, they aren't quite > answering > | > my questions. So, allow me to elaborate, if you will. > | > > | > Firstly, I need to get linux-source-2.6.12 from the Debian archives (with > | > Synaptic, in my case). Do I need linux-patch-debian-2.6.12 or > | > linux-tree-2.6.12? > | > | I find it easiest to just grab the vanilla sources straight from > | kernel.org. The Debian ones tend to be crippled and patched, which > | makes it a pain to apply new patches. > | > | Basically, the steps are: > | > | 1. Download the kernel source > | > | 2. Extract it to /usr/src, or wherever you'd prefer > | > | 3. Download the bootsplash patch from http://www.bootsplash.de/files/ > | > | 4. 'cd' into the extracted kernel source directory and run 'patch -p1 > |/path/to/bootsplash.diff' > | > | 5. Run 'make menuconfig', customize as needed, and be sure to set > |CONFIG_BOOTSPLASH=y > | > | 6. Run 'make-kpkg kernel_image'. See /usr/share/doc/kernel-packages for > |lots more info. > | > | 7. Use 'dpkg -i' to install the newly build kernel package > | > | > Next, I need use kernel-package. How do I do this? What of menuconfig or > some > | > such thing? Must I 'do' this as well? > | > > | > There is also the matter of Patching. When and how do I do this so that I > will > | > have Bootsplash? There is an entry for Sources.list, so I can acquire that > | > which I need from the Bootsplash web-site. But, what do I need? How do I > | > implement this? > | > | Add to the /etc/apt/sources.list: > | > | deb http://debian.bootsplash.de unstable main > | > | And then install: > | > | bootsplash > | bootsplash-theme-whatever > | > | And probably sysv-rc-bootsplash if you want a working progress bar. > | It looks like they also have some packages for apply the kernel patch, > | but I've never bothered with those. > | > | I think that's about it... > | > | -- > Thanks for the tut.. > But after downloading a vanilla linux-2.6.12.6 kernel, > the patch -p1 --verbose bootsplash-3.1.6-2.6.12.diff > don't work. (nothing happen) > Have to ^c to stop it after 30min. patch was waiting for user input... try that instead (or read the doc ;-) patch -p1 --verbose < bootsplash-3.1.6-2.6.12.diff > > > mess-mate > -- > You have a will that can be influenced by all with whom you come in contact. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Pooly Webzine Rock : http://www.w-fenec.org/
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On 9/14/05, Seeker5528 <[EMAIL PROTECTED]> wrote: On Mon, 12 Sep 2005 18:01:47 +0530"L.V.Gandhi" <[EMAIL PROTECTED]> wrote:> > On a side note I had installed the boot-icons package sometime in the > > past and never got around to getting it operational and it started> > working too.> >> > I installed it. It shows tux image. No show of % progress of booting or> any progress bar. Other than tux image, what is it supposed to do? How to > configure it to get that.The progress bar stopped working for me on one of my kernel upgrades,but then there was a splashy update that fixed it after that, I didn'tdo any poking around while it was broken to attempt fixing it and both have had updates since then without losing the progress bar.The boot-icons package when used by it's self should give you iconsaccross the top of the screen indicating the progress, while the textscrolls below as normal. In combination with splashy I see the first progress icon, then thesplashy image, then the rest of the progress icons display over thetop of the splashy image.Also if you are running a stock debian kernel with grub as the boot loader you should not edit the automagic kernel entries you shouldinstead find the kopt= line it the grub menu.lst file:# kopt=root=/dev/hda3 ro: and add the vga= option for whatever mode you prefer there: # kopt=root=/dev/hda3 ro vga=0x317: keeping the hash symbol as indicated at the top of the file. Then opena terminal window and type:update-grub: to activate the change. Using this method the option will be carried forward as you install kernel updates.Thanks for the response. splashy-0.1.5 versions didn't show progress bar with debian sarge stock 2.6.8-2-386 kernel. But version 0.1.4 has given me the picture and progress bar while 0.1.5 gave only picture not progress bar. Thanks for the tip of not removing hash in front of kopt. I will try with that. What is this boot-icons package. I don't have in stable repository.-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, 12 Sep 2005 18:01:47 +0530 "L.V.Gandhi" <[EMAIL PROTECTED]> wrote: > > On a side note I had installed the boot-icons package sometime in the > > past and never got around to getting it operational and it started > > working too. > > > > I installed it. It shows tux image. No show of % progress of booting or > any progress bar. Other than tux image, what is it supposed to do? How to > configure it to get that. The progress bar stopped working for me on one of my kernel upgrades, but then there was a splashy update that fixed it after that, I didn't do any poking around while it was broken to attempt fixing it and both have had updates since then without losing the progress bar. The boot-icons package when used by it's self should give you icons accross the top of the screen indicating the progress, while the text scrolls below as normal. In combination with splashy I see the first progress icon, then the splashy image, then the rest of the progress icons display over the top of the splashy image. Also if you are running a stock debian kernel with grub as the boot loader you should not edit the automagic kernel entries you should instead find the kopt= line it the grub menu.lst file: # kopt=root=/dev/hda3 ro : and add the vga= option for whatever mode you prefer there: # kopt=root=/dev/hda3 ro vga=0x317 : keeping the hash symbol as indicated at the top of the file. Then open a terminal window and type: update-grub : to activate the change. Using this method the option will be carried forward as you install kernel updates. Later, Seeker -- 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/13/05, David R. Litwin <[EMAIL PROTECTED]> wrote: The link I provide let me set up Splashy with relative ease. I should think, off hand, that you need to edit the config.xml file located in the splashy directory. Read the readme that comes along with your theme. http://ubuntuforums.org/showthread.php?t=41709 I installed it. It shows tux image. No show of % progress of booting or any progress bar. Other than tux image, what is it supposed to do? How to configure it to get that.I have gone through the page. But it doesn't give any info regarding missing progress bar. Any help regarding progress bar is appreciated.-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
David R. Litwin wrote: > Bob Proulx wrote: > > The only reason I was dragged in was that I fell for your > > troll. > > Did you mean MY troll? I hope that what I have written does not appear to be > a troll! I'm just asking questions: I'm very curious. I'm terribly sorry if > I sound mean. I'm really not terribly good at writing E-Mails. Let me apologize for the mixup. The part I was referring to was written by Brian Nelson. For some reason I read your followup about the binary blobs after Brian's posting about the crippled kernel and got them mixed up. I am very sorry for that. Please accept my apology. Bob signature.asc Description: Digital signature
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
The link I provide let me set up Splashy with relative ease. I should think, off hand, that you need to edit the config.xml file located in the splashy directory. Read the readme that comes along with your theme. http://ubuntuforums.org/showthread.php?t=41709 I installed it. It shows tux image. No show of % progress of booting or any progress bar. Other than tux image, what is it supposed to do? How to configure it to get that.-- —A watched bread-crumb never boils.—My hover-craft is full of eels.—‽ <--You've just been Interrobanged.—[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On 9/10/05, Seeker5528 <[EMAIL PROTECTED]> wrote: On Mon, 05 Sep 2005 21:55:31 -0700Jeff D <[EMAIL PROTECTED]> wrote:> what about using splashy? it doesn't require a kernel rebuild and is in> experimental or you can add: >> deb http://splashy.Alioth.debian.org/debian/ unstable main> deb-src http://splashy.Alioth.debian.org/debian/ unstable mainI second that nomination.I'm using splashy and it works pretty well.On a side note I had installed the boot-icons package sometime in thepast and never got around to getting it operational and it started working too.I installed it. It shows tux image. No show of % progress of booting or any progress bar. Other than tux image, what is it supposed to do? How to configure it to get that.-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, 05 Sep 2005 21:55:31 -0700 Jeff D <[EMAIL PROTECTED]> wrote: > what about using splashy? it doesn't require a kernel rebuild and is in > experimental or you can add: > > deb http://splashy.Alioth.debian.org/debian/ unstable main > deb-src http://splashy.Alioth.debian.org/debian/ unstable main I second that nomination. I'm using splashy and it works pretty well. On a side note I had installed the boot-icons package sometime in the past and never got around to getting it operational and it started working too. Later, Seeker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
The only reason I was dragged in was that I fell for yourtroll. Did you mean MY troll? I hope that what I have written does not appear to be a troll! I'm just asking questions: I'm very curious. I'm terribly sorry if I sound mean. I'm really not terribly good at writing E-Mails. -- —A watched bread-crumb never boils.—My hover-craft is full of eels.—‽ <--You've just been Interrobanged.—[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
Brian Nelson wrote: > [EMAIL PROTECTED] (Bob Proulx) writes: > >> I find it easiest to just grab the vanilla sources straight from > >> kernel.org. The Debian ones tend to be crippled and patched, which > >> makes it a pain to apply new patches. > > > > I always find it easier to use the Debian stock kernels. They have > > all of the toys preconfigured and patches can be easily applied. > > > > (Just to make a counter case because I think using both Debian patched > > kernel source an using upstream kernel.org source are valid. But I > > don't think the Debian source is crippled in any way. If you think it > > is then please file a bug in the BTS about it.) > > The kernel packagers remove drivers that have embedded firmware blobs > due to lack of source for the blobs. See for example: > > http://bugs.debian.org/239952 I will try to avoid the whole non-DFSG and legal question debate (again) here because it usually goes on forever and just acknowledge your point. The only reason I was dragged in was that I fell for your troll. Bob signature.asc Description: Digital signature
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
Brian Nelson <[EMAIL PROTECTED]> wrote: | "David R. Litwin" <[EMAIL PROTECTED]> writes: | | > Before I go any further, yes, I need bootsplash: My computer is dual-boot and | > the other user insists on A: Using Windows and B: Shutting Down every Evening. | > In addition, I shall be getting a lap-top soon. (By the bye, why doesn't | > Debian have Bootsplash as a standard?) | > | > I know I need to compile a kernel (which I can do with synaptic and | > kernel-package) and then patch it. | > | > I do not know how. | > | > I have skimmed through a HOWTO or three. However, they aren't quite answering | > my questions. So, allow me to elaborate, if you will. | > | > Firstly, I need to get linux-source-2.6.12 from the Debian archives (with | > Synaptic, in my case). Do I need linux-patch-debian-2.6.12 or | > linux-tree-2.6.12? | | I find it easiest to just grab the vanilla sources straight from | kernel.org. The Debian ones tend to be crippled and patched, which | makes it a pain to apply new patches. | | Basically, the steps are: | | 1. Download the kernel source | | 2. Extract it to /usr/src, or wherever you'd prefer | | 3. Download the bootsplash patch from http://www.bootsplash.de/files/ | | 4. 'cd' into the extracted kernel source directory and run 'patch -p1 |/path/to/bootsplash.diff' | | 5. Run 'make menuconfig', customize as needed, and be sure to set |CONFIG_BOOTSPLASH=y | | 6. Run 'make-kpkg kernel_image'. See /usr/share/doc/kernel-packages for |lots more info. | | 7. Use 'dpkg -i' to install the newly build kernel package | | > Next, I need use kernel-package. How do I do this? What of menuconfig or some | > such thing? Must I 'do' this as well? | > | > There is also the matter of Patching. When and how do I do this so that I will | > have Bootsplash? There is an entry for Sources.list, so I can acquire that | > which I need from the Bootsplash web-site. But, what do I need? How do I | > implement this? | | Add to the /etc/apt/sources.list: | | deb http://debian.bootsplash.de unstable main | | And then install: | | bootsplash | bootsplash-theme-whatever | | And probably sysv-rc-bootsplash if you want a working progress bar. | It looks like they also have some packages for apply the kernel patch, | but I've never bothered with those. | | I think that's about it... | | -- Thanks for the tut.. But after downloading a vanilla linux-2.6.12.6 kernel, the patch -p1 --verbose bootsplash-3.1.6-2.6.12.diff don't work. (nothing happen) Have to ^c to stop it after 30min. mess-mate -- You have a will that can be influenced by all with whom you come in contact. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
David R. Litwin wrote: Before I go any further, yes, I need bootsplash: My computer is dual-boot and the other user insists on A: Using Windows and B: Shutting Down every Evening. In addition, I shall be getting a lap-top soon. (By the bye, why doesn't Debian have Bootsplash as a standard?) what about using splashy? it doesn't require a kernel rebuild and is in experimental or you can add: deb http://splashy.Alioth.debian.org/debian/ unstable main deb-src http://splashy.Alioth.debian.org/debian/ unstable main to your sources list .. easier than a recompile and pretty much does the same thing. see: http://splashy.alioth.debian.org/ hth jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
Isn't this perhaps the problem? I've been trying to get to gripswith debian for years and I haven't ventured outside stable. I still feel out of my depth and - no offence meant, honestly -you're obviously out of your depth and you shouldn't think youhave the right to demand answers to all your questions.Why not get some experience with sarge? If it hasn't got what you want, try another distribution or go back to Windows?I do understand well what you are saying. That is why I waited so long to say I had Sid: I knew this would happen.Allow me to answer. I have Sid because it has things that are new and Shiny. I am compulsive in that way, using Synaptic to see if there are any upgrades available many, many times daily. I have read many things and found (in general) the following to be true (which was backed up by a computer-savvy acquaintance of mine): Stable is for Servers (those who need a STABLE system. I do believe that Debian Stable is one of the most stable O. S.s available.), Testing fine (indeed!) for most, Unstable not really unstable at all. Minus the things that are currently happening (getting over the shift to Xorg, updating KDE and things that go along with it), unstable is really the Debian Definition. For the average computer fellow, he won't notice any glitches. So, why not have the newest and best? And, besides, maybe I'll find a bug some day and get to report it (or, at least, give it to some one who will report it properly). I've probably learnt more from using Sid than from using Testing or Stable combined. Windows? Simply, I'm hooked on Linux.Recap: I'll stick with Sid, understanding that things may be harder to resolve and that some may be less willing. And, I won't use Windows if I can help it. But, verily, I do comprehend what you are saying; fear not that your message has gone un-heeded. -- —A watched bread-crumb never boils.—My hover-craft is full of eels.—‽ <--You've just been Interrobanged.—[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, 5 Sep 2005 20:02:55 -0700 (PDT) Alvin used the keyboard to craft this: >|bad boy ... >| >|i asume you do know, that your system is statisticly more likely >|to die exponentionally each time you reboot your PC.. the more >|you reboot it, the lifespan of your machine just wend down significantly Really or is this just another urban myth. I had a laptop running windows, powered by a generator [really bad] for 5 years, then mains power when I moved, and it ran for another 3 years, used all the time, booted at least once, usually many more times a a day. But then the 850MB hard drive started to get develop some bad blocks, and the m/b battery died and I allowed it to rest. 8 out of 10 ain't bad. Windows crashed sometimes, but not that often. I have read some posts on this rebooting, many times. Opinion seems to vary, and am on my second lappy at the moment. This time on deep cycle batteries, charged by solar panels and generator at times. Gets booted at least 3 times a day for the last 12 months. Often more some days. Dependant on power, so must be switched off. I will see how long its hardware lasts. It would also depend on the make and model of each machine, I would think, and it would also depend on each piece of hardware. I just tend to question everything. +++ Registered Linux User:- 329524 +++ Whether the flower looks better in the nosegay than in the meadow where it grew and we had to wet our feet to get it! Is the scholastic air any advantage? ...Henry David Thoreau *** Really starting to enjoy Linux Debian Sarge _ -- 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 Mon, Sep 05, 2005 at 10:51:46PM -0400, David R. Litwin wrote: > I'm using Sid Isn't this perhaps the problem? I've been trying to get to grips with debian for years and I haven't ventured outside stable. I still feel out of my depth and - no offence meant, honestly - you're obviously out of your depth and you shouldn't think you have the right to demand answers to all your questions. Why not get some experience with sarge? If it hasn't got what you want, try another distribution or go back to Windows? Again, please don't take offence, but you have to be realistic. Cheers, David -- David Jardine "Running Debian GNU/Linux and loving every minute of it." -L. von Sacher-M.(1835-1895) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
[EMAIL PROTECTED] (Bob Proulx) writes: >> I find it easiest to just grab the vanilla sources straight from >> kernel.org. The Debian ones tend to be crippled and patched, which >> makes it a pain to apply new patches. > > I always find it easier to use the Debian stock kernels. They have > all of the toys preconfigured and patches can be easily applied. > > (Just to make a counter case because I think using both Debian patched > kernel source an using upstream kernel.org source are valid. But I > don't think the Debian source is crippled in any way. If you think it > is then please file a bug in the BTS about it.) The kernel packagers remove drivers that have embedded firmware blobs due to lack of source for the blobs. See for example: http://bugs.debian.org/239952 -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
You don't need grub to use linux, lilo can be used instead. I prefer lilo togrub. I actually started my Linux days with LILO. I like GRUB more. IMHO, grub is too flexible.If I may: Huh? How can some thing be too flexible? This is most interesting.-- —A watched bread-crumb never boils.—My hover-craft is full of eels. —‽ <--You've just been Interrobanged.—[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, Sep 05, 2005 at 10:51:46PM -0400, David R. Litwin wrote: snip... > Also, one good-man mentioned that I would need to configure GRUB when I > install the kernel. Every time I have apt-got a linux-image, it says it is > searching for GRUB and modifying it accordingly (and, in fact, also for > Bootsplash). Why wouldn't it work this time? How can I configure GRUB when I > need GRUB to access linux? You don't need grub to use linux, lilo can be used instead. I prefer lilo to grub. IMHO, grub is too flexible. But I am using sarge, maybe lilo has been removed in etch. -- Paul E Condon [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 Mon, 5 Sep 2005, David R. Litwin wrote: > > My appologies: I really, really want Bootsplash. than you be able to make it work "yourself", as it is tons of work > As I wrote (and so alluded to), my computer IS re-booted quite a bit. bad boy ... i asume you do know, that your system is statisticly more likely to die exponentionally each time you reboot your PC.. the more you reboot it, the lifespan of your machine just wend down significantly - i bet you do not have working PCs that are 10 years old and still doing its mail/web magic > Besides, it's æsthetically pleasing (to me) than when bootsplash is working, you'd be a happy genious > Any way, have you any advice to get me closer to me goal of > Bootsplashedness? http://linux-boot.net/Splash/ and doing "x11" stuff in framebuffer is equally fun and a good techi-ness status c ya alvin
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
All was going well until:$ make xconfig** Unable to find the QT installation. Please make sure that the* QT development package is correctly installed and the QTDIR* environment variable is set to the correct location. *make[1]: *** [scripts/kconfig/.tmp_qtcheck] Error 1make: *** [xconfig] Error 2I looked in Synaptic for qt-dev and the closest I found was: qt4-dev-tools. Is that what I need? Won't that screw with KDE (I'm using Sid and haven't upgraded any thing involving KDE and its components)? Also, one good-man mentioned that I would need to configure GRUB when I install the kernel. Every time I have apt-got a linux-image, it says it is searching for GRUB and modifying it accordingly (and, in fact, also for Bootsplash). Why wouldn't it work this time? How can I configure GRUB when I need GRUB to access linux? Thank you kindly.-- —A watched bread-crumb never boils.—My hover-craft is full of eels.—‽ <--You've just been Interrobanged.—[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, Sep 05, 2005 at 11:09:31PM +0200, Rakotomandimby Mihamina wrote: > not using HTML... Well, what did you expect? You're using evocrap as a MUA. Switch to something decent that actually allows you to control which part of a correctly-formatted rich-text message (ie including both HTML and non-HTML parts) is presented to you. I certainly never saw his HTML-encoded message. But then again, I use a decent MUA. -- Marc Wilson | Air pollution is really making us pay through [EMAIL PROTECTED] | the nose. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
Brian Nelson wrote: > "David R. Litwin" <[EMAIL PROTECTED]> writes: > > Before I go any further, yes, I need bootsplash: My computer is > > dual-boot and the other user insists on A: Using Windows and B: > > Shutting Down every Evening. But the other user will never see bootsplash. You booting linux will see it. But the other user booting MS-Windows will never see it. > > In addition, I shall be getting a lap-top soon. (By the bye, why doesn't > > Debian have Bootsplash as a standard?) You might wan to review Bug#190560 in the BTS. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=190560 It looks to be stagnating is all. Blowing a little on the embers may bring the fire to life. > > I have skimmed through a HOWTO or three. However, they aren't > > quite answering my questions. So, allow me to elaborate, if you > > will. If this was not in the ones you read then start again with this document: http://newbiedoc.sourceforge.net/system/kernel-pkg.html > I find it easiest to just grab the vanilla sources straight from > kernel.org. The Debian ones tend to be crippled and patched, which > makes it a pain to apply new patches. I always find it easier to use the Debian stock kernels. They have all of the toys preconfigured and patches can be easily applied. (Just to make a counter case because I think using both Debian patched kernel source an using upstream kernel.org source are valid. But I don't think the Debian source is crippled in any way. If you think it is then please file a bug in the BTS about it.) I am not running bootsplash myself so I will hold myself back from going into a description of how I would do it using the Debian kernel source. Besides as I said, I think using either one is quite valid. Bob signature.asc Description: Digital signature
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, 2005-09-05 at 16:36 -0400, David R. Litwin wrote: [snip] > > Any way, have you any advice to get me closer to me goal of > Bootsplashedness? > You might find this url helpful: http://hacks.oreilly.com/pub/h/3124 FWIW, I've got bootsplash here working fine on a 2.6.11 kernel but I cannot get it to work properly on a 2.6.12 one (I get the picture but not the progress bar). You may have better luck. In my case, it could be complicated by my running the new set of ATI 3d drivers and all their multifarious extra config settings. However, bootsplash does look a bit hit or miss on Debian. The other thing to watch out for is that some of the bootsplash themes are grotesquely awful and an ordinary scrolling log or even a blank screen might be preferable to them. :) Fish -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
"David R. Litwin" <[EMAIL PROTECTED]> writes: > Before I go any further, yes, I need bootsplash: My computer is dual-boot and > the other user insists on A: Using Windows and B: Shutting Down every Evening. > In addition, I shall be getting a lap-top soon. (By the bye, why doesn't > Debian have Bootsplash as a standard?) > > I know I need to compile a kernel (which I can do with synaptic and > kernel-package) and then patch it. > > I do not know how. > > I have skimmed through a HOWTO or three. However, they aren't quite answering > my questions. So, allow me to elaborate, if you will. > > Firstly, I need to get linux-source-2.6.12 from the Debian archives (with > Synaptic, in my case). Do I need linux-patch-debian-2.6.12 or > linux-tree-2.6.12? I find it easiest to just grab the vanilla sources straight from kernel.org. The Debian ones tend to be crippled and patched, which makes it a pain to apply new patches. Basically, the steps are: 1. Download the kernel source 2. Extract it to /usr/src, or wherever you'd prefer 3. Download the bootsplash patch from http://www.bootsplash.de/files/ 4. 'cd' into the extracted kernel source directory and run 'patch -p1 /path/to/bootsplash.diff' 5. Run 'make menuconfig', customize as needed, and be sure to set CONFIG_BOOTSPLASH=y 6. Run 'make-kpkg kernel_image'. See /usr/share/doc/kernel-packages for lots more info. 7. Use 'dpkg -i' to install the newly build kernel package > Next, I need use kernel-package. How do I do this? What of menuconfig or some > such thing? Must I 'do' this as well? > > There is also the matter of Patching. When and how do I do this so that I will > have Bootsplash? There is an entry for Sources.list, so I can acquire that > which I need from the Bootsplash web-site. But, what do I need? How do I > implement this? Add to the /etc/apt/sources.list: deb http://debian.bootsplash.de unstable main And then install: bootsplash bootsplash-theme-whatever And probably sysv-rc-bootsplash if you want a working progress bar. It looks like they also have some packages for apply the kernel patch, but I've never bothered with those. I think that's about it... -- Society is never going to make any progress until we all learn to pretend to like each other. -- 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 Mon, 2005-09-05 at 16:36 -0400, David R. Litwin wrote: > Any way, have you any advice not using HTML... -- Administration & Formation à l'administration de serveurs dédiés: http://www.google.fr/search?q=aspo+infogerance+serveur
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
No one *needs*bootsplash.My appologies: I really, really want Bootsplash. > (By the bye, why doesn't Debian have Bootsplash as a standard?)Is there some particular reason it should? Most people actually *use* the computer rather than rebooting it over and over and over and over...As I wrote (and so alluded to), my computer IS re-booted quite a bit. Besides, it's æsthetically pleasing (to me) and a hasel to do. So, why not just have it implicit? Any way, have you any advice to get me closer to me goal of Bootsplashedness?Thanks in advance.-- —A watched bread-crumb never boils.—‽ <--You've just been Interrobanged. —[...]and that's the he and the she of it.
Re: Compiling Kernel for Bootsplash: The Whole Seven Metres.
On Mon, Sep 05, 2005 at 03:48:25PM -0400, David R. Litwin wrote: > Before I go any further, yes, I need bootsplash: My computer is dual-boot > and the other user insists on A: Using Windows and B: Shutting Down every > Evening. In addition, I shall be getting a lap-top soon. What do any of those have to do with needing bootsplash? No one *needs* bootsplash. > (By the bye, why doesn't Debian have Bootsplash as a standard?) Is there some particular reason it should? Most people actually *use* the computer rather than rebooting it over and over and over and over... -- Marc Wilson | Having no talent is no longer enough. -- Gore Vidal [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel without -O2 flag
Sorav Bansal <[EMAIL PROTECTED]> writes: > Hi all, > > There is a curious thing that I noticed in the kernel. The kernel does > not compile if you remove the -O2 flag in the Makefile. It gives an error > in an ASM directive mentioning that a register is being spilled. The x86 has a very few registers. With in-line assembly you can easily tie some registers up. I guess gcc got into a corner it couldn't get out of. I would guess it's a bug in gcc, but at least it had the presence of mind to fail loudly. > Is this normal behavior? I suppose it is. Have you tried -O1? I know that the kernel depends upon certain functions being inlined for proper behavior. The kernel has some hard time constraints since it needs to deal with the hardware. You fiddle with the compile options at your own risk. -- Johan KULLSTAM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
S.D.A. wrote: On Sun, Apr 04, 2004 at 05:43:39PM -0400 or thereabouts, Roberto Sanchez wrote: Werner Mahr wrote: Or shorter: make dep bzImage modules modules_install This will make the Steps one by one, and if one fails the other will fail also. The Debian way is much easier: http://newbiedoc.sourceforge.net/system/kernel-pkg.html This doesn't resolve for me -- Is there another URL perhaps? It's there. SourceForge's nameservers have been a bit flaky today. -Roberto Sanchez signature.asc Description: OpenPGP digital signature
Re: Compiling kernel
On Sun, Apr 04, 2004 at 05:43:39PM -0400 or thereabouts, Roberto Sanchez wrote: > Werner Mahr wrote: > >Or shorter: make dep bzImage modules modules_install This will make the Steps > >one by one, and if one fails the other will fail also. > > > > The Debian way is much easier: > > http://newbiedoc.sourceforge.net/system/kernel-pkg.html This doesn't resolve for me -- Is there another URL perhaps? -- Steve + Sunday Apr 04 2004 06:16:01 PM EDT + First rule of public speaking. First, tell 'em what you're goin' to tell 'em; then tell 'em; then tell 'em what you've tole 'em. pgp0.pgp Description: PGP signature
Re: Compiling kernel
Am Sonntag, 4. April 2004 23:43 schrieb Roberto Sanchez: > Werner Mahr wrote: > > Am Sonntag, 4. April 2004 20:04 schrieb Sebastiaan: > >>Then it's a simple make dep && make bzImage && make modules && make > >>modules_install > > > > Or shorter: make dep bzImage modules modules_install > > This will make the Steps one by one, and if one fails the other will fail > > also. > > The Debian way is much easier: > > http://newbiedoc.sourceforge.net/system/kernel-pkg.html > > fakeroot make-kpkg --append-to-version= --revision= > kernel_image kernel_headers > dpkg -i ../kernel-image--__.deb > > That's it. It will also automatically update lilo ar grub. > It also leaves you a .deb that you can deploy to multiple > machines. I do it the Debian Way, but if Sebastiaan does it not the Debian Way, he can at least save to type && make 3 times. -- MfG usw. Werner Mahr registered Linuxuser: 295882 pgp0.pgp Description: signature
Re: Compiling kernel
Werner Mahr wrote: Am Sonntag, 4. April 2004 20:04 schrieb Sebastiaan: Then it's a simple make dep && make bzImage && make modules && make modules_install Or shorter: make dep bzImage modules modules_install This will make the Steps one by one, and if one fails the other will fail also. The Debian way is much easier: http://newbiedoc.sourceforge.net/system/kernel-pkg.html fakeroot make-kpkg --append-to-version= --revision= kernel_image kernel_headers dpkg -i ../kernel-image--__.deb That's it. It will also automatically update lilo ar grub. It also leaves you a .deb that you can deploy to multiple machines. -Roberto Sanchez signature.asc Description: OpenPGP digital signature
Re: Compiling kernel
Am Sonntag, 4. April 2004 20:04 schrieb Sebastiaan: > Then it's a simple make dep && make bzImage && make modules && make > modules_install Or shorter: make dep bzImage modules modules_install This will make the Steps one by one, and if one fails the other will fail also. -- MfG usw. Werner Mahr registered Linuxuser: 295882 pgp0.pgp Description: signature
Re: Compiling kernel
Michael Satterwhite wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been looking at the documentation for compiling the kernel, and something seems missing to me. There is ample documentation on configuring the kernel, but I don't see the issue of the starting point addressed anywhere. It seems to be assumed that if you're going to compile the kernel, then you want to individually visit every configuration parameter and make a selection. There is good documentation everywhere on how to do this. If you have a working kernel, however, it seems far more logical to use its configuration as a starting point and make the changes relative to that. In SuSE, there are good instructions on getting this starting point, but I don't see anything like that in Debian. I *DO* see a config file in the /boot directory, but it is ambiguous (at best) as to whether this is the configuration for the running kernel. Being fair, when something is so pointedly not addressed, it usually means I should have known the answer without asking - but I'll admit to ignorance. Would someone be so kind as to point me at the place for the current config (probably the one in /boot, but this isn't something I want to take a chance on) for a starting point? It is the starting point. Is in fact the config for the running kernel. You can use it for a future kernel too. When you run make-kpkg and are using it, he will stop and prompt for a new kernel parameter that now exists, so you know what the new ones are. E.g. I roll my own kernel because I use multi-seat Linux, Backstreet-Ruby. So they came out with a 2.4.25 patch while I was using 2.4.23. So I put the 2.4.23 .config into the 2.4.25 dir. and just ran "make-kpkg --revision 1 kernel_image" and he prompted for all the new 2.4.25 parms. I forgot now what they were but all support for new hardware that I don't have so I could answer "N" to all(the default). Then he created a .deb file in /usr/src that is the new kernel image. You just dpkg -i that and you got yourself a new kernel you can boot. Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 04 April 2004 13:36, Patrick Wiseman wrote: > You _could_ do this, but I recommend very highly compiling the kernel "the > Debian way." It takes care of all the little details missing any one of > which might leave you with a hosed system! I keep a file reminding me of > the steps; here's its current contents: Compiling the kernel was never the issue. The starting point for the configuration was. I do, however, thank you for your copy of this file. It does make sense to do it "the Debian way" as long as I'm running Debian. I'm learning, and I do thank those of you who have helped. I appreciate your feedback more than you know. - ---Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFAcF6ZjeziQOokQnARAjH2AJ4o5gl9XM1MeDJd1s6bWRsYXGbtLwCgi8+R ZNleGVm5PnEwKbBC42naRVk= =lAlk -END PGP SIGNATURE-
Re: Compiling kernel
On Sun, 4 Apr 2004 at 8:04pm, Sebastiaan wrote: :High, Not just at the moment; maybe later :) :On Sun, 4 Apr 2004, Michael Satterwhite wrote: : :> -BEGIN PGP SIGNED MESSAGE- :> Hash: SHA1 :> :> I've been looking at the documentation for compiling the kernel, and something :> seems missing to me. :> :> There is ample documentation on configuring the kernel, but I don't see the :> issue of the starting point addressed anywhere. It seems to be assumed that :> if you're going to compile the kernel, then you want to individually visit :> every configuration parameter and make a selection. There is good :> documentation everywhere on how to do this. :> :> If you have a working kernel, however, it seems far more logical to use its :> configuration as a starting point and make the changes relative to that. In :> SuSE, there are good instructions on getting this starting point, but I don't :> see anything like that in Debian. I *DO* see a config file in the /boot :> directory, but it is ambiguous (at best) as to whether this is the :> configuration for the running kernel. :> :> Being fair, when something is so pointedly not addressed, it usually means I :> should have known the answer without asking - but I'll admit to ignorance. :> Would someone be so kind as to point me at the place for the current config :> (probably the one in /boot, but this isn't something I want to take a chance :> on) for a starting point? :> :In /boot there is a file named config- with being your running :kernel. Unpack the kernel source in /usr/src/linux and copy :/boot/config-... to /usr/src/linux/.config : :Then run 'make oldconfig', which will only ask to configure new options to :that kernel. After that you can run make menuconfig or xconfig in order to :change the settings. : :Then it's a simple make dep && make bzImage && make modules && make :modules_install , copy thekernel from arch/.../boot/bzImage to /boot and :adapt your bootloader to this kernel. You _could_ do this, but I recommend very highly compiling the kernel "the Debian way." It takes care of all the little details missing any one of which might leave you with a hosed system! I keep a file reminding me of the steps; here's its current contents: Current kernel image is kernel-image-2.4.22_mycroft.1.1.0_i386.deb To compile kernel: In /usr/src/linux: make xconfig #configure as desired make-kpkg clean make-kpkg --revision=mycroft.1.1 kernel_image #revision as appropriate While it's compiling, edit /etc/lilo.conf if necessary (adding boot options, etc.) Move old modules out of the way: rm -Rf /lib/modules/2.4.22.old ;\ mv /lib/modules/2.4.22 /lib/modules/2.4.22.old To install new kernel and modules: In /usr/src/linux: dpkg -i ../kernel-image-2.4.22... #do 'ls ..' to find right image One thing I _don't_ do the Debian way, having started out as a Slackware user, is do all this 'fakeroot'; I just do it as root. The packages necessary to so compile the kernel, and other details, are to be found in the Debian Installation Manual, here for the i386 architecture: http://www.debian.org/releases/stable/i386/ch-post-install.en.html#s-kernel-baking Patrick -- Patrick Wiseman [EMAIL PROTECTED] Linux user #17943 *Google First, Ask Later* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 04 April 2004 13:04, Sebastiaan wrote: > High, > > On Sun, 4 Apr 2004, Michael Satterwhite wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > I've been looking at the documentation for compiling the kernel, and > > something seems missing to me. > > > > There is ample documentation on configuring the kernel, but I don't see > > the issue of the starting point addressed anywhere. It seems to be > > assumed that if you're going to compile the kernel, then you want to > > individually visit every configuration parameter and make a selection. > > There is good documentation everywhere on how to do this. > > > > If you have a working kernel, however, it seems far more logical to use > > its configuration as a starting point and make the changes relative to > > that. In SuSE, there are good instructions on getting this starting > > point, but I don't see anything like that in Debian. I *DO* see a config > > file in the /boot directory, but it is ambiguous (at best) as to whether > > this is the configuration for the running kernel. > > > > Being fair, when something is so pointedly not addressed, it usually > > means I should have known the answer without asking - but I'll admit to > > ignorance. Would someone be so kind as to point me at the place for the > > current config (probably the one in /boot, but this isn't something I > > want to take a chance on) for a starting point? > > In /boot there is a file named config- with being your running > kernel. Unpack the kernel source in /usr/src/linux and copy > /boot/config-... to /usr/src/linux/.config That was the piece of magic I needed. I was guessing that this was the current config, but I couldn't find anything that SAID it was the current config. Thanks much! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD4DBQFAcFA9jeziQOokQnARAkZzAJ0eMetsRUeRMhbr+Us7foizUJ6OvACWLlvv +BA28a39pHv+LLc0vLg5WA== =p0x1 -END PGP SIGNATURE-
Re: Compiling kernel
High, On Sun, 4 Apr 2004, Michael Satterwhite wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been looking at the documentation for compiling the kernel, and something > seems missing to me. > > There is ample documentation on configuring the kernel, but I don't see the > issue of the starting point addressed anywhere. It seems to be assumed that > if you're going to compile the kernel, then you want to individually visit > every configuration parameter and make a selection. There is good > documentation everywhere on how to do this. > > If you have a working kernel, however, it seems far more logical to use its > configuration as a starting point and make the changes relative to that. In > SuSE, there are good instructions on getting this starting point, but I don't > see anything like that in Debian. I *DO* see a config file in the /boot > directory, but it is ambiguous (at best) as to whether this is the > configuration for the running kernel. > > Being fair, when something is so pointedly not addressed, it usually means I > should have known the answer without asking - but I'll admit to ignorance. > Would someone be so kind as to point me at the place for the current config > (probably the one in /boot, but this isn't something I want to take a chance > on) for a starting point? > In /boot there is a file named config- with being your running kernel. Unpack the kernel source in /usr/src/linux and copy /boot/config-... to /usr/src/linux/.config Then run 'make oldconfig', which will only ask to configure new options to that kernel. After that you can run make menuconfig or xconfig in order to change the settings. Then it's a simple make dep && make bzImage && make modules && make modules_install , copy thekernel from arch/.../boot/bzImage to /boot and adapt your bootloader to this kernel. Greetz, Sebas -- The software box said 'Requires Windows 95 or better', so I installed Linux. Als Pacman in de jaren '80 de kinderen zo had be?nvloed zouden nu veel jongeren rondrennen in donkere zalen terwijl ze pillen eten en luisteren naar monotone electronische muziek. (Kristian Wilson, Nintendo, 1989) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
> That's what make oldconfig is for. cp the stock config from /boot, > and continue from there. You should be prompted for new changes but > anything in the old kernel will be selected by default. > and you can also load that .config file from make menuconfig/xconfig too, and make whatever changes you might want to the old one. rajesh menon at http://www.cs.nyu.edu/~prm225/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
On Sun, Apr 04, 2004 at 12:18:13PM -0500, Michael Satterwhite wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been looking at the documentation for compiling the kernel, and something > seems missing to me. > >From Debian Reference: # apt-get install debhelper modutils kernel-package libncurses5-dev # apt-get install kernel-source-2.4.18 # use latest version # apt-get install fakeroot # vi /etc/kernel-pkg.conf# input my name and email $ cd /usr/src# build directory $ tar --bzip2 -xvf kernel-source-2.4.18.tar.bz2 $ cd kernel-source-2.4.18# if this is your kernel source $ cp /boot/config-2.4.18-386 .config # get current config as default $ make menuconfig# customize as one wishes $ make-kpkg clean# must run (per: man make-kpkg) $ fakeroot make-kpkg --append_to_version -486 --initrd \ --revision=rev.01 kernel_image \ modules_image # modules_image is for pcmcia-cs* etc. $ cd .. # dpkg -i kernel-image*.deb pcmcia-cs*.deb # install HTH, Jim Seymour -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
> If you have a working kernel, however, it seems far more logical to use its > configuration as a starting point and make the changes relative to that. In > SuSE, there are good instructions on getting this starting point, but I don't > see anything like that in Debian. I *DO* see a config file in the /boot > directory, but it is ambiguous (at best) as to whether this is the > configuration for the running kernel. yes, that would be the one. just to put your mind at ease, you can open that file in any text editor, and see that your setup follows what is in it. and i hope you know that you can use config files to go from 2.x.0 to 2.x.10. but u cant use a 2.x config for a 2.y rajesh menon at http://www.cs.nyu.edu/~prm225/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
Incoming from Michael Satterwhite: > I've been looking at the documentation for compiling the kernel, and something > seems missing to me. > > There is ample documentation on configuring the kernel, but I don't see the > issue of the starting point addressed anywhere. It seems to be assumed that > if you're going to compile the kernel, then you want to individually visit > every configuration parameter and make a selection. There is good > documentation everywhere on how to do this. > > If you have a working kernel, however, it seems far more logical to use its > configuration as a starting point and make the changes relative to that. In That's what make oldconfig is for. cp the stock config from /boot, and continue from there. You should be prompted for new changes but anything in the old kernel will be selected by default. http://groups.google.com/groups?q=%2Bdebian+make+oldconfig&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=87adpp99h9.fsf%40glaurung.green-gryphon.com&rnum=1 -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
On 4/4/2004 1:30 PM, Rajesh Menon wrote: there isn't really a specified place to find the .config of your last kernel build. usually, when you finish configuring and save the config, it will be present in the kernel src dir. i don't have any .config under /boot cos i build them in my /home and save em under one folder. so, if you did a kernel build a while ago, look in that src tree and you should find it there. if you havent, then i think you will find it under /boot (you could just do a 'locate .config' and that should tell you if you dont find it there.) He's wanting to know where he can find a .config that corresponds to the default kernel installed on a fresh Debian system; not a custom built kernel. Randy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
there isn't really a specified place to find the .config of your last kernel build. usually, when you finish configuring and save the config, it will be present in the kernel src dir. i don't have any .config under /boot cos i build them in my /home and save em under one folder. so, if you did a kernel build a while ago, look in that src tree and you should find it there. if you havent, then i think you will find it under /boot (you could just do a 'locate .config' and that should tell you if you dont find it there.) hth. On Sun, 4 Apr 2004, Michael Satterwhite wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been looking at the documentation for compiling the kernel, and something > seems missing to me. > > There is ample documentation on configuring the kernel, but I don't see the > issue of the starting point addressed anywhere. It seems to be assumed that > if you're going to compile the kernel, then you want to individually visit > every configuration parameter and make a selection. There is good > documentation everywhere on how to do this. > > If you have a working kernel, however, it seems far more logical to use its > configuration as a starting point and make the changes relative to that. In > SuSE, there are good instructions on getting this starting point, but I don't > see anything like that in Debian. I *DO* see a config file in the /boot > directory, but it is ambiguous (at best) as to whether this is the > configuration for the running kernel. > > Being fair, when something is so pointedly not addressed, it usually means I > should have known the answer without asking - but I'll admit to ignorance. > Would someone be so kind as to point me at the place for the current config > (probably the one in /boot, but this isn't something I want to take a chance > on) for a starting point? > > tia > - ---Michael > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) > > iD8DBQFAcENcjeziQOokQnARAqAhAKCMGQ4aUb8+Aok9fahGWyhFcsIJuACgtzv0 > dtvNs/M/CqlUCtm0Uz8MEa0= > =jAqk > -END PGP SIGNATURE- > > > > rajesh menon at http://www.cs.nyu.edu/~prm225/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel
On Sun, Apr 04, 2004 at 12:18:13PM -0500, Michael Satterwhite wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been looking at the documentation for compiling the kernel, and something > seems missing to me. > > There is ample documentation on configuring the kernel, but I don't see the > issue of the starting point addressed anywhere. It seems to be assumed that > if you're going to compile the kernel, then you want to individually visit > every configuration parameter and make a selection. There is good > documentation everywhere on how to do this. > > If you have a working kernel, however, it seems far more logical to use its > configuration as a starting point and make the changes relative to that. In > SuSE, there are good instructions on getting this starting point, but I don't > see anything like that in Debian. I *DO* see a config file in the /boot > directory, but it is ambiguous (at best) as to whether this is the > configuration for the running kernel. > > Being fair, when something is so pointedly not addressed, it usually means I > should have known the answer without asking - but I'll admit to ignorance. > Would someone be so kind as to point me at the place for the current config > (probably the one in /boot, but this isn't something I want to take a chance > on) for a starting point? I haven't needed to do this for a while (recompile) but if I recall you can move that file in /boot to a file called .config in /usr/src/kernel-src or where ever the root of your kernel source tree is. If it isn't .config I'm 99% sure it's another hidden dot-file in the same place. Good luck. pgp0.pgp Description: PGP signature
Re: Compiling Kernel Problems xconfig
On Fri, Jan 23, 2004 at 03:36:23PM +, James Hosken wrote: > > [EMAIL PROTECTED]:/usr/src/linux$ make xconfig > make[1]: `scripts/fixdep' is up to date. > * > * Unable to find the QT installation. Please make sure that the > * QT development package is correctly installed and the QTDIR > * environment variable is set to the correct location. > * > make[1]: *** [scripts/kconfig/.tmp_qtcheck] Error 1 > make: *** [xconfig] Error 2 > [EMAIL PROTECTED]:/usr/src/linux$ > /usr/share/doc/kernel-package/README.gz from testing has some remarks about it. For example, and make xconfig also requires either tkX.X-dev for 2.4.X kernels, or libqt3-mt-dev and g++ >= 3.0 for the new 2.6 kenel versions . You might want to look at this file on your machine. -- "If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas." -- George Bernard Shaw (sent by shaulk @ actcom . net . il) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling Kernel Problems xconfig
Hello James Hosken (<[EMAIL PROTECTED]>) wrote: > I'm working my way through the "Creating custom kernels with Debian's > kernel-package system" from > >http://newbiedoc.sourceforge.net/tutorials/kernel-pkg/config-kernel-pkg.html.en > > When I get to make xconfig I get the error > > > [EMAIL PROTECTED]:/usr/src/linux$ make xconfig > make[1]: `scripts/fixdep' is up to date. > * > * Unable to find the QT installation. Please make sure that the > * QT development package is correctly installed and the QTDIR > * environment variable is set to the correct location. Trying to compile Kernel 2.6? > * > make[1]: *** [scripts/kconfig/.tmp_qtcheck] Error 1 > make: *** [xconfig] Error 2 > [EMAIL PROTECTED]:/usr/src/linux$ > > > I really don't know what QT is and what to install. Can any one > enlighten me, thanks. You probably need to install libqt2 and libqt2-headers or libqt3 and libqt3-headers. Use apt-cache libqt to get more information on available packages. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel on a different computer
Monique Y. Herman said: > You might also look into distcc, which allows you to run the compile > across multiple computers. > > Oh, wait, just reread - the above won't help with harddrive space =/ > but it's still a really cool tool. > > -- > monique i never could get distcc to work, anyone have a simple guide to configuring it after installation? -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel on a different computer
> On Tue, 23 Dec 2003 at 12:04 GMT, Piers Kittel penned: > > Hello all, > > > > I've got an ancient 486 which needs its kernel recompiled, but it is > > extremely slow, and the hard drive isn't big enough - and I think it's > > possible to recompile the kernel on my main PC and transfer the kernel > > and modules over - how to do this? > > > > Thanks very much for your help in advance > > In normal operation, the kernel-package scripts figure out what architecture to compile for by looking at things like uname (don't remember exactly), but this behavior can be overridden. Look at the make-kpkg man page. -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel on a different computer
On Tue, 23 Dec 2003 at 12:04 GMT, Piers Kittel penned: > Hello all, > > I've got an ancient 486 which needs its kernel recompiled, but it is > extremely slow, and the hard drive isn't big enough - and I think it's > possible to recompile the kernel on my main PC and transfer the kernel > and modules over - how to do this? > > Thanks very much for your help in advance > You might also look into distcc, which allows you to run the compile across multiple computers. Oh, wait, just reread - the above won't help with harddrive space =/ but it's still a really cool tool. -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling kernel on a different computer
Piers Kittel <[EMAIL PROTECTED]> writes: > I've got an ancient 486 which needs its kernel recompiled, but it is > extremely slow, and the hard drive isn't big enough - and I think it's > possible to recompile the kernel on my main PC and transfer the kernel > and modules over - how to do this? Build the kernel normally using kernel-package, configuring it for the target machine. (http://newbiedoc.sourceforge.net/ has what seems to be the canonical Debian kernel compilation how-to these days.) When you're done, you should have a kernel-image-*.deb file; copy it to the target machine using scp or some such. Then log in as root on the target machine and use 'dpkg --install' to install the kernel. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel
GCS wrote: On Sun, Dec 21, 2003 at 07:59:20PM -0700, Lucas Albers <[EMAIL PROTECTED]> wrote: I sure wish debian had a secure version of the kernel; a binary version of grsecurity would add a huge amount of security. Anyone know why Debian does not have this in the main archive? At least a grsecurity patch for recent kernels? It is incompatible with the IPSec backport in Debian's[Herbert Xu's] 2.4 kernel. Search the debian-devel archives for the flamefest[and don't start another one here]. [Look at the middle of September into the beginning of October, major thread titled "Debian should not modify the kernels" with several other smaller threads] pgp0.pgp Description: PGP signature
Re: compiling kernel
On Sun, Dec 21, 2003 at 07:59:20PM -0700, Lucas Albers <[EMAIL PROTECTED]> wrote: > I sure wish debian had a secure version of the kernel; a binary version of > grsecurity would add a huge amount of security. Anyone know why Debian does not have this in the main archive? At least a grsecurity patch for recent kernels? Thanks, GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel
GCS said: > But no other problem really. Anyway, I _do agree with you strongly_: > 2.6.0 is not for widespread yet. I will switch at ~2.6.10 on my servers, > depending the fixes get in by that time. Until then I use > 2.4.23+grsecurity. You are on my same wavelength. I thought I was the only person that did 2.4.23+grecurity on mission critical production servers. I run 2.4.23+grsec on my most important departmental servers, that if they died or whatnot, I would have 300 people in my face. I sure wish debian had a secure version of the kernel; a binary version of grsecurity would add a huge amount of security. Their really is no comparison between exec-shield and grsecurity. -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel
On Sun, Dec 21, 2003 at 10:52:26AM -0700, Lucas Albers <[EMAIL PROTECTED]> wrote: > > Anyway, I have many machines, three of them running with kernel 2.6.0, > > compiled with gcc 3.3; no problems. > What a man, I'm not touching 2.6.0 until it's in the 10 release. I agree with you. 2.6.0 still has too many problems, not suitable for multi user systems (security), and has other big problems as well. OK, I also lied (what's the past tense of lie? I always forget), as I have problems with 2.6.0: - one machine has boot problems with LVM2, I have to wait an extra ~30 secs, as it tries to open my cdrom (without any medium in it). It fails, wait, and retry about 20 times. If I put a cd into it, then it fails immediately and continue; - on my laptop I can not burn a cd if it exceeds ~400M. It burns for a while, and then just freeze the machine. Small cd burning is ok, and also ok if I reboot to 2.4.23. So I burn cd on an other computer. :-| But no other problem really. Anyway, I _do agree with you strongly_: 2.6.0 is not for widespread yet. I will switch at ~2.6.10 on my servers, depending the fixes get in by that time. Until then I use 2.4.23+grsecurity. Cheers, GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel
GCS said: >> Stable gcc for stable kernel, and testing gcc for testing kernel? > ? There's no such relationship. > >> I've done 2.4.22 with gcc 3.2.3 (gcc testing) and it appeared to work >> correctly. > 3.2.3 is _not_ a test version of gcc. There's a newer one, fe I have > 3.3.3 installed. Please be sure that you do not mix up the Debian > testing distribution (Sarge) with test versions of software. Sarge is > testing because the developers assembly the packages to work _together_, > they have correct dependencies, configuration etc. Also mostly they > package the _stable_ version of software. I was not implying that the testing distribution was an unstable collection. I stand corrected I was referring to gcc 3.3 which is part of sarge. Thanks for correction. > Anyway, I have many machines, three of them running with kernel 2.6.0, > compiled with gcc 3.3; no problems. What a man, I'm not touching 2.6.0 until it's in the 10 release. -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel
On Sun, Dec 21, 2003 at 01:57:38AM -0700, Lucas Albers <[EMAIL PROTECTED]> wrote: > Stable gcc for stable kernel, and testing gcc for testing kernel? ? There's no such relationship. > I've done 2.4.22 with gcc 3.2.3 (gcc testing) and it appeared to work > correctly. 3.2.3 is _not_ a test version of gcc. There's a newer one, fe I have 3.3.3 installed. Please be sure that you do not mix up the Debian testing distribution (Sarge) with test versions of software. Sarge is testing because the developers assembly the packages to work _together_, they have correct dependencies, configuration etc. Also mostly they package the _stable_ version of software. Anyway, I have many machines, three of them running with kernel 2.6.0, compiled with gcc 3.3; no problems. Cheers, GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel for another system
On Tuesday 09 December 2003 09:46, John L. Fjellstad wrote: > Yeah, I figured that out after looking at the dependency list of > the kernel-packages. I'm wondering though if using gcc3.3 would > have any impact (since everything else on the stable system would > have the programs compiled with gcc2.95) Well, that's what I've been thinking. But isn't the kernel basically one self-contained unit? I mean sure: The modules depend on the kernel but they're both compiled with the same compiler anyway, right? Apart from that: The kernel is pure C, isn't it? The changees from gcc2.95 to gcc3.2 were in the C++ ABI, they didn't affect C compatibility IIRC. So it really doesn't make much sense to have any unresolved symbols here - and, as I said, at least for me it worked. Anyways, I'm really no expert on this. But it's been really interesting to discuss it - always something to learn on this list! Best regards, Magnus -- --- Magnus von Koeller --- email:[EMAIL PROTECTED] address: International University Campus 9, App. 13 D-76646 Bruchsal / Germany phone:+49-7251-700-659 mobile: +49-179-4562940 web: http://www.vonkoeller.de pgp0.pgp Description: signature
Re: compiling kernel for another system
Colin Watson wrote: > The kernel doesn't use the libc, so I expect that this is a red herring. > (I don't know the real answer, though.) Yeah, I figured that out after looking at the dependency list of the kernel-packages. I'm wondering though if using gcc3.3 would have any impact (since everything else on the stable system would have the programs compiled with gcc2.95) This thread has been very educational, and I suspect Magnus is right. I'm almost tempted to recompile my kernel again, just to test it out (it's one of those, good to know, things). -- 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 for another system
On Thu, Dec 04, 2003 at 04:29:51PM +0100, John L. Fjellstad wrote: > My server runs Debian stable, while my workstation runs Debian testing. > Since the server is a slower machine, I would like to create the kernel > package on my workstation and install the deb package on my server. > Is this possible? > > When I tried, I got several unresolved symbols when installing the deb > package during the /sbin/depmod -a stage. I'm guessing because testing > uses libc6 2.3.2, while stable uses libc6 2.2.5. The kernel doesn't use the libc, so I expect that this is a red herring. (I don't know the real answer, though.) -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel for another system
On Monday 08 December 2003 00:59, Bill Goudie wrote: > The unresolved symbols still exist -- depmod is run with "-q" > from /etc/init.d/modutils. This suppresses the error warnings. Well, what I did was run this from the command line: # depmod -a Even this: # depmod -a -e And it doesn't complain about /any/ missing symbols. -- --- Magnus von Koeller --- email:[EMAIL PROTECTED] address: International University Campus 9, App. 13 D-76646 Bruchsal / Germany phone:+49-7251-700-659 mobile: +49-179-4562940 web: http://www.vonkoeller.de pgp0.pgp Description: signature
Re: compiling kernel for another system
On Sun, Dec 07, 2003 at 05:37:16PM -0600, Bill Goudie wrote: > On Sun, Dec 07, 2003 at 11:28:41PM +0100, Magnus von Koeller wrote: > > On Sunday 07 December 2003 23:11, Bill Goudie wrote: > > > The upshot of all this is that modules with unresolved symbols > > > require functions which were excluded from both the kernel and any > > > other installed modules for that kernel version. ?If for some > > > reason you built this module but don't need it, then these errors > > > can be ingored. Otherwise, I believe you will not be able to load > > > the module. > > > > So that would also mean that if you ignore these errors and boot into > > the new kernel anyway, you should still get these depmod errors? > > Because once I'd booted into the new kernel, depmod -a runs without > > errors. > > Yes, I would expect the errors to still occur. At least they did on my > system. I accidently included an uneeded module in the last build and > I still see the same message: > > $ depmod -a > depmod: *** Unresolved symbols in > /lib/modules/2.4.23/kernel/drivers/media/radio/miropcm20.o > > So, I'm not sure what to make of your situation. I'm must be wrong > about something. The unresolved symbols still exist -- depmod is run with "-q" from /etc/init.d/modutils. This suppresses the error warnings. -- A woman did what a woman had to, the best way she knew how. To do more was impossible, to do less, unthinkable. -- Dirisha, "The Man Who Never Missed" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel for another system
On Sun, Dec 07, 2003 at 11:28:41PM +0100, Magnus von Koeller wrote: > On Sunday 07 December 2003 23:11, Bill Goudie wrote: > > The upshot of all this is that modules with unresolved symbols > > require functions which were excluded from both the kernel and any > > other installed modules for that kernel version. ?If for some > > reason you built this module but don't need it, then these errors > > can be ingored. Otherwise, I believe you will not be able to load > > the module. > > So that would also mean that if you ignore these errors and boot into > the new kernel anyway, you should still get these depmod errors? > Because once I'd booted into the new kernel, depmod -a runs without > errors. Yes, I would expect the errors to still occur. At least they did on my system. I accidently included an uneeded module in the last build and I still see the same message: $ depmod -a depmod: *** Unresolved symbols in /lib/modules/2.4.23/kernel/drivers/media/radio/miropcm20.o So, I'm not sure what to make of your situation. I'm must be wrong about something. -- There are ten or twenty basic truths, and life is the process of discovering them over and over and over. -- David Nichols -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling kernel for another system
On Sunday 07 December 2003 23:11, Bill Goudie wrote: > The upshot of all this is that modules with unresolved symbols > require functions which were excluded from both the kernel and any > other installed modules for that kernel version. If for some > reason you built this module but don't need it, then these errors > can be ingored. Otherwise, I believe you will not be able to load > the module. So that would also mean that if you ignore these errors and boot into the new kernel anyway, you should still get these depmod errors? Because once I'd booted into the new kernel, depmod -a runs without errors. -- --- Magnus von Koeller --- email:[EMAIL PROTECTED] address: International University Campus 9, App. 13 D-76646 Bruchsal / Germany phone:+49-7251-700-659 mobile: +49-179-4562940 web: http://www.vonkoeller.de pgp0.pgp Description: signature
