From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: g3vbv@blueyonder.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-git10 make bzImage problem
Date: Fri, 19 Oct 2007 14:26:22 +0200 [thread overview]
Message-ID: <5a4c581d0710190526r735d175du346d43a0bd18c9fd@mail.gmail.com> (raw)
In-Reply-To: <4715481F.7060502@blueyonder.co.uk>
On 10/17/07, Sid Boyce <g3vbv@blueyonder.co.uk> wrote:
> When booted, it complains that kernel size is too big, but size OK for a
> bzImage, not for zImage as is returned by the file command, -git9 was
> OK, x86_64 SMP kernel on two 64x2 boxes.
> I shall supplymy .config if needed, but they are the same as for -git9.
>
> # l arch/x86/boot/bzImage
> -rw-r--r-- 1 root root 1761496 2007-10-16 22:45 arch/x86/boot/bzImage
>
> # file arch/x86_64/boot/bzImage
> arch/x86_64/boot/bzImage: symbolic link to
> `/usr/src/linux-2.6.23-git10/arch/x86/boot/bzImage'
>
> # file arch/x86/boot/bzImage
> arch/x86/boot/bzImage: Linux/x86 Kernel, Setup Version 0x206, zImage,
> RO-rootFS, root_dev 0x801, swap_dev 0x1, Prompt for Videomode
Same here - but it -git13 seems to be back to proper behavior...
[asuardi@sandman boot]$ file vmlinuz-2.6.23-git? vmlinuz-2.6.23-git??
vmlinuz-2.6.23-git3: Linux kernel x86 boot executable RO-rootFS,
root_dev 0x807, swap_dev 0x1, Normal VGA
vmlinuz-2.6.23-git6: Linux kernel x86 boot executable RO-rootFS,
root_dev 0x807, swap_dev 0x1, Normal VGA
vmlinuz-2.6.23-git10: Linux kernel x86 boot executable zImage, version
2.6.23-git10 (asuardi@sandman) , RO-rootFS, root_dev 0x807, swap_dev
0x1, Prompt for Videomode
vmlinuz-2.6.23-git13: Linux kernel x86 boot executable RO-rootFS,
root_dev 0x807, swap_dev 0x1, Normal VGA
--alessandro
"you feel the sweet breath of time
it's whispering, its truth not mine"
(Interpol, 'No I In Threesome')
prev parent reply other threads:[~2007-10-19 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 23:24 Sid Boyce
2007-10-17 0:09 ` Sid Boyce
2007-10-19 12:26 ` Alessandro Suardi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4c581d0710190526r735d175du346d43a0bd18c9fd@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®