From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Bobulsky <rulerof@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Is: radeon 6990 with dom0 is not showing graphics. Was: Re: Some MSI related bugs when trying to use VT-d. Help identify software vs hardware problem?
Date: Tue, 28 May 2013 14:40:49 -0400 [thread overview]
Message-ID: <20130528184049.GA23266@phenom.dumpdata.com> (raw)
In-Reply-To: <3656599526576098219@unknownmsgid>
> When I say that they weren't hidden, while I didn't check with lspci -v,
> running xl pci-assignable-list shows that nothing is available to pass to a
> DomU. I have to xl pci-assignable-add every device I want to use
> regardless of whether or not it is hidden via my GRUB command line.
> Additionally, the Radeon driver was bound to the card I hid via grub, and
> its HDMI audio device was also bound to snd-hda-intel (I think) in spite of
> it also being in the grub command line.
>
> xl itself mentions that it is seizing devices from others drivers in order
> to bind them to pciback.
Ah, OK. that sounds good.
>
>
>
> I ended up on kernel 3.8.11 because various other kernels I tried,
>
> including 3.4.9 and something from the 3.7.x line both resulted in X
>
> failing to start, but only when booting Xen. After playing kernel shuffle
>
>
> X failing to start?
>
>
> Blinking (or solid, I cant recall precisely) underscore-type cursor in the
> upper left corner of the screen, and it appears to be at a BIOS-like
> text-mode resolution.
>
> What card at that point are you using? Is the radeon
> or another? How does it fail?
>
>
> I tried with the Radeon 6990, and also with a Radeon 5850. I tried with
> and without the Radeon driver, too, it didn't seem to make much difference
> :(
>
> If you boot with 'drm.debug=255 debug loglevel=8' on your
> command line what does dmesg (or /var/log/messages) show? Can you attach
> that
> please.
>
>
> I usually rebooted the system so my dmesg was out of date by the time i get
> my hands on it. I could try to SSH in, which should work as the system
> responds to Ctrl-Alt-Del by rebooting after a few seconds, or grab a
> historical log.... I'll report back next week :)
OK, lets track this as a seperate issue. If you use 'radeon.modset=0' on
the Linux command line do you see anything.
prev parent reply other threads:[~2013-05-28 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 10:38 Some MSI related bugs when trying to use VT-d. Help identify software vs hardware problem? Andrew Bobulsky
2013-05-08 8:45 ` George Dunlap
2013-05-08 16:48 ` Andrew Bobulsky
2013-05-10 13:36 ` Konrad Rzeszutek Wilk
2013-05-10 15:20 ` Andrew Bobulsky
2013-05-22 20:21 ` Konrad Rzeszutek Wilk
2013-05-22 21:32 ` Andrew Bobulsky
2013-05-28 18:40 ` Konrad Rzeszutek Wilk [this message]
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=20130528184049.GA23266@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=rulerof@gmail.com \
--cc=xen-devel@lists.xen.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).