Unoffical empeg BBS

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

Page 1 of 2 1 2 >
Topic Options
#348613 - 30/10/2011 18:55 Error "Bad pump response" occured during stage 0x25
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I've been trying to install a Transcend 64GB SSD and I keep getting the above error when trying to load the developer image. I've tried re--downloading the image several times, but I get the same error.

I'm able to run the disk builder without errors, so I don't believe that I've got a bad cable or port (also: I'm able to run a pair of conventional drives without problems). I've double- and triple-checked the physical connections and they seem good (and if they were bad, the disk builder would error, wouldn't it?).

I've tried searching the forums. but haven't found anything yet that helps.

Can someone give me some help with this? I'm willing to believe that I've overlooked something, but I've no idea what that could be right now.

Top
#348614 - 30/10/2011 19:10 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
If it helps, I've got a couple Linux computers around here (Ubuntu and Xubuntu, but if I need to load another flavor, I'm able to do that).

Top
#348623 - 31/10/2011 00:08 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
MMmm.. really need to see the serial port output from the failure.

But you could try wiping the paritition table from the card and then try again -- that might be all that was wrong.

From a Linux box: dd if=/dev/zero of=/dev/hdX bs=512 count=1
...where you replace "/dev/hdX" with the actual device path to the CFcard on the Linux box ("lsscsi").

-ml

Top
#348645 - 31/10/2011 11:49 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
In case it makes a difference, this is an IDE SSD (v. an IDE CF setup).

I can get the serial port output tonight, when I get home from work (sadly, I don't have either the equipment or the employer tolerance to work on it now).

I've played with Linux a bit, but I'm still pretty unfamiliar with it...should I enter the command above (with "/dev/hd1" (I'm assuming that the laptop's HDD is "0" and the RioCar will be "1"))?


Edited by bauble (31/10/2011 12:22)

Top
#348646 - 31/10/2011 12:38 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Oh, your earlier post suggested familiarity with Linux, but that's obviously not the case now. smile

So, no, you should NOT even attempt the commands I suggested -- you'll likely lose everything on both systems if you try.

Find a friend who knows this stuff, or perhaps somebody else here might help you through it (?).

Cheers

Top
#348650 - 31/10/2011 13:36 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Sorry - I didn't mean to imply that I was any kind of a Linux adept; just that I have the OS running (and from looking at some posts, it seems that some things are done more easily through it).

FWIW, I don't have anything on either system (the SSD has only successfully run the disk builder and the Lunix systems were built so I could gain some familiarity with the OS, but they don't have anything other than a base load).

So...do I have anything to worry about, other than wiping the RioCar and the computer?

Top
#348655 - 31/10/2011 15:19 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
Originally Posted By: bauble
when trying to load the developer image. I've tried re--downloading the image several times, but I get the same error.


Where are you getting this file?

At least one of the files from the empeg.com web site is known to be corrupted. Are you using Mark Lord's bigdisk files from rtr.ca?
_________________________
Tony Fabris

Top
#348658 - 31/10/2011 16:19 Re: Error "Bad pump response" occured during stage 0x25 [Re: tfabris]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I did use Mark Lord's disk builder.

But I pulled the image from the empeg.com website. Is there a better place to get it? (it would be great if that's all there is to the problem!)

Top
#348660 - 31/10/2011 19:34 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
Yes, the same place you got Mark Lord's builder.

It's linked from this FAQ entry:

I get a 'pump' error when I try to upgrade my player firmware.
_________________________
Tony Fabris

Top
#348661 - 31/10/2011 20:20 Re: Error "Bad pump response" occured during stage 0x25 [Re: tfabris]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Thank you! I'll try the new image as soon as I get home.

Top
#348665 - 01/11/2011 01:07 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Well, I was going to try the new image, but I couldn't get the disk builder to run. Here's the serial port output. Can someone take pity on a poor n00b and tell me what I'm doing wrong?


empeg audio-in initialised, CS4231A revision a0.
empeg-car bootstrap v1.02 20
empeg remote control/panel button initialised.
If there is anyone
empeg usb initialised, PDIUSBD12 id 1012let them speak now,
empeg state support initialised 0089/88c1 (save to d0005700).orever hold their peace...it seems not. Let fly the Penguins
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
Copying kernel...
empeg-car b
RAM disk driver initialized: 16 RAM disks of 4096K size

empeg single cha
hdb: TS64GSSD25-M, ATA DISK drivere is anyone present who wants to
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffffr forever hold their peace...it seems n
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff554
Copying kernel...
hdb: TS64GSSD25-M, ATA DISK drive20001106 ([email protected])
ide_data_test: wrote 0x0000 read 0xffff
If there is anyone present who want
ide_data_test: wrote 0xffff read 0xffffow,
ide_data_test: wrote 0

ide_data_test: wrote 0xffff read 0xffff................................... don
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55.2.17-rmk5-np17-empeg55-hijack-v508 (hi
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff95.3 20010315 (release)) #2 Fri Jan 9 1
ide_data_test: wrote 0xffff read 0xffff
Proce
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide0: unexpected interrupt, status=0xff, count=1
ide0 at 0x000-0x007,0x038 on irq 6
hdb: TS64GSSD25-M, 61136MB w/1kB Cache, CHS=7793/255/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:09:f
2
Partition check:
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

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.04initialise
Copying kernel...
empeg audio-
Calling linux kernel...r
Uncompressing Linux..................................... done, booting the kerne
USB:
empeg usb initialised, PDIUSBD12 id 1012
l.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version
empeg state support initialised 0089/88c1 (save to d0005b80).quest
2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
show_
USB: Non-standard r
empeg
Processor: Intel StrongARM-1100 revision 11
USB: No
empeg power-pic drive
Checking for extra DRAM:)
c1000000: wrote ffffffff, read e28cc001ver initialized: 16 RAM disks of 4096K
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
USB: Non-stand
empeg single chann
empeg-car player (hardware revision 9, serial number 30102546) primary interface...USB: N
USB: N
ide_data
Linux NET4.0 for Linux 2.20000
Based upon Swansea University Computer Society NET3.039
ide_data_test: wrote 0x0000 read 0x000
NET4: Linux TCP/IP 1.0 for NET4.0
USB: N
ide_data_test
IP Protocols: ICMP, U
TCP: Hash tables configured (ehash 16384 bhas

Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")ote 0x5555 read 0x0000
empeg display initialised.Non-standard reque
empeg dsp audio initialisedD25-M, ATA DISK driveon-sta
empeg dsp mixer initialised
USB:
empeg dsp initialisedte 0x0000 read 0x0000
CS4231A: not responding (39) --> no v
USB: Non-standard
empeg power-pic driver initialised (first boot)Non-standard request
i
RAM disk driver initialized: 16 RAM disks of 4096K sizet
empeg single channel IDE
Probing primary interface...t: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x0000 read 0xfe3dSB: Non-standar
ide_dat
ide_data_test: wrote 0xffff read 0xfe3d
hda: TS
ide_data_test: wrote 0xaaaa read 0xee28
USB: Non-s
ide_data_test: wrote 0x5555 read 0xfe3d

ide_data_test: wrote
ide_data_test: wrote 0x0000 read 0xfe3d9
hda: TS6
ide_data_test: wrote 0xffff read 0xfe3dStahlman ([email protected])
ide_data_test: wrote 0xaaaa read 0xee28SB: Non-standard req
ide_data_test: wrote 0x5555 read 0xf63d8000 IRQ:7 INTF:TP MEM:6144b
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3d0x000

ide_data_test: wrote 0xaaaa read 0xee28(priority -1)
ide_data_test: wrote 0x5555 read 0xfe3dquestuest[1 disk] i
ide_data_test: wrote 0x0000 read 0xfe3d version 0, size = 24670208 bytes
ide_data_test: wrote 0xffff read 0xfe3
USB: Non-standa
Setting maximal mount count t
ide_data_test: wrote 0x5555 read 0xfe3dB
Setting interval between check 0 s
ide_data_test: wrote 0x0000 read 0xfe3d
USB: Non-standard requestdard re
ide_data_test: wrote 0xffff read 0xfe3dg hda4 filesysteshow_message("Making hd
ide_data_test: wrote 0xaaaa read 0xee28request
ide_data_test: wrote 0x5555 read 0xf63d
m
mke2fs 1.14, 9-J
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3d
0 blocks (0.00
ide_data_test: wrote 0xaaaa read 0xee2

Tuning hda4
ide_data_test: wrote 0x5555 read 0xfe3d
tune2fs 1.17, 26-Oct-19
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3d
Setting i
ide_data_test: wrote 0xaaaa read 0
Mountin
ide_data_test: wrote 0x5555 read 0xf63dng hda4")

ide_data_test: wrote 0x0000 read 0xfe3dw_message("Making directories")
ide_data_test: wrote 0xffff read 0xfe3d
show_message("Remounting
ide_data_test: wrote 0xaaaa read 0xee28ompleted
show_message("hd
ide_data_test: wrote 0x5555 read 0xf63
Zeroing hda3

ide_data_test: wrote 0xffff read 0xfe3d
Done!

ide_data_test: wrote 0xaaaa read 0xee28
bash-2.01#
empeg-car boots
ide_data_test: wrote 0x5555 read 0xfe3d
ide_data_test: wrote 0x0000 read 0xfe3dwants to upgrade
ide_data_test: wrote 0xffff read 0xfe3d
ide_data_test: wrote 0xaaaa read 0xee28 seems not. Let fly the Penguins of Lin
ide_data_test: wrote 0x5555 read 0xfe3d


ide_data_test: wrote 0x0000 read 0xfe3d
Calling linux kernel...
ide_data_test: wrote 0xffff read 0xfe3dnux....................................
ide_data_test: wrote 0xaaaa read 0xee28
ide_data_test: wrote 0x5555 read 0xfe3drsion 2.2.17-rmk5-np17-empeg55-hijack-v
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3
ide_data_test: wrote 0x5555 read 0xfe3dmpeg-car player (hardware revision 9, s
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3dmem=16m
Calibratin
ide_data_test: wrote 0xaaaa read 0xee28
Memory
ide_data_test: wrote 0x5555 read 0xfe3deserved, 364k data, 4k init)
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xfe3dorder 2, 16k)
ide_data_test: wrote 0xffff read 0xfe3dable entries: 16384
ide_data_test: wrote 0xffff read 0xfe3d.039
ide_data_test: wrote 0xaaaa read 0xee281.
ide_data_test: wrote 0x5555 read 0xf63d
TCP: Hash tab
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3dinux-2.2 (Dag Brattli)
ide_data_test: wrote 0xaaaa read 0xee28kswapd v 1.5
SA110
ide_data_test: wrote 0x5555 read 0xf63dial options enabled
ide_data_test: wrote 0x0000 read 0xfe3d
ttyS00 at 0xf8010000 (irq = 15) is
ide_data_test: wrote 0xffff read 0xfe3d
ttyS01 at 0xf805
ide_data_test: wrote 0xaaaa read 0xee2
USB
ide_data_test: wrote 0xaaaa read 0xee28 ID=-1d=5sult=
ide_data_test: wrote 0x5555 read 0xfe3dk Lord")andard reque
ide_data_test: wrote 0x0000 read 0xfe3d
empeg display initialised.est
ide_data_test: wrote 0xffff read 0xfe3dnitialisedd request
ide_data_test: wrote 0xaaaa read 0xee28isedandard request: Non-standar
ide_data_test: wrote 0x5555 read 0xfe3d
empeg dsp initialised
ide_data_test: wrote 0x0000 read 0xfe3dS4231A revision a0x
ide_data_test: wrote 0xffff read 0xfe3d
empeg remote control/panel butto
ide_data_test: wrote 0xaaaa read 0xee28rd requestrevision 1
ide_data_test: wrote 0x5555 read 0xfe3

ide_data_test: wrote 0xffff read 0xfe3dide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0xaaaa read 0xee28USB: Non-
ide_data_test: wrote
ide_data_test: wrote 0x5555 read 0xd63d

USB: Non-standard r
ide_data_test: wrote 0x0000 read 0xfe3d_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xfe3d-standard requestrq = 17) is
ide_data_test: wrote 0xaaaa read 0xee28 wrote 0xffff read 0x0000
ide_data_test: wrote 0x5555 read 0xfe3dard request
id
ide_data_test: wrote 0x0000 read 0xfe3
ide_data_test: wrote 0xffff read 0xfe3d
ide_data_test: wrote 0xffff read 0x0
ide_data_test: wrote 0xaaaa read 0xee28
USB: Non-standard request
ide_data_test: wrote 0x5555 read 0xfe3daa read 0x0000tandard request
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0x5555 read 0
ide_data_test: wrote 0xffff read 0xfe3d
USB: Non-st

ide_data_t
ide_data_test: wrote 0xaaaa read 0xee28
USB: Non-s
ide_data_test: wrote 0x5555 read 0xfe3d
ide_data_test: wrote 0xffff read
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0xfe3d 0x
ide_data_test: wrote 0x0000 read 0xfe3d
USB:
ide_
ide_data_test: wrote 0xffff read 0xfe3d
ide_data_test: wrote 0xaaaa read 0xee28
USB: Non-s
ide_data_test: wrote 0x5555 read 0xd63d0000 read 0x0000request
ide_data_test: wrote 0x0000 read 0xfe3d
ide_data_test: wrote 0xffff read 0x
ide_data_test: wrote 0xffff read 0xfe3d
ide_data_test: wrote 0xaaaa read 0x
ide_data_test: wrote 0xaaaa read 0xee2
USB: Non-standard
ide_data_test: wrote 0xaaaa read 0xee28 read 0x0000-standard requestSD25-M, AT
ide_data_test: wrote 0x5555 read 0xfe3d
USB: Non-sta
ide_data_test: wrote 0x0000 read 0xfe3d
Partition check:on-standard requ
ide_data_test: wrote 0xffff read 0xfe3d hda5 hda6 > hda2 hda3 hda4
ide_data_test: wrote 0xaaaa read 0xee28
RAMDISK: ext2 filesystem found
ide_data_test: wrote 0x5555 read 0xfe3

Setting
VFS: Mounted root (ext2 filesystem).72 bytesNon-standard req
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05 (priority -1)standard requestequeste 0xaaaa read 0x000
Kernel panic: VFS: Unable to mount root fs on 03:05
Setting up swapspace vers

empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
hda:
USB: Non-standard request
USB: Non-stand
Calling linux kernel...
ext2fs_che
Uncompressing Linux..................................... done, booting the kerne
USB: Non-s
l.da
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version
USB: No
Linux ext2 filesystem format
2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009 4096000, 7962624, 11239424,
Processor: Intel StrongARM-1100 revision 11
Writing superblocks
Checking for extra DRAM: information: done
c1000000: wrote ffffffff, read e28cc001
Tuning hda4
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Cne2fs 1.17, 26-Oct-1999 for

Page cache hash table entries: 4096 (order 2, 16k)
Done!
show_message("Done
POSIX conformance testing by UNIFIX
ide_data_test: wrote 0x00
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
ide_data_test: wrote 0xaaaa rea
NET4: Linux TCP/IP 1.0 for NET4.0

ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART0000
ide_
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
ide_data_test: wrote 0
Signature is 636f6972 'rioc'

Tuner: loopback=0, ID=-1SK drive
show_message("Hijack v508 by Mark Lord")0000 read 0x0000
empeg display initialised.st: wrote 0xf
empeg dsp audio initialised

empeg usb initialised, PDIUSBD12 id 1012
USB: Non-standard reque
empeg state support initialised 0089/88c1 (save to d0005880). 0x0000
USB: Non-stand
empeg RDS driver initialised
ide_data_test: wrote
empeg power-pic driver initialised (first boot)
USB: N
ide_data_te
RAM disk driver initialized: 16 RAM disks of 4096K size
USB: Non-stan
USB: No
hda
empeg single channel IDEdrive
Probing primary interface...ard reque
ide_data_test: wrote 0x0000 read 0xffff0000
ide_data_test: wrote 0xffff rea

hdb: TS64GSSD25-M, ATA DISK drivendard request
ide_data_test: wrote 0x0000 read 0xffffe_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xffff read 0xffffB: Non-standard request
ide_data_test: wrote 0xaaaa read 0xffaa:v0.12 03/06/96 by Erik Stahlman (erik@
ide_data_test: wrote 0x5555 read 0xff55


SMC919
hdb: TS64GSSD25-M, ATA DISK drive7 INTF:TP MEM:
ide_data_test: wrote 0xaaaa read 0xffaa
USB: N
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide0: unexpected interrupt, status=0xff, count=1
ide0 at 0x000-0x007,0x038 on irq 6
hdb: TS64GSSD25-M, 61136MB w/1kB Cache, CHS=7793/255/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:09:f
2
Partition check:
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

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.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version
2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102546)
Command line: mem=16m6028k swap-space (pri
Calibrating delay loop... 207.67 BogoMIPS
USB: Non-standard reques
Memory: 15000k/16M available (996k code, 20k reserved, 364k data, 4k init)SB: Non-standard requestd request6k)
Dentry hash table entries: 2048 (order 2, 16k)
ext2fs_check_if_mount: No such file or direc
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
hda4 is mounted.
POSIX conformance testing by UNIFIX
Linux ext2 filesystem for
Linux NET4.0 for Linux 2.2

Filesystem l
Based upon Swansea University Computer Society NET3.039group

NET4: Linux TCP/IP 1.0 for NET4.00, 7962624, 11239424,
IP Protocols: ICMP, UDP, TCPing inode tables: done
TCP: Hash tables configured (ehash 16384 bhasilesystem
show_
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
Making directories
show_m
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Remounting ro
show_me
Signature is 636f6972 'rioc'
hda4
Tuner: loopback=0, ID=-1how_message("hda4 comple
show_message("Hijack v508 by Mark Lord")ng hda3
show_message("Zeroin
empeg display initialised.
/bin/cat: write
empeg dsp audio initialisedce
empeg dsp mixer initialised
show_message("Done!")
empeg dsp initialisedash-2.01#


empeg audio-in initialised, CS4231A r
ide_data_test: wrote 0xffff read 0xffff
NetWinder Floating Point Em
ide_data_test: wrote 0xaaaa read 0xffaaorp.
ide_data_test: wrote 0x5555 read 0xffff: Non-standard requ
hdb: TS64GSSD25-M, ATA DISK drive
empeg-car player
ide_data_test: wrote 0x0000 read 0xffff2546) 16MB DRAM
ide_data_test: wrote 0xffff read 0xffff
USB: Non-standard request
ide_data_test: wrote 0xaaaa read 0xffaa
Command line: mem=16m
ide_data_test: wrote 0x5555 read 0xff55ng delay loop... 207.67 BogoMIPS
hdb: TS64GSSD25-M, ATA DISK drive
USB: Non-standard request
ide_data_test: wrote 0x0000 read 0xffffailable (996k code, 20k reserved, 364k
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa Non-standard request
P
ide_data_test: wrote 0xaaaa read 0xffaar 2, 16k)
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide0: unexpected interrupt, status=0xff, count=1
ide0 at 0x000-0x007,0x038 on irq 6
hdb: TS64GSSD25-M, 61136MB w/1kB Cache, CHS=7793/255/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:09:f
2
Partition check:
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

Top
#348667 - 01/11/2011 02:19 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
You need to use something other than hyperterminal -- it mangles the logs (as seen above) making them quite a bit less useful than they normally would be.

Most people eventually discover "putty" on windows. MUCH better than the silly little hyperterm thingie.

-ml

Top
#348673 - 01/11/2011 02:30 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I *thought* it looked garbled. I was afraid it indicated something was wrong.

I've conned one of my Linux-enabled friends to help me tomorrow. I'm assuming he'll be able to get a better serial port output. Is there anything else you can recommend (I know you don't have much info at this point; not trying to be pushy)?

And thank you *so* much (and to Mr. Fabris as well) for your help and suggestions so far.

Top
#348677 - 01/11/2011 04:24 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
Ross Wellington
enthusiast

Registered: 21/02/2006
Posts: 325
Hi,

It certainly doesn't like the USB device that it sees.

Ross
_________________________
In SI, a little termination and attention to layout goes a long way. In EMC, without SI, you'll spend 80% of the effort on the last 3dB.

Top
#348678 - 01/11/2011 09:31 Re: Error "Bad pump response" occured during stage 0x25 [Re: Ross Wellington]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Quote:
ide0: unexpected interrupt, status=0xff, count=1


That part looks bad, indicating a hardware fault.
Most likely with where the IDE hard disk cable connects to the mainboard. The connector there (both parts) is extremely fragile, and frequently falls apart.

This means, the ribbon cable half can separate from its connector, which sometimes is curable by recrimping it.

But it more often means the "IDE header" (pins soldered to the mainboard) have broken their solder joints. Repairing those requires a practised and delicate touch with a temperature controlled soldering iron. Even just examining the connection requires good magnification to see the solder breaks.

Capture / post a better copy of the serial log and then we'll know for sure.

Cheers

Top
#348679 - 01/11/2011 11:53 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Ok - here's a copy of the output, using PuTTY:


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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102546) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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'
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
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 d0005980).
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...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xffff
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xffff
hdb: TS64GSSD25-M, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hdb: TS64GSSD25-M, ATA DISK drive
ide0: unexpected interrupt, status=0xff, count=1
ide0 at 0x000-0x007,0x038 on irq 6
hdb: TS64GSSD25-M, 61136MB w/1kB Cache, CHS=7793/255/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:09:f2
Partition check:
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

Top
#348680 - 01/11/2011 11:57 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
If there *is* a problem with the IDE header, would that keep the unit form running any drives? I've been running a couple conventional hard drives in it; and have been (carefully) swapping them into the unit when I get frustrated with the SSD.

Top
#348681 - 01/11/2011 13:38 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
drakino
carpal tunnel

Registered: 08/06/1999
Posts: 7868
Is the SSD the only drive in the system when you made that log above?

Top
#348682 - 01/11/2011 14:10 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Mmm.. okay, I'm betting that the drive error had something to do with the SSD being so much quicker at starting up than a mechanical drive. So it's probably harmless. You can disregard my earlier comments on it, now that we've got a proper boot log (nice job!).

So now you just need some kinder person to walk you through the s/w install on the drive. Looks like you're close already.

Top
#348683 - 01/11/2011 14:17 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Are you sure? I posted the below before seeing your message. Am I overlooking something again?


It is (the only drive in the system).

On further testing, I think my SSD may be bad (frustrating as that is): I had a Linux-enabled friend try to zero the drive, but the Linux computer didn't recognize it; I put it on my Windows 7 computer (via a USB adapter) and get a message that I have to initialize the disk...and then get a message that "The device is not ready." So I'm going to be calling Transcend to see about a replacement.

Thanks for all the help and patience.


Edited by bauble (01/11/2011 14:19)

Top
#348684 - 01/11/2011 14:48 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
If some kind soul can give me instructions for installing the software, I'd be more than happy to try that before giving up and calling Transcend.

Top
#348687 - 01/11/2011 16:08 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
Originally Posted By: bauble
I *thought* it looked garbled. I was afraid it indicated something was wrong.


Hyperterminal only mangles the output when you try to use the clipboard (ctrl-C) to copy the diagnostic output. If you use the "capture text" feature it works fine. Look in this FAQ entry here for more details:

Quote:

You can also grab a complete boot log for diagnostic purposes. This is done by Selecting "Transfer, Capture Text" to begin creating the log file, then "Transfer, Capture Text, Stop" when you have captured the desired activity to that file.

Note: Some versions of Hypterterminal, specifically the one that comes with Windows XP, have a severely bug-ridden copy/paste function that scrambles the lines of text as they are copied to the clipboard. If you are trying to capture a boot log for diagnostic purposes, use the Capture Text feature instead.

The reverse is not true, however. If you have been given a list of diagnostic or repair commands to execute at the shell prompt, it is safe (and recommended) that you copy and paste the commands instead of trying to type them. The shell prompt is very sensitive to mistakes in spacing, spelling, and capitalization, and pasting the commands will produce the best results.
_________________________
Tony Fabris

Top
#348688 - 01/11/2011 16:57 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
Roger
carpal tunnel

Registered: 18/01/2000
Posts: 5683
Loc: London, UK
Originally Posted By: bauble
If some kind soul can give me instructions for installing the software, I'd be more than happy to try that before giving up and calling Transcend.


If you can't get it working in a normal PC first, then there's little point in attempting to get it to work in the empeg.

FWIW, I think I built mine with Mark's bigdisk builder and then used a Hijack+player upgrade file.
_________________________
-- roger

Top
#348689 - 01/11/2011 17:00 Re: Error "Bad pump response" occured during stage 0x25 [Re: tfabris]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I *had* thought I was familiar with the FAQs. I see now that I was sorely mistaken.


I really do appreciate that you and others have taken the time to create it/them. I'll re-read tonight.

Top
#348694 - 01/11/2011 18:10 Re: Error "Bad pump response" occured during stage 0x25 [Re: Roger]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
That's kind of what I thought...but I think I've proven that I don't know very much about how this beastie operates, so I was (and am) willing to be corrected).

Top
#348700 - 01/11/2011 20:55 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
drakino
carpal tunnel

Registered: 08/06/1999
Posts: 7868
Originally Posted By: bauble
It is (the only drive in the system).
Quote:
hdb: TS64GSSD25-M, ATA DISK drive

Your SSD is set to Slave, instead of Master. You need a jumper to set it to master. Here is the info from the manual for your SSD.

*edit* the reason I can tell this is that hdb is the typical Linux designation for a hard drive on the primary IDE bus, as the slave device. hda is the normal primary master device. I don't remember offhand how hardcoded the player software is, but my belief is that the player software (and root fs) needs to be on hda.


Attachments
Screen Shot 2011-11-01 at 15.53.44.png




Edited by drakino (01/11/2011 20:59)

Top
#348707 - 02/11/2011 00:53 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I'd really thought you were on to something, as I'd at one point had the SSD jumpered. I tried again, jumpered once as master and once as slave (thinking that I wanted to cover all/both bases)...no luck. :-(


sigh. I think I'm back to thinking that my SSD is bad.

Top
#348712 - 02/11/2011 01:40 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
And I've just run the diskbuilder and upgrade on two other drives (one conventional HDD, one SSD (it's only 2GB, but I thought would serve to test)); so I'm thinking, barring the input of those more knowledgeable than I, that my SSD is bad.

Top
#348713 - 02/11/2011 02:19 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
The boot log you posted from putty showed a perfectly functional SSD. Linux on the empeg was able to communicate with it, read the IDENTIFY block from the firmware, and read the first sector from the media (partition table).

I see no firm evidence of a broken SSD yet.

Top
#348716 - 02/11/2011 02:30 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
drakino
carpal tunnel

Registered: 08/06/1999
Posts: 7868
The disk looks to be built properly based on your logs. What happens when you apply an upgrade file? Try it again (just the upgrade, not the disk builder), with the drive jumped to master. Then post a log again to help us narrow it down.

Top
#348721 - 02/11/2011 11:17 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Ok; I'll try that as soon as I get home tonight.

Top
#348759 - 02/11/2011 22:23 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
I've tried putting the image on the SSD; I get the same "Bad pump response". :-(

Here's the serial output:

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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102546) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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'
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
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 d0004080).
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...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
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:09:f2
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

Top
#348762 - 02/11/2011 22:39 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
drakino
carpal tunnel

Registered: 08/06/1999
Posts: 7868
It looks like we are back to the SSD not being detected. Is it plugged into the same spot on the cable it was last time?

Mark, any idea if this is a potential bad IDE header issue where the drive works only as a slave device and not master? Though what I find odd is that things worked when both hard drives were in the system. Maybe a bad cable instead (the crimping issue?)

Top
#348763 - 02/11/2011 22:41 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
For no good reason, I slaved the Transcend SSD to the smaller (2GB) one (the 2GB was able to load by itself without any issues).

I got a message "Error "Couldn't find pump" occurred during stage 0x25" on the computer; and the RioCar has a message: "abb0.-1 hda: err: stat_timo".

If it helps, here's the serial output from this setup:


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 kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30102546) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k 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)
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'
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
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 d0004300).
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...
ide_data_test: wrote 0x0000 read 0x8ea1
ide_data_test: wrote 0xffff read 0x8ea1
ide_data_test: wrote 0xaaaa read 0x8ea1
ide_data_test: wrote 0x5555 read 0x8ea1
hda: SanDisk SDCFH-002G, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: SanDisk SDCFH-002G, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: SanDisk SDCFH-002G, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: SanDisk SDCFH-002G, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: SanDisk SDCFH-002G, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0x0000
ide_data_test: wrote 0xaaaa read 0x0000
ide_data_test: wrote 0x5555 read 0x0000
hda: SanDisk SDCFH-002G, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: SanDisk SDCFH-002G, 1918MB w/1kB Cache, CHS=3897/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:09:f2
Partition check:
hda:hda: irq_timo: status=0xf1
show_message("aab0.-1 hda: err: irq_timo")
ide0: reset: failed
[PTBL] [974/64/63] hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
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 initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To ComðStarting player
Timezone: EST
Hijack: intercepting config.ini

hijack: removed menu entry: "Serial Port Assignment"
kftpd: listening on port 21
khttpd: listening on port 80
player.cpp : 385:empeg-car 2.01 2004/07/06.
! tags.cpp : 61:Failed to open tags (0xc0041002).
hda: stat_timo: status=0xf8
show_message("aab0.-1 hda: err: stat_timo")
hda: no DRQ after issuing WRITE
ide0: reset timed-out, status=0x80
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
hda: drive not ready for command
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
ide0: reset timed-out, status=0x80
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
end_request: I/O error, dev 03:03 (hda), sector 0
hda: drive not ready for command
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
hda: drive not ready for command
Abnormal player termination
Player received SIGINT, user interruption
Switching to shell-player loop
Starting bash.
ide0: reset timed-out, status=0x80
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
hda: drive not ready for command
ide0: reset timed-out, status=0x80
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
end_request: I/O error, dev 03:05 (hda), sector 17694
hda: drive not ready for command
hda: stat_timo: status=0x80
show_message("aab0.-1 hda: err: stat_timo")
hda: drive not ready for command

Top
#348764 - 02/11/2011 22:43 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Can it be a problem with the player or the cable if I'm able to use both to successfully set up two conventional drives (one master and one slave)?

Top
#348766 - 02/11/2011 23:18 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Just realized I hadn't answered your question; apologies.

Yes, the SSD is on the same spot on the cable; and jumpered as master (well, it was when you posted that question).

Top
#348771 - 03/11/2011 05:03 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
drakino
carpal tunnel

Registered: 08/06/1999
Posts: 7868
The different permutations helps, though I'm personally out of suggestions. Hopefully Mark can help decode some of the messages in the last boot log you posted, with the SSD as slave and the smaller 2G drive as master. My understanding of it shows that the empeg didn't properly detect the slave (hdb) drive.

Top
#348781 - 03/11/2011 11:44 Re: Error "Bad pump response" occured during stage 0x25 [Re: drakino]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
I have no idea what you're doing wrong.
But the hardware appears to be working, though I dunno why the SSD doesn't show up as master when no other drive is connected.

Cheers

Top
#348821 - 03/11/2011 23:01 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
bauble
journeyman

Registered: 23/06/2003
Posts: 57
Well, phooey. Thanks, everyone. I really appreciate the help.

I'm going to see if I can get a replacement drive (it bothers me that I can't use the drive on the RioCar, another Linux computer, a Windows 7 computer and a Windows XP computer) and see if that makes any difference.

Top
#348828 - 04/11/2011 09:09 Re: Error "Bad pump response" occured during stage 0x25 [Re: bauble]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Last time I got this error it was because the stupid cable was not seated completely into the motherboard. D'OH! Now I know why they hot-glued these cables into place at the factory.

Top
#348829 - 04/11/2011 09:13 Re: Error "Bad pump response" occured during stage 0x25 [Re: Hollywood Justin]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Mark or anyone else, are you aware of or can you foresee any issues with using solid state drives such as a size limit or brands incompatible with your big disk builder image? If it works with an MK2a, I really want an SSD!

Top
#348830 - 04/11/2011 09:20 Re: Error "Bad pump response" occured during stage 0x25 [Re: Hollywood Justin]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
What about using a PATA SSD with a 2.5 inch SATA SSD or HDD Drive to IDE 44 Pin IDE adapter? Is there any reason that wouldn't work ('cause the SATA SSD's seem to be much less expensive)?

Top
#348832 - 04/11/2011 11:12 Re: Error "Bad pump response" occured during stage 0x25 [Re: Hollywood Justin]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Originally Posted By: Hollywood Justin
Mark or anyone else, are you aware of or can you foresee any issues with using solid state drives such as a size limit or brands incompatible with your big disk builder image? If it works with an MK2a, I really want an SSD!

No, they should all work. If we find one that doesn't, then we'll fix things. smile

Top
#348882 - 04/11/2011 21:04 Re: Error "Bad pump response" occured during stage 0x25 [Re: mlord]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
We still get great support from you for this discontinued product - better than some companies' products that are still in production! You are awesome, Mark!

Top
Page 1 of 2 1 2 >