Fajar - do you know something about video BAR errors?
On Sun November 13 2011, 12:17:22 PM, jim burns wrote:
> > > Let's see which driver is servicing the video card. On my systems,
> > > cirrusfb is a module, vesa is builtin. Builtins will not show up as
> > > a
> > > kernel driver in lspci -vvv. Then we'll see whether the cirrusfb
> > > module
> > > gets an error on loading.
> >
> >
> >
> > It seems not during loading even I've found this in the dmesg:
> > [ 32.626308] cirrusfb 0000:00:02.0: BAR 0: can't reserve [mem
> > 0xf0000000-0xf1ffffff pref]
> > [ 32.626312] cirrusfb 0000:00:02.0: cannot reserve region 0xf0000000,
> > abort [ 32.626324] cirrusfb: probe of 0000:00:02.0 failed with error
> > -16>
> > > What distribution is your dom0, and what xen version?
> >
> > First of all, I say that my dom0 works like a charm with most of my
> > domUs. Gentoo Linux x86_64 kernel 3.1.0-gentoo
> > app-emulation/xen-4.1.2
> > app-emulation/xen-tools-4.1.2
> > I'm using xl toolstack.
> >
> > > Finally, post your full dmesg from your domu. Maybe something will
> > > jump
> > > out at me.
> >
> >
> >
> > Yes, here it is: http://pastebin.com/vNpumSik
> >
> >
> >
> > Thanks a lot,
> > --
> > Flavio
>
> Yeah - the BAR error bothers me. Something is preventing the cirrusfb from
> initializing. Normally you get a handoff from the builtin vesa driver to
> the installed card driver. This is from my baremetal suse system:
>
> fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic
> driver
>
> BAR errors are not something I have experience with. I'm going to repost
> this section of your post, and see if Fajar has something to say.
>From his dmesg output:
[ 0.667812] vesafb: framebuffer at 0xf0000000, mapped to
0xffffc90000580000, using 1875k, total 4096k
[ 0.667815] vesafb: mode is 800x600x16, linelength=1600, pages=3
[ 0.667817] vesafb: scrolling: redraw
[ 0.667820] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[ 0.668044] bootsplash 3.1.6-2004/03/31: looking for picture...
[ 0.668047] bootsplash: silentjpeg size 124451 bytes
[ 0.674284] bootsplash: ...found (800x600, 62872 bytes, v3).
[ 0.688156] Console: switching to colour frame buffer device 96x33
[ 0.701329] fb0: VESA VGA frame buffer device
[ 32.626308] cirrusfb 0000:00:02.0: BAR 0: can't reserve [mem
0xf0000000-0xf1ffffff pref]
[ 32.626312] cirrusfb 0000:00:02.0: cannot reserve region 0xf0000000, abort
[ 32.626324] cirrusfb: probe of 0000:00:02.0 failed with error -16
They are both reserving the same area of memory, and unlike on my system, vesa
is not handing off to the selected card driver.
His system configuration is in the parent and grandparent of this post, and
his domu config was posted on Nov. 8.
Thanx.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home