Argh. Screenshot attached.

(yes, I'm running v3alpha8 -- I'm one of those crazy ogg people. But this is a hijack upgrade which uses hijack's kftpd to write to the firmware memory location, if I understand all the bits right.)

While jEmplode works great most of the time, I get this cases where it seems to hang. This is the first time it wasn't during song uploads, but it's in the middle of a hijack upgrade. Nothing has changed for the last 30 minutes, so I guess it's abort and see what I need to do to get back to normal.

This is sort of a companion thread to the one I started a few days ago, and all of the deails are the same. I've upgraded hijack with jemplode at least three times this week, the player was freshly booted before starting jEmplode, and there is only the ksock -104 messages on the console.

Anyone have any suggestions before I start closing programs and throwing 'kill's around?

--Nathan

I just closed the upgrade progress window and then quit jEmplode. Restarted jEmplode and the upgrade stalled briefly about the same point but then completed sucessfully. Whew, I was afraid I'd have to do a full empeg image reload because the flash was zapped or something.

--Nathan

The first stall was probably due to the kftpd bugs I added in v423/v42 -- ftp still worked, it just wasn't exiting properly.

So jemplode hung on the kernel upgrade *after* it was upgraded.. so no harm done. Your second attempt then just overwrote the same kernel again for good measure.

I *think* v425 is now just fine, but I don't have an empeg anywhere near me right now -- I took the train to Toronto for the weekend.

Cheers

Mark,

Enjoy your weekend!

Hijack v425 did suppress the kernel level ksock ... -104 error message, but it's still being displayed when it gets passed up to kftpd.

kftpd: ksock_rw() failed, rc=-104

Not a problem, tho'

Thanks again!

--Nathan

Okay, thanks. I've added a one-liner to take care of that now, for whenver v426 gets released.

Cheers