Date: Sun, 22 Apr 2012 19:40:04 -0400 (EDT) From: doug <doug@fledge.watson.org> To: Mark Felder <feld@feld.me> Cc: freebsd-questions@FreeBSD.org Subject: Re: recommendation(s) for new computer Message-ID: <alpine.BSF.2.00.1204221448150.87726@fledge.watson.org> In-Reply-To: <op.wc2zsxdm34t2sn@tech304> References: <4F917E90.9000205@uni-dortmund.de> <op.wc2xcbkw34t2sn@tech304> <cc6d0a6a-79b2-45b5-8ffd-b8ff11ba8604@cds005.dcs.int.inet> <op.wc2zsxdm34t2sn@tech304>
index | next in thread | previous in thread | raw e-mail
On Fri, 20 Apr 2012, Mark Felder wrote:
> On Fri, 20 Apr 2012 15:34:11 -0500, Dale Scott <dalescott@shaw.ca> wrote:
>
>> As do Intel (video) drivers....
>
> Not if they require GEM/KMS like all the modern variants do; they're not
> supported in FreeBSD yet. I have a laptop (Google CR48) that's running the
> very experimental GEM/KMS code because otherwise it's stuck with a horrible
> resolution. Even with a custom kernel and custom ports/X11 patches it still
> has quirks like not being able to get your vty back after you start X.
Is there a PR on this, or at least are the developers aware of it? I could not
find a PR. I am running an out-of-the-box 9.0. I tested xorg 7.5 with nothing
else other than xdm installed does and got this result. This makes it impossible
to investigate any other issues that might arise.
My setup:
FreeBSD artemis.boltsys.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0:
Tue Jan 3 07:46:30 UTC 2012
root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
xorg-7.5.1
xdm-1.1.11
twm-1.0.7
xorg.conf
Section "Monitor"
#DisplaySize 410 260 # mm
Identifier "Monitor0"
VendorName "ACR"
ModelName "AL1916W"
HorizSync 30.0 - 82.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "Wrestler [Radeon HD 6310]"
BusID "PCI:0:1:0"
EndSection
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1204221448150.87726>