XFree86-4-Server-snap fails on VIA CLE266 running 5-CURRENT
chris at shenton.org
Mon Apr 12 10:28:49 PDT 2004
Sorry for the cross-posting, problem seems to cross these three lists;
remove inappropriate ones on reply if desired.
I've got a VIA EPIA box which has the CastleRock CLE266 video
chipset. Matt Dillion provided instructions on how to get the port
XFree86-4-Server-snap to run, so I've been able to run its 18.104.22.168
build for a while.
Last night I updated the port, which got XFree86 22.214.171.124. It works
on my other non-VIA machines, but on the VIA CLE266 box it bombs upon
startup, using the same XFree86Config file I had been using
earlier. /var/log/XFree86.0.log repeats several times before death:
Symbol drmOpen from module /usr/X11R6/lib/modules/drivers/via_drv.o is unresolvable
Symbol drmClose from module /usr/X11R6/lib/modules/drivers/via_drv.o is unresolvable
After some googling I added lines to my XFree86Config:
This made the "drmOpen/drmClose unresolvable" messages go away, but it
died anyway, with no indication why.
I suspected that DRI/DRM isn't working for me, since VIA isn't one of
the common chipsets that seem to be supported, like here:
-rw-r--r-- 1 root wheel 141 Sep 9 2003 Makefile
-rw-r--r-- 1 root wheel 110 Nov 6 2002 Makefile.inc
drwxr-xr-x 2 root wheel 512 Jan 14 06:04 mga
drwxr-xr-x 2 root wheel 512 Jan 14 06:04 r128
drwxr-xr-x 2 root wheel 512 Jan 14 06:04 radeon
drwxr-xr-x 2 root wheel 512 Jan 14 06:04 sis
drwxr-xr-x 2 root wheel 512 Jan 14 06:04 tdfx
I then recomiled the XFree86-4-Server-snap after hacking the Makefile
to get it to *not* use:
But again, it died on the VIA on startup, with no message indicating
what failed in the log file.
Am I correct in thinking that the problem is with FreeBSD's DRI/DRM
support of the VIA CLE266 chips? If so, is there a way to tell
XFree86Config to NOT use these features, to disable these options?
If it's something else, any suggestions for a work-around?
If 126.96.36.199 simply won't on my HW, can someone provide the
incantation to cvsup the port from back when it used XFree86-188.8.131.52 ?
Any other suggestions?
More information about the freebsd-ports