Date: Fri, 10 Jun 2005 11:50:15 -0700 From: Remington L <mrl0lz@gmail.com> To: Craig Kleski <ckleski@mbc.edu> Cc: freebsd-questions@freebsd.org, Ben Paley <ben@spooty.net> Subject: Re: 1280x800 display, i810, 915, etc etc etc Message-ID: <fe18b22805061011501743fb3d@mail.gmail.com> In-Reply-To: <200506101336.55019.ckleski@mbc.edu> References: <200506071529.47798.ben@spooty.net> <fe18b2280506091509583f3800@mail.gmail.com> <200506100827.53946.ben@spooty.net> <200506101336.55019.ckleski@mbc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
It is also not officially supported by Xorg. I am told by the driver=20 developer 6.8.3 will fully support it(hopefully eliminating the need for an= y=20 VBIOS workaround) On 6/10/05, Craig Kleski <ckleski@mbc.edu> wrote: >=20 > On Friday 10 June 2005 07:27 am, Ben Paley wrote: > > On Thursday 09 June 2005 23:09, Remington L wrote: > > > Correction, sorry for the previously post(I'm at work). The problem > > > lies with the Intel VBIOS not reporting the correct resolution to > > > Xorg. As a workaround you need to modify the VBIOS and use an > > > updated i810 driver. Here is the Xorg i810 driver: > > > http://www.fairlite.demon.co.uk/intel.html > > > To modify the VBIOS please install and run sysutils/915resolution. > > > Thank'll fix it! > > > > I shouldn't complain because it seems actually to be running at > > 1280x800 at last (at least, kde display manager tells me so, and > > Opera reports it using screen.availHeight and screen.availWidth!), > > but there are a couple of odd things going on... > > > > A) I ran 915resolution before doing all the things I did to get it > > working, resetting all of the 1280x1024 modes to 1280x800. But it > > only works on the memory copy of the VBIOS, and, indeed, this morning > > when I rebooted, and still now, 915resolution -l gives three modes at > > 1280x1024 and none at 1280x800... AND YET my screen is running > > happily at 1280x800! > > > > B) None of my attempts to use the i810 driver came to anything. If I > > added Chipset "915G" I would get slightly different errors, but never > > a working screen (though interestingly I managed to get as far as > > hearing the KDE startup sound even when I couldn't see anything!). My > > current xorg.conf uses the generic vesa driver. > > > > So the two things that I was concentrating on - the VBIOS and the > > driver, turn out not to have been the real issues at all. Heaven > > knows *what* the real issues were... it all just goes to show that X > > configuration is black magic, and I could just as easily have waved a > > chicken at it for the same result, and probably quicker (though not > > as cheap, of course). > > > > If anyone is interested, I will be glad to send my xorg.conf, and > > logs and all the rest of it. > > > > Thank you all very much for your help! I may be none the wiser, but I > > am much happier! > > > > Cheers, > > Ben > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" >=20 > IIRC, i915 agp is not supported in -stable >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D80396 >=20 > Somewhere in this PR is a patch for i915 agp support. Theoretically it > should allow you to use the i810 driver and not the VESA driver. >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fe18b22805061011501743fb3d>