Emergency S.O.S.

Locked New Topic
RELATED
PRODUCTS

Post

The tech guys are @ NAMM.
I've got major shows around the corner, and I've changed nothing lately...
I use my Receptor (Rev. C) everyday, and tonight at a rehearsal, it would not go past it's 'Initializing System' window.

I don't ever connect a mouse or screen directly to the unit ~ this was the only thing the woman who answered at Muse could think of.
I also tried un-plugging the power supply
I also tried powering-up while holding both the Multi & Setup buttons at the same time (she suggested that as well)

Now I'm home, and the problem persists ~ I was thinking, wishing, it was a problem with the power at the rehearsal studio... Nope.

Can anyone help me, PLEASE?
JV

Post

Hi JV,

Maybe you've tried those things, but you never know:
-first of all, did you install the log fixer ? (see other thread discussing that point)

-Try connecting an external screen and a mouse and a keyboard.Start the receptor, do what the screen tells you (i don't remember the actual key , del or tab...) to enter the unix menus instead of the initializing process, and then, in the menu, check that the time and date are the right ones.If not, modify them. Sometimes it's the reason why...
-Another weird thing that happened to me, as i said in another thread (maybe you've already read it): The audio card, which is vertical card inserted in a slot and tightened to the real panel by two screws, seems to be very sensitive.I was stuck like you in the initialisation process. Muse tech told me to unscrew that card from rear panel, remove it from the slot (carefully note how the connections are made before doing that !), then put it back in place and retighten the screws, verifying that it's very firmly installed. It worked for me ...
-You can also check that your rams are firmly inserted in their slots.

Good luck,
Jean-Luc

Post

Thanks Jean-Luc,

I installed the Log Fixer, about a month or so ago.
As I said, I use my Receptor almost everyday... this has me baffled.
I'm really hesitant to open it up and make adjustments ~ I think I'll call them again, before I take any action.
JV

Post

JayVee wrote:Thanks Jean-Luc,

I installed the Log Fixer, about a month or so ago.
As I said, I use my Receptor almost everyday... this has me baffled.
I'm really hesitant to open it up and make adjustments ~ I think I'll call them again, before I take any action.

I think that's exactly what happened when I first got the receptor shipped after purchasing .. the answer was to basically open it up and make sure all cables connecting to the motherboard were seated properly .. basically I unplugged and plugged in everything that I could. She started up next attempt.

-giz

Post

Like I said, I've hesitated to go 'under-the-hood', but it does seem the logical course of action, before rush shipping to California.

I'll still try to speak with a specialist before the end of the day...

I'm scared :-o
JV

Post

gizmostatic wrote:
JayVee wrote:Thanks Jean-Luc,

I installed the Log Fixer, about a month or so ago.
As I said, I use my Receptor almost everyday... this has me baffled.
I'm really hesitant to open it up and make adjustments ~ I think I'll call them again, before I take any action.

I think that's exactly what happened when I first got the receptor shipped after purchasing .. the answer was to basically open it up and make sure all cables connecting to the motherboard were seated properly .. basically I unplugged and plugged in everything that I could. She started up next attempt.

-giz
I had the exact same scenario two days after taking delivery of my receptor two years ago. Muse advised to open it up and check cables, which I did, and the problem didn't reoccur.

Post

Well, what the @$%#!!!
I'm inside and have not seen anything that looks loose.
Regardless, I've followed some of your suggestions:

I pulled out and replaced just about anything I could, including the RAM... Still not happening.

the Audio Card that Jean-Luc described, is NOT attached the same way his is; I can't see how it's fastened, if at all, but if the vertical card, next to the Hard-Drive is it, it's in there very tight.

This is absolute hell for me, the timing could only be worse if it happened on stage.

I'm hoping someone might suggest something else, or I'm putting the cover back on, and likely looking at a $200. each way overnight courier on Monday...
JV

Post

[quote="JayVee"]Well, what the @$%#!!!

the Audio Card that Jean-Luc described, is NOT attached the same way his is; I can't see how it's fastened, if at all, but if the vertical card, next to the Hard-Drive is it, it's in there very tight.quote]

HI again,

Maybe they've changed the way it's attached,(a firm slot and screws in the REAR PANEL) but i think it's worth trying:like yours, mine didn't seem loose at all, but when I tried this, it solved the problem (I don't know, maybe a matter of static electricity, or maybe a coincidence, but I had spent many days like you trying everything, and when I did that, My receptor started and it never happened again...)
Have you tried what I suggested about the Time and Date? (You'll need a external screen for that).It's quite simple, you just have to do follow the instructions on screen to enter the menus before the receptor welcome screen appears)

Post

I didn't try attaching a mouse & monitor...
JV

Post

JayVee wrote:I didn't try attaching a mouse & monitor...
You should try...You'll also need to attach an usb keyboard , because you'll have to type something to enter the menus, and then if the time and date aren't the right ones , to correct them...Don't worry , it's totally safe doing this.You just follow the instructions on screen.
(I don't remember if it's Del or Tab you'll have to type to enter BIOS...but maybe you already know all that stuff!)
A few months before my problem with the audio card, I got stuck in the init page the same way, and muse told me to check time and date. That's what I did and apparently it was the solution because my receptor went back to life when I restarted it...
hope you'll fix your problem !
JL

Post

Okay, I'll see if I have the adaptor so that I can attach one of my monitors (for viewing) to the back of my Receptor...
I do have a mouse and keyboard for the unit.
I don't understand how I'll be able to access any of the systems, if I couldn't do it via Ethernet and my Mac...
But I'll give it a try a little later.

Thanks for your suggestions.
JV

Post

I was in a state where it stayed on the initializing screen..i assumed that it was locked on this screen, but actually other stuff was actually happening in the background (which is not obvious from the muse screen)....how long have you let it stay on the initializing screen? i was letting it stay there for 5 or 10 minutes before getting frustrated and turning it off. when i reported to muse, they told me to run a diagnostic and when i did (i connect to a vga monitor which has more info)i saw that while the muse screen said initializing...it was actually doing a disk check which is REALLY slow...at the end of all that, everything was fine and i never had the problem again. but it took at least a half an hour to reboot.

so i would say let it run for an hour or so and see what happens.
here is the info they forwarded to me. VERBOSE BOOT is what you should try. good luck


---------------------
Receptor will not initialize

Reason: Conflict with hardware.
Disconnect everything but the power cable.
Turn Receptor on.

Lost Bios:
Connect a VGA monitor and computer keyboard.

Shut off the power and attach a keyboard. With the power off, hold down the DELETE key on the keyboard and then turn the power on. This will enter the BIOS setup utility. You should see a password prompt come up. If it doesn't then the BIOS is scrambled for sure. If it does ask you for a password, then enter the password MUSE123.
First thing to do is to check the date. Depending on the vintage of your hardware, it is either displayed on the first page or you'll need to go to "Standard CMOS Features" by using the arrows to highlight the selection and then press return to call up that submenu.
The date should be today's date and the time should be set to PST. As I type this, the date and time on mine is Fri, Nov 24 2006, 12:23:10. It hasn't been reset for dailight savings time,and this is no big deal.
The next thing to check is that you need the system set to HALT ON.... No Errors. This is also usually in the Standard CMOS System settings. This has to be set to
Finally, you MUST SAVE THESE CHANGES, by using the arrows to navigate over to Save & Exit Setup. At that point, you select YES and hit return to save the changes.
Reboot the system and see if it comes up.

Verbose boot:
Press F12 and you'll get what is called a 'verbose boot' that gives the progress of the system as it boots up.
If you see any errors about the hard drive contact Muse Research Support. support@museresearh.com

Lose Connection:
Disconnect Receptor from power any power source!
Remove the Receptor lid.
Press down on all connection to verify they are seated.
Place lid back on Receptor and try to power up again.

Post

Thanks.
I did leave it for 30 minutes, a couple of times.

To be perfectly honest, if what you've described is true, and it happens randomly, we all should have been made aware of this.

To me, it's BS that it should go into a 'diagnostic', randomly, and not indicate so.
I was at an important rehearsal, and what if I was on stage or TV?

I've sent my unit back for both servicing and an upgrade.
JV

Post

I had the same problem on my first gig last night .. at least it was finished at the start of the last set (and helped myself with a laptop running cubase and B 4 for my organ sounds). I was lucky that I brought a motif with me and used the internal sounds also, but I can't describe the smile on the singers face in the last set with the beautifull receptor sounds. Ivory/Fm7/Atmosphere layers are the bomb!

Does anybody know how to disable these random file checks?
I'm starting to get a love/hate relationship with my receptor this way.

Post

The log file says the following forcing 1,5 hours!

Jul 12 02:23:27 Receptor-314706 fsck: /dev/hda4
Jul 12 02:23:27 Receptor-314706 fsck: has been mounted 21 times without being checked, check forced.
Jul 12 02:23:28 Receptor-314706 fsck: /dev/hda4: |
Jul 12 02:25:08 Receptor-314706 last message repeated 69 times
Jul 12 03:56:36 Receptor-314706 fsck: /dev/hda4: 102692/90865664 files (1.5% non-contiguous), 56368588/181703182 blocks
Jul 12 03:56:37 Receptor-314706 rc.sysinit: Checking filesystems succeeded
Jul 12 03:56:37 Receptor-314706 rc.sysinit: Mounting local filesystems: succeeded

Locked

Return to “Muse Research and Development”