Bug#291453: marked as done (Information on how to obtain images needs reorganization)

2020-05-19 Thread Debian Bug Tracking System
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

Re: Bug#291453: Information on how to obtain images needs reorganization

2020-05-19 Thread Holger Wansing
"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

Bug#556999: marked as done (Should adapt documentation about booting from an ISO image to GRUB2)

2020-05-19 Thread Debian Bug Tracking System
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 documentati

Re: Bug#556999: Should adapt documentation about booting from an ISO image to GRUB2

2020-05-19 Thread Holger Wansing
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

Bug#961057: Acknowledgement (debian-installer: qemu-system-s390x installation fails due to missing modules)

2020-05-19 Thread Valentin Vidić
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

Bug#961056: debian-installer: qemu-system-s390x installation fails due to incorrect serial device

2020-05-19 Thread Valentin Vidić
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

2020-05-19 Thread John Paul Adrian Glaubitz
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/t

Bug#961057: debian-installer: qemu-system-s390x installation fails due to missing modules

2020-05-19 Thread Valentin Vidic
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.im

Bug#961056: debian-installer: qemu-system-s390x installation fails due to incorrect serial device

2020-05-19 Thread Valentin Vidic
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/debia

Re: Graphical installer on arm64 (netboot and cdrom)

2020-05-19 Thread Alper Nebi Yasak
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 cons