Bug#919842: Jetson-tx1: successful, but required customized boot media

2019-01-19 Thread Vagrant Cascadian
implementation lacks some features (SMP, SATA). Once booted with the USB firmware blob loaded and correct .dtb loaded, the install worked fine. live well, vagrant -- Package-specific info: Boot method: microSD Image version: https://d-i.debian.org/daily-images/arm64/20190119-02:06/netboot

Re: Multiple console support in d-i

2019-01-19 Thread Ben Hutchings
On Sun, 2019-01-20 at 01:21 +, Wookey wrote: > On 2019-01-19 20:11 +, Ben Hutchings wrote: > > On Sat, 2019-01-19 at 11:08 +, Steve McIntyre wrote: > > [...] > > > * add lots more console= options to the grub.cfg for arm64 (to cover > > >all the possibilities), then let d-i

Re: Multiple console support in d-i

2019-01-19 Thread Wookey
On 2019-01-19 20:11 +, Ben Hutchings wrote: > On Sat, 2019-01-19 at 11:08 +, Steve McIntyre wrote: > [...] > > * add lots more console= options to the grub.cfg for arm64 (to cover > >all the possibilities), then let d-i startup work out which devices > >exist from /proc/cmdlinge

Re: UEFI Secure Boot changes in d-i and live images

2019-01-19 Thread Ben Hutchings
On Sun, 2019-01-20 at 00:16 +0100, Philipp Kern wrote: > Hi, > > On 2019-01-13 20:23, Steve McIntyre wrote: [...] > > I'll test all these again in the next couple of days to verify that > > things have pulled through as I expect, then it's time to post to > > d-d-a and write a blog too. We've

Processed: Bug #900918 in debian-installer marked as pending

2019-01-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #900918 [debian-installer] debian-installer: Please make the generated images reproducible Ignoring request to alter tags of bug #900918 to the same tags previously set -- 900918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900918 Debian

Re: UEFI Secure Boot changes in d-i and live images

2019-01-19 Thread Philipp Kern
Hi, On 2019-01-13 20:23, Steve McIntyre wrote: I've just pushed changes to a few bits of d-i this weekend to make SB work for amd64: * build/util/efi-image: We can use pre-existing (and already signed) EFI binaries instead of building a new monolithic image ourselves (which won't be

Processed: Re: Bug#900918: debian-installer: Please make the generated images reproducible

2019-01-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #900918 [debian-installer] debian-installer: Please make the generated images reproducible Added tag(s) pending. -- 900918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900918 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#900918: debian-installer: Please make the generated images reproducible

2019-01-19 Thread Cyril Brulebois
date as well.) Checking all MINIISO occurrences might also make sense > I suppose? FWIW, dropping all fontconfig-related bits (see attached patch) makes it possible to confirm only mini.iso (regular and gtk ones) are showing differences now: installer-amd64/20190119/images/MD5SUMS installer

Bug#900918: debian-installer: Please make the generated images reproducible

2019-01-19 Thread Cyril Brulebois
ple times in the same sid devel chroot: installer-amd64/20190119/images/cdrom/gtk/initrd.gz installer-amd64/20190119/images/hd-media/boot.img.gz installer-amd64/20190119/images/hd-media/gtk/initrd.gz installer-amd64/20190119/images/MD5SUMS installer-amd64/20190119/images/netboot/g

Bug#900918: debian-installer: Please make the generated images reproducible

2019-01-19 Thread Cyril Brulebois
Hi Chris, Chris Lamb (2019-01-19): > > * 0c19a29645a6a3136f3a51da5d5cf1cfcec5fdfb mentions file system > >ordering only, but that's just the sort part > > I've split this commit and it is much clearer now. Perfect, thanks. > > * 71391967763708055a65ed68999db8f4ea6fc6e6 sets “deb1”

Bug#919813: os-prober fails to find any os's at all.

2019-01-19 Thread Hendrik Boom
Package: os-prober Version: 1.77 os-prober fails to find any os's at all after a new Debian buster install, not even the installed and running DEbian buster. The install was done using the net-install CD on a USB stick on 2019 01 18, downloaded immediately before the installation.

Re: Multiple console support in d-i

2019-01-19 Thread Ben Hutchings
On Sat, 2019-01-19 at 11:08 +, Steve McIntyre wrote: [...] > * add lots more console= options to the grub.cfg for arm64 (to cover >all the possibilities), then let d-i startup work out which devices >exist from /proc/cmdlinge and spawn d-i on each. [...] I think you should look in

Re: Please dak copy-installer 20190118

2019-01-19 Thread Cyril Brulebois
Hi, Joerg Jaspert (2019-01-19): > On 15287 March 1977, Cyril Brulebois wrote: > > FTPmasters, please sync the installer from sid to testing: > > > > dak copy-installer 20190118 > > [ ] dak@fasolo:~$ dak copy-installer 20190118 > > Will copy installer version 20190118 from suite unstable to

Re: Scheduling 9.7

2019-01-19 Thread Cyril Brulebois
Hi, Jonathan Wiltshire (2019-01-18): > Please indicate your availablility out of: > > - (Feb 2 unlikely, FOSDEM) > - Feb 9 > - Feb 16 I should be able to make anything work regarding d-i preparations/checks before the point release, thanks. Cheers, -- Cyril Brulebois (k...@debian.org)

Re: Multiple console support

2019-01-19 Thread peter green
On 19/01/19 04:27, Wookey wrote: Arm64 (arm in general in fact) has a rather fundamental problem with D-I, which is that both serial and display are sensible default devices for the installer to run on. Which is 'correct' depends very much on the hardware and the circumstances. You may be

Re: Multiple console support in d-i

2019-01-19 Thread Ian Campbell
On Sat, 2019-01-19 at 11:08 +, Steve McIntyre wrote: > >So far I have done a proof-of-concept hack and demonstrated that > >running two instances does in fact work nicely without anything > >obvious breaking. The console selection still needs some work/checking > >(I've run out of time for

Bug#900918: debian-installer: Please make the generated images reproducible

2019-01-19 Thread Chris Lamb
[Keeping Kibi in CC as requested off-list, dropping mtools@p.d.o] Dear Kibi, First, thank you so much for your review. I believe I have resolve all of your issues on the corresponding merge request, as well as rebasing it against the current master:

Re: Multiple console support

2019-01-19 Thread Richard Hector
On 19/01/19 5:27 PM, Wookey wrote: > This problem doesn't arise on x86 where there is 'always' a screen (or > some BIOs magic to reflect what would be on the screen to serial). Is that true? I'm sure the Soekris box I've got (in storage) (admittedly, probably not a supported cpu any more) only

Re: Scheduling 9.7

2019-01-19 Thread Donald Norwood
On 1/19/19 5:28 AM, Steve McIntyre wrote: > On Fri, Jan 18, 2019 at 06:44:56PM +, Jonathan Wiltshire wrote: >> Hi, >> >> 9.7 is a bit overdue already (current events being a bit of a time-sink). >> >> Please indicate your availablility out of: >> >> - (Feb 2 unlikely, FOSDEM) > > Quite. >

Re: Please dak copy-installer 20190118

2019-01-19 Thread Joerg Jaspert
On 15287 March 1977, Cyril Brulebois wrote: FTPmasters, please sync the installer from sid to testing: dak copy-installer 20190118 [ ] dak@fasolo:~$ dak copy-installer 20190118 Will copy installer version 20190118 from suite unstable to testing. Architectures to copy: i386, amd64, mipsel,

Re: Scheduling 9.7

2019-01-19 Thread Joerg Jaspert
On 15286 March 1977, Jonathan Wiltshire wrote: - Feb 9 - Feb 16 Can deal with both. -- bye, Joerg

Bug#911133: Graphical installer

2019-01-19 Thread Steve McIntyre
Forgot to add the bug in on the mails I just sent. Wookey has been working through how to do some of this. See: * https://lists.debian.org/debian-boot/2019/01/msg00183.html * https://lists.debian.org/debian-boot/2019/01/msg00184.html and my responses there. -- Steve McIntyre, Cambridge, UK.

Re: arm64 graphical installer

2019-01-19 Thread Steve McIntyre
[ Adding CC to debian-arm for interest ] On Sat, Jan 19, 2019 at 03:39:44AM +, Wookey wrote: >I've done some work on getting the graphical installer going on arm64. \o/ >It's not quite finished, but Steve suggested I publish where I'm at so >I can get some help with the right set of module

Re: Scheduling 9.7

2019-01-19 Thread Steve McIntyre
On Fri, Jan 18, 2019 at 06:44:56PM +, Jonathan Wiltshire wrote: >Hi, > >9.7 is a bit overdue already (current events being a bit of a time-sink). > >Please indicate your availablility out of: > > - (Feb 2 unlikely, FOSDEM) Quite. > - Feb 9 > - Feb 16 Both of those currently look free for