This bug was fixed in the package lilo - 1:23.2-1
---
lilo (1:23.2-1) unstable; urgency=medium
[ Joachim Wiedorn ]
* New upstream release:
- Fix for larger kernel setup code. (Closes: #625266)
- Update of manpages (mkrescue.8, lilo.conf.5).
* Update of some patches; remo
** Branch linked: lp:debian/lilo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/260059
Title:
lilo needs to warn if initrd is too large
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
With the new upstream version 23.1 this problem should be solved.
Have a nice day.
Joachim (Germany)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/260059
Title:
lilo needs to warn if initrd is too
Brian - do you know the status of this defect ? thnx
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Soren - it seems that there is a proposed fix in this bug report could
you possibly test it out?
** Changed in: lilo (Ubuntu)
Status: Confirmed => Triaged
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are
** Changed in: lilo (Ubuntu)
Status: New => Confirmed
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
The user Juan Sebastian Cobaleda Cano is a troll, or something. We, in
the Ubuntu-Co Team are checking all his changes in Launchpad. Sorry for
the problems.
** Changed in: lilo (Ubuntu)
Assignee: Juan Sebastian Cobaleda Cano (sebastiancobaleda) => (unassigned)
Status: Fix Released => N
I fail to understand your argumentation. If the supposed fix ("large-
memory") is in Lilo, how can this be a kernel problem?
"add a check to lilo that will tell the user that their initrd.img is
over a certain size and that they might want to add the "large-memory"
option to lilo.conf. This *defin
I just spent the better part of a day trying to find out why one of my
servers refused to boot any kernels newer than 2.6.24-17-server. After
countless hours of debugging, it turns out that the size of my
initrd.img's had grown ever so slightly, but it was just enough to push
it over a critical thr
** Changed in: lilo (Ubuntu)
Assignee: (unassigned) => cobaleda (sebastiancobaleda)
Status: New => Confirmed
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Oh bugger. I tried emailing John Coffman, the author of LILO, to get his
take on this (the previous comment), but the mail bounced.
It pretty much sums up my _suspicions_:
LILO has a heuristic to determine when the "large-memory" option is needed, but
it underestimates, leading to this edge case.
On Sat, Aug 23, 2008 at 08:10:51PM -, Mads Chr. Olesen wrote:
> Could you provide the size of the initrd image, gunzipped?
Oh, you think uncompressed size matters? Hm.. Perhaps.
[EMAIL PROTECTED]:~$ gzip -l /boot/initrd.img-2.6.24-{17,21}-server
compresseduncompressed ratio
Could you provide the size of the initrd image, gunzipped?
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
More correctly, it did not boot because of large-memory wasn't there in
lilo.
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I second this request, this bit me as well, my fresh install of ubuntu
server 8.04.1 amd64 did not install because the large-memory option was
not in lilo.conf.
Either put it there from start, or even better, provide a chance of
editing the generated lilo.conf during install before installing the
** Attachment added: "lilo.log"
http://launchpadlibrarian.net/17030785/lilo.log
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Attachment added: "lilo.conf"
http://launchpadlibrarian.net/17030778/lilo.conf
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Hmm, the issue doesn't seem as straightforward after all.
In lilo there is already a check for a too large initrd (boot.c, search
for FLAG_TOOBIG). I wonder why it wasn't triggered.
Could you attach your lilo.conf? And, if possible, the output of running
lilo with a couple of "-v" flags (and with
** Description changed:
-
I just spent the better part of a day trying to find out why one of my
servers refused to boot any kernels newer than 2.6.24-17-server. After
countless hours of debugging, it turns out that the size of my
initrd.img's had grown ever so slightly, but it was just e
** Attachment added: "Screenshot of the boot failure"
http://launchpadlibrarian.net/16981902/bootfail.png
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
20 matches
Mail list logo
