On Tue, Jan 15, 2013 at 10:04:57AM -0600, Rob Landley wrote: > On 01/15/2013 05:45:44 AM, Alexander Graf wrote: > >On 15.01.2013, at 12:39, Suzuki K. Poulose wrote: > >> On 01/15/2013 04:39 PM, Alexander Graf wrote: > >>> On 15.01.2013, at 12:05, Suzuki K. Poulose wrote: > > > >Does this one work for you? > > > >http://ftp.nl.debian.org/debian/dists/stable/main/installer-s390/current/images/generic/kernel.debian > > I tried grabbing that and grabbing the initrd image in the same > directory, booting them with: > > qemu-system-s390x -kernel kernel.debian -nographic -m 1024 -initrd > initrd.debian \ > -append "rdinit=/bin/ash" > > And it booted to a shell prompt... with a broken console. When I did > "ls -l" at the resulting prompt it echoed back an ANSI escape > sequence, one character at a time, which looks like the response to > the ansi screen size probe busybox does (to query the display size > of an xterm across a virtual serial console).
I get the same result with this combination of kernel and initrd. However, with a more simple ramdisk (built by myself) that only has busybox in it I could boot into a shell that worked just fine. It seems to me that something in initrd.debian is not working well with qemu/virtio_console but I haven't debugged it further. Jens > I.E. qemu is getting deeply confused that what comes from stdin and > what you type on the keyboard aren't quite the same thing. Some kind > of strange ncurses hackage, looks like? > > I tried sticking "cat |" in front of the above qemu pipeline and it > got REALLY confused. > > Rob