Re: Graphics initialization issue(?)

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Fri, Jul 21, 2017 at 15:02:09 +0200, Havard Eidnes wrote:

> once it hit the graphics driver, the screen went black (but not
> "no signal").
[...]
> This symptom appears to be different from the "doesn't init
> graphics when doing an auto-boot" where I have a suggestion for
> some OFW settings which I've not tried out yet.
[...]
> radeonfb0 at pci0 dev 16 function 0found EDID property...
> : ATI Technologies Radeon 9200 5962 (rev. 0x01)
> radeonfb0: Video BIOS not present
> radeonfb0: No video BIOS, using default clocks
> radeonfb0: refclk = 27.000 MHz, refdiv = 12 minpll = 125000, maxpll = 400000
> radeonfb0: 64 MB aperture at 0x98000000, 64 KB registers at 0x90000000
> radeonfb0: display 0: initial virtual resolution 1600x1200 at 8 bpp
> radeonfb0: using 32 MB per display
> radeonfb0: port 0: physical 1600x1200 60Hz
> radeonfb0: port 1: physical 1600x1200 60Hz


Have you seen my reply to you previous mail?

| Another problem was the radeon driver.  I couldn't get it to work with
| the DVI output, so I had to disable it in the kernel config so that
| genfb can take over.  IIRC, this is the problem only with DVI, the VGA
| is ok.  But if you are not sure which display you are gonna use, it
| might make sense to proactively
| 
|   no radeonfb*    at pci?
| 
| Or we should get macallan a mac mini, not pun intended :)

-uwe