Bug#291453: marked as done (Information on how to obtain images needs reorganization)
Your message dated Tue, 19 May 2020 22:46:20 +0200 with message-id <20200519224620.b33aabf53a73cbb9eb7b6...@mailbox.org> and subject line Re: Bug#291453: Information on how to obtain images needs reorganization has caused the Debian Bug report #291453, regarding Information on how to obtain images needs reorganization to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 291453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Debian-installer-version: d-i rc2 floppies (root.img + boot.img + net-drivers.img) uname -a: Linux pitr 2.4.27-2-586-tsc #1 Thu Dec 30 18:06:49 JST 2004 i586 GNU/Linux Date: 20050119-20 Method: Floppy boot and network installation Machine: Fuijutsu desktop PC Processor: Pentium II/200 MHz Memory: 80 Mb Root Device: NEC IDE 1,7Gb Root Size/partition table (df output): Filsystem 1K-blockAnvänt Tillgängl Anv% Monterat på /dev/hda2 685777391811257376 61% / tmpfs39400 0 39400 0% /dev/shm /dev/hda1 793680708548 44816 95% /media/hda1 Output of lspci and lspci -n: :00:00.0 0600: 8086:7030 (rev 02) :00:0c.0 0601: 8086:7000 (rev 01) :00:0c.1 0101: 8086:7010 :00:0c.2 0c03: 8086:7020 (rev 01) :00:0d.0 0300: 1002:5654 (rev 40) Base System Installation Checklist: [O] = OK, [E] = Fel (beskriv utförligt nedan på engelska), [ ] = testade ej Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [E?] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O/E] Reboot: [E] Comments/Problems: -- First, some observations about the installation manual: My first problem was finding the correct floppy images. I think either section 5.1.4 of the manual (Booting the Installer on Intel x86/Booting from Floppies) or section 4.3 (Creating Floppies from Disk Images) should explain which images I need or at least link directly to the MANIFEST file. That link is now in section 4.2.1 where it is not easily found. A link to the ftp directory containing the floppies and to rawrite/rwwrtwin would also be handy. Also, I think that the section about floppy reliability should be moved from 5.3.1 to 4.3. These changes would get all important information about boot floppies in two places instead of four. OK, I can now see that section A.2.2 actually does some of what I ask for. Is it really necessary to spread information to all these places? In general, I also think that chapters 4 and 5 of the manual should be reorganized from "Obtaining media" and "Boot" to one chapter covering the entire process of different types of installations (Floppy/CD/Netboot/USB/harddrive). Sections A through C should be integrated with the beginning of the document. These comments apply to the installation manual at http://d-i.alioth.debian.org/manual/en.i386/index.html, as of 2005-01-05. Now to the installation: I choose Swedish as my language in the first screen, but didn't get swedish until several screens later. That could have been really confusing if I hadn't understod english quite well. On my admittedly very slow computer there are several blank screens that come up after a choice has been made and they sometimes last for more than a couple of seconds. This may give the impression that d-i has hung, but is no big problem. I tried to get an old ISA network card working, but failed. I would have liked rmmod to be present on the system though, now I had to reboot (shifting three floppies) every time I wanted to try another IRQ. I finally gave up and replaced the network card with one that worked. Shouldn't the installation floppies give me the choice to insert a CD (the netinst image for example)? It just downloaded everything from the Debian mirror. Or should I somehow have used the CD instead of the root floppy? The downloads went OK anyway, but not completely smooth. The installer tried to download Packages.gz three times before getting it right. Partitioning went smoothly, I just reused (reformated) an old ext2 partition (hda2) where I used to have Hurd installed. I ignored a partition (hda1) with an old Debian (Linux) installation and reused a swap partition (hda3). There was a tiny skull indicated by my new root partition, but the installer
Re: Bug#291453: Information on how to obtain images needs reorganization
"Klas Adolfsson" wrote: > My first problem was finding the correct floppy images. I think either > section 5.1.4 of the manual (Booting the Installer on Intel x86/Booting from > Floppies) or section 4.3 (Creating Floppies from Disk Images) should explain > which images I need or at least link directly to the MANIFEST file. That > link is now in section 4.2.1 where it is not easily found. A link to the ftp > directory containing the floppies and to rawrite/rwwrtwin would also be > handy. Also, I think that the section about floppy reliability should be > moved from 5.3.1 to 4.3. These changes would get all important information > about boot floppies in two places instead of four. OK, I can now see that > section A.2.2 actually does some of what I ask for. Is it really necessary > to spread information to all these places? This bugreport claims about documentation issues in the installation-guide for booting from floppy, and it is more than 15 years old. Therefore I'm closing it now. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#556999: marked as done (Should adapt documentation about booting from an ISO image to GRUB2)
Your message dated Tue, 19 May 2020 21:47:02 +0200
with message-id <20200519214702.ad30c35022fa513d21dab...@mailbox.org>
and subject line Re: Bug#556999: Should adapt documentation about booting from
an ISO image to GRUB2
has caused the Debian Bug report #556999,
regarding Should adapt documentation about booting from an ISO image to GRUB2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
556999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Boot method: from HD
Image version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/mini.iso
Date: 2009/11/17
Machine: Older self made 32 bit PC
Processor: Athlon XP
Memory: 1GB
Partitions: automatic partitioning used
Output of lspci -knn (or lspci -nn): not important, all HW is working
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 CD: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [ ]
Install boot loader:[ ]
Overall install:[ ]
Comments/Problems:
1. Problem to boot from ISO image
I use GRUB2 and I had problem to find the way how to boot from ISO image. The
documentation describes only GRUB legacy. Please add something like:
menuentry "installation mini.iso" {
loopback loop (hd1,1)/mini.iso
linux(loop)/linux findiso=/mini.iso
initrd (loop)/initrd.gz
}
to the installation manual (and also to the GRUB2 man page).
2. Two network cards confusion
I have two network cards, first is connected to Internet, second to the local network.
Both are the same, so I cannot guess which one is the "primary" by name (of
course the second one tried...).
Maybe some (optional?) autodetection (try to find DHCP server in parallel on
all cards?) can help the user. But maybe my case is rare and it is not
important to solve it.
3. HD partitioning
I selected HD and the auto-partitioning (all in one partition) and then I get list of all my HDs with all partitions. I
was very confused because it was not clear for me what really changed (why there are so much line, when I selected only
one HD) and button "continue" was named "write changes permanently". I spent some time by "go
step back" and do it again, read included documentation... on the end I decided to try to continue and next screen
was list of changes with button "confirm changes".
I think that this step must be changed. I have two suggestions:
a) change the button "write changes permanently" to something like "continue" or
"see list of changes".
b) merge the two screens together, so user will see what will really change.
4. I was not able to select only some packages
I can select only predefined packs of software (desktop, www server...). I want
for example only Gnome (not KDE) etc.
5. A lot of waiting
User must wait often between steps.
Current workflow is:
I) user input
II) wait - something download and install
III) user input
IV) wait - something download and install
...
My suggestions are:
a) download packages on the background to the ramdisk (start immediately when
network is detected)
b) do things in parallel (download - prepare HD - user input then download -
install - user input)
c) try to merge all user inputs to one place (or two places?)
d) merge regional settings to one place (two screens?, do not ask two times for
keyboard settings)
e) decrease size of the packages (lzma compression?)
Thank you for your work,
TonyMi
--- End Message ---
--- Begin Message ---
Version: 20120826
Tonda Míšek wrote:
> 1. Problem to boot from ISO image
> I use GRUB2 and I had problem to find the way how to boot from ISO image. The
> documentation describes only GRUB legacy. Please add something like:
> menuentry "installation mini.iso" {
> loopback loop (hd1,1)/mini.iso
> linux(loop)/linux findiso=/mini.iso
> initrd (loop)/initrd.gz
> }
> to the installation manual (and also to the GRUB2 man page).
Christian Perrier replied:
> > 1. Problem to boot from ISO image
> >
> > I reassign your report to the installation guide for that reason.
Since this lack of documentation has been fixed in installation-guide 20120826,
I'm closing this bug.
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Re: Bug#556999: Should adapt documentation about booting from an ISO image to GRUB2
Version: 20120826
Tonda Míšek wrote:
> 1. Problem to boot from ISO image
> I use GRUB2 and I had problem to find the way how to boot from ISO image. The
> documentation describes only GRUB legacy. Please add something like:
> menuentry "installation mini.iso" {
> loopback loop (hd1,1)/mini.iso
> linux(loop)/linux findiso=/mini.iso
> initrd (loop)/initrd.gz
> }
> to the installation manual (and also to the GRUB2 man page).
Christian Perrier replied:
> > 1. Problem to boot from ISO image
> >
> > I reassign your report to the installation guide for that reason.
Since this lack of documentation has been fixed in installation-guide 20120826,
I'm closing this bug.
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#961057: Acknowledgement (debian-installer: qemu-system-s390x installation fails due to missing modules)
It seems that virtio_scsi might also be required for cdrom: # lsmod Module Size Used by rng_core 20480 0 aes_s390 24576 0 des_s390 20480 0 des_generic28672 1 des_s390 sha_common 16384 0 virtio_balloon 20480 0 sr_mod 28672 0 cdrom 57344 1 sr_mod virtio_scsi24576 0 scsi_mod 225280 2 virtio_scsi,sr_mod virtio_blk 24576 0 virtio_net 49152 0 net_failover 20480 1 virtio_net failover 16384 1 net_failover -- Valentin
Bug#961056: debian-installer: qemu-system-s390x installation fails due to incorrect serial device
On Tue, May 19, 2020 at 07:23:21PM +0200, John Paul Adrian Glaubitz wrote: > Please see #926539 [1]. Thanks, I have sent the patch for the driver instead: https://lkml.org/lkml/2020/5/19/854 -- Valentin
Bug#961056: debian-installer: qemu-system-s390x installation fails due to incorrect serial device
On 5/19/20 7:03 PM, Valentin Vidic wrote: > Running the installation inside a QEMU instance does not work in buster: > (...) > steal-ctty: No such file or directory > > Than just hangs there because of the problem with the serial port name. > Installer tries to use nonexistent serial device /dev/ttyS1, while the real > name is /dev/ttysclp0. Proposed fix is here: Please see #926539 [1]. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#961057: debian-installer: qemu-system-s390x installation fails due to missing modules
Package: debian-installer Version: 20190702+deb10u4 Severity: important Dear Maintainer, Installer initrd does not include modules virtio_blk and virtio_net (+dependencies) preventing a successful installation inside a QEMU VM: $ virt-install --arch=s390x --name test --memory 1024 --disk test.img \ --extra-args=console=ttyS0 \ -l http://ftp.de.debian.org/debian/dists/buster/main/installer-s390x/ -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#961056: debian-installer: qemu-system-s390x installation fails due to incorrect serial device
Package: debian-installer Version: 20190702+deb10u4 Severity: important Dear Maintainer, Running the installation inside a QEMU instance does not work in buster: $ virt-install --arch=s390x --name test --memory 1024 --disk none \ --extra-args=console=ttyS0 \ -l http://ftp.de.debian.org/debian/dists/buster/main/installer-s390x/ Starting install... Retrieving file kernel.debian... | 3.3 MB 00:00:00 Retrieving file initrd.debian... | 9.7 MB 00:00:01 Allocating 'virtinst-kernel.debian.mnba14e7' | 3.3 MB 00:00:00 Transferring virtinst-kernel.debian.mnba14e7 | 3.3 MB 00:00:00 Allocating 'virtinst-initrd.debian.2q88l_1j' | 9.7 MB 00:00:00 Transferring virtinst-initrd.debian.2q88l_1j | 9.7 MB 00:00:00 Connected to domain test Escape character is ^] [1.785649] Linux version 4.19.0-9-s390x (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 +SMP Debian 4.19.118-2 (2020-04-29) [1.786919] setup: Linux is running under KVM in 64-bit mode [1.788555] setup: The maximum memory size is 1024MB [1.790050] cpu: 1 configured CPUs, 0 standby CPUs [1.822704] Write protected kernel read-only data: 8976k ... [6.148235] mip6: Mobile IPv6 [6.148389] NET: Registered protocol family 17 [6.149302] mpls_gso: MPLS GSO support [6.151503] registered taskstats version 1 [6.152310] zswap: loaded using pool lzo/zbud [6.154776] AppArmor: AppArmor sha1 policy hashing enabled [6.780329] Freeing unused kernel memory: 684K [6.780784] Write protected read-only-after-init data: 20k [6.780870] Run /init as init process steal-ctty: No such file or directory Than just hangs there because of the problem with the serial port name. Installer tries to use nonexistent serial device /dev/ttyS1, while the real name is /dev/ttysclp0. Proposed fix is here: https://salsa.debian.org/installer-team/rootskel/-/merge_requests/2/diffs -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 19:36, 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.
I don't think this (having to set console=tty0 on arm64) is going to
change on the kernel side, see:
https://lore.kernel.org/linux-serial/20200513143755.GM17734@linux-b0ei/
where Petr Mladek said:
My suggestion is:
+ Fix SPCR setting or device tree of your device when the defaults
are not as expected.
+ Use command line to force your value when the defaults are not
as expected and you could not change them.
So I tested my earlier patch, and did a bit more. I've attached three
patches, first two for debian-installer and the third for rootskel.
The first patch fixes arm64 netboot and netboot-gtk mini.iso images
which now have 'Graphical install' GRUB entries using /gtk/initrd.gz
files which don't exist, by making that file identical to /initrd.gz.
The second patch adds "console=tty0" to GRUB entries marked as
"Graphical" in grub-gencfg. Without this, "Graphical automated install"
runs on the serial console (since that may be the "preferred" console
due to stdout-path or SPCR on arm64). The console=tty0 cmdline argument
also ends up in the installed system's /etc/default/grub.cfg, which is
correct IMO.
The third patch considers tty0 a possible console even if it's not in
/proc/consoles (the patch I sent earlier). The text-mode installer
already launches on the display in the stdout-path case, but not on the
SPCR case. With this it launches on the display in that case as well.
I've tested on an arm64 QEMU VM. After all the patches:
- "Install" launches on serial and display
- "Graphical install" launches on display and serial
- "Automated install" launches only on serial
- "Graphical automated install" launches only on display
On systems where console is set with stdout-path instead, "Graphical
install" would launch only on display, but the others would be the same.
>From 2970cde5a6217a76a0b499987c4e9c40485db891 Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 18 May 2020 22:35:07 +0300
Subject: [PATCH] Include a /gtk/initrd.gz in graphical arm mini.iso builds
Signed-off-by: Alper Nebi Yasak
---
build/config/arm.cfg | 4
1 file changed, 4 insertions(+)
diff --git a/build/config/arm.cfg b/build/config/arm.cfg
index 4e12bae63..fcf8858b2 100644
--- a/build/config/arm.cfg
+++ b/build/config/arm.cfg
@@ -46,6 +46,10 @@ arch_miniiso: arm_grub_efi
ln -f $(TEMP_KERNEL) $(TEMP_CD_TREE)/linux
ln -f $(TEMP_INITRD) $(TEMP_CD_TREE)/initrd.gz
+ if [ "$(GRAPHICAL_INSTALLER)" = y ]; then \
+ mkdir -p $(TEMP_CD_TREE)/gtk; \
+ ln -f $(TEMP_INITRD) $(TEMP_CD_TREE)/gtk/initrd.gz; \
+ fi
mkdir -p $(TEMP_CD_TREE)/.disk
echo "Debian GNU/Linux $(DEBIAN_VERSION) $(ARCH) - netboot mini.iso $(BUILD_DATE)"\
--
2.26.2
>From f776932c463ed2f921255e395a72373e8ef403b5 Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 18 May 2020 22:50:34 +0300
Subject: [PATCH] Explicitly set console=tty0 for graphical GRUB entries
Signed-off-by: Alper Nebi Yasak
---
build/util/grub-gencfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/build/util/grub-gencfg b/build/util/grub-gencfg
index 97fe42432..f4b6adbda 100755
--- a/build/util/grub-gencfg
+++ b/build/util/grub-gencfg
@@ -169,6 +169,7 @@ sub menuentry ($;%)
push @cmdline, "theme=dark" if $xattr{Dark};
push @cmdline, "---";
push @cmdline, "quiet" if $xattr{Quiet};
+push @cmdline, "console=tty0" if $xattr{Graphical};
my $cmdline = join(" ", @cmdline);
--
2.26.2
>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.2
