Hello;

I have a problem with my MK2 EMPEG. I was updating the database in EMPLODE and the Synchronising did not succeed. The EMPEG got stuck witht he Synchronising logo and EMPLODE reported an error with updating the unit.

Now, whenever I plug it, it gets stuck on "BUILDING MUSIC DATABASE". I left it like this for a few hours and nothing happens.

I opened the unit to confirm that both drives are properly connected - everything is OK, including the slave pin for the second drive. I tried to unplug the 2nd hd and it does not make a difference.

I tried to re-load the consumer software (1.02) but it gets stuck on PUMPING DISK (the progress bar starts at 1milimeter and stops)

I tried to load the car-disk mounting utility but it gets stuck in PUMPING as well (the progress bar will go about as far as the word PUMPING).

HELP! Please email back to [email protected]

Thanks.

Update since my email to carsupport: I had a 10gig hard drive sitting here from a laptop upgrade and i connected it to my EMPEG... (this has some dos/windows stuff on it). To my surprise, I was able to run car2-builder which formated the drive. I could access the unit in the shell.

However, when I tried to install car2-consumer-v1.03, it also got stuck on 1 milimeter of PUMPING PARTITION


Note 2: When the crash occured, I was using EMPLODE 1.03 with my EMPEG which had consumer software 1.02. Could this have caused the crash???

Here is a dump of what happens when i boot-up:

-----
ls
bash: ,Cls: command not found
bash-2.01# pwd
/
bash-2.01# ls -la
total 26
drwxr-xr-x 15 0 0 1024 Aug 6 1999 .
drwxr-xr-x 15 0 0 1024 Aug 6 1999 ..
drwxr-xr-x 2 0 0 1024 Aug 6 1999 bin
drwxr-xr-x 2 0 0 1024 Nov 26 1999 dev
drwxr-xr-x 5 0 0 1024 Sep 4 08:48 drive0
drwxr-xr-x 2 0 0 1024 Jun 2 1999 drive1
drwxr-xr-x 4 0 0 1024 Jul 12 1999 empeg
drwxr-xr-x 2 0 0 1024 Jun 19 1999 etc
drwxr-xr-x 2 0 0 1024 Jun 7 1999 lib
drwxr-xr-x 2 0 0 12288 Aug 27 2000 lost+found
drwxr-xr-x 2 0 0 1024 Jun 2 1999 mnt
drwxr-xr-x 2 0 0 1024 Jun 2 1999 proc
drwxr-xr-x 2 0 0 1024 Aug 8 2000 sbin
drwxr-xr-x 2 0 0 1024 Apr 13 1999 tmp
drwxr-xr-x 3 0 0 1024 Jun 1 1999 usr
bash-2.01# w
bash: w: command not found
bash-2.01# who
bash: who: command not found
bash-2.01# man ls
bash: man: command not found
bash-2.01# who
bash: who: command not found
bash-2.01# w
bash: w: command not found
bash-2.01# whois
bash: whois: command not found
bash-2.01# w
bash: w: command not found
bash-2.01#
bash-2.01#
bash-2.01#

empeg-car bootstrap v1.00 20000601 ([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.03
Copying kernel...
Calling linux kernel...
Uncompressing Linux................................... done, booting the kernel.

Linux version 2.2.14-rmk5-np17-empeg43 ([email protected]) (gcc versi
on 2.95.2 19991024 (release)) #213 Sat Jun 23 16:35:13 BST 2001
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 80000469)
Command line: mem=12m temp=36
Calibrating delay loop... 207.67 BogoMIPS
Memory: 11008k/12M available (960k code, 20k reserved, 292k data, 8k 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 ffffffff 'ÿÿÿÿ'
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 d0005600).
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: TOSHIBA MK1016GAP, ATA DISK drive
hda: TOSHIBA MK1016GAP, ATA DISK drive
hda: TOSHIBA MK1016GAP, ATA DISK drive
hda: TOSHIBA MK1016GAP, ATA DISK drive
hda: TOSHIBA MK1016GAP, ATA DISK drive
hda: TOSHIBA MK1016GAP, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TOSHIBA MK1016GAP, 9590MB w/0kB Cache, CHS=19485/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:10:01:d
5
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
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: 8k initKernel panic: No init found. Try passing init= option to kernel.

------

Me again..........

Now that installing the car2-consumer-v1.03 software failed, trying to re-install the car2-builder also fails in PUMPING PARTITION (the task bar gets stuck about as far as the word partition)

what could the problems be/???

Do you have anything that is tied to the serial port that could be interrupting or corrupting the data stream?

Paul G.
SN# 090000587 (96GB Smoke)

I do not believe that I do.... the empeg was using the etthernet cable when this occured.

Update: After installing the car2-consumer-v1.03 which FAILED (in pumping), in took power out and re-powered the unit. I seem to be able to get this under the EMPEG logo:

"Builder Image"
"Driver(s) appear to be already built"

If I press ENTER on the PC, it goes into:
"Making /dev/hdd4/ filesystem..." forever.

If I press q or anything else, I get the shell and I can look around in Hyperterm.

clues?

Post deleted by filou

Hmm... It sounds like the builder image is there, at least partly.

Powerdown the unit and reapply the builder image (you don't want anything on this hard drive, right???).

Let it load completely and run that.

If it hangs up in the load, give it a little time. Does it actually error, or just pause?

How are you applying the load? I assume you are using the update utility.

Paul G.
SN# 090000587 (96GB Smoke)

Post deleted by filou

Within the garbage, I also get this:

=================
00000440: eb00017d e1a0000b eb000186 e3a00040 eb000179 e2460004 eb000182 e3a000
0d
00000460: eb000175 e3a0000a eb000173 eaffffd7 73207469 736d6565 746f6e20 654c20
2e
00000480: 6c662074 68742079 65502065 6975676e 6f20736e 694c2066 2178756e 00000a
0d
000004a0: 202c6861 70657473 726f6620 64726177 74697720 6f792068

Internal error: Oops: 0
CPU: 0
pc : [<00146000>] lr : []
sp : c096e028 ip : c096e09c fp : c096e098
r10: c00e76e0 r9 : ffffffff r8 : 00000000
r7 : c001daf0 r6 : 00104801 r5 : 00000006 r4 : e50b0010
r3 : 000000be r2 : c01001c4 r1 : c096e09c r0 : 00000006
Flags: nZCv IRQs off FIQs on Mode SVC_32 Segment user
Control: D01B517D Table: D01B517D DAC: 00000015
Process (pid: 0, stackpage=c096d000)
Stack:
Backtrace:
Function entered at [] from []
Function entered at [] from []
r10 = C00E76E0 r8 = 00000000 r7 = FFFFFFFF r6 = 60000093
r5 = C096E124 r4 = C01001A4
Function entered at [] from []
r5 = 00146000 r4 = C096E160
Code: pc not in code space
Bad mode in prefetch abort handler detected: mode SVC_32
Vectors:
00000000: ef9f0000 ea0000cd e59ff3b0 ea0000bb ea00009a ea0000e2 ea000078 e3a0c0
04
00000020: e58bc018 e5dac000 e5dad000 e18cc40d e0c8c0b2 e59bc000 e31c0004 0affff
f8
Stubs:
00000200: e59fd1bc e24ee004 e58de000 e14fe000 e58de004 e361f093 e20ee00f e79fe1
0e

=============

And now when I boot up (with power), I can not go into shell at all, because I get the garbage righ after bootup :-((((((((((((

HELP!

Your email has been received by carsupport, and they'll help you fix this when they reach you later today.

Don't panic

Rob

Thanks rob......

Yes, this is not leading to much :-)

If they want to call me, the number here is +1-514-276-7997. I do not mind calling back anywhere in the world.

One more...........

This is what comes in HYPERTERM when the unit is stuck in "Building music database":

EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4
Remounting filesystem read-only
EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4
Remounting filesystem read-only
EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4
Remounting filesystem read-only
EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4
Remounting filesystem read-only
EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4
Remounting filesystem read-only
EXT2-fs error (device ide0(3,4)): ext2_readdir: bad entry in directory #65: inod
e out of bounds - offset=516, inode=16712318, rec_len=12, name_len=4


It seems like the consistency of the error I get when i power up is not very good, but this happened all night (after the failed synchro from emplode)


Could it be a bad RAM or cable? The cable looks ok, but i'm no expert.

Looks like it needs a fsck; when it is running, ctrl-C to a shell and type:

e2fsck /dev/hda4

Hugo

All fixed...... bada ATA cable between the 2 drives. pfiew.

How did your cable go bad just like that? Did you make any modifications to the drives yourself?

Riocar 10gig (for now) S/N : 10101747 amber

Actually, it was just circumstancial (I think):

It turns out that the unit works well if the drive is sitting on the case of the EMPEG, but it does NOT work if the drive is harnested inside (as it should be).

See Problem continuation...

It turns out that the unit works well if the drive is sitting on the case of the EMPEG, but it does NOT work if the drive is harnested inside (as it should be).

Drive cable? It is in different position with the drive tray out...

Dragi "Bonzi" Raos
Zagreb, Croatia
Q#5196, MkII#80000376, 18GB green