>>> mainbus0 at root: Unknown IP35 type 0 >> >> Wow. I would not have expected this. Can you send the output of `hinv >> -mvvv' of this machine at the PROM `>>>' prompt? I would have expected >> Origin 3000 to report themselves as Origin 300. Oh well. >> > here it goes: > >> hinv -mvvv > location: /hw/rack/001/bay/33 > Part:030-1604-004;Name:IP35;Serial:LMT028;Revision:-B;Group:ff;Capability:ffffffff;Variety:ff;Laser:000000004df7ef90; > > location: /hw/rack/001/bay/33 > Part:030-1557-007;Name:IBRICK;Serial:LMZ317;Revision:-A;Group:ff;Capability:ffffffff;Variety:ff;Laser:000000004dfc441b;
Ah, of course. Your system is built of a C-Brick connected to an I-Brick, so it reports itself as a regular C-Brick. >>> iec0 at ioc0: 128KB SSRAM, address ff:ff:ff:ff:ff:ff >> >> This is bad. On these systems, the Ethernet address is obtained by >> querying the brick L1 controller for the proper IA record. Either the >> query failed or the Ethernet address is stored elsewhere. Can you send >> > This is not too bad. The ethernet from the L1 controller and the OpenBSD > system differ, but I was actually able to install OpenBSD on a USB drive. > After reboot I tried to boot from it, but then it went into ddb. > The L1 MAC Address is: 08:00:69:11:ca:be > The MAC Address OpenBSD then used for dhcp was: fe:e1:ba:d0:b7:1f This is normal - sort of. When the Ethernet address can not be obtained, the kernel uses a random address starting with fe:e1:ba:d (to be pronounced `feel bad'). Unfortunately it will change on every boot. Can you elaborate on ``it went into ddb''? This is bad, the kernel should have asked for its root device and followed with the usual multiuser boot. >> the output of `eeprom' at the `L1>' prompt? (you will probably need to >> hit ^T or ^D on the L1 serial port to get such a prompt) >> > Here is the output: [...] Indeed, the Ethernet address is not stored on your C-Brick eeprom, but on the I-Brick eeprom. I have changed this code to query the I-Brick for the Ethernet address when running on a C-Brick, would you mind testing this kernel? > AARGH!!! I found out the misery of the hard drives. I actually have two 18 > GB 10k RPM FC hard drives in the box. But the Fibre Channel Bulkhead Card, > which should be normally in the i-brick is missing. I just figured out > yesterday. Unfortunately I bougth the box about 1 and a half year ago via > e-bay. I already sent a mail to those people yesterday asking whether they > may still have one around. I don't have much hope, but who knows... > So right now I am looking for such a thing, but guess I can plug in any > SCSI card and plug a SCSI disk to it? Yes, but there are two things to consider: first, the I-Brick probably only accepts 3.3V PCI cards, and second, only QLogic boards will get recognized by the PROM (i.e. you won't be able to boot from a non-QLogic board). > Will it also work when I try to attach a PCI graphics card, and a USB > keyboard into the i-brick and use the cluster as a desktop? ;) Not yet. PCI graphics will neither get initialized by the PROM, nor by OpenBSD (to be fair, some ATI cards may get recognized and initialized by the PROM, turning your machine from an Origin into an Onyx, but I am not sure about this). Miod
