All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58914] New: Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID
Date: Mon, 31 Dec 2012 23:32:34 +0000	[thread overview]
Message-ID: <bug-58914-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4251 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=58914

          Priority: medium
            Bug ID: 58914
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Cannot start Radeon driver: "drmOpenByBusid:
                    drmGetBusid reports " no bus ID
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: david.hagood@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 72358
  --> https://bugs.freedesktop.org/attachment.cgi?id=72358&action=edit
X Start up log messages

The Radeon driver will not load with the Radeon kernel drivers in Linux 3.8.0

The following is an excerpt from the startup:

[   109.112] (II) Loading extension DRI2
[   109.112] (II) LoadModule: "radeon"
[   109.112] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[   109.112] (II) Module radeon: vendor="X.Org Foundation"
[   109.112]    compiled for 1.12.3, module version = 7.0.99
[   109.112]    Module class: X.Org Video Driver
[   109.112]    ABI class: X.Org Video Driver, version 12.0
[   109.112] (II) RADEON: Driver for ATI Radeon chipsets:
        ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
(many cards snipped)
[   109.114] (--) using VT number 8

[   109.119] (II) [KMS] Kernel modesetting enabled.
[   109.120] (II) RADEON(0): Creating default Display subsection in Screen
section
        "Default Screen Section" for depth/fbbpp 24/32
[   109.120] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[   109.120] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp
pixmaps)
[   109.120] (==) RADEON(0): Default visual is TrueColor
[   109.120] (==) RADEON(0): RGB weight 888
[   109.120] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[   109.120] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f)
[   109.120] drmOpenDevice: node name is /dev/dri/card0
[   109.120] drmOpenDevice: open result is 9, (OK)
[   109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0
[   109.120] drmOpenDevice: node name is /dev/dri/card0
[   109.120] drmOpenDevice: open result is 9, (OK)
[   109.120] drmOpenByBusid: drmOpenMinor returns 9
[   109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0
[   109.120] drmOpenDevice: node name is /dev/dri/card0
[   109.120] drmOpenDevice: open result is 9, (OK)
[   109.120] drmOpenByBusid: drmOpenMinor returns 9
[   109.120] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[   109.120] drmOpenByBusid: drmGetBusid reports 

That last line is not a copy/paste issue - it literally is
"[   109.120] drmOpenByBusid: drmGetBusid reports "

(as in, there is no bus ID given)

Then the X Radeon driver looks for any other DRI node, fails, and dies.

[   109.120] drmOpenDevice: node name is /dev/dri/card1
[   109.125] drmOpenByBusid: drmOpenMinor returns -1
(snip many other searches)
[   109.170] drmOpenDevice: node name is /dev/dri/card14
[   109.174] drmOpenByBusid: drmOpenMinor returns -1
[   109.174] drmOpenDevice: node name is /dev/dri/card15
[   109.178] drmOpenByBusid: drmOpenMinor returns -1
[   109.178] drmOpenDevice: node name is /dev/dri/card0
[   109.178] drmOpenDevice: open result is 9, (OK)
[   109.178] drmOpenDevice: node name is /dev/dri/card0
[   109.178] drmOpenDevice: open result is 9, (OK)
[   109.178] drmGetBusid returned ''
[   109.178] (EE) RADEON(0): [drm] failed to set drm interface version.
[   109.178] (EE) RADEON(0): Kernel modesetting setup failed
[   109.178] (II) UnloadModule: "radeon"
[   109.178] (EE) Screen(s) found, but none have a usable configuration.

I have tried the following:
1) adding the following parameters in /etc/modprobe.d/radeon.conf
   options radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1
2) Adding the following to /etc/initramfs-tools/modules
   radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1
and rebuilding the ramdisk.

The kernel has the following configuration with respect to the Radeon drivers:
CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_KMS=y
# CONFIG_FB_RADEON is not set

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5780 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-12-31 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31 23:32 bugzilla-daemon [this message]
2013-01-02 11:44 ` [Bug 58914] Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID bugzilla-daemon
2013-01-02 12:22 ` bugzilla-daemon
2013-01-02 17:10 ` bugzilla-daemon
2013-01-03  3:24 ` bugzilla-daemon
2013-01-03 10:30 ` bugzilla-daemon
2019-11-19  8:31 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-58914-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.