Re: Help with debian-cd's UEFI boot on a Debian derivative

2014-07-09 Thread Steve McIntyre
On Wed, Jul 09, 2014 at 06:50:36PM +0200, Raphael Hertzog wrote:
>On Wed, 09 Jul 2014, Steve McIntyre wrote:
>> On Wed, Jul 09, 2014 at 12:22:50PM +0200, Raphael Hertzog wrote:
>> >So looking further into d-i changes related to this, I found this:
>> >http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84
>> >
>> >And the debian-installer images we generated thus have this change
>> >too. Is it possible that this change works with grub 2.0 but not
>> >1.99 of wheezy?
>> 
>> Ooh, maybe. It's *possible*, I'm not sure tbh. For Wheezy CD builds we
>> still use the Wheezy branch of debian-cd, so I've not tested that
>> combo.
>
>So I rebuilt d-i images with this commit reverted and then rebuilt
>my ISO image with the new d-i images, and the problem is gone.

Excellent!

>Thanks for your help!

No problem, glad you've got there. I didn't think I did much... :-)

>I double checked that the current Debian weekly build boots fine, in other
>word this change works well with grub 2, but not with grub 1.99.

ACK, thanks for that.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140709210028.gq18...@einval.com



Re: Help with debian-cd's UEFI boot on a Debian derivative

2014-07-09 Thread Raphael Hertzog
On Wed, 09 Jul 2014, Steve McIntyre wrote:
> On Wed, Jul 09, 2014 at 12:22:50PM +0200, Raphael Hertzog wrote:
> >So looking further into d-i changes related to this, I found this:
> >http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84
> >
> >And the debian-installer images we generated thus have this change
> >too. Is it possible that this change works with grub 2.0 but not
> >1.99 of wheezy?
> 
> Ooh, maybe. It's *possible*, I'm not sure tbh. For Wheezy CD builds we
> still use the Wheezy branch of debian-cd, so I've not tested that
> combo.

So I rebuilt d-i images with this commit reverted and then rebuilt
my ISO image with the new d-i images, and the problem is gone.

Thanks for your help!

I double checked that the current Debian weekly build boots fine, in other
word this change works well with grub 2, but not with grub 1.99.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140709165036.ga6...@x230-buxy.home.ouaza.com



Re: Help with debian-cd's UEFI boot on a Debian derivative

2014-07-09 Thread Steve McIntyre
On Wed, Jul 09, 2014 at 12:22:50PM +0200, Raphael Hertzog wrote:
>On Wed, 09 Jul 2014, Raphael Hertzog wrote:
>> We use the Debian grub package unchanged. What changed here is
>> that we have rebuilt debian-installer images which picked those
>> supplementary modules.
>
>So looking further into d-i changes related to this, I found this:
>http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84
>
>And the debian-installer images we generated thus have this change
>too. Is it possible that this change works with grub 2.0 but not
>1.99 of wheezy?

Ooh, maybe. It's *possible*, I'm not sure tbh. For Wheezy CD builds we
still use the Wheezy branch of debian-cd, so I've not tested that
combo.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140709104944.ga17...@einval.com



Re: Help with debian-cd's UEFI boot on a Debian derivative

2014-07-09 Thread Raphael Hertzog
On Wed, 09 Jul 2014, Raphael Hertzog wrote:
> We use the Debian grub package unchanged. What changed here is
> that we have rebuilt debian-installer images which picked those
> supplementary modules.

So looking further into d-i changes related to this, I found this:
http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=81109010691ee0fc9357bd10be8fe116b9bb9f84

And the debian-installer images we generated thus have this change
too. Is it possible that this change works with grub 2.0 but not
1.99 of wheezy?

/me feels that I'm getting closer to the root of the problem

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140709102250.gb27...@x230-buxy.home.ouaza.com



Re: Help with debian-cd's UEFI boot on a Debian derivative

2014-07-09 Thread Raphael Hertzog
On Tue, 08 Jul 2014, Steve McIntyre wrote:
> >And I build the image with "make official_images". The build seems to work 
> >fine
> >but the resulting image doesn't boot with UEFI. I get a grub screen but
> >whenever I select an entry, grub tells me:
> >> error: unknown command `linux'.
> >> error: unknown command `initrd'.
> >>
> >> Press any key to continue...
> 
> That suggests a problem in the grub search path for loading modules, maybe?

Possibly, but where is that search path defined?

I didn't find any reference to something like that in grub.cfg and we use the
exact same grub binary than wheezy.

> >--- debian-7.0-amd64-NETINST-1.filelist 2014-07-08 16:19:24.206922498 +0200
> >+++ kali-7.0-amd64-NETINST-1.filelist   2014-07-08 16:19:47.834925117 +0200
> >@@ -41,6 +41,7 @@
> > /mnt/boot/grub/x86_64-efi/efi_uga.mod
> > /mnt/boot/grub/x86_64-efi/elf.mod
> > /mnt/boot/grub/x86_64-efi/ext2.mod
> >+/mnt/boot/grub/x86_64-efi/extcmd.mod
> > /mnt/boot/grub/x86_64-efi/fat.mod
> > /mnt/boot/grub/x86_64-efi/fixvideo.mod
> > /mnt/boot/grub/x86_64-efi/font.mod
> >@@ -105,6 +106,7 @@
> > /mnt/boot/grub/x86_64-efi/msdospart.mod
> > /mnt/boot/grub/x86_64-efi/multiboot2.mod
> > /mnt/boot/grub/x86_64-efi/multiboot.mod
> >+/mnt/boot/grub/x86_64-efi/normal.mod
> > /mnt/boot/grub/x86_64-efi/ntfscomp.mod
> > /mnt/boot/grub/x86_64-efi/ntfs.mod
> > /mnt/boot/grub/x86_64-efi/ohci.mod
> 
> Hmm. I'd be worried about grub changes here. What happens if you use
> the Debian grub package instead?

We use the Debian grub package unchanged. What changed here is
that we have rebuilt debian-installer images which picked those
supplementary modules.

Those files are in the official Debian grub package in wheezy:
$ dpkg -c 
/ext/mirror/debian/pool/main/g/grub2/grub-efi-amd64-bin_1.99-27+deb7u2_amd64.deb
 |grep -E 'normal|extcmd'
-rw-r--r-- root/root  7144 2013-07-03 05:39 
./usr/lib/grub/x86_64-efi/extcmd.mod
-rw-r--r-- root/root164968 2013-07-03 05:39 
./usr/lib/grub/x86_64-efi/normal.mod

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140709094853.gh21...@x230-buxy.home.ouaza.com