Bug#479101: Bug#479607: With lilo 22.8-5 still can't boot on macbookpro
On Mon, Jul 14, 2008 at 11:00:00PM +0200, Eugen Dedu wrote:
> reopen 479607
> thanks
>
> annonygmouse wrote:
>>
>> Hi folks I've seen bug 479607 has been closed with lilo version 22.8-5
>> but I still can't boot my machine with 2.6.25-2...
>>
>>
>> debianmbp:~# LANG=C aptitude show lilo
>> Package: lilo
>> State: installed
>> Automatically installed: no
>> Version: 1:22.8-5
>> Priority: optional
>> Section: admin
>> Maintainer: William Pitcock <nenolod@sacredspiral.co.uk>
>> Uncompressed Size: 1208k
>> Depends: mbr, debconf (>= 1.2.9) | debconf-2.0, libc6 (>= 2.7-1),
>> libdevmapper1.02.1 (>= 2:1.02.20)
>> Suggests: lilo-doc
>> Conflicts: manpages (< 1.29-3)
>> Description: LInux LOader - The Classic OS loader can load Linux and others
>> This package contains lilo (the installer) and boot-record-images to
>> install Linux, OS/2, DOS and generic Boot Sectors of other OSes.
>>
>> You can use LILO to manage your Master Boot Record (with a simple text
>> screen, text menu or colorful splash graphics) or call LILO from
>> other Boot-Loaders to jump-start the Linux kernel.
>>
>> Tags: admin::boot, interface::commandline, role::program, scope::utility
>>
>> debianmbp:~#
>>
>> Running lilo shows the following.
>>
>> debianmbp:~# lilo
>> Warning: LBA32 addressing assumed
>> Added Linux *
>> Added LinuxOLD
>> One warning was issued.
>> debianmbp:~#
>>
>>
>> Is this the warning saying that de 8MB barrier has been met? Because I
>> think this warning happened before...
>
> Hi,
>
> It seems to me that lilo does not show any warning for the image which
> does not work on my machine. In fact, as previously said, the image has
> less than 8MB:
>
> -rw-r--r-- 1 root root 6998498 2008-05-16 10:11 initrd.img-2.6.25-2-amd64
>
> I put a few days ago this image as the default one and run lilo: no
> warning was issued about the size, still rebooting the computer does not
> work.
>
> So I reopen this bug.
Lilo was fixed in version 1:22.8-6.4 onwards. Can you confirm that it resolves
the problem for you?
Cheers,
Moritz
Reply to: