My unit was working fine. I then installed a few instruments and effects from the free section, added the TC banks, and the file "fix-perm-samples-1-1.rpm" which I thought would enable me to delete some stuff from the samples folder that was left by the previous owner. Everything seems to install OK via the remote utility. I switched the unit off, again, no probs. However, the first time I switched it on again, I got the message "initializing system" with the hourglass moving but nothing else happens (it's been over one hour now). I tried plugging a monitor, keyboard and mouse to see if I could see anything on the screen regarding the initial boot, but the screen stays blank.
Any idea as to what I could do to revive the unit ?
Thanks.
Receptor stuck on "initializing system"
-
- KVRian
- 571 posts since 14 Oct, 2004 from UK
-
- KVRian
- 1116 posts since 22 Apr, 2005 from Nashville, TN USA
This has happened to me a few times. Seems like unplugging the power cord may have some effect. Of course you probably know you can hold the power button down and it will power off (hard power off). Try that, and then unplug the power cord, and then start it up.Kermit Jagger wrote:My unit was working fine. I then installed a few instruments and effects from the free section, added the TC banks, and the file "fix-perm-samples-1-1.rpm" which I thought would enable me to delete some stuff from the samples folder that was left by the previous owner. Everything seems to install OK via the remote utility. I switched the unit off, again, no probs. However, the first time I switched it on again, I got the message "initializing system" with the hourglass moving but nothing else happens (it's been over one hour now). I tried plugging a monitor, keyboard and mouse to see if I could see anything on the screen regarding the initial boot, but the screen stays blank.
Any idea as to what I could do to revive the unit ?
Thanks.
Yeah, it's a scary thing. Happened to me the first couple of days I had my unit. I almost sent it back. Also when I called them, they had me open the unit up and make sure the cable connectors, like to the hard drive especially, were seated well. They were.
I never really figured out what caused it initially. The other day it did this to me and the hard-power off alone solved it that time.
good luck!
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Thanks for the suggestion. I tried that, unplugging the RJ45 cable as well, but no dice. I'll try leaving it unplugged for a while and see whether it changes anything. I also had a look inside but the HD cable seems properly seated.
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Update:
I used another RAM module and plugged another drive, if only to see whether I could see the BIOS when starting the unit. Nothing on screen, no beep, nada...
Sounds like the CPU is dead or the motherboard has a problem. And yet, it<s one of those that was changed not to long ago due to supplier problems.
Has anyone experienced a dead CPU with the Receptor ?
I used another RAM module and plugged another drive, if only to see whether I could see the BIOS when starting the unit. Nothing on screen, no beep, nada...
Sounds like the CPU is dead or the motherboard has a problem. And yet, it<s one of those that was changed not to long ago due to supplier problems.
Has anyone experienced a dead CPU with the Receptor ?
-
- KVRer
- 11 posts since 6 Apr, 2005
This happened to me a while ago, and the solution (for me, at least) turned out to be resetting the system date in the BIOS.
To do this, you have to connect a VGA monitor and PS2 keyboard (not USB) directly to the unit. I don't think a mouse is necessary. Boot up holding down the Delete on the keyboard, and you should see the BIOS screen come up on the monitor. I don't have my system set up this way right now, so I don't recall the specifics, but you have to navigate to the system settings screen in the BIOS, where you'll find the system date setting. If the date is incorrect, set it to the current date, then reboot the system using the keyboard commands, and it should start normally, with all your configurations intact.
If the date is already correct, then you have some other problem, and this procedure won't help. But give it a try anyway.
To do this, you have to connect a VGA monitor and PS2 keyboard (not USB) directly to the unit. I don't think a mouse is necessary. Boot up holding down the Delete on the keyboard, and you should see the BIOS screen come up on the monitor. I don't have my system set up this way right now, so I don't recall the specifics, but you have to navigate to the system settings screen in the BIOS, where you'll find the system date setting. If the date is incorrect, set it to the current date, then reboot the system using the keyboard commands, and it should start normally, with all your configurations intact.
If the date is already correct, then you have some other problem, and this procedure won't help. But give it a try anyway.
Richard Lainhart
http://www.otownmedia.com
http://www.otownmedia.com
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Thanks Richard.
My problem is that I don't see a boot screen. I've tried with a 17" CRT and a 15" TFT but the screen stays blank, whether I press the delete key or not. The only thing is that the HD spins, the lights on the keyboard flash briefly but then, nothing else happens.
My problem is that I don't see a boot screen. I've tried with a 17" CRT and a 15" TFT but the screen stays blank, whether I press the delete key or not. The only thing is that the HD spins, the lights on the keyboard flash briefly but then, nothing else happens.
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
I've done that at the same time, but whilst waiting for an answer, it didn't hurt asking others if they had experienced this and what they'd done about it.
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Update, after failing to restart it for a while, in the end it came back to life and has been working fine since. No idea as to what caused the initial problem, it's like the motherboard didn't shut properly and had difficulty restarting.
Still, Muse were very helpful in trying to fix the problem, which is comforting.
Still, Muse were very helpful in trying to fix the problem, which is comforting.
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Final twist in the tale.
Today I had the same problem again. However, I've found the source, or at least, what to do about it.
Basically, when the Receptor is not booting, not displaying anything on the monitor, unplug the black & white power cable from the motherboard (left side) and replug it. This did the trick for me and enabled me to resume booting properly.
Thus, my initial problem seems to be a bad power cable (from power button to motherboard) or perhaps a problem with the jumper at the end of the cable (bad contact with the mobo pins).
Today I had the same problem again. However, I've found the source, or at least, what to do about it.
Basically, when the Receptor is not booting, not displaying anything on the monitor, unplug the black & white power cable from the motherboard (left side) and replug it. This did the trick for me and enabled me to resume booting properly.
Thus, my initial problem seems to be a bad power cable (from power button to motherboard) or perhaps a problem with the jumper at the end of the cable (bad contact with the mobo pins).
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
I thought I had the correct answer, but it turned out that it was a wrong setting in the BIOS. Problem is, as it is password-protected, I never thought about that, thinking the settings were correct since set at factory.
Anyway, if one day your Receptor gets stuck and you cannot see any boot on a monitor, it could be that the BIOS parameter "Halt On" is set to "All" like mine was. Contact Muse to get the password and change "Halt On" to "No error".
You could also remove the battery and reset the BIOS, but that means you know how to set the various parameters. If you don't, wait until Muse tell you what to do and how.
Anyway, if one day your Receptor gets stuck and you cannot see any boot on a monitor, it could be that the BIOS parameter "Halt On" is set to "All" like mine was. Contact Muse to get the password and change "Halt On" to "No error".
You could also remove the battery and reset the BIOS, but that means you know how to set the various parameters. If you don't, wait until Muse tell you what to do and how.