Re: Missing GnuPG signatures for checksums
Hi Steve and Julien, On 4/20/20 6:45 PM, Steve McIntyre wrote: There are checksums for these in the archive (dists/buster/main/installer-amd64/current/images/SHA256SUMS etc.) and those files are themselves checksummed in the top-level buster Release file, and that's signed by Release.gpg (or via InRelease if you prefer that route). Yes, it's not very obvious... Many thanks, I got it now! Steve, also many thanks for the automatically generated reference for all preseed options, I found apt-setup/disable-cdrom-entries there, very nice to have everything in one place, most of them aren't documented anywhere else.[1] Best regards, Laurentiu [1] https://jack.einval.com/debian-preseed/
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 07:36:42PM +0300, Alper Nebi Yasak wrote: >On 20/04/2020 18:38, Steve McIntyre wrote: >> Does /dev/tty0 show up in /proc/consoles in your setup? We might need >> to tweak that yet... > >Here is a small but untested patch for rootskel's reopen-console for that. Hmmm. Is this the right answer, though? I've got totally headless arm64 machines that also have a /dev/tty0. Would we want to run d-i there? Maybe, I'm genuinely not sure. It might be harmless, I guess...? >(Thanks for the cd image, it'll probably take me until tomorrow to test and >report back on it) Cool. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 03:43:57PM +0100, Steve McIntyre wrote: >On Mon, Apr 20, 2020 at 03:21:20PM +0100, Steve McIntyre wrote: >>On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >>>On 20/04/2020 16:36, Steve McIntyre wrote: I'm just going to test again with that change included, then I can push a netinst image somewhere for you to test... >>> >>>I'd appreciate it. Here's another patch, this time for the armhf graphical >>>cdrom. I checked that it boots into a graphical installer when run in a QEMU >>>arm VM (still with 'direct kernel boot') but no further. If you can also make >>>an armhf netinst image from this I can test that too (at least in a VM, not >>>sure the configs for my chromebook were enabled on the armhf kernel..). >> >>Ah, OK. I wasn't sure if it was worth trying to add this on armhf >>too... :-) >> >>I'm just building with a different local patch to add the setting >>GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the >>graphical installer to each of the grub-gencfg calls. I'll let that >>finish first... > >Try the image at > > http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ > >please? OK, so this lot seems to work in a VM at least (thanks Marcin!), so I've pushed this set of patches to master now. I'm not sure about adding the graphical installer for armhf right now, but I'm open to being convinced... Once we have a working d-i daily build I'll also push my changes for debian-cd to use it on arm64. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Re: Missing GnuPG signatures for checksums
Hi Laurențiu On Mon, Apr 20, 2020 at 06:38:48PM +0200, Laurențiu Păncescu wrote: >Hello, > >I'm trying to put a preseed file on the same USB stick as the installation, >using hd-media/boot.img.gz is easier than remastering the iso. It works, but >there seems not to be any signed checksum file for these images and they are >served only over http: > >http://http.us.debian.org/debian/dists/buster/main/installer-amd64/current/images/ > >How can I check if these images are authentic? I guess I could mount a signed >CD iso like netinst, copy vmlinuz and initrd from there and create my own USB >stick with syslinux - is there a better way? There are checksums for these in the archive (dists/buster/main/installer-amd64/current/images/SHA256SUMS etc.) and those files are themselves checksummed in the top-level buster Release file, and that's signed by Release.gpg (or via InRelease if you prefer that route). Yes, it's not very obvious... -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
Re: Missing GnuPG signatures for checksums
On Mon, Apr 20, 2020 at 06:38:48PM +0200, Laurențiu Păncescu wrote: > Hello, > > I'm trying to put a preseed file on the same USB stick as the installation, > using hd-media/boot.img.gz is easier than remastering the iso. It works, but > there seems not to be any signed checksum file for these images and they are > served only over http: > > http://http.us.debian.org/debian/dists/buster/main/installer-amd64/current/images/ > > How can I check if these images are authentic? I guess I could mount a > signed CD iso like netinst, copy vmlinuz and initrd from there and create my > own USB stick with syslinux - is there a better way? > Hi, http://http.us.debian.org/debian/dists/buster/InRelease is signed and contains checksums for the d-i SHA256SUMS file. (I realize that still makes verification awkward.) Cheers, Julien
Missing GnuPG signatures for checksums
Hello, I'm trying to put a preseed file on the same USB stick as the installation, using hd-media/boot.img.gz is easier than remastering the iso. It works, but there seems not to be any signed checksum file for these images and they are served only over http: http://http.us.debian.org/debian/dists/buster/main/installer-amd64/current/images/ How can I check if these images are authentic? I guess I could mount a signed CD iso like netinst, copy vmlinuz and initrd from there and create my own USB stick with syslinux - is there a better way? Thanks in advance, Laurențiu
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 18:38, Steve McIntyre wrote:
Does /dev/tty0 show up in /proc/consoles in your setup? We might need
to tweak that yet...
Here is a small but untested patch for rootskel's reopen-console for that.
(Thanks for the cd image, it'll probably take me until tomorrow to test
and report back on it)
>From 1713b6544d4950d2861710b48aff16b4b0a119af Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 20 Apr 2020 19:27:18 +0300
Subject: [PATCH] Use /dev/tty0 as a console even if it's not in /proc/consoles
Signed-off-by: Alper Nebi Yasak
---
src/sbin/reopen-console-linux | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/sbin/reopen-console-linux b/src/sbin/reopen-console-linux
index 13b15a3..0816be4 100755
--- a/src/sbin/reopen-console-linux
+++ b/src/sbin/reopen-console-linux
@@ -78,6 +78,13 @@ do
fi
done
+# /dev/tty0 may not show up in /proc/consoles (at least on QEMU aarch64),
+# debian-installer should run on it anyway if it exists.
+if [ -c /dev/tty0 ] && ! { echo "$consoles" | grep -q "^tty0$"; }; then
+ consoles="${consoles:+$consoles$NL}tty0"
+ log " Adding tty0 to possible consoles list"
+fi
+
if [ -z "$consoles" ]; then
# Nothing found? Default to /dev/console.
log "Found no consoles! Defaulting to /dev/console"
--
2.26.1
Re: F2FS support
> You will also need to add support for f2fs in libparted to get it works in > d-i (a patch is pending on upstream and in the debian package). I wasn't aware that there is no f2fs support in libparted yet - thanks for doing that. I hope your patch gets reviewed soon. > Otherwises, I can format a fresh install and it boots :) That's awesome to hear! Cheers, Stephan
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 03:21:20PM +0100, Steve McIntyre wrote: >On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >>On 20/04/2020 16:36, Steve McIntyre wrote: >>> I'm just going to test again with that change included, then I can >>> push a netinst image somewhere for you to test... >> >>I'd appreciate it. Here's another patch, this time for the armhf graphical >>cdrom. I checked that it boots into a graphical installer when run in a QEMU >>arm VM (still with 'direct kernel boot') but no further. If you can also make >>an armhf netinst image from this I can test that too (at least in a VM, not >>sure the configs for my chromebook were enabled on the armhf kernel..). > >Ah, OK. I wasn't sure if it was worth trying to add this on armhf >too... :-) > >I'm just building with a different local patch to add the setting >GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the >graphical installer to each of the grub-gencfg calls. I'll let that >finish first... Try the image at http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >On 20/04/2020 16:36, Steve McIntyre wrote: >> I'm just going to test again with that change included, then I can >> push a netinst image somewhere for you to test... > >I'd appreciate it. Here's another patch, this time for the armhf graphical >cdrom. I checked that it boots into a graphical installer when run in a QEMU >arm VM (still with 'direct kernel boot') but no further. If you can also make >an armhf netinst image from this I can test that too (at least in a VM, not >sure the configs for my chromebook were enabled on the armhf kernel..). Ah, OK. I wasn't sure if it was worth trying to add this on armhf too... :-) I'm just building with a different local patch to add the setting GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the graphical installer to each of the grub-gencfg calls. I'll let that finish first... -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 16:36, Steve McIntyre wrote:
I'm just going to test again with that change included, then I can
push a netinst image somewhere for you to test...
I'd appreciate it. Here's another patch, this time for the armhf
graphical cdrom. I checked that it boots into a graphical installer when
run in a QEMU arm VM (still with 'direct kernel boot') but no further.
If you can also make an armhf netinst image from this I can test that
too (at least in a VM, not sure the configs for my chromebook were
enabled on the armhf kernel..).
>From b194a1f9d4619eceb42e355d469c7cd8b54992f7 Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 20 Apr 2020 16:50:07 +0300
Subject: [PATCH] Add modules and build files for armhf graphical installer
cdrom
Signed-off-by: Alper Nebi Yasak
---
build/config/armhf/cdrom.cfg | 2 +-
build/config/armhf/cdrom/gtk.cfg | 19 +++
build/pkg-lists/cdrom/grub/gtk/armhf.cfg | 11 +++
3 files changed, 31 insertions(+), 1 deletion(-)
create mode 100644 build/config/armhf/cdrom/gtk.cfg
create mode 100644 build/pkg-lists/cdrom/grub/gtk/armhf.cfg
diff --git a/build/config/armhf/cdrom.cfg b/build/config/armhf/cdrom.cfg
index 2a6fafd77..68cc87078 100644
--- a/build/config/armhf/cdrom.cfg
+++ b/build/config/armhf/cdrom.cfg
@@ -1,4 +1,4 @@
# el-torito is too large at the moment, so is disabled.
-FLAVOUR_SUPPORTED = grub
+FLAVOUR_SUPPORTED = grub gtk
MEDIA_TYPE = CD-ROM
diff --git a/build/config/armhf/cdrom/gtk.cfg b/build/config/armhf/cdrom/gtk.cfg
new file mode 100644
index 0..76024e2f1
--- /dev/null
+++ b/build/config/armhf/cdrom/gtk.cfg
@@ -0,0 +1,19 @@
+TARGET = $(INITRD) $(KERNEL) $(DEBIAN_CD_INFO)
+
+MANIFEST-KERNEL = "kernel for use with EFI to build a CD (graphical)"
+MANIFEST-INITRD = "initrd for use with EFI to build a CD (graphical)"
+MANIFEST-DEBIAN_CD_INFO = "EFI config files for CD (graphical)"
+
+TYPE = cdrom/grub/gtk
+
+EXTRANAME = gtk/
+
+IS_PURE_GTK = 1
+
+KEEP_GI_LANGS = 1
+
+VIDEO_MODE=$(VIDEO_MODE_GTK)
+
+# All images that include cdebconf should include symbols needed by these
+# plugins.
+EXTRAUDEBS += cdebconf-gtk-entropy
diff --git a/build/pkg-lists/cdrom/grub/gtk/armhf.cfg b/build/pkg-lists/cdrom/grub/gtk/armhf.cfg
new file mode 100644
index 0..bda77cdab
--- /dev/null
+++ b/build/pkg-lists/cdrom/grub/gtk/armhf.cfg
@@ -0,0 +1,11 @@
+#include "gtk-linux"
+
+#mouse-modules-${kernel:Version}
+event-modules-${kernel:Version}
+xserver-xorg-input-evdev-udeb
+xserver-xorg-video-fbdev-udeb
+
+#speakup-modules-${kernel:Version}
+#sound-modules-${kernel:Version}
+#console-setup-linux-fonts-udeb
+#espeakup-udeb
--
2.26.1
Re: Graphical installer on arm64 (netboot and cdrom)
On Sun, Apr 19, 2020 at 10:23:06PM +0300, Alper Nebi Yasak wrote:
>On 16/04/2020 15:40, Steve McIntyre wrote:
>> On Tue, Apr 14, 2020 at 05:43:36PM +0100, Steve McIntyre wrote:
>> >
>> > ACK.
>> >
>> > Building locally to test here...
>>
>> And I have a build that looks OK by eye. Unfortunately, my local test
>> machine (Macchiatobin) seems to be dying and I can't test this
>> effectively now. :-(
>
>Ah, OK. Thanks for spending time on this.
>
>> It needs some tiny debian-cd changes and then we'll get
>> netinst, DVD images etc. also including the graphical installer. Final
>> thing missing - the grub.cfg that's generated for the CD/DVD/USB boot
>> doesn't include menu entries for graphical boot.
>Adding INITRD_GTK to build/config/arm.cfg as in:
>
>diff --git a/build/config/arm.cfg b/build/config/arm.cfg
>index fe8cf80f9..898795658 100644
>--- a/build/config/arm.cfg
>+++ b/build/config/arm.cfg
>@@ -23,6 +23,7 @@ arch_cd_info_dir: arm_grub_efi
> grub-gencfg \
> KERNEL /%install%/vmlinuz \
> INITRD /%install%/initrd.gz \
>+ INITRD_GTK /%install%/gtk/initrd.gz \
> HEADER boot/$(ARCH)/grub/grub-efi.cfg \
> > $(TEMP_CD_INFO_DIR)/grub/grub.cfg; \
> cp -a $(GRUB_FONT) $(TEMP_CD_INFO_DIR)/grub/font.pf2; \
>
>seems to be enough for the last part, I'm getting "Graphical install" and
>others in both cdrom{,/gtk}/debian-cd_info.tar.gz files' grub.cfg files.
>
>I expect that change will make the "Graphical" entries appear also on armhf
>where there isn't a cdrom/gtk build yet, so I'll also have a look at that.
>
>Hopefully I can learn enough debian-cd to build and test with proper images
>this time around :)
I'm just going to test again with that change included, then I can
push a netinst image somewhere for you to test...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
Re: F2FS support
Hey, You will also need to add support for f2fs in libparted to get it works in d-i (a patch is pending on upstream and in the debian package). Moreover , the crc32 udeb module is needed (required by the f2fs module), it is enabled in the last linux version normally but just be sure that crc-modules udeb is installed. The last days I have tested, only description and meta were missing on some mountoptions (it crashed ramdomly when I was trying to use options). Otherwises, I can format a fresh install and it boots :) Hope this helps, Regards, Romain Le dim. 19 avr. 2020 à 22:49, Stephan Lachnit a écrit : > Hi Steve, > > It's been quite some time since we last talked about the F2FS module for > d-i. Since then Romain Perier updated the mount options for Linux 5.5 and > (some other things). Today I looked into it, and I finally build the udeb! > Salsa Repo: https://salsa.debian.org/stephanlachnit/partman-f2fs > Mentors: https://mentors.debian.net/package/partman-f2fs > > @Romain JTLYK I rebased the repo and adjusted some stuff in your commits > (debhelper version in control e.g.). > > I haven't build an image or even tried an installation yet, that would be > the next step. Since the university starts for me this week, I'm not sure > how much time I have in the next couple of days/weeks, so any help is > appreciated. > > Since Bullseye is not that far away anymore, I would really like to see > the F2FS support in the next d-i release. I guess there is no ETA yet? > > Cheers, > Stephan >
Bug#958288: Installation report
Package: installation-reports Context - trying to install Debian on an Apple imac intel duo 2, using debian-mac-testing-amd64-netinst.iso Boot method - first attempt : USB stick - imac did not see the USBstick Boot method - second attempt : CD image burnt using xfburn Image version: tried with 64 and 32 bit images. Both stopped with same error Date: <20/04/2020 5am> Machine: Processor: Memory:2gigs Partitions: Output of lspci -knn (or lspci -nn): system not installed Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[O ] Configure network: [O ] Detect media: [E ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Installer failed to find a boot image for the system on the media.
