Bebox Not working, need help

Hello i’m new on Bebox,
i love this machine, but mine is not booting. When i turn the Bebox on both LED stripes of the processors are lightening up and stay like this. Nothing else happend.


Board Revision is ASSY 830 0000 - 06

I am grateful for any help


hot damn a BeBox. These are rare and go for a LOT of money now-a-days :slight_smile:

Most likely your hard drive died. Spinning magnetic media likes to do that.
I think the BeBox used an IDE hard disk. I’d start there and test the disk to see if it still works.

If you’re looking to modernize, something like this might be “good enough”

Other things that could fail from age would be capacitors (unsolder, and replace with the same value), memory modules getting unseated, etc.

You should post more pictures :nerd_face:


Thank you for the fast answer. I checked the Ram (changed with working one from another computer 72Pin Edo Ram), at least there must be a boot screen with the Logo “be”, but there is nothing. Only both LED Stripes lightening up and staying like in the image. Could it be possible, that the boot Rom is faulty?

IMG_8512 2

Even without a Harddrive there must be something on the Screen, i also changed the GPU with another compatible PCI GPU from the compatibility list. But no reaction. The capacitors look at the first sight okey, but i can try to change them. Best regards

The BeBox has both SCSI and IDE. So it could be either. But that is not it. This wouldn’t stop the BeBox booting. If it was the hard drive, you would see the Be Boot logo, but it would just sit there.

I would check the RAM. The firstthing a BeBox does when it turns on is POST. The POST involves it testing the RAM, and the Blinken lights light up solid from bottom to top, left then right, when the test is happening for EVERY stick. If you are getting solid light, I suspect the POST is failing. This is possibly a bad RAM stick, but if you see it doing the tests, count how many times it does it before it stops, and that stick will possibly be bad.

I mean, the other option is that given the age of the computer, something electrical had died. I would check the capacitors.

1 Like

Yeah, that sounds possible. Did you update the ROM recently?

There are Boot rom update floppy images kicking around on the internet. I think there might be a floppy image on the BeOS R5 CD image too.

So - it feels like RAM or something. You could try this:

  • remove the RAM
  • remove/disconnect the various daughter cards
  • clean all contacts with isopropyl alcohol or similar
  • if you know electronics, try testing components
  • put it all back together
  • pray to your preferred god figure.

If it is the boot Rom, it is an issue. The Boot Rom is not just a Rom, there are two parts. It has a “nub” and the main updatable image. You’d need to find a way to program a new chip with the nub part at the very least (I don’t think the boot ROM Update disks ever touch that part.)

I have been playing a lot with old Mac hardware recently, and old hardware is tricky. It an look bad, but just have a dirty contact. I thought I killed my 9500 a number of times but stripping it and putting it back together… it is just problematic sometimes.

I don’t own a BeBox anymore, so I’m sorry i can’t help more. You might get info fromt he old Be Newsletters about troubleshooting this type of issue. Also, maybe reach out to someone like Joseph Palmer. Who knows…

1 Like

Hello, no. I got the bebox from a friend, we traded two computers. he told me that the bebox is not working. I’m now trying to fix it.

I found this on a bebox website:

When you turn on the BeBox, CPU 0 starts running in the nub, while CPU 1 is held in reset. The >nub’s job is to locate, size, test, and configure the memory, check the floppy drive for a special Boot >ROM Upgrader disk, and then pass control to the main part of the boot ROM.

I did a dump of the AM29F040. And i ordered a New old Stock over ebay. So i can write a new BootRom, i know It’s partitioned into sections, including a small “nub” and a main part. If someone can provide me a Rom Dump File would be awesome. Otherwise it is very difficult to create a working one.


The RAM has to be installed by pairs unless, did you only replace one stick?
Is the floppy drive plugged in (correctly)?

Look here for some of the BeDevTalk mailing lists and archives, one the posters may have had the same problem:

I started browsing through both the newsgroups and mailing list, found that specific problems multiple times:

one person had this issue intermittently, he sometimes managed to boot it by gently pushing on one of the side panels, or turning it off and on again a decent number of times, also sometimes nothing was working anyway.

A few people had problems with some keyboards causing the system not to start up as well.

A thread in May 1996 had someone (the BeOS bible author Chris H.) with the exact same problem as you, both LED ramps being lit up all the time and nothing else happening) being due to the power supply being set to the wrong input voltage by default on its brand new BeBox, Be tech support eventually found out that it would cause the problem after some further testing later in that mailing list thread.

1 Like

Not sure if it helps but the Boot ROMs are here, if someone has a handy C program to dump the ROM in its entirety including the nub I can get it off my BeBox I expect. There is also what looks like the Nub + ROM here as well. If you have the dumps from your programmer it should be possible to confirm if indeed it has a ROM on there from the images linked, typically any recently used BeBox would have R3.2 or 4.5 (or 5?) ROMs loaded, would take a bit of comparing to figure out which ROM it is. Note if it’s an older BeBox it may not support the latest ROMs but looks like it is one of the newer ones.

From memory the R3.2’s (and below) simply used a dd’ed floppy to load and write, the 4.5/5 used an app + image to write the updated ROM from a working BeOS 4.5/5 install as it was a maintenance release ROM effectively. So the BeBox by default will always check the floppy drive with an access on boot to see if there’s a ROM to load from floppy.

Having said that probably best to (carefully) remove all the expansion cards & RAM (and test it elsewhere), and reset the I/O board, the Number 9 Trio64 cards should still work for video (or Matrox Millennium II) as not just any Trio64 would work it seems (my friend had one and it didn’t, fortunately I had the official one and it worked which he’s borrowing). Also keep in mind to reduce board flex as they’re getting fragile.

I don’t recommend randomly removing the caps without confirming with an ESR meter unless you can definitely confirm they’re faulty, it’s probably easier to start targeting the power supply to check it’s outputting the correct voltages/current as it’s easier to test without needing to have it plugged into your BeBox. If the caps have gone bad in the power supply that could be locking the BeBox up, you should be able to smell if they have leaked (or check with ESR meter once discharged).

If you scroll to the end of the rom image with a hrx editor, see if the put the date with the be inc copyright in ascii text, it’s really common for firmwarevof that vintage