NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

xsrc/55984: OpenGL works in gdb, window remains black when run normally



>Number:         55984
>Category:       xsrc
>Synopsis:       OpenGL works in gdb, remains black when run normally
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    xsrc-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 09 21:20:00 +0000 2021
>Originator:     Rhialto
>Release:        NetBSD 9.1
>Organization:
>Environment:
System: NetBSD murthe.falu.nl 9.1 NetBSD 9.1 (GENERIC) #0: Sun Oct 18 19:24:30 UTC 2020 mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
    With the Amiga emulator emulators/fs-uae, I have the following problem.
    Tried with pkgsrc-2020Q4 but the problem exists for a while, probably
    since I updated to NetBSD-9.0.

    - If I run it normally, I get a black (emulated) screen.
    - If I run it from gdb, it appears to work. At least the user
      interface is visible, and if you have a (non-free) Kickstart
      image, I get the boot screen. With a (free) AROS kickstart
      replacement, I get at least the GUI.
    - I have Driver "radeon" in my xorg.conf; probably #Driver
      "modesetting" didn't work so well.
      [    31.845] (--) RADEON(0): Chipset: "ATI Radeon HD 5450" (ChipID = 0x68f9)
    - It also fails on my laptop with Intel i945 chipset and Driver
      "modesetting" (where the "intel" driver failed horribly in
      general).
    - I'm using "native X" for both cases.
    - On all this hardware, fs-uae worked fine at some time in the past.
    - I have a report upstream but more likely it is a NetBSD problem;
      https://github.com/FrodeSolheim/fs-uae/issues/246

>How-To-Repeat:
    How to reproduce:

    - Build emulators/fs-uae
    - Run it once so that it sets up some directories in ~/FS-UAE
    - Obtain aros-rom.bin as follows:
      - on http://www.aros.org/nightly1.php download any version of
	amiga-m68k-boot-iso
      - unzip, and extract from the .iso image the file
	boot/amiga/aros-rom.bin
      - For your convenience I have placed the file at
	https://www.falu.nl/~rhialto/aros-rom.bin
    - Place aros-rom.bin in ~/FS-UAE/Kickstarts . We need it only as a
      ROM that gets accepted by fs-uae, it doesn't seem to work
      otherwise, at least in the test configuration.
    - Create the configuration file ~/FS-UAE/Configurations/Aros.fs-uae:

[fs-uae]
amiga_model = A1200
kickstart_file = aros-rom.bin

    - Run the command    fs-uae ~/FS-UAE/Configurations/Aros.fs-uae
    - Observe that you get a window that remains uniformly black.
    - When you press F12, nothing changes.
    - If your mouse gets captured, press the middle button to
      un-capture.
    - ^C this run.
    - Run the command    gdb --args fs-uae
      ~/FS-UAE/Configurations/Aros.fs-uae
    - Type "r" to the (gdb) prompt
    - Observe that you get at least a slightly-less black part in the
      center of the window and some stripes flash sometimes.
    - If you hit F12, you get the GUI and can quit normally (navigate to
      the X in the top right and hit enter)

    I wonder if this is somehow related to another weirdness I have
    observed in emulators/vice. Using the gtk3-version, the first time I
    start it after a (re)boot, it fails to initialize something with GL.
    The next time it works.
>Fix:
    Not known...

-Olaf.
-- 
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___  Anyone who is capable of getting themselves made President should on
\X/  no account be allowed to do the job.       --Douglas Adams, "THGTTG"



Home | Main Index | Thread Index | Old Index