Previous Thread
Next Thread
Print Thread
Page 1 of 3 1 2 3
sdl mame64 unresponsive #112642
02/16/18 02:41 AM
02/16/18 02:41 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Hi guys, I'm encountering a problem, dunno if it's just me or not. I'm on Ubuntu 17.10, with an nVidea GeForce GTX 970M. I doubt that matters much, but basically, if I launch mame64, the program will hang and never get to the menu. I did the following:

Code
git checkout mame0194
make clean
make -j 7
./mame64 -w


The very first time I do this, it will take a long time, but it will eventually come up with the UI. Then if I reboot my laptop and try again, it will launch, and it may say "Initializing" but it will never bring up the menu or accept input. (I'm using -w so that I don't go fullscreen and lose control of the laptop.) If I try
Code
mame64 -w pacman
, it will also say "Initializing" and never come back. I always have to Force Quit the app, it won't respond to anything else.

I don't know if I've provided enough detail, but this did not used to be a problem. I only noticed it recently, so just to be on the safe side, I tried checking out mame0193 instead and trying that instead. I got the same results. Is there a verbose debug mode that logs out what's going on and why it's getting stuck?

Thanks very much for your help.

Last edited by Procyon; 02/16/18 02:56 AM.
Re: sdl mame64 unresponsive [Re: Procyon] #112643
02/16/18 02:50 AM
02/16/18 02:50 AM
Joined: Mar 2001
Posts: 16,020
USA
R
R. Belmont Offline
Very Senior Member
R. Belmont  Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,020
USA
Try -verbose.

Re: sdl mame64 unresponsive [Re: R. Belmont] #112644
02/16/18 02:58 AM
02/16/18 02:58 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Thank you, shoulda thought of that. Here we go:
Code
Available videodrivers: x11 mir wayland dummy 
Current Videodriver: x11
	Display #0
		Renderdrivers:
			    opengl (0x0)
			 opengles2 (0x0)
			  software (0x0)
Available audio drivers: 
	pulseaudio          
	alsa                
	sndio               
	dsp                 
	disk                
	dummy               
Build version:      0.193 (mame0193)
Build architecure:  
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 
Build defines 1:    LSB_FIRST=1 PTR64=1 
SDL/OpenGL defines: SDL_COMPILEDVERSION=2006 USE_OPENGL=1 
Compiler defines A: __GNUC__=7 __GNUC_MINOR__=2 __GNUC_PATCHLEVEL__=0 __VERSION__="7.2.0" 
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1 
Compiler defines C: __USE_FORTIFY_LEVEL=0 
Enter init_monitors
Adding monitor screen0 (1920 x 1080)
Leave init_monitors
Enter sdlwindow_init

Hints:
	SDL_FRAMEBUFFER_ACCELERATION             (null)
	SDL_RENDER_DRIVER                        (null)
	SDL_RENDER_OPENGL_SHADERS                (null)
	SDL_RENDER_SCALE_QUALITY                 (null)
	SDL_RENDER_VSYNC                         (null)
	SDL_VIDEO_X11_XVIDMODE                   (null)
	SDL_VIDEO_X11_XINERAMA                   (null)
	SDL_VIDEO_X11_XRANDR                     (null)
	SDL_GRAB_KEYBOARD                        (null)
	SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS         (null)
	SDL_IOS_IDLE_TIMER_DISABLED              (null)
	SDL_IOS_ORIENTATIONS                     (null)
	SDL_XINPUT_ENABLED                       (null)
	SDL_GAMECONTROLLERCONFIG                 (null)
	SDL_JOYSTICK_ALLOW_BACKGROUND_EVENTS     (null)
	SDL_ALLOW_TOPMOST                        (null)
	SDL_TIMER_RESOLUTION                     (null)
	SDL_RENDER_DIRECT3D_THREADSAFE           (null)
	SDL_VIDEO_ALLOW_SCREENSAVER              (null)
	SDL_ACCELEROMETER_AS_JOYSTICK            (null)
	SDL_MAC_CTRL_CLICK_EMULATE_RIGHT_CLICK   (null)
	SDL_VIDEO_WIN_D3DCOMPILER                (null)
	SDL_VIDEO_WINDOW_SHARE_PIXEL_FORMAT      (null)
	SDL_VIDEO_MAC_FULLSCREEN_SPACES          (null)
	SDL_MOUSE_RELATIVE_MODE_WARP             (null)
	SDL_RENDER_DIRECT3D11_DEBUG              (null)
	SDL_VIDEO_HIGHDPI_DISABLED               (null)
	SDL_WINRT_PRIVACY_POLICY_URL             (null)
	SDL_WINRT_PRIVACY_POLICY_LABEL           (null)
	SDL_WINRT_HANDLE_BACK_BUTTON             (null)
Leave sdlwindow_init
Enter sdl_info::create
Audio: Start initialization
Audio: Driver is pulseaudio
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 25600 bytes
Audio: End initialization
Keyboard: Start initialization
Input: Adding keyboard #0: System keyboard (device id: System keyboard)
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding mouse #0: System mouse (device id: System mouse)
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Searching font Liberation Sans in -. path/s
Matching font: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf
Region ':user1' created
Killed


It reached that "Region ':user1' created" line and sat there for a good two minutes before I killed it.

Last edited by Procyon; 02/16/18 03:00 AM.
Re: sdl mame64 unresponsive [Re: Procyon] #112645
02/16/18 02:59 AM
02/16/18 02:59 AM
Joined: Apr 2006
Posts: 702
USA
Tafoid Offline
Senior Member
Tafoid  Offline
Senior Member
Joined: Apr 2006
Posts: 702
USA
Originally Posted by Procyon
Hi guys, I'm encountering a problem, dunno if it's just me or not. I'm on Ubuntu 17.10, with an nVidea GeForce GTX 970M. I doubt that matters much, but basically, if I launch mame64, the program will hang and never get to the menu. I did the following:

Code
git checkout mame0194
make clean
make -j 7
./mame64 -w


The very first time I do this, it will take a long time, but it will eventually come up with the UI. Then if I reboot my laptop and try again, it will launch, and it may say "Initializing" but it will never bring up the menu or accept input. (I'm using -w so that I don't go fullscreen and lose control of the laptop.) If I try
Code
mame64 -w pacman
, it will also say "Initializing" and never come back.

I don't know if I've provided enough detail, but this did not used to be a problem. I only noticed it recently, so just to be on the safe side, I tried checking out mame0193 instead and trying that instead. I got the same results. Is there a verbose debug mode that logs out what's going on and why it's getting stuck?

Thanks very much for your help.


A few things to try:

First of, use -verbose trigger. This will detail a lot fo the initialization process and may help you discover an issue.
Try alternative video modes: -video opengl -video bgfx -video soft
Check other running programs. I've come across an issue with another person having problems using "vjoy".
Unplug, one at a time, your USB devices. There could be a possible conflict or inability to read a controller or other.




Re: sdl mame64 unresponsive [Re: Tafoid] #112646
02/16/18 03:04 AM
02/16/18 03:04 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Originally Posted by Tafoid
First of, use -verbose trigger. This will detail a lot fo the initialization process and may help you discover an issue.
Try alternative video modes: -video opengl -video bgfx -video soft
Check other running programs. I've come across an issue with another person having problems using "vjoy".
Unplug, one at a time, your USB devices. There could be a possible conflict or inability to read a controller or other.


Thanks Tafoid, verbose output provided above. I had tried opengl and bgfx, hadn't tried soft, but I got the same thing. No other running programs, this will happen right after a reboot. No vjoy either (isn't that a Windows only thing? Or is there vjoy for linux?) Nothing plugged into USB.

Re: sdl mame64 unresponsive [Re: Procyon] #112647
02/16/18 03:36 AM
02/16/18 03:36 AM
Joined: Apr 2006
Posts: 702
USA
Tafoid Offline
Senior Member
Tafoid  Offline
Senior Member
Joined: Apr 2006
Posts: 702
USA
Originally Posted by Procyon
Originally Posted by Tafoid
First of, use -verbose trigger. This will detail a lot fo the initialization process and may help you discover an issue.
Try alternative video modes: -video opengl -video bgfx -video soft
Check other running programs. I've come across an issue with another person having problems using "vjoy".
Unplug, one at a time, your USB devices. There could be a possible conflict or inability to read a controller or other.


Thanks Tafoid, verbose output provided above. I had tried opengl and bgfx, hadn't tried soft, but I got the same thing. No other running programs, this will happen right after a reboot. No vjoy either (isn't that a Windows only thing? Or is there vjoy for linux?) Nothing plugged into USB.


Your verbose output mentions that you are using MAME 0.193, not MAME 0.194.
Can you try 0.193 here? http://sdlmame.wallyweek.org/download




Re: sdl mame64 unresponsive [Re: Tafoid] #112648
02/16/18 03:57 AM
02/16/18 03:57 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Yeah, like I said, I synced to 0.193 recently to see if it was a new problem with 0.194, or something I was experiencing across all versions of MAME. Do you want me to download your source and compile from that? Or install the .deb? I'm sort of leery about doing that because I have things tuned to work well in a dual-boot environment and I don't want to screw that up, but I'll try it if you think it will help.

Re: sdl mame64 unresponsive [Re: Procyon] #112649
02/16/18 04:44 AM
02/16/18 04:44 AM
Joined: Apr 2006
Posts: 702
USA
Tafoid Offline
Senior Member
Tafoid  Offline
Senior Member
Joined: Apr 2006
Posts: 702
USA
I'm honestly not sure. The person who packages them has done it for a long time so it is a reliable source and linked from the mamedev.org downloads page. Since I am only using Windows, I can't really advise further. I'll leave you to other non-Windows Dev and Users who may have experience with your issues.

Good Luck!




Re: sdl mame64 unresponsive [Re: Procyon] #112654
02/16/18 01:04 PM
02/16/18 01:04 PM
Joined: Mar 2001
Posts: 16,020
USA
R
R. Belmont Offline
Very Senior Member
R. Belmont  Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,020
USA
Does your ROM path point to an NFS or other remote server? That's one thing that could be consistent with what you're seeing if there's some network problem accessing the ROMs.

Re: sdl mame64 unresponsive [Re: R. Belmont] #112655
02/16/18 01:30 PM
02/16/18 01:30 PM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Originally Posted by R. Belmont
Does your ROM path point to an NFS or other remote server? That's one thing that could be consistent with what you're seeing if there's some network problem accessing the ROMs.


No, they're on my NTFS partition, which is mounted to Ubuntu through /media/procyon/Data. Here's the verbose output of when I try to load pacman from the command line. As you can see, it doesn't seem to have any problems finding the files.

Code
Available videodrivers: x11 mir wayland dummy 
Current Videodriver: x11
	Display #0
		Renderdrivers:
			    opengl (0x0)
			 opengles2 (0x0)
			  software (0x0)
Available audio drivers: 
	pulseaudio          
	alsa                
	sndio               
	dsp                 
	disk                
	dummy               
Build version:      0.193 (mame0193)
Build architecure:  
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 
Build defines 1:    LSB_FIRST=1 PTR64=1 
SDL/OpenGL defines: SDL_COMPILEDVERSION=2006 USE_OPENGL=1 
Compiler defines A: __GNUC__=7 __GNUC_MINOR__=2 __GNUC_PATCHLEVEL__=0 __VERSION__="7.2.0" 
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1 
Compiler defines C: __USE_FORTIFY_LEVEL=0 
Enter init_monitors
Adding monitor screen0 (1920 x 1080)
Leave init_monitors
Enter sdlwindow_init

Hints:
	SDL_FRAMEBUFFER_ACCELERATION             (null)
	SDL_RENDER_DRIVER                        (null)
	SDL_RENDER_OPENGL_SHADERS                (null)
	SDL_RENDER_SCALE_QUALITY                 (null)
	SDL_RENDER_VSYNC                         (null)
	SDL_VIDEO_X11_XVIDMODE                   (null)
	SDL_VIDEO_X11_XINERAMA                   (null)
	SDL_VIDEO_X11_XRANDR                     (null)
	SDL_GRAB_KEYBOARD                        (null)
	SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS         (null)
	SDL_IOS_IDLE_TIMER_DISABLED              (null)
	SDL_IOS_ORIENTATIONS                     (null)
	SDL_XINPUT_ENABLED                       (null)
	SDL_GAMECONTROLLERCONFIG                 (null)
	SDL_JOYSTICK_ALLOW_BACKGROUND_EVENTS     (null)
	SDL_ALLOW_TOPMOST                        (null)
	SDL_TIMER_RESOLUTION                     (null)
	SDL_RENDER_DIRECT3D_THREADSAFE           (null)
	SDL_VIDEO_ALLOW_SCREENSAVER              (null)
	SDL_ACCELEROMETER_AS_JOYSTICK            (null)
	SDL_MAC_CTRL_CLICK_EMULATE_RIGHT_CLICK   (null)
	SDL_VIDEO_WIN_D3DCOMPILER                (null)
	SDL_VIDEO_WINDOW_SHARE_PIXEL_FORMAT      (null)
	SDL_VIDEO_MAC_FULLSCREEN_SPACES          (null)
	SDL_MOUSE_RELATIVE_MODE_WARP             (null)
	SDL_RENDER_DIRECT3D11_DEBUG              (null)
	SDL_VIDEO_HIGHDPI_DISABLED               (null)
	SDL_WINRT_PRIVACY_POLICY_URL             (null)
	SDL_WINRT_PRIVACY_POLICY_LABEL           (null)
	SDL_WINRT_HANDLE_BACK_BUTTON             (null)
Leave sdlwindow_init
Enter sdl_info::create
Audio: Start initialization
Audio: Driver is pulseaudio
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 25600 bytes
Audio: End initialization
Keyboard: Start initialization
Input: Adding keyboard #0: System keyboard (device id: System keyboard)
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding mouse #0: System mouse (device id: System mouse)
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Searching font Liberation Sans in -. path/s
Matching font: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf
Region ':maincpu' created
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: found /media/procyon/Data/MAME/roms/puckman.zip ECD
unzip: /media/procyon/Data/MAME/roms/puckman.zip has no ZIP64 ECD locator
unzip: read /media/procyon/Data/MAME/roms/puckman.zip central directory
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
Region ':gfx1' created
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
Region ':proms' created
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
Region ':namco' created
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
unzip: found /media/procyon/Data/MAME/roms/puckman.zip in cache
unzip: opened archive file /media/procyon/Data/MAME/roms/puckman.zip
unzip: closing archive file /media/procyon/Data/MAME/roms/puckman.zip and sending to cache
Killed

Page 1 of 3 1 2 3

Moderated by  R. Belmont 

Who's Online Now
4 registered members (Stiletto, drewcifer, Lord Nightmare, AJR), 90 guests, and 2 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,587
Posts112,169
Members4,817
Most Online283
Oct 11th, 2018
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.051s Queries: 14 (0.024s) Memory: 5.7324 MB (Peak: 5.9504 MB) Zlib enabled. Server Time: 2018-10-18 01:20:24 UTC