Re: kernel compile error in wheezy [solved!]

[Stephen Powell]

On Tue, 19 Jul 2011 00:29:49 -0400 (EDT), Frank Miles wrote:
> 
> Thanks to everyone who helped - yes, it was indeed something about
> my environment.  In /etc/profile, I've long exported an environment
> variable of the form:
> 
>   export LIBRARY_PATH="/home/myname/devel/lib:."
> 
> I have a dim memory that when compiling cross-compilers that the
> '.' directory is a problem.  Commenting this out allows the kernel
> compile to proceed.  What's strange is that I've had this for many
> years without any kernel-compile problem.  No longer!
> 
> There may be some gcc docs that warn of this, not sure exactly where,
> but it might shed more light on this situation.
> 
> Thanks again, everyone-

Glad you got it working.  Thanks for the follow-up.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1196455862.778722.137811653.javamail.r...@md01.wow.synacor.com

Re: kernel compile error in wheezy [solved!]

[Frank Miles]

Thanks to everyone who helped - yes, it was indeed something about
my environment.  In /etc/profile, I've long exported an environment
variable of the form:

export LIBRARY_PATH="/home/myname/devel/lib:."

I have a dim memory that when compiling cross-compilers that the
'.' directory is a problem.  Commenting this out allows the kernel
compile to proceed.  What's strange is that I've had this for many
years without any kernel-compile problem.  No longer!

There may be some gcc docs that warn of this, not sure exactly where,
but it might shed more light on this situation.

Thanks again, everyone-

Frank


--
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/alpine.lrh.2.01.1107182120300.6...@homer01.u.washington.edu

Re: kernel compile error in wheezy

[Stephen Powell]

On Sun, 17 Jul 2011 13:35:00 -0400 (EDT), Frank Miles wrote:
> Stephen wrote:
>> ...
>> I'm guessing that elks-libc is what is needed.  Is that package installed
>> on your system?
>> ...
> 
> No, it's not installed.  Sure seems strange, requiring a 16-bit library
> for the build of a 64-bit system.  I have stdarg.h from gcc versions 4.3,
> 4.4, and 4.6, and libstdc++ of the same versions.  But it would be an
> easy solution, so... (installing,.. retrying...):
>   -> still fails :(

Hmm.  Well, I'm not sure what to suggest.  It's obviously something strange
in your environment, since many others have been able to successfully compile
the kernel.  You might try deleting the kernel source code directory and
unpack the tar file again.  Maybe something got hosed up somehow.  The only
other thing I might suggest is to delete older versions of the C compiler
and libraries until you have only the newest one or until you find an
installed package that requires an older library.  Then try again.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/542932932.734934.1310945631739.javamail.r...@md01.wow.synacor.com

Re: kernel compile error in wheezy

[Frank Miles]

Thanks to Stan, Stephen, and Maderios!

-
Stan wrote:


Do you get the same error using the (new) Debian kernel method?

$ make KDEB_PKGVERSION=custom.1.0 deb-pkg


I'll have to learn more about the new method for the future.
For right now, unfortunately the answer is yes, I get the same error.

-
Stephen wrote:


...
I'm guessing that elks-libc is what is needed.  Is that package installed
on your system?
...


No, it's not installed.  Sure seems strange, requiring a 16-bit library
for the build of a 64-bit system.  I have stdarg.h from gcc versions 4.3,
4.4, and 4.6, and libstdc++ of the same versions.  But it would be an
easy solution, so... (installing,.. retrying...):
-> still fails :(


-
Maderios wrote:

For my part:
make-kpkg kernel_image --initrd
and it works.


Same error - it bombs on compiling arch/x86/kernel/asm-offsets.c, in each
case looking for included file stdarg.h [again, I have at least 6 versions
of this file depending on compiler].

Thanks for trying!  I'm mystified, having compiled many kernels over the
years on a various computers without difficulty.  Is there any way that
I could have mangled the include search path?  I'm using bash as the shell
interpreter, that's still ok isn't it?

-Frank


--
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/alpine.lrh.2.01.1107171013290.13...@homer01.u.washington.edu

Re: kernel compile error in wheezy

[Ralf Mardorf]

$ uname -a
Linux debian 2.6.39.1 #1 SMP PREEMPT Tue Jun 7 01:40:05 CEST 2011 x86_64
GNU/Linux

is a self-build (rt patch emu kernel) with source from kernel.org and at
least 2.6.39-2 from the repositories was ok too, didn't tested the
upgrade to 2.6.39-3 until now, which btw. still is named 2.6.39-2.

I build by running

make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers

of cause I don't add staging (or what ever it is named, that couldn't be
used with real rt-patches) and some other thingies, that are unimportant
for my usage.

Hm, yes, my architecture is amd64.


-- 
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/1310920578.8771.6.camel@debian

Re: kernel compile error in wheezy

[maderios]

On 07/16/2011 08:19 PM, Frank Miles wrote:

I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64].
As I've done many times - using
make-kpkg --revision N kernel_image


Hi
For my part:
make-kpkg kernel_image --initrd
and it works.
greetings
Maderios


--
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/4e22afd4.4010...@gmail.com

Re: kernel compile error in wheezy

[Stan Hoeppner]

On 7/16/2011 1:19 PM, Frank Miles wrote:
> I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64].
> As I've done many times - using
> make-kpkg --revision N kernel_image
> But with the recent linux-source update - shortly after starting I get:

Do you get the same error using the (new) Debian kernel method?

$ make KDEB_PKGVERSION=custom.1.0 deb-pkg

-- 
Stan



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e226a84.50...@hardwarefreak.com

Re: kernel compile error in wheezy

[Stephen Powell]

On Sat, 16 Jul 2011 14:19:17 -0400 (EDT), Frank Miles wrote:
> 
> I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64].
> As I've done many times - using
>   make-kpkg --revision N kernel_image
> But with the recent linux-source update - shortly after starting I get:
> 
> CC  arch/x86/kernel/asm-offsets.s
>   In file included from 
> /usr/src/linux-source-2.6.39/arch/x86/include/asm/percpu.h:44:0,
>   from 
> /usr/src/linux-source-2.6.39/arch/x86/include/asm/current.h:5,
>   from 
> /usr/src/linux-source-2.6.39/arch/x86/include/asm/processor.h:15,
>   from 
> /usr/src/linux-source-2.6.39/arch/x86/include/asm/atomic.h:6,
>   from ./include/linux/crypto.h:20,
>   from arch/x86/kernel/asm-offsets.c:8:
>   ./include/linux/kernel.h:12:20: fatal error: stdarg.h: No such file or 
> directory
>   compilation terminated.
>   make[3]: *** [arch/x86/kernel/asm-offsets.s] Error 1
>   make[2]: *** [prepare0] Error 2
> 
> There don't seem to be any current bugs like this.  A previous 2.6.39
> compiler was uneventful.
> 
> Any ideas would be appreciated!

Using the procedures found at

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

I cannot reproduce your error.  I am using package linux-source-2.6.39,
version 2.6.39-3.  I have tried two machine architectures: s390 and i386,
but not amd64.

On my i386 system, there are four files ending in stdarg.h.
They are as follows:

/usr/lib/bcc/include/stdarg.h
/usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.5/include/stdarg.h
/usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6/include/stdarg.h
/usr/include/c++/4.6/tr1/stdarg.h

These files belong to the elks-libc, gcc-4.5, gcc-4.6,
and libstdc++6-4.6-dev packages, respectively.  Since libstdc++6-4.6-dev
is for c++, and obviously either gcc-4.5 or gcc-4.6, or both, must
be already installed (or you wouldn't be able to compile anything),
I'm guessing that elks-libc is what is needed.  Is that package installed
on your system?  elks-libc is a recommendation (and not a dependency)
of bcc; so you may not have it installed on your system if you are in
the habit of installing only dependencies and skipping recommendations.
But it looks like it may be a requirement for compiling the kernel.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/755477887.725131.1310868477179.javamail.r...@md01.wow.synacor.com

Re: Kernel compile and install does not create initrd

[Manoj Srivastava]

On Sat, Jan 16 2010, Hugo Vanwoerkom wrote:

> Patrick Wiseman wrote:
>> On Sat, Jan 16, 2010 at 2:44 PM, Hugo Vanwoerkom  wrote:
>>> Patrick Wiseman wrote:

>>> If this is the latest version of make-kpkg, did you
>>> 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/
>>> ?
>>
>> Uh, no, I didn't.  I have now.  And dkpg-reconfigure has now created
>> the initrd image, and grub has found it.  Thanks!  (I appreciate the
>> help, but where should I have looked?  My googling did not turn up
>> that solution!  And neither did 'man make-kpkg', although I see now
>> there's some obtuse language in there which is perhaps meant to convey
>> the same information.)
>>
>
> This was dicussed on the list. My reference is:
> http://groups.google.com/group/linux.debian.user/browse_thread/thread/38247e9a7f3561ea/6fe4f2d08bc209a1?hl=ia&q=group:linux.debian.user+insubject:kernel-package#6fe4f2d08bc209a1
> and you're right, that post does not show up by googling initrd or
> kernel. So much for google...

,[  Manual page make-kpkg(1) line 132/382 ]
| --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).   <-*
`

I guess this could be made more, umm, insistent, somehow.

manoj
-- 
There ain't nothin' in this world that's worth being a snot
over. --Larry Wall in <1992aug19.041614.6...@netlabs.com>
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


-- 
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/87635gpunz@anzu.internal.golden-gryphon.com

Re: Kernel compile and install does not create initrd

[Hugo Vanwoerkom]

Patrick Wiseman wrote:

On Sat, Jan 16, 2010 at 2:44 PM, Hugo Vanwoerkom  wrote:

Patrick Wiseman wrote:

I have compiled a custom kernel, using 'make-kpkg clean && make-kpkg
--initrd --revision=sage.1.0 kernel-image', 'sage' being the name of
my machine.  I then installed it, using 'dpkg -i
linux-image-2.6.30_sage.1.0_amd64.deb'.  I had thought that would be
enough to create the initrd necessary to boot, but there is no
initrd-image in /boot corresponding to the kernel, and (of course)
none listed in /boot/grub/menu.lst for this kernel's entry.  So (again
of course) there's a kernel panic when I attempt to boot using this
kernel.  I tried dpkg-reconfigure on the kernel, but no joy.
initramfs and initrd support are enabled in my kernel config.  So can
anyone tell me what I'm doing wrong?  (I'm sure it's obvious, but I'm
not seeing it, and I've read the relevant sections of the Debian Linux
Kernel Handbook.)


If this is the latest version of make-kpkg, did you
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/
?


Uh, no, I didn't.  I have now.  And dkpg-reconfigure has now created
the initrd image, and grub has found it.  Thanks!  (I appreciate the
help, but where should I have looked?  My googling did not turn up
that solution!  And neither did 'man make-kpkg', although I see now
there's some obtuse language in there which is perhaps meant to convey
the same information.)



This was dicussed on the list. My reference is:
http://groups.google.com/group/linux.debian.user/browse_thread/thread/38247e9a7f3561ea/6fe4f2d08bc209a1?hl=ia&q=group:linux.debian.user+insubject:kernel-package#6fe4f2d08bc209a1
and you're right, that post does not show up by googling initrd or 
kernel. So much for google...


Hugo


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

Re: Kernel compile and install does not create initrd

[Patrick Wiseman]

On Sat, Jan 16, 2010 at 2:44 PM, Hugo Vanwoerkom  wrote:
> Patrick Wiseman wrote:
>>
>> I have compiled a custom kernel, using 'make-kpkg clean && make-kpkg
>> --initrd --revision=sage.1.0 kernel-image', 'sage' being the name of
>> my machine.  I then installed it, using 'dpkg -i
>> linux-image-2.6.30_sage.1.0_amd64.deb'.  I had thought that would be
>> enough to create the initrd necessary to boot, but there is no
>> initrd-image in /boot corresponding to the kernel, and (of course)
>> none listed in /boot/grub/menu.lst for this kernel's entry.  So (again
>> of course) there's a kernel panic when I attempt to boot using this
>> kernel.  I tried dpkg-reconfigure on the kernel, but no joy.
>> initramfs and initrd support are enabled in my kernel config.  So can
>> anyone tell me what I'm doing wrong?  (I'm sure it's obvious, but I'm
>> not seeing it, and I've read the relevant sections of the Debian Linux
>> Kernel Handbook.)
>>
>
> If this is the latest version of make-kpkg, did you
> 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/
> ?

Uh, no, I didn't.  I have now.  And dkpg-reconfigure has now created
the initrd image, and grub has found it.  Thanks!  (I appreciate the
help, but where should I have looked?  My googling did not turn up
that solution!  And neither did 'man make-kpkg', although I see now
there's some obtuse language in there which is perhaps meant to convey
the same information.)

Patrick


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

Re: Kernel compile and install does not create initrd

[Hugo Vanwoerkom]

Patrick Wiseman wrote:

I have compiled a custom kernel, using 'make-kpkg clean && make-kpkg
--initrd --revision=sage.1.0 kernel-image', 'sage' being the name of
my machine.  I then installed it, using 'dpkg -i
linux-image-2.6.30_sage.1.0_amd64.deb'.  I had thought that would be
enough to create the initrd necessary to boot, but there is no
initrd-image in /boot corresponding to the kernel, and (of course)
none listed in /boot/grub/menu.lst for this kernel's entry.  So (again
of course) there's a kernel panic when I attempt to boot using this
kernel.  I tried dpkg-reconfigure on the kernel, but no joy.
initramfs and initrd support are enabled in my kernel config.  So can
anyone tell me what I'm doing wrong?  (I'm sure it's obvious, but I'm
not seeing it, and I've read the relevant sections of the Debian Linux
Kernel Handbook.)



If this is the latest version of make-kpkg, did you
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/

?

Hugo


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

Re: kernel compile - Unable to mount root fs

[Amax]

This is a bug in the 2.6.30 source.  The quick work-around for this is:

update-initramfs -c -k "uname"

"uname" being whatever you've named your custom kernel & do it without 
the quotations.

Check to see if there is now an initrd-image file for your kernel in the /
boot directory & if there is do an "update-grub" & you're good to go.

~Amax~

-- 
A person needs only two tools: WD-40 and duct tape. If it doesn't move
and it should, use WD-40. If it moves and shouldn't, use the tape.
 -- Red Green

Registered Linux User No. 306834


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

Re: kernel compile - Unable to mount root fs

[Tzafrir Cohen]

On Sun, Jul 19, 2009 at 01:06:51PM +0200, Siggy Brentrup wrote:
> On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:

> > Remove just the word "single" and you should be good to go.
> > 
> > Don Quixote
> 
> Lucky Don Quixote :), obviously you never have been hitten by fsck not
> being able to cope with a broken FS.  In such a situation the machine
> automagically boots into single user mode.

No. Just append 'init=/bin/bash' (or /bin/sh) at the prompt. Or
'single', if you prefer.

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754 || friend


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

Re: kernel compile - Unable to mount root fs

[pobega]

> On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
>> On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
>> > hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>>
>> On some of your vmlinux lines in your menu.lst you have the word
>> "single".  That boots you into single-user mode, that you exit from by
>> hitting Ctrl-D.
>>
>> Remove just the word "single" and you should be good to go.
>>
>> Don Quixote
>
> Lucky Don Quixote :), obviously you never have been hitten by fsck not
> being able to cope with a broken FS.  In such a situation the machine
> automagically boots into single user mode.
>
> Maybe it should be made clearer that you're at your own risk when
> hitting C-d.  I'd never do that on a production box or when the
> FS contains valuable data.
>
> Siggy

This is OT, but I remember my first day away at school. I bought a new
EeePC months earlier, installed Debian on it, prepared my install for my
CS classes...then when I got to my first class, I booted up only to have a
jfs error. It took me an hour or so to figure out how to fix.



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

Re: kernel compile - Unable to mount root fs

[pobega]

> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>
> http://img149.imageshack.us/img149/5726/screenshotual.png
>

You got that error using make-kpkg, or just as a general kernel error?


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

Re: kernel compile - Unable to mount root fs

[pobega]

> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>
> http://img149.imageshack.us/img149/5726/screenshotual.png
>

You got that error using make-kpkg, or just as a general kernel error?


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

Re: kernel compile - Unable to mount root fs

[Soren Orel]

It only brings up this error message on a VirtualBox machine.. :D
I tried to compile the vanillia kernel on two other machines, and it worked,
booted without error.. :)
The VirtualBox machine was only to try, how it works, thank you!

On Sun, Jul 19, 2009 at 1:06 PM, Siggy Brentrup wrote:

> On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
> > On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
> > > hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
> >
> > On some of your vmlinux lines in your menu.lst you have the word
> > "single".  That boots you into single-user mode, that you exit from by
> > hitting Ctrl-D.
> >
> > Remove just the word "single" and you should be good to go.
> >
> > Don Quixote
>
> Lucky Don Quixote :), obviously you never have been hitten by fsck not
> being able to cope with a broken FS.  In such a situation the machine
> automagically boots into single user mode.
>
> Maybe it should be made clearer that you're at your own risk when
> hitting C-d.  I'd never do that on a production box or when the
> FS contains valuable data.
>
> Siggy
> --
> Please don't cc: me when replying on the list.
>bsb-at-psycho-dot-informationsanarchistik-dot-de
> or:bsb-at-psycho-dot-i21k-dot-de
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkpi/ksACgkQ94B/SGO8KQfxfgCfY+eQXjZOb9cpLslPyUNxzzbJ
> vdQAn1HSWhJ7Rx5jAHlNk2IFXxJVa9Jw
> =Finx
> -END PGP SIGNATURE-
>
>

Re: kernel compile - Unable to mount root fs

[Siggy Brentrup]

On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
> On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
> > hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
> 
> On some of your vmlinux lines in your menu.lst you have the word
> "single".  That boots you into single-user mode, that you exit from by
> hitting Ctrl-D.
> 
> Remove just the word "single" and you should be good to go.
> 
> Don Quixote

Lucky Don Quixote :), obviously you never have been hitten by fsck not
being able to cope with a broken FS.  In such a situation the machine
automagically boots into single user mode.

Maybe it should be made clearer that you're at your own risk when
hitting C-d.  I'd never do that on a production box or when the
FS contains valuable data.

Siggy
-- 
Please don't cc: me when replying on the list.
bsb-at-psycho-dot-informationsanarchistik-dot-de
or:bsb-at-psycho-dot-i21k-dot-de


signature.asc
Description: Digital signature

Re: kernel compile - Unable to mount root fs

[Don Quixote de la Mancha]

On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D

On some of your vmlinux lines in your menu.lst you have the word
"single".  That boots you into single-user mode, that you exit from by
hitting Ctrl-D.

Remove just the word "single" and you should be good to go.

Don Quixote
-- 
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com


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

Re: kernel compile - Unable to mount root fs

[Soren Orel]

hmmm.. it works, but I have to hit Ctrl+D at every boot... :D

http://img149.imageshack.us/img149/5726/screenshotual.png

On Sat, Jul 18, 2009 at 12:00 PM, Siggy Brentrup wrote:

> Sorry that I didn't see this thread earlier.
>
> On Sat, Jul 18, 2009 at 11:17 +0200, Soren Orel wrote:
> > it works!
> >
> > I just forget:
> >
> > cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.30-1
> >
> >
> > and:
> > mkinitramfs -o /boot/initrd.img-2.6.30-1 2.6.30.1
>
> % apt-get install kernel-package
> % man make-kpkg
>
> might have been useful.
>
> IIRC this has been written in order not to forget
> crucial steps after once bitten.
>
> Regs
>  Siggy
> --
> Please don't cc: me when replying on the list.
>bsb-at-psycho-dot-informationsanarchistik-dot-de
> or:bsb-at-psycho-dot-i21k-dot-de
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkphnUoACgkQ94B/SGO8KQe2NQCgw4DTfS2iNHrzkbVjRhZftSOj
> QrYAn13qZ/fsIDhdYJyxWeBPlhz1y8FN
> =ACkV
> -END PGP SIGNATURE-
>
>

Re: kernel compile - Unable to mount root fs

[Siggy Brentrup]

Sorry that I didn't see this thread earlier.

On Sat, Jul 18, 2009 at 11:17 +0200, Soren Orel wrote:
> it works!
> 
> I just forget:
> 
> cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.30-1
> 
> 
> and:
> mkinitramfs -o /boot/initrd.img-2.6.30-1 2.6.30.1

% apt-get install kernel-package
% man make-kpkg

might have been useful.

IIRC this has been written in order not to forget
crucial steps after once bitten.

Regs
  Siggy
-- 
Please don't cc: me when replying on the list.
bsb-at-psycho-dot-informationsanarchistik-dot-de
or:bsb-at-psycho-dot-i21k-dot-de


signature.asc
Description: Digital signature

Re: kernel compile - Unable to mount root fs

[Soren Orel]

it works!

I just forget:

cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.30-1


and:
mkinitramfs -o /boot/initrd.img-2.6.30-1 2.6.30.1


and to edit grub:
title kernel 2.6.30.1-barminev
root (hd0,1)
kernel /vmlinuz-2.6.30-1 root=/dev/hda2 ro
initrd /initrd.img-2.6.30-1

thank you!!! alias köszi! :D

On Sat, Jul 18, 2009 at 10:01 AM, Aioanei Rares
wrote:

> mkinitrd is a standard command on all linux systems, so you can check
> its manual page. Maybe man update-initramfs can help too. Best of
> luck.
>
> On 7/17/09, Don Quixote de la Mancha  wrote:
> > In your Grub menu.lst file, there are some lines that look like this one:
> >
> >   initrd  /initrd.img-2.6.26-2-686
> >
> > You need a line like that just below the item for the kernel you're
> > trying to boot, except that you want the initrd version to match the
> > new kernel version.
> >
> > initrd stands for Initial RAM Disk.  It's a compressed archive that
> > contains the contents of a small initial root filesystem, with just
> > enough in it to to load the modules you're going to need to mount your
> > root filesystem.  In particular it needs to have the modules for your
> > lvm and any RAID controllers.
> >
> > I've never made an initrd on Debian, but on Fedora the command is
> mkinitrd.
> >
> > Don Quixote
> > --
> > Don Quixote de la Mancha
> > quix...@dulcineatech.com
> > http://www.dulcineatech.com
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmas...@lists.debian.org
> >
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
>
>

Re: kernel compile - Unable to mount root fs

[Aioanei Rares]

Aioanei Rares wrote:

mkinitrd is a standard command on all linux systems, so you can check
its manual page. Maybe man update-initramfs can help too. Best of
luck.

On 7/17/09, Don Quixote de la Mancha  wrote:
  

In your Grub menu.lst file, there are some lines that look like this one:

  initrd  /initrd.img-2.6.26-2-686

You need a line like that just below the item for the kernel you're
trying to boot, except that you want the initrd version to match the
new kernel version.

initrd stands for Initial RAM Disk.  It's a compressed archive that
contains the contents of a small initial root filesystem, with just
enough in it to to load the modules you're going to need to mount your
root filesystem.  In particular it needs to have the modules for your
lvm and any RAID controllers.

I've never made an initrd on Debian, but on Fedora the command is mkinitrd.

Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com


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





  

And sorry for the top-post.


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

Re: kernel compile - Unable to mount root fs

[Aioanei Rares]

mkinitrd is a standard command on all linux systems, so you can check
its manual page. Maybe man update-initramfs can help too. Best of
luck.

On 7/17/09, Don Quixote de la Mancha  wrote:
> In your Grub menu.lst file, there are some lines that look like this one:
>
>   initrd  /initrd.img-2.6.26-2-686
>
> You need a line like that just below the item for the kernel you're
> trying to boot, except that you want the initrd version to match the
> new kernel version.
>
> initrd stands for Initial RAM Disk.  It's a compressed archive that
> contains the contents of a small initial root filesystem, with just
> enough in it to to load the modules you're going to need to mount your
> root filesystem.  In particular it needs to have the modules for your
> lvm and any RAID controllers.
>
> I've never made an initrd on Debian, but on Fedora the command is mkinitrd.
>
> Don Quixote
> --
> Don Quixote de la Mancha
> quix...@dulcineatech.com
> http://www.dulcineatech.com
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
>
>


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

Re: kernel compile - Unable to mount root fs

[Don Quixote de la Mancha]

In your Grub menu.lst file, there are some lines that look like this one:

  initrd  /initrd.img-2.6.26-2-686

You need a line like that just below the item for the kernel you're
trying to boot, except that you want the initrd version to match the
new kernel version.

initrd stands for Initial RAM Disk.  It's a compressed archive that
contains the contents of a small initial root filesystem, with just
enough in it to to load the modules you're going to need to mount your
root filesystem.  In particular it needs to have the modules for your
lvm and any RAID controllers.

I've never made an initrd on Debian, but on Fedora the command is mkinitrd.

Don Quixote
-- 
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com


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

Re: kernel compile - Unable to mount root fs

[Soren Orel]

thank you for the quick replies :O

I just only did, what I mentioned in the starting mail:S

ls -la /boot:
http://pastebin.com/f7dc58737

cat /boot/grub/menu.lst
http://pastebin.com/f566152fc

On Fri, Jul 17, 2009 at 9:11 PM, Don Quixote de la Mancha <
quix...@dulcineatech.com> wrote:

> Did you build and install your initrd?  You might need to load a
> module to mount your root filesystem, and if so it should be in the
> initrd.
>
> The initrd also needs to be named in your grub entry.
>
> It's not enough just to build and install the module, because those
> are accessible only after your root fs is mounted!
>
> --
> Don Quixote de la Mancha
> quix...@dulcineatech.com
> http://www.dulcineatech.com
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
>
>

Re: kernel compile - Unable to mount root fs

[Don Quixote de la Mancha]

Did you build and install your initrd?  You might need to load a
module to mount your root filesystem, and if so it should be in the
initrd.

The initrd also needs to be named in your grub entry.

It's not enough just to build and install the module, because those
are accessible only after your root fs is mounted!

-- 
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com


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

Re: kernel compile - Unable to mount root fs

[Soren Orel]

trying in single mode:
http://img514.imageshack.us/img514/7868/screenshotsrf.png
trying in normal mode:
http://img219.imageshack.us/img219/6290/screenshot1u.png

I forget to tell, that this pc uses lvm :S

On Fri, Jul 17, 2009 at 8:59 PM, Aioanei Rares wrote:

> Soren Orel wrote:
>
>> debian lenny
>>
>> I download 2.6.30-1 source
>> tar -xjf linux-2.6.30.1.tar.bz2
>> cd linux-2.6.30.1
>> cp /boot/config-2.6.26-2-686 ./.config
>> apt-get install make gcc libncurses5-dev
>> make menuconfig (replace M to *):
>>
>> Device Drivers - Multiple device support (RAID and LVM) - Device mapper
>> support
>> File systems - Ext3 journalling file system support
>>
>> time make -j2
>> make modules_install install
>> update-grub
>>
>> then...reboot...
>>
>> "VFS: Unable to mount root fs on"
>>
>> What am I missing? I still have to make more "modules to built-ins"?
>>
>> thank you... :\
>>
> Did grub made an entry in its menu allowing you to boot in single mode? Try
> that please and report back. I've had the same problem a while ago on
> testing/unstable.
>

Re: kernel compile - Unable to mount root fs

[Aioanei Rares]

Soren Orel wrote:

debian lenny

I download 2.6.30-1 source
tar -xjf linux-2.6.30.1.tar.bz2
cd linux-2.6.30.1
cp /boot/config-2.6.26-2-686 ./.config
apt-get install make gcc libncurses5-dev
make menuconfig (replace M to *):

Device Drivers - Multiple device support (RAID and LVM) - Device 
mapper support

File systems - Ext3 journalling file system support

time make -j2
make modules_install install
update-grub

then...reboot...

"VFS: Unable to mount root fs on"

What am I missing? I still have to make more "modules to built-ins"?

thank you... :\
Did grub made an entry in its menu allowing you to boot in single mode? 
Try that please and report back. I've had the same problem a while ago 
on testing/unstable.



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

Re: kernel compile module compile

[Celejar]

On Tue, 14 Aug 2007 02:54:55 -0400 (CDT)
"Orestes Leal" <[EMAIL PROTECTED]> wrote:

> Maybe this modules doesn't work 'yet' with that kernel,
> one Question, How do you build your kernel?
> it´s suggested by linux that the sources of the kernel
> must not be placed in /usr/src
> 
> for example my kernel sources are in /kernelsource

Since best practices are anyway not to build kernels as root, I unpack
my kernels into $HOME/someplace.

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator

Re: kernel compile module compile

[Orestes Leal]

Maybe this modules doesn't work 'yet' with that kernel,
one Question, How do you build your kernel?
it´s suggested by linux that the sources of the kernel
must not be placed in /usr/src

for example my kernel sources are in /kernelsource


El Dom, 12 de Agosto de 2007, 2:08 pm, L.V.Gandhi escribió:
> I was trying to compile kernel src from backports with alsa modules
> and ipw3945 modules. src was tar-.gz files fo this modules.
> I get error like this
>
> /usr/src/modules/alsa-driver/include/adriver.h: In function
> 'snd_pci_orig_save_state':
> /usr/src/modules/alsa-driver/include/adriver.h:1099: error: too many
> arguments to function 'pci_save_state'
> /usr/src/modules/alsa-driver/include/adriver.h: In function
> 'snd_pci_orig_restore_state':
> /usr/src/modules/alsa-driver/include/adriver.h:1103: error: too many
> arguments to function 'pci_restore_state'
> make[7]: *** [/usr/src/modules/alsa-driver/acore/hwdep.o] Error 1
> make[6]: *** [/usr/src/modules/alsa-driver/acore] Error 2
> make[5]: *** [_module_/usr/src/modules/alsa-driver] Error 2
> make[4]: *** [modules] Error 2
> make[4]: Leaving directory `/usr/src/linux-source-2.6.21'
> make[3]: *** [compile] Error 2
> make[3]: Leaving directory `/usr/src/modules/alsa-driver'
> make[2]: *** [build-stamp] Error 2
> make[2]: Leaving directory `/usr/src/modules/alsa-driver'
> make[1]: *** [kdist_image] Error 2
> make[1]: Leaving directory `/usr/src/modules/alsa-driver'
> Module /usr/src/modules/alsa-driver failed.
> Hit return to Continue
> make[4]: Entering directory `/usr/src/linux-source-2.6.21'
>   CC [M]  /usr/src/modules/ipw3945/ipw3945.o
> /usr/src/modules/ipw3945/ipw3945.c: In function
> 'ipw_setup_activity_timer':
> /usr/src/modules/ipw3945/ipw3945.c:1351: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_bg_activity_timer':
> /usr/src/modules/ipw3945/ipw3945.c:1371: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_scan_schedule':
> /usr/src/modules/ipw3945/ipw3945.c:2436: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_scan_cancel':
> /usr/src/modules/ipw3945/ipw3945.c:2502: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_scan_completed':
> /usr/src/modules/ipw3945/ipw3945.c:2533: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_bg_calibrated_work':
> /usr/src/modules/ipw3945/ipw3945.c:4570: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c:4582: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_disassociate':
> /usr/src/modules/ipw3945/ipw3945.c:6756: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_gather_stats':
> /usr/src/modules/ipw3945/ipw3945.c:7140: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_bg_request_scan':
> /usr/src/modules/ipw3945/ipw3945.c:8392: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function
> 'ipw_handle_assoc_response':
> /usr/src/modules/ipw3945/ipw3945.c:9816: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_associate_network':
> /usr/src/modules/ipw3945/ipw3945.c:1: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_rx_handle':
> /usr/src/modules/ipw3945/ipw3945.c:11381: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_wx_set_mode':
> /usr/src/modules/ipw3945/ipw3945.c:11824: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c:11825: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function 'ipw_bg_rate_scale_flush':
> /usr/src/modules/ipw3945/ipw3945.c:13983: warning: passing argument 1
> of 'cancel_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c:14010: warning: passing argument 2
> of 'queue_delayed_work' from incompatible pointer type
> /usr/src/modules/ipw3945/ipw3945.c: In function
> 'ipw_rate_scale_tx_resp_handle':
> /usr/src/modules/ipw3945/ipw3945.c:14267: warning: passing argument 1
> of 'can

Re: kernel compile -processor type

[Orestes leal]

> What should be kernel compile -processor type for
> Intel(R) Core(TM)2 CPU T5500  @ 1.66GHz
> -- 
> L.V.Gandhi
> http://lvgandhi.tripod.com/
> linux user No.205042
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

In the kernel config go to the processor type and select (in 2.6.22.2 or 
similars)
"Core 2 Processors" or something like that, recompile the kernel, do the 
required steps 
and reboot.

-olr


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

Re: Kernel compile the old way

[Bernard Adrian]

Ismael Valladolid Torres <[EMAIL PROTECTED]> a écrit : 


[...]

> The more customized your kernel to your system, the better. But often
> improvements don't compensate the amount of work it requires to end up
> with a kernel fully optimized to your system.
>
> I usually use Debian kernel's config as my .config when compiling a
> new kernel. And Debian's config more or less expect you to be using
> initrd. That's why I usually use initrd when compiling a custom kernel
> although probably it would be better not to use it. For me, it's a
> balance between amount of work needed and real improvement.
>
> My two euro cents. :)

Thanks - merci for your advice !
-- 
Bernard Adrian 


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

Re: Kernel compile the old way

[Ismael Valladolid Torres]

Bernard Adrian escribe:
> Should i understand my system would work better if i install the same
> kernel without initrd ?

The more customized your kernel to your system, the better. But often
improvements don't compensate the amount of work it requires to end up
with a kernel fully optimized to your system.

I usually use Debian kernel's config as my .config when compiling a
new kernel. And Debian's config more or less expect you to be using
initrd. That's why I usually use initrd when compiling a custom kernel
although probably it would be better not to use it. For me, it's a
balance between amount of work needed and real improvement.

My two euro cents. :)

Cordially, Ismael
-- 
Ismael Valladolid Torres "Il est vain de pleurer sur l'esprit, il suffit
  de travailler pour lui." Albert Camus
http://digitrazos.info/
http://lamediahostia.blogspot.com/OpenPGP key ID: 0xDE721AF4
http://www.hispasonic.com/foro73.html  Jabber ID: [EMAIL PROTECTED]


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

Re: Kernel compile the old way

[John Hasler]

I wrote:
> For a distribution kernel it provides support for all possible
> permutations and combinations of hardware.  I don't know of any
> advantages for a custom kernel.

Manoj Srivastava writes:
> Well, I have a fully encrypted laptop hard drive, apart from a 42MB /boot
> (including encrypted swap).  Now way to do that without using an initrd
> image.

Obviously, there are special situations.  I've seen it claimed that
everyone should always use initrd, but without explanation.
-- 
John Hasler


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

Re: Kernel compile the old way

[Manoj Srivastava]

On Sat, 11 Nov 2006 10:30:19 -0600, John Hasler <[EMAIL PROTECTED]> said: 

> Amit Joshi writes:
>> What exactly are the advantages of using an initrd?

> For a distribution kernel it provides support for all possible
> permutations and combinations of hardware.  I don't know of any
> advantages for a custom kernel.

Well, I have a fully encrypted laptop hard drive, apart from a
 42MB /boot (including encrypted swap).  Now way to do that without
 using an initrd image.

manoj
-- 
A fool and his honey are soon parted.
Manoj Srivastava <[EMAIL PROTECTED]> 
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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

Re: Kernel compile the old way

[Bernard Adrian]

John Hasler <[EMAIL PROTECTED]> a écrit : 

> Initrd is an extra bit of complexity at bootup but it makes no difference
> once the system is up.  Don't worry about it.

Ok. Thanks !
-- 
Bernard Adrian 
http://www.bernadrian.net


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

Re: Kernel compile the old way

[Bernard Adrian]

Bernard Adrian <[EMAIL PROTECTED]> a écrit : 


[...]

> I'm compiling a custom kernel (2.6.1) with initrd for my system (AMD K6-II 64

Oups : i wanted to say kernel 2.6.17 and no 2.6.1

-- 
Bernard Adrian 
http://www.bernadrian.net


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

Re: Kernel compile the old way

[John Hasler]

Bernard Adrian writes:
> Should i understand my system would work better if i install the same
> kernel without initrd ?

Initrd is an extra bit of complexity at bootup but it makes no difference
once the system is up.  Don't worry about it.
-- 
John Hasler


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

Re: Kernel compile the old way

[Bernard Adrian]

John Hasler <[EMAIL PROTECTED]> a écrit : 

> For a distribution kernel it provides support for all possible permutations
> and combinations of hardware.  I don't know of any advantages for a custom
> kernel.

Huh,

I'm compiling a custom kernel (2.6.1) with initrd for my system (AMD K6-II 64
Mo RAM). I get an initrd.img of 2.4 Mo. Ext3 and so are not in modules.

Should i understand my system would work better if i install the same
kernel without initrd ?

Thanks
-- 
Bernard Adrian 
http://www.bernadrian.net


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

Re: Kernel compile the old way

[Hugo Vanwoerkom]

Amit Joshi wrote:

On Saturday 11 November 2006 22:00, John Hasler wrote:

Amit Joshi writes:

What exactly are the advantages of using an initrd?

For a distribution kernel it provides support for all possible permutations
and combinations of hardware.  I don't know of any advantages for a custom
kernel.
--
John Hasler


Oh..thanks for the information. Now I know why custom built kernels don't have 
initrd images. :)




Not exactly. I use a custom kernel and the suspend2 patch. That enables 
you to suspend/resume and show the progress of that process with a userui.


But if you want to see the progress on *resume* you have to use an 
initrd that loads the userui *before* the kernel gets control.


Sad to say it doesn't work. Tried it with yaird.

Problem: yaird uses Perl to put the initrd together but not too much in 
the way of info as to what actually happens.


Hugo


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

Re: Kernel compile the old way

[Amit Joshi]

On Saturday 11 November 2006 22:00, John Hasler wrote:
> Amit Joshi writes:
> > What exactly are the advantages of using an initrd?
>
> For a distribution kernel it provides support for all possible permutations
> and combinations of hardware.  I don't know of any advantages for a custom
> kernel.
> --
> John Hasler

Oh..thanks for the information. Now I know why custom built kernels don't have 
initrd images. :)

Regards, 
Amit.
-- 
Remember fellas, what we do in life echoes in eternity! 


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

Re: Kernel compile the old way

[John Hasler]

Amit Joshi writes:
> What exactly are the advantages of using an initrd?

For a distribution kernel it provides support for all possible permutations
and combinations of hardware.  I don't know of any advantages for a custom
kernel.
-- 
John Hasler


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

Re: Kernel compile the old way

[Amit Joshi]

On Saturday 11 November 2006 20:00, Wackojacko wrote:
> Marc Wilson wrote:
> > On Fri, Nov 10, 2006 at 02:10:53PM -0600, Hugo Vanwoerkom wrote:
> >> make menuconfig
> >> make-kpkg --revision 1 kernel_image
> >
> > Don't you end up with an initrd that way?  I admit to never wasting my
> > time with kernel-package, but I thought you couldn't avoid one if you
> > insisted on using it.
>
> No if you want an initrd you have to specify it to make-kpkg.
>
> HTH
>
> Wackojacko

What exactly are the advantages of using an initrd?
Oh I know it is Initial RAM Disk..but does it speed up the boot process or 
something?? Just curious...
-- 
Remember fellas, what we do in life echoes in eternity! 


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

Re: Kernel compile the old way

[Wackojacko]

Marc Wilson wrote:

On Fri, Nov 10, 2006 at 02:10:53PM -0600, Hugo Vanwoerkom wrote:

make menuconfig
make-kpkg --revision 1 kernel_image


Don't you end up with an initrd that way?  I admit to never wasting my time
with kernel-package, but I thought you couldn't avoid one if you insisted
on using it.


No if you want an initrd you have to specify it to make-kpkg.

HTH

Wackojacko


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

Re: Kernel compile the old way

[Marc Wilson]

On Fri, Nov 10, 2006 at 02:10:53PM -0600, Hugo Vanwoerkom wrote:
> make menuconfig
> make-kpkg --revision 1 kernel_image

Don't you end up with an initrd that way?  I admit to never wasting my time
with kernel-package, but I thought you couldn't avoid one if you insisted
on using it.

-- 
 Marc Wilson | IF I HAD A MINE SHAFT, I don't think I would just
 [EMAIL PROTECTED] | abandon it.  There's got to be a better way.  --
 | Jack Handley, The New Mexican, 1988.


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

RE: Kernel compile the old way

[Mike Kuhar]

I went to compile a vanilla kernel from kernel.org, and so read the
directions at the Debian site.  They seem to me to be needlessly
complicated.  Is there something in Debian which would prevent me from
compiling a kernel the good old fashioned way --

make menuconfig
make && make modules_install
cp bzImage and System.map to /boot
edit the grub menu

-- and skip the initrd whatever?  And, if so, where does Debian load the
modules from, so I can edit that too?  It's not /etc/modules - only a
few there.

Any advice appreciated.  Thanks.

I'm currently in the unstable tree and I build my own kernels all the time.
I have not found any compelling reason to get the plain vanilla kernel
source, nor going the "make-kpkg --revision 1 kernel_image" route.  Once I
had a working .conf file I reuse that for every kernel rebuild.  I use the
linux-source-{version} from debian for my rebuilds.  And I don't have to
name my kernels, of mess with grub, once it's set up.

The steps are:
make menuconfig
make bzImage
make modules
make modules_install

and the one step that everyone leaves out, which handles grub:

make install

In point of fact, that last step does nothing specifically with grub.  What
it does do is change the symbolic links.  That is, it changes /boot/vmlinuz
to link to the latest built kernel, and /boot/vmlinuz.old to the previously
built kernel.  Grub always points to /boot/vmlinuz and /boot/vmlinuz.old.
The downside of this is that your previous build always becomes vnlinuz.old,
even if it's the same version.  The upside is that all previously built
kernels remain in /boot untill you remove them.

My problem, is that I can never remember which version I'm using.  What I
mean is, I can't remenber if linux-sourse-2.6.18-4 or 2.6.18-5 is my working
kernel.  The .config file has a variable under '# General setup' called
CONFIG_LOCALVERSION which I set to the version I'm currently building.  In
my current case, it's set as:

CONFIG_LOCALVERSION="-5"

So when I do a uname -a, I see the the Linux version as 2.6.18-5, instead of
2.6.18.  It comes in handy.

When you build a particular kernel source for the first time, you don't have
to run 'make clean'.  This is only needed if you have to rebuild the
specific kernel a second or third time.

You can always see the versions available by simply doing:

apt-get install linux-source

If you're currently using linux-source-2.6.16, don't do an "apt-get remove
linux-source-2.6.16" until you have had a successful build on
linux-source-2.6.18.

Good luck.  -mike


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

Re: Kernel compile the old way

[Amit Joshi]

On Saturday 11 November 2006 00:56, Ed wrote:
> I went to compile a vanilla kernel from kernel.org, and so read the
> directions at the Debian site.  They seem to me to be needlessly
> complicated.  Is there something in Debian which would prevent me from
> compiling a kernel the good old fashioned way --
>
> make menuconfig
> make && make modules_install
> cp bzImage and System.map to /boot
> edit the grub menu
>
> -- and skip the initrd whatever?  And, if so, where does Debian load the
> modules from, so I can edit that too?  It's not /etc/modules - only a
> few there.
>
> Any advice appreciated.  Thanks.

AFAIK modprobe can load modules only if they are compiled that way in the 
kernel. [M] indicates that the particular driver is compiled in as a module. 

The debian patched kernels are pretty good. I won't use a Vanilla source 
unless there's any specific need to do that. 

Also, I am not sure..but SID might be having the latest stable kernel in its 
repositories. 
The simplest way to install a debian-patched kernel is: 
[EMAIL PROTECTED] install kernel-image-

This procedure simply installs the kernel, without having to run the make 
menuconfig thing et al. Moreover it also updates the /boot/grub/menu.lst file 
automatically. Truly advantageous you see.. :)

-- 
Remember fellas, what we do in life echoes in eternity! 


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

Re: Kernel compile the old way

[Hugo Vanwoerkom]

Ed wrote:
I went to compile a vanilla kernel from kernel.org, and so read the 
directions at the Debian site.  They seem to me to be needlessly 
complicated.  Is there something in Debian which would prevent me from 
compiling a kernel the good old fashioned way --


make menuconfig
make && make modules_install
cp bzImage and System.map to /boot
edit the grub menu

-- and skip the initrd whatever?  And, if so, where does Debian load the 
modules from, so I can edit that too?  It's not /etc/modules - only a 
few there.


Any advice appreciated.  Thanks.




make menuconfig
make-kpkg --revision 1 kernel_image

Does all of that and you need not do more but:

dpkg -i 
boot with the newly installed kernel







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

Re: kernel compile volume picture.

[Kent West]

L.V.Gandhi wrote:


On 2/18/06, Kent West <[EMAIL PROTECTED]> wrote:

 


Do you get it if you log into a different windowing environment (Gnome,
fluxbox, edtc)?

Do you get it if you log in as a different user?
   



As I don't have other wm or other user I didn't try them.

 

The reason I asked is to isolate the problem. Is it something started by 
KDE (even though it's obviously triggered by your new kernel)? So even 
though you don't have a different windowing environment, or a different 
user, it's still a good test. Adding a new window manager or user is 
fairly trivial.


"aptitude install twm" or "aptitude install icewm" will get you a new wm.
"adduser testman" will get you a new user.

Also, try logging in without using kdm: "/etc/init.d/kdm stop" followed 
by "startx". You can create/edit "~/.xinitrc", placing a single line in 
it with the name of your preferred window manager (or other X client, 
such as "xterm") to take KDE out of the picture.



Do you get it if you start with your old kernel?
   



no. Also as I have said in reply to other post, I compiled kernel with
out dell laptop support in kernel, I don't get it.
 


Sorry; I misread the earlier post.

--
Kent


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

Re: kernel compile volume picture.

[L . V . Gandhi]

On 2/18/06, Kent West <[EMAIL PROTECTED]> wrote:

> Do you get it if you log into a different windowing environment (Gnome,
> fluxbox, edtc)?
>
> Do you get it if you log in as a different user?

As I don't have other wm or other user I didn't try them.

> Do you get it if you start with your old kernel?

no. Also as I have said in reply to other post, I compiled kernel with
out dell laptop support in kernel, I don't get it.
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042

Re: kernel compile volume picture.

[Kent West]

L.V.Gandhi wrote:

>Today I compiled kernel with same config but for enabling dell laptop
>option and disabling radeonfb. But when I boot with new kernel and do
>login through kdm, I get volume picture as given in attachment. I
>don't know how to remove it? Why does it appear?
>
>  
>
Do you get it if you log into a different windowing environment (Gnome,
fluxbox, edtc)?

Do you get it if you log in as a different user?

Do you get it if you start with your old kernel?

-- 
Kent


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

Re: kernel compile volume picture.

[L . V . Gandhi]

On 2/18/06, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
> L.V.Gandhi wrote:
> > Today I compiled kernel with same config but for enabling dell laptop
> > option and disabling radeonfb. But when I boot with new kernel and do
> > login through kdm, I get volume picture as given in attachment. I
> > don't know how to remove it? Why does it appear?
> >
>
> You mean you login through kdm and go to konsole this nice things stays
> pasted on the screen?

Yes. But konsole I don't close while logging out. Volume picture
remains stay put.

> What's the kernel?
2.6.15. But I compiled kernel with dell laptop disabled, I didn't get anymore.

--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042

Re: kernel compile volume picture.

[Hugo Vanwoerkom]

L.V.Gandhi wrote:

Today I compiled kernel with same config but for enabling dell laptop
option and disabling radeonfb. But when I boot with new kernel and do
login through kdm, I get volume picture as given in attachment. I
don't know how to remove it? Why does it appear?



You mean you login through kdm and go to konsole this nice things stays 
pasted on the screen?


What's the kernel?

H


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

Re: Kernel compile fails.

[Linas Zvirblis]

Alejandro Bonilla Beeche wrote:

   I have a box with Sid with the latest upgrades, (almost cause 
dist-upgrade wants to remove a lot of stuff)


Anyway, fact is that I can't compile any kernel on the Linus tree. This, 
for more than a month.


Could anyone please help me find out which package is the broken one? 
/bin/sh in Bash.


2.6.16-rc1 has a bug that trashes /dev/null and is the cause for this 
error. Recreate /dev/null and compile it as a non-root user. LKML people 
seem to be aware of this, so it likely to be fixed in the future release 
(2.6.16-rc1-git4 is still affected). I also learned the lesson the hard 
way by forgetting to exit root before compiling. Oh well...


Other than that, 2.6.16-rc1 works fine, but may break iptables on some 
systems (also a known bug).



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

Re: kernel-compile-troubleshooting -- help with a howto

[Chris Bannister]

On Fri, Nov 11, 2005 at 01:43:17PM -0500, Matt Price wrote:
> Hi folks,
> 
> I've compiled my own kernel numerous times but am not
> programming-literate; often I wish there was a howto that explained the
> significance of certain common problems that I seem to have over and
> over again.  Haven't found one, though, so thought I'd write my own: 
> 
> http://wiki.debian.org/KernelCompileTroubleshooting
> 
> Unfurtunatley, I'm so ignorant, I can't really answer my own
> questions!  Therefore, I'm asking for help.  I'd like to hear what is
> wrong, misleading, or justp lain missing from this document.  The
> current version is appended below, and feel free to carry on this
> ocnversation eithero n the list, or by direct modification of the wiki
> page (which is after all what wikis are for).  
> 
> Thanks,
> 
> Matt
> 
> --
> KernelCompileTroubleshooting
> 
> BuildYourOwnKernel
> Please Do not Trust This Page! Author is Ignorant! Instead, Amend with
> Corrections!
> 
> Sometimes the standard howto is not enough. This page describes some
> factors that affect the success of kernel compilation and
> installation, for non-programmers like the author who don't really
> understand what happens when the kernel is
> compiled. BuildYourOwnKernel and the link collected their is a much
  ^
should be "there" instead of "their"


> better place to start!
> 1. Compile-time problems
> setting gcc version
> 
> GCC is the gnu-c-compiler; it's the program used to compile all the
> C-based programs on your system (that's most of them). New versions of
> the compiler are periodically released, I guess either because the C
> language standard changes, or because new hardware comes on line that
> requires special implementations (I think, for instance, that it's
> easier to use recent gcc versions to compile
> 64-bit-processor-compatible code; but I don't really know, I already
> said I'm not a programmer!). In general, the linux kernel does not
> compile equally well with all versions of gcc. It would be nice to
> have a complete list of which kernel versions suggest/require which
> gcc versions, but I don't have one; I do know, though, that Debian/Sid
> kernels are currently (Oct. 2005) all compiled with gcc-4.0. However
> I've had lots of trouble compiling kernels 2.6.12 and lower with
> gcc-4.0.
> 
> On Debian, /usr/bin/gcc is a symlink, so in principle you can just
> change the target from gcc-4.0 to gcc-3.4 whenever you like. This
> however is not recommended, because many packages will expect the link
> to point to a particular version of gcc (why is this? I'd love to know
> the answer.).
> 
> Instead, we can easily change the version of gcc used by make-kpkg
> using the "MAKEFLAGS" command:
> 
> *
> 
>   MAKEFLAGS="CC=gcc-3.4" make-kpkg kernel-image
> 
> Question: Does this always really work? Or are there other factors in
> your environment that can influence compile-time behaviour by
> make-kpkg?
> 
> One thing to done here is that third-party modules built for the
  ^^

How about "Third party modules built for the"

> resulting kernel must be built with the same version of gcc as the
> kernel-package itself. You can do that thusly:
> 
> *
> 
>   using module assistant:
>   o
> 
> CC="gcc-3.4" module-assistant auto-install
> some_source_package
> 
>   or
>   o
> 
> module-assistant --cc="gcc-3.4" auto-install
> some_source_package
> *
> 
>   in the old-fashioned way:
>   o
> 
> ./configure CC="gcc-3.4" make
> 
> Anyone know if this is really true?
> Cleaning the Tree
> 
> When you compile a kernel, hundereds (thousands?) of new files are
 ^
hundreds

> created in the kernel tree. By default those files are left in place
> after the kernel is built. That's great if you want to recompile the
> kernel soon after -- maybe you forgot to include a module? -- the
> computer just reuses the files from the last install, and the whole
> process only takes a minute or two instead of an hour.
> 
> However, sometimes the files left behind can break your next
> compilation. I don't really know why, but here are some things I've
> seen:
> 
> *
> 
>   You want to change the revision or "append-to-version" flags on
> your compile (maybe because, after 10 or 20 tries, you've actually
> made a kernel that compiles, installs, and boots, and you don't want
> to delete that kernel when you install the next one). make-kpkg will
> not let you proceed without cleaning the tree.
> *
> 
>   Somehow you've screwed up something in your build environment --
> maybe on your last attempt you accidentally compiled with a different
> gcc-version? -- and the files left behind on your disk are
> corrupted. THen stuff further down the road will get screwed up too
> (is this really true?).
> 
> So when

Re: kernel-compile-troubleshooting -- help with a howto

[Alvin Oga]

On Fri, 11 Nov 2005, Matt Price wrote:

> I've compiled my own kernel numerous times but am not
> programming-literate; often I wish there was a howto that explained the
> significance of certain common problems that I seem to have over and
> over again.

which problems

>  Haven't found one, though, so thought I'd write my own: 

good idea
 
> http://wiki.debian.org/KernelCompileTroubleshooting
>
> Unfurtunatley, I'm so ignorant, 

nah

> I can't really answer my own questions!

nah .. whether it's the right answer or one of many dozen right 
answers is the question

> Therefore, I'm asking for help.  I'd like to hear what is
> wrong, misleading, or justp lain missing from this document.

there's already (too many) generic "kernel howto"
- most address their tidbits the author wanted to cover
but not other stuff

> Sometimes the standard howto is not enough.

or too much info ( usually the case )

if the target audience are beginners, and if the idea is to simplify
generic kernel compiling, less info is better ?? ( imho )

#
# make a script "make-kernel-for-my-box.sh" if compiling
# a kernel is too much headache .. 99% of all this is scriptable
#   - the 1% is the actual reboot and see if it works
#
cd /usr/local/src
get the latest kernel from kernel.org
tar jxvfp linux-latest.tar.bz2
cd linux-latest

( optional ) make dep, make clean if you're paranoid
make bzlilo
- this assumes the defaults is good enuff for some
folks that is not paranoid and don't want to fine
tune this or that

make install
- usually installed as /vmlinuz and /System.map
- mv /vmlinuz /boot/vmlinuz-latest
- mv /System.map /boot/System.map-latest
make modules
make modules_install
- cp .config /boot/config-latest
- update lilo or grub
- reboot

some minor tweeking ..  ( fixing problems )
cd linux-latest
make xconfig

- start turning everything off and/or use the default
from the "help"

- you will need to make sure your motherboard chipset
is turned on or as a module in the kernel

- check and study the output of lspci and find the
  corresponding kernel option in the kernel config gui

- figure out which file systems you want to support

make 
make install
...

some security tricks .. ( tweeking to minimize buffer overflow risks )

apply kernel patches to harden the puppy ...

by this point, you shouldn't be needing a kernel-howto
other than for the detailed specific security hardening howto



another common problem is  doesn't work, where xxx is
some kind of disk, sound, network problems

- one has to check which chipset is used ( lspci )
and turn on that driver in the kernel

another common problem is the modules doesn't install

- the gcc to use for making and installing the modules have to
be the same gcc that was used to compile the original kernel
that is being used/booted


> 1. Compile-time problems
> setting gcc version
> 
> GCC is the gnu-c-compiler

playing with gcc is asking for next generation troubles but that's
part of the fun
- you'd also need to have the proper glibc, bash, /lib
and other cousins

c ya
alvin


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

Re: Kernel Compile - the Debian way

[martin f krafft]

also sprach Clive Menzies <[EMAIL PROTECTED]> [2005.07.26.0144 +0200]:
> For an explanation of the kernel workings, Martin Krafft's new book, The
> Debian System, might be the place: http://debiansystem.info/about

My book does not talk about "kernel workings" (which would be an
entire book of its own), but it covers pretty much all aspects of
Debian kernel handling: what the different kernel-* packages are
(starting with 2.6.12, that's linux-*!), when and why they are
needed, how they are supposed to be used, and it shows how to use
make-kpkg to create Debian kernel images, apply kernel patches, and
create modules for existing kernels. Finally, it explains Debian's
approach to modules and how module-assistant makes an
administrator's (and maintainer's life) much easier.

So yeah, if you already know how to compile kernels and you are
looking for the Debian Way, you'll find answers in my book.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
 
"i am not in favor of long engagements. they give people the
 opportunity of finding out each other's character before marriage, 
 which i think is never advisable."
-- oscar wilde


signature.asc
Description: Digital signature

Re: Kernel Compile - the Debian way

[Paul E Condon]

On Mon, Jul 25, 2005 at 06:00:27PM -0500, Josh Battles wrote:
> I'd like to learn how to compile a kernel the Debian way and haven't had that
> much luck finding a faq or walkthrough that explains what I'm doing
> step-by-step and why I'm doing it.  I hear that it's easier than the
> "standard way" and I'd like to find out for myself what it's all about.
> 
> can someone point me to a doc/faq/tutorial somewhere that gives me the hows
> and a well written version of the whys?  I've searched all over and haven't
> really been able to find much that didn't just tell me to blindly follow the
> given steps.
> 
> Thanks
> 
> -- 
> - Josh
> www.omg-stfu.com
> 

Look at the package named 'kernel-package'. It is, IMHO, the best! It builds a
Debian style kernel-image package which you can install using dpkg. The man
page for mkpkg (?) is very complete. 

-- 
Paul E Condon   
[EMAIL PROTECTED]


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

Re: Kernel Compile - the Debian way

[Clive Menzies]

On (25/07/05 18:00), Josh Battles wrote:
> I'd like to learn how to compile a kernel the Debian way and haven't had that
> much luck finding a faq or walkthrough that explains what I'm doing
> step-by-step and why I'm doing it.  I hear that it's easier than the
> "standard way" and I'd like to find out for myself what it's all about.
> 
> can someone point me to a doc/faq/tutorial somewhere that gives me the hows
> and a well written version of the whys?  I've searched all over and haven't
> really been able to find much that didn't just tell me to blindly follow the
> given steps.

A very good howto is at:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html

For an explanation of the kernel workings, Martin Krafft's new book, The
Debian System, might be the place: http://debiansystem.info/about

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business



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

Re: kernel compile error

[Jule Slootbeek]

that worked, strange, did some stuff change in the config file?
-JSS
[EMAIL PROTECTED] wrote:
Jule
The /usr/include/version.h in general does not match
the /usr/src/linux/include/linux/version.h which will be created during a
kernel configureation
Try
 # make mrproper
before
 # make bzImage
MarvS
Original Message:
-
From: Jule Slootbeek [EMAIL PROTECTED]
Date: Fri, 22 Oct 2004 15:32:25 -0400
To: [EMAIL PROTECTED]
Subject: kernel compile error
Hey all
	I'm just trying to install 2.6.9 and am getting this error, i have no 
idea why

dolphy:/usr/src/linux# make bzImage
/bin/sh: Syntax error: Unterminated quoted string
make: *** [include/linux/version.h] Error 2
the only include/linux/version.h i can find is in /usr/include/linux/ 
which looks like this

#define UTS_RELEASE "2.6.0-test7"
#define LINUX_VERSION_CODE 132608
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
I'm not sure why it says 2.6.0-test7, but for the rest i don't see 
anything wrong with this.

anybody ahve an idea?
thanks
-JSS
--
Jule Slootbeek
[EMAIL PROTECTED]
http://www.thesloot.com
617 901 6958
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RE: kernel compile error

[[EMAIL PROTECTED]]

Jule

The /usr/include/version.h in general does not match
the /usr/src/linux/include/linux/version.h which will be created during a
kernel configureation

Try
 # make mrproper
before
 # make bzImage

MarvS
Original Message:
-
From: Jule Slootbeek [EMAIL PROTECTED]
Date: Fri, 22 Oct 2004 15:32:25 -0400
To: [EMAIL PROTECTED]
Subject: kernel compile error


Hey all
I'm just trying to install 2.6.9 and am getting this error, i have no 
idea why

dolphy:/usr/src/linux# make bzImage
/bin/sh: Syntax error: Unterminated quoted string
make: *** [include/linux/version.h] Error 2

the only include/linux/version.h i can find is in /usr/include/linux/ 
which looks like this

#define UTS_RELEASE "2.6.0-test7"
#define LINUX_VERSION_CODE 132608
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

I'm not sure why it says 2.6.0-test7, but for the rest i don't see 
anything wrong with this.

anybody ahve an idea?

thanks

-JSS

-- 
Jule Slootbeek
[EMAIL PROTECTED]
http://www.thesloot.com


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



mail2web - Check your email from the web at
http://mail2web.com/ .

Re: Kernel Compile

[matt zagrabelny]

On Mon, 2004-08-30 at 19:06, Grant wrote:
> Hey,
> 
> I have a laptop P2 300mhz, 128mb ram and a desktop box thats 2ghz,512mb ram.
> 
> The question is that could i use my 2ghz machine to make and compile a 
> kernel, then package it up into a .deb and send it to the laptop and 
> install it and it work ?
> 
> Would i need any extras ? i know i would have to select the hardware for 
> the laptop, but would i need to include the hardware for the 2ghz or 
> just the laptop ?
> 
> Thanks
> Grant.
> 
kernel-package is the package that contains make-kpkg which will make a .deb
file containing the kernel, associated modules, and the scripts to
modify lilo.conf or grub.conf.

check out newbiedoc.sourceforge.net for a good tutorial on how it works.

-matt


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

Re: Kernel Compile

[Grant]

Sergio Basurto wrote:
Why you must recompile the kernel?, the current dist
support almost any hardware!!
If you really need to do that:
You must compile the Kernel with the hardware of the
laptop, there is not need to include your desktop
hardware.
kernel-package in woody dist, can help you to achive
the .deb package easily.
I also recomend you that have a look to:
http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
Is a very good reference.
Regards.
On Tue, 31 Aug 2004 01:06:59 +0100, Grant wrote:
 

Hey,
I have a laptop P2 300mhz, 128mb ram and a desktop box
thats 2ghz,512mb ram.
The question is that could i use my 2ghz machine to
make and compile a 
kernel, then package it up into a .deb and send it to
the laptop and 
install it and it work ?

Would i need any extras ? i know i would have to
   

select
 

the hardware for 
the laptop, but would i need to include the hardware
for the 2ghz or 
just the laptop ?

Thanks
Grant.

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

Ing. Sergio Basurto Juárez
Tel: 04455-85322945
 

Hey,
I need to compile the kernel as i havnt been able to get the sound card 
working on my laptop.

The laptop is a omnibook 4150A, the B version is supported quite well  
from what i have seen on the internet, but i havnt had much luck with 
this laptop on anything other than mandrake, so i am assuming that if i 
recompile the kernel i can add in what ever mandrake used for my sound card.

from a few sites they say its a CS4282 but everything i have tried so 
far hasnt worked so i am hopping this compile will sort it :)

I wont include the desktop hardware i was just curious as it's using the 
desktop to compile so i thought it might be needed :)

Thanks.
Grant.

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

Re: Kernel Compile

[Sergio Basurto]

Why you must recompile the kernel?, the current dist
support almost any hardware!!
If you really need to do that:
You must compile the Kernel with the hardware of the
laptop, there is not need to include your desktop
hardware.

kernel-package in woody dist, can help you to achive
the .deb package easily.

I also recomend you that have a look to:
http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html

Is a very good reference.

Regards.

On Tue, 31 Aug 2004 01:06:59 +0100, Grant wrote:

> 
> Hey,
> 
> I have a laptop P2 300mhz, 128mb ram and a desktop box
> thats 2ghz,512mb ram.
> 
> The question is that could i use my 2ghz machine to
> make and compile a 
> kernel, then package it up into a .deb and send it to
> the laptop and 
> install it and it work ?
> 
> Would i need any extras ? i know i would have to
select
> the hardware for 
> the laptop, but would i need to include the hardware
> for the 2ghz or 
> just the laptop ?
> 
> Thanks
> Grant.
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]

Ing. Sergio Basurto Juárez
Tel: 04455-85322945


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

Re: Kernel Compile

[Grant]

Stefan O'Rear wrote:
On Tue, Aug 31, 2004 at 01:06:59AM +0100, Grant wrote:
 

Hey,
I have a laptop P2 300mhz, 128mb ram and a desktop box thats 2ghz,512mb ram.
The question is that could i use my 2ghz machine to make and compile a 
kernel, then package it up into a .deb and send it to the laptop and 
install it and it work ?

Would i need any extras ? i know i would have to select the hardware for 
the laptop, but would i need to include the hardware for the 2ghz or 
just the laptop ?
   

Probably just the laptop, BUT, I seem to recall the *config doing
limited hardware probing (like, if you don't watch out you'll get a P4
only kernel).
You may wish to look into distcc. It is a wrapper for gcc that spreads
the work between multiple computers, e.g:
Your laptop and your desktop will be faster than your desktop alone.
 

Hey,
Thanks for the reply.
I think i will try a compile on my desktop first and then transfer it over.
As the laptop has only just been installed up so i havnt a problem with 
loosing anything if the kernel doesnt work or i mess something up.

Then if that doesnt work, i think i will look at trying the other thing 
you mentioned about spreading between them.

Thanks again
Grant.

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

Re: Kernel Compile

[Stefan O'Rear]

On Tue, Aug 31, 2004 at 01:06:59AM +0100, Grant wrote:
> Hey,
> 
> I have a laptop P2 300mhz, 128mb ram and a desktop box thats 2ghz,512mb ram.
> 
> The question is that could i use my 2ghz machine to make and compile a 
> kernel, then package it up into a .deb and send it to the laptop and 
> install it and it work ?
> 
> Would i need any extras ? i know i would have to select the hardware for 
> the laptop, but would i need to include the hardware for the 2ghz or 
> just the laptop ?

Probably just the laptop, BUT, I seem to recall the *config doing
limited hardware probing (like, if you don't watch out you'll get a P4
only kernel).

You may wish to look into distcc. It is a wrapper for gcc that spreads
the work between multiple computers, e.g:

make menuconfig

CC=distcc make -j4 bzImage

Your laptop and your desktop will be faster than your desktop alone.

Note that old (< 2.6 i think) kernels simply can't be built with
multiple processors, so you'd be out of luck whether it's distcc or your
shiny new quad-Opteron PC.

-- 
The world's most effective spam filter:
ln -sf /dev/full /var/mail/$USER


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

Re: Kernel Compile (being really stupid)

[Pigeon]

On Tue, May 25, 2004 at 08:40:02AM +, Rus Foster wrote:
> I'm having one of those stupid days..
> 
> I'm trying to compile the kernel and am getting
> 
> scripts/basic/fixdep.c:97: sys/types.h: No such file or directory
> scripts/basic/fixdep.c:98: sys/stat.h: No such file or directory
> scripts/basic/fixdep.c:99: sys/mman.h: No such file or directory
> scripts/basic/fixdep.c:100: unistd.h: No such file or directory
> scripts/basic/fixdep.c:101: fcntl.h: No such file or directory
> scripts/basic/fixdep.c:102: string.h: No such file or directory
> scripts/basic/fixdep.c:103: stdlib.h: No such file or directory
> scripts/basic/fixdep.c:104: stdio.h: No such file or directory
> 
> Now I know this is due to the system not finding the header files. I've 
> created a linux from /usr/src/linux to /usr/src/linux/include/linux. What 
> am I missing?
> 
> This is a bare bones install so I might of missed a package

libc6-dev?

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F


pgpA0joCHL53i.pgp
Description: PGP signature

Re: Kernel Compile (being really stupid)

[Rus Foster]

> 
> try libc6-dev  .. that's where I'd expect to find atleast stdio.h and
> string.h
> 
> HTH,
>   Shaun

Cheers knew it would be something stupid

Rus
-- 
e: [EMAIL PROTECTED] : t: 1-888-327-6330   
www.jvds.com - Root on your own box
www.vpscolo.com - Your next hosting company
www.cherryhosting.net - Shared Hosting With Everything On Top


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

Re: Kernel Compile (being really stupid)

[Shaun ONeil]

On Tue, 2004-05-25 at 08:40 +, Rus Foster wrote:
> I'm having one of those stupid days..
> 
> I'm trying to compile the kernel and am getting
> 
> scripts/basic/fixdep.c:97: sys/types.h: No such file or directory
> scripts/basic/fixdep.c:98: sys/stat.h: No such file or directory
> scripts/basic/fixdep.c:99: sys/mman.h: No such file or directory
> scripts/basic/fixdep.c:100: unistd.h: No such file or directory
> scripts/basic/fixdep.c:101: fcntl.h: No such file or directory
> scripts/basic/fixdep.c:102: string.h: No such file or directory
> scripts/basic/fixdep.c:103: stdlib.h: No such file or directory
> scripts/basic/fixdep.c:104: stdio.h: No such file or directory
> 
> Now I know this is due to the system not finding the header files. I've 
> created a linux from /usr/src/linux to /usr/src/linux/include/linux. What 
> am I missing?
> 
> This is a bare bones install so I might of missed a package
> 
> Rus
> 
> -- 
> e: [EMAIL PROTECTED] : t: 1-888-327-6330   
> www.jvds.com - Root on your own box
> www.vpscolo.com - Your next hosting company
> www.cherryhosting.net - Shared Hosting With Everything On Top
> 


try libc6-dev  .. that's where I'd expect to find atleast stdio.h and
string.h

HTH,
  Shaun



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

Re: Kernel compile blues

[Pigeon]

On Mon, Feb 23, 2004 at 07:43:01PM +, Pigeon wrote:
> On Sun, Feb 22, 2004 at 09:26:04AM +0100, John L Fjellstad wrote:
> > Also, note that 2.6 kernels won't work in Woody unless you have
> > backports of module-init-tools (and probably a couple of other stuff).
> 
> ... modutils, if you want to keep the ability to boot earlier kernels.
> module-init-tools conflicts with versions of modutils <= 2.4.21-1.

...oh yeah, and procps, libsysfs, sysfsutils.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F


pgp0.pgp
Description: PGP signature

Re: Kernel compile blues

[Pigeon]

On Sun, Feb 22, 2004 at 09:26:04AM +0100, John L Fjellstad wrote:
> Also, note that 2.6 kernels won't work in Woody unless you have
> backports of module-init-tools (and probably a couple of other stuff).

... modutils, if you want to keep the ability to boot earlier kernels.
module-init-tools conflicts with versions of modutils <= 2.4.21-1.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F


pgp0.pgp
Description: PGP signature

Re: Kernel compile blues

[Kai Schindelka]

Miroslav Maiksnar wrote:
cd /usr/src/linux/
make menuconfig
make-kpkg clean
make-kpkg --revision  --append_to_version - \
kernel-image
cd ..
It is IMHO better to add option '--config menu' to second make-kpkg
command and do not use `make menuconfig` (it will prevent some warnings
when changing  or ). And also you can add
'modules-image' after kernel-image to compile external modules (nvidia,
slmodem, etc.). 
You are right. I just kept the first working approach, which does not
mean an "RTFM again" could not yield better results. Thanks for the
hint.
Personally, I do not use --revision, because (AFAIK) kernels with same
version and appendix but different revision number cannot be installed
at same time.
I use --revision to store information about the Kernel package;
--append_to_version also has a revision number, which is raised
on every Kernel build. (There's a wrapper script around that which
automatically downloads the Kernel source for new versions, etc.)
So when you compile and install new (invalid) kernel, it
deinstalls old (working) one and you loose possibility to boot old
kernel. Instead I use "-" as 
Our hostnames tend to be quite long, and for a machine park it would
not be an option to compile Kernels individually. But 
contains a revision number, indeed.
So my favorite commandline is:

make-kpkg clean && time make-kpkg --config menu \
--append-to-version -- kernel_image modules_image
Thanks again.

PS: If I am wrong about something, let me know.
No, you are right. TMTOWTDI for the latter, but then I may be wrong
about my approach also.
--
Bye, Kai
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel compile blues

[John L Fjellstad]

Deboo <[EMAIL PROTECTED]> writes:

> VFS: Cannot open root device "" or 03:06
> Kernel panic: VFS: Unable to mount root fs on 03:06

Did you compile in the correct filesystem? (ie ext3, ext2).  When you
are using initrd, did you compile in support for initrd *and* ram?

I generally avoid initrd if I can, and only use if I building generic
kernels (which is about never)

Also, note that 2.6 kernels won't work in Woody unless you have
backports of module-init-tools (and probably a couple of other stuff).

> 4. make menuconfig (If this is a re-compile of the same kernel I'm
> currently using, then copy the it's .config to this dir)

If you are upgrading, do make oldconfig

> 7. If all ok, run make modules_install (Sometimes all is ok till step 6
> but this one fails)
> 8.  If all ok, copy arch/i386/boot/bzImage to /boot/vmlinuz-2.x.x
> 9. Copy System.map to /boot/System.map-2.x.x

I usually copy before I make modules_install, but I don't know if it
makes any difference

> 11. Make an initrd image: mkinitrd -r /dev/hdax -o initrd-2.x.x.img
> /lib/modules/2.x.x

Is the -r switch really necessary?  And I never added
/lib/modules/2.x.x.   Did you make changes to
/etc/mkinitrd/mkinitrd.conf and /etc/mkinitrd/modules to add the modules
you need to boot up?

-- 
John L. Fjellstad
web: http://www.fjellstad.org/  Quis custodiet ipsos custodes


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

Re: Kernel compile blues

[Miroslav Maiksnar]

V Ne, 22. 02. 2004 v 00:04, Kai Schindelka píše:
> cd /usr/src/linux/
> make menuconfig
> make-kpkg clean
> make-kpkg --revision  --append_to_version - \
> kernel-image
> cd ..

It is IMHO better to add option '--config menu' to second make-kpkg
command and do not use `make menuconfig` (it will prevent some warnings
when changing  or ). And also you can add
'modules-image' after kernel-image to compile external modules (nvidia,
slmodem, etc.). 
Personally, I do not use --revision, because (AFAIK) kernels with same
version and appendix but different revision number cannot be installed
at same time. So when you compile and install new (invalid) kernel, it
deinstalls old (working) one and you loose possibility to boot old
kernel. Instead I use "-" as 

So my favorite commandline is:

make-kpkg clean && time make-kpkg --config menu \
--append-to-version -- kernel_image modules_image

Mixi

PS: If I am wrong about something, let me know.


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

Re: Kernel compile blues

[Kai Schindelka]

Deboo wrote:
Looks like the HA driver module the boot drive is attached to is missing
in initrd. A misconfigured LILO may also be the cause.
	HA driver module? What's that?
I'm sorry: Host Adapter. I am no native speaker.

And I use grub, not lilo.
Ok, that leaves that out.

> Anyway, is it good to compile 2.6 kernels monolithic?

I'm not absolutely sure on this. Any comments?

In my opinion, it shouldn't be an issue if it is possible by
configuration, but I may be totally wrong on this. I am not
going to use 2.6 Kernels for productive purposes right now.
I would recommend trying a pristine 2.4.25 Kernel from kernel.org first.
Center on booting an unmodified Kernel, then reconfigure, then patch.
>
By unmodified, do you mean no changes to .config, and compiling
with the default options?
No. I meant unpatched Kernel sources with sensible .config changes
reflecting your system's environment. I doubt the default options
will always result in a stable (or bootable) Kernel on most modern
machines.
I do disable everything I don't need. But, I need to
compile win4lin support as well as cmpci sound+modem driver and in
it's readme, they clearly say to compile it as a module.
In this case, better follow the readme.

Not possible in a monolithic kernel.
For me, it was the same thing with the latest QLogic Fibre Channel HBA
drivers. The Kernel driver kept throwing I/O errors, so I patched the
sources to use the one from QLogic, but that wouldn't run stable, too.
The module is fine now.
I am using monolithic kernels where possible; on all machines except
those with Fibre Channel connect, that is.
I do not know C or C++. I'm no programmer.
You don't need to have to. Compiling a Kernel requires no programming
skills. Albeit they may be helpful, though.
Problems arise when I get errors, and the errors are due to some
file syntax problem by the programmer or such. And if I don't have
net access, I get really stuck.
True. But I am stuck just a little bit further down the road, too. I can
read the source and understand what's going on, but in case of errors
most of the time the source is far too complex to fix them on my own.
In my experience the stable Kernel always compiles fine. It has proven
best not to use those third party drivers and add-ons that don't. Even
when I was able to fix some of the errors myself, I often experienced
stability problems afterwards. So I leave debugging to the Kernel hacker
community. But I tend to rather do without some functionality in favour
of a stable system anyway. YMMV.
After that, the image is installed with "dpkg -i ".
	This is the "debian way" of installing kernels isn't it?
Yes.

  I'd still
like to stick compiling kernels the generic way, except for
keeping my custom compiled kernels as debs for later.
You could do both. AFAIK kernel-package does not hinder you compiling a 
kernel the generic way. It just saves you the trouble building a Debian
package yourself.

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

Re: Kernel compile blues

[Kai Schindelka]

Roberto Sanchez wrote:
Also have a look at this excellent step-by-step HOWTO:

http://newbiedoc.sourceforge.net/system/kernel-pkg.html
Excellent, indeed. Thanks for the link!

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

Re: Kernel compile blues

[Jérémie Knuesel]

>First of all I'm right now stuck with apt-get not ready to install
>anything as per another post from me.
>
>This is what I get:
>
> E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily
> unavailable)
> E: Unable to lock the administration directory (/var/lib/dpkg/), is
> another process using it?
>
>Mind helping with this too? :)
Mmm quoting from 
http://www.debian.org/doc/manuals/apt-howto/ch-erros.en.html :

> If the error looked like:
>
>  E: Could not open lock file /var/lib/dpkg/lock - open (13 
Permission denied)
>  E: Unable to lock the administration directory (/var/lib/dpkg/), 
are you root?
>
> when trying any apt-get method other than source, you don't have root 
permission, that is, you're running as a normal user.
>
> There's an error similar to the above which happens when you run two 
copies of apt-get at the same time, or even if you try to run apt-get 
while a dpkg process is active. The only method that can be used 
simultaneously with others is the source method.

So it presumably comes from another process running (some 
dpkg/dselect/apt process)... See if you find one such process running in 
the background or something...
Is it a recurrent problem? (even after a reboot?)

>Thanks a lot for the links above. Don't we need to compile a
>kernel in the generic way before using kpkg?
Well I never compiled a kernel in the generic way :) I just switched 
from Windows to debian, and when I had to compile my first kernel, I 
asked google how to compile a kernel for debian and found the page
I gave you in my previous email. make-kpkg works really well for me. I 
guess it takes care of configuration problems by itself. To avoid 
module-related problems, I always compile my kernels with different 
--append-to-version strings (see make-kpkg manual). However, I recall 
having had a problem with initrd too, this was fixed with a line in 
lilo.conf, I can't remember... maybe "initrd=/boot/xxx" (I don't use 
initrd anymore).

Good luck,

Jeremie

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

Re: Kernel Compile Problems

[Brian Brazil]

On Sun, Feb 22, 2004 at 11:11:24AM -0500, Robert Tilley wrote:
> scripts/lxdialog/dialog.h:29:20: curses.h: No such file or directory

Install libncurses-dev. IIRC its one of the suggests for kernel-source-*

Brian


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

Re: Kernel compile blues

[Deboo]

On Sun, 22 Feb 2004, Jérémie Knuesel wrote:

> Try using kernel-package: I've compiled a lot of kernels without problem
> with it, just following the instructions on this page:
>
> http://newbiedoc.sourceforge.net/system/kernel-pkg.html
>
> Also, if you want to install a 2.6 kernel, make sure you have installed
> the module-init-tools package.
>
> Another site you may find helpful (never used but it seems comprehensive):
>
> http://www.osnews.com/story.php?news_id=2949


First of all I'm right now stuck with apt-get not ready to install
anything as per another post from me.

This is what I get:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily
unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is
another process using it?

Mind helping with this too? :)

Thanks a lot for the links above. Don't we need to compile a
kernel in the generic way before using kpkg?

Regards,
Deboo

--
---
Can someone, who causes pain to others,
experience real joy?
---


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

Re: Kernel compile blues

[Deboo]

On Sun, 22 Feb 2004, Kai Schindelka wrote:

> > VFS: Cannot open root device "" or 03:06
> > Kernel panic: VFS: Unable to mount root fs on 03:06
>
> Looks like the HA driver module the boot drive is attached to is missing
> in initrd. A misconfigured LILO may also be the cause.

HA driver module? What's that? mkinitrd doesn't give any error
while making initrd. And I use grub, not lilo. This is what I need
more info on - initrd. Anyway, is it good to compile 2.6 kernels
monolithic?


> I would recommend trying a pristine 2.4.25 Kernel from kernel.org first.
> Patches can always be applied later. Then rebuild. Center on booting an
> unmodified Kernel, then reconfigure, then patch. Better to start with
> the least complex option, I guess. Always keep working Kernel packages
> as a backup.

By unmodified, do you mean no changes to .config, and compiling
with the default options?


> For the same reason I'd start with a static Kernel. Apart from being
> more secure, it is easier to build. And disable everything you don't
> absolutely need to get the machine up and running. Bells and whistles
> can always be added later. Switch to modules when the static Kernel
> runs stable.

I do disable everything I don't need. But, I need to
compile win4lin support as well as cmpci sound+modem driver and in
it's readme, they clearly say to compile it as a module. Not
possible in a monolithic kernel. Or it could be plex86 if that
works. I've been able to compile the plex86 but didn't do anything
after that.


> > I do not know C or C++. I'm no programmer.
>
> You don't need to have to. Compiling a Kernel requires no programming
> skills. Albeit they may be helpful, though.

Problems arise when I get errors, and the errors are due to some
file syntax problem by the programmer or such. And if I don't have
net access, I get really stuck.

> Have a look at the packages build-essential and kernel-package.
> The following works for me on a Debian stable:
>
> After that, the image is installed with "dpkg -i ".

This is the "debian way" of installing kernels isn't it? I'd still
like to stick compiling kernels the generic way, except for
keeping my custom compiled kernels as debs for later.



--
---
Can someone, who causes pain to others,
experience real joy?
---


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

Re: Kernel compile blues

[Jérémie Knuesel]

Try using kernel-package: I've compiled a lot of kernels without problem 
with it, just following the instructions on this page:

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

Also, if you want to install a 2.6 kernel, make sure you have installed 
the module-init-tools package.

Another site you may find helpful (never used but it seems comprehensive):

http://www.osnews.com/story.php?news_id=2949

Yours,

Jeremie Knuesel

Deboo wrote:
I'm using debian woody. Been compiling kernels since quite many years on
Slack, RH and Mandrake. It's very few times I have completely been
successful booting with the compiled kernel in debian (Have used sarge
too).
Past few days I have been sitting just compiling and re-compiling various
kernels, all except 2.4.18 have failed to boot. Some don't compile and
give errors, others mostly have a problem with initrd image anf get stuck
saying
VFS: Cannot open root device "" or 03:06
Kernel panic: VFS: Unable to mount root fs on 03:06
I've compiled morre than four 2.4.x kernels, one 2.6.0 and three 2.2.x
kernels, some with and without patches too, these last few days I've been
compiling. I'm not concluding anything but really wondering how people
really compile.
I do not know C or C++. I'm no programmer. Most of the time compiling
fails due to some error in some .c file which I cannot know how to do. At
other times, it's something else like modules. Yes, I've been able to do
monolithic kernels and able to boot without problems with them I would
say. But the modular ones, hardly 2 - 3 times.
I'll list the steps I use for compiling (what am I missing?)
[...]


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

Re: Kernel compile blues

[Deboo]

On Sat, 21 Feb 2004, Roberto Sanchez wrote:

> Kai Schindelka wrote:
> > Have a look at the packages build-essential and kernel-package.
> > The following works for me on a Debian stable:
> >
> > cd /usr/src/linux/
> > make menuconfig
> > make-kpkg clean
> > make-kpkg --revision  --append_to_version - \
> > kernel-image
> > cd ..
> >
> > After that, the image is installed with "dpkg -i ".
> >
>
> Also have a look at this excellent step-by-step HOWTO:
>
> http://newbiedoc.sourceforge.net/system/kernel-pkg.html


Thanks for this link and the info. Well, I had thought to use kpkg but I
should first be able to install and boot using the kernel compiled in the
generic way, isn't it? That's what has been happening. I'll do a
monolithic kernel now I guess. But I _need_ modular kernel for some things
I have, like cmpci sound card+modem driver and more. A patched one on
that.


--
---
Can someone, who causes pain to others,
experience real joy?
---


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

Re: Kernel compile blues

[Roberto Sanchez]

Kai Schindelka wrote:
Deboo wrote:

I'm using debian woody. Been compiling kernels since quite many years on
Slack, RH and Mandrake. It's very few times I have completely been
successful booting with the compiled kernel in debian (Have used sarge
too).

Have a look at the packages build-essential and kernel-package.
The following works for me on a Debian stable:
cd /usr/src/linux/
make menuconfig
make-kpkg clean
make-kpkg --revision  --append_to_version - \
kernel-image
cd ..
After that, the image is installed with "dpkg -i ".

Also have a look at this excellent step-by-step HOWTO:

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

-Roberto


signature.asc
Description: OpenPGP digital signature

Re: Kernel compile blues

[Kai Schindelka]

Deboo wrote:
I'm using debian woody. Been compiling kernels since quite many years on
Slack, RH and Mandrake. It's very few times I have completely been
successful booting with the compiled kernel in debian (Have used sarge
too).
Past few days I have been sitting just compiling and re-compiling various
kernels, all except 2.4.18 have failed to boot. Some don't compile and
give errors, others mostly have a problem with initrd image anf get stuck
saying
VFS: Cannot open root device "" or 03:06
Kernel panic: VFS: Unable to mount root fs on 03:06
Looks like the HA driver module the boot drive is attached to is missing
in initrd. A misconfigured LILO may also be the cause.
I've compiled morre than four 2.4.x kernels, one 2.6.0 and three 2.2.x
kernels, some with and without patches too, these last few days I've been
compiling. I'm not concluding anything but really wondering how people
really compile.
I would recommend trying a pristine 2.4.25 Kernel from kernel.org first.
Patches can always be applied later. Then rebuild. Center on booting an
unmodified Kernel, then reconfigure, then patch. Better to start with
the least complex option, I guess. Always keep working Kernel packages
as a backup.
For the same reason I'd start with a static Kernel. Apart from being
more secure, it is easier to build. And disable everything you don't
absolutely need to get the machine up and running. Bells and whistles
can always be added later. Switch to modules when the static Kernel
runs stable.
I do not know C or C++. I'm no programmer.
You don't need to have to. Compiling a Kernel requires no programming
skills. Albeit they may be helpful, though.
There's only one time I was successful in making initrd work in 2.4.18, in
others I just could not. What am I doing wrong? I'm nearly tired of
compiling but I can't do without linux and I have read the howtos and
other docs many times. Wierd for me.
Have a look at the packages build-essential and kernel-package.
The following works for me on a Debian stable:
cd /usr/src/linux/
make menuconfig
make-kpkg clean
make-kpkg --revision  --append_to_version - \
kernel-image
cd ..
After that, the image is installed with "dpkg -i ".

Good luck!

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

Re: kernel compile error

[Florian Sukup]

> I had this, but no Modules (like I siad before). I tried to Compile 
> 2.4.22 from kernel.org and get now the same Errors.
> It's confusing, I remove the directory, decompress it again, do an 
> make oldconfig && make dep && make and get the same Error on another 
> file. The Error is sometimes here and sometimes anywhere. Now I try 
> to do a module an all that I don't really need to be compiled in.
> Seems that we have to try until it works, because noone seems to care 
> on this Thread or Problem. You and I not counted :-).

As far as I can remember, I couldn't run the 2.4.20 kernel image on that
computer. It hangs somewhere at disk checking (not fs, before that).
Same with the Knoppix CD, which also uses that kernel.

This is an old computer where I have a 120 and 60 GB disk in. If I enter
the bios setup and I go to the disk page, the bios cannot recognize the
disk and hangs. Nevertheless the woody CD could be started and
installed.

So maybe it has something to do with the bios setup.

I have to check the exact error messages. Maybe someone else on this
list gets an idea what could be wrong. The problem is, that this
computer is not local. So, I have to get there to do this. I should do
this soon.

How old is your computer? Similar situation?

Florian.


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

Re: kernel compile error

[Werner Mahr]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Mittwoch, 17. September 2003 17:00 schrieb Florian Sukup:

> Is that what you mean? It's y at my configuration. But it does
> compile correctly. Any other ideas?

I had this, but no Modules (like I siad before). I tried to Compile 
2.4.22 from kernel.org and get now the same Errors.
It's confusing, I remove the directory, decompress it again, do an 
make oldconfig && make dep && make and get the same Error on another 
file. The Error is sometimes here and sometimes anywhere. Now I try 
to do a module an all that I don't really need to be compiled in.
Seems that we have to try until it works, because noone seems to care 
on this Thread or Problem. You and I not counted :-).

- -- 
MfG usw

Werner Mahr

GPG-Key-ID 9CCBC2B0
Registered-Linux-User: 303822 (http://counter.li.org)
ICQ-Nr. 317910541
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/aH85OUGIhpzLwrARAi/eAKCu0fURGbVP27Lz/mKE1utZdf5gKQCcCG8P
8qgzUO1HrrVfLiInrJNBrCY=
=A2fA
-END PGP SIGNATURE-


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

Re: kernel compile error

[Florian Sukup]

On Tue, Sep 16, 2003 at 04:44:57PM +0200, Werner Mahr wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Am Dienstag, 16. September 2003 16:13 schrieb Florian Sukup:
> > What do you mean with 'Kernelconfig'? Is it
> > /usr/src/kernel-source-2.4.20/.config? Or a tool which I don't
> > know?
> I mean .config, sorry.

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

Is that what you mean? It's y at my configuration. But it does compile
correctly. Any other ideas?


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

Re: kernel compile error

[Werner Mahr]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Dienstag, 16. September 2003 16:13 schrieb Florian Sukup:
> What do you mean with 'Kernelconfig'? Is it
> /usr/src/kernel-source-2.4.20/.config? Or a tool which I don't
> know?
I mean .config, sorry.
- -- 
MfG usw

Werner Mahr

GPG-Key-ID 9CCBC2B0
Registered-Linux-User: 303822 (http://counter.li.org)
ICQ-Nr. 317910541
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/ZyHsOUGIhpzLwrARAk3vAJ91wj2DAObM52xZAtDs2dRDXnbcAQCeM/3b
tfPtRSyTjBM1LxVVZiImbJI=
=lqoo
-END PGP SIGNATURE-


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

Re: kernel compile error

[Florian Sukup]

Thank you for your reply.

> 
> I had the same Problem when I tried to compile my Kernel. I had in 
> Kernelconfig no Modules configured, moduleloader was included (nvidia 
> etc.). 2 Minutes before I got your Mail I tried it with Modules and 
> it worked. I don't know if this was the Error but its the only thing 
> I changed. 

What do you mean with 'Kernelconfig'? Is it
/usr/src/kernel-source-2.4.20/.config? Or a tool which I don't know?

> Maybe you have not gcc-2.95, I had a newer one and deinstalled it, 
> but I don't know if I tried it after that before today.

I have gcc 2.95.4-14 installed

Thanks in advance further info.

Florian.


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

Re: kernel compile error

[Werner Mahr]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Dienstag, 16. September 2003 14:16 schrieb Florian Sukup:

[Many things with many output]

I had the same Problem when I tried to compile my Kernel. I had in 
Kernelconfig no Modules configured, moduleloader was included (nvidia 
etc.). 2 Minutes before I got your Mail I tried it with Modules and 
it worked. I don't know if this was the Error but its the only thing 
I changed. 
Maybe you have not gcc-2.95, I had a newer one and deinstalled it, 
but I don't know if I tried it after that before today.

- -- 
MfG usw

Werner Mahr

GPG-Key-ID 9CCBC2B0
Registered-Linux-User: 303822 (http://counter.li.org)
ICQ-Nr. 317910541
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/Zwx0OUGIhpzLwrARAp2nAJ9gxClrLAPQjH20XzepdVyg90IdgwCfffU+
A2NCXaI1ZDqFox0sJ4FA26U=
=T3Hs
-END PGP SIGNATURE-


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

RE: kernel compile issues

[Joyce, Matthew]

> > I can boot with the OldLinux ok, are there any logs I should be 
> > looking at ? ...checking the config (menuconfig), I cannot see 
> > anything which might cause this behavior, if any thing it's 
> a pretty 
> > light build.
> 
> Did you (if necessary) change the LILO-configuration file and 
> run "lilo" as root (or the equivalent to these steps, if you 
> use GRUB)?
> 
> C.
> 
> -- 
> Christian Schoeller {Schueler} | "Eine weltweite Geschenkverteilung

Yes, I'm sure lilo was ran after 'dkpg -i'

Thanks

mj



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

Re: kernel compile issues

[Christian Schoeller]

On Mon, Sep 01, 2003 at 09:24:59AM +1000, Joyce, Matthew wrote:
> I can boot with the OldLinux ok, are there any logs I should be looking at ?
> ...checking the config (menuconfig), I cannot see anything which might cause
> this behavior, if any thing it's a pretty light build.

Did you (if necessary) change the LILO-configuration file and run
"lilo" as root (or the equivalent to these steps, if you use GRUB)?

C.

-- 
Christian Schoeller {Schueler} | "Eine weltweite Geschenkverteilung
MAIL {mailto:[EMAIL PROTECTED]| wuerde jede Zivilisation unmoeglich
HTTP {http://www.yaup.at.tt}   | machen." --aus: "Kapitalismus und
EBAY {c_p_s!}  | Freiheit" von Milton Friedman 

pgp0.pgp
Description: PGP signature

Re: Kernel compile error with make-kpkg

[Chris Metzler]

On Sat, 12 Jul 2003 17:15:13 +0200
"Esben Laursen" <[EMAIL PROTECTED]> wrote:
>
[ past traffic trimmed ]
> 
> The funny part is that if I do a "make dep && make && make modules"
> there is no error message and it compile correct. why is that?

Read your original error messages again.  You're not running into
compile problems; you're running into problems with depmod.  It
*compiled* correctly for you under make-kpkg, just as it does for
you with "make dep && make && make modules".  But make-kpkg does
more than just those things; it also verifies that your module set
will work through depmod, and in your case it runs into trouble.
If after "make dep && make && make modules" you tried to *install
and run* that kernel/module set, you'd have run into the same
trouble, I'd bet.  Right about when it ran depmod in order to
build the dependency file for modprobe to use.

So what about all the rest of the stuff I typed; was it helpful?

-c


-- 
Chris Metzler   [EMAIL PROTECTED]
(remove "snip-me." to email)

"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear


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

Re: Kernel compile error with make-kpkg

[Kevin McKinley]

On Sat, 12 Jul 2003 17:15:13 +0200
"Esben Laursen" <[EMAIL PROTECTED]> wrote:

Please trim replies.

> The funny part is that if I do a "make dep && make && make modules" there
> is no error message and it compile correct. why is that?
> 
> Could it be possible that I are missing some kind of lib to the
> kernel-package where make-kpkg is in??

How do you know it compiles correctly?

Have you installed and run the kernel that results?

make-kpkg is a script; it requires no libraries so that's not the issue.

Kevin


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

Re: Kernel compile error with make-kpkg

[Kevin McKinley]

On Sat, 12 Jul 2003 13:39:35 +0200
"JZidar" <[EMAIL PROTECTED]> wrote:

> Isn't the correct syntax something like:
> make-kpkg --append-to-version=.something kernel_image (note the = and .)?

The period isn't required; I used it to separate the kernel version from the
rest of the append-to-version value.

I thought the = was required but apparently it isn't. Many people report
using "--append-to-version " and it works.

Kevin


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

Re: Kernel compile error with make-kpkg

[Esben Laursen]

- Original Message - 
From: "Chris Metzler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Esben Laursen" <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 3:18 PM
Subject: Re: Kernel compile error with make-kpkg


> On Sat, 12 Jul 2003 13:08:39 +0200
> "Esben Laursen" <[EMAIL PROTECTED]> wrote:
> > From: "Chris Metzler" <[EMAIL PROTECTED]>
> > >On Fri, 11 Jul 2003 23:50:06 +0200
> > >"Esben Laursen" <[EMAIL PROTECTED]> wrote:
> >>> 
> >>> Here is the error I get:
> >>> 
> >>> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> >>> mkdir -p pcmcia; \
> >>> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf
> >>> ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F
> >>> System.map -b/usr/src/linux/debian/tmp-image -r 2.4.21-test; fi
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ media/radio/miropcm20.o depmod:
> >>> aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6
> >>> depmod: aci_version_Rsmp_93350c87
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ net/wan/comx.o depmod: proc_get_inode
> >>> make[2]: *** [_modinst_post] Error 1
> >>> make[2]: Leaving directory `/usr/src/linux-2.4.21'
> >>> make[1]: *** [real_stamp_image] Error 2
> >>> make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >>> 
> >>> Can anyone help me with what's wrong??
> >> 
> >> You need to provide more information than you've given.  Specifically,
> >> what version of gcc did you use (the output of linux/scripts/ver_linux
> >> would provide lots of info, but the gcc version you're using is
> >> probably enough).  Also, and especially, what architecture are you on,
> >> and did you specify that architecture in your kernel config?
> > 
> > Here is the output from a gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> > gcc version 2.95.4 20011002 (Debian prerelease)
> > 
> > Im trying to compile a kernel with support for the PII CPU, and my
> > kernel now is a standart Debain kernel-image-2.4.18-bf2.4 with the 386
> > architecture. Im also importing the /boot/config-2.4.18-bf2.4 from the
> > "make menuconfig" so that I get all the things I need and only have to
> > change a few things like the architecture. I've attached the
> > /usr/src/linux/scripts/var_linux file so you can see it.
> 
> Heh, OK, but as I wrote above, what I was interested in was the *output*
> from var_linux, not the contents of the script itself.  But you gave me
> the most important thing that output would have told me, which was your
> gcc version.
> 
> The reason I was interested in gcc version is because there have been
> numerous and various problems lately compiling kernels with gcc 3.3.
> In some cases, for reasons I don't understand and other people here
> probably do, this has resulted in unresolved symbols issues, akin to
> what you ran into (mistakes in parsing the text of files, maybe?).  But
> no probs have been reported with 2.95 -- in fact, that's what most
> people who've experienced problems with 3.3 have dropped back to -- and
> 2.95 is what you're using.  So that probably isn't it.
> 
> I was also curious about architecture because I was wondering if you
> were trying to make a kernel for an architecture other than x86.  The
> reason:  the errors you're getting are for drivers for some old ISA
> bus hardware from the mid-90's; and in Googling, I found instances of
> people getting errors like this when compiling on architectures that
> didn't even support the ISA bus in the first place.  But, you're
> compiling for a PII, so that isn't it either.
> 
> In the meantime, though, until someone with more clue than I jumps
> in, the below may help.
> 
> The first error:
> 
> } depmod: *** Unresolved symbols in 
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/media/radio/miropcm20.o
> } depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> } depmod: aci_port_Rsmp_0d82adb6
> } depmod: aci_version_Rsmp_93350c87
> 
> This is coming from miropcm20.o, which is the driver for the MiroSOUND
> PCM20 radio card.  Do you need that driver?  If not, you could turn it
> off, and

Re: Kernel compile error with make-kpkg

[Chris Metzler]

On Sat, 12 Jul 2003 13:08:39 +0200
"Esben Laursen" <[EMAIL PROTECTED]> wrote:
> From: "Chris Metzler" <[EMAIL PROTECTED]>
> >On Fri, 11 Jul 2003 23:50:06 +0200
> >"Esben Laursen" <[EMAIL PROTECTED]> wrote:
>>> 
>>> Here is the error I get:
>>> 
>>> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
>>> mkdir -p pcmcia; \
>>> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf
>>> ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F
>>> System.map -b/usr/src/linux/debian/tmp-image -r 2.4.21-test; fi
>>> depmod: *** Unresolved symbols in
>>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
>>> ers/ media/radio/miropcm20.o depmod:
>>> aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6
>>> depmod: aci_version_Rsmp_93350c87
>>> depmod: *** Unresolved symbols in
>>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
>>> ers/ net/wan/comx.o depmod: proc_get_inode
>>> make[2]: *** [_modinst_post] Error 1
>>> make[2]: Leaving directory `/usr/src/linux-2.4.21'
>>> make[1]: *** [real_stamp_image] Error 2
>>> make[1]: Leaving directory `/usr/src/linux-2.4.21'
>>> 
>>> Can anyone help me with what's wrong??
>> 
>> You need to provide more information than you've given.  Specifically,
>> what version of gcc did you use (the output of linux/scripts/ver_linux
>> would provide lots of info, but the gcc version you're using is
>> probably enough).  Also, and especially, what architecture are you on,
>> and did you specify that architecture in your kernel config?
> 
> Here is the output from a gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> gcc version 2.95.4 20011002 (Debian prerelease)
> 
> Im trying to compile a kernel with support for the PII CPU, and my
> kernel now is a standart Debain kernel-image-2.4.18-bf2.4 with the 386
> architecture. Im also importing the /boot/config-2.4.18-bf2.4 from the
> "make menuconfig" so that I get all the things I need and only have to
> change a few things like the architecture. I've attached the
> /usr/src/linux/scripts/var_linux file so you can see it.

Heh, OK, but as I wrote above, what I was interested in was the *output*
from var_linux, not the contents of the script itself.  But you gave me
the most important thing that output would have told me, which was your
gcc version.

The reason I was interested in gcc version is because there have been
numerous and various problems lately compiling kernels with gcc 3.3.
In some cases, for reasons I don't understand and other people here
probably do, this has resulted in unresolved symbols issues, akin to
what you ran into (mistakes in parsing the text of files, maybe?).  But
no probs have been reported with 2.95 -- in fact, that's what most
people who've experienced problems with 3.3 have dropped back to -- and
2.95 is what you're using.  So that probably isn't it.

I was also curious about architecture because I was wondering if you
were trying to make a kernel for an architecture other than x86.  The
reason:  the errors you're getting are for drivers for some old ISA
bus hardware from the mid-90's; and in Googling, I found instances of
people getting errors like this when compiling on architectures that
didn't even support the ISA bus in the first place.  But, you're
compiling for a PII, so that isn't it either.

In the meantime, though, until someone with more clue than I jumps
in, the below may help.

The first error:

} depmod: *** Unresolved symbols in 
/usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/media/radio/miropcm20.o
} depmod: aci_rw_cmd_Rsmp_cc7c4cd8
} depmod: aci_port_Rsmp_0d82adb6
} depmod: aci_version_Rsmp_93350c87

This is coming from miropcm20.o, which is the driver for the MiroSOUND
PCM20 radio card.  Do you need that driver?  If not, you could turn it
off, and this problem may very well go away.  But in the meantime, when
I read about this driver in linux/Documentation/Configure.help, I see:

} miroSOUND PCM20 radio
} CONFIG_RADIO_MIROPCM20
}   Choose Y here if you have this FM radio card. You also need to say Y
}   to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound")
}   for this to work.

Note that last sentence.  The unresolved symbols you're getting are all
defined in linux/drivers/sound/aci.c or aci.h (hence the "aci_" prefix).
If you need support for this card (the MiroSOUND PCM20), then you also
need to turn on CONFIG_SOUND_ACI_MIXER under the sound section.  I'm
betting you don't have that turned on when you should, and that's the
reasons for these unresolved symbol messages.  If I'm right, then you
need to either have them both on, or both off, as per that last sentence
quoted above.

Incidentally, normally, there should be code in the miropcm20-radio.c
driver that prevents the compile of that driver if you haven't set the
config options it depends on (in this case, CONFIG_SOUND_ACI_MIXER); it
doesn't look like that code is t

Re: Kernel compile error with make-kpkg

[JZidar]

- Original Message -
From: "Esben Laursen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 1:08 PM
Subject: Re: Kernel compile error with make-kpkg



- Original Message -
From: "Chris Metzler" <[EMAIL PROTECTED]>
To: "Esben Laursen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 12:43 AM
Subject: Re: Kernel compile error with make-kpkg


> On Fri, 11 Jul 2003 23:50:06 +0200
> "Esben Laursen" <[EMAIL PROTECTED]> wrote:
> >
> > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
> > this error no matter what I try!! The command im useing is: make-kpkg
> > --append_to_version -test kernel-image
> >
> > I think it's when the package is being build there is an error, or am I
> > wrong?
> >
> > Here is the error I get:
> >
> > cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> > mkdir -p pcmcia; \
> > find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> > pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> > /usr/src/linux/debian/tmp-image -r 2.4.21-test; fi depmod: ***
> > Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > media/radio/miropcm20.o depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> > depmod: aci_port_Rsmp_0d82adb6
> > depmod: aci_version_Rsmp_93350c87
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > net/wan/comx.o depmod: proc_get_inode
> > make[2]: *** [_modinst_post] Error 1
> > make[2]: Leaving directory `/usr/src/linux-2.4.21'
> > make[1]: *** [real_stamp_image] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >
> > Can anyone help me with what's wrong??
>
> You need to provide more information than you've given.  Specifically,
> what version of gcc did you use (the output of linux/scripts/ver_linux
> would provide lots of info, but the gcc version you're using is probably
> enough).  Also, and especially, what architecture are you on, and did
> you specify that architecture in your kernel config?
>
> -c
>
> --
> Chris Metzler [EMAIL PROTECTED]
>
>Here is the output from a gcc -v
>Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
>gcc version 2.95.4 20011002 (Debian prerelease)
>
>Im trying to compile a kernel with support for the PII CPU, and my kernel
>now is a standart >Debain kernel-image-2.4.18-bf2.4 with the 386
>architecture.
>Im also importing the /boot/config-2.4.18-bf2.4 from the "make menuconfig"
>so that I get all the >things I need and only have to change a few things
>like the architecture.
>I've attached the /usr/src/linux/scripts/var_linux file so you can see it.

Isn't the correct syntax something like:
make-kpkg --append-to-version=.something kernel_image (note the = and .)?




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