Greetings!

NO!!!!!

I just received my empeg after having it get stuck in customs for five days. Booted it up, and ... it shows a very nice logo. Nothing more.

I went into hyperterminal and received the same series of messages that Alex Lear (alear) received. See boot log at the bottom of this message. I then went in and ran the boot tests.

Well, there are two items that concern me. 1) cs4231 sometimes fails as seen in the test log (not always, only on occasion), 2) cannot find root device. From reading Alex's problem, it sounds like it might be a hard drive issue. Has anyone seen cs4231 errors before?

I have a bad feeling that I will have to send this back. I hope not to - I have already been hung up in customs once for a week. If there is any way I can repair it...

Note: I cannot hear the drives spin up. I don't know how quiet the drives are, but (if they are spinning) they are really quiet... This is a dual drive 36GB configuration (maybe 40gb???). I have also tried to load the 1.01 developer image and the 1.0 developer image - neither will load. Emp-upgrade cannot find the unit.

Help. I am also sending a copy of this posting to support@empeg.com, just in case...

---------
1) bootlog

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

Copying kernel...
Calling linux kernel...
Uncompressing Linux.................................... done, booting the kernel.
Linux version 2.2.14-rmk5-np17-empeg35 (mac@fatboy.internal.empeg.com) (gcc version 2.95.2 19991024 (release)) #19 Fri Aug 4 15:58:47 BST 2000
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 90000587)
Command line: mem=12m temp=38
Calibrating delay loop... 207.67 BogoMIPS
Memory: 11000k/12M available (968k 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
empeg display initialised.
empeg dspaudio driver initialized
empeg audio-in initialised, CS4231A revision a0
empeg infra-red support initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004700).
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:02:4b
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: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

---------
2) testlog

empeg-car bootstrap v1.00 20000601 (hugo@empeg.com)
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...
0000 empeg-car board test version 0.04
0100 ram test starting
0110 testing ic 1 (0-3mb, low word)
0120 testing ic 2 (0-3mb, high word)
0130 testing ic 3 (4-7mb, low word)
0140 testing ic 4 (4-7mb, high word)
0150 testing ic 19 (8-11mb, low word)
0160 testing ic 32 (8-11mb, high word)
01f0 ram test done
0200 ide detect
0210 command issued
0212 drq=1 but irq=0 (no drive connected?)
0300 dsp/i2c test
03f0 dsp/i2c ok
0400 temperature detect
0410 temperature is 36
04f0 temperature ok
0500 usb detect
0510 usb rev 1012
05f0 usb ok
0600 ethernet detect
0610 ethernet rev 334b
06f0 ethernet ok
0700 cs4231 detect
0711 cs4231 not responding \* other boots report this as "0710 cs4231 rev a0 ; 07f0 cs4231 ok" *\
00f0 tests complete


Paul G.
Q# 15189
SN# 090000587
Status: D.O.A. - 29 Sept 2000 (36GB Green)

Looks like the now infamous drive cable issue to me.

I won't be the one to tell you to void your warranty (that's Tony's job ;), but I'll bet that if you pop the lid you'll find a drive cable dangling.

-Zandr

-Zandr
Mk.I #150
Mk.II #39

I know how you feel. I hope it is as simple as an unplugged drive.

Alex Lear

Hmm, it does look like a drive cable off; these are now hot-melt glued in the factory so it shouldn't happen at all :(

Rob has intstructions about how to open the empeg & check the cable - unfortunately, he's on his way to the european meet now, so it'll probably have to wait until monday.

The CS4231 fail is quite possibly due to the drive cable being partially off - it is probably loading the bus down in strange ways.

Hugo

Greetings!

I hope it is that simple a problem. I can handle going in and adjusting the cables - FedEx'ing the unit back is what worries me more. The FDA seemed to take a strange interest in the unit last time. I guess they handle the FCC paperwork. That, and I would *really* like to start playing / loading / tinkering with the empeg...

Meanwhile, this is a dual drive unit. It may also (I don't know for certain) be one of the first ones with the 2 x 20GB drives instead of the 18. The unit was shipped one day after Rob's announcement. Some other assorted thoughts (mostly about manufacturing):

a) If these are 20GB, could the order for new drives caused manufacturing to stop hot-gluing the drive cables?
b) Is manufacturing not gluing dual drive units at all?
c) If these are 20GB, could a change in physical disk size make the cables more likely to slip?
d) Is there any way I could find out in the present state what size these drives are?
e) Are there any other self-test / boot key sequences, like ^T, that would give any additional information?

Paul G.
Q# 15189
SN# 090000587
Status: D.O.A. - 29 Sept 2000 (36GB Green)

a/b/c - No, the drives will definitely be glued. I suspect you have a 40gb unit, but I can't be sure without the serial number (and even then I'd need to get into the sales database... which I don't know how to use!).

d/e - If the unit can't find the drives, it can't identify them unfortunately.

Hugo

I won't be the one to tell you to void your warranty (that's Tony's job ;)

Okay, fine then.

Pgrzelak, the FAQ section of the BBS has a hard-disk-upgrade document. Somewhere in there you'll find details on how to open the Mark2 player lid. If you choose to do this, let us know how it goes. I think we're all very curious to see if/why the cabling came undone after they'd already implemented the gluing fix. Got a digital camera?

One thing I fear is that the devices are somehow being mishandled in transit. If this is severe enough to cause the cables and the glue to come undone, how safe can the drives themselves be?

___________
Tony Fabris

Greetings!

I have read through the FAQ, and I don't think I will have any problems getting into the unit, although I might have to dig around for the right hex tool / Allen wrench. I will await "official approval" before opening the unit, though. Tempting though it may be, I don't want to void the warranty. Not yet, anyway...

I will keep everyone up to date as to what happens. I strongly suspect that this unit was not glued, but if it was (and still came loose) I share your concerns.

As to the digital camera - bad timing. I just lent it to someone at work. He is getting married / honeymooning in Hawaii... I will see what I can do. I doubt I will be able to get thermal scans though!!!

Paul G.
Q# 15189
SN# 090000587
Status: D.O.A. - 29 Sept 2000 (36GB Green)

Accordind to Rob in an e-mail to me about my delayed unit, the FDA is concerned due to "hazardous radiation" that can be emmitted from that little Kenwood remote. I guess the FDA hasn't kept up with modern times if they don't know the effects of IR.

In the meantime my player works normally. Rob sent me instruction on how to open the player. The problem was a loose hd cable.
Sometimes the player worked great, sometimes he didn't boot up. The problem seems now to be solved. No problem for over 3 weeks.

Alex

Greetings!

Well, I got the "official go-ahead" from the folks@empeg to check the drive cables.

First impressions:

1) They really mean "no user servicable parts inside".
2) Child labor is the only way anyone can work for any length of time in such a confined space.
3) I agree with the "do not enter" warranty policy. It is a very compact design, with little space to spare. I am not a small person (read this as very large), and working in the unit made me a bit nervous.

Taking the fascia off was easy. I had a brief moment of worry when the bottom button decided to jump off the table onto the floor, but it did not get away.

Opening the unit, I did not notice any hot glue around the hard drive connectors. It may have been on the bottom of the tray, but I did not see any. A close visual inspection showed nothing wrong. Sigh.

Removing the shock tray was a bit tight. At first, there seemed to be a slight cable resistance at the left-rear of the unit, but it lifted free quite easily after I was able to get my fingers in there. I looked at the main board. Visually everything was OK. I placed my finger on the hard drive connector, and gave a slight push. It slid onto the pins with a reassuring "THOK". Well, it was probably barely on. It looked connected, but was just hanging in place. One note: FedEx cannot read or understand the concept of "This End Up". Maybe being shipped, stuck in customs and delivered upside-down shook the connector loose???

Closed up the unit, and tried it out. Perfect! I loaded up Developer 1.01 RC2 without any problem. Configured the time and initial settings. My next step is to do the "no guts, no glory" attempt to download 21GB of music at one shot. This is running as I type. So far, it progresses well...

Thanks to the folks@empeg - great unit! Also thanks to Alex Lear and Tony Fabris for the documentation on how to get at the player. I studied it well in advance of the notification, and I found it extremely helpful!


Paul G.
Q# 15189
SN# 090000587

I've never known of a warranty return to get delayed. There are four reasons:

1. Value is low - $100 - because we can choose an almost arbitrary figure for second hand goods
2. Package is marked as re-import following temporary export
3. Duty is charged to empeg - FedEx have our product profile on file and know that there's no charge for a car player
4. The remote isn't included, so the FDA don't get involved

Also, please refer to the post I'm about to enter into general.

Rob

I see this as a "good news, bad news" kind of thing:

Good news: The problem was simply because there wasn't any glue on the connectors.
Bad news: There wasn't any glue on the connectors.

Hugo, Rob, have you been practicing your dope-slaps? I think someone at your assembly facility is in dire need.

___________
Tony Fabris

I'm not aware that they have ever glued the connector onto the main board - it's the drive connector that had a tendancy to come off. They probably deserve the dope slap anyway for not pushing the connector on properly in the first place.

Rob

It seemed to me that he said there wasn't any glue at either end of the cable, drive or motherboard...

___________
Tony Fabris

At least none that I saw. I examined the hard drives from above, looking into the unit. I did not see any visible glue from that angle. When it looked fine to me, I moved on to the main board.

I think FedEx deserves some "talking to" because they are the ones who had the thing upside down. This is a pet peeve of mine - it very clearly says "This End Up" on the box.

I am extraordinarily happy. The sync is proceeding very well. I hope to have everything running this evening, and to actually install the unit this weekend.

Paul G.
Q# 15189
SN# 090000587

Except mine. It had a remote in it on the way back, and was promptly delayed a bit so customs could cut the bottom of the box open to get to the unit. Lucially I was on vacation and didn't notice the delay until I got back to see the wonderful sight of a working empeg again.

Customs did hate me for some reason though. I really don't want to see the day when I am tracking my MkII to see it delayed in customs.

Greetings!

Well the sync finished, and I am happy to report that the USB drivers / protocols seem to be working flawlessly. I don't know about what other people have seen, but I have been able to do very large syncs without problem.

Paul G.
Q# 15189
SN# 090000587 (40GB Green)

This is great news. Did you do all 21gb in a single synch? I think that'd be a record.

If not, what was the largest chunk you did at once?

___________
Tony Fabris

Actually, in two syncs. But the biggest chunk, 20GB, was in one sync. I dragged my entire library (pre-formated in a W2K directory structure of /artist/alphabetical/name/track) over and let it run overnight. It took about 14-16 hours, but it succeeded without incident. The rest of it was just odds & ends that I decide I had space for, a new album that just arrived in the mail and some assorted playlists that I added later.

I don't know what problems people were having with USB sync before, but it is either fixed in 1.01RC2 or it depends on system resources. I run W2K Pro, empeg is my only connected USB device, 256MB RAM. Also, I left it overnight, so their was very little contention for resources.

Paul G.
Q# 15189
SN# 090000587 (40GB Green)

Hmm

I must say I have less positive results with emptool (linux) over ethernet. It frequently locks up for me ... During syncs. It transfers about 10 to 20 Mb sometimes and then the percentage display just ... freezes ... Maybe I am missing something but it is something that has happend to me several times now.

Cheers,
Hans

Mk2 - Blue - 080000431

I do believe that 20gb in a single synch is a record. At least for end-users, anyway, I don't know what the Empeg folks have tried in internal testing.

Regarding the Linux Emptool lockups: Hans, were you running 1.01 RC2?

___________
Tony Fabris

Yes, I am, developer release (I just couldn't resist that ).

Hans


Mk2 - Blue - 080000431

I had my emptool freeze (actually, it seems is was empeg side that was freezing) intermintently over Ether, after half a CD worth of music or so, with 1.01B2 (I was trying to fix a DHCP problem with it). With 1.0 syncs are OK (but I usually transfer CD by CD). Syncs over serial don't work at all (but terminal does, so, with working Ether I don't care). I am using an ancient IBM ThinkPad 380ED with RH5.2 and Xircom PCMCIA 10Base-T adapter. (On WinNT both serial and Ether work.)

Have you tried to downgrade to 1.0?

Good luck!

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

The final 1.01 release might fix your problem. You said you had the player freeze on you (not emptool). There is a note in the 1.01 final release notes saying that they fixed a problem where the player might intermittently freeze during synchs.

I don't know when 1.01 final will be announced- I got it today because I'm an alpha tester (and Mike, if you're listening, it's been working fine for me, you ought to post it on the main web site).

___________
Tony Fabris

I don't know when 1.01 final will be announced- I got it today because I'm an alpha tester (and Mike, if you're listening, it's been working fine for me, you ought to post it on the main web site).

I don't normally read General (If I did then I wouldn't get any work done) but you caught me this time... :-)

I nearly forgot about announcing it properly but it's up there now.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

Hi,


I do believe that 20gb in a single synch is a record. At least for end-users, anyway, I don't know what the Empeg folks have tried in internal testing.

Not trying to claim the award here, but when I 1st received my MKII and the intial dual drive bugs were ironed out, I did over 30G on a single weekend session without a single problem using W2K .

Regards,




_________________________________________
John, (MK1 #114-20G, MK2 #15-36G).

So, the beta RC2 is now outdated/obsolete or is it the same just a slimmer build? Just wondering if I should download any beta while waiting for the EMPEG to ship/arrive...gosh i hope it is soon....

I am a number, BUT I am almost a free man! And that number is 15562 which now equals an 18Gb Green!