Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#182708 - 03/10/2003 14:33 dead drive?
Cambscar
journeyman

Registered: 21/07/1999
Posts: 61
Loc: Cambridge, UK
Hi all,

Work stuff's kept me so busy lately I somehow missed the fact that v3 player software had been leaked until I saw Hugo for the first time in ages today. On finding out about it, I came home tonight with the intention of upgrading to find out what's new.

The initial install went OK, but I found that the player was 'building player database' on every boot, hanging for a fraction of a second quite often during playback, and that the drive heads were making a clicking very regularly at about a second intervals. I then decided to revert to v2, and to repeat the whole process to see if things stayed the same.

On doing so, Emplode hung during the install process. The flash programming part all seems to go OK, but once it reaches the pumping partition process, it takes forever to pass "Finding pump (preparing first hard disk)", and once that does eventually complete,
"Selecting pump device" just times out with the error "Bad pump response during stage 0x25".

Attempting to connect to a shell doesn't get any further than the boot message (see below) and about the only thing I can do is get to a Pump> prompt during boot using CTRL-A. If you try and boot the player, either in car or off the power supply you get the initial boot screen, the player hangs at the boot logo, then finally shows "no hard disk found contact support"

I've physically checked the IDE connector and cable, and all seems OK there. The obvious question- have I somehow managed to stuff the disc?? You can hear that it spins up initally on power up OK.

Anyone got any suggestions, or do I face the drive into work tomorrow with no music?

Dominic

empeg-car bootstrap v1.00 20000601 (hugo@empeg.com)
On DC power, quick boot

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.14-rmk5-np17-empeg54 (rob@tatu) (gcc version 2.95.3 20010315 (release)) #19 Wed Jul 2 23:26:54 BST 2003
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 90000930)
Command line: mem=12m noinitrd
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10968k/12M available (964k code, 20k reserved, 332k 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 University Computer Society NET3.039
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 636f6972 'rioc'
Scheduling custom logo.
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 d0005b80).
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...
Probing primary interface...
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:12:03:a2
VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

Top
#182709 - 03/10/2003 14:40 Re: dead drive? [Re: Cambscar]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31600
Loc: Seattle, WA
Don't panic. Pump errors are discussed here.
_________________________
Tony Fabris

Top
#182710 - 03/10/2003 14:43 Re: dead drive? [Re: Cambscar]
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
The kernel's not seeing a hard drive at all. Check the FAQ for possible reasons.
_________________________
Bitt Faulk

Top
#182711 - 03/10/2003 15:22 Re: dead drive? [Re: tfabris]
Cambscar
journeyman

Registered: 21/07/1999
Posts: 61
Loc: Cambridge, UK
Hi Tony,

I just swapped the drive out for an old one I've got kicking around, and it's now working fine. Well, fine's probably not the right word for an Empeg with 540mb, but it works

I guess it's time to have a hunt around on eBay.

Dominic

Top
#182712 - 03/10/2003 15:43 Re: dead drive? [Re: Cambscar]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31600
Loc: Seattle, WA
Before assuming that the drive is bad, try putting the original one back in and seeing if it magically starts working. At that point, suspect the cable or the IDE header before assuming that the drive is bad.

I mean, bad drives are possible, but problems with the cable and the IDE header are more likely.
_________________________
Tony Fabris

Top
#182713 - 03/10/2003 16:03 Re: dead drive? [Re: tfabris]
Cambscar
journeyman

Registered: 21/07/1999
Posts: 61
Loc: Cambridge, UK
Yep, tried that too. I've swapped back and forth a couple of times. The original drive consistently doesn't work. The other consistently does. The thing that really made me decide that the player wasn't happy running v3 in the first place were the noises the drive was making. I'm sure it's in some way related to the whole upgrade process as it's been faultless up to now.There's no way I'd even consider saying it was caused by it though. Could just be that it wasn't 100 percent to start with, and the extra load during the upgrade was too much for it. Or possibly even me doing something stupid I've not realised yet. Either way, Rob couldn't have been any clearer in the readme. I'm just gutted that I'm going to have to wait until I find another drive before I can play with v3 now!

Dominic

Top