I have a Mk.2 (not 2a), dual-drive, formerly running 1.03 with no trouble.
Every time I've tried to install *any* version of 2.0 on the device I've had the same problem: the install goes fine, everything's working great, I can use the player fine with the buttons/knob, but as soon as I hit any button on the remote except for the volume adjuster, the player freezes -- and then, on subsequent boots, hangs with "Starting audio..." on the display and, from the serial port output, obviously just after running "player.cpp".

With the player like this, emplode won't even talk to it on serial, ethernet, nor USB. I can get a shell by hitting control-C on the serial port, but I'm at a loss as to what to do to fix this.

Downgrading to 1.03 fixes things -- of course, upgrading to 2.0bX breaks them again.

Does anyone have any idea what might be going on?

Thor

Are you sure you are trying to upgrade with the MKll version and not the MKl version?

Assuming that you're certain the 2.0x upgrade files are good files instead of corrupted downloads, then I think it's time to contact support. Before you do, re-install 1.03 (it's OK to go down in versions) to verify that your statement about 1.03 working is still true.

Good point, Laura.

Thor, are you sure the file said "CAR2" in the file name?

Uh, yes. I have all three models of the Empeg, so I'm pretty careful not to load the wrong image onto the wrong player! Currently loaded on the player that has lost its sh*t is car2-developer-2.0b11. Sigh.

Are configuration settings used by the player stored in the filesystem somewhere? Perhaps I could just zap them, so player.cpp would at least start again.

Thor

Are configuration settings used by the player stored in the filesystem somewhere?

Ooo. Ooo. Ooo.... Go here.

Did that fix it?

Greetings!

Could this also be a corrupted startup playlist or file?

YOW!

So, there are at least two bugs:

1) After the upgrade from 1.03, attempting to enter the playlist menu *at all* hung the player. That seems to have been the original problem.

I removed config.ini -- no help. Ran player -i, which said the "tags" file was bad, then rebuilt the database -- that fixed it.

2) This player used to live in a car, where it had a tuner module attached. Now it lives in my stereo rack, where, needless to say, there's no tuner. While monkeying with the unfamiliar labels on the Kenwood remote (the one I happened to have handy today) I evidently selected the tuner input source. It appears that without the tuner attached...that reliably hangs the player, which attempts to select the tuner again at boot time and hangs again! Luckily `player -i' fixes that, too. I guess I'll have to train my wife to never touch the "tuner" button...

Thor

Odd, it should never select the "tuner" input source unless there's really a tuner attached. Is there a reason it thinks there's a tuner attached when there isn't one?

Beats me -- there is not a tuner attached, and the player is *not* in a sled and does *not* think it's in a sled (serial port is at 115200).

I have multiple players and multiple cars; it's possible that this Mk.2 was last hooked up to a tuner with a non-default tuner selector setting. I wonder if there's a bug lurking there?

I can select aux input and then go back to the "player" input -- no problem there. Hit the tuner button on the kenwood remote, though, and it well and truly hangs and won't come back without "player -i".

Wow, never heard of that.

I say, if you can reproduce that behavior, send it to [email protected] .

It gets even weirder. This kills my Mk.2 every time, but does nothing to my Mk.2a -- I can switch back and forth to the tuner all I like, and the player doesn't hang at all. Mmmmmm, heisenbug.

Thor

Greetings!

Interesting. That is weird - the 2 and the 2a should be code identical. Other than memory amounts, they should be functionally identical. Are your configurations between the boxes (player version, config.ini, etc.) identical?

heisenbug

ROFL, I love that. I'm going to use that interchangeably with "FM" when describing bugs from now on.

I'm going to use that interchangeably with "FM" when describing bugs from now on.

I'll bite... FM? Fscking Magic maybe?

Correct.