Anyone know what the largest hard drive you can put in the player is? So far the biggest Ive found is 120 gig.

The only real limit is physical size, and I think all new drives are small enough to fit in. Also, higher capacity drives require a special procedure for installation, but that's a one-time deal per drive. 120GB seems to be as big as they get these days.

One thing is that if you have an incredibly huge DB then you might need more RAM. You'll probably want to do the set max FID for the dynamic data partition hack on the player binary as well.

Greetings!

There should be no trouble at all with the 120GB. There are a few small things to be aware of, as mentioned above, but there is nothing that should stop you. I am personally holding off for perpendicular storage at the moment, but the theoretical maximum is 2x120GB.

Seagate 160GB drives will be out later this year, with a promise of larger drives soon after. Perpendicular is the next major step forward for drive makers, so you will see a lot of vendors leapfrogging capacities in the near term.

As long as you are IDE, you should be okay.

Actually, Seagate has announced a 160GB 2.5 inch drive for the November timeframe. The other players are soon to follow in early 2006 with 180, 200 and beyond. They are talking about getting even higher densities into 2007, upwards of 300GB.

As for the flash animation, it really reminded me of the old Schoolhouse Rock episodes...

Greetings!

Thanks to all the people who pointed out to me that the new Seagate Momentus 5400.3 160GB laptop hard drive using perpendicular storage will become available in February. Still, their list price of $375 per drive is a bit extreme at the moment, especially when I still have a few GB free with dual 100s... Tempting...

Looking at that release statement, it appears they are selling it as an external USB 2.0 drive. Hopefully they will realize people will want it in their notebooks, and sell it without the markup for the enclosure. If not you could always ebay the enclosures.

Well, the enclosure variation (S-ATA also) are a few months later, if I read it correctly. The bare drives should ship sooner (I hope).

OK guys, form an orderly queue here.

Resistance is futile.

Must... resist... 320GB empeg...

On that same page is a laptop drive I'm looking forward to put in the Empeg when available. The Endurastar's are suppose to operate in ranges of -20°C to +85°C and supposedly more suited for automotive uses e.g. navigation & the like.

Ah, but the capacity!!! Wasn't there a tread where Hugo or Rob had a few of these drives as "samples"???

Well, I've just got a Seagate Momentus 160Gb drive and tried it out.
With mlords big disk builder.
No dice.

The serial output shows it trying todetect it, fails then kernel panics.

It aint power. The seagate label suggests 0.487A, I tried an old travelstar with a 1.1A requirement and it works fine. Spinup surely wont take that much more, besides, it does spin up ok.

From various testing at work with hard drives in our products (this one was a sample. perks) I've been finding issues with spin up times (was causing us problems) and drives not actually being ready before the OS starts looking for them.

Has anyone had a similar problem with dries in the empeg?

Is anyone running a Seagate momentus 160Gb drive?
I can grab an 80Gb tomorrow and try that out. Surely it wont be a capacity issue with mlords big disk upgrade?

empeg-car bootstrap v1.02 20001106 (hugo@empeg.com)
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-empeg52-hijack-v488 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Feb 15 10:29:26 EST 2008
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 30103019) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (992k code, 20k reserved, 368k 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 67706d65 'empg'
Tuner: loopback=0, ID=-1
show_message("Hijack v488 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 d0005680).
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 0xffc0
ide_data_test: wrote 0xffff read 0xffc0
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x57c0
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0xffff read 0xff00
ide_data_test: wrote 0xaaaa read 0xaa00
ide_data_test: wrote 0x5555 read 0x5500
hda: ST9160821A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9160821A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9160821A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9160821A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9160821A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9160821A, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: ST9160821A, 152627MB w/8192kB Cache, CHS=19457/255/63, LBA48
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:26:0b:cb
Partition check:
hda: unknown partition table
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). ½Õ¹ÑõÅ)5ÿEXT2-fs: unable to read superblockv0.03 (19980601) ѽÉõÉÍ¥éõÅÁÉÑ
Kernel panic: VFS: Unable to mount root fs on 03:05)5?¦&'¦ÝõÁ±Ý
¹Ñõɱ±¥µ¥ÑõÁ)5VÓª±­Í¥éõÅÁÉѱ½ )kk«kÍå½¹¹½Ù¥

Nothing wrong in that boot log -- the drive is working perfectly normally, as is the kernel.

But what *is* wrong, is that the builder has not successfully built the drive prior to this boot attempt.

Cheers

Yeah, a 160 should work with the bigdisk builder, right? I'd say, try running the builder again. Did you already try it more than once?

Yeah I tried it a couple of times and it sort of hung part way through I forget exactly where now, but was during the windows process.

I know the 20Gb one just sailed through after I removed the 160GB one. I didn't have to re-run the windows app I think ?

I'll blank the disk totally and try it again.
Then try the 120 if I'm unsuccesful.

OK back at home now.

Trying the 160Gb I get this:



It sits at that for ages, then I get this:



Then I hook up PuTTy and power cycle the empeg and I get this:

empeg-car bootstrap v1.02 20001106 (hugo@empeg.com)
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-empeg52-hijack-v488 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Feb 15 10:29:26 EST 2008
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 30103019) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (992k code, 20k reserved, 368k 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 67706d65 'empg'
Tuner: loopback=0, ID=-1
show_message("Hijack v488 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 d0005800).
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 0xffc2
ide_data_test: wrote 0xffff read 0xffc2
ide_data_test: wrote 0xaaaa read 0xaa82
ide_data_test: wrote 0x5555 read 0x57c0
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0xff42
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff40
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
ide_data_test: wrote 0x0000 read 0xff42
ide_data_test: wrote 0xffff read 0xff42
ide_data_test: wrote 0xaaaa read 0xaa02
ide_data_test: wrote 0x5555 read 0x5740
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:26:0b:cb
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



So no dice then.



With the 120Gb and just the power cycle, I first get this:

Probing primary interface...
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0xffff read 0xff00
ide_data_test: wrote 0xaaaa read 0xaa00
ide_data_test: wrote 0x5555 read 0x5500
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0xffff read 0xff00
ide_data_test: wrote 0xaaaa read 0xaa00
ide_data_test: wrote 0x5555 read 0x5500
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6



Then this after a very check power cycle (hard power hardly removed):

Probing primary interface...
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0xffff read 0xff00
ide_data_test: wrote 0xaaaa read 0xaa00
ide_data_test: wrote 0x5555 read 0x5500
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0xffa5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9120822A, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6




Now, for the empeg this is possibly a shot in the dark on my part, but it tallies with some of the problems I mentioned earlier with newer hard drives requiring much longer spin up times.
The second attempt at detecting the 120Gb seems to have found it much faster.
I assume that is what the above info refers to ?

I can get the 160Gb to appear in the serial output in the same manner, quickly recycling the power to the empeg.

So, is it possible to have some sort of wait cycle placed into the kernel before an attempt is made to detect the hard drive?
This is what I've had to do at work to make hard drives work correctly.


e.g. Spin up till drive ready times are running at 16 seconds !!! on newer Seagate SV35.4 drives.


P.S: 120Gb installs ok, but really want to use the 160Gb :o)


Is there a reset header on the PCB which I can trip to reset the empeg without having to lose the power? I wondered about tripping the 3.3V jumpers but that doesn't sound like a hugely fantastic idea.
That way I can keep drive power but restart the kernel over.

You are getting the pump error when running the builder upgrade file? Or just when you try to install fresh player software after the builder failed?

Remember that the builder must run to completion and reach the stress test before you can even think about installing fresh player software. Make sure you're following all the steps in the drive upgrade guide to the letter.

Check this FAQ entry regarding the pump error:

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

If there's an active Hijack kernel in flash, I think it's got a "Reboot Machine" option on its main menu somewhere.

OK, now I've done the 160Gb and here is how...


When the instructions say to leave the empeg off I've ignored them and left it turned on in a state of kernel panic.

When the builder says it's looking for the empeg I have very rapidly switched the power to the empeg on and off.
This seemingly doesn't give the drive enough time to spin down and allows the disk builder to see it.


If I repeat the process following the builder instructions and leave the emepg turned off before detection, the pump fails everytime.

I can only assume this is because the system didn't have enough time to find the disk.



mlord; could Hijack possibly hold up the kernel from detecting the hard drive for a configurable period? Or would that have to be done elsewhere, ie: a custom build of the main kernel?


So, now I have a built drive. I cannot fail to get the system to see it. Maybe now it's warmed up the system is able to detect it better?!?!
I know I've had problems detecting a disk in the past which has been out in the car all night in winter.

No have the player software installed. Will leave it off till tomorrow and see if it has trouble detecting the disk then after a long cool down.

Is that what you've got? Sixteen seconds is probably long enough to defeat the caching algorithms, which pre-load about the first ten seconds of upcoming tracks in the hope that that's easily long enough to spin the drive up (the worst ones we could then find were about five seconds).

Peter

That's good sleuthing. I'll update the FAQ entry about "Bad Pump".

Peter:
No, but to give those as an example. Perhaps poorly. They are 3.5" drives designed for the DVR and set top box markets.
Shocking isn't it.

I'm running a Seagate Momentus 5400.3 drive, the specs annoyingly don't say for this drive:

http://www.seagate.com/docs/pdf/datasheet/disc/ds_momentus_5400.pdf

I'll see about asking our contact tomorrow for the figure.



Tony:
The player software seems to detect the drivee a lot better. It certainly takes longerfrom watching the debug before it goes looking for it!

I'm not touching it for now (too easy to break it). You can rebuild the kernel from source, and change the detection logic as needed for your setup.

The file is linux/drivers/block/ide-probe.c .
Look for the line "timeout = (HZ/4);".
Make that a bigger number (say, (HZ) instead of (HZ/4) and give it a try.
HZ means "one second".

Cheers

Hi,

I have used the Western Digital WD2500BEVE 250 GB Drives and have never had a problem with spin-up time. They seem to spin up within a few seconds (both drives) in empegs.

Is the Seagate that much slower?

I haven't had any trouble installing drives in my empegs.

Ross

He's using a slow 3.5" desktop drive, rather than the usual snappy notebook drive.

What makes you say that? He said it was a Seagate Momentus 160gb drive, and a quick google tells me that drive is a laptop drive.

The drive with the 16 second spin up time wasn't that drive, it was a 3.5 inch one.

Sorry, missed that point.

Sorry. I confused the issue by mentioning that.
It was meant as a reference to modern drives taking longer to psin up and recently the trouble I've been having getting them working in our legacy products (PATA change to SATA is causing troubles but fixable ones).

As luck would have it, our Seagate rep is in tomorrow and the question about the Momentus is in our brief to ask, since it isn't in their technical documents.
Hopefully the person asking will remember for me.

I'll look about the kernel, it'll involve asking someone to do me a favour, or a lot of time on my part looking at setting up a development environment. Thanks for the walk through mlord !

The saga continues.

I've been just listening to the radio without any mp3's loaded on the unit and came to do that yesterday but cannot.
Emplode doesn't likeit, it quits with a message along the lines of: Failed to open tags (0xc0041002)

So I deleted the partitions on the drive and used Mark's version 10 of the big disk builder. Previously I'd used version 3 and heeded the warnings about it being experiemental.
I also used his build of the code with hijack 488 preinstalled.
Worked fine, but still I get the same message.

For whatever reason it's not liking this 160Gb drive.
I looked over the partitions are suggested in other threads:

http://empegbbs.com/ubbthreads.php/ubb/showflat/Number/306417
http://empegbbs.com/ubbthreads.php/ubb/showflat/Number/311430

But giving in for now.

I'm about to swap down to a 120Gb, but happy to debug if it'll help people out in the future. I can stick it into a spare empeg for testing.

I'm hoping the 120Gb will work ok.

The original 20Gb which came out of it works fine.

OK, life hates me.
The 120Gb drive isn't working either.
Same issue.

Emplode says:

Download failed while checking database
Error 0xc0041002




I'm sure I read the FAQ correctly.
Big disk builder kernal upload with the tool. Check.
Player kernel upload with same tool. Check.

0xC0041002 is "No such file or directory" (Player error)

Clearly it can't find its database files.

Did it look like the builder upgrade and the player upgrade both worked?

If so, get to a shell prompt and see if you have the "fids" folder in the expected location.

If so, see if forcing a database rebuild fixes the problem.

I remember when I upgraded my Empeg with 2 160GB drives that I had problems with the V10 disk builder. I went back to the V9 disk builder and everything worked.

I also did one sync using Jemplode .70 after the upgrade only setting the config.ini.

Attack, thanks for that. I'll give it a whirl with my spare player. Sick of taking the other one apart and it's only just wearing it out more.