Rockbox Technical Forums
Support and General Use => Plugins/Viewers => Topic started by: sss on April 15, 2010, 06:09:34 PM
-
Rockdoom is broken on at least the Nano 1G in newer SVN firmwares (tested r25650). 3.5.1 works, I even compiled the 3.5.1 source (http://download.rockbox.org/release/3.5.1/rockbox-3.5.1.7z) with the scrollwheel patch and that works fine. Some people do not seem to be experiencing this, why are some Nanos behaving differently?
Doom will crash with semi-random errors, sometimes it will run if you change a wad file name temporarily to upper or lower case, but then will generate a DATA ABORT crash shortly after displaying the title screen. Sometimes if you can get to the title screen it will look corrupted. That's not all. The text in the rockbox menus is weird, some letters have been replaced with letters 1 value up. Funny but true: one of them read, "Fart-forward". It's always random letters being replaced with the preceding letters (b->a, y->x, etc). I thought my partition was corrupt or something but none of these problems occur with 3.5.1. I like the new features in the newer versions, but I do not like the bugs.
-
Can you check your file system for errors? The strange character substitution makes me suspect there might be some file system corruption at play. It will be good to exclude this possibility before looking for other causes.
I don't have any problem running Doom on my F40 with r25652 (nor am I seeing character substitutions).
-
Before I posted, I had already checked the filesystem for errors. I just reformatted the fat32 partition, copying over a fresh copy of r25652 and I still have the same problems. In addition, the device is very slow to transfer, getting rates of about 1-2MB/s over USB2. I don't know if this is normal for a nano since I bought it for rockbox (and don't like the apple firmware). Nevertheless the slowness is ridiculous.
___
Wait, after rebooting again, the fonts look normal, and rockdoom runs! However, rockdoom is definitely unstable now (unlike before), crashing when loading a new game while currently playing or transitioning between levels.
Going from LVL 1to LVL 2 doom2.wad --> data abort at 01fc14dc (0)
So 3.5.1 definitely has something right that the new firmwares do not have, otherwise I would be seeing the same sorts of problems there. I think I will be sticking with my 3.5.1 build until they fix the newer revisions.
-
Given that you're the only person experiencing this problem, it can't be fixed until you track down what the problem is.
But Chronon is right in that it looks very strongly like your flash was having issues, and the fact that 3.5.1 is working could just be luck in terms of which parts of the disk things are currently written to, or what other stresses your device was under at the time. The fact that a reboot seems to have changed the symptoms *strongly* suggests it's hardware related - something is on the verge of going out.
-
Are you saying the flash is going bad? I've tested the newer builds again and again with the same problems, and flash writes to different locations all of the time, so if that were true, it would work some of the time!
Who can be sure if I am the only one with this problem?
Is there a way to reformat or reset a nano beyond fat partition reformatting?
-
If you really don't believe it's a problem with your nano, do a binary search and track down the individual commit that began the problem.
-
Where do I find the committed changes and dates? Got a link?
-
You shouldn't really need to look at those - you should be starting with a known good build and binary searching toward the current build until you have a specific revision number that you know is the problem.
It's actually better if you don't look at the logs too much before then - going in with specific expectation can cause accidental jumping to conclusions. Each one should be tested pretty thoroughly even if it seems to work at first (come up with a series of tests, and run them multiple times across a few reboots).
-
It would be nice to know what subversion revision 3.5.1 is so I would have a place to start.
-
It's tagged in SVN (and a branch any way, so the regular commit log wouldn't have shown you necessarily where it is). Just checking out the right revision, instead of specifically using the release branch, wouldn't necessarily get you the right thing to use.
-
I'd like to
tentatively close this thread. (Safe to be deleted)
The doom bug is still there and a hard crash will result in one of many possible character glitches, but I will resolve this in my new thread I've opened elsewhere.