No announcement yet.

[drm] Could not set DRM device bus ID.

  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by agd5f View Post
    Did you build a kernel with radeon drm support?

    # Graphics support
    # CONFIG_AGP_ALI is not set
    # CONFIG_AGP_AMD is not set
    # CONFIG_AGP_AMD64 is not set
    # CONFIG_AGP_NVIDIA is not set
    # CONFIG_AGP_SIS is not set
    # CONFIG_AGP_SWORKS is not set
    # CONFIG_AGP_EFFICEON is not set
    # CONFIG_DRM_TDFX is not set
    # CONFIG_DRM_R128 is not set
    Here lsmod

    [email protected]:/usr/src/linux-$ lsmod
    Module                  Size  Used by
    radeon                124804  0
    drm                    64288  1 radeon
    snd_seq_dummy           2692  0
    snd_seq_oss            23956  0
    snd_seq_midi_event      6144  1 snd_seq_oss
    snd_seq                38048  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_pcm_oss            30624  0
    snd_mixer_oss          12288  1 snd_pcm_oss
    ipv6                  220724  12
    af_packet              14208  2
    fuse                   41756  1
    sg                     25904  0
    sr_mod                 12964  0
    cdrom                  30104  1 sr_mod
    ata_generic             4612  0
    ide_pci_generic         3588  0
    aes_i586                7808  1
    aes_generic            27944  1 aes_i586
    snd_emu10k1           112548  0
    snd_rawmidi            17696  1 snd_emu10k1
    snd_ac97_codec         87972  1 snd_emu10k1
    ac97_bus                1792  1 snd_ac97_codec
    snd_pcm                53512  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
    pata_via                7300  0
    snd_seq_device          6412  5 snd_seq_dummy,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
    evdev                   7940  1
    libata                120648  2 ata_generic,pata_via
    snd_timer              16900  3 snd_seq,snd_emu10k1,snd_pcm
    snd_page_alloc          7432  2 snd_emu10k1,snd_pcm
    snd_util_mem            4096  1 snd_emu10k1
    psmouse                32016  0
    serio_raw               4612  0
    snd_hwdep               6148  1 snd_emu10k1
    scsi_mod              127460  3 sg,sr_mod,libata
    airo                   55684  0
    emu10k1_gp              2688  0
    gameport                9736  2 emu10k1_gp
    via82cxxx               5636  0
    snd                    44212  11 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
    soundcore               6084  1 snd
    i2c_viapro              7444  0
    i2c_core               22928  1 i2c_viapro
    ide_core               83336  2 ide_pci_generic,via82cxxx
    via_agp                 7680  1
    agpgart                28976  2 drm,via_agp
    unix                   19088  268


    • #12
      BTW, thanks for the quick reply.

      I hope we here on this forum can puzzle this one out.


      • #13
        For those in the know, what are the relevent issues in this situation? I understand the MVP3 chipset has had past issues with the ATI video driver. Other reports I've read from other say that acceleration does work with this hardware combiniation under M-soft operating systems. That seems to be the only 'successes' I've read about.

        Does the root of this problem lie in a disconnect between the linux chipset support and the ATI r200 driver?

        In your humble opinion does a solution lie more with the chipset support? Or the radeon support?



        • #14
          Please pastebin your full xorg log and dmesg.


          • #15
            pastebin of Xorg log

            Here is the Xorg log.



            • #16
              Kernel Developers comments

              I sent a kernel developer a snippet of my Xorg log and asked his opinion.
              Here is a dusty issue I've brought to the ATI driver board.
              I'm just trying to understand if the via chipset support
              is where I should pursuit this issue, or strictly the
              X radeon driver folks. Or, some other.

              My MVP3 chipset board will does not allow my ATI r2xx video
              adapter to use DRI. The X log simply shows:

              He sent a brief reply. It might be helpful.

              Without looking to deeply into it, it looks like drmOpenDevice opens /dev/dri/card0 and then tries to set the busID of that device. That fails, probably because that's the VIA device. drmOpenDevice should then try /dev/dri/card1, but it doesn't. Also a little suspicious is the drmBetBusid return.

              So the issue is probably either in core drm or in libdrm.


              • #17
                Can you pastebin dmesg as well please ?


                • #18
                  pastebin of dmesg

                  Originally posted by bridgman View Post
                  Can you pastebin dmesg as well please ?
                  Yup, sorry I was futzing around a bit.



                  • #19
                    This is another hint from a kernel developer that responded.
                    > (II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module version 1.29.0
                    > .....
                    > drmGetBusid returned ''
                    > (II) [drm] DRM interface version 1.0
                    > (EE) [drm] Could not set DRM device bus ID.
                    > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.

                    Weird... maybe some process is keeping the DRM device open, does

                    sudo lsof /dev/dri/card0

                    give any results when the X server isn't running? If not, check out the kernel output; if it doesn't seem to have anything relevant, try writing 1 to /sys/modul /drm/parameters/debug before starting the X server.
                    FYI running the lsof /dev/dri/card0, did nothing at all.

                    I don't know what he means by "try writing 1 to /sys/modul /drm/parameters/debug". If someone helps me decipher this request, I'll try it. Thanks.


                    • #20
                      Originally posted by User0x45 View Post
                      This is another hint from a kernel developer that responded.

                      FYI running the lsof /dev/dri/card0, did nothing at all.

                      I don't know what he means by "try writing 1 to /sys/modul /drm/parameters/debug". If someone helps me decipher this request, I'll try it. Thanks.
                      (as root)
                      echo 1 > /sys/module/drm/parameters/debug

                      or when loading the drm module before starting X:
                      modprobe drm debug=1