[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] intel agp card support 2


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
  • From: Stijn De Weirdt <stijn.deweirdt@xxxxxxxxx>
  • Date: Tue, 4 Jan 2005 18:02:34 +0100
  • Delivery-date: Wed, 05 Jan 2005 02:12:09 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=BnQOHch88X8JqMvI8uYGZhcGbF9CjQH4a7Bk3PIWX9qc/xXrcsFU3xy0hO2qXlGrYPYPErrv3DiffVCQ/k6jfD5zx2o4ZMDooIGV+G1YDSojOVynTf4WY3uo1DCVqnhqp8n5egbOaY+j8cuuHF27H8mICyrhA9ZS7ZtM6jq88ug=
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>

attachment added


On Tue, 4 Jan 2005 18:01:30 +0100, Stijn De Weirdt
<stijn.deweirdt@xxxxxxxxx> wrote:
> On Tue, 4 Jan 2005 08:34:19 -0700 (MST), Ronald G. Minnich
> <rminnich@xxxxxxxx> wrote:
> > > (WW) I810(0): Bad V_BIOS checksum
> >
> > this is bad. It's a warning but it should not be happening. It means the
> > vga bios checksum was wrong. Do you get this if you boot without xen, i.e.
> > standard linux?
> yes, it's actaully not that unfrequent.
> >
> > > (II) I810(0): Primary V_BIOS segment is: 0xc000
> > > (WW) System lacks support for changing MTRRs
> > > (EE) I810(0): unknown type(0xffffffff)=0xff
> > 
> i think this is much worse :)
> 
> > I forget where this EE comes from, but:
> > > (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, 
> > > EDX=0x00000000
> > > (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, 
> > > EDI=0x00002000
> > > (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, 
> > > GS=0x0000
> > > (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200
> > > (II) I810(0): code at 0x000c0014:
> > >  e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47
> > >  41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f
> > > (II) stack at 0x00001ffa:
> > >  00 06 00 00 00 32
> > > (II) I810(0): VESA BIOS not detected
> >
> > As I read this, the module loader tried to run the vga bios and failed, as
> > it could not get to the actual BIOS code? That's how it looks to me
> > anyway.
> >
> > I have no idea: has anyone seen option rom access working under Xen? I
> > have not, but I have not tried this recently. The VGA bios ROM is not
> > accessible on my laptop, however.
> >
> > Does Xen currently allow a guest to set enable the option rom access and
> > set the register (0x30 I think) for the option ram base address?
> >
> >
> > > (EE) I810(0): VBE initialization failed.
> >
> > So you get this error, and ...
> >
> > > (II) UnloadModule: "i810"
> > > (II) UnloadModule: "int10"
> > > (II) UnloadModule: "vgahw"
> > > (II) Unloading /usr/X11R6/lib/modules/libvgahw.a
> > > (II) UnloadModule: "vbe"
> > > (II) Unloading /usr/X11R6/lib/modules/libvbe.a
> > > (II) UnloadModule: "int10"
> > > (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a
> > > (EE) Screen(s) found, but none have a usable configuration.
> >
> > it unloads the modules since it can't run the vga bios.
> >
> > ron
> > 
> i've attached a working X.0.log
> 
> hopefully this gets resolved soon.
> 
> stijn
>

Attachment: XFree86.0.log
Description: Binary data


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.