hi,all
http://ertw.com/blog/archives/make_bzimage_vs_make_zimage-170404.html
someone tell me that the kernel made by 'make bzImage' is smaller then the one 'make
zImage' made it.
is it correct?
--
P4/2.4B
ELSA 528/128
512MB DDR333
240GB
MSI 845PE
BenQ FP557s
Pioneer DVD-120A
LG GCE-8320B
On Sun, 18 Jul 2004 16:07:26 +0800, cwinl [EMAIL PROTECTED] wrote:
hi,all
http://ertw.com/blog/archives/make_bzimage_vs_make_zimage-170404.html
someone tell me that the kernel made by 'make bzImage' is smaller then the one 'make
zImage' made it.
is it correct?
Interesting article. I
On Sun, 2004-07-18 at 04:07, cwinl wrote:
hi,all
http://ertw.com/blog/archives/make_bzimage_vs_make_zimage-170404.html
someone tell me that the kernel made by 'make bzImage' is smaller then
the one 'make zImage' made it.
is it correct?
No. zImage and bzImage use the same compression
el: Jueves, 07 de Marzo de 2002 06:56 p.m.
Para: k
CC: debian-user-spanish@lists.debian.org
Asunto: Re: Error en make zImage Kernel 2.4.18
El sector de arranque es de 512 bytes, y el kernel que estas compilando
es de 908 bytes, por lo que no cabe en el sector de arranque, lo que
puedes hacer es
El error es el siguiente:
Root device is (3,1)
Boot sector 512 bytes
Setup is 2510 bytes
System is 908 kB
System is too big. Try using bzImage or modules.
make[1]: *** [zImage] Error 1
make[1]: Leaving directory '/usr/srv/linux/arch/i386/boot'
Make: *** [zImage] Error 2
Alguna idea de que paso
k ha escrito:
El error es el siguiente:
Root device is (3,1)
Boot sector 512 bytes
Setup is 2510 bytes
System is 908 kB
System is too big. Try using bzImage or modules.
make[1]: *** [zImage] Error 1
make[1]: Leaving directory '/usr/srv/linux/arch/i386/boot'
Make: *** [zImage] Error 2
make bzImage
make[1]: *** [zImage] Error 1
make[1]: Leaving directory '/usr/srv/linux/arch/i386/boot'
Make: *** [zImage] Error 2
Alguna idea de que paso?
Esto tiene rollback aun despues de un make dep?
Rollback? Para que?
Salu2,
--
Roberto
El sector de arranque es de 512 bytes, y el kernel que estas compilando es de
908 bytes, por lo que no cabe en el sector de arranque, lo que puedes hacer es
compilar lo que se pueda como módulos, con esto reduces el tamaño, o, en lugar
de teclar 'make zImage', teclea 'make bzImage'. Saludos
siguiente:
Root device is (3,1)
Boot sector 512 bytes
Setup is 2510 bytes
System is 908 kB
System is too big. Try using bzImage or modules.
make[1]: *** [zImage] Error 1
make[1]: Leaving directory '/usr/srv/linux/arch/i386/boot'
Make: *** [zImage] Error 2
Alguna idea de que paso?
Esto tiene
Johannes Franken [EMAIL PROTECTED] wrote:
On Mon, Feb 25, 2002 at 05:17:38PM +0100, Martin Klaiber wrote:
Hm, dann brauche ich aber immer noch die ganzen Installationsskripte.
Die hast Du ja auf CD. Sobald Du den Kernel gebootet und eine Shell
erhalten hast (z,B. mit der zdisk), mounte das
Martin Klaiber [EMAIL PROTECTED] wrote:
Aber da die libc6 über das security-update schon in der neuen Version
vorhanden ist, gibt's doch dauernd Probleme mit Abhängigkeiten, wenn
man eines der devel-Pakete installieren will.
Grmpf. Ich hatte vergessen auch in dselect die Paketliste zu
On Mon, Feb 25, 2002 at 05:17:38PM +0100, Martin Klaiber wrote:
Ich bräuchte also Installationsdisketten mit einem zImage-Kernel.
Kann mir jemand Tips geben, wie ich mir solche Disketten machen kann?
Mit zdisk kannst Du ein minimales root-filesystem (als .tgz) plus
einen selbstgebackenen
i386, vor einiger Zeit Upgrade von Potato auf Woody gemacht. Zur Zeit
läuft noch 2.2.17
Zunächst beginnt's mit Warnungen:
z.B. warning: '.' redefined
/usr/src/kernel-source-2.4.17/include/linux/modules/i386_ksyms.ver:86:
warning:
this is the location of the previous
- Original Message -
From: Gerhard Reuteler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, February 16, 2002 11:53 AM
Subject: kernel-source-2.4.17 make zImage Fehler
i386, vor einiger Zeit Upgrade von Potato auf Woody gemacht. Zur Zeit
läuft noch 2.2.17
Zunächst beginnt's
Hi,
I'm running debian unstable, and all of a sudden I can't compile a kernel.
The actual compilation seems to go ok (and leaves a vmlinux in the root of
the kernel source tree), but when trynig to make a zImage or bzImage I get
the error:
ld -m elf_i386 -Ttext 0x1000 -e startup_32 -o vmlinux
make head or tail of
it. (maybe I should read another 10 more times?) Thank you. This is because I
want to do a make zImage. My laptop can't stand a bzImage. Or can the
kernel-package make a zImage kernel??
regards,
joey
--
___
Get your free email from
Hi,
I have found the steps to making a new kernel. If I have a kernel-source.deb
file, can I just do a make zImage supposing I have just installed debian with a
bzImage?
regards,
joey
-Original Message-
From: Joey Kool [EMAIL PROTECTED]
Date: Mon, 07 Aug 2000 15:08:44 +0800
On 7, aug, 2000 at 04:08:00 +0800, Joey Kool wrote:
Hi,
I have found the steps to making a new kernel. If I have a
kernel-source.deb file, can I just do a make zImage supposing I have just
installed debian with a bzImage?
Yes!
regards,
joey
-Original Message-
From
Now, you say you _have_to_ have a zImage, so you just have to compile
all that you can as modules, and only have the bare essentials that you
need _in_ the kernel, untill you partitions are mounted and you can
load the modules.
I heard that the zImage support is going to be removed from
-Original Message-
From: Morten Liebach [EMAIL PROTECTED]
Date: Mon, 7 Aug 2000 10:34:44 +0200
To: debian-user@lists.debian.org
Subject: Re: how to make a zImage
Hi,
Thanks. The book is Debian GNU/Linux Unleashed with a CD containing the
binaries for slink. It has a chapter
On 09 Jun 2000, Bolan Meek wrote:
[snip]
I don't think you're supposed to `make clean` after `make dep`:
you'll be removing some of the work done by `make menuconfig`
and `make dep`. I always go straight to `make zImage` or bzImage`
after `make dep`.
[snip]
According to Welsh and Kaufman
adam.edgar wrote:
I have run into a bit of a problem when compiling the test kernel
under potato. When I make zImage it runs all the way to the end and then
crashes after reporting that the system is to large.
In that case, use `make bzImage`. It uses bzip2, if I'm not mistaken,
so
I have run into a bit of a problem when compiling the test kernel
under potato. When I make zImage it runs all the way to the end and then
crashes after reporting that the system is to large. Yet the size it
reports is actualy smaller than that of the current kernel (The default
for potato
on kernel 2.0.36.
2. downloaded linux-2.2.14.tar.gz (from
http://www.kernel.org) to /usr/src.
3. as root and from /usr/src, i ran tar xvzf
lin*.tar.gz
4. cd to /usr/src/linux
5. ran make mrproper
6. ran make config
7. configured the kernel
8. ran make zImage
9. tried to find the newly
I'm sure someone here can tell you exactly where it is. I would guess
somewhere in the directory where you unpacked the source code. A couple
of ways you could find it is use the 'find' command or 'updatedb' and
then use 'locate zImage'
hth,
kent
cls--colo spgs wrote:
debs,
i'm working
I never made a zImage, I guess you should make a bzImage (it's
smaller), but if you want to find it just go to /usr/src/linux and type
find . | grep Image
By the way a bzImage always resides in $SRCDIR/arch/i386/boot/
Ron Rademaker
PS. Don't forget to make and install your modules! (make
/usr/src, i ran tar xvzf
lin*.tar.gz
4. cd to /usr/src/linux
5. ran make mrproper
6. ran make config
7. configured the kernel
8. ran make zImage
9. tried to find the newly recompiled kernel
(zimage?/linux?) in /usr/src/linux/arch/i386/boot. all
that's there is: makefile
You're looking in the right place (/usr/src/linux/arch/i386/boot) for the
zImage file. If it's not there, your description is missing some detail
that, if we know it, would explain what happened. A couple of possibilities:
1. You never mention actually making the symlink ln -s
/usr/src/linux
cls--colo spgs [EMAIL PROTECTED] writes:
cls i'm working on my first kernel recompile. i'm at the
cls point where i need to move the recompiled kernel to the
cls to boot location. unfortunately, i cannot find the
cls recompiled kernel.
Since nobody seems to have suggested it yet, why don't you
Hola
Enzo A. Dari escribió:
A propósito, el Contents-i386 no debería venir también en los
CD's? En los mios no está (Official Debian de Linux Central).
En la Debian 2.0 de Linux Actual si que viene.
--
Deica logo
Hola amigos voay avanzando.
Pero ahora me ocurre que al ejecutar make zImage despues de make
menuconfig me da un error que es
as86 -o - a -o bootsect.o bootsect.s
make[1] as86: Command not found
make[1]: ***[bootsect.o] Error 127
Con lo cual me he quedado parado pues necesito compilar el Kernel
hola a la lista, es el primer mensaje que envio y creo que responde a
una pregunta, despues de este ya preguntare yo :-))
lo del make zImage yo diria que no tienes instalado el paquete de
ensamblador, a mi tambien me paso eso.
hasta pronto
Hola amigos voay avanzando.
Pero ahora me ocurre que
as86 está en un paquete que se llama bin86 y creo que está en la seccion
main/devel.
-Mensaje original-
De: José Valcarce Alonso [mailto:[EMAIL PROTECTED]
Enviado el: miércoles 20 de enero de 1999 9:13
Para: debian-user-spanish@lists.debian.org
Asunto: make zImage
Hola amigos voay
Yo, después de hacer make menuconfig, ejecuto make dep, después make
clean y después make zImage.
No sé si será este el problema.
Saludos
On Wed, Jan 20, 1999 at 04:47:20AM +0100, Antonio Angel Sanz Arróspide wrote:
Yo, después de hacer make menuconfig, ejecuto make dep, después make
clean y después make zImage.
Pista: El paquete kernel-package es vuestro mejor amigo.
--
Enrique Zanardi
On Wed, 20 Jan 1999, Antonio Angel Sanz Arróspide wrote:
Yo, después de hacer make menuconfig, ejecuto make dep, después make
clean y después make zImage.
No sé si será este el problema.
Saludos
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
On Wed, Jan 20, 1999 at 11:29:09AM +, Melkor wrote:
Ah, has hecho los enlaces de /usr/src/linux/include/linux.h asm.h
scsi.h a /usr/include/linux.h asm.h scsi.h ? Es importante hacerlo antes
de ponerse a compilar.
¡¡¡NO!!! Con Debian eso es totalmente innecesario. Lo de los enlaces es
Enrique Zanardi wrote:
On Wed, Jan 20, 1999 at 11:29:09AM +, Melkor wrote:
Ah, has hecho los enlaces de /usr/src/linux/include/linux.h asm.h
scsi.h a /usr/include/linux.h asm.h scsi.h ? Es importante hacerlo antes
de ponerse a compilar.
¡¡¡NO!!! Con Debian eso es totalmente
On Wed, 20 Jan 1999, Enrique Zanardi wrote:
On Wed, Jan 20, 1999 at 11:29:09AM +, Melkor wrote:
Ah, has hecho los enlaces de /usr/src/linux/include/linux.h asm.h
scsi.h a /usr/include/linux.h asm.h scsi.h ? Es importante hacerlo antes
de ponerse a compilar.
¡¡¡NO!!! Con Debian
On Wed, Jan 20, 1999 at 12:47:11PM +, Melkor wrote:
alguna alma caritativa dispone de un compilador Pascal decente? (para
linux, naturalmente). Se lo pagare en bendiciones.
No estoy seguro de si es decente ;-) pero exite el gpc (GNU Pascal
Compiler). Del paquete gpc para Debian:
José Valcarce Alonso wrote:
Hola amigos voay avanzando.
Pero ahora me ocurre que al ejecutar make zImage despues de make
menuconfig me da un error que es
as86 -o - a -o bootsect.o bootsect.s
make[1] as86: Command not found
make[1]: ***[bootsect.o] Error 127
...
En los mirrors de debian
On Wed, 20 Jan 1999, David Charro Ripa wrote:
Enrique Zanardi wrote:
On Wed, Jan 20, 1999 at 11:29:09AM +, Melkor wrote:
Ah, has hecho los enlaces de /usr/src/linux/include/linux.h asm.h
scsi.h a /usr/include/linux.h asm.h scsi.h ? Es importante hacerlo antes
de ponerse a
On Sat, Oct 10, 1998 at 01:59:48PM +0100, Grzegorz Adam Hankiewicz wrote:
Ahora, a pesar de que todo funciona aparentemente bien y sin
problemas, sigo recibiendo unos mensajes de error o aviso al arrancar.
Esto es lo que me pone:
/dev/hdb2: clean, 31967/165888 files, 354098/661248 blocks
menuconfig ; make zImage y ahí casca.
Llega un momento en el que parece que debe ejecutar un comando y
no lo encuentra, y no lo he visto en el dselect. Este es el error exacto:
make[1]: Entering directory `/usr/src/kernel-source-2.0.34/arch/i386/boot'
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.34
Grzegorz Adam Hankiewicz [EMAIL PROTECTED] writes:
as86 -0 -a -o bootsect.o bootsect.s
make[1]: as86: Command not found
Instala el paquete bin86.
--
Jesús Rodrigo e-mail: [EMAIL PROTECTED]
, and
some other laptops can't boot from a bzImage.
There is a kernel patch however that lets me boot my tecra from a bzImage
It's small enough to include it for your convienience
The kernel I get from 'make zImage' fails in the same way.
Then it must be a different problem.
However, 'make
On Wed, Sep 02, 1998 at 02:21:42PM +0200, Nils Rennebarth wrote:
It's small enough to include it for your convienience
which I didn't do. Here it is
Nils
--
*-*
| Quotes from the net: L Linus Torvalds, W Winfried
'make zImage' fails in the same way.
However, 'make bzImage' gives me a kernel that is only ONE byte smaller
(340654 vs 340655).
The files themselves are quite different internally, but this made me
suspicious anyway.
I'm working with 2.0.34
I'd love to hear any other suggestions, particularly
On Fri, 6 Mar 1998, Ian Perry wrote:
Hi,
Can anyone please tell me the difference between the files vmliniz and
zImage ?
I recompiled the kernel-2.0.32 and the new vmlinux file in the linux
directory was 1087525 bytes
while the original kernel-2.0.32 vmlinux file was 675524 bytes
Hi,
Can anyone please tell me the difference between the files vmliniz and
zImage ?
I recompiled the kernel-2.0.32 and the new vmlinux file in the linux
directory was 1087525 bytes
while the original kernel-2.0.32 vmlinux file was 675524 bytes... quite a
difference.
the new zImage file
After executing the command make zImage, I cannot find zImage.
Here are the last 6 lines of screen output from make zImage. Is this
of any significance?
make[1]: Entering directory `/usr/src/kernel-source-2.0.30/arch/i386/boot'
as86 -0 -a -o bootsect.o bootsect.s
make[1]: as86: Command
David Densmore wrote:
After executing the command make zImage, I cannot find zImage.
Here are the last 6 lines of screen output from make zImage. Is this
of any significance?
make[1]: Entering directory
`/usr/src/kernel-source-2.0.30/arch/i386/boot'
as86 -0 -a -o bootsect.o bootsect.s
-a -o bootsect.o bootsect.s
make[1]: as86: Command not found
make[1]: *** [bootsect.o] Error 127
make[1]: Leaving directory
`/usr/src/kernel-source-2.0.30/arch/i386/boot'
make: *** [zImage] Error 2
Do I really need to recompile the kernel to get my sound card to
work?
it may
David Densmore wrote:
After executing the command make zImage, I cannot find zImage.
Here are the last 6 lines of screen output from make zImage. Is this
of any significance?
make[1]: Entering directory
`/usr/src/kernel-source-2.0.30/arch/i386/boot'
as86 -0 -a -o bootsect.o
54 matches
Mail list logo
