FS#12721 - Doom hangs on "Starting Graphics engine"
I downloaded the doom.WAD file from the extras page on rockbox.org
When I run Doom I get the menu and can change settings. But when I click “Play” it runs some dialog on the screen then stops on “Starting Graphics engine”
The full text on the screen is:
S_Init: Setting up sound.
HU_Init: Setting up heads up display.
Starting Graphics engine
The only way I can find to leave this screen is to hold Menu + Select until rockbox reboots.
The Build I am using is: 9dd2eb4-120729
Closed by speachy
2020-07-14 15:05
Reason for closing: Out of Date
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
2020-07-14 15:05
Reason for closing: Out of Date
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
As of mid-2019, this doesn't appear
to be an issue any more.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Ive tested it with versions as new as 71778bd-121007
and it still doesnt work
Same problem on an iPod Classic 7G.
Build ID is 50f0dd8-140310.
Doom was installed using the Rockbox Utility.
Are the timer APIs implemented? IIRC Gigabeat S would lock there until the timer was implemented.
I couldn't find this piece of information, sorry - i'm a beginner here. How could i check if the timer is implemented in the current build?
Gerrit #912 fixes this (on the classic at least), but it has not been throughly tested yet, and the underlying bug (in the timer subsystem) has not been fixed.