Buddha not booting from DOM

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.
  • Hello,


    I have recently acquired an Amiga 3000D from Ebay, All the original boxes etc so it was a good deal. Although the unit functions without any problems, the battery had leaked. I have cleaned it with vinegar and demonised water and all the tracks are thankfully in tact.


    There is an Opalvision video card installed and after adding the Buddha, it is not booting up from the DOM, it is not showing on the boot menu (two mouse buttons held down). There is a post with a similar issue with another user that had a leak.


    Buddha IDE not booting...?


    I have taken a picture from system configuration and system information and board is detected, I have a 500gb IDE drive attached with not partitions.


    Should the DOM boot be listed along with the floppy drive and SCSI hard drive installed?


    If they fault is with my autoconfig, I can send it for repair, in the meantime, can I download the software from the link bellow and install it manually?


    http://wiki.icomp.de/wiki/File:BuddhaInstallUpdate1.2.lha


    If the problem is with my autoconfig hardware, how come it appears in detection? What chips are involved with autoconfig as all the traces/tracks are good?


    Many thanks


    Paul

  • Autoconfig appears to work in this case, as the unit is shown. However, no other autoconfig device is shown, but you described that some other card is in the system, which should show up in the autoconfig list.


    Just to make sure that the IDE drive is not at fault - does the computer boot from the DOM if you have only that connected to the Buddha?


    The other case you've linked to (also with a leaked battery) does not compare, as that system is an A2000.

  • Hello,


    the extra card is an OpalVison video card and only slots in the bus at on the daughter board near the back. It does not plug into the Zorro slots which is near the front of the case.


    I have tried it without the Opalvision card and in each slot. It does not boot or appear in the boot menu when hold two mouse buttons.


    if the Dom is faulty, can I manually install or download the Dom contents from where?


    thank you

  • can I manually install

    Yes - the installation procedure as originally described by Commodore will work. You will of course need the installation floppy disks.



    or download the Dom contents from where?

    I'm sorry, the DOM contains licensed material that we're not allowed to put online. If the DOM is really faulty, we can test that here and copy the contents on it again. However, this only happened once in over two years, and the reason for that support case was most likely user error. We do test each Buddha with the very DOM that it's shipped with, and it will only get the warranty ID after it has successfully booted from the installation DOM.


    What ROMs does your A3000 have? Is it one of the rare 16MHz Kickstart-loading types, or is it the 25MHz type that came with 2.0 ROMs?

  • It is kickstart 2.0, 1991 model, 25Mhz. It boots from SCSI and says Amiga release 2, Kickstart 37.175 Workbench 37.17.


    I think it is unlikely that the Dom is faulty so not sure how to proceed? It seems odd that it’s detected but does not show up in HDtoolbox or boots.


    I have some 3.x (not 3.1) ROMs in the next couple of weeks, maybe that will help? I also have some install disks to do a reinstall of workbench.


    as the kernel does not require drivers, is there any diagnostic software an try, I understand the software is licensed, but maybe there is some way you can arrange some other method to install the soft way that is not DOM based? Any media like floppy etc to jump start it?


    if the tools reported it not there, at least it would explain the issue. The only place that would cause this behaviour would be the kickstart, so with any luck, new ROMs might resolve it.


    paul

  • It seems odd that it’s detected but does not show up in HDtoolbox or boots.

    The DOM is configured with a very low boot priority. It will only boot if there is no other already-installed partition in the system. Since you have a working 2.0 installation, the DOM will not automatically bootk.


    You should, however, see the DOM on the WB screen and in the device list of Sysinfo.


    I have some 3.x (not 3.1) ROMs in the next couple of weeks, maybe that will help?

    Those are unofficial ROMs by Cloanto -I recommend not to use them. My personal recommendatoin is to use the official 3.1.4 ROMs from Hyperion. Please understand that we will not supply any support if you are using the 3.x ROMs.


    as the kernel does not require drivers, is there any diagnostic software an try,

    Sysinfo is a good tool to find out if the ROM has been launched. Check for buddhascsi.device in the device list.

  • Okay, I will order the hyperion, I had not completed the 3.x ROMs.


    I have removed all other boot devices from the a3000, I simply get the no boot device screen.


    I can not see a mounted volume in wb nor sysi fo. So I will get the new ROMs and report back. Am I able to rerun the product if swapping the roms out does not succeed?


    I really don’t want to, but I am stuck here with what seems to be a device that can detect the hardware is present, but having no means of actually installing the device and prepping a device


    Any other ideas on how to progress this? If the kickstart is responsible for the device and no need to install device drivers into the kernel (as I have read), then what other applications are required to initialise the IDE interface in Amiga DOS?


    mare there any other utilities available to get the Buddha card playing ball with Workbench or Amiga dos? Would downloading the flash lha from your website and attempting to flash the board help?


    I did read that you need to hold down the left mouse button while you powering up is required to remove the flash write flash text?


    it would be great if I could just see the board scanned by HDtoolbox (it shows up as scsi, right?). At least then if my current ide hard disk would not work, I could go on the hunt for another!


    any other ideas would be much appreciated!
    Paul

  • Am I able to rerun the product if swapping the roms out does not succeed?

    Sure - that's the natural thing to do if you can't get it to work :-)


    are there any other utilities available to get the Buddha card playing ball with Workbench or Amiga dos?

    Like I wrote: The standard procedure(s) for installing an OS from floppies to a harddrive will always work with the Buddha.


    Would downloading the flash lha from your website and attempting to flash the board help?

    I doubt it. The controller is seen in early startup, so the basic autoconfig works and is very likely to launch the driver. I asked you to verify with Sysinfo before, but you didn't follow that suggestion yet.

    any other ideas would be much appreciated!

    Please don't deviate too much by trying every possible solution by only 30% - this will never get you to the end. Please verify with Sysinfo what version of the driver is loaded (if any). Just check the list of devices on the main screen.

  • Okay, device list does not show anything under “SYSTEM SOFTWARE INSTALLED” other than SCSI, which I assume is the onboard controller.


    Using DiagROM 1.2, other tests, Autoconfig it finds the Buddha card. Link to system free pool:NO, Autoboot: YES, Linked to next board:YES, Extended size: NO, Size:64kb, Zero II I/O detected and assigned to: $00E90000 - $00EA0000. Assign board? Yes (LMB) No (RMB) (If possible) or ESC EXIT.


    so, it would seem all is well, guess I will have to wait for new ROMs...

  • Okay, device list does not show anything under “SYSTEM SOFTWARE INSTALLED” other than SCSI, which I assume is the onboard controller.

    Depending on the flash version (which may either be the old Elaborate Bytes ROM or the newer one which got an update last year) this may be OK. The Elaborate Bytes ROM will always add devices to the list (for example buddha_atapi.device), but the newer ROM will not waste any memory by adding the device if it did not find any IDE device on the controller. So this may mean that the new software is in, but it does not find any IDE drive.


    Please let me know the warranty ID of the controller or the order ID in our shop system, so I can look up when the controller has been prepared here, and if there are any special notes in the database.

  • OK, that's so new that there's no doubt that you have the latest CPLD, latest flash and everything should work as advertised. If an IDE device is not found (and thus the buddhascsi.device driver is not installed), there's a few possibilities: Either the IDE devices you're trying are not compatible (or not powered - check the jumper for DOM power), or the controller suffered damage.


    Should the damage come from an accidental reverse-installation, then the "resistor of shame" (which is labelled R2) is blown. This protects more expensive components from being blown. The resistor can be replaced by any technician in the world without the need to send the card back to Germany.

  • I have tried with the new ROMs, as advised. The card is detected in the boot menu expansion board diagnostic. I have an ATA 250Gb IDE connected, no boot. The drive does work although no partition.


    I have an Amiga 2000 arrive today that has a Buddha card in, I will try it out on that over the weekend.


    just for clarity, would the Dom still boot if no hard drive was attached?


    I have defo not plugged the card in “upside down”. Started my first job at 18 hack sawing XT cases to fit 386 25SX boards in and adding sound blaster cards to ISA while still setting IRQ & DMA channels by jumper before the days of plug n play.


    will let you know the outcome.


    thanks for your persistence!

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.