Hey Mark..
I tried your config settings and got 0000.73 & 0000.83 sigkill err.. (if I flip through visuals it happens the moment I hit Borgbeat)
But only with the Borgbeat visual... [3d cube] so far I can't seem to get the other visuals to produce this...
Do the error codes translate to anything meaningful?
They are "playlist_fid" dot "track_number". Playlist 0000 is your "master" (down-down-down) playlist, and the track numbers seem to be just about everything.
So something else is wrong, nobody has that many bad tracks.
A few possibilities:
- Bit errors in the empeg SRAM chips (dubious).
- IDE header issues (again doubtful in this case, because it should cause even more severe issues).
- Not enough available RAM for the player (still possible, I guess: try ReserveCache=64 ?).
- Bad data in the player's dynamic data partition.
Several others here have been unable to run v3alpha successfully, and simply went back to v2.01 without the same issues. You could do that, I suppose. But if most of us *can* run v3, then there's gotta be something fixable.
The variable is the dynamic data partition, aka
/dev/hda3. You could zero that out and see if things improve.
So, what I would do in your situation is the following:
- Run set_empeg_max_fid to patch the player for large numbers of tracks. Regardless.
- Then, nuke the dynamic data partition: connect via serial, and hit Control^C to kill off the player.
- Now nuke the dynamic data, and force a database rebuild, using the following sequence of commands:
cat /dev/zero > /dev/hda3
rwm
rm /empeg/var/[dtp]*
player -i
## wait for the player to rebuild databases and start up,
## then hit Control^C again, and continue with:
rom
exit
Good luck!