Date: Wed, 26 Feb 2003 14:13:58 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: Daniel Eischen <eischen@vigrid.com> Cc: current@FreeBSD.org Subject: Re: What broke X between 5.0R and recent current? Message-ID: <20030226131358.GB631@crow.dom2ip.de> In-Reply-To: <3E5A9CA9.A31E8081@vigrid.com> References: <3E5A9CA9.A31E8081@vigrid.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2003/02/24 at 17:28:57 -0500, Daniel Eischen wrote: > So I got a new Dell laptop, ATI Radeon 7500. Installed FreeBSD > 5.0-RELEASE, X 4.2.1, and KDE right off the FreeBSD Mall CD-ROM. > I configured X from the installation setup and was happily > running X and KDE @ 1400x1050. Cool. > > Then I cvsup'd to a recent -current from about a week ago, > which my other laptop and desktop are currently running just > fine (both use very old 3.x or 4.x built X's, probably XFree86 > 3.2.x and running with compat libraries). Now X refuses to > work. It's not the kernel because before installing world, > I installed the kernel and booted it to make sure everything > still worked. X was happy with the old kernel too 'cause > I went back and tried it again also. But after the installworld, > X didn't work, not even xf86cfg. I tried the installworld with > and without mergemaster'ing and X didn't work regardless. I > went back and did another fresh install of 5.0R and X worked > again, but after another installworld, I got the same problem. > The XFree86 log file is at the end. It aborts with: > > [...] > (II) LoadModule: "ddc" > (II) Reloading /usr/X11R6/lib/modules/libddc.a > (II) RADEON(0): VESA VBE DDC supported > (II) RADEON(0): VESA VBE DDC Level none > (II) RADEON(0): VESA VBE DDC transfer in appr. 2 sec. > (II) RADEON(0): VESA VBE DDC read failed > (==) RADEON(0): Write-combining range (0xfcff0000,0x80000) was already clear > (==) RADEON(0): Write-combining range (0xe0000000,0x2000000) > (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=35000; xclk=16600 > (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) > > Fatal server error: > Caught signal 10. Server aborting > > Any ideas? I'm in the process of trying a more recent -current > and am also going to try and rebuild X (though we shouldn't > have to do that). I saw something like that on my notebook, too - in my case, it was a problem in the radeon driver which could be worked around by adding an explicit "Modes" line in the used Display subsection in XF86Config, like: Section "Screen" [...] DefaultColorDepth 24 [...] SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection - Thomas -- Thomas Moestl <tmoestl@gmx.net> http://www.tu-bs.de/~y0015675/ <tmm@FreeBSD.org> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030226131358.GB631>