Okay, I was in the process of upgrading a friend's Empeg to b11 and during the partition pump power was lost. WHY it was lost is not important (okay, one of my cats stepped on the UPS switch... again) but now the player is frozen at the logo. Watching the boot through telnet, I get the info below. I'm almost certain this is not a hard drive error, but rather something to do with the interrupted upgrade. Any info on how I can restore to factory and start over? There's no music on the thing, but I'd like to get it upgraded and off ASAP. Thanks, telnet log below.

empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.14-rmk5-np17-empeg50 ([email protected]) (gcc versi
on 2.95.3 20010315 (release)) #8 Fri Feb 8 18:48:15 GMT 2002
Processor: Intel StrongARM-1100
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102983)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15024k/16M available (964k code, 20k reserved, 372k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea Universit
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 206f6972 'rio '
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004600).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: FUJITSU MHL2300AT, ATA DISK drive
hdb: FUJITSU MHL2300AT, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
hdb: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:26:0b:a
7
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initWarning: unable to open an initial console

Everything looks ok, just apply the upgrade file again. Basicially it looks like it got interrupted when it was writing the new software to the disk, so it boots the kernel fine (thats in flash and was the first part of the upgrade), but then it can't find it's startup files on disk to start the player.

Keep in mind the upgrade won't be able to autorestart your empeg. Pull the plug and power it back up when the upgrade says "Apply power now".

Excellent, thanks for the help. I was a bit nervous about trying to reapply a kernel without knowing the nature of my problem.

I'll go return a copy protected CD in your honour.

Run the upgrade again, that should fix it.

The upgrade process is designed to be robust. The code on the unit that loads the upgrade is in a protected area of memory, so it theory it is near impossible for a failed upgrade to break anything permanently. Reapplying the upgrade should always fix things.

That Hugo, he's a clever chap...