kernel mode setting

kernel mode setting

[Michael D Labriola]

Should Kernel Mode Setting (KMS) work in the xen/master branch with Xen 
3.4.2?  I noticed that most of the example grub.confs I've seen around 
have nomodeset on the kernel command line...

-Mike

---
Michael D Labriola
Electric Boat
mlabriol@gdeb.com
401-848-8871 (desk)
401-848-8513 (lab)
401-316-9844 (cell)

Re: kernel mode setting

[Pasi Kärkkäinen]

On Wed, Feb 10, 2010 at 09:53:15AM -0500, Michael D Labriola wrote:
> Should Kernel Mode Setting (KMS) work in the xen/master branch with Xen 
> 3.4.2?  I noticed that most of the example grub.confs I've seen around 
> have nomodeset on the kernel command line...
> 

Try it and let us know :)

I've had problems with kms on my radeon system.. but it might work for you.

-- Pasi

Re: kernel mode setting

[Michael D Labriola]

Well, here's what I've done so far.  In a fit of rage aimed towards the 
lameness of the nv driver, I cherry-picked all the drm commits from the 
official nouveau git tree into my xen/master checkout.  And it semi-works. 
 Baremetal it looks good for a few minutes then X gets corrupted.  Under 
Xen 3.4.2, X locks up before anything is even painted to the screen.  If I 
force the xorg nouveau driver to use software rendering, my system appears 
to be perfectly stable with good 2d support.  My compiled upstream nouveau 
tree works perfectly (although the hardware acceleration is slow).

Now, it was late at night and I was bleary eyed... and that's a TON of 
commits to get merged in a code base I've never looked at before...  and I 
GUESSED at which commits to apply... so I'm encouraged that anything 
worked at all.  :-)

Now I'm trying to decide if the X lockup under Xen is my fault (mangled a 
merge conflict, missed a commit, etc), or whether something in the 3.4.2 
hypervisor in just plain incompatible with KMS DRM drivers.  I suppose I 
can try getting a Xen 4.0-rc build installed and see if the behavior 
changes...

And there's also the potential to try getting it to work under xen/next... 
although I'm not so sure that that would be wise at this point.

-Mike

---
Michael D Labriola
Electric Boat
mlabriol@gdeb.com
401-848-8871 (desk)
401-848-8513 (lab)
401-316-9844 (cell)



Pasi Kärkkäinen <pasik@iki.fi> 
02/10/2010 10:15 AM

To
Michael D Labriola <mlabriol@gdeb.com>
cc
Xen-devel <xen-devel@lists.xensource.com>
Subject
Re: [Xen-devel] kernel mode setting






On Wed, Feb 10, 2010 at 09:53:15AM -0500, Michael D Labriola wrote:
> Should Kernel Mode Setting (KMS) work in the xen/master branch with Xen 
> 3.4.2?  I noticed that most of the example grub.confs I've seen around 
> have nomodeset on the kernel command line...
> 

Try it and let us know :)

I've had problems with kms on my radeon system.. but it might work for 
you.

-- Pasi

Re: kernel mode setting

[Konrad Rzeszutek Wilk]

On Wed, Feb 10, 2010 at 10:45:52AM -0500, Michael D Labriola wrote:
> Well, here's what I've done so far.  In a fit of rage aimed towards the 
> lameness of the nv driver, I cherry-picked all the drm commits from the 
> official nouveau git tree into my xen/master checkout.  And it semi-works. 
>  Baremetal it looks good for a few minutes then X gets corrupted.  Under 
> Xen 3.4.2, X locks up before anything is even painted to the screen.  If I 
> force the xorg nouveau driver to use software rendering, my system appears 
> to be perfectly stable with good 2d support.  My compiled upstream nouveau 
> tree works perfectly (although the hardware acceleration is slow).
> 
> Now, it was late at night and I was bleary eyed... and that's a TON of 
> commits to get merged in a code base I've never looked at before...  and I 
> GUESSED at which commits to apply... so I'm encouraged that anything 
> worked at all.  :-)
> 
> Now I'm trying to decide if the X lockup under Xen is my fault (mangled a 
> merge conflict, missed a commit, etc), or whether something in the 3.4.2 
> hypervisor in just plain incompatible with KMS DRM drivers.  I suppose I 
> can try getting a Xen 4.0-rc build installed and see if the behavior 
> changes...
> 
> And there's also the potential to try getting it to work under xen/next... 
> although I'm not so sure that that would be wise at this point.

It does not have the backends in yet, so you can't launch guests yet :-(