Unoffical empeg BBS

Quick Links: Empeg FAQ | Software | RioCar.Org | Hijack | jEmplode | emphatic
Repairs: Repairs | Addons: Eutronix | Cases

Page 2 of 2 < 1 2
Topic Options
#317629 - 29/12/2008 16:40 Re: SSD upgrade woes... [Re: Major_Sarcasm]
Major_Sarcasm
member

Registered: 28/08/2003
Posts: 149
Loc: Isle of Wight, UK
OK, W set to zero and uploaded tracks with no errors. I guess that means that your modified hijack is what fixed the problem.

Just out of interest, will enabling/disabling write-caching have any performance benefits/detriments in this environment?

Do you have any idea why I was unable to use /dev/hdb to specify the slave SSD with hdparm?
_________________________
Steve

Top
#317634 - 30/12/2008 02:23 Re: SSD upgrade woes... [Re: Major_Sarcasm]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Originally Posted By: Major_Sarcasm
OK, W set to zero and uploaded tracks with
no errors. I guess that means that your modified hijack is what
fixed the problem.

Great. I'll make it an "official" release shortly.

Quote:
Just out of interest, will enabling/disabling
write-caching have any performance benefits/detriments
in this environment?

I think I'd suggest disabling it, as our kernel doesn't know
anything about safely flushing the write cache, and
(contrary to common opinion) the empeg s/w *does*
write to the media (dynamic data partition)
during normal playback operation.

So just leave write-caching
off for safety with these slow-writing SSDs.
For regular hard disks, no issues either way.

Quote:
Do you have any idea why I was unable to use /dev/hdb
to specify the slave SSD with hdparm?

No. But that *has to work* if you want a two-drive system.
I'm probably just missing something obvious..

Cheers


Edited by mlord (30/12/2008 02:25)

Top
#317635 - 30/12/2008 02:40 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Originally Posted By: mlord
Great. I'll make it an "official" release shortly.

Or maybe not. Sourceforge seems to have finally broken my scripts,
and removed the ability to easily upload binary files.

I refuse to use their absolutely STUPID "file release manager"
crap for Hijack, so this might be the end of Hijack availability
at Sourceforge
.

Hmmph.

EDIT: hacked it, working again. For now.


Edited by mlord (30/12/2008 11:44)

Top
#317638 - 30/12/2008 03:28 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
I've also updated the bigdisk builder stuff on my server,
to include Hijack v504 in the images. Untested, of course. smile

Top
#317642 - 30/12/2008 11:29 Re: SSD upgrade woes... [Re: mlord]
Major_Sarcasm
member

Registered: 28/08/2003
Posts: 149
Loc: Isle of Wight, UK
I added the second drive back in late last night and uploaded ~27GB of files with no problems whatsoever. I had a look in the fids folders on each drive and it seems to be balancing the files between the two.

Mark, as ever, I am most grateful for your assistance.
_________________________
Steve

Top
#317648 - 30/12/2008 16:34 Re: SSD upgrade woes... [Re: mlord]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 30555
Loc: Seattle, WA
Mark, you are awesome.
_________________________
Tony Fabris

Top
#318440 - 25/01/2009 04:57 Re: SSD upgrade woes... [Re: tfabris]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
I am using v504 disk builder image with a single 64 GB SSD of the same brand and getting a ton of these virtual memory errors:

VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")

This is on an old 12MB player, any ideas why?
_________________________
#080000512 green 12GB

Top
#318441 - 25/01/2009 12:15 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Which exact builder file are you using (name and bytecount, please)?

Can you capture a trace from the serial port while running it (helps a LOT)?

Thanks.

Top
#318442 - 25/01/2009 13:55 Re: SSD upgrade woes... [Re: mlord]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
builder_bigdisk_v3.upgrade
2.16 MB (2,267,745 bytes)
MD5 0b8b1f793a7e2a7e8253fad6a35afc41

Code:
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v504 (hijack@rtr.ca) (gcc version
2.95.3 20010315 (release)) #2 Mon Dec 29 23:29:04 EST 2008
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c0c00000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 80000512) 12MB DRAM
Command line: mem=12m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10944k/12M available (996k code, 20k reserved, 324k 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 v504 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 d0005000).
empeg RDS driver initialised
empeg power-pic driver initialised
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 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xff55
hda: 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
hda: 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
hda: 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
hda: 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
hda: 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
hda: TS64GSSD25-M, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TS64GSSD25-M, 61136MB w/0kB Cache, CHS=7793/255/63
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:10:02:0
0
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.
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 init+ /bin/mount -n /proc
+ log 'Builder image'
+ echo 'Builder image'
Builder image
+ echo 'POPUP show_message("Builder image")
9999 Builder image'
+ DRIVE1=
+ '[' -e /proc/ide/hdb -a -e /proc/ide/hdc ']'
+ '[' -e /proc/ide/hdb ']'
+ '[' -e /proc/ide/hdc ']'
+ /bin/mount -n -t ext2 -o ro,nocheck /dev/hda4 /drive0
+ '[' -d /drive0/fids ']'
+ /bin/umount /drive0
+ /bin/mkswap /dev/hda6
Setting up swapspace version 0, size = 16412672 bytes
+ /bin/swapon /dev/hda6
Adding Swap: 16028k swap-space (priority -1)
+ /bin/mkswap /dev/hda3
Setting up swapspace version 0, size = 24670208 bytes
+ /bin/swapon /dev/hda3
Adding Swap: 24092k swap-space (priority -2)
+ log 'Tuning hda5'
+ echo 'Tuning hda5'
Tuning hda5show_message("Tuning hda5")

+ echo 'POPUP 9999 Tuning hda5'
+ /bin/tune2fs -c -1 -i0 /dev/hda5
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
+ makedrive hda4 /drive0
+ dev=/dev/hda4
+ log 'Making hda4 filesystem'
+ echo 'Makishow_message("Making hda4 filesystem")
ng hda4 filesystem'
Making hda4 filesystem
+ echo 'POPUP 9999 Making hda4 filesystem'
+ /bin/mkfs.ext2 -v -s 1 -i 131072 -m 0 /dev/hda4
mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Linux ext2 filesystem format
Filesystem label=
488256 inodes, 62492850 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
7629 block groups
8192 blocks per group, 8192 fragments per group
64 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409, 663553,
        1024001, 1990657, 2809857, 5120001, 5971969, 17915905, 19668993,
        25600001, 53747713,

Writing inode tables: done
Writing superblocks and filesystem accounting information: show_message("1530.-1
 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
show_message("1530.-1 nomem err")
VM: do_try_to_free_pages failed for mkfs.ext2...
_________________________
#080000512 green 12GB

Top
#318443 - 25/01/2009 16:09 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Mmm.. looks like you are doing everything The Right Way(tm).

So, the mkfs thinks it is running out of memory,
which is very odd given the amount of swap space
we allocate for its use.

If I can find my 32GB CF card, I'll give this a try
on that later today in a Mk2 12MB unit. And then perhaps
again with a larger hard disk.

Cheers


Edited by mlord (25/01/2009 16:17)

Top
#318444 - 25/01/2009 16:18 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
If you grok Linux, you could just finish off the process by hand.
A reboot (from its present state) will give you a shell prompt
at the serial console, where you could re-issue the mkfs.ext2
command from the script by hand.

Cheers


Edited by mlord (25/01/2009 16:19)

Top
#318446 - 25/01/2009 22:32 Re: SSD upgrade woes... [Re: mlord]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
I know enough to fumble around, but I couldn't figure out how to get a prompt on the builder image as every reboot attempts to reformat the drive. Seems like it would be pretty easy to work around if I could get to a prompt. Is that mkfs cmd the end of the script?

Thank you so much for such a ridiculously fast response btw, and I really appreciate the help.
_________________________
#080000512 green 12GB

Top
#318447 - 25/01/2009 22:48 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Here's a builder version that logs you in, and tells you what to do.

Have fun. smile


Edited by mlord (25/01/2009 22:49)

Top
#318448 - 26/01/2009 01:09 Re: SSD upgrade woes... [Re: mlord]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
Thanks for that new image. However, when I manually run the first cmd (mkfs.ext2) I get the same nomem error.
_________________________
#080000512 green 12GB

Top
#318449 - 26/01/2009 01:30 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Originally Posted By: 101
Thanks for that new image. However, when I manually run the first cmd (mkfs.ext2) I get the same nomem error.


Mmm.. bummer, but not completely unexpected.

I'm not sure why it fails to use the swap space for memory, but.. oh well.

Can you connect the drive to a Linux box (internally,
or externally via USB or whatever)
and just do the same commands to it from there?

That's the workaround at this point.

Cheers


Edited by mlord (26/01/2009 01:31)

Top
#318450 - 26/01/2009 01:41 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
I've scrounged up a Mk2 and a 60GB (hard) drive here now,
and we will see what happens with it.. gimme a few minutes..


Edited by mlord (26/01/2009 01:42)

Top
#318451 - 26/01/2009 02:01 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Mmm.. no problems here. But regardless, this might help:

builder_bigdisk_v3_alt.upgrade

This one has tweaked mkfs options to (hopefully) reduce the amount of RAM required.

Give it a whirl..

Top
#318455 - 26/01/2009 12:12 Re: SSD upgrade woes... [Re: mlord]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
The alt one you posted (link is a little squirrely)seems to have made it through the script. There was one error "zeroing hda3":
/bin/cat: write error: No space left on device
Not sure if that was normal or not, just sounds like it wrote to the end.

Do you think the problem is related to the empeg-flash driver? Seems like something is being loaded that is bigger than normal and causing an issue with this SSD on a 12MB player.
_________________________
#080000512 green 12GB

Top
#318460 - 26/01/2009 13:32 Re: SSD upgrade woes... [Re: 101]
tman
carpal tunnel

Registered: 24/12/2001
Posts: 5528
Originally Posted By: 101
Do you think the problem is related to the empeg-flash driver? Seems like something is being loaded that is bigger than normal and causing an issue with this SSD on a 12MB player.

It doesn't mean flash as in SSD. There is a small amount of flash memory inside the empeg that stores some current state and config data.

Top
#318461 - 26/01/2009 14:11 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Originally Posted By: 101
The alt one you posted (link is a little squirrely)
seems to have made it through the script.
There was one error "zeroing hda3":
/bin/cat: write error: No space left on device
Not sure if that was normal or not

Yes, that's normal. Ignore it.

Quote:
Do you think the problem is related to the empeg-flash
driver? Seems like something is being loaded that is bigger
than normal and causing an issue with this SSD on a 12MB player.

No. Linux on the empeg doesn't even know you have an SSD.
It thinks of it and treats it exactly as a regular hard drive.

So, the _alt_ builder worked though, and you should now be all set.

Cheers

Top
#318466 - 26/01/2009 19:15 Re: SSD upgrade woes... [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
I've now updated the bigdisk builder images (at rtr.ca)
with Hijack v508. There's also now a new _v4_ builder
which uses a 4KB blocksize (rather than 1KB),
and a 4X higher bytes:inodes ratio.

These changes make it much more suitable for large disks
and/or low-memory usage.

Cheers


Edited by mlord (26/01/2009 19:16)

Top
#318474 - 26/01/2009 22:57 Re: SSD upgrade woes... [Re: mlord]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
Thanks again so much for the help Mark, all seems to be working.

Only issues I have now are config related. I've been using the old 2.0 beta for like 7 years and I need to figure out how to get the fader back and now the player no longer shuts off in the car. So I'll need to do some searches to get up to speed on restoring that functionality, and what else is new.

SSD issues seem to be resolved.
_________________________
#080000512 green 12GB

Top
#318526 - 27/01/2009 23:44 Re: SSD upgrade woes... [Re: 101]
101
new poster

Registered: 30/10/2000
Posts: 34
Loc: US
Okay, I am completely baffled. I've done some searches and apparently I have "home mode in the car" syndrome and saw all these threads about a blown diode and HW replacement etc.

I will say that being a HW guy (encoder replacement was much more straight forward to me than swapping in an SSD) this is ridiculous. I put in my old drive with the old firmware and all functionality returned with 0 issues. Clearly this is a software problem, yet there's many threads on diode replacement and I couldn't find anything pointing to software.

What is the deal here? I have been out of the loop for years and just want to replace my dying mechanical HD with an SSD.

Can I just image my old drive to the SSD? At this point I could care less about losing a few gig to an LBA issue. I just want it to work with no hassle, as I don't have as much time to spend on this as I would like.

Suggestions? Please?

_________________________
#080000512 green 12GB

Top
#318544 - 28/01/2009 13:05 Re: SSD upgrade woes... [Re: 101]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
What is shown on the Hijack Menu's "Force AC/DC Power Mode"
screen on your player?

Post the four lines here, please.

Top
#362525 - 10/09/2014 19:18 Re: SSD upgrade woes... [Re: Major_Sarcasm]
haffi
new poster

Registered: 04/06/2002
Posts: 19
Loc: Iceland
Hi all I know this is an old thread but I am having similar problems...

I inserted a SSD 120GB Kingston SSD now into the Empeg with Adapter and It is getting the HDA timeout issues on the Display.
Can someone help me with this ? Is there a way to telnet into the empeg ? my Serial port does way to much of Crashing my computer ( since its a usb adapter ).
I used the Big disk Image first and then the hijack 5.18.

I am able to upload some tracks but it crashes the player all the time.
I have tried swapping out the SSD and the Adapter , plus the HDD cable with the same results.
Thanks
_________________________
Haf■ˇr Hilmarsson
CCIE VOICE #24527
Iceland.

Top
#362526 - 10/09/2014 21:18 Re: SSD upgrade woes... [Re: Major_Sarcasm]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Yeah, my apologies for putting this on the back burner. Hijack has a telnetd built-in, which can be enabled by putting "ktelnetd_port=23" into the "[hijack]" section of the player's config.ini file.

For the adapter, I don't yet know what's wrong, and haven't made the time to investigate yet. But I have seem similar behaviour with some adapters in the past, and might still have one on hand that misbehaves like that. So.. there's hope.

With luck, it's just a timing thing: SSDs respond _instantly_ to stuff that takes milliseconds with mechanical drives, and something may just not be ready for that as soon as it ought to be.

Cheers

Top
#363920 - 02/05/2015 15:37 Re: SSD upgrade woes... [Re: Major_Sarcasm]
haffi
new poster

Registered: 04/06/2002
Posts: 19
Loc: Iceland
Any new Mlord ? my player works ok... but if I try to fast forward and randomly it freezez up , and I think your right with the timing issues.
Where can I start.

If I telnet to the empeg and try fsck -fay /dev/hda4 it just says

empeg:/# fsck -fay /dev/hda4
fsck -fay /dev/hda4
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (1): Memory allocation failed
Parallelizing fsck version 1.19 (13-Jul-2000)


my

empeg:/# hdparm -I /dev/hda
hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
Model Number: KINGSTON SVP200S3120G
Serial Number: 50026B72270195F5
Firmware Revision: 501ABBF0
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
Used: unknown (minor revision code 0x0110)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 234441648
LBA48 user addressable sectors: 234441648
device size with M = 1024*1024: 114473 MBytes
device size with M = 1000*1000: 120034 MBytes (120 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
Write-Read-Verify feature set
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* SATA-I signaling speed (1.5Gb/s)
* SATA-II signaling speed (3.0Gb/s)
* SMART Command Transport (SCT) feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
2min for SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50026b72270195f5
NAA : 5
IEEE OUI : 26b7
Unique ID : 2270195f5
Integrity word not set (found 0x0000, expected 0x6ea5)
_________________________
Haf■ˇr Hilmarsson
CCIE VOICE #24527
Iceland.

Top
#363921 - 03/05/2015 07:11 Re: SSD upgrade woes... [Re: Major_Sarcasm]
haffi
new poster

Registered: 04/06/2002
Posts: 19
Loc: Iceland
Player displays this and then the empeg is non responsive
0000.0 hda: err: stat_timo
_________________________
Haf■ˇr Hilmarsson
CCIE VOICE #24527
Iceland.

Top
#363922 - 03/05/2015 13:25 Re: SSD upgrade woes... [Re: Major_Sarcasm]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
When that message appears on the display, there will be a corresponding, more detailed message at the serial port.
Something like: hda: stat_timo: status=0x80
followed by another line describing what it was trying to do at the time.

Any chance you could capture those messages and post them here?
Based on the value it prints for "status=0x..", it might be possible to work around the issue.

In particular, if it says "status=0x88", and "no DRQ after issuing WRITE", then it's a very easy fix.

Thanks.


Edited by mlord (03/05/2015 13:33)

Top
#363923 - 03/05/2015 13:41 Re: SSD upgrade woes... [Re: haffi]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13494
Loc: Canada
Originally Posted By: haffi

If I telnet to the empeg and try fsck -fay /dev/hda4 it just says

empeg:/# fsck -fay /dev/hda4
fsck -fay /dev/hda4
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (1): Memory allocation failed


To work around that problem with fsck, just do "swapon -a" before starting the fsck command.


Edited by mlord (03/05/2015 13:42)

Top
Page 2 of 2 < 1 2