Paul,

    I hope your latest output-device in the email was a typo:

    output-device    pci2@D ...

It should be:

    output-device    pci2/@D ...

You need the slash. Also in order to be usable from OF it has to have an OF
ROM. It is a MAC video card, right? Do something like:

    " pci1" select-dev ls unselect-dev
    " pci2" select-dev ls unselect-dev

to figure out which bus your video card is on. Then use the address on the bus
(the "D" above) to specify the device.

                    kevin

paul beard wrote:

> On Saturday 15 December 2001 10:52 am, Kevin Diggs opined:
> > need something like:
> >
> >     pcix/@D
> >
> >     where x is the pci bus that your card is on (a 0 or a 1). There should
> > be two on the 9500. It is an alias to /bandit@whereever (I think the OF
> > command to list aliases is devalias).
>
> Aha.
>
> 0 > devalias
> vci0                /chaos@F0000000
> pci1                /bandit@F2000000
> pci2                /bandit@F4000000
> fd                  /bandit/gc/swim3
> kbd                 /bandit/gc/via-cuda/adb/keyboard
> ttya                /bandit/gc/escc/ch-a
> ttyb                /bandit/gc/escc/ch-b
> enet                /bandit/gc/mace
> scsi                /bandit/gc/53c94
> scsi-int            /bandit/gc/mesh
>
> well, pci2 wasn't it.
> output-device       pci2@D              ttya
>
> nor pci1. pci0, maybe? why zero-based number in some places and one-based in
> others? Grr.
>
> it seems to me dmesg should have some clues on this as well: what would I
> look for there? any of this look promising?
>
> bandit1 at mainbus0
> pci1 at bandit1 bus 1
> pci1: i/o space, memory space enabled
> pchb1 at pci1 dev 11 function 0
> pchb1: Apple Computer Bandit Host-PCI Bridge (rev. 0x03)
> ofb0 at pci1 dev 13 function 0: cannot map framebuffer
>
> what's pchb1? Hmm . . .
> --
> Paul Beard
> 8040 27th Ave NE
> Seattle WA 98115
>
> How many hardware guys does it take to change a light bulb?
>
> "Well the diagnostics say it's fine buddy, so it's a software problem."