From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58914] Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID
Date: Thu, 03 Jan 2013 03:24:16 +0000 [thread overview]
Message-ID: <bug-58914-502-mH16FOtko7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58914-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 815 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58914
--- Comment #4 from David Hagood <david.hagood@gmail.com> ---
I cannot say with rigor that it did work with older kernels, as prior to
upgrading to Ubuntu 12.4 I was running the non-Free fglrx drivers (forgive me
RMS for I have sinned....)
Bisecting is hard, because I am using many of the features of the newer kernel
now, and backtracking would be difficult. But if you can suggest a version to
test I can start.
I have seen other people running the Intel drivers reporting this same sort of
error (the missing busID in the drmGetBusid call), and they thought it was a
race condition (hence putting the driver into the initrd, which the Intel
driver folks said fixed their problem).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1665 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
next prev parent reply other threads:[~2013-01-03 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 23:32 [Bug 58914] New: Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID bugzilla-daemon
2013-01-02 11:44 ` [Bug 58914] " bugzilla-daemon
2013-01-02 12:22 ` bugzilla-daemon
2013-01-02 17:10 ` bugzilla-daemon
2013-01-03 3:24 ` bugzilla-daemon [this message]
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-mH16FOtko7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).