On Sat, 10 Jan 2009 12:14:59 +1100 Dana <[email protected]> wrote: > On Sat, Jan 3, 2009 at 5:43 AM, Robert <[email protected]> wrote: > > Everything now works with -current. >
Hi, > I've never had much luck with the intel driver, even with somewhat > recent snapshots. > I am using intel(4) exclusivly without any problems. > When I try and use it, it bombs out with an "Unable to map mmio range" > error, then says that the server has segfaulted. > Never seen that msg before. > I'd like to try and do some X debugging, but it seems like if I try > and build X, it then interferes with the currently installed X > somehow, which I can't really have on this machine (I could be wrong, > however). > > The vesa driver works, though Xorg.0.log ends up spamming > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > eventually and continuously. > That one neither. There should be no need to compile X yourself to get this working. I'm using snapshots on my X200. > > [1] A catch to get the X intel(4) working for me: > > The X200 reports two outputs/monitors that have to be disabled. > > (This might mess with the dockingstation, but i don't have one of > > those.) > > This didn't help -- same error. > intel(4) "worked" for me even without those options, but i got a screen stitched together of 1024x768 tiles. > Dmesg: (ignore the stuff about sd1, I keep an empty SD-microSD > converter in there) > OpenBSD 4.4-current (GENERIC.MP) #2050: Sun Jan 4 13:27:04 MST 2009 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP I'm using a newer kernel built from source but an older snapshot. (Yeah yeah, kernel and userland out of sync, i know what i have to do before i cry for help.) To check if there are regressions concerning your problem i'm gonna update to the latest snapshot and report back. Which gets me to a gut feeling: Have you updated/sysmerge'd the coresponding xetc44.tgz? - Robert
