Unoffical empeg BBS

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

Topic Options
#326403 - 28/09/2009 19:25 Mk1 and Mk2 trouble...
banghi
new poster

Registered: 10/10/1999
Posts: 14
Loc: Olympia, WA
having a bit of trouble with my empegs... some i have been able to sort out by reading through the archives, some i have not. i own a couple of mk1's and a mk2. i don't do linux really, but know my way around a shell enough that i can follow instructions.

first problem, usb support. both my mk1's are fully functional, but i am only able to connect to them via serial. i wanted to use my vista laptop, but haven't been able to get it to recognize the USB. plugged in it asks for drivers, point it to where i unzipped the emplode2.0 download but it doesn't like them. the faq states "Reports are that the driver works with Vista but not with x64." this is what i expect my issue to be. the laptop doesn't have serial and the mk1's don't have ethernet. the only way to get it to work would be usb, so i think i am sol on this.

dusted off an old XP machine, installed emplode and the USB drivers. this was a fresh install, the box had never had either installed prior to this weekend. checked in device manager, shows USB as having 'SONICblue Rio Car' there. open emplode but keep getting 'unknown player on USB' in there. selecting the unknown player results with the 'The player appears to no longer be connected' warning. this machine has a serial port (unlike my laptop) and this is how i can currently connect to both the mk1's. i even uploaded a custom logo to confirm that part of the equasion is working.

worst case scenario, i update these players via serial. emplode loads music, slow as it is. i can live with this, one is for my wifes car and the second is a backup and test device. i am just puzzled as it seems USB should work.

second problem, mk2 drive. i bought it with two 18gig drives installed, and it worked great for a long time. a while back it started failing, not recognizing the drives and i just stopped using it. now that i have been dealing with the mk1's i thought i would tackle this beast. rather than bother with possible bad drives i pulled a 60gig drive from an old laptop that wasn't being used. figured i would run an update over it and that would wipe all the previous data, giving me a clean slate to toss music at. the old drives were both toshiba's and so was this one. i thought i would be able to do the upgrade without much difficulty. haha...

so i download mark lords bigdisk.v4 image from rtr.ca and run it over the drive. seemed to go well until i think i am having the 'fids' issue that was so well documented. the machine keeps giving me the 'drives already built' message. fine, i'll go in and delete fids as instructed and then reapply the image. only thing is that the last command to execute is 'rom' and my shell keeps giving me the 'command not found' message. trying the image again changes nothing. great, so now i decide i'll just connect the drive to my laptop and format it there. while i am at it i figure i will format the 18gig drives for safe measure. turns out one of them was dead for sure, so i know now that was at least contributing to my problems. i slap the 60gig back in the mk2, rinse and repeat. after reimaging i get the same 'drives already built' message. so i think, i'll try the one good 18gig drive. same thing. looking at the hyperterm bootup output i see...

Click to reveal..
empeg-car bootstrap v1.00 20000601 ([email protected])77,
hda: TOSHIBA MK1814GAV,
On DC power, quick bootwrote 0x0000 read 0xff0

e000 v1.04ta_test: w
Copying kernel...xff00
Calling linux kernel...
ide_data_test: wrot
Uncompressing Linux..................................... done, booting the kerne0xaaaa read 0xaa00rote 0xffff read 0xff00
ide_data_test: wrote 0
l.55
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 ([email protected]) (gcc versionDISK drive0xaaaa read 0xaa00
ide0 at 0x000-0x007,0x038 on i
2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009GAV, 17301MB w/0kB Cache, CHS=35152/16/63
Makin
Processor: Intel StrongARM-1100 revision 11

DISK driveMK1814GAV, ATA DISK drivee("Mak
Checking for extra DRAM:
c0c00000: wrote ffffffff, read e28cc001ata_test: wrote 0x0000 read 0xff00
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel 0xffff read 0xff00
Buffer cache hash table entries: 16384 (order 4, 64k)
hda: hda1 < hda5 hd
Page cache hash table entries: 4096 (order 2, 16k)

hda: hda1 < hda5 hda6 > hda2
POSIX conformance testing by UNIFIX(ext2 filesystem) readonly.
Linux NET4.0 for Linux 2.2
bas
Uncom
Based upon Swansea University Computer Society NET3.039g unused kernel memory: 4k initng the kern
NET4: Linux TCP/IP 1.0 for NET4.0
Builder image

b
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
bash-2.01# savenux............
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UARTot found
bash-2.01#
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
or forever

Signature is ffffffff 'ÿÿÿÿ'
bash-2.01# help
Tuner: loopback=0, ID=-1
GNU
show_message("Hijack v508 by Mark Lord")own-linux-gnu)
empeg display initialised.
Calibrating delay l
empeg dsp audio initialised

ide_data_test: wrote 0xaaaa read 0xab80[-e ename] [-nlr] [first] [last
ide_data_test: wrote 0x5555 read 0x5580
ttyS02 at 0xf803
ide_data_test: wrote 0x0000 read 0xff80job_spec] for NAME
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xab80
function NAME { COMMANDS ; }
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80D=-1ta_test: wrote 0xaaaa
ide_data_test: wrote 0xffff read 0xff80r] [-p pathname] [name ...]
ide_data_test: wrote 0xaaaa read 0xab80N | -N] [-n] pwd [-PL]
ide_data_test: wrote 0x5555 read 0xff80eg power-pic driver initialised (fi
ide_data_test: wrote 0x0000 read 0xff80 [-r] [-p prompt] [-a array] [ readonly
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xab8
RAM disk
ide_data_test: wrote 0xffff read 0xff80
set [--abefhkmnptuvxBCHP] [-o
ide_data_test: wrote 0xaaaa read 0xab80
ide_data_test: wrote 0x5555 read 0x5580on 0x334
bash
ide_data_test: wrote 0x0000 read 0xff64t found
2.95.
ide_data_test: wrote 0xffff read 0xff641# exitJan 9 16:06:35
ide_data_test: wrote 0xaaaa read 0xbf64otstrap v1.00 20000601 ([email protected])
ide_data_test: wrote 0x5555 read 0x7764
hda: TOSHIBA MK1814GAV, ATA DISK drivethere is anyone present who wants to u
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0xffff read 0xff00forever hold their peace...it seems not
ide_data_test: wrote 0xaaaa read 0xaa00
ide_data_test: wrote 0xffff read 0xff00
ide_data_test: wrote 0xaaaa read 0xaa00g by UNIFIXessage("Tuning hda5")
ide_data_test: wrote 0x5555 read 0x5500
l.
Linux version 2.2.17-rmk
hda: TOSHIBA MK1814GAV, ATA DISK driveca) (gcc version3/06/96
ide_data_test: wrote 0x0000 read 0xff00
Based u
ide_data_test: wrote 0xffff read 0xff00
Checking for extr
ide_data_test: wrote 0xaaaa read 0xaa00
c0c00000: wrote ffffffff, read e28cc00
ide_data_test: wrote 0x5555 read 0x5500
NetWinder Floating Point Emula
hda: TOSHIBA MK1814GAV, ATA DISK drivep.8030000 (irq = 16) is a
ide_data_test: wrote 0x0000 read 0xff00
ide_data_test: wrote 0x5555 read 0x5500
hda: TOSHIBA MK1814GAV, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: TOSHIBA MK1814GAV, 17301MB w/0kB Cache, CHS=35152/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:0c:00:1
b
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: 4k initBuilder image
show_message("Builder image")
show_message("Drives already built")

bash-2.01#


so at this point i am beat. i have RTFM and the faq, searched the boards and just don't know where i am failing. formating the drives didn't change anything and as i am getting the same results on different working drives i can only assume that the problem may lie within the player itself. if anyone has the time to puzzle this one out i would appreciate any guidance. sorry that this is so long and rambling, i was trying to be as complete as possible.

tia
_________________________
pax
clt (#155, 215, 303, 6000000000000000027)

Top
#326405 - 28/09/2009 19:52 Re: Mk1 and Mk2 trouble... [Re: banghi]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
Originally Posted By: banghi
plugged in it asks for drivers, point it to where i unzipped the emplode2.0 download but it doesn't like them. the faq states "Reports are that the driver works with Vista but not with x64." this is what i expect my issue to be.


Is your Vista computer running the 64-bit version of the operating system? Right click on My Computer and press PROPERTIES. Somewhere on that screen it should say either "32 bit operating system" or "64 bit operating system".


Quote:
dusted off an old XP machine, installed emplode and the USB drivers. this was a fresh install, the box had never had either installed prior to this weekend. checked in device manager, shows USB as having 'SONICblue Rio Car' there. open emplode but keep getting 'unknown player on USB' in there


And so the USB driver that you fed Windows was the one from the Emplode 2.0 zip file? And the player in question definitely contains the 2.0 firmware? If so, that *should* have worked. That's a real stumper.

If the player happened to have firmware that was earlier than 2.0 final, that would explain it.


Quote:
the machine keeps giving me the 'drives already built' message. fine, i'll go in and delete fids as instructed and then reapply the image. only thing is that the last command to execute is 'rom' and my shell keeps giving me the 'command not found' message.


Hm, from the sound of it, you are running the bigdisk *builder* image, and it should work.

That's situation you describe is a real catch-22. I've never had to actually do that particular procedure myself, my builder images always Just Ran.

RWM and ROM are just scripts which execute several commands internally.

Anyone have the proper commands that would execute the same steps as typing ROM would have executed?


_________________________
Tony Fabris

Top
#326406 - 28/09/2009 19:57 Re: Mk1 and Mk2 trouble... [Re: tfabris]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
And Mark, is there any chance that the Bigdisk Builder images could be hacked to remove that "drives already built" BS and just have it format with extreme prejudice? Or at least prompt?

Once upon a time, I was told that you just pressed Enter on that screen and it would continue the build. At some point I changed the Drive Upgrade Guide to say the new thing about removing FIDs first, possibly because pressing Enter didn't work any more, or had never worked in the first place. Did it ever work? I don't remember what that discussion was about.
_________________________
Tony Fabris

Top
#326407 - 28/09/2009 19:59 Re: Mk1 and Mk2 trouble... [Re: banghi]
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
Maybe someone should build a VMware appliance that can do emplode or jemplode.
_________________________
Bitt Faulk

Top
#326408 - 28/09/2009 20:30 Re: Mk1 and Mk2 trouble... [Re: tfabris]
banghi
new poster

Registered: 10/10/1999
Posts: 14
Loc: Olympia, WA
Originally Posted By: tfabris
Originally Posted By: banghi
plugged in it asks for drivers, point it to where i unzipped the emplode2.0 download but it doesn't like them. the faq states "Reports are that the driver works with Vista but not with x64." this is what i expect my issue to be.


Is your Vista computer running the 64-bit version of the operating system? Right click on My Computer and press PROPERTIES. Somewhere on that screen it should say either "32 bit operating system" or "64 bit operating system".


yeah it is, thats why i guess i am out of luck. i still hope to use it via ethernet if i can figure out the mk2 issues.

Originally Posted By: tfabris
Quote:
dusted off an old XP machine, installed emplode and the USB drivers. this was a fresh install, the box had never had either installed prior to this weekend. checked in device manager, shows USB as having 'SONICblue Rio Car' there. open emplode but keep getting 'unknown player on USB' in there


And so the USB driver that you fed Windows was the one from the Emplode 2.0 zip file? And the player in question definitely contains the 2.0 firmware? If so, that *should* have worked. That's a real stumper.


yes on both accounts. just took a few minutes to confirm. test mk1 connects via serial but not USB. both emplode and the mk1's about list version 2.0 for their respective ware.

Originally Posted By: tfabris
If the player happened to have firmware that was earlier than 2.0 final, that would explain it.


yeah, checked the 'about' of the mk1 and it clearly shows 2.0 on it. i did try to keep these somewhat up to date. wink


Originally Posted By: tfabris
Quote:
the machine keeps giving me the 'drives already built' message. fine, i'll go in and delete fids as instructed and then reapply the image. only thing is that the last command to execute is 'rom' and my shell keeps giving me the 'command not found' message.


Hm, from the sound of it, you are running the bigdisk *builder* image, and it should work.

That's situation you describe is a real catch-22. I've never had to actually do that particular procedure myself, my builder images always Just Ran.

RWM and ROM are just scripts which execute several commands internally.

Anyone have the proper commands that would execute the same steps as typing ROM would have executed?


if so i would love to give that a shot. it is the builder v4 i am using. have thought about trying earlier versions, but don't want to make a bigger mess than i already have. at this point i am not sure where to go, so again any help is very appreciated.
_________________________
pax
clt (#155, 215, 303, 6000000000000000027)

Top
#326409 - 28/09/2009 20:35 Re: Mk1 and Mk2 trouble... [Re: banghi]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
Originally Posted By: banghi
yeah it is, thats why i guess i am out of luck. i still hope to use it via ethernet if i can figure out the mk2 issues.


Yeah, Emplode with Ethernet works great on Vista, I use it every day. Doesn't solve your MK1 problems, unfortunately.

Hang tight for answers to your other questions, I'm sure Mark or others will be along shortly with solutions.
_________________________
Tony Fabris

Top
#326410 - 28/09/2009 20:41 Re: Mk1 and Mk2 trouble... [Re: banghi]
maczrool
pooh-bah

Registered: 13/01/2002
Posts: 1649
Loc: Louisiana, USA
Have you tried using the standard builder? I think 60 gigs is kinda on the borderline between which builder should be used. Sometimes when building I have better luck with the standard builder.

Stu
_________________________
If you want it to break, buy Sony!

Top
#326411 - 28/09/2009 20:54 Re: Mk1 and Mk2 trouble... [Re: maczrool]
banghi
new poster

Registered: 10/10/1999
Posts: 14
Loc: Olympia, WA
i downloaded a few different images from both the empeg site and mark lords. in the end i just stuck with his version 4 as it seemed as if it was the defacto one to use at this point from everything i had read. i'll go give the last 'official' release a shot. think that was 2.01 consumer i grabbed. i'll capture the log after it reboots and toss that up in a spoiler so it doesn't clutter the thread.

-edit-

well that actually cleared things up for me. from what i had read i thought that the version i was using would work for me. going back to consumer 2.01 seems to have worked. it loaded on the good 18gig drive flawlessly. i have opened the machine up via serial on the xp box with no problem. going to spend the rest of the evening putting 2.01 on the 60gig and getting it to connect to the laptop via ethernet.

still unsure why USB no workie on xp for the mk1's, but as i said if i have to suffer with serial for the time being, so be it.

thanks again for reading my troubles and offing good advice!


Edited by banghi (28/09/2009 21:25)
_________________________
pax
clt (#155, 215, 303, 6000000000000000027)

Top
#326412 - 28/09/2009 21:41 Re: Mk1 and Mk2 trouble... [Re: banghi]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
Originally Posted By: banghi
well that actually cleared things up for me. from what i had read i thought that the version i was using would work for me.


It should have. I wonder if Mark needs to look at that for some reason or other.

Did you receive the "Drive is already built" message with the standard builder?
_________________________
Tony Fabris

Top
#326414 - 28/09/2009 22:30 Re: Mk1 and Mk2 trouble... [Re: tfabris]
banghi
new poster

Registered: 10/10/1999
Posts: 14
Loc: Olympia, WA
nope, just kicked me to the 'end of playlist' message. from there serial worked. xp still didn't like UBS, got the same 'unknown player' message. thats on all my players, so i really doubt the issue is on their end. i am transfering one track atm just to get something on the drive then will go build the 60gig. ethernet didn't take off like i had hoped, but at this point i just want to close the box up before i start messing around with that.
_________________________
pax
clt (#155, 215, 303, 6000000000000000027)

Top
#326415 - 29/09/2009 00:13 Re: Mk1 and Mk2 trouble... [Re: tfabris]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14491
Loc: Canada
Originally Posted By: tfabris
Originally Posted By: banghi
well that actually cleared things up for me. from what i had read i thought that the version i was using would work for me.


It should have. I wonder if Mark needs to look at that for some reason or other.


"Drives already built" is the clue.
The version I enhanced won't build if the drives look "built".

I suppose I ought to remove the seat-belts and have it just blow away the contents regardless. Far more sensible, that.

Cheers

Top
#326426 - 29/09/2009 15:46 Re: Mk1 and Mk2 trouble... [Re: mlord]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
Originally Posted By: mlord
I suppose I ought to remove the seat-belts and have it just blow away the contents regardless. Far more sensible, that.


Or just allow the user to press any key to get past it and let it build anyway...
_________________________
Tony Fabris

Top
#326428 - 29/09/2009 16:51 Re: Mk1 and Mk2 trouble... [Re: tfabris]
maczrool
pooh-bah

Registered: 13/01/2002
Posts: 1649
Loc: Louisiana, USA
Quote:
Or just allow the user to press any key to get past it and let it build anyway...


Is the absence of this feature unique to Mark's builder? I've long been pressing 'any key' to force a build but can't recall whether that was restricted to the standard builder or not.

Stu
_________________________
If you want it to break, buy Sony!

Top
#326436 - 29/09/2009 18:19 Re: Mk1 and Mk2 trouble... [Re: maczrool]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
I don't know. There was some reason that I changed the FAQ.

The FAQ used to say Press Enter to make it build anyway.

Now the FAQ says delete your FIDs.

But this guy can't delete his FIDs!!!!!!!!!!

Why did I change the FAQ?

Was it because Press Enter never really worked?

Or is it because Press Enter doesn't work on Mark's stuff?

Don't know.
_________________________
Tony Fabris

Top
#326448 - 29/09/2009 20:35 Re: Mk1 and Mk2 trouble... [Re: tfabris]
banghi
new poster

Registered: 10/10/1999
Posts: 14
Loc: Olympia, WA
fwiw i did find information on pressing enter and deleting fids prior to posting, neither worked. i suspected that the mod batch/command might have been preventing the delete process from working, i never was quite clear on what that was to do.

regardless, i have the mk2 finally running with a lone 18gig drive. the other is dead and i can't get the 60gig to funtion properly. opening emplode via serial just crashes the program with that drive. ethernet is working for the mk2, still having the USB issue with both the mk1's. my next course of action is to find another xp box gathering dust and see if a different machine provides results.

should have done this a while ago, but just now got around to it. did i say thanks already? i was getting frustrated taking this on my own...
_________________________
pax
clt (#155, 215, 303, 6000000000000000027)

Top