Announcement

Collapse
No announcement yet.

Debian Radeon X1600 KMS (MacBookPro2,1)

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

  • Debian Radeon X1600 KMS (MacBookPro2,1)

    Hi guys,

    I'm trying to get KMS working on Debian (unstable), but I can't get it past the first steps.

    I'm using the 'linux-image-2.6.32-trunk-amd64 (2.6.32-5)' kernel (which is based on 2.6.32.3), and as soon as I 'modprobe radeon modeset=1' the system hardlocks (LCD panel switches off).

    Package 'firmware-linux-nonfree' is installed.

    Any ideas anyone? Anyone experienced something similar?

    Thanks,
    Robin

  • #2
    Does it work any better with a newer kernel or drm-radeon-testing?
    http://git.kernel.org/?p=linux/kerne...radeon-testing

    Comment


    • #3
      KMS is working fine with my Macbook Pro1,1 X1600 running Debian unstable and custom kernel. Currrently I'm running 2.6.33-rc7 with modesetting compiled inline and enabled by default

      Firmware for R520 is built into kernel. There is no need for external firmware as is the case with R600.

      My kernel config:
      http://pastebin.com/m61a4d3cc

      Comment


      • #4
        Ah... my config will not work for you as Macbook Pro2,1 is Core2. I only have a lowly 32-bit machine. :-)

        Comment


        • #5
          Originally posted by amphigory View Post
          Ah... my config will not work for you as Macbook Pro2,1 is Core2. I only have a lowly 32-bit machine. :-)
          The important part is the kernel version.

          Comment


          • #6
            Originally posted by agd5f View Post
            The important part is the kernel version.
            I've had KMS working fine since 2.6.32 on my Macbook Pro. I wonder if X was running when robin1979 enabled KMS. I've always had KMS enabled prior to starting X. Also, is fb console inserted as well when enabling modesetting via module?

            Comment


            • #7
              Originally posted by amphigory View Post
              I've had KMS working fine since 2.6.32 on my Macbook Pro. I wonder if X was running when robin1979 enabled KMS. I've always had KMS enabled prior to starting X. Also, is fb console inserted as well when enabling modesetting via module?
              No, X wasn't running. I even removed X from the boot and did a fresh boot so to make sure X hadn't messed up some registers.

              I'll double check the fbcon module (fbcon.ko isn't it?).


              I'll try a custom (newer) kernel if I have to. Was hoping to get it working out-of-the-box .

              Comment


              • #8
                Can you ssh to your laptop after enabling KMS? Or is it totally borked?

                For what it is worth here are the salient parts of dmesg on my laptop:

                Code:
                [email protected]:~$ dmesg | grep -e radeon -e drm
                Kernel command line: auto BOOT_IMAGE=linux-33 ro root=804 processor.max_cstate=2 radeon.dynclks=1 quiet gpt
                [drm] Initialized drm 1.1.0 20060810
                [drm] radeon defaulting to kernel modesetting.
                [drm] radeon kernel modesetting enabled.
                radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
                radeon 0000:01:00.0: setting latency timer to 64
                [drm] radeon: Initializing kernel modesetting.
                [drm] register mmio base: 0x90300000
                [drm] register mmio size: 65536
                [drm] GPU reset succeed (RBBM_STATUS=0x10000140)
                [drm] Generation 2 PCI interface, using max accessible memory
                [drm] radeon: VRAM 128M
                [drm] radeon: VRAM from 0x00000000 to 0x07FFFFFF
                [drm] radeon: GTT 512M
                [drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
                radeon 0000:01:00.0: irq 28 for MSI/MSI-X
                [drm] radeon: using MSI.
                [drm] radeon: irq initialized.
                [drm] Detected VRAM RAM=128M, BAR=128M
                [drm] RAM width 128bits DDR
                [drm] radeon: 128M of VRAM memory ready
                [drm] radeon: 512M of GTT memory ready.
                [drm] GART: num cpu pages 131072, num gpu pages 131072
                [drm] radeon: 1 quad pipes, 2 z pipes initialized.
                [drm] PCIE GART of 512M enabled (table at 0x00040000).
                [drm] radeon: cp idle (0x10000C03)
                [drm] Loading R500 Microcode
                platform radeon_cp.0: firmware: using built-in firmware radeon/R520_cp.bin
                [drm] radeon: ring at 0x0000000020000000
                [drm] ring test succeeded in 14 usecs
                [drm] radeon: ib pool ready.
                [drm] ib test succeeded in 0 usecs
                [drm] Default TV standard: NTSC
                [drm] Radeon Display Connectors
                [drm] Connector 0:
                [drm]   LVDS
                [drm]   DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
                [drm]   Encoders:
                [drm]     LCD1: INTERNAL_LVTM1
                [drm] Connector 1:
                [drm]   S-video
                [drm]   Encoders:
                [drm]     TV1: INTERNAL_KLDSCP_DAC2
                [drm] Connector 2:
                [drm]   DVI-I
                [drm]   HPD1
                [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
                [drm]   Encoders:
                [drm]     DFP1: INTERNAL_KLDSCP_TMDS1
                [drm] Connector 3:
                [drm]   VGA
                [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
                [drm]   Encoders:
                [drm]     CRT2: INTERNAL_KLDSCP_DAC2
                [drm] fb mappable at 0x800C0000
                [drm] vram apper at 0x80000000
                [drm] size 5299200
                [drm] fb depth is 24
                [drm]    pitch is 5888
                fb0: radeondrmfb frame buffer device
                [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0

                Comment


                • #9
                  Originally posted by amphigory View Post
                  Can you ssh to your laptop after enabling KMS? Or is it totally borked?
                  It hardlocks, can't SSH to it anymore. Doesn't even reply to ping.

                  Comment


                  • #10
                    Another possibility might be a loaded module KMS does not play nice with. vesafb?

                    Comment

                    Working...
                    X