Processing control commands:
> tags -1 + pending
Bug #284760 [installation-guide] debian-installer-manual:
netboot/debian-installer/i386/initrd.gz
Added tag(s) pending.
--
284760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284760
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tags -1 + pending
Olaf van der Spek wrote:
> http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#boot-initrd
>
> > you should download the netboot/debian-installer/i386/initrd.gz file
>
> The manual doesn't tell where this file can be downloaded.
> I think a link is
Package: debian-installer
Version: debian-bullseye-DI-alpha2-amd64-netinst.iso
qemu-system-x86_64 -cdrom debian-bullseye-DI-alpha2-amd64-netinst.iso
-nographic -vga none -m 1024
At the Debian install prompt pressing the escape key get me to the boot
prompt.
boot: install console=ttyS0,115200n8
On 5/20/20 1:18 PM, Philipp Kern wrote:
> But then I keep wondering how representative qemu is. Is VT220 SCLP even
> something you get on a real z machine? Not that we shouldn't fix qemu,
> of course. But Hercules might be closer to the real thing in this regard.
Hercules shows the exact same
On 20.05.20 12:42, Valentin Vidić wrote:
> On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
>> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
>>
>> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
>> that it would
Processing commands for cont...@bugs.debian.org:
> reassign 961056 src:linux,rootskel
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails
due to incorrect serial device
Bug reassigned from package 'rootskel' to 'src:linux,rootskel'.
Ignoring request to alter found
Processing commands for cont...@bugs.debian.org:
> merge 961056 926539
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails
due to incorrect serial device
Unable to merge bugs because:
severity of #926539 is 'serious' not 'important'
package of #926539 is
On 5/20/20 12:42 PM, Valentin Vidić wrote:
> It is hard to tell, but it seems the current state is hardcoded
> in different places:
>
> https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html
This wouldn't cause breakage as with your change, the console name
would actually be ttysclp0.
On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
>
> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
> that it would potentially break existing setups but
Processing commands for cont...@bugs.debian.org:
> reassign 961056 rootskel
Bug #961056 [src:rootskel] debian-installer: qemu-system-s390x installation
fails due to incorrect serial device
Bug reassigned from package 'src:rootskel' to 'rootskel'.
Ignoring request to alter found versions of bug
Processing commands for cont...@bugs.debian.org:
> reassign 961056 src:rootskel
Bug #961056 [debian-installer] debian-installer: qemu-system-s390x installation
fails due to incorrect serial device
Bug reassigned from package 'debian-installer' to 'src:rootskel'.
No longer marked as found in
Hi!
On 5/20/20 11:00 AM, Valentin Vidić wrote:
> Similar change for console name on s390x was not accepted:
>
> https://lkml.org/lkml/2020/5/19/854
>
> so please fix in rootskel.
I don't see any discussion in this thread. I would like to know the reasoning
why kernel upstream thinks that
On 5/20/20 11:17 AM, John Paul Adrian Glaubitz wrote:
> I don't see any discussion in this thread. I would like to know the reasoning
> why kernel upstream thinks that this naming inconsistency is correct. It
> makes no sense, in my opinion and it can potentially trigger more problems.
Ah, sorry.
Similar change for console name on s390x was not accepted:
https://lkml.org/lkml/2020/5/19/854
so please fix in rootskel.
--
Valentin
14 matches
Mail list logo
