Re: Debian way of compiling a kernel.

[Arthur Machlas]

Ughn.. think google just discarded my post instead of sending. Don't
want to retype; but here's the link:

http://users.wowway.com/~zlinuxman/Kernel.htm


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTikwHint7Z5tS82Pkk=+f3p-ec6dbeg0nkgpq...@mail.gmail.com

Re: Debian way of compiling a kernel.

[Jochen Schulz]

Boyd Stephen Smith Jr.:
> 
> If you just want a .deb to install, I've heard there's a makefile target in 
> the kernel tarball that works fine.  I believe but can't confirm that the 
> .debs generated by the makefile in the kernel tarball will properly invoke 
> the postint scripts that are used to update grub.cfg, menu.lst, or the lilo 
> boot sector.

I routinely compile vanilla kernels from git just using make, make
deb-pkg and when installing the resulting package, grub2 and the
initramfs get updated just fine.

J.
-- 
I wear a lot of leather but would never wear fur.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Debian way of compiling a kernel.

[Sven Joachim]

On 2011-02-10 09:18 +0100, Boyd Stephen Smith Jr. wrote:

> If you just want a .deb to install, I've heard there's a makefile target in 
> the kernel tarball that works fine.

That target is called deb-pkg, i.e. you type "make deb-pkg" and get a
nice Debian package.

> I believe but can't confirm that the 
> .debs generated by the makefile in the kernel tarball will properly invoke 
> the postint scripts that are used to update grub.cfg, menu.lst, or the lilo 
> boot sector.

The maintainer scripts in the generated package just run the hooks under
/etc/kernel.d, in Squeeze and later those should take care of generating
an initramfs, updating the bootloader's configuration etc.

Sven


-- 
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/87oc6kb89k@turtle.gmx.de

Re: Debian way of compiling a kernel.

[Boyd Stephen Smith Jr.]

In <20110209223754.5fa03...@ws82.int.tlc>, Dan Serban wrote:
>I ask.  What is the "real" ... "accepted" ... and "suggested" method that I
>follow, I don't understand why kernel-package looks deprecated, or what
>have you, but any information would be appreciated.

If you want to use Debian's configuration and Debian's patches I'd look into 
downloading the source package and modifying it, but that can be a daunting 
task; there are a number of Debian-isms to learn along the way.  Once you 
know what you are doing, you can update the debian/changelog, use a target in 
debian/rules to prepare a .orig.tar, and use dpkg-buildpkg to get a set of 
binary packages that are significantly similar to the ones from the kernel 
packaging team.

If you just want a .deb to install, I've heard there's a makefile target in 
the kernel tarball that works fine.  I believe but can't confirm that the 
.debs generated by the makefile in the kernel tarball will properly invoke 
the postint scripts that are used to update grub.cfg, menu.lst, or the lilo 
boot sector.

The wiki has some pretty good information, too:
http://wiki.debian.org/DebianKernel
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
http://wiki.debian.org/DebianKernelCustomCompilation

All of those pages seem to reference:
http://kernel-handbook.alioth.debian.org/
Specifically:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
which I'm pretty sure is the official documentation produced by the Debian 
Linux Kernel packaging team.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Debian way of compiling a kernel.

[Dan Serban]

Ages ago, when amd64 wasn't part of the debian collection, I used to
compile kernels myself using make-kpkg.  This worked wonderfully, when I
had to debug driver patches etc.  (all is now of course stable).

Since then I've forgotten this process, but this is not my problem.  I
wanted to test a fixed DSDT acpi table against a motherboard I am having
flaky io issues with, I know the kernel is intended to handle these
problems but I did want to see if it helped.

When I hit the wiki page, I was surprised to see the procedure of building
a debian kernel, nothing I have done before to handle building a slightly
modified deb kernel.

I ask.  What is the "real" ... "accepted" ... and "suggested" method that I
follow, I don't understand why kernel-package looks deprecated, or what
have you, but any information would be appreciated.

Thank you.


-- 
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/20110209223754.5fa03...@ws82.int.tlc

Re: compiling a kernel from kernel.org [SOLVED]

[Manoj Srivastava]

On Wed, Oct 21 2009, Gregor Galwas wrote:

> The only problem to be solved was the initrd. it has NOT been
> generated by dpkg during the installation.
> so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked
> fine. update-grub - worked fine as well.

,[ Manual page make-kpkg(1) ]
|  --initrd
| If make-kpkg is generating a kernel-image package, arrange to
| convey to the hook scripts run from the post installation
| maintainer scripts that this image requires an initrd, and that
| the initrd generation hook scripts should not short circuit
| early. Without this option, the example initramfs hook scripts
| bundled in with kernel-package will take no action on
| installation.  The same effect can be achieved by setting the
| environment variable INITRD to any non empty value.  Please note
| that unless there are hook scripts in /etc/kernel or added into
| the hook script parameter of /etc/kernel-img.conf.  no initrd
| will be created (the bundled in example scripts are just
| examples -- user action is required before anything happens).
`

,[ /usr/share/doc/kernel-package/README.gz ]
|  gotchas. Note that you will have to arrange for the actual
|  initrd creation to take place by installing a script like
|  /usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird
|  or, alternately,
|  /usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs 
|  into the corresponding directories /etc/kernel/post{inst,rm}.d,
|  since the kernel-postinst does not arrange for the initramfs
|  creator to be called. You can thus select your own;
|  initramfs-tools or yaird.
| 
|  Let me repeat: 
|  Since nothing is created automatically. you need to provide a hook
|  script for things to happen when you install the kernel image
|  package.  The user provides such scripts. For example, to invoke
|  mkinitramfs, I did:
| --8<---cut here---start->8---
|  cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/yaird \
| /etc/kernel/postinst.d/
|  cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/yaird \
| /etc/kernel/postrm.d/
| --8<---cut here---end--->8---
| 
| Or, alternately, you could do:
| --8<---cut here---start->8---
|  cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \
| /etc/kernel/postinst.d/
|  cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \
| /etc/kernel/postrm.d/
| --8<---cut here---end--->8---
| 
| These scripts above to nothing unless the corresponding
|  packages are installed (initramfs-tools or yaird), so you could
|  potentially cp both over -- as long as you never install both yaird
|  and initramfs-tools at the same time.
| 
| To run grub, I have in /etc/kernel-img.conf:
| --8<---cut here---start->8---
| postinst_hook = update-grub
| postrm_hook   = update-grub
| --8<---cut here---end--->8---
| 
| You can look at other example in the examples directory:
| /usr/share/kernel-package/examples/ to see if there are other example
| script you want to cp into /etc/kernel -- and you can create your own
| scripts.
| 
| For example, if you use linux-headers-* packages to compile third
| party modules so that you do not have to keep the sources directory
| around, you might be interested in:
| --8<---cut here---start->8---
| /etc/kernel/header_postinst.d/link
| /etc/kernel/header_postrm.d/link
| /etc/kernel/header_prerm.d/link
| /etc/kernel/postinst.d/force-build-link
| /etc/kernel/postrm.d/force-build-link
| --8<---cut here---end--->8---
| 
| These scripts will try to make sure that the symlink
|  /lib/modules/$VERSION/build 
|  is sane -- that is points to the header packages whether you install
|  the image packages first, or the header packages first -- and takes
|  care of cleanup when either of the packages are installed.
`

Perhaps people who maintain FAQ's on this list add the above?

manoj

-- 
Some people have a great ambition: to build something that will last, at
least until they've finished building it.
Manoj Srivastava    
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: compiling a kernel from kernel.org [SOLVED]

[thveillon.debian]

Gregor Galwas wrote:
> Hey,
> 
> Thx everybody for your quick answers and friendly help.
> 
> You were right. I removed all Xen options from the kernel config and
> 
> linux-image-2.6.32-rc5_20091016-2_amd64.deb
> 
> has been built.
> Installing it with "dpkg -i ..." worked fine.
> The only problem to be solved was the initrd. it has NOT been generated
> by dpkg during the installation.
> so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked fine.
> update-grub - worked fine as well.
> 
> Finally I can use KMS with my radeon 4670 :)
> 
> Greetings
> Gregor Galwas
> 

Hi, regarding the initrd, you need to copy over to /etc/kernel/* the
relevant scripts from /usr/share/kernel-package/examples/etc/kernel/*
(look for "initramfs" or "yaird" if you use it). It will save you the
mkinitramfs step.
Also have a look at
/usr/share/kernel-package/examples/etc/sample.kernel-img.conf to trigger
links creation and such.

Tom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: compiling a kernel from kernel.org [SOLVED]

[Gregor Galwas]

Hey,

Thx everybody for your quick answers and friendly help.

You were right. I removed all Xen options from the kernel config and

linux-image-2.6.32-rc5_20091016-2_amd64.deb

has been built.
Installing it with "dpkg -i ..." worked fine.
The only problem to be solved was the initrd. it has NOT been generated by  
dpkg during the installation.
so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked fine.  
update-grub - worked fine as well.


Finally I can use KMS with my radeon 4670 :)

Greetings
Gregor Galwas

On Tue, 20 Oct 2009 21:34:53 +0200, Manoj Srivastava   
wrote:



Hi,

Well, firstly, if you are going to be using the buildpackage
 target, instead of the far faster kernel_image target, you should
 either configure /etc/kernel-pkg.conf, adding your name and email, and
 have that in a keyring your gpg knows about, or pass the --us and --uc
 arguments on the command line.

I think, unless you know what you are doing, try first with
 kernel_image target.

Next, you seem to have Xen options turned on in your config, and
 thus make-kpkg is trying to create a xenu-linux image. This is
 undergoing some development, so if you want Xen images, please get the
 12.024 version of kernel-package from Sid.

If you are just trying to build a normal kernel, redo your
 .config not to have Xen stuff in it.

manoj



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: compiling a kernel from kernel.org

[Manoj Srivastava]

Hi,

Well, firstly, if you are going to be using the buildpackage
 target, instead of the far faster kernel_image target, you should
 either configure /etc/kernel-pkg.conf, adding your name and email, and
 have that in a keyring your gpg knows about, or pass the --us and --uc
 arguments on the command line.

I think, unless you know what you are doing, try first with
 kernel_image target.

Next, you seem to have Xen options turned on in your config, and
 thus make-kpkg is trying to create a xenu-linux image. This is
 undergoing some development, so if you want Xen images, please get the
 12.024 version of kernel-package from Sid.

If you are just trying to build a normal kernel, redo your
 .config not to have Xen stuff in it.

manoj
-- 
This is an unauthorized cybernetic announcement.
Manoj Srivastava    
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

compiling a kernel from kernel.org

[Gregor Galwas]

hello,

in the new last days I've been trying to compile a recent kernel from  
kernel.org


I fetched a kernel from http://www.kernel.org/

mainline:   2.6.32-rc5  2009-10-16  [Full Source]
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.32-rc5.tar.bz2

unpacked it using tar xjvf linux-2.6.32-rc5.tar.bz2 -C /usr/src
linked : ln -s /usr/src/linux-2.6.32-rc5.tar.bz2 /usr/src/linux

cp /boot/config-`uname -r` /usr/src/linux/.config
make oldconfig

then I started building the packages with

make-kpkg buildpackage --revision 20091016 --initrd

it started compiling it and it ended after a loinger time with :


make[1]: Leaving directory `/usr/src/linux-2.6.32-rc5'
 dpkg-genchanges -b -mUnknown Kernel Package Maintainer  
  

../linux-source-2.6.32-rc5_20091016_amd64.changes
dpkg-genchanges: warning: package linux-image-2.6.32-rc5 in control file  
but not in files list
dpkg-genchanges: warning: package linux-image-2.6.32-rc5-dbg in control  
file but not in files list
dpkg-genchanges: warning: package linux-uml-2.6.32-rc5 in control file but  
not in files list
dpkg-genchanges: warning: package linux-xen0-2.6.32-rc5 in control file  
but not in files list

dpkg-genchanges: binary-only upload - not including any source code
 signfile linux-source-2.6.32-rc5_20091016_amd64.changes
gpg: skipped "Unknown Kernel Package Maintainer": secret key not available
gpg: [stdin]: clearsign failed: secret key not available

dpkg-buildpackage: binary only upload (no source included)
dpkg-buildpackage: warning: Failed to sign .changes file
make: *** [debian/stamp/build/buildpackage] Error 1

following packages have been created in /usr/src:

linux-doc-2.6.32-rc5_20091016_all.deb
linux-headers-2.6.32-rc5_20091016_amd64.deb
linux-headers-2.6.32-rc5_2.6.32-rc5-10.00.Custom_amd64.deb
linux-manual-2.6.32-rc5_20091016_all.deb
linux-source-2.6.32-rc5_20091016_all.deb
linux-source-2.6.32-rc5_20091016_amd64.changes
linux-xenu-2.6.32-rc5_20091016_amd64.deb
linux-xenu-2.6.32-rc5_2.6.32-rc5-10.00.Custom_amd64.deb


ok, so far - it looked good even thouigh that "xenu" part annoyed me  
somehow.


when I treid to install linux-xenu-2.6.32-rc5_20091016_amd64.deb

I got:

pegasos:/usr/src# dpkg -i linux-xenu-2.6.32-rc5_20091016_amd64.deb
Selecting previously deselected package linux-xenu-2.6.32-rc5.
(Reading database ... 215220 files and directories currently installed.)
Unpacking linux-xenu-2.6.32-rc5 (from  
linux-xenu-2.6.32-rc5_20091016_amd64.deb) ...

Done.
Setting up linux-xenu-2.6.32-rc5 (20091016) ...
Internal Error: Could not find image (/boot/vmlinuz-2.6.32-rc5)
dpkg: error processing linux-xenu-2.6.32-rc5 (--install):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 linux-xenu-2.6.32-rc5


Obviously something is badly wrong then.
I am using Debian Unstable with kernel 2.6.31 (Linux pegasos  
2.6.31-trunk-amd64 #1 SMP Mon Oct 12 23:36:11 UTC 2009 x86_64 GNU/Linux)  
and Grub2


anyone has an idea whats wrong here? Or am I doing it completely wrong?

Thx for reading at least...

Gregor Galwas



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[Alan Ianson]

On Wed October 25 2006 06:39, David Baron wrote:
> On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
> > On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> > > With this install of Debian I decided to stick to what I know, and
> > > grabbed the binary installer direct from NVidia.  I ran that, and in
> > > less than two minutes I was up and running.  No complaints from Debian
> > > and no complaints from NVidia.  Oh, except for one because I had tried
> > > to compile it before I updated the system fully and so I had a gcc
> > > which didn't match the kernel, but that was fixed in no time.
> >
> > Apparently the binary installer from NVidia messes with the libraries on
> > the system and is not the recommended method for installing.
> >
> > Read http://home.comcast.net/~andrex/Debian-nVidia/
> >
> > The Debian way is certainly a lot easier. Now where has that nvidia-glx
> > package gone?
>
> Nvidia's own gives me twice the frame rate of Debian's nvidia-glx (Sid).
>
> Nvidia is looking for some Xorg SDK to tell it where to place its module.
> Not finding that, it uses the default /usr/lib which means interference
> with/by xorg glx packages. Each time you put in new Xorg stuff, simply
> rerun their installer. A bit of a bother but as you said, a few minutes.
>
> Examin their "advanced" options. There may be a way to tell it where to
> install the glx stuff. Then simply have xorg.conf check modules there
> first :-)

When I (cough) installed nvidia's own installer I installed xorg-dev first so 
it could figure out where to put stuff. I'm running with an m-a installed 
module now and am having good results. Wish I had checked the frame rate but 
it seems to be working well in any case.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[David Baron]

On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
> On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> > With this install of Debian I decided to stick to what I know, and
> > grabbed the binary installer direct from NVidia.  I ran that, and in
> > less than two minutes I was up and running.  No complaints from Debian
> > and no complaints from NVidia.  Oh, except for one because I had tried
> > to compile it before I updated the system fully and so I had a gcc
> > which didn't match the kernel, but that was fixed in no time.
>
> Apparently the binary installer from NVidia messes with the libraries on
> the system and is not the recommended method for installing.
>
> Read http://home.comcast.net/~andrex/Debian-nVidia/
>
> The Debian way is certainly a lot easier. Now where has that nvidia-glx
> package gone?

Nvidia's own gives me twice the frame rate of Debian's nvidia-glx (Sid).

Nvidia is looking for some Xorg SDK to tell it where to place its module. Not 
finding that, it uses the default /usr/lib which means interference with/by 
xorg glx packages. Each time you put in new Xorg stuff, simply rerun their 
installer. A bit of a bother but as you said, a few minutes.

Examin their "advanced" options. There may be a way to tell it where to 
install the glx stuff. Then simply have xorg.conf check modules there 
first :-)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[cothrige]

* Chris Bannister ([EMAIL PROTECTED]) wrote:
> 
> Apparently the binary installer from NVidia messes with the libraries on
> the system and is not the recommended method for installing.
> 
> Read http://home.comcast.net/~andrex/Debian-nVidia/
> 
> The Debian way is certainly a lot easier. Now where has that nvidia-glx
> package gone?
> 

Well, that is exactly the problem.  I tried several times initially to
install it via apt but it could never do it.  IIRC, there was no
nvidia-glx package and so it would not install.  This was a test of an
installation BTW which ended up being only temporary.  When I finally
committed and gave over my main partition to Debian I decided to
simply try it the old fashioned way and see how it went.  So far so
good, though I expect that may change at any time.  Many thanks for
the howto though.  The next time I compile a kernel I will try it the
Debian way, just to see how I perhaps messed up the first time.

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a Nvidia module [was Re: Compiling a kernel]

[Chris Bannister]

On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> With this install of Debian I decided to stick to what I know, and
> grabbed the binary installer direct from NVidia.  I ran that, and in
> less than two minutes I was up and running.  No complaints from Debian
> and no complaints from NVidia.  Oh, except for one because I had tried
> to compile it before I updated the system fully and so I had a gcc
> which didn't match the kernel, but that was fixed in no time.

Apparently the binary installer from NVidia messes with the libraries on
the system and is not the recommended method for installing.

Read http://home.comcast.net/~andrex/Debian-nVidia/

The Debian way is certainly a lot easier. Now where has that nvidia-glx
package gone?

-- 
Chris.
==
" ... the official version cannot be abandoned because the implication of
rejecting it is far too disturbing: that we are subject to a government
conspiracy of `X-Files' proportions and insidiousness."
Letter to the LA Times Magazine, September 18, 2005.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Michael D. Norwick]

[EMAIL PROTECTED] wrote:

>You have gotten a couple DIFFERENT approaches to installing a kernel on
Debian.
>At least one comment should send up a warning:

Yes, a level-minded user.

>On compiling with --initrd, I finally drank the coolade last year. 
Before I tried to have no
>modules, compiling needed modules into the kernel itself.  Since
everyone now compiles
>oodles of modules, mostly uneeded, but, unknown uneeded, instructions
now usually talk
>about modules.  As others in this thread have mentioned.

I just finally succumbed to the Jim Jones thing in the last couple of
days after years of
building non-initrd kernels on Debian due to a strong dislike of devfs. 
I do not know if it
is intentional on the part of the Debian development team to force
initrd on the population,
but, I have found it quite difficult, and very time consuming, trying to
build and boot a non-
initrd kernel from the 2.6.1x series.  No need for the rtfm/google is
your friend' stuff I have
most of the current Debian docs from packages, self edited
OpenOffice.org libraries, and
web picked pdf's.
All I wanted was to locally build a trusted 2.6.18 series kernel with
CITI_NFS4 patches.
After several build iterations on a -rc6 source tree.  The one that
finally booted without a
'kernel panic: vfs: error root fileysystem not found' error, was a
'make-kpkg --initrd'
build.
Per usual, the alsa system still won't greet me when KDE starts, though
all the modules are
loaded, but this thing runs as a kerberos slave with our ldap database
replicated to it.  So
sound sucks, and I guess I don't need it (more like, I don't have time
to screw with it).

I guess while I'm ranting;  Linux was promoted years ago as being able
to run on outdated
hardware.  My budget does not allow me to purchase the latest hardware
pushed down to
us by Intel, AMD, and MS, every millisecond.  But it sure seems like Linux
(all distributions) and the 'BSD's for that matter, have developed a
preference for
recent (within the last three years) hardware.  Maybe I'm confusing
'able' and 'useable'.

Oh well, I think there might be something for me in 'man kernel-img.conf'.

Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* Jameson C. Burt ([EMAIL PROTECTED]) wrote:
> You have gotten a couple DIFFERENT approaches to installing a kernel on
> Debian.
> At least one comment should send up a warning:
> if the approach becomes too intricate, or requires specialization,
> very likely you read minute details that you should never need learn
> (unless you're creating Debian packages).
[...]

Yes, I am trying to avoid extremely involved approaches just so I
don't do things I won't know how to undo later.  I always try to
understand just how I can backtrack after some action in order to
avoid real lasting irreparable damage.  Eventually that was what
became of my foray into Gentoo, or at least partly, and I would hope
to avoid doing that again.

[...]
> It's surprising how many new options get added with each new kernel,
> so "make oldconfig" can take 30 minutes, or even 2 hours if you go from a 
> running
> 2.4.* kernel to a 2.6.18 kernel (then, you need to rethink all this).

It has certainly surprised me, again and again.  If I go any period at
all with a kernel, by the time I go back to recompile a new one I am
mired in reading trying to understand what all of these new options
do.  This time I had a string of errors and then a kernel panic in the
process of hammering out what some of it out.

> I recently installed (largely the Debian way) kernel 2.6.18.1,
> which isn't available in the current Debian testing version (etch)
> and anything beyond 2.6.16 probably never will be in etch 
> since etch is being stabilized to become "stable" in the next few
> months.

My install of etch has 2.6.17, so they must be moving pretty fast.
But, like you, I compiled the 2.6.18.1 today and it is running fine at this
time.  Thanks to all the help I received from those such as yourself
here at this list.

[...]
> Each time, I sequentially change my name with a sequence number from
> jameson2 to jameson3, jameson4, jameson5, ...,
> so my modules go into a different directory
> (modules get installed into their own directories like  
> /lib/2.6.18.1-jameson2-oldconfig/)
> This lets lets grub run my old kernels with their modules in their own
> /lib/* directory.
> Each such module directory uses about 50MB.

Many thanks for this tip.  Since my new kernel was different from the
previous, I upgraded from 2.6.17 to 2.6.18, I did not need to worry
about that.  But, it will be very handy when I need to compile again
and don't want to clobber all of my modules.  This is the second very
useful tip in that area I have read on this list.

> On compiling with  --initrd, I finally drank the coolade last year.
> Before, I tried to have no modules, compiling needed modules into the
> kernel itself.  
> Since almost everyone now compiles oodles of modules, mostly uneeded,  
> but unknown uneeded, instructions now usually talk about modules.
> As others in this thread have mentioned,
> when booting, some necessary modules must be accessed right away,
> so you are better off compiling with  --initrd.

Or you could use my method mentioned above, and just wait for kernel
panics. ;-) I actually did manage to have a fairly modular kernel with
those absolute necessities builtin.  And because the old kernel and
modules are still on board if something fatal does go wrong at least I
can go back and begin again.  Or, I hope I can.

> You mentioned NVidia.
> I presume you have an Nvidia card with 3D acceleration.
> Without using NVidia's binary driver, you will find XWindows using the
> open-source "nv" WWindows driver, 
> and being slow even though you don't run games.
> To install NVidia's driver, you either most use an older kernel 
> corresponding to Debian's packages that help with NVidia's binaries,
> or you must run an NVidia executable.
> I have tried both.
> Since I use kernels newer than Debian has in testing (etch), 
> I go to nvidia.com, get NVidia's driver, then run it.

I actually did this with the Debian kernel.  It is always what I did
with Slack and so I am used to it.  I had installed Ubuntu a couple of
weeks ago, (no offense to the Ubuntu folks but I wasn't crazy about
it), and I worked the better part of two days trying to get my nvidia
card working.  I read page after page of howtos and fora or list
messages, and none agreed on how to do it, except that you would hose
your system if you used the drivers from nvidia.  Well, I hosed the
system doing it the "ubuntu" way, because just as I try to avoid I
ended up doing things I didn't understand and so could not undo.  One
error stacked up on another and pretty soon it was bye-bye Ubuntu.

With this install of Debian I decided to stick to what I know, and
grabbed the binary installer direct from NVidia.  I ran that, and in
less than two minutes I was up and running.  No complaints from Debian
and no complaints from NVidia.  Oh, except for one because I had tried
to compile it before I updated the system fully and so I had a gcc
which didn't match the kernel, but that was fixed in no time.

> While getting a

Re: Compiling a kernel

[David A.]

I look here when I compile my own kernel:
http://kernel-handbook.alioth.debian.org/

/David.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Jameson C. Burt]

You have gotten a couple DIFFERENT approaches to installing a kernel on
Debian.
At least one comment should send up a warning:
if the approach becomes too intricate, or requires specialization,
very likely you read minute details that you should never need learn
(unless you're creating Debian packages).
Indeed, to follow such minute details would create configuration files
that would hinder later trying standard Debian approaches.
In particular, the standard Linux kernel package approach to installation from 
README in
every tar file from  ftp.kernel.org
should become fewer steps under Debian. 
To get the latest Linux kernels, you can still get your kernels from
ftp.kernel.org, although this may not seem as straight forward.
The Debian kernel packages are infrequently coordinated with another 
package like an nvidia 3D XWindows driver.

I myself put ftp.kernel.org kernels in /usr/local/src/kernels,
since I run out of room in /usr/src 
(EACH uncompressed kernel package takes 600MB -- almost 1GB).
In the past, you probably ran  "make xconfig" or one of its equivalents
-- you can still do this before continuing with the standard Debian
approach. 
Although, if you follow standard Debian
procedure with packages only, you get almost every module compiled so  "make 
xconfig"
might become something you merely run and immediately exit.

With a previous Debian kernel package installed and running,
and with a new kernel, you probably want to coordinate
the options of the new kernel with your running kernel.
That is, you want to get a corresponding .config file,
so copy your running kernel's (uname -a) config file something like
   cp  /boot/config-2.6.17-2-486   .config
to the directory where your kernel package resides
(with a particular kernel setting, you once could find these in
/proc/config.gz, but I haven't seen these in a year).
Then, before any  "make xconfig",  run 
   make oldconfig
to which you probably select the "M" or module answer to  most
questions, although some questions only allow yes/no.
When booting, some application with "apple" (probably looking for an apple 
network)
was hanging bootup for about 1 minute, so I eventually removed that from
the kernel.
It's surprising how many new options get added with each new kernel,
so "make oldconfig" can take 30 minutes, or even 2 hours if you go from a 
running
2.4.* kernel to a 2.6.18 kernel (then, you need to rethink all this).

I recently installed (largely the Debian way) kernel 2.6.18.1,
which isn't available in the current Debian testing version (etch)
and anything beyond 2.6.16 probably never will be in etch 
since etch is being stabilized to become "stable" in the next few
months.
You are probably installing testing (etch), since stable is quite old
now, and its kernels are archaic.

When I compile my kernels, I always do something like
   CONCURRENCY_LEVEL=2   make-kpkg  --initrd  --append-to-version \
   '-jameson2-oldconfig'  kernel-image
for 2 processors to finish more quickly, but with 1 processor you 
might just run something like
   make-kpkg  --initrd  --append-to-version '-jameson2-oldconfig'  \
   kernel-image
Each time, I sequentially change my name with a sequence number from
jameson2 to jameson3, jameson4, jameson5, ...,
so my modules go into a different directory
(modules get installed into their own directories like  
/lib/2.6.18.1-jameson2-oldconfig/)
This lets lets grub run my old kernels with their modules in their own
/lib/* directory.
Each such module directory uses about 50MB.

On compiling with  --initrd, I finally drank the coolade last year.
Before, I tried to have no modules, compiling needed modules into the
kernel itself.  
Since almost everyone now compiles oodles of modules, mostly uneeded,  
but unknown uneeded, instructions now usually talk about modules.
As others in this thread have mentioned,
when booting, some necessary modules must be accessed right away,
so you are better off compiling with  --initrd.

You mentioned NVidia.
I presume you have an Nvidia card with 3D acceleration.
Without using NVidia's binary driver, you will find XWindows using the
open-source "nv" WWindows driver, 
and being slow even though you don't run games.
To install NVidia's driver, you either most use an older kernel 
corresponding to Debian's packages that help with NVidia's binaries,
or you must run an NVidia executable.
I have tried both.
Since I use kernels newer than Debian has in testing (etch), 
I go to nvidia.com, get NVidia's driver, then run it.
While getting an executable from nvidia.com directly worked well,
I noticed that it must have overwitten a few Debian installed files.
So when I upgrade Debian, I am prepared (but haven't seen)
for possible graphics oddities, in which case I would rerun nvidia.com's 
executable to re-ovewrite those files.

You have heard from many of us, some complementing others information,
some giving non-Debian approaches, and you don't really know who to
listen to.
YOU NEED TO GO TO A DEB

Re: Compiling a kernel

[Yura]

John O'Hagan wrote:

On Sunday 22 October 2006 18:02, cothrige wrote:
[...]
  

In the past, as a Slackware user, I never installed an OS where I
didn't immediately compile a new kernel.  Slack uses a 2.4 kernel, and
I use some peripheral items which seem to require, or at least greatly
prefer a 2.6 kernel.  The process I used was very simple, and I got
quite used to it.  I downloaded the sources from www.kernel.org and
opened them up in /usr/src/.  I then would run 'make menuconfig',
'make' and 'make modules_install.'  I copied the bzImage into /boot,
as well as the System.map and config file.  I edited lilo.conf, ran
/sbin/lilo and rebooted into the new kernel.  All usually went well
and I rarely had to look back.



[...]
  

Or, is there maybe a Debian tool to compile a kernel which is
intended to be used rather than this "classic" method?  While things
seem fine with the kernel installed from apt, better than fine
actually, I figure the day is going to come when I will need to
compile a new kernel, and I would like to know if possible what to
expect.  Not to mention just plain how to do it.


[...]

Hi Patrick,

I always compile my own kernels the Debian (testing) way like this:

-Install the latest Debian linux-source package (currently 
linux-source-2.6.17); or you can use vanilla source as you describe
  
Can't find linux-source using apt, may be kernel-source? I've found 
kernel-source-2.6.11. Is it the newest?
-Make a symlink /usr/src/linux to the resulting 
folder /usr/src/linux-source-2.6.17 (is this step still necessary?)

-Configure the kernel
-In /usr/src/linux, run "make-kpkg buildpackage kernel-image" (there are other 
options, in the man page)

-Install the resulting .deb packages in /usr/src with dpkg -i
- Reboot into your new kernel

This will build a kernel without an initrd, so you must compile in all drivers 
for the the boot disk(s). Or use the --initrd option.


If you are recompiling a kernel with the same version name, you must 
move /lib/modules/[$KERNEL_VERSION] out of the way (you are warned if you 
forget!), or you can use the --revision or --append-to-version options to 
avoid this.


HTH,

John


  



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* Andrei Popescu ([EMAIL PROTECTED]) wrote:
> 
> initrd's are especially useful for distros, because a kernel with all
> stuff compiled in is not an option (too big), but you still need some
> of the modules very early in the boot process, when the root filesystem
> is not accessible yet. For your particular system you can afford to
> compile everything in, because you know exactly what you need and what
> you don't.

That does make sense.  I can see how it would make sense in that
situation.  It should have occurred to me, but I suppose I was just
not taking the time to look at it from all sides.  Thanks for the
clarification.

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Damon L. Chesser]

cothrige wrote:

* Tim Post ([EMAIL PROTECTED]) wrote:
  

depmod should be called by the makefile upon make modules_install after
a successful build. Its really as easy as make, make modules_install ,
make install and a mkinitrd (if you need one). 


If using GRUB, remember by default the selection menu is hidden. You'll
need to comment out the "hiddenmenu" line, and of course turn on pretty
colors.



Okay, a touch of confusion on this.  I am unfamiliar with grub, only
having started using it with this install of Debian and that having
been setup by the Debian installer.  Right now the menu is not hidden,
but are you saying that a 'make install' of the kernel will add
hiddenmenu to my configuration?  BTW, I have never used make install,
kinda scary I suppose, and so don't know much about it.  Probably
won't use it now either, unless it is highly recommended.

  

/etc/modules is a newline delimited list of modules that are loaded at
boot time.



What is the difference between this and the modprobe.d files?  I
notice that my system has both (alsa, nvidia and such in modprobe.d
and loop is all that is in modules).  The man pages didn't seem to
clarify why both are needed.

  

You can further tweak how modules are loaded by modifying your initrd
directly.


[snip]

I have never used initrd, at least not when I have compiled a kernel.
To be entirely honest I have never fully understood just what it
does.  I was under the impression it was for things like booting from
reiser fs and having to load modules to do it.  However, that always
made me wonder why a person would just not compile in the reiser
support, and so I have naturally assumed that I was dead wrong on why
it existed and what it accomplished.  But, since I have never seemed
to need it, i.e. my system has always booted fairly predictably
without it, I never tried to learn more.

  

Kernel hacking is quite a bit easier on GNU distributions (like Debian)
once you get used to the differences from whitebox / gentoo. Not saying
its not fun on those flavors, I just happen to really prefer GNU.



I am going to open my mouth and prove my total ignorance, as I have
never even approached any kernel hacking.  But, what is a 'whitebox'
and how is it different from GNU?  I would have thought that Gentoo
was a GNU distro.

Many thanks,

Patrick


  

Patrick,

Not just reiserfs but say if your hard drive type was a modual (ide, 
sata, etc).  Yes it is cleaner perhaps to hard code it in, but on the 
other hand, if you miss one item in the chain, you get kernel panic.  I 
would suggest you install kernel-package and read the README in 
/usr/share/doc/kernel-package .  It has a rather complete  walk through 
on how to do it the debian way, including the initrd.  

Make-kpkg will in fact make all the moduals, add them, and the kernel 
and make a .deb you then use dpkg -i kernelname.deb  to install, and 
that will modify grub for you (or lilo I suspose).  Comes in real handy 
if you have more then one box with the same hardware, just transfer the 
.deb and install it.  Plus now your system knows it is installed and if 
you use the make-kpgk --append-to=customename_or_number_here then apt 
will not replace your kernel (unless you happen to name it something 
that matches a apt-getable kernel.  Real nice.


I hope that helps.

--
Damon L. Chesser
[EMAIL PROTECTED]
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Andrei Popescu]

cothrige <[EMAIL PROTECTED]> wrote:

> I have never used initrd, at least not when I have compiled a kernel.
> To be entirely honest I have never fully understood just what it
> does.  I was under the impression it was for things like booting from
> reiser fs and having to load modules to do it.  However, that always
> made me wonder why a person would just not compile in the reiser
> support, and so I have naturally assumed that I was dead wrong on why
> it existed and what it accomplished.  But, since I have never seemed
> to need it, i.e. my system has always booted fairly predictably
> without it, I never tried to learn more.

initrd's are especially useful for distros, because a kernel with all
stuff compiled in is not an option (too big), but you still need some
of the modules very early in the boot process, when the root filesystem
is not accessible yet. For your particular system you can afford to
compile everything in, because you know exactly what you need and what
you don't.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* John O'Hagan ([EMAIL PROTECTED]) wrote:
> 
> Installing the kernel-package generated by make-kpkg will automatically 
> detect 
> and update grub, and add itself to menu.list. How easy is that?

Now that it is a nifty feature.  I suppose there is certainly
something to be said for the Debian approach to this after all.

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* Gilles Mocellin ([EMAIL PROTECTED]) wrote:
> 
> This modprobe.conf is modularized in several files (you can add one) 
> in /etc/modprobe.d/.

Ahh yes, I see that.  I would think I could run
'generate-modprobe.conf > ~/modprobe.conf' and then split the info up
as I need it.  Shouldn't be too impossible I would think.

Thanks,

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* Tim Post ([EMAIL PROTECTED]) wrote:
> depmod should be called by the makefile upon make modules_install after
> a successful build. Its really as easy as make, make modules_install ,
> make install and a mkinitrd (if you need one). 
> 
> If using GRUB, remember by default the selection menu is hidden. You'll
> need to comment out the "hiddenmenu" line, and of course turn on pretty
> colors.

Okay, a touch of confusion on this.  I am unfamiliar with grub, only
having started using it with this install of Debian and that having
been setup by the Debian installer.  Right now the menu is not hidden,
but are you saying that a 'make install' of the kernel will add
hiddenmenu to my configuration?  BTW, I have never used make install,
kinda scary I suppose, and so don't know much about it.  Probably
won't use it now either, unless it is highly recommended.

> /etc/modules is a newline delimited list of modules that are loaded at
> boot time.

What is the difference between this and the modprobe.d files?  I
notice that my system has both (alsa, nvidia and such in modprobe.d
and loop is all that is in modules).  The man pages didn't seem to
clarify why both are needed.

> You can further tweak how modules are loaded by modifying your initrd
> directly.
[snip]

I have never used initrd, at least not when I have compiled a kernel.
To be entirely honest I have never fully understood just what it
does.  I was under the impression it was for things like booting from
reiser fs and having to load modules to do it.  However, that always
made me wonder why a person would just not compile in the reiser
support, and so I have naturally assumed that I was dead wrong on why
it existed and what it accomplished.  But, since I have never seemed
to need it, i.e. my system has always booted fairly predictably
without it, I never tried to learn more.

> Kernel hacking is quite a bit easier on GNU distributions (like Debian)
> once you get used to the differences from whitebox / gentoo. Not saying
> its not fun on those flavors, I just happen to really prefer GNU.

I am going to open my mouth and prove my total ignorance, as I have
never even approached any kernel hacking.  But, what is a 'whitebox'
and how is it different from GNU?  I would have thought that Gentoo
was a GNU distro.

Many thanks,

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Tim Post]

depmod should be called by the makefile upon make modules_install after
a successful build. Its really as easy as make, make modules_install ,
make install and a mkinitrd (if you need one). 

If using GRUB, remember by default the selection menu is hidden. You'll
need to comment out the "hiddenmenu" line, and of course turn on pretty
colors.

/etc/modules is a newline delimited list of modules that are loaded at
boot time.

You can further tweak how modules are loaded by modifying your initrd
directly. You'll need to do this if you use things like AoE/iSCSI to
access the root file system you pass to your kernel (i.e.
root=/dev/etherd/e3.0) or any service that loads and unloads its own
modules to start / stop but must be on in order to boot. You shouldn't
need to unless you have a custom / unique setup, but here's how anyway -

Just mount it :

mkdir /tmp/initrd-mnt

modprobe loop
mount -o loop -t cramfs /boot/my.initrd-img.x.x.x /tmp/initrd-mnt

Then simply pico the file named "linuxrc", or edit the file containing
the list of modules. You'll see the modprobe lines loading modules, feel
free to add or detract :) This is really handy to get things like
AoE/iSCSI or cluster file systems going prior to mounting the root fs or
any other odd boot needs.

Just remember, linuxrc isn't smart, its mission is only to load modules
and pivot over to the root fs you specify... so make sure you add some
logic to deal with mod load failures if they happen (if you tinker, that
is).

Kernel hacking is quite a bit easier on GNU distributions (like Debian)
once you get used to the differences from whitebox / gentoo. Not saying
its not fun on those flavors, I just happen to really prefer GNU.

Many more comprehensive step by step kernel building tutorials are
easily found via Google .. this should be enough to get you going with a
degree of confidence however :)

HTH

Best,
-Tim

On Sun, 2006-10-22 at 09:43 -0500, cothrige wrote:
> * Tim Post ([EMAIL PROTECTED]) wrote:
> 
> Hello Tim,
> 
> [snip] 
> > Then make your initrd if needed and tweak as needed, verify /etc/modules
> > is what you want it to be and you should be good to go. Cross your
> > fingers and reboot.
> 
> This makes me think.  Recently I have gotten in the habit, after
> installing the kernel and all the associated parts, of running
> generate-modprobe.conf to get all the modules covered.  But, it seems
> that there is no modprobe.conf in Debian, and so I wonder if there is
> a similar tool or method to generate the information covering the
> modules?  Before I ran this I would have to really hunt around to
> cover the alsa stuff and so on, and so it was a nice shortcut.
> 
> Thanks a lot,
> 
> Patrick
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[John O'Hagan]

On Monday 23 October 2006 00:36, cothrige wrote:
> * John O'Hagan ([EMAIL PROTECTED]) wrote:

>>[snip summary of Debian kernel compilation]

> Will I still have to configure grub?  And will update-grub work or
> will I have to manually edit menu.lst?  
[...]

Installing the kernel-package generated by make-kpkg will automatically detect 
and update grub, and add itself to menu.list. How easy is that?

Regards,

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Gilles Mocellin]

Le dimanche 22 octobre 2006 16:43, cothrige a écrit :
> * Tim Post ([EMAIL PROTECTED]) wrote:
>
> Hello Tim,
>
> [snip]
>
> > Then make your initrd if needed and tweak as needed, verify /etc/modules
> > is what you want it to be and you should be good to go. Cross your
> > fingers and reboot.
>
> This makes me think.  Recently I have gotten in the habit, after
> installing the kernel and all the associated parts, of running
> generate-modprobe.conf to get all the modules covered.  But, it seems
> that there is no modprobe.conf in Debian, and so I wonder if there is
> a similar tool or method to generate the information covering the
> modules?  Before I ran this I would have to really hunt around to
> cover the alsa stuff and so on, and so it was a nice shortcut.

This modprobe.conf is modularized in several files (you can add one) 
in /etc/modprobe.d/.


pgpsn3q6uXsut.pgp
Description: PGP signature

Re: Compiling a kernel

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/22/06 09:36, cothrige wrote:
> * John O'Hagan ([EMAIL PROTECTED]) wrote:
>> Hi Patrick,
> 
> Hello John,
>  
[snip]
>> If you are recompiling a kernel with the same version name, you must 
>> move /lib/modules/[$KERNEL_VERSION] out of the way (you are warned if you 
>> forget!), or you can use the --revision or --append-to-version options to 
>> avoid this.

Or edit the CONFIG_LOCALVERSION line of /usr/src/linux/.config.

> This is new to me.  Will these flags stop clobbering of my modules?

Yes.

> If so, that is a very cool feature.  I forget to move my modules at
> least half of the time and it really stinks.  I think it is because in
> Slack since I was going from a 2.4 to a 2.6 it never seemed to
> matter.  I am going to do some reading on this.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFO4QjS9HxQb37XmcRApgKAJ9JxmTNiMF3qWjIyWqYVVhysdnHqQCgzFzB
Gg12/+mviMDqkuNrTpKfTOw=
=nrBp
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* Tim Post ([EMAIL PROTECTED]) wrote:

Hello Tim,

[snip] 
> Then make your initrd if needed and tweak as needed, verify /etc/modules
> is what you want it to be and you should be good to go. Cross your
> fingers and reboot.

This makes me think.  Recently I have gotten in the habit, after
installing the kernel and all the associated parts, of running
generate-modprobe.conf to get all the modules covered.  But, it seems
that there is no modprobe.conf in Debian, and so I wonder if there is
a similar tool or method to generate the information covering the
modules?  Before I ran this I would have to really hunt around to
cover the alsa stuff and so on, and so it was a nice shortcut.

Thanks a lot,

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[cothrige]

* John O'Hagan ([EMAIL PROTECTED]) wrote:
> Hi Patrick,

Hello John,
 
> I always compile my own kernels the Debian (testing) way like this:
> 
> -Install the latest Debian linux-source package (currently 
> linux-source-2.6.17); or you can use vanilla source as you describe
> -Make a symlink /usr/src/linux to the resulting 
> folder /usr/src/linux-source-2.6.17 (is this step still necessary?)

I have wondered this too.  I always do it, but it seems like I read
something somwhere suggesting that it is not needed.

> -Configure the kernel
> -In /usr/src/linux, run "make-kpkg buildpackage kernel-image" (there are 
> other 
> options, in the man page)
> -Install the resulting .deb packages in /usr/src with dpkg -i

Will I still have to configure grub?  And will update-grub work or
will I have to manually edit menu.lst?  I am still getting the hang of
grub.  It was never a part of Slackware and so I had become very
comfortable with lilo.

> - Reboot into your new kernel
> 
> This will build a kernel without an initrd, so you must compile in all 
> drivers 
> for the the boot disk(s). Or use the --initrd option.

I prefer to go without initrd myself.  Just seems a tad faster, though
probably my imagination.
 
> If you are recompiling a kernel with the same version name, you must 
> move /lib/modules/[$KERNEL_VERSION] out of the way (you are warned if you 
> forget!), or you can use the --revision or --append-to-version options to 
> avoid this.

This is new to me.  Will these flags stop clobbering of my modules?
If so, that is a very cool feature.  I forget to move my modules at
least half of the time and it really stinks.  I think it is because in
Slack since I was going from a 2.4 to a 2.6 it never seemed to
matter.  I am going to do some reading on this.

Many thanks for the help.

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[John O'Hagan]

On Sunday 22 October 2006 18:02, cothrige wrote:
[...]
> In the past, as a Slackware user, I never installed an OS where I
> didn't immediately compile a new kernel.  Slack uses a 2.4 kernel, and
> I use some peripheral items which seem to require, or at least greatly
> prefer a 2.6 kernel.  The process I used was very simple, and I got
> quite used to it.  I downloaded the sources from www.kernel.org and
> opened them up in /usr/src/.  I then would run 'make menuconfig',
> 'make' and 'make modules_install.'  I copied the bzImage into /boot,
> as well as the System.map and config file.  I edited lilo.conf, ran
> /sbin/lilo and rebooted into the new kernel.  All usually went well
> and I rarely had to look back.
>
[...]
> Or, is there maybe a Debian tool to compile a kernel which is
> intended to be used rather than this "classic" method?  While things
> seem fine with the kernel installed from apt, better than fine
> actually, I figure the day is going to come when I will need to
> compile a new kernel, and I would like to know if possible what to
> expect.  Not to mention just plain how to do it.
[...]

Hi Patrick,

I always compile my own kernels the Debian (testing) way like this:

-Install the latest Debian linux-source package (currently 
linux-source-2.6.17); or you can use vanilla source as you describe
-Make a symlink /usr/src/linux to the resulting 
folder /usr/src/linux-source-2.6.17 (is this step still necessary?)
-Configure the kernel
-In /usr/src/linux, run "make-kpkg buildpackage kernel-image" (there are other 
options, in the man page)
-Install the resulting .deb packages in /usr/src with dpkg -i
- Reboot into your new kernel

This will build a kernel without an initrd, so you must compile in all drivers 
for the the boot disk(s). Or use the --initrd option.

If you are recompiling a kernel with the same version name, you must 
move /lib/modules/[$KERNEL_VERSION] out of the way (you are warned if you 
forget!), or you can use the --revision or --append-to-version options to 
avoid this.

HTH,

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Tim Post]

Patrick, 

Its relatively easy .. and you can make it a bit easier on yourself.

Untar from kernel.org in /usr/src

be sure ncurses-dev and ncurses are present

make menuconfig and configure your kernel

now make (or make -j xx, where xx = # of cpu's if > 1) [ fancy gcc hacks
go here if your brave ]

if modular - make modules_install
make install (will copy vmlinuz and friends to /boot)

I typically use grub, however I think it will update lilo for you if
present and in use. 

Then make your initrd if needed and tweak as needed, verify /etc/modules
is what you want it to be and you should be good to go. Cross your
fingers and reboot.

Really very little difference at all. "make help" is also very helpful. 

HTH

Best,
-Tim

On Sun, 2006-10-22 at 03:02 -0500, cothrige wrote:
> I am sure this is a really stupid question, but having read through
> the reference and searched online (some searches involve such common
> terms they never return anything useful) I have really been unable to
> find a clear answer.  I hope someone here can help.
> 
> In the past, as a Slackware user, I never installed an OS where I
> didn't immediately compile a new kernel.  Slack uses a 2.4 kernel, and
> I use some peripheral items which seem to require, or at least greatly
> prefer a 2.6 kernel.  The process I used was very simple, and I got
> quite used to it.  I downloaded the sources from www.kernel.org and
> opened them up in /usr/src/.  I then would run 'make menuconfig',
> 'make' and 'make modules_install.'  I copied the bzImage into /boot,
> as well as the System.map and config file.  I edited lilo.conf, ran
> /sbin/lilo and rebooted into the new kernel.  All usually went well
> and I rarely had to look back.
> 
> However, I cannot find out if this will work in Debian.  (I am using
> grub so obviously the lilo thing would not) The entire system behind
> everything seems so much more detailed and complex than Slack that I
> have my doubts this will work at all.  Do I have to use kernel sources
> from Debian?  And will this completely throw off dependency situations
> in apt?  Or, is there maybe a Debian tool to compile a kernel which is
> intended to be used rather than this "classic" method?  While things
> seem fine with the kernel installed from apt, better than fine
> actually, I figure the day is going to come when I will need to
> compile a new kernel, and I would like to know if possible what to
> expect.  Not to mention just plain how to do it.
> 
> Many thanks in advance,
> 
> Patrick
> 
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Seweryn Kokot]

For more than a year I compile my kernels the way you described
(universal vay) and I have no problems. Of course there is a debian
way but it's not a must.

Regards,
Seweryn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel

[Andrei Popescu]

cothrige <[EMAIL PROTECTED]> wrote:

> I am sure this is a really stupid question, but having read through
> the reference and searched online (some searches involve such common
> terms they never return anything useful) I have really been unable to
> find a clear answer.  I hope someone here can help.

I never compiled on Debian, but I watched many threads so I hope I can
give you a few pointers.

The Debian Way (tm) to compile a kernel is using make-kpkg. This will
create a .deb which you can install using 'dpkg -i'. I haven't done
this myself, but the archives of this list contain many examples.
AFAICT this can be done with sources from kernel.org as well.

The default Debian kernel needs an initrd because it has many things
compiled as modules. You might be able to avoid the initrd if you
compile most (or everything) in. YMMV

You can compile a kernel from scratch using the classic method. After
you copy the image in /boot just run update-grub and it will add it to
your boot menu. You might want to read the notes in
/boot/grub/menu.lst if you want/need to add boot options.

HTH,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a kernel

[cothrige]

I am sure this is a really stupid question, but having read through
the reference and searched online (some searches involve such common
terms they never return anything useful) I have really been unable to
find a clear answer.  I hope someone here can help.

In the past, as a Slackware user, I never installed an OS where I
didn't immediately compile a new kernel.  Slack uses a 2.4 kernel, and
I use some peripheral items which seem to require, or at least greatly
prefer a 2.6 kernel.  The process I used was very simple, and I got
quite used to it.  I downloaded the sources from www.kernel.org and
opened them up in /usr/src/.  I then would run 'make menuconfig',
'make' and 'make modules_install.'  I copied the bzImage into /boot,
as well as the System.map and config file.  I edited lilo.conf, ran
/sbin/lilo and rebooted into the new kernel.  All usually went well
and I rarely had to look back.

However, I cannot find out if this will work in Debian.  (I am using
grub so obviously the lilo thing would not) The entire system behind
everything seems so much more detailed and complex than Slack that I
have my doubts this will work at all.  Do I have to use kernel sources
from Debian?  And will this completely throw off dependency situations
in apt?  Or, is there maybe a Debian tool to compile a kernel which is
intended to be used rather than this "classic" method?  While things
seem fine with the kernel installed from apt, better than fine
actually, I figure the day is going to come when I will need to
compile a new kernel, and I would like to know if possible what to
expect.  Not to mention just plain how to do it.

Many thanks in advance,

Patrick

Re: Compiling a kernel without making a .deb package.

[Micha Feigin]

On Wed, Dec 10, 2003 at 10:02:28AM -0600, John Foster wrote:
> Joseph Jones wrote:
> 
> >I can compile a kernel into a .deb package as described in the 
> >newbiedoc, but I need to compile a kernel with drivers for my laptop's 
> >NIC so I can make a rescue disc to do a network install from. Could 
> >anyone advise me as to how I do this, if possible in relation to the 
> >instructions in the newbiedoc?
> >
> >Thanks :)
> >
> >Joe
> >
> >
> ___
> Download a kernel tarball from http:// www.kernel.org  & open it into a 
> directory on the compiling system /usr/src/linux ; make sure you have 
> the correct modutils installed for the kernel version being 
> compiled.Read and follow exactly the instructions contained in the 
> tarball for compiling the kernel. Depending on your hardware 
> requirement, this may be easy or not:-)
> 

I coming in, in the middle so forgive me if I repeat things.
You can build the kernel using make [x,m,old]config, make clean, make
dep, make bzImage, make modules, make install.
To make things somewhat simpler, you can build the deb package and then
do
ar x 
this will give you three files. The data.tar.gz is the actual
installation in the right directory tree for the kernel including the
kernel, modules and documentation.

> John Foster
> 
> 
> 
> 
> -- 
> 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 a Kernel - Need ncurses

[Arnt Karlsen]

On Wed, 10 Dec 2003 22:16:25 -0800, 
"Scarletdown" <[EMAIL PROTECTED]> wrote in message 
<[EMAIL PROTECTED]>:

> I am once again giving a whirl at compiling a 2.4.22 kernel; this 
> time on my test box which I am telnetted into so I don't have to 
> keep switching back and forth via the KV switch.
> 
> Anyway, I managed to unpack the tarball and create the symbolic link 
> to it.  But when I try make menuconfig, I get the following:

..if you pipe is fat enough (lan or T1 etc) and that box has X, 
'make xconfig'.  Another way is 'make oldconfig', this takes 
you old ".config" for granted, and only ask for your input on 
new stuff.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Monique Y. Herman]

On Fri, 12 Dec 2003 at 03:00 GMT, Paul Stolp penned:
> * Monique Y. Herman <[EMAIL PROTECTED]> [2003-12-11 05:43]:
>> 
>> Btw, I just discovered that lilo bug #222098 appears to still be live
>> in 1:22.5.8-6.  It prevents me from running lilo successfully.  So
>> caveat emptor and all that ...
> 
> Hmm, same problem here. looked for a bug report, didn't see it was
> about to report. read this first.
> 

I found the solution embedded in another report, by the way.  Add the
following to your lilo.conf:

#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222099
disk=/dev/sda inaccessible
disk=/dev/sdb inaccessible

As near as I could figure from the response to the bug report, this is
not considered a bug so much as a "user education" issue.  I find that
weird, since I never had to add those lines before ... *shrug*

>> 
>> Now I just have to remember how to install an old version of a
>> package ... any hints?
> 
> lilo doesn't really have any dependencies, and I was getting
> desperate, so dpkg --force-all -i lilo_from_woody.deb
> 
> then put it on hold.
> 

I seem to remember woody's lilo being old enough to cause problems for
my system, but I can't recall why.  Anyway, the above lilo.conf mods
fixed it for me.

-- 
monique


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Paul Stolp]

* Monique Y. Herman <[EMAIL PROTECTED]> [2003-12-11 05:43]:
> 
> Btw, I just discovered that lilo bug #222098 appears to still be live in
> 1:22.5.8-6.  It prevents me from running lilo successfully.  So caveat
> emptor and all that ...

Hmm, same problem here. looked for a bug report, didn't see it was about
to report. read this first.

> 
> Now I just have to remember how to install an old version of a package
> ... any hints?

lilo doesn't really have any dependencies, and I was getting desperate,
so dpkg --force-all -i lilo_from_woody.deb

then put it on hold.

> 
> -- 
> monique
> 
> 
> -- 
> 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 a Kernel - Need ncurses

[James Williamson]

On Thursday 11 Dec 2003 6:16 am, Scarletdown wrote:
> I am once again giving a whirl at compiling a 2.4.22 kernel; this
> time on my test box which I am telnetted into so I don't have to
> keep switching back and forth via the KV switch.
>
> Anyway, I managed to unpack the tarball and create the symbolic link
> to it.  But when I try make menuconfig, I get the following:
>
> rm -f include/asm
> ( cd include ; ln -sf asm-i386 asm)
> make -C scripts/lxdialog all
> make[1]: Entering directory `/usr/src/linux-2.4.22/scripts/lxdialog'
> /usr/bin/ld: cannot find -lncurses
> collect2: ld returned 1 exit status
>
> >> Unable to find the Ncurses libraries.
> >>
> >> You must have Ncurses installed in order
> >> to use 'make menuconfig'

Not so much fun, but you could use make config which doesn't use
curses.

James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Kernel - Need ncurses

[Rob Benton]

try using libncurses5 and libncurses5-dev


On Thu, 2003-12-11 at 00:16, Scarletdown wrote:
> I am once again giving a whirl at compiling a 2.4.22 kernel; this time
> on my test box which I am telnetted into so I don't have to keep
> switching back and forth via the KV switch.
> 
> Anyway, I managed to unpack the tarball and create the symbolic link
> to it.  But when I try make menuconfig, I get the following:
> 
> rm -f include/asm
> ( cd include ; ln -sf asm-i386 asm)
> make -C scripts/lxdialog all
> make[1]: Entering directory `/usr/src/linux-2.4.22/scripts/lxdialog'
> /usr/bin/ld: cannot find -lncurses
> collect2: ld returned 1 exit status
> 
> >> Unable to find the Ncurses libraries.
> >>
> >> You must have Ncurses installed in order
> >> to use 'make menuconfig'
> 
> make[1]: *** [ncurses] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.22/scripts/lxdialog'
> make: *** [menuconfig] Error 2
> 
> I then tried installing ncurses using apt-get install ncurses
> 
> The dismal results follow:
> 
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Package ncurses has no available version, but exists in the database.
> This typically means that the package was mentioned in a dependency
> and
> never uploaded, has been obsoleted or is not available with the
> contents
> of sources.list
> E: Package ncurses has no installation candidate
> 
> Does this mean that ncurses simply can't be installed and I am SOL on
> getting this kernel compiled, or are there other ways besides apt-get
> install to get ncurses set up?
> 
> Also, after I get the new kernel compiled (if I get it compiled), how
> can I import it to another system without having to go through the
> whole process again?  Ultimately, this will be used on my primary
> workstation, which uses an Asus A7N8X Deluxe MB, and the NVidia
> drivers for this board require this new kernel (bf24 doesn't work for
> the NVidia drivers).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a Kernel - Need ncurses

[Scarletdown]

I am once again giving a whirl at compiling a 2.4.22 kernel; this 
time on my test box which I am telnetted into so I don't have to 
keep switching back and forth via the KV switch.


Anyway, I managed to unpack the tarball and create the symbolic link 
to it.  But when I try make menuconfig, I get the following:


rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts/lxdialog all
make[1]: Entering directory `/usr/src/linux-2.4.22/scripts/lxdialog'
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status


>> Unable to find the Ncurses libraries.
>>
>> You must have Ncurses installed in order
>> to use 'make menuconfig'


make[1]: *** [ncurses] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.22/scripts/lxdialog'
make: *** [menuconfig] Error 2


I then tried installing ncurses using apt-get install ncurses


The dismal results follow:


Reading Package Lists... Done
Building Dependency Tree... Done
Package ncurses has no available version, but exists in the 
database.
This typically means that the package was mentioned in a dependency 
and
never uploaded, has been obsoleted or is not available with the 
contents
of sources.list
E: Package ncurses has no installation candidate


Does this mean that ncurses simply can't be installed and I am SOL 
on getting this kernel compiled, or are there other ways besides 
apt-get install to get ncurses set up?


Also, after I get the new kernel compiled (if I get it compiled), 
how can I import it to another system without having to go through 
the whole process again?  Ultimately, this will be used on my 
primary workstation, which uses an Asus A7N8X Deluxe MB, and the 
NVidia drivers for this board require this new kernel (bf24 doesn't 
work for the NVidia drivers).

Re: Compiling a kernel without making a .deb package.

[Joseph Jones]

Monique Y. Herman wrote:

On Wed, 10 Dec 2003 at 16:02 GMT, John Foster penned:
 

Joseph Jones wrote:

   

I can compile a kernel into a .deb package as described in the
newbiedoc, but I need to compile a kernel with drivers for my
laptop's NIC so I can make a rescue disc to do a network install
from. Could anyone advise me as to how I do this, if possible in
relation to the instructions in the newbiedoc?
Thanks :)

Joe

 

___ Download a
kernel tarball from http:// www.kernel.org  & open it into a directory
on the compiling system /usr/src/linux ; make sure you have the
correct modutils installed for the kernel version being compiled.Read
and follow exactly the instructions contained in the tarball for
compiling the kernel. Depending on your hardware requirement, this may
be easy or not:-)
John Foster

   

You can compile debian's kernel without turning it into a .deb.

This is what I do (because it's what I've always done and I'm too lazy
to change).  Note: it does *not* use initrd!
dselect #get latest kernel src package
cd /usr/src/kernel-source-
make mrproper #clean any leftover compile stuff
make xconfig
make dep
make bzImage
make modules
make install #puts System.map, vmlinuz, config in /boot; moves last
#version to blah.old
make modules_install
vi lilo.conf
lilo
reboot
 

That sounds like what I want to do (I tried the methods in the how-to as 
suggested by Paul Johnson, but my system didn't seem to do anything for 
hours... no errors, nothing in the prompt... na-da, when I can usually 
compile a kernel in a .deb within minutes) apart from I need initrd in 
the kernel to make a rescue disc :(

Anyone have any other suggestions?

Joe

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Burkhard Woelfel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 10 December 2003 20:35, H. S. wrote:
> So now if I use mrproper, I *always* save my .config to some other
> directory, in my case in a tmp in a user's home.
> ->HS

That's what I am doing for every kernel I compile, for every one of my
machines.

~/kernelconfigs/[hostname]/[kernelversion]/.config

I don't own that many machines though...
Makes it easy to downgrade kernels if I want to, keeping them doesn't hurt
much. Even if it might be nonsense to keep them all, it's good to have them
sometimes, especially on machines where keeping a whole kernel directory
would be wasting too much space.

- - Burkhard

- --

Public key available here:

key FP 0A65 5E83 F44F 47A5 3DFC 19C5 7779 E411 FD82 303B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/1456d3nkEf2CMDsRAowcAJ404AUYw02PhFmAQLiZOAMlH4QWVQCePyZx
kPgdjfkV6/rgtAJuvhtA/RQ=
=cZyu
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Monique Y. Herman]

On Wed, 10 Dec 2003 at 19:35 GMT, H. S. penned:
> Monique Y. Herman wrote:
> 
>> 
>> dselect #get latest kernel src package cd
>> /usr/src/kernel-source- make mrproper #clean any leftover
>> compile stuff
> 
> I tried this a few days ago, but I hadn't read the makefile to know
> what mrproper was doing and I lost my old config file which I had
> renamed, IIRC, as .config_OLD or .config_org   :(
> 
> So now if I use mrproper, I *always* save my .config to some other
> directory, in my case in a tmp in a user's home.
> 
> ->HS
> 

Btw, I just discovered that lilo bug #222098 appears to still be live in
1:22.5.8-6.  It prevents me from running lilo successfully.  So caveat
emptor and all that ...

Now I just have to remember how to install an old version of a package
... any hints?

-- 
monique


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[H. S.]

Monique Y. Herman wrote:

dselect #get latest kernel src package
cd /usr/src/kernel-source-
make mrproper #clean any leftover compile stuff
I tried this a few days ago, but I hadn't read the makefile to know what 
mrproper was doing and I lost my old config file which I had renamed, 
IIRC, as .config_OLD or .config_org   :(

So now if I use mrproper, I *always* save my .config to some other 
directory, in my case in a tmp in a user's home.

->HS



--
(Remove all underscores from my email address to get the correct one. 
Apologies for the inconvenience, but this is to reduce spam.)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Monique Y. Herman]

On Wed, 10 Dec 2003 at 16:02 GMT, John Foster penned:
> Joseph Jones wrote:
> 
>> I can compile a kernel into a .deb package as described in the
>> newbiedoc, but I need to compile a kernel with drivers for my
>> laptop's NIC so I can make a rescue disc to do a network install
>> from. Could anyone advise me as to how I do this, if possible in
>> relation to the instructions in the newbiedoc?
>>
>> Thanks :)
>>
>> Joe
>>
>>
> ___ Download a
> kernel tarball from http:// www.kernel.org  & open it into a directory
> on the compiling system /usr/src/linux ; make sure you have the
> correct modutils installed for the kernel version being compiled.Read
> and follow exactly the instructions contained in the tarball for
> compiling the kernel. Depending on your hardware requirement, this may
> be easy or not:-)
> 
> John Foster
> 

You can compile debian's kernel without turning it into a .deb.

This is what I do (because it's what I've always done and I'm too lazy
to change).  Note: it does *not* use initrd!

dselect #get latest kernel src package
cd /usr/src/kernel-source-
make mrproper #clean any leftover compile stuff
make xconfig
make dep
make bzImage
make modules
make install #puts System.map, vmlinuz, config in /boot; moves last
 #version to blah.old
make modules_install
vi lilo.conf
lilo
reboot

-- 
monique


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[John Foster]

Joseph Jones wrote:

I can compile a kernel into a .deb package as described in the 
newbiedoc, but I need to compile a kernel with drivers for my laptop's 
NIC so I can make a rescue disc to do a network install from. Could 
anyone advise me as to how I do this, if possible in relation to the 
instructions in the newbiedoc?

Thanks :)

Joe


___
Download a kernel tarball from http:// www.kernel.org  & open it into a 
directory on the compiling system /usr/src/linux ; make sure you have 
the correct modutils installed for the kernel version being 
compiled.Read and follow exactly the instructions contained in the 
tarball for compiling the kernel. Depending on your hardware 
requirement, this may be easy or not:-)

John Foster



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel without making a .deb package.

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Dec 09, 2003 at 11:00:16PM +, Joseph Jones wrote:
> I can compile a kernel into a .deb package as described in the 
> newbiedoc, but I need to compile a kernel with drivers for my laptop's 
> NIC so I can make a rescue disc to do a network install from. Could 
> anyone advise me as to how I do this, if possible in relation to the 
> instructions in the newbiedoc?

http://ursine.ca/doc/HOWTO/en-html/Kernel-HOWTO/index.html

You will also find this and much more documentation in
/usr/share/doc/HOWTO if you have linux-doc-html installed.  Or you can
bookmark http://ursine.ca/doc/HOWTO/en-html/HOWTO-INDEX/howtos.html
for the HOWTO index.

- -- 
 .''`. Paul Johnson <[EMAIL PROTECTED]>
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/1o6wUzgNqloQMwcRArjvAJ0YGz2v79NKi/RFSlJ5MBoaX1Z6kQCdHl96
vwrt2qfsniDjSNzVgu1M6CQ=
=VZv/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a kernel without making a .deb package.

[Joseph Jones]

I can compile a kernel into a .deb package as described in the 
newbiedoc, but I need to compile a kernel with drivers for my laptop's 
NIC so I can make a rescue disc to do a network install from. Could 
anyone advise me as to how I do this, if possible in relation to the 
instructions in the newbiedoc?

Thanks :)

Joe

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel won't boot (was Re: compiling a kernel)

[ronin2]

On Thu, 3 Apr 2003 23:25:04 -0800 (PST)
Joris Huizer <[EMAIL PROTECTED]> wrote:

> I think I might need to set  " Advanced partition
> selection " on and select some
> partition types there - but I'm not at all sure (I'm
> just curious why it's off)

You don't need any "Advanced partition" types enabled. I dual-boot several
Linux machines with several versions of Windows, and I don't enable any of
those.

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel won't boot (was Re: compiling a kernel)

[Joris Huizer]

Hello,

Thanks for your reply, Elizabeth !

I checked - but the Second extended fs support was
allready on.
I attached the current filesystem supports.

I think I might need to set  " Advanced partition
selection " on and select some
partition types there - but I'm not at all sure (I'm
just curious why it's off)

If I do enable it, I see there is an option enabled:
  PC BIOS (MSDOS partition tables) support 
with the help:
--
 CONFIG_MSDOS_PARTITION:  
  
 Say Y here if you would like to use hard disks under
Linux which
 were partitioned on an x86 PC (not necessarily by
DOS).
--

I don't just try as I have allready some broken
kernels now (I tried some things without succes before
asking here)

If this is indeed the correct difference, or when you
know something else which is incorrect now, please
send a reply !

Thanks for any help,


Joris

--- Elizabeth Barham <[EMAIL PROTECTED]> wrote:
> Joris writes:
> 
> > In case you allready received this question (or
> even answered ??) I
> > apologise, but I have seen no reactions, or my own
> question, so I
> > guess something has gone wrong
> > 
> > The thing is, I can't figure out what's option I
> should choose which
> > is currently off. As I thought I might have
> changed a lot at the
> > same time, I started again on the original config
> and compiled the
> > kernel.  Unfortunately, I have the same problem
> again:
> 
> Probably ext2 file system support. 
> 
> make menuconfig
> 
>  File systems --->
>  <*> Second extended fs support 
> 
> Elizabeth

__
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

filesystems.tgz
Description: filesystems.tgz

Re: kernel won't boot (was Re: compiling a kernel)

[Elizabeth Barham]

Joris writes:

> In case you allready received this question (or even answered ??) I
> apologise, but I have seen no reactions, or my own question, so I
> guess something has gone wrong
> 
> The thing is, I can't figure out what's option I should choose which
> is currently off. As I thought I might have changed a lot at the
> same time, I started again on the original config and compiled the
> kernel.  Unfortunately, I have the same problem again:

Probably ext2 file system support. 

make menuconfig

 File systems --->
 <*> Second extended fs support 

Elizabeth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kernel won't boot (was Re: compiling a kernel)

[Joris Huizer]

Hello everybody,

In case you allready received this question (or even
answered ??) I apologise, but I have seen no
reactions, or my own question, so I guess something
has gone wrong

The thing is, I can't figure out what's option I
should choose which is currently off. As I thought I
might have changed a lot at the same time, I started
again on the original config and compiled the kernel.
Unfortunately, I have the same problem again:

The files are like this. On
 file /boot/*  
I got

/boot/vmlinuz-2.2.20:Linux kernel
x86 boot executable RO-rootFS, Normal VGA
/boot/vmlinuz-2.4.18.02042003:   Linux kernel
x86 boot executable RO-rootFS, root_dev=0x341, Normal
VGA
/boot/vmlinuz-2.4.18.02042003c:  Linux kernel
x86 boot executable RO-rootFS, root_dev=0x341, Normal
VGA

Note that the original 2.2.20 doesn't have the
root_dev=0x341 (which is the number which is mentioned
in the error)

Can anybody help ?

Thanks for any help,

Joris

--- [EMAIL PROTECTED] wrote:
> On Wed, 2 Apr 2003 12:53:43 -0800 (PST)
> Joris Huizer <[EMAIL PROTECTED]> wrote:
> 
> > request_module[block_major-3]: Root fs not mounted
> > UFS Cannot open root device "341" or 03:41
> > Please append a correct "root" boot option
> > kernel panic: UFS: Unable to mount root fs on
> 03.41
> 
> It looks like you didn't include support for your
> root filesystem in
> your new kernel.
> 
> If you do "make menuconfig" and look under
> filesystems, I'll bet you
> find your root filesystem type has "M" next to it,
> instead of "*".
> 
> Kevin
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[ronin2]

On Wed, 2 Apr 2003 12:53:43 -0800 (PST)
Joris Huizer <[EMAIL PROTECTED]> wrote:

> request_module[block_major-3]: Root fs not mounted
> UFS Cannot open root device "341" or 03:41
> Please append a correct "root" boot option
> kernel panic: UFS: Unable to mount root fs on 03.41

It looks like you didn't include support for your root filesystem in
your new kernel.

If you do "make menuconfig" and look under filesystems, I'll bet you
find your root filesystem type has "M" next to it, instead of "*".

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[Joris Huizer]

Thanks everybody for the suggestions on a succesfull
kernel compilation

I now compiled it but it won't boot. 
I get this error stuff - and I don't know what it
means :
--

request_module[block_major-3]: Root fs not mounted
UFS Cannot open root device "341" or 03:41
Please append a correct "root" boot option
kernel panic: UFS: Unable to mount root fs on 03.41

--

There may be typo's - the output was not put in
/var/log/kern.log and the first letter fell off the
screen.


Can anybody tell me what this is - and, more important
- how to fix it ?

Thanks very much !

Joris

__
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[Ruediger Arp]

Am Wed, 02 Apr 2003 10:10:08 +0200 schrieb Joris Huizer:

> Hello everybody,
> 
> As I want scsi emulation, and I'm missing the sr_mod module, I think
> I'll have to compile a new kernel.
> 
> What do I need to do for this, exactly? I'll have to get the source,
> ofcourse, but next to that ?

http://www.debian.org/doc/FAQ/ch-kernel.en.html#s-customkernel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[ronin2]

On Tue, 1 Apr 2003 23:35:10 -0800 (PST)
Joris Huizer <[EMAIL PROTECTED]> wrote:

> Hello everybody,
> 
> As I want scsi emulation, and I'm missing the sr_mod
> module, I think I'll have to compile a new kernel.
> 
> What do I need to do for this, exactly? I'll have to
> get the source, ofcourse, but next to that ?

Go here to find out how to compile your kernel The Debian Way:

http://newbiedoc.sourceforge.net/system/kernel-pkg.html

Read through it carefully, then start again at the top and do what it
says. :)

Would you prefer a 2.2.20 kernel, or would you like to upgrade to 2.4.x?

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[ajlewis2]

In linux.debian.user, you wrote:
> Hello everybody,
> 
> As I want scsi emulation, and I'm missing the sr_mod
> module, I think I'll have to compile a new kernel.
> 
> What do I need to do for this, exactly? I'll have to
> get the source, ofcourse, but next to that ?
> 
> I know allready before the compiling many hardware
> issues are going to asked. 
> 
> I tried compiling the kernel once before, but I gave
> up then as I had the feeling I new much too little to
> answer everything correctly
> 
> As I don't know that much on the hardware details, how
> can I get a more or less complete list of hardware
> features ?
> 
> For example, I do know 'uname -a' will get me some
> info on the debian kernel version (currently that's
> 2.2.20)
> 
> Could you please tell me some more commands like this
> one which will give more info about other issues, like
> mouse, keyboard, etc - the more the better I imagine,
> as the prog will ask loads of things
> 
> Thanks for any help,
> 
> Joris Huizer

I get the source and then use the README that is contained in it.  It has
excellent instructions.  Tips: Configure.help in the Documentation directory
answers lots of questions about what various things are for.  Be sure to
look in /boot for the config file for the current kernel.  If you put that
in your /usr/src/linux directory with the name '.config', you will have the
things you already have.  If you don't do that, you will have to carefully
make sure that you select all that you need.  Little things like PPP are not
default. Copy the config file *after* 'make mrproper' Be sure you always
keep a copy of your current config file for the next time you do this
procedure.  An accidental wipe out of it when you run 'make mrproper' is a
real pain.

Anita



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel

[sean finney]

hey joris,

here's the first three steps i recommend:

# apt-get install kernel-source-2.4.20
# apt-get install kernel-package
$ cd /usr/share/doc/kernel-package

(if you're running woody, you want kernel-source-2.4.18 i believe)

debian really treats you well with kernel-compiling utilities and
documentation.  search back in this mailing list for make-kpkg, there've
been several howto's (and good kernel newbie doc links) posted...


good luck
sean

On Tue, Apr 01, 2003 at 11:35:10PM -0800, Joris Huizer wrote:
> Hello everybody,
> 
> As I want scsi emulation, and I'm missing the sr_mod
> module, I think I'll have to compile a new kernel.
> 
> What do I need to do for this, exactly? I'll have to
> get the source, ofcourse, but next to that ?
> 
> I know allready before the compiling many hardware
> issues are going to asked. 
> 
> I tried compiling the kernel once before, but I gave
> up then as I had the feeling I new much too little to
> answer everything correctly
> 
> As I don't know that much on the hardware details, how
> can I get a more or less complete list of hardware
> features ?
> 
> For example, I do know 'uname -a' will get me some
> info on the debian kernel version (currently that's
> 2.2.20)
> 
> Could you please tell me some more commands like this
> one which will give more info about other issues, like
> mouse, keyboard, etc - the more the better I imagine,
> as the prog will ask loads of things
> 
> Thanks for any help,
> 
> Joris Huizer
> 
> __
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> http://tax.yahoo.com
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


pgp0.pgp
Description: PGP signature

compiling a kernel

[Joris Huizer]

Hello everybody,

As I want scsi emulation, and I'm missing the sr_mod
module, I think I'll have to compile a new kernel.

What do I need to do for this, exactly? I'll have to
get the source, ofcourse, but next to that ?

I know allready before the compiling many hardware
issues are going to asked. 

I tried compiling the kernel once before, but I gave
up then as I had the feeling I new much too little to
answer everything correctly

As I don't know that much on the hardware details, how
can I get a more or less complete list of hardware
features ?

For example, I do know 'uname -a' will get me some
info on the debian kernel version (currently that's
2.2.20)

Could you please tell me some more commands like this
one which will give more info about other issues, like
mouse, keyboard, etc - the more the better I imagine,
as the prog will ask loads of things

Thanks for any help,

Joris Huizer

__
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Andrew Hurt]

On 12/23/02 19:46, Nathan E Norman wrote:


'man mount' tells you what the options _are_ ... finding out what the
options _do_ is a bit more work :)  I haven't actually found a great
reference for ext3 yet.


Thank you.

So, 'data=ordered' (default) means that the data is written to the file system 
before the (meta)data is written to the journal.

And 'data=journal' means that the data is written to the journal before it is 
written to the file system.

. . . and the journal is kind of a marker-database (the 'meta' part of the 
data) that keeps track of the whats and the wheres of the actual data.

I guess I'd better be exploring this further ;-)
--
andrew


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Vincent Lefevre]

On Mon, Dec 23, 2002 at 18:46:07 -0600, Nathan E Norman wrote:
> On Mon, Dec 23, 2002 at 07:28:21PM -0500, Andrew Hurt wrote:
[data=journal, etc]
> > Where might I find more info on the types/benefits of these options?
> 
> 'man mount' tells you what the options _are_ ... finding out what the
> options _do_ is a bit more work :)  I haven't actually found a great
> reference for ext3 yet.

And what are the benefits?

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Mon, Dec 23, 2002 at 07:28:21PM -0500, Andrew Hurt wrote:
> On 12/23/02 18:57, Nathan E Norman wrote:
> >On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote:
> >
> >>How do I tell what type of mode I currently have
> >
> >Look in your fstab (or vgrep the output of 'mount') and look at the
> >options in parens after the "type ext3" bit: if you don't see
> >"data=journal" (or some other "data=" option) then you are running the
> >default which is "data=ordered", which means you are in the clear.
> >
> >[example snipped]
> >
> >HTH,
> 
> Yes; I have (rw) for all.
> 
> Where might I find more info on the types/benefits of these options?

'man mount' tells you what the options _are_ ... finding out what the
options _do_ is a bit more work :)  I haven't actually found a great
reference for ext3 yet.

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  I retract that silly statement.  Somebody slap me.
  -- Roy Smith


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Andrew Hurt]

On 12/23/02 18:57, Nathan E Norman wrote:

On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote:


How do I tell what type of mode I currently have


Look in your fstab (or vgrep the output of 'mount') and look at the
options in parens after the "type ext3" bit: if you don't see
"data=journal" (or some other "data=" option) then you are running the
default which is "data=ordered", which means you are in the clear.

[example snipped]

HTH,


Yes; I have (rw) for all.

Where might I find more info on the types/benefits of these options?
--
andrew


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote:
> On 12/21/02 20:52, Craig Dickson wrote:
> >Frank Copeland wrote:
> >
> >>AIUI, the problem with ext3 filesystems applies only if they are in
> >>journal mode, which isn't the default. I've also seen suggestions that
> >>the bug exists in several versions of the 2.4.x kernels prior to
> >>2.4.20.
> >
> >You mean "data journaling" mode -- ext3 is always journaling, so your
> >statement as written makes no sense, though what you meant to say is
> >correct. The default "ordered" mode is not affected by the bug in
> >2.4.20.
> 
> Just a small aside, guys:
> 
> How do I tell what type of mode I currently have (I'm with ext3, and still 
> using kernel-2.4.19).

Look in your fstab (or vgrep the output of 'mount') and look at the
options in parens after the "type ext3" bit: if you don't see
"data=journal" (or some other "data=" option) then you are running the
default which is "data=ordered", which means you are in the clear.

For example:

  nnorman@aglarond:~ $ mount
  /dev/sda1 on / type ext3 (rw,errors=remount-ro)
  proc on /proc type proc (rw)
  /dev/sda2 on /usr type ext3 (rw,data=journal)
  /dev/sda4 on /var type ext3 (rw,data=journal)
  /dev/sda5 on /tmp type ext3 (rw)
  /dev/sda6 on /var/tmp type ext3 (rw)
  /dev/sda7 on /home type ext3 (rw)

HTH,

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  If you don't know what your program is supposed to do, you'd
  better not start writing it.
  -- Edsger Dijkstra


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Andrew Hurt]

On 12/21/02 20:52, Craig Dickson wrote:

Frank Copeland wrote:


AIUI, the problem with ext3 filesystems applies only if they are in
journal mode, which isn't the default. I've also seen suggestions that
the bug exists in several versions of the 2.4.x kernels prior to
2.4.20.


You mean "data journaling" mode -- ext3 is always journaling, so your
statement as written makes no sense, though what you meant to say is
correct. The default "ordered" mode is not affected by the bug in
2.4.20.


Just a small aside, guys:

How do I tell what type of mode I currently have (I'm with ext3, and still 
using kernel-2.4.19).

Thanks!
--
andrew


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Craig Dickson]

Frank Copeland wrote:

> AIUI, the problem with ext3 filesystems applies only if they are in
> journal mode, which isn't the default. I've also seen suggestions that
> the bug exists in several versions of the 2.4.x kernels prior to
> 2.4.20.

You mean "data journaling" mode -- ext3 is always journaling, so your
statement as written makes no sense, though what you meant to say is
correct. The default "ordered" mode is not affected by the bug in
2.4.20.

Craig




msg20446/pgp0.pgp
Description: PGP signature

ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

[Frank Copeland]

On 21 Dec 02 19:15:50 GMT, Nathan E Norman <[EMAIL PROTECTED]> wrote:

> BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems.

AIUI, the problem with ext3 filesystems applies only if they are in
journal mode, which isn't the default. I've also seen suggestions that
the bug exists in several versions of the 2.4.x kernels prior to
2.4.20.

-- 
Frank Copeland
Home Page: http://thingy.apana.org.au/~fjc/> 
Not the Scientology Home Page: http://xenu.apana.org.au/ntshp/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Sat, Dec 21, 2002 at 01:36:53PM -0600, Gerald V. Livingston II wrote:
> Where did you see text regarding 2.4.20 problems with ext3? The box
> has ext2 right now but I was going to convert some time after the
> kernel upgrade.

See Herbert Xu's reply to my earlier post; 2.4.20 only barfs if you
are using "data=journal" on your ext3 filesystems.  Most people
aren't.

Best,

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  You see, the best way to solve a problem is to rigorously define
  it in terms of other people's problems and then run away quickly.
  -- Roland McGrath


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Sun, Dec 22, 2002 at 11:40:27AM +1100, Herbert Xu wrote:
> Nathan E Norman <[EMAIL PROTECTED]> wrote:
> > 
> > BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems.
> > OTOH, 2.4.19 seems to not want to provide DRM support for the Creator.
> 
> 2.4.20 ext3 is OK as long as you don't enable data=journal (the default
> is data=ordered).

Hmm, you're absolutely correct.  Thank you!  I can now rest easier
running 2.4.20 on my workstations.  I'll have to stick with 2.4.19 on
the servers.

Best,

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  No.
  > Should I include quotations after my reply?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Herbert Xu]

Nathan E Norman <[EMAIL PROTECTED]> wrote:
> 
> BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems.
> OTOH, 2.4.19 seems to not want to provide DRM support for the Creator.

2.4.20 ext3 is OK as long as you don't enable data=journal (the default
is data=ordered).
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Gerald V. Livingston II]

Nathan E Norman said:

> On Sat, Dec 21, 2002 at 01:40:51AM -0600, Gerald V. Livingston II
> wrote:
>> Is there any special info on getting a 2.4.20 kernel to compile
>> under
>> woody on a Sun UltraSparc-1 Creator.
>>
>> Yes, the Debian Way (tm) -- or not, I don't care. Right now it fails
>> at the "make dep" stage using either method. First it was some
>> missing
>> header files. Figured out where they were and got that fixed.
>>
>> Then it was "cannot execute cc1 -- no such file". Found it, linked
>> it
>> into /usr/bin. Now it an "invalid option to "cc1":
>>
>> "cc1   --mmedlow  no such option"
>>
>> Cascading errors, yuck.
>
> Did you follow the instructions found at
>
>   http://www.debian.org/ports/sparc/#kernelsun4u
>
> ?
>
> Note that you need to install package 'egcs64'.
>
> You should undo the link you created, and I'm nervous about whatever
> you did regarding "missing header files".  Please post the exact
> commands you issued and the errors you received.
>
> BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems.
> OTOH, 2.4.19 seems to not want to provide DRM support for the Creator.
>
> I'm running 2.4.20 on an Ultra 30 w/Creator 3D, and 2.4.19 on an Ultra
> 60 headless.  Both compiled "the debian way" using source from
> kernel.org.
>

I'm working through the sparc page instructions again right now.
Appears to be a case of too many hands in the pot. The gentleman who
owns the box has been a RH user forever. He was alone with the system
overnight and it appears he was playing with aptitude and trying to
compile the kernel by hand the i386 way.

We had gcc packages from all over the place and links to who knows
what. egcs64 (which I HAD installed) was there, but not really.

I went through and --purge removed every gcc package I could without
removing the whole system. Reinstalled egcs64 then gcc-3* (which
pulled a lot of 2.95 back in). the compile of 2.4.20 is running now
and don't think I even saw any warnings.

Gotta love ssh though. I was getting really tired of running back and
forth between offices trying to fix that box. Now if the happy meal
driver will just hold up for a bit longer.

Where did you see text regarding 2.4.20 problems with ext3? The box
has ext2 right now but I was going to convert some time after the
kernel upgrade.

Thank you,

Gerald

-- 
Gerald
http://www.phorce1.com
http://www.buskatiers.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Sat, Dec 21, 2002 at 12:02:33AM -0800, nate wrote:
> I don't have personal experience with linux on sparc yet, Downloading
> the woody ISOs for it now and plan to install it on my ultra 1 probably
> tomorrow though.

Don't waste time with the ISOs.  Set up a RARP server and TFTP server
on an existing debian box, and do the netboot thing (details at the
debian website).  It's easy, fast, and works great.

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  For myself, I can only say that I am astonished and somewhat terrified at
  the results of this evening's experiments.  Astonished at the wonderful
  power you have developed, and terrified at the thought that so much hideous
  and bad music may be put on record forever.
  -- Sir Arthur Sullivan, message to Edison, 1888


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Nathan E Norman]

On Sat, Dec 21, 2002 at 01:40:51AM -0600, Gerald V. Livingston II wrote:
> Is there any special info on getting a 2.4.20 kernel to compile under
> woody on a Sun UltraSparc-1 Creator.
> 
> Yes, the Debian Way (tm) -- or not, I don't care. Right now it fails
> at the "make dep" stage using either method. First it was some missing
> header files. Figured out where they were and got that fixed.
> 
> Then it was "cannot execute cc1 -- no such file". Found it, linked it
> into /usr/bin. Now it an "invalid option to "cc1":
> 
> "cc1   --mmedlow  no such option"
> 
> Cascading errors, yuck.

Did you follow the instructions found at

  http://www.debian.org/ports/sparc/#kernelsun4u

?

Note that you need to install package 'egcs64'.

You should undo the link you created, and I'm nervous about whatever
you did regarding "missing header files".  Please post the exact
commands you issued and the errors you received.

BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems.
OTOH, 2.4.19 seems to not want to provide DRM support for the Creator.

I'm running 2.4.20 on an Ultra 30 w/Creator 3D, and 2.4.19 on an Ultra
60 headless.  Both compiled "the debian way" using source from
kernel.org.

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  See, if you were allowed to keep the money, you wouldn't create
  jobs with it. You'd throw it in the bushes or something.  But
  the government will spend it, thereby creating jobs.
  -- Dave Barry


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[Gerald V. Livingston II]

nate said:

> Gerald V. Livingston II said:
>> Is there any special info on getting a 2.4.20 kernel to compile
>> under
>> woody on a Sun UltraSparc-1 Creator.
>
>
> I'm not sure how closely you track the kernel but I've read several
> places that the "generic" kernel is rarely the choice for anything
> other then x86. the non x86 stuff is not always in sync, doesn't
> always
> work etc ...that said, where did you get the sources? I would expect
> the source package for whatever kernels debian has to build on the
> sparc. But if your getting a kernel directly from kernel.org it may
> not(without some patches).
>
> I don't have personal experience with linux on sparc yet, Downloading
> the woody ISOs for it now and plan to install it on my ultra 1
> probably
> tomorrow though.
>
> nate
>

I'll have to check to see if there are 2.4.20 source packages for
sparc. I know the kernel-image packages only go up to 2.4.19 so I had
grabbed the kernel source from kernel.org.

Be aware that anything less than 2.4.19 (woody installs 2.4.18) has
some problems with the happy meal ethernet interface. I googled around
and it seems it it a kernel problem that was solved at around
2.4.19.pre4 or so. I saw no reason to install a 2.4.19 kernel when
2.4.20 is out. Besides, I want to build a lean kernel with everything
we don't need stripped out.

Woody seems to have kernel-image up to 2.4.19 but kernel-source only
up to 2.4.18 for sparc. Guess I'll have to look in Sarge for the
kernel-source package.

I'll report progress.

Gerald

-- 
Gerald
http://www.phorce1.com
http://www.buskatiers.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel on an UltraSparc?

[nate]

Gerald V. Livingston II said:
> Is there any special info on getting a 2.4.20 kernel to compile under
> woody on a Sun UltraSparc-1 Creator.


I'm not sure how closely you track the kernel but I've read several
places that the "generic" kernel is rarely the choice for anything
other then x86. the non x86 stuff is not always in sync, doesn't always
work etc ...that said, where did you get the sources? I would expect
the source package for whatever kernels debian has to build on the
sparc. But if your getting a kernel directly from kernel.org it may
not(without some patches).

I don't have personal experience with linux on sparc yet, Downloading
the woody ISOs for it now and plan to install it on my ultra 1 probably
tomorrow though.

nate




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a kernel on an UltraSparc?

[Gerald V. Livingston II]

Is there any special info on getting a 2.4.20 kernel to compile under
woody on a Sun UltraSparc-1 Creator.

Yes, the Debian Way (tm) -- or not, I don't care. Right now it fails
at the "make dep" stage using either method. First it was some missing
header files. Figured out where they were and got that fixed.

Then it was "cannot execute cc1 -- no such file". Found it, linked it
into /usr/bin. Now it an "invalid option to "cc1":

"cc1   --mmedlow  no such option"

Cascading errors, yuck.

Gerald

-- 
Gerald
http://www.phorce1.com
http://www.buskatiers.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel for another machine

[Bob Nielsen]

On Tue, Oct 15, 2002 at 04:07:04PM -0500, Alex Malinovich wrote:
> I've got an Athlon XP 2000 system running as my desktop machine. I've
> also got a PIII 850 laptop and a p133 mail server. While recompiling the
> kernel on the laptop isn't too time consuming it still takes almost
> twice as long as it does on my desktop. And don't even get me started
> about the p133... :)
> 
> Using the Debian Way of rolling a kernel, can I use my desktop to
> compile the kernel for the other machines? Are there any special flags,
> or is there any special optimization that is done at compile time that I
> might lose if I compile on a machine other than the one the kernel is
> going to be run on?
> 
> Eventually, I'd like to do all of my compilation on my desktop, but for
> now I'd be content with just the kernel. Though if anyone has any
> general tips on the subject, they'd be very much appreciated.

I take it you've never compiled a kernel on a 386 (type 'make', come
back the next morning to see if it succeeded)!

Actually, this is (IMHO) one of the biggest pluses for the Debian
method of kernel compilation/packaging.  Compile on the desktop using
make-kpkg and transfer the file over to the other computer(s).  You can
choose 386 and have the kernel not be CPU-dependent but I believe it is
also possible (although I haven't tried it) to compile an optimized
kernel on a machine with a different series of CPU (within the i386
family).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel for another machine

[Jeff]

Alex Malinovich, 2002-Oct-15 16:07 -0500:
> I've got an Athlon XP 2000 system running as my desktop machine. I've
> also got a PIII 850 laptop and a p133 mail server. While recompiling the
> kernel on the laptop isn't too time consuming it still takes almost
> twice as long as it does on my desktop. And don't even get me started
> about the p133... :)
> 
> Using the Debian Way of rolling a kernel, can I use my desktop to
> compile the kernel for the other machines? Are there any special flags,
> or is there any special optimization that is done at compile time that I
> might lose if I compile on a machine other than the one the kernel is
> going to be run on?
> 
> Eventually, I'd like to do all of my compilation on my desktop, but for
> now I'd be content with just the kernel. Though if anyone has any
> general tips on the subject, they'd be very much appreciated.
> 
> -Alex

Actually, using kernel-package makes the kernel image very portable.
I do this exact thing.  I've compiled kernels for friends and emailed
the .deb to them.  There are no flags or anything special you need to
do, besides using the appropriate config options for the machine in
question.  Also, you'll probably want to use a different source tree
for each machine, and use a different name for each kernel-image using
the --revision=customename.1.0 option.

jc

--
Jeff CoppockSystems Engineer
Diggin' Debian  Admin and User


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a kernel for another machine

[Sean 'Shaleh' Perry]

On Tuesday 15 October 2002 14:07, Alex Malinovich wrote:
> I've got an Athlon XP 2000 system running as my desktop machine. I've
> also got a PIII 850 laptop and a p133 mail server. While recompiling the
> kernel on the laptop isn't too time consuming it still takes almost
> twice as long as it does on my desktop. And don't even get me started
> about the p133... :)
>
> Using the Debian Way of rolling a kernel, can I use my desktop to
> compile the kernel for the other machines? Are there any special flags,
> or is there any special optimization that is done at compile time that I
> might lose if I compile on a machine other than the one the kernel is
> going to be run on?
>

make-kpkg was designed to make this possible.

What you need to do is configure the kernel (make xconfig, menuconfig, 
whatever) once for each machine and save the .config file found in the top of 
the kernel source somewhere safe.  Then just cp machine.config 
/usr/src/linux/.config and run make-kpkg.

The kernel compilation follows the options given it and does not look at your 
system.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Compiling a kernel for another machine

[Alex Malinovich]

I've got an Athlon XP 2000 system running as my desktop machine. I've
also got a PIII 850 laptop and a p133 mail server. While recompiling the
kernel on the laptop isn't too time consuming it still takes almost
twice as long as it does on my desktop. And don't even get me started
about the p133... :)

Using the Debian Way of rolling a kernel, can I use my desktop to
compile the kernel for the other machines? Are there any special flags,
or is there any special optimization that is done at compile time that I
might lose if I compile on a machine other than the one the kernel is
going to be run on?

Eventually, I'd like to do all of my compilation on my desktop, but for
now I'd be content with just the kernel. Though if anyone has any
general tips on the subject, they'd be very much appreciated.

-Alex



signature.asc
Description: This is a digitally signed message part

Re: compiling a kernel?

[guennelk]

On Sat, May 04, 2002 at 03:08:13PM +0300, Tuomo Karhu wrote:
> Could you give me main commands and short help/explanation howto compile 
> debian kernel?

I prefere to use make-kpkg the Debian-Kernel-Package-Manager. I think
you have to install the kernel-package. It produces Kernel-.deb
packages and does almost evrything for you:

make (x/menu)config
make-kpkg clean
make-kpkg kernel_image

cu klaus


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel?

[craigw]

On Sat May 04, 2002 at 03:45:42PM -0400, Kapil Khosla wrote:
> 
> If you want it really really short
> apt-cache search kernel-image
> 
> You will get a variety of hits
> Choose 1
> 
> apt-get install kernel-image...
> 
> You dont need anything else, It will modify lilo.conf, etc etc, and you just 
> reboot :)
> 
> If you wanna really compile a kernel, In debian you can use some neat 
> packages but the standard way to do it
> download the source
> make xconfig
> make dep
> make bzImage
> make modules
> make modules_install
> copy bzImage from /usr/src/linux/arch/i386/boot/bzImage /boot/
> edit lilo.conf
> run lilo

what is the deal with /boot/map or /boot/System.map, etc?

and what do the error messages mean when they tell me that it is not
parsable as a system map?
-- 
-CraigW



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel?

[Nick Guerrera]

On Sat, 2002-05-04 at 08:08, Tuomo Karhu wrote:
> Could you give me main commands and short help/explanation howto compile 
> debian kernel?
> 
> Thanks.
> 
> Tuomo Karhu

Check out chapter 9 of the Debian FAQ:

http://www.debian.org/doc/FAQ/ch-kernel.html


Nick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling a kernel?

[Kapil Khosla]

If you want it really really short
apt-cache search kernel-image

You will get a variety of hits
Choose 1

apt-get install kernel-image...

You dont need anything else, It will modify lilo.conf, etc etc, and you just 
reboot :)

If you wanna really compile a kernel, In debian you can use some neat packages 
but the standard way to do it
download the source
make xconfig
make dep
make bzImage
make modules
make modules_install
copy bzImage from /usr/src/linux/arch/i386/boot/bzImage /boot/
edit lilo.conf
run lilo
Just reboot,
Kapil


Kapil

On Sat, 4 May 2002 15:08:13 +0300
"Tuomo Karhu" <[EMAIL PROTECTED]> wrote:

> Could you give me main commands and short help/explanation howto compile 
> debian kernel?
> 
> Thanks.
> 
> Tuomo Karhu
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RE: compiling a kernel?

[Jonas Björck]

Use the guide on this site http://newbiedoc.sourceforge.net/tutorials/kernel-pkg.en/intro-kernel-pkg.html


 

Cheers.

 

Jonas

 

-Original Message-
From: Tuomo Karhu
[mailto:[EMAIL PROTECTED] 
Sent: den 4 maj 2002 14:08
To: debian-user@lists.debian.org
Subject: compiling a kernel?

 



Could you give me main commands and
short help/explanation howto compile debian kernel?





 





Thanks.





 





Tuomo Karhu

compiling a kernel?

[Tuomo Karhu]

Could you give me main commands and short 
help/explanation howto compile debian kernel?
 
Thanks.
 
Tuomo Karhu

Re: compiling a kernel?

[Hans Steinraht]

I did it!!!

As root I checked disk space, and did: make-kpkg --revision=3:custom.1.0 
kernel_image (with an underscore).
And it works, I get the image.deb and after dpkg -i it is installed.

After rebooting it's a bit dissapointing that my new kernel will not work, but 
I'm going to start to find out why that is.
When somebody allready have an idea about this error:
 kmod: failed to exec /sbin/modprobe -s -k binfmt -464c, errno=8

Ok, I start reading about this.
Hans



On Sat, Oct 06, 2001 at 12:30:33AM +, Hans Steinraht wrote:
> 
> -- 
> Hi,
> 
> I just started with Debian, installed the compact unstable version and came 
> to the conclusion that I had to compile a new kernel to let Debian do the 
> things I want.
> 
> This is the firsttime I'm doing this, so I followed the steps described in 
> the Debian GNU/Linux FAQ, and in the README file that came with the 
> 2.2.19-kernel.
> 
> - make-kpkg clean
> - make menuconfig
> - make-kpkg --revision Custum.1 kernel-image
> 
> All looks to go well, the kernel and modules are build (vmlinuz appears in 
> /usr/src/linux and in modules I see the modules that I choose).
> 
> Then the process stops.
> This is the last text that I see on my screen:
> 
>  make INSTALL_MOD_PATH=/usr/src/linux/debian/tmp-image
>   modules-install
>  make[2]: Entering directory '/usr/src/kernel-source-2.2.19'
> 
> Is there someone who can tell me what the reason is for this?
> 
> Thanks,
> Hans
>  
> 
> 
> 
>-- 
>
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 

-- 



   -- 
-<->-<->-<->-<   >-<->-<->-<->-
-  [EMAIL PROTECTED]  -
 -  [EMAIL PROTECTED]  
  -<->-<->- -<->-<->-
 <   > 
  

Re: compiling a kernel?

[John]

On Sat, Oct 06, 2001 at 12:30:33AM +, Hans Steinraht wrote:
> 
> - make-kpkg --revision Custum.1 kernel-image
> 
This has never failed me:

make-kpkg --revision=3:custom.1.0 kernel_image

John
-- 
-_-_-_-_-_-_-_-_-_-_-
 Using [Debian] Linux
_-_-_-_-_-_-_-_-_-_-_





pgpjm8INeNUQs.pgp
Description: PGP signature

Re: compiling a kernel?

[Osamu Aoki]

On Sat, Oct 06, 2001 at 12:30:49AM +0200, Eduard Bloch wrote:
> > - make-kpkg clean
> > - make menuconfig
> > - make-kpkg --revision Custum.1 kernel-image
> 
> It is called kernel_image, an underscore, not -.

Yes but reading make-kpkg perl script, it seems to accept both as same
target as undocumented feature.

Question is,
1.  Are you root? (May not be critical)
2.  Do you have disk space needed for all the work? "du" "df"

Cheers :-)

-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ 
+  Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D  +
+  My debian quick-reference, http://www.aokiconsulting.com/quick/+

Re: compiling a kernel?

[Eduard Bloch]

#include 
Hans Steinraht wrote on Sat Oct 06, 2001 um 12:30:33AM:
> 
> -- 

Hehe, never put -- at the beginning, it is a sign for beginning a
signature and some software cuts everything below.

> - make-kpkg clean
> - make menuconfig
> - make-kpkg --revision Custum.1 kernel-image

It is called kernel_image, an underscore, not -.

Gruss/Regards,
Eduard.
-- 
> Zum Unlesbarmachen kann man auch cdrecord blank=full auf eine CD-R
> anwenden ;-)
aber doch wohl nur in /dev/mikrowelle oder? :-)
  Andreas 'Knv' Kanev in de.comp.hardware.cd-brenner

compiling a kernel?

[Hans Steinraht]

-- 
Hi,

I just started with Debian, installed the compact unstable version and came to 
the conclusion that I had to compile a new kernel to let Debian do the things I 
want.

This is the firsttime I'm doing this, so I followed the steps described in the 
Debian GNU/Linux FAQ, and in the README file that came with the 2.2.19-kernel.

- make-kpkg clean
- make menuconfig
- make-kpkg --revision Custum.1 kernel-image

All looks to go well, the kernel and modules are build (vmlinuz appears in 
/usr/src/linux and in modules I see the modules that I choose).

Then the process stops.
This is the last text that I see on my screen:

 make INSTALL_MOD_PATH=/usr/src/linux/debian/tmp-image
  modules-install
 make[2]: Entering directory '/usr/src/kernel-source-2.2.19'

Is there someone who can tell me what the reason is for this?

Thanks,
Hans
 



   -- 
   

Re: Compiling a kernel on another processor

[Harry Henry Gebel]

On Mon, Sep 17, 2001 at 12:52:20AM +, Rajesh Fowkar wrote:
> This is at one of my clients place. He has got an athlon machine. Are there
> any issues in compiling the kernel on a different machine with a different
> processor ? Now I am thinking of compiling the kernel for this Celerone
> machine on the Athlon machine. I will set the parameters for kernel as per
> the celerone machine. Will this create any problems ?
> 
> What is the best way to compile kernel like this ?
> 
> After compiling the kernel on Athlon I am planning to copy this kernel to
> the celerone machine along with the modules /lib/modules/2.4.9 !!!
> Is this OK ?

This shouldn't be a problem as long as you choose the correct processor
when you run 'make config'.

-- 
Harry Henry Gebel
West Dover Hundred, Delaware
GPG encrypted email gladly accepted. Key ID: B853FFFE
Fingerprint: 15A6 F58D AEED 5680 B41A  61FE 5A5F BB51 B853 FFFE


pgpLWeh1HZbsG.pgp
Description: PGP signature

first shot at compiling a kernel

[Keith & Cecile Schooley]

I tried compiling a kernel (2.2.17) for the first time.  It compiled,
rebooted, and generally worked okay, but there were a few problems

1)  I received a startup message indicating that I was using kerneld and
almost certainly didn't want to.  I don't know how I turned it on, so I
don't know how to turn it off.

2)  It initialized Soundblaster at io 220 and 330, irq 1 and 5 (which is
what it runs at under Windows), but then said "AWE 32 not recognized."  I
still don't have sound.  (Compiled SB and PNP into the kernel.)

3)  I received a string of error messages on module autodetect (need to
rerun startup sequence to get the exact message).  I don't have any modules
compiled into the kernel (although I do have the possibility of module
dependency enabled).  Do I have to compile modules anyway, even though I'm
not using any?  Or are the old modules from the generic kernel causing the
problem?

Any suggestions?  Thanks in advance.

Grace and peace,

Keith

Re: Compiling a kernel for another machine

[A+B Frank]

Sebastiaan wrote:
> 
> Hi,
> 
> has anyone an idea how to cross compile a kernel, so to compile a kernel
> for a ppc on an i386?
> 
> Just curius.
> 
> Greetz,
> Sebastiaan

Hi,
you'll have to set up gcc as a cross compiler and look at the patches
in the kernel sources for ppc.

regards 
Albrecht

RE: Compiling a kernel for another machine

[Sebastiaan]

Hi,

has anyone an idea how to cross compile a kernel, so to compile a kernel
for a ppc on an i386? 

Just curius.

Greetz,
Sebastiaan


On Tue, 30 Jan 2001, Sean 'Shaleh' Perry wrote:

> 
> On 30-Jan-2001 [EMAIL PROTECTED] wrote:
> > I know this is possible (I even vaguely remember seeing it mentioned 
> > somewhere). 
> > 
> > What I want to do is compile a kernel on my desktop PC for my laptop. 
> > Just build it, copy the new kernel image across the network, rejig 
> > the laptop's lilo, reboot it, and Roberta's your crossdressing Aunt.
> > 
> > I have this worry about all those bits I marked as Modules, though. I 
> > guess I have to copy those too, hmm? From where to where? Is there 
> > anything else I should worry about?
> > 
> 
> apt-get install kernel-package
> cd /usr/share/doc/kernel-package
> 
> do the right thing(tm)
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 

Re: Compiling a kernel for another machine

[Gary Jones]

On 30 Jan 2001, "Hall Stevenson" <[EMAIL PROTECTED]> wrote:

> > I have this worry about all those bits I marked as Modules,
> > though. I guess I have to copy those too, hmm? From where
> > to where? Is there anything else I should worry about?
> 
> I think most people will suggest you use the "make-kpkg" utility. It
> will create a "*.deb" file which you can copy to the laptop.

Ahh! I never even thought of that! Its obvious though - what I'm 
doing is dsitributing (even if it is only about 3' away) a kernel, so 
I need to package it. Cool.

> Then just
> "dpkg --install kernel-package-custom.deb" and it will install things
> where they need to go.

Thanks, both to you, and the others who suggested the same (sort of) 
thing :-)

So I've been there, done that, installed the package. Great. Now it 
says it can't find the serial module. Serial module? I don't remember 
even seeing an option for that. It seems kerneld is looking in 
/etc/modules for the list of modules to load at startup, where, sure 
enough, it lists serial as one which it should load, and no it isn't 
in /lib/modules//. This is the 
first time I've had a play with kerneld, and it seems to have gone 
wrong :-( Does anyone have any clues as to what I've missed?

-- 
Gary
Debian 2.1r4 (kernel v2.0.39); XFree86 3.3.6
If you don't know where you are going, any road will take you there.
(Lewis Carroll, 'Alice in Wonderland')

Re: Compiling a kernel for another machine

[Hall Stevenson]

> I know this is possible (I even vaguely remember seeing
> it mentioned somewhere).
>
> What I want to do is compile a kernel on my desktop
> PC for my laptop. Just build it, copy the new kernel image
> across the network, rejig the laptop's lilo, reboot it, and
> Roberta's your crossdressing Aunt.
>
> I have this worry about all those bits I marked as Modules,
> though. I guess I have to copy those too, hmm? From where
> to where? Is there anything else I should worry about?

I think most people will suggest you use the "make-kpkg" utility. It
will create a "*.deb" file which you can copy to the laptop. Then just
"dpkg --install kernel-package-custom.deb" and it will install things
where they need to go.

You could do what you want by hand, but the above is likely the easiest
way.

Hall