WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Pkg-xen-devel] [Xen-devel] xen-linux-system-2.6.32-5-xen-amd64: Len

To: Mike Viau <viaum@xxxxxxxxxxxxxxx>
Subject: Re: [Pkg-xen-devel] [Xen-devel] xen-linux-system-2.6.32-5-xen-amd64: Lenovo R61, kernel boots on baremetel, no boot with xen4 hypervisor‏
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 30 Aug 2010 10:44:14 -0400
Cc: pkg-xen-devel@xxxxxxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, ijc@xxxxxxxxxxxxxx
Delivery-date: Mon, 30 Aug 2010 07:47:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY148-w3BE60AD1AB0DB474C16EEEF890@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BAY148-w599FBD6DC05A72EB8AFB0EEF890@xxxxxxx> <1283162286.6575.10.camel@xxxxxxxxxxxxxxxxxxxxxx> <BAY148-w2387D01B21A10D67FEDB1BEF890@xxxxxxx> <1283175591.6575.73.camel@xxxxxxxxxxxxxxxxxxxxxx> <BAY148-w3BE60AD1AB0DB474C16EEEF890@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-12-10)
On Mon, Aug 30, 2010 at 10:16:17AM -0400, Mike Viau wrote:
> 
> > On Mon, 30 Aug 2010 14:39:51 +0100 <ijc@xxxxxxxxxxxxxx> wrote:
> > 
> > Sid kernel would be most interesting first off, I think.
> > 
> > Ian.
> 
> Same behaviors after updating the three packages: 
> xen-linux-system-2.6.32-5-xen-amd64, linux-image-2.6.32-5-xen-amd64, and 
> linux-base (2.6.32-21).
> 
> apt-cache policy xen-linux-system-2.6.32-5-xen-amd64
> xen-linux-system-2.6.32-5-xen-amd64:
>   Installed: 2.6.32-21
>   Candidate: 2.6.32-21
>   Version table:
>  *** 2.6.32-21 0
>         500 http://mirror.csclub.uwaterloo.ca sid/main Packages
>         100 /var/lib/dpkg/status
>      2.6.32-20 0
>         990 http://mirror.csclub.uwaterloo.ca squeeze/main Packages
> 
> apt-cache policy linux-image-2.6.32-5-xen-amd64
> linux-image-2.6.32-5-xen-amd64:
>   Installed: 2.6.32-21
>   Candidate: 2.6.32-21
>   Version table:
>  *** 2.6.32-21 0
>         500 http://mirror.csclub.uwaterloo.ca sid/main Packages
>         100 /var/lib/dpkg/status
>      2.6.32-20 0
>         990 http://mirror.csclub.uwaterloo.ca squeeze/main Packages
> 
> apt-cache policy linux-base
> linux-base:
>   Installed: 2.6.32-21
>   Candidate: 2.6.32-21
>   Version table:
>  *** 2.6.32-21 0
>         500 http://mirror.csclub.uwaterloo.ca sid/main Packages
>         100 /var/lib/dpkg/status
>      2.6.32-20 0
>         990 http://mirror.csclub.uwaterloo.ca squeeze/main Packages
> 
> Bare-metal or with hypervisor does not boot with nomodeset on the kernel 
> cmdline.
> 
> Just for troubleshooting purpose the current default Debian squeeze kernel 
> linux-image-2.6.32-5-amd64 (2.6.32-20) also does not boot when nomodeset is 
> set on the kernel cmdline.
> 

Well, 'nomodeset' I don't think will help b/c you don't have KMS in
squeeze (I believe so).

The other thing is that you have:
Aug 21 09:08:27 BUBBLE kernel: [    5.046676] NVRM: loading NVIDIA UNIX
x86_64 Kernel Module  173.14.25  Thu Jan 28 01:53:43 PST

the proprietary NVidia driver loaded. We haven't tried those
yet and instead focused on making sure the upstream nouveau drivers
work with Xen. Which they do now.

I would suggest you boot in runlevel 3, so that X is not started and see
if the machine works (as in, you don't see other failures).

And if you want X and the NVidia driver (the proprietary one), you might
need to take the brunt of debugging it and finding where the NVidia is
doing some weird stuff.

Or, there is another option, and that to use a back-ported version of
2.6.34 DRM/KMS/TTM driversets which include the nouveau support.
(I am right now running with that on a GeForce 8600 GT on Xen 4.1 +
latest PVOPS kernel).


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

<Prev in Thread] Current Thread [Next in Thread>