Announcement

Collapse
No announcement yet.

R600/r700 kms - no go

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • R600/r700 kms - no go

    Ubuntu 9.04 system, hd4850

    compiled/tried two kernels - latest from drm-next(few days old git) and 2.6.32-rc3-git3
    xf86-video-ati from git

    booting with argument - radeon.modeset=1 results in black screen as soon as X starts, system still working.

    if i try to switch to console (ctrl-alt-f1) system seems to freeze (no reaction on caps lock pressing).

    tried also with and without vesafb module builtin(with option vga=838)

    no go at all.

    what can I try ?

    also tried to boot with single option then modprobe radeon, seems it worked once, for console

    from dmesg, with drm-next kernel
    [ 35.738973] [drm] Initialized drm 1.1.0 20060810
    [ 35.792593] [drm] radeon kernel modesetting enabled.
    [ 35.792637] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 35.792640] radeon 0000:01:00.0: setting latency timer to 64
    [ 35.794100] [drm] radeon: Initializing kernel modesetting.
    [ 35.794120] [drm] register mmio base: 0xE5000000
    [ 35.794121] [drm] register mmio size: 65536
    [ 35.794177] ATOM BIOS: Wekiva
    [ 35.794182] [drm] Clocks initialized !
    [ 35.794192] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
    [ 35.794194] [drm] Detected VRAM RAM=256M, BAR=256M
    [ 35.794195] [drm] RAM width 128bits DDR
    [ 35.794256] [TTM] Zone kernel: Available graphics memory: 4090722 kiB.
    [ 35.794257] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    [ 35.794268] [drm] radeon: 256M of VRAM memory ready
    [ 35.794269] [drm] radeon: 512M of GTT memory ready.
    [ 35.794295] [drm] Loading RV770 CP Microcode
    [ 35.794440] platform radeon_cp.0: firmware: requesting radeon/RV770_pfp.bin
    [ 35.840675] platform radeon_cp.0: firmware: requesting radeon/RV770_me.bin
    [ 35.863403] [drm] GART: num cpu pages 131072, num gpu pages 131072
    [ 35.895784] [drm] ring test succeeded in 1 usecs
    [ 35.895851] [drm] radeon: ib pool ready.
    [ 35.895899] [drm] ib test succeeded in 0 usecs
    [ 35.895995] [drm] Radeon Display Connectors
    [ 35.895996] [drm] Connector 0:
    [ 35.895997] [drm] DVI-I
    [ 35.895998] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
    [ 35.895999] [drm] Encoders:
    [ 35.896005] [drm] DFP1: INTERNAL_UNIPHY
    [ 35.896006] [drm] CRT2: INTERNAL_KLDSCP_DAC2
    [ 35.896007] [drm] Connector 1:
    [ 35.896007] [drm] DIN
    [ 35.896008] [drm] Encoders:
    [ 35.896009] [drm] TV1: INTERNAL_KLDSCP_DAC2
    [ 35.896010] [drm] Connector 2:
    [ 35.896011] [drm] DVI-I
    [ 35.896012] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c
    [ 35.896013] [drm] Encoders:
    [ 35.896014] [drm] CRT1: INTERNAL_KLDSCP_DAC1
    [ 35.896015] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
    [ 36.035774] [drm] fb mappable at 0xD0141000
    [ 36.035775] [drm] vram apper at 0xD0000000
    [ 36.035776] [drm] size 7257600
    [ 36.035777] [drm] fb depth is 24
    [ 36.035778] [drm] pitch is 6912
    [ 36.035815] fb0: radeondrmfb frame buffer device
    [ 36.035817] registered panic notifier
    [ 36.035820] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
    Last edited by netkas; 11 October 2009, 05:06 PM.

  • #2
    Are your libdrm and mesa also from git?

    Are you sure you disabled all framebuffer devices?

    Comment


    • #3
      Originally posted by pingufunkybeat View Post
      Are your libdrm and mesa also from git?

      Are you sure you disabled all framebuffer devices?
      yes, those from drm..

      disabled all fb devices ?

      vesafb and etc ? nop, it works if i boot without radeon.modeset=1, then modprobe radeon modeset=1

      I have a screen this way, but X11 kills it when it starts

      and no matter was vesafb loaded or not

      Ahh, no I see, ./configure for ati driver says kms : no

      so, Updated xorg server to 1.6.3 (xf86-video-ati configure output needs to be more imformative)

      recompiled ati driver and all works fine, except that i have to manualy make - modprobe radeon modeset=1 , otherwise black screen when X starts

      if I add radeom modeset=1 to /etc/modules, then i get half of screen visible, and another half is black, system freeze.

      without passing vga=838 options to kernel - freeze as soon as radeon modeset=1 loaded
      Last edited by netkas; 11 October 2009, 06:25 PM.

      Comment


      • #4
        you need to load fbcon to get console once the drm loads.

        Comment


        • #5
          Originally posted by agd5f View Post
          you need to load fbcon to get console once the drm loads.
          console is working when drm loaded, but sometimes (rarely) it gets me black screen.

          When booted with radeon.modeset=1 (or radeon modeset=1 added to /etc/modules, or another way to load module automaticaly) - i get black screen when X starts up

          Only way to get it working - boot with option - single, then modprobe radeon modeset=1, then resume booting.

          Comment


          • #6
            I'm having the same problem. I use Ubuntu 9.10 with xorg-edgers and kernel 2.6.32-rc6 from Kernel PPA, with a Radeon HD2400.

            When using KMS (through "option radeon modeset=1" in /etc/modules), as soon as X starts, I get a blank screen and the system freezes.

            Comment


            • #7
              tried 2.6.32-rc7.

              All the same, even worse, with rc5 if I run xinit glxgears -- /usr/bin/Xorg -ac -config /etc/X11/xorg.conf , with previously loaded radeon (modeset=1) - it always was woeking.

              Now with rc7, half of time I'm getting system freeze with lower half of screen showing some pic with colored snow.

              Comment


              • #8
                you might try Dave's drm-radeon-testing branch.

                Comment


                • #9
                  agd5f (or some other dev),

                  do you already know if you will be able to enable KMS by default in Linux 2.6.33 or 2.6.34?

                  I am asking because Ubuntu Lucid will be using Linux 2.6.33.

                  Comment


                  • #10
                    KMS is already enabled by default in Fedora 12, and it looks like the bulk of the KMS fixes are making it into 2.6.32, so it *seems* likely that 2.6.33 would be suitable.
                    Test signature

                    Comment

                    Working...
                    X