On Tue, 4 Jan 2005, Stijn De Weirdt 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
> >
This is the good one:
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 16192 kB
(II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA
BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 865G
(--) I810(0): Chipset: "865G"
So the checksum is wrong.
But ... note that the VESA BIOS detected is not happening.
I am pretty sure that what is going on is that the option rom is not
getting mapped to 0xc0000 as required. I don't see how the MTRR failure
should really matter in this case. One thing that might matter: Linux
(without Xen) probably does not enable BIOS shadowing for the 0xc0000
region, and probably does not even now use it as RAM. But under Xen, is
that 0xc0000 set up as RAM or ... I have no idea, I have not looked at
this part of the linux modes -- a disadvantage to mainly having done Plan
9 work so far.
I also vaguely remember you can try to invoke X and tell it to NOT try to
run the vga bios, have you tried that? there is no real need to run it.
Sorry, I'm doing too much guessing here, I hope this helps.
ron
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home