vesa and 2560x1440

[Michal Suchanek]

On 18 October 2014 08:26, basteon <basteon at gmail.com> wrote:
> On 10/18/14, basteon <basteon at gmail.com> wrote:
>> On 10/13/14, Michal Suchanek <hramrach at gmail.com> wrote:
>>> Hello,
>>>
>>> On 13 October 2014 11:37, basteon <basteon at gmail.com> wrote:
>>>> hello,
>>>> I use 2.3.3 vesa xorg driver.
>>>> But with radeon kernel driver I got black screen and nothing more.
>>>> Just after I make modprobe -av radeon
>>>> I use  GIGABYTE GA-E350N board with AMD Radeon HD 6310.
>>>
>>> Can you connect over SSH or serial console and collect the kernel
>>> messages after you insert the radeon module?
>>>
>>> The onboard 6310 card should work except it's hell slow. I used to run
>>> a system with one some years ago.
>>>
>>> What connection do you use to connect the display? Some connections
>>> may not be able to use full resolution. Can you try using fbset or
>>> xrandr to switch to lower resolution once the module is inserted?
>>>
>> [  453.506960] [drm] Loading PALM Microcode
>> [  453.518644] r600_cp: Failed to load firmware "radeon/PALM_pfp.bin"
>> [  453.518717] [drm:evergreen_startup] *ERROR* Failed to load firmware!

Yes, the graphics is not expected to work correctly without a firmware.

That's a severe defect of the Radeon driver since the firmware  is
apparently buggy and/or the interface is not well understood and it
fails miserably under some circumstances. It should however bring up a
card correctly when it is in VGA text mode which is what the BIOS sets
up on boot.

> And after I load the firmware, I got this.
> And anyway black screen.
> [  208.761365] [drm] Initialized drm 1.1.0 20060810
> [  208.858346] [drm] radeon defaulting to kernel modesetting.
> [  208.858352] [drm] radeon kernel modesetting enabled.
> [  208.858423] radeon 0000:00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [  208.858431] radeon 0000:00:01.0: setting latency timer to 64
> [  208.867813] [drm] initializing kernel modesetting (PALM 0x1002:0x9802).
> [  208.867907] [drm] register mmio base: 0xFE000000
> [  208.867910] [drm] register mmio size: 262144
> [  208.868214] ATOM BIOS: AMD
> [  208.868265] radeon 0000:00:01.0: VRAM: 384M 0x0000000000000000 -
> 0x0000000017FFFFFF (384M used)
> [  208.868271] radeon 0000:00:01.0: GTT: 512M 0x0000000018000000 -
> 0x0000000037FFFFFF
> [  208.868446] [drm] Detected VRAM RAM=384M, BAR=256M
> [  208.868453] [drm] RAM width 16bits DDR
> [  208.868865] [TTM] Zone  kernel: Available graphics memory: 820394 kiB.
> [  208.868876] [TTM] Initializing pool allocator.
> [  208.868938] [drm] radeon: 384M of VRAM memory ready
> [  208.868988] [drm] radeon: 512M of GTT memory ready.
> [  208.869047] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [  208.869054] [drm] Driver supports precise vblank timestamp query.
> [  208.869131] radeon 0000:00:01.0: irq 40 for MSI/MSI-X
> [  208.869145] radeon 0000:00:01.0: radeon: using MSI.
> [  208.869210] [drm] radeon: irq initialized.
> [  208.869220] [drm] GART: num cpu pages 131072, num gpu pages 131072
> [  208.873133] [drm] Loading PALM Microcode
> [  208.905519] radeon 0000:00:01.0: WB enabled
> [  208.922151] [drm] ring test succeeded in 1 usecs
> [  208.922326] [drm] radeon: ib pool ready.
> [  208.922445] [drm] ib test succeeded in 0 usecs
> [  208.953333] [drm] Radeon Display Connectors
> [  208.953339] [drm] Connector 0:
> [  208.953342] [drm]   HDMI-A
> [  208.953345] [drm]   HPD2
> [  208.953349] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448
> 0x644c 0x644c
> [  208.953353] [drm]   Encoders:
> [  208.953356] [drm]     DFP1: INTERNAL_UNIPHY
> [  208.953359] [drm] Connector 1:
> [  208.953362] [drm]   VGA
> [  208.953366] [drm]   DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0
> 0x64e4 0x64e4
> [  208.953369] [drm]   Encoders:
> [  208.953371] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
> [  209.009294] [drm] Internal thermal controller without fan control
> [  209.009542] [drm] radeon: power management initialized
> [  209.090148] [drm] fb mappable at 0xC0141000
> [  209.090152] [drm] vram apper at 0xC0000000
> [  209.090155] [drm] size 14745600
> [  209.090157] [drm] fb depth is 24
> [  209.090160] [drm]    pitch is 10240

This appears correct for a 2560 mode. The framebuffer should take up
about 15M so even with as little as 384M graphics memory even triple
buffering of the framebuffer should not pose a problem.

Did you try setting the resolution lower in case the transmitter you
are using cannot handle a mode this large?

Thanks

Michal