Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 16:00, Adrian Davey wrote:
> On 2016-05-18 11:44, David Griffith wrote:
>> On Wed, 18 May 2016, Adrian Davey wrote:
>>
>>> On 2016-05-18 11:27, David Griffith wrote:
 On Wed, 18 May 2016, Mark Cave-Ayland wrote:

> On 18/05/16 11:11, David Griffith wrote:
>
>>> Ahhh so it appears that Debian have broken QEMU packages for
>>> qemu-system-sparc :(
>>>
>>> You should be able to grab the binaries directly from QEMU git at
>>> http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d
>>>
>>>
>>> - simply drop both files into /usr/share/qemu manually and see if
>>> that
>>> helps.
>>
>> No change.  Still black.
>
> How strange.
>
> First can you check again with the different display options: -display
> sdl, -display gtk and -display vnc and see if that changes
> anything? At
> least if anything is wrong and you launch these from a terminal you
> may
> see some errors on the command line.
>
> Secondly what happens if you remove the -hda part from your command
> line
> and just try booting the ISO?

 Still black.
>>>
>>> package openbios-sparc adds
>>> /usr/share/openbios/QEMU,tcx.bin
>>> /usr/share/openbios/openbios-sparc32
>>> /usr/share/openbios/openbios-sparc64
>>>
>>> it could be that qemu is not looking at the correct location, I see
>>> only symlinks from /usr/share/qemu/ to /usr/share/openbios for
>>> sparc32/64 files.
>>
>> Okay.  Now that those video bin files are in the proper place and
>> named correctly, the graphical window is showing something normal.  I
>> guess the package is mangled.
>>
>> Now that that's done, neither "boot 2" nor "boot cdrom" will work.
>>
>> ===begin quote===
>> Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args:
>> Internal loopback test -- Wrong packet length; expected 36, observed 64
>>
>> Can't open boot device
>>
>> Type  help  for more information
>> ok boot cdrom
>> Boot device: /iommu/sbus/espdma@5,840/esp@5,880/sd@6,0:d  File
>> and args:
>>
>> Can't open boot device
>>
>> ok boot 2
>> Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args: 2
>> Internal loopback test -- Wrong packet length; expected 36, observed 64
>>
>> Can't open boot device
>>
>> ok
>> ===end quote===
> 
> FYI
> 
> BUG #824665 "openbios-sparc: missing QEMU,cgthree.bin file" created,
> once it's included then we can file a bug report for qemu-system-sparc
> to include the symlinks for all the sparc display bin files.
> 
> Regards,
> 
> Adrian

Looks like you beat me to it - thanks a lot! As I'm at the bleeding edge
of QEMU I'm always building everything from git rather than use .deb
packages these days so things like this I'm likely to miss...


ATB,

Mark.

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 12:22, Romain Dolbeau wrote:

> 2016-05-18 13:06 GMT+02:00 Mark Cave-Ayland
> >:
>> The short version is that the QEMU NVRAM format is different from that
>> of a real SS-5 machine (and indeed QEMU doesn't support NVRAM
>> persistence for that interface yet)
> 
> It's quite easy to fix this if you're willing to patch qemu.
> 
> IIRC: After starting with the SS5 PROM file, reset the (virtual) nvram
> like you would do on a real SS5 with a failed nvram battery. Then from
> the qemu monitor, dump the physical memory for the nvram (now with a
> 'valid' content) in a file. Then just patch qemu to load the data from
> that file after the nvram is initialized (file hw/sparc/sun4m.c, 
> function nvram_init()).
> 
> It also saves a lot of time when you give qemu the full 256 MiB of
> memory, since with a valid nvram the PROM won't check all of the memory.

Last time I looked the problem was that the fw_cfg interface has a fixed
header across all architectures (i.e. some locations towards the
beginning of NVRAM are already accounted for) and there were some
specific issues with the implementation - if you search the QEMU
archives you can find the detail there.

TBH as OpenBIOS will now boot most things (including Solaris) on
qemu-system-sparc, the need for improved NVRAM is greatly reduced as the
main complaint was having to type into the PROM at boot time. IMO time
is better spent elsewhere e.g. improving qemu-system-sparc64 emulation
which is currently where I try and spend my time where possible.


ATB,

Mark.

Re: booting qemu sparc gives black window

[Adrian Davey]

On 2016-05-18 11:44, David Griffith wrote:

On Wed, 18 May 2016, Adrian Davey wrote:


On 2016-05-18 11:27, David Griffith wrote:

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:11, David Griffith wrote:


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d

- simply drop both files into /usr/share/qemu manually and see if 
that

helps.


No change.  Still black.


How strange.

First can you check again with the different display options: 
-display
sdl, -display gtk and -display vnc and see if that changes anything? 
At
least if anything is wrong and you launch these from a terminal you 
may

see some errors on the command line.

Secondly what happens if you remove the -hda part from your command 
line

and just try booting the ISO?


Still black.


package openbios-sparc adds
/usr/share/openbios/QEMU,tcx.bin
/usr/share/openbios/openbios-sparc32
/usr/share/openbios/openbios-sparc64

it could be that qemu is not looking at the correct location, I see 
only symlinks from /usr/share/qemu/ to /usr/share/openbios for 
sparc32/64 files.


Okay.  Now that those video bin files are in the proper place and
named correctly, the graphical window is showing something normal.  I
guess the package is mangled.

Now that that's done, neither "boot 2" nor "boot cdrom" will work.

===begin quote===
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args:
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

Type  help  for more information
ok boot cdrom
Boot device: /iommu/sbus/espdma@5,840/esp@5,880/sd@6,0:d  File 
and args:


Can't open boot device

ok boot 2
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args: 2
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

ok
===end quote===


FYI

BUG #824665 "openbios-sparc: missing QEMU,cgthree.bin file" created, 
once it's included then we can file a bug report for qemu-system-sparc 
to include the symlinks for all the sparc display bin files.


Regards,

Adrian

Re: booting qemu sparc gives black window

[Romain Dolbeau]

2016-05-18 13:06 GMT+02:00 Mark Cave-Ayland :
> The short version is that the QEMU NVRAM format is different from that
> of a real SS-5 machine (and indeed QEMU doesn't support NVRAM
> persistence for that interface yet)

It's quite easy to fix this if you're willing to patch qemu.

IIRC: After starting with the SS5 PROM file, reset the (virtual) nvram like
you would do on a real SS5 with a failed nvram battery. Then from the qemu
monitor, dump the physical memory for the nvram (now with a 'valid'
content) in a file. Then just patch qemu to load the data from that file
after the nvram is initialized (file hw/sparc/sun4m.c,  function
nvram_init()).

It also saves a lot of time when you give qemu the full 256 MiB of memory,
since with a valid nvram the PROM won't check all of the memory.

Cordially,

--
Romain Dolbeau

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:57, David Griffith wrote:

>> Excellent! If you drop the -bios ss5.bin from the command line and use
>> the in-built OpenBIOS ROM then you can use -boot d on the command line -
>> that really is the easiest option IMO.
>>
>> Otherwise you need to manually type "boot disk2:d" into the BIOS on
>> every boot as per
>> http://tyom.blogspot.co.uk/2009/12/solaris-under-qemu-how-to.html.
> 
> Why should the boot command work differently under QEMU from how it
> works on real hardware?

The short version is that the QEMU NVRAM format is different from that
of a real SS-5 machine (and indeed QEMU doesn't support NVRAM
persistence for that interface yet) which is why it appears corrupted to
a real PROM and so it has to ask for the boot device.

OpenBIOS uses the QEMU fw_cfg interface to obtain the boot device
directly from the hypervisor which is why it can do this directly, and
is generally preferred where possible for licensing reasons as the legal
position on distributing real Sun ROMs is unclear.


ATB,

Mark.

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:44, David Griffith wrote:


On Wed, 18 May 2016, Adrian Davey wrote:


On 2016-05-18 11:27, David Griffith wrote:

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:11, David Griffith wrote:


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d


- simply drop both files into /usr/share/qemu manually and see if
that
helps.


No change.  Still black.


How strange.

First can you check again with the different display options: -display
sdl, -display gtk and -display vnc and see if that changes anything? At
least if anything is wrong and you launch these from a terminal you may
see some errors on the command line.

Secondly what happens if you remove the -hda part from your command
line
and just try booting the ISO?


Still black.


package openbios-sparc adds
/usr/share/openbios/QEMU,tcx.bin
/usr/share/openbios/openbios-sparc32
/usr/share/openbios/openbios-sparc64

it could be that qemu is not looking at the correct location, I see
only symlinks from /usr/share/qemu/ to /usr/share/openbios for
sparc32/64 files.


Okay.  Now that those video bin files are in the proper place and named
correctly, the graphical window is showing something normal.  I guess
the package is mangled.

Now that that's done, neither "boot 2" nor "boot cdrom" will work.

===begin quote===
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args:
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

Type  help  for more information
ok boot cdrom
Boot device: /iommu/sbus/espdma@5,840/esp@5,880/sd@6,0:d  File
and args:

Can't open boot device

ok boot 2
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args: 2
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

ok
===end quote===


Excellent! If you drop the -bios ss5.bin from the command line and use
the in-built OpenBIOS ROM then you can use -boot d on the command line -
that really is the easiest option IMO.

Otherwise you need to manually type "boot disk2:d" into the BIOS on
every boot as per
http://tyom.blogspot.co.uk/2009/12/solaris-under-qemu-how-to.html.


Why should the boot command work differently under QEMU from how it works 
on real hardware?



--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:44, David Griffith wrote:

> On Wed, 18 May 2016, Adrian Davey wrote:
> 
>> On 2016-05-18 11:27, David Griffith wrote:
>>> On Wed, 18 May 2016, Mark Cave-Ayland wrote:
>>>
 On 18/05/16 11:11, David Griffith wrote:

>> Ahhh so it appears that Debian have broken QEMU packages for
>> qemu-system-sparc :(
>>
>> You should be able to grab the binaries directly from QEMU git at
>> http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d
>>
>>
>> - simply drop both files into /usr/share/qemu manually and see if
>> that
>> helps.
>
> No change.  Still black.

 How strange.

 First can you check again with the different display options: -display
 sdl, -display gtk and -display vnc and see if that changes anything? At
 least if anything is wrong and you launch these from a terminal you may
 see some errors on the command line.

 Secondly what happens if you remove the -hda part from your command
 line
 and just try booting the ISO?
>>>
>>> Still black.
>>
>> package openbios-sparc adds
>> /usr/share/openbios/QEMU,tcx.bin
>> /usr/share/openbios/openbios-sparc32
>> /usr/share/openbios/openbios-sparc64
>>
>> it could be that qemu is not looking at the correct location, I see
>> only symlinks from /usr/share/qemu/ to /usr/share/openbios for
>> sparc32/64 files.
> 
> Okay.  Now that those video bin files are in the proper place and named
> correctly, the graphical window is showing something normal.  I guess
> the package is mangled.
> 
> Now that that's done, neither "boot 2" nor "boot cdrom" will work.
> 
> ===begin quote===
> Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args:
> Internal loopback test -- Wrong packet length; expected 36, observed 64
> 
> Can't open boot device
> 
> Type  help  for more information
> ok boot cdrom
> Boot device: /iommu/sbus/espdma@5,840/esp@5,880/sd@6,0:d  File
> and args:
> 
> Can't open boot device
> 
> ok boot 2
> Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args: 2
> Internal loopback test -- Wrong packet length; expected 36, observed 64
> 
> Can't open boot device
> 
> ok
> ===end quote===

Excellent! If you drop the -bios ss5.bin from the command line and use
the in-built OpenBIOS ROM then you can use -boot d on the command line -
that really is the easiest option IMO.

Otherwise you need to manually type "boot disk2:d" into the BIOS on
every boot as per
http://tyom.blogspot.co.uk/2009/12/solaris-under-qemu-how-to.html.


ATB,

Mark.

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Adrian Davey wrote:


On 2016-05-18 11:27, David Griffith wrote:

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:11, David Griffith wrote:


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d

- simply drop both files into /usr/share/qemu manually and see if that
helps.


No change.  Still black.


How strange.

First can you check again with the different display options: -display
sdl, -display gtk and -display vnc and see if that changes anything? At
least if anything is wrong and you launch these from a terminal you may
see some errors on the command line.

Secondly what happens if you remove the -hda part from your command line
and just try booting the ISO?


Still black.


package openbios-sparc adds
/usr/share/openbios/QEMU,tcx.bin
/usr/share/openbios/openbios-sparc32
/usr/share/openbios/openbios-sparc64

it could be that qemu is not looking at the correct location, I see only 
symlinks from /usr/share/qemu/ to /usr/share/openbios for sparc32/64 files.


Okay.  Now that those video bin files are in the proper place and named 
correctly, the graphical window is showing something normal.  I guess the 
package is mangled.


Now that that's done, neither "boot 2" nor "boot cdrom" will work.

===begin quote===
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args:
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

Type  help  for more information
ok boot cdrom
Boot device: /iommu/sbus/espdma@5,840/esp@5,880/sd@6,0:d  File and 
args:


Can't open boot device

ok boot 2
Boot device: /iommu/sbus/ledma@5,8400010/le@5,8c0  File and args: 2
Internal loopback test -- Wrong packet length; expected 36, observed 64

Can't open boot device

ok
===end quote===


--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Adrian Davey]

On 2016-05-18 11:27, David Griffith wrote:

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:11, David Griffith wrote:


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d

- simply drop both files into /usr/share/qemu manually and see if 
that

helps.


No change.  Still black.


How strange.

First can you check again with the different display options: -display
sdl, -display gtk and -display vnc and see if that changes anything? 
At
least if anything is wrong and you launch these from a terminal you 
may

see some errors on the command line.

Secondly what happens if you remove the -hda part from your command 
line

and just try booting the ISO?


Still black.


package openbios-sparc adds
/usr/share/openbios/QEMU,tcx.bin
/usr/share/openbios/openbios-sparc32
/usr/share/openbios/openbios-sparc64

it could be that qemu is not looking at the correct location, I see only 
symlinks from /usr/share/qemu/ to /usr/share/openbios for sparc32/64 
files.


Regards,

Adrian

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:32, Adrian Davey wrote:

> package openbios-sparc adds
> /usr/share/openbios/QEMU,tcx.bin
> /usr/share/openbios/openbios-sparc32
> /usr/share/openbios/openbios-sparc64
> 
> it could be that qemu is not looking at the correct location, I see only
> symlinks from /usr/share/qemu/ to /usr/share/openbios for sparc32/64 files.

Yeah, that's definitely missing /usr/share/openbios/QEMU,cgthree.bin
which will be invoked with -vga cg3.

David: you can try removing -vga cg3 and see if can get the framebuffer
to initialise; even if the OS can't use the default TCX framebuffer you
should at least see the yellow OpenBIOS console instead of a black
screen (and confirms that it is the missing QEMU,cgthree.bin ROM which
is the problem).

Given that I've been building QEMU release from git master for years now
and a local test just now works fine, I can't help thinking that this is
related to the Debian packages...


ATB,

Mark.

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:11, David Griffith wrote:


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d

- simply drop both files into /usr/share/qemu manually and see if that
helps.


No change.  Still black.


How strange.

First can you check again with the different display options: -display
sdl, -display gtk and -display vnc and see if that changes anything? At
least if anything is wrong and you launch these from a terminal you may
see some errors on the command line.

Secondly what happens if you remove the -hda part from your command line
and just try booting the ISO?


Still black.

--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:21, John Paul Adrian Glaubitz wrote:

> On 05/18/2016 12:07 PM, Mark Cave-Ayland wrote:
>> Ahhh so it appears that Debian have broken QEMU packages for
>> qemu-system-sparc :(
> 
> Possible license issue. ROM files are always a bit of a problem
> for distributions which actually respect copyrights and make sure
> all packages come with a full source.
> 
> If neither of that is an issue with these ROM files, I suggest
> filing a bug against Debian's qemu package.

Yeah the QEMU,*.bin ROM files are fine as I wrote them myself in Forth
and they are generated as part of the OpenBIOS build for SPARC32 (i.e.
under a GPLv2 license).


ATB,

Mark.

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:11, David Griffith wrote:

>> Ahhh so it appears that Debian have broken QEMU packages for
>> qemu-system-sparc :(
>>
>> You should be able to grab the binaries directly from QEMU git at
>> http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d
>>
>> - simply drop both files into /usr/share/qemu manually and see if that
>> helps.
> 
> No change.  Still black.

How strange.

First can you check again with the different display options: -display
sdl, -display gtk and -display vnc and see if that changes anything? At
least if anything is wrong and you launch these from a terminal you may
see some errors on the command line.

Secondly what happens if you remove the -hda part from your command line
and just try booting the ISO?


ATB,

Mark.

Re: booting qemu sparc gives black window

[John Paul Adrian Glaubitz]

On 05/18/2016 12:07 PM, Mark Cave-Ayland wrote:
> Ahhh so it appears that Debian have broken QEMU packages for
> qemu-system-sparc :(

Possible license issue. ROM files are always a bit of a problem
for distributions which actually respect copyrights and make sure
all packages come with a full source.

If neither of that is an issue with these ROM files, I suggest
filing a bug against Debian's qemu package.

Adrian

-- 
 .''`.  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

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 11:01, David Griffith wrote:


On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 10:47, David Griffith wrote:


Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with
jessie-backports to
no avail.  None of your suggestions worked at all.


Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
you see any of the GTK menus at all around the black screen? What
happens if you try and connect to the framebuffer over VNC, e.g. adding
-vnc :1 to the command line and using a VNC client pointed at
localhost?


No menus at all.  The VNC client window is also black.


The only other thing I can think of is that the Debian packages don't
include the QEMU,cgthree.bin ROM file required to initialise the display
in the device tree. Can you see both this file, QEMU,tcx.bin and
openbios-sparc32 in /usr/share/qemu for your installation?


I see only openbios-sparc32, not QEMU,tcx.bin or QEMU,cgthree.bin.


Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d
- simply drop both files into /usr/share/qemu manually and see if that
helps.


No change.  Still black.

--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 11:01, David Griffith wrote:

> On Wed, 18 May 2016, Mark Cave-Ayland wrote:
> 
>> On 18/05/16 10:47, David Griffith wrote:
>>
> Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with
> jessie-backports to
> no avail.  None of your suggestions worked at all.

 Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
 you see any of the GTK menus at all around the black screen? What
 happens if you try and connect to the framebuffer over VNC, e.g. adding
 -vnc :1 to the command line and using a VNC client pointed at
 localhost?
>>>
>>> No menus at all.  The VNC client window is also black.
>>
>> The only other thing I can think of is that the Debian packages don't
>> include the QEMU,cgthree.bin ROM file required to initialise the display
>> in the device tree. Can you see both this file, QEMU,tcx.bin and
>> openbios-sparc32 in /usr/share/qemu for your installation?
> 
> I see only openbios-sparc32, not QEMU,tcx.bin or QEMU,cgthree.bin.

Ahhh so it appears that Debian have broken QEMU packages for
qemu-system-sparc :(

You should be able to grab the binaries directly from QEMU git at
http://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios;h=1cbe7b99f5fd330fab9880b0d06f0c029b00;hb=a257c741491ff1c3c192d13a89c136dd6401c54d
- simply drop both files into /usr/share/qemu manually and see if that
helps.


ATB,

Mark.

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 10:47, David Griffith wrote:


Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with jessie-backports to
no avail.  None of your suggestions worked at all.


Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
you see any of the GTK menus at all around the black screen? What
happens if you try and connect to the framebuffer over VNC, e.g. adding
-vnc :1 to the command line and using a VNC client pointed at localhost?


No menus at all.  The VNC client window is also black.


The only other thing I can think of is that the Debian packages don't
include the QEMU,cgthree.bin ROM file required to initialise the display
in the device tree. Can you see both this file, QEMU,tcx.bin and
openbios-sparc32 in /usr/share/qemu for your installation?


I see only openbios-sparc32, not QEMU,tcx.bin or QEMU,cgthree.bin.

--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 10:47, David Griffith wrote:

>>> Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with jessie-backports to
>>> no avail.  None of your suggestions worked at all.
>>
>> Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
>> you see any of the GTK menus at all around the black screen? What
>> happens if you try and connect to the framebuffer over VNC, e.g. adding
>> -vnc :1 to the command line and using a VNC client pointed at localhost?
> 
> No menus at all.  The VNC client window is also black.

The only other thing I can think of is that the Debian packages don't
include the QEMU,cgthree.bin ROM file required to initialise the display
in the device tree. Can you see both this file, QEMU,tcx.bin and
openbios-sparc32 in /usr/share/qemu for your installation?


ATB,

Mark.

Re: booting qemu sparc gives black window

[David Griffith]

On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 10:34, David Griffith wrote:


On Wed, 18 May 2016, Mark Cave-Ayland wrote:


On 18/05/16 10:02, David Griffith wrote:


I've been trying to boot an old debian ISO under qemu sparc, but all I
can get is a black screen unless I use the -nographic option.  I start
with this:

qemu-img create -f qed sparcdisk.img 2G

Then this:

qemu-system-sparc -bios ss5.bin -vga cg3 -g 1152x900 -hda sparcdisk.img
-cdrom debian-40r9-sparc-netinst.iso

My host system is Debian 8.


Which version of QEMU is supplied with Debian 8? On a recent QEMU you
should find that OpenBIOS will boot all OSs on SS-5 machines, so no need
to provide an external ROM image. The following should work for you and
give a 1024x768 framebuffer:

qemu-system-sparc -vga cg3 -hda sparcdisk.img -cdrom
debian-40r9-sparc-netinst.iso -boot d

Otherwise I've just tried the following locally and it works fine here
on QEMU 2.6:

qemu-system-sparc -vga cg3 -cdrom debian-31r1a-sparc-businesscard.iso
-bios ss5.bin

Before each QEMU release I tend to boot debian-31r1a and debian-40r4a
ISOs through to userspace to make sure there are no regressions so I
would expect this to work.


Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with jessie-backports to
no avail.  None of your suggestions worked at all.


Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
you see any of the GTK menus at all around the black screen? What
happens if you try and connect to the framebuffer over VNC, e.g. adding
-vnc :1 to the command line and using a VNC client pointed at localhost?


No menus at all.  The VNC client window is also black.

--
David Griffith
d...@661.org

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 10:02, David Griffith wrote:

> I've been trying to boot an old debian ISO under qemu sparc, but all I
> can get is a black screen unless I use the -nographic option.  I start
> with this:
> 
> qemu-img create -f qed sparcdisk.img 2G
> 
> Then this:
> 
> qemu-system-sparc -bios ss5.bin -vga cg3 -g 1152x900 -hda sparcdisk.img
> -cdrom debian-40r9-sparc-netinst.iso
> 
> My host system is Debian 8.

Which version of QEMU is supplied with Debian 8? On a recent QEMU you
should find that OpenBIOS will boot all OSs on SS-5 machines, so no need
to provide an external ROM image. The following should work for you and
give a 1024x768 framebuffer:

qemu-system-sparc -vga cg3 -hda sparcdisk.img -cdrom
debian-40r9-sparc-netinst.iso -boot d

Otherwise I've just tried the following locally and it works fine here
on QEMU 2.6:

qemu-system-sparc -vga cg3 -cdrom debian-31r1a-sparc-businesscard.iso
-bios ss5.bin

Before each QEMU release I tend to boot debian-31r1a and debian-40r4a
ISOs through to userspace to make sure there are no regressions so I
would expect this to work.


ATB,

Mark.

Re: booting qemu sparc gives black window

[Mark Cave-Ayland]

On 18/05/16 10:34, David Griffith wrote:

> On Wed, 18 May 2016, Mark Cave-Ayland wrote:
> 
>> On 18/05/16 10:02, David Griffith wrote:
>>
>>> I've been trying to boot an old debian ISO under qemu sparc, but all I
>>> can get is a black screen unless I use the -nographic option.  I start
>>> with this:
>>>
>>> qemu-img create -f qed sparcdisk.img 2G
>>>
>>> Then this:
>>>
>>> qemu-system-sparc -bios ss5.bin -vga cg3 -g 1152x900 -hda sparcdisk.img
>>> -cdrom debian-40r9-sparc-netinst.iso
>>>
>>> My host system is Debian 8.
>>
>> Which version of QEMU is supplied with Debian 8? On a recent QEMU you
>> should find that OpenBIOS will boot all OSs on SS-5 machines, so no need
>> to provide an external ROM image. The following should work for you and
>> give a 1024x768 framebuffer:
>>
>> qemu-system-sparc -vga cg3 -hda sparcdisk.img -cdrom
>> debian-40r9-sparc-netinst.iso -boot d
>>
>> Otherwise I've just tried the following locally and it works fine here
>> on QEMU 2.6:
>>
>> qemu-system-sparc -vga cg3 -cdrom debian-31r1a-sparc-businesscard.iso
>> -bios ss5.bin
>>
>> Before each QEMU release I tend to boot debian-31r1a and debian-40r4a
>> ISOs through to userspace to make sure there are no regressions so I
>> would expect this to work.
> 
> Debian 8 installs QEMU 2.5.  I upgraded to 2.6 with jessie-backports to
> no avail.  None of your suggestions worked at all.

Hmmm I wonder if what you're seeing is a framebuffer issue with GTK? Do
you see any of the GTK menus at all around the black screen? What
happens if you try and connect to the framebuffer over VNC, e.g. adding
-vnc :1 to the command line and using a VNC client pointed at localhost?


ATB,

Mark.