Jsut tryin to get FTP goin and i can connect and i can upload - butr anything over 7mb dies in the bum.
is this a limit of hijack ?

i think it is the ReserveCache parameter in the config.ini, not sure ?

No such limit in Hijack, and ReserveCache shouldn't have anything to do with it either if you're also using Beta11 player software.

Look on the serial port for error messages.

Just as a confirmation...

I just now sent a 7.5 megabyte file to the player via Hijack FTP, using version 216 of Hijack, and it worked fine with no problems. Entire file uploaded. Then I deleted the file and set it back to read-only with the http://empeg/?ro command.


HOWEVER, something very interesting!

After setting it back to RO, the player did one of its beta11 lockups where the front panel controls and IR commands freeze up but the music keeps playing and the visual keeps animating. Now that the player is in this mode, I can play with it... Here is what I see:

Right now the player screen is showing the box with the "Done" message from the RO command up on the screen, with the visual animating underneath it The disk drive icon is up, it's the small disk icon with the solid gray center. This is interesting seeing the Hijack "Done" box atop the animating hula hoops. It looks like this:



The front panel controls do nothing, the IR remote does nothing. However, the Hijack web server software works fine and serves up the root index.html file. The player software does not respond to commands sent to it via the hijack "button" commands, though.

Hijack seems to be fully able to build its XML playlists and serve them up to the web browser. I have no trouble browsing my playlists with the web browser.

Let me see if the long-press of the button activates the hijack menu.... Nope. Can't initiate the Hijack main menu with a long buttonpress, either via the front panel, the IR remote, or the XML web interface.

Player keeps loading songs from the hard disk and doing all the necessary caching etc., it's still playing the current playliust perfectly and animating Hula Hoops under that "Done" Window.

Wow this is totally interesting. I wonder what else I can do to help narrow down the source of the UI lockup bug?

Ooo. The transient line came up one pixel. Now it looks like this:



Everything is still locked.

And now the lockups just cleared themselves completely. The player is now functioning normally everything is fine. Like magic.

The keys I pressed during the lockup now all "poured out" and executed.

Pushing the car back up the mountain to see if the brakes failed again did not cause the car to crash a second time. (Uploading the 7.5mb file a second time did not induce the lockup).

This matches with the lockups I see, everytime I have been bothered to wait long enough the lockup has cleared after several minutes (sometimes more than ten minutes), again then sending the missing button pushes.

They are very rare now in beta11, in beta7 they happened almost every day (every 7 hours), now they happen about once every 40 hours.

so whats the procedure i need to follow to upload stuff ?
and where should i upload it if that matters ?:

atm i console in via serial and issue RW. thern i ftp in and try uploading a file (35mb) to /tmp and every time it gets to around 7mb it comes back with connectin reset by peer and starts again. or if im using commandline ftp it jsut says file completed and tell me it transfered 7mb or so.

any ideas ? i want to be able to use the empeg as a knd of portable hdd for some of my other files between work and home

Mmmm.. cool.

The only way it can get stuck with the 1-second "Done" message on the screen, with visuals still active behind it, is for the IR driver to be continuously feeding dribble to Hijack/Player.

If that's the case, I'd expect to see the IR interrupt counter (viewable by surfing to /proc/interrupts) counting up at least once a second, probably much faster. There may be additional relevant information under /proc/empeg_ir, especially if one just sits there and hits refresh in the browser.

Mmm...

>so whats the procedure i need to follow to upload stuff ?

Simple: find a partition that has enough space on it.

The root partition on your player probably (just guessing here..) has only about 7MB of available space, so your FTP bombs once that space is consumed.

The more useful place to put stuff is on the /drive0 (and/or /drive1 for a 2-drive unit) partition.

Cheers

I think hitting "Cancel" on the remote ought to get rid of the Pop-Up, and then permit use of the Hijack menu.. not 100% sure of that, though. This is weird.

I think hitting "Cancel" on the remote ought to get rid of the Pop-Up, and then permit use of the Hijack menu..

"Cancel" on the remote was one of the things I'd tried. Presses of the cancel key did not do anything until later when all of my keystrokes spilled out of some kind of buffer.

Not that Tony said otherwise but should things have been different if Cancel was the first key pressed after the lockup?

Rue

Here is a question to everyone who's ever had this lockup...

(And I do mean THIS EXACT LOCKUP, not any other lockup. I mean the lockup where the player keeps playing, the visuals keep animating, but the player stops responding to button input for ten minutes or so at a time...)

... When this lockup happened. Were you on Info:Transient? Always, every time? Or has this happened to anyone in another info view?

ahh i see why noe jsut checked riocar faq and saw that the root dir is only 16mb hmm maybe thats why ehheheh
will try uploadingf to it tonight i a more approprite place like /drive0

It's happened to me in full screen info mode.

I'm *ALWAYS* on INFO TRACK. And this lockup happens at least once every two days with B11. It happened once or twice (ever) with b7.

And I do have this exact, very same, lockup. not any other lockup. not the relative of this lockup, nor a friend. This very same lockup. (It's possible for it to be in multiple players at once, believe it or not )

Anyway, pressing the CANCEL button first hasn't done anything when I've tried it. On second thought, that's not exactly true. It was probably the second button I pressed. Because I didn't know the player had stopped responding to buttons until after I had pressed the first "other" button.

I was pretty sure that with b7 I had this happen at least once without Hijack. But I've been running Hijack as this problem has increased frequency. Can anyone else confirm these lockups without Hijack installed?

And it doesn't take any special input or access to make the player lock. It happens while I'm just driving along not pressing anything. I'll try skipping to the next track and will notice I can't. Simple as that.

Bruno

Happened twice so far with b11 in Info: Track mode... many times with b7. I can't identify a specific action that triggered it - I only noticed when I went to change tracks (unless that caused it???). I never waited long enough for it come back - I always pulled it out and re-inserted. Also, it happened with many different versions of Hijack installed.

Also, it happened with many different versions of Hijack installed.

We've already determined that it's not caused by or related to Hijack, as Doug Burnside gets the same lockup on a pure-stock player.

What I found interesting is that the bug managed to interrupt Hijack's ability to repaint its "Done" window without interrupting Hijack's ability to serve web pages. I thought that might give a clue as to the source of the bug.

I wonder if it's a failure between the display board connection to the mainboard...
Hugo mentioned a few things about that cause problems in the thread about the dimmer problems...

I had it a lot with b7, only 3 times so far with b11 but it is always with transient. Sometimes it has happened with the info on its way up and other times on its way back down - but it is always the 1 row of pixels showing.
Everything else still works - player, http and ftp servers - but I can't use remote or buttons to do anything.
It eventually comes back...mostly

I wonder what else I can do to help narrow down the source of the UI lockup bug?

Watch the clock. Press 1 until the time comes up. Set it via the menu if it's wrong, as accurately as possible. Keep an eye on it, periodically checking for remaining in synchrony with your watch. Especially have a look at it just after a lockup, and see whether it has lurched backwards.

Do the Hijack HTML headers include a timestamp? Or is there some other way of getting the result of gettimeofday() out of Hijack even if the player is locked?

Peter

As long has Hijack HTTP is working, you can surf to /proc and read *anything* you want from the system data structures there.

Like /proc/uptime, /proc/interrupts, or /proc/nn, where "nn" == the PId of the process you want to examine.

I really think that by now the Rio boys would be using this to help debug lockups in their lab!

-ml

Tony,
I watched a lockup yesterday at work, and I watched it finally "get over it" as well. It was in transient mode, stuck with one pixel showing at the bottom. The transient line didn't change when the songs changed, but the visuals were still going. No button input was accepted. Then, about one song before the player "got over" the lockup, a second line of different transient information showed (now two pixels deep, and different pixels than before). When the player finally did get over it, the menu popped back up like it had remembered my key presses in a buffer or something (although I'm not sure I pressed the menu button, but I might haver). Sorry if all of this has been observed before.

-Jeff

Sorry if all of this has been observed before.

All of it has been observed before, but it's OK to report confirmation. Hope they can nail this bug soon.

I had one today...I hit the pause button and noticed it didn't work...then saw the one pixel row thing...but I never pressed another button and when it unlocked it never did pause
btw: I was in InfoTex mode and it did change when the songs changed...

I had one today

Any associated clock timekeeping issues?

Peter

yeah I did notice that the clock got knocked back about roughly equal to the time it was locked up...