> Please find attached two sets of output from dmesg running on an Onyx 4
> First attempt to boot the machine resulted in it hanging while scanning 
> the scsi bus on isp0 (Which I believe is the PCI SCSI card). Using the 
> kernel config prompt to disable isp* allowed the machine to boot and 
> install to a USB stick. I haven't worked out what to put in the PROM to 
> have the kernel use sd0 for root automatically, so I'm also having to 
> input that at boot time.

Nice machine you've got there! Is this an 8-pipe model?

There have been a few fixes in the PCI setup code late march, which
should fix your isp(4) issue. Could you try a more recent snapshot than
march 24? Preferrably binaries less than one week old.

Unfortunately, there is no way for the kernel to figure out your root
device is the USB stick, if the PROM doesn't support booting from it
(and I don't think any SGI PROM can do this). But then if indeed the isp
driver works for you with a newer kernel, you will be able to use any
SCSI disk, and boot from it.

> If anyone would like remote access to the machine to take a look at the 
> hardware, then that can be arranged. Serial consoles are fine, SSH is 
> proving difficult at the moment (pty allocation request failed on 
> channel 0, if anyone knows how to fix that I'd be grateful!)

This could help improving hardware support for your particular machine,
however if you don't mind testing kernels you hopefully won't need the
hassle to set up remote serial console.

In the meantime, I would like to get a dmesg from a recent GENERIC-IP27
kernel, as well as the output of `hinv -v' at the PROM chevrom prompt
(or from an IRIX prompt if you still have IRIX installed on the system),
and the output of `pcidump -x' from the OpenBSD system running
GENERIC-IP27).

> vendor "SGI", unknown product 0x100c (class undefined unknown subclass 0x00, 
> rev 0x1a) at pci0 dev 1 function 0 not configured

Do you have an idea what this card is? I can't find any information
about it. This might be an onboard device though.

Miod

Reply via email to