-
-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird problem with screen not being cleared #9
Comments
Strange, I haven't seen any such problems so far. I usually have the emulator running without GUI also, but I can quit it normally (there is a slight delay of a few seconds sometimes, until the audio thread is terminated, but it will exit cleanly). Are you on the latest DietPi (v130)? |
Thanks for the report. Could you please send us a bug report? I'd like to check your current installation and settings. @midwan |
Sure i can! :) Only one question: Do i have to run dietpi-bugreport after or before killing the systemd-journald process? See ya and thanks for the quick response! :) P.D: I'm using this DietPi version: http://dietpi.com/downloads/images/DietPi-AmiBerry_RPi-armv6-%28Jessie%29.7z . But the uae4arm im using is the midwan one. |
After please, but dont kill the systemd-journald process until after the bug report is sent. |
My tests:
Unable to replicate when using either autostart method:
Unable to replicate with @ariath Some questions while we wait for bug report:
|
This the bugreport reference code: eaf73419-df52-422e-830a-bca42c70c495-0 . I used the DietPi-AmiBerry image from here: http://blitterstudio.com/amiberry/ (the one in the installation step). The only additional software i remember have installed is ProFTP (from DietPi-Software) and the required ones to download and build uae4arm (gcc, make, git, etc ...). I remember that the uae4arm config i'm using is one i copied from my Android tablet, and the only changes i did in the system are the required ones to configure the WiFi and Bluetooth. See ya! P.D: What i see really strange is that the emulator exits just fine if i use use_gui=yes. I only get this behaviour when i use use_gui=no :S. P.D 2: I include the config i'm using for the emulator (autostart is currently a symbolic link to this config) P.D 3: BTW, what does this lines could mean? :S |
Excellent, i'll take a look 👍
Thats most likely the cause. But i'll run some tests to confirm. Edit: Would you be able to upload your android |
It is the Amiga 500.txt that i attached in the previous post :) . What i did was:
See ya! |
@ariath Diff check: https://www.diffchecker.com/fJQnDH5S
|
Replicated | Uae4arm menu remains visible under
|
@ariath
|
Thanks for the confirmation, I'll look into this. |
After some testing, i think xinit was the problem. I removed it from the script and, not only the screen is now clear after resuming the emulation, but the emulator finally exits correctly . Anyways, here is the requested info: root@AmigaPi:~# df -h root@AmigaPi:~# ls -lha / But, doing some testing, i have another "bug" (seems to be ALSA audio): sep 14 19:25:07 AmigaPi systemd[1]: Unit uae4arm-rpi.service entered failed state. This happens when i navigate through the GUI with the keyboard arrows. But i can open a terminal from SSH and kill the processes with htop, so, only the emulator, or the X session, is freezing. See ya! |
The system is configured to run it as a service, so if it detects it has stopped it will try to re-run it automatically. If you want to start it manually, you should disable the service with: |
No, it is okay this way, i want the emulator to boot with the Pi :). But, what about this line? Also, i wonder... why the default script runs the emulator with xinit if it is not required? See ya! |
Looks like a ALSA buffer underrun. Which is strange because i believe your Try running Uae4arm at a higher priority:
You could even try scheduler FIFO (high priority, similar to realtime), but, its untested with uae4arm.
Excellent 👍 And thanks for pasting those results.
I believe this was a added to fix an issue with keyboard LEDS on 1st release: https://github.com/Fourdee/DietPi/issues/474#issuecomment-243847858 |
@ariath The cachesize=8192 is probably the JIT cache, not the audio buffer. :) Also, it's probably obsolete since the emulator uses a fixed number internally (8192) anyway, and doesn't use the config value at all. It's there for config compatibility reasons with WinUAE. If the suggestion to run UAE at a higher priority does help the underrun issue, I'd be grateful if you could tell us so. Finally, the xinit was added to get proper support for the Caps Lock key, since it didn't seem to work when started from the console, as @Fourdee mentioned. This is also something that will be fixed eventually. |
I have tried setting the emulator priority to -5, but, as soon i navigate with the keyboard keys to the Quit button, it freezes. But... this time, i didn't get any ALSA error message :S. What i wonder is... why this happens only with the Quit button, and, why only happens when i use the keyboard cursor keys to select the control? When i use the mouse all goes fine :S. See ya! P.D: Well, i think i was wrong. The emulator don't freezes upon selecting the Quit button. |
@ariath I didn't have time to test this one yet, so bear with me... :)
|
No problem, i was also quite busy yerterday XD. I have done some tests today, and i have found a couple of places where the emulator freezes (basically, its CPU usage goes to 99%): Miscellaneus tab, Input tab and the Reset button. All you have to try is to navigate with the cursor keys. Is then when, if i try to navigate left or right (i repeat, the cursor si currently over the Reset button), the emulator freezes. At the Input tab, i have noticed the freeze at the mouse sensivity slider, and in the Miscellaneus one, going down through the check boxes. I wonder if the problem would happen with a gamepad also. I have a sixaxis, but i haven't tried to pair it with the Pi yet :S. See ya! P.D: Also, the resolution sliders have a slight problem: If you slide them to the right, they are fine, but... if you try to slide them to the left... the cursor go back to the section tabs :P. P.D 2: And yes, i only have problems with the keyboard. I have not experienced any problem with the mouse. |
@ariath Thanks for that detailed report, I will test it out and see. |
@Fourdee Thanks for that extra info, I'll take a look. It's probably running in a loop waiting to detect any input events, and updating the UI on VSync. |
Confirmed - Emulator GUI freezes when navigating with keyboard, if you are on the Reset button and press Left/Right keys. Also, 100% CPU usage in GUI, even without it actually doing anything. I'll get it fixed. |
- When using the keyboard to navigate, the GUI would get stuck if you pressed LEFT/RIGHT when focused on the Reset button. - Fixed Display slider Left/Right navigation (Left would get Display focused instead of moving the slider)
The latest commit fixes the navigation issues. I'll see what we can do about the high CPU usage in the GUI. |
There are 2 more places where i have noticed freezes: Miscellaneus tab: There are 3 checkboxes and two another controls below them (as i remember). The emulator freezes when the cursor is placed at the last checkbox and and you press down to go to the other two controls. Input tab: The freeze happens at the mouse sensivity slider. See ya! |
@ariath Thanks for reporting these, I'll get it fixed! |
The GUI would freeze if you pressed down when on the "bsdsocket.library" checkbox, in the Miscellaneous section.
I've added a fix for the GUI getting stuck there, I will also add the possibility to go down to the Numlock LED and ScrollLock LED options as the next step (those controls are new so the navigation would not go there). |
I'm using a RPi 3 with DietPi.
I have noticed that the screen don't get cleared when you resume the emulation, as there are chunks of the config GUI around the screen.
I have experienced another strange bug: If i configure the autostart config to not use the GUI, when i try to exit the emulator the systemd-journald process starts eating the 99% of the CPU and i cannot exit the emulator unless i open another console and kill the systemd-journald process.
Then, if i execute "journalctl -r", i get a lot of entries like these ones:
bash[101]: IP: 0x76ece624 [e5820000] 0xa7804664
bash[101]: processed: 0x76ece620
As i said, this only happens when i quit the emulator after the autostart config was autoloaded.
See ya!
The text was updated successfully, but these errors were encountered: