xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
@ 2011-05-27 12:50 John McDermott (U.S. Navy Employee)
  2011-05-27 13:55 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 6+ messages in thread
From: John McDermott (U.S. Navy Employee) @ 2011-05-27 12:50 UTC (permalink / raw)
  To: xen-devel

Xen Users,

In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results.

Any suggestions?

Sincerely,

John
----
What is the formal meaning of the one-line program
#include "/dev/tty"

J.P. McDermott			building 12
Code 5542			mcdermott@itd.nrl.navy.mil
Naval Research Laboratory	voice: +1 202.404.8301
Washington, DC 20375, US	fax:   +1 202.404.7942

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
  2011-05-27 12:50 PVOPS dom0 requires nomodeset to boot but video requires modesetting driver John McDermott (U.S. Navy Employee)
@ 2011-05-27 13:55 ` Konrad Rzeszutek Wilk
  2011-05-27 15:31   ` John McDermott (U.S. Navy Employee)
  0 siblings, 1 reply; 6+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-05-27 13:55 UTC (permalink / raw)
  To: John McDermott (U.S. Navy Employee); +Cc: xen-devel

On Fri, May 27, 2011 at 08:50:45AM -0400, John McDermott (U.S. Navy Employee) wrote:
> Xen Users,
> 
> In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results.
> 

You need to give more details. lspci -vv, dmesg, serial console, which version of Dom0, etc.

> Any suggestions?

Couple, but not sure if they apply without the data above.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
  2011-05-27 13:55 ` Konrad Rzeszutek Wilk
@ 2011-05-27 15:31   ` John McDermott (U.S. Navy Employee)
  2011-05-27 15:52     ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 6+ messages in thread
From: John McDermott (U.S. Navy Employee) @ 2011-05-27 15:31 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

[-- Attachment #1: Type: text/plain, Size: 520 bytes --]

Konrad,

Thanks. Domain 0 is one of Jeremy's pvops kernels, the latest 2.6.32.25, as far as I can tell, downloaded as a snapshot. The tarball called itself xen-51f9f52, but I don't know if that is a unique id. I am trying to bring this up on Fedora 14. X forwarding works just fine. I have not set up the networking properly on this box, so that will not look right, but does not matter.

Attached are the outputs from the serial console, dmesg, lspci, and X logs for bare metal and Xen boots of the dom0 kernel:


[-- Attachment #2: dumps.tgz --]
[-- Type: application/octet-stream, Size: 37820 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1175 bytes --]



Sincerely,

John

On May 27, 2011, at 9:55 AM, Konrad Rzeszutek Wilk wrote:

> On Fri, May 27, 2011 at 08:50:45AM -0400, John McDermott (U.S. Navy Employee) wrote:
>> Xen Users,
>> 
>> In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results.
>> 
> 
> You need to give more details. lspci -vv, dmesg, serial console, which version of Dom0, etc.
> 
>> Any suggestions?
> 
> Couple, but not sure if they apply without the data above.

----
What is the formal meaning of the one-line program
#include "/dev/tty"

J.P. McDermott			building 12
Code 5542			mcdermott@itd.nrl.navy.mil
Naval Research Laboratory	voice: +1 202.404.8301
Washington, DC 20375, US	fax:   +1 202.404.7942










[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
  2011-05-27 15:31   ` John McDermott (U.S. Navy Employee)
@ 2011-05-27 15:52     ` Konrad Rzeszutek Wilk
  2011-05-27 16:17       ` John McDermott (U.S. Navy Employee)
  0 siblings, 1 reply; 6+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-05-27 15:52 UTC (permalink / raw)
  To: John McDermott (U.S. Navy Employee); +Cc: xen-devel

On Fri, May 27, 2011 at 11:31:01AM -0400, John McDermott (U.S. Navy Employee) wrote:
> Konrad,
> 
> Thanks. Domain 0 is one of Jeremy's pvops kernels, the latest 2.6.32.25, as far as I can tell, downloaded as a snapshot. The tarball called itself xen-51f9f52, but I don't know if that is a unique id. I am trying to bring this up on Fedora 14. X forwarding works just fine. I have not set up the networking properly on this box, so that will not look right, but does not matter.
> 
> Attached are the outputs from the serial console, dmesg, lspci, and X logs for bare metal and Xen boots of the dom0 kernel:
> 

Nothing jumps at me. The Xorg doesn't boot b/c there is no /dev/fb0, but it
is present when you boot baremetal.

Can you fiddle with 'drm.debug=255' and 'i915' parameters to see if it can
output some more details?

Also, 2.6.32.25 is a bit old. You should try to update it.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
  2011-05-27 15:52     ` Konrad Rzeszutek Wilk
@ 2011-05-27 16:17       ` John McDermott (U.S. Navy Employee)
  2011-05-31 13:52         ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 6+ messages in thread
From: John McDermott (U.S. Navy Employee) @ 2011-05-27 16:17 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

Konrad,

Agreed. However, this is the newest kernel I have been able to build and boot, on the target box. I started with the latest and worked my way back down to 2.6.32.25, to get one that would build and boot. Most of our platforms are up to about 2.6.32.32 or thereabouts.

The target is an Intel DG35JO board, which is a bit old itself? It does not expose all of the latest VT-d features, so perhaps it would be better to set the whole platform aside and put efforts into getting newer hardware that can do things like SR-IOV and EPT?

Sincerely,

John
---

On May 27, 2011, at 11:52 AM, Konrad Rzeszutek Wilk wrote:

> Also, 2.6.32.25 is a bit old. You should try to update it.

----
What is the formal meaning of the one-line program
#include "/dev/tty"

J.P. McDermott			building 12
Code 5542			mcdermott@itd.nrl.navy.mil
Naval Research Laboratory	voice: +1 202.404.8301
Washington, DC 20375, US	fax:   +1 202.404.7942

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
  2011-05-27 16:17       ` John McDermott (U.S. Navy Employee)
@ 2011-05-31 13:52         ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 6+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-05-31 13:52 UTC (permalink / raw)
  To: John McDermott (U.S. Navy Employee); +Cc: xen-devel

On Fri, May 27, 2011 at 12:17:57PM -0400, John McDermott (U.S. Navy Employee) wrote:
> Konrad,
> 
> Agreed. However, this is the newest kernel I have been able to build and boot, on the target box. I started with the latest and worked my way back down to 2.6.32.25, to get one that would build and boot. Most of our platforms are up to about 2.6.32.32 or thereabouts.

Whooooa. What are the boot issues with the newer kernels?

BTW, you hadn't provided me with the 'drm.debug=255' and 'i915..' debug options.
> 
> The target is an Intel DG35JO board, which is a bit old itself? It does not expose all of the latest VT-d features, so perhaps it would be better to set the whole platform aside and put efforts into getting newer hardware that can do things like SR-IOV and EPT?

It should work. I've some more ancient boxes than that and they boot fine.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-05-31 13:52 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-27 12:50 PVOPS dom0 requires nomodeset to boot but video requires modesetting driver John McDermott (U.S. Navy Employee)
2011-05-27 13:55 ` Konrad Rzeszutek Wilk
2011-05-27 15:31   ` John McDermott (U.S. Navy Employee)
2011-05-27 15:52     ` Konrad Rzeszutek Wilk
2011-05-27 16:17       ` John McDermott (U.S. Navy Employee)
2011-05-31 13:52         ` Konrad Rzeszutek Wilk

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).