Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
X Operating Systems GUI BSD

XFree86 4.3.0 in FreeBSD Ports Tree 23

Posted by michael from the eye-candy dept.
Dan writes "Eric Anholt has committed the long awaited XFree86 4.3.0 to the FreeBSD ports tree. Please report any issues, bugs, etc. directly to him. The port appears to have support for popular cards such as NVidia, ATI, etc. Eric suggests that you use portupgrade to ensure you update fully from an earlier version of XFree86."
This discussion has been archived. No new comments can be posted.

XFree86 4.3.0 in FreeBSD Ports Tree More

XFree86 4.3.0 in FreeBSD Ports Tree

Comments Filter:

  • A pleasant surprise... (Score:4, Informative)

    by CoolVibe ( 11466 ) on Wednesday March 12, 2003 @01:15PM (#5494880) Journal
    Heck, I did a portupgrade after cvsupping my ports and hey presto, new X. Woohoo! What a nice present.

    Oh, I have to remark that the nvidia drivers for FreeBSD work surprisingly well under Xfree 4.3. So far no problems. My Geforce 4 is happily screaming away at 1600x1200. Life is good :)

  • matrox g550 didn't work for me (Score:4, Informative)

    by TheGratefulNet ( 143330 ) on Wednesday March 12, 2003 @01:21PM (#5494927)
    I had to use the linux tarball of the matrox supplied *drv.o files.

    the bsd ones (from the ports) just kept giving weird errors.

    the port maintainer knows this now, but if you are running a dual-dvi system (which NEEDS the matrox HAL lib) then maybe try getting the linux .o files and putting them in the /modules/lib... area instead of the port-built ones.

    fyi.
    • Hmm, odd. I seem to remember that the Xfree86 port had an WITH_MATROX_GXX_DRIVER (or somesuch) knob you could twiddle, but looking at the port Makefile, it seems to be gone.

      Basically, what it did was download the Matrox Gxx source drivers and build them with X11. It's how I got my dual-head Matrox G400 working under FreeBSD on my other workstation.

      Oh well... Guess I'd have to wait with updating X on that box.

      • that knob DID produce a few .o files.

        but those files DIDN'T WORK! don't know why - its beyond me - but I know for a fact they didn't work and that the 'linux' .o files (from the matrox site) did work.

        weird. but true.

        also, dualhead and dualhead DVI are quite diff. I run dual dvi. for that, you need the HAL lib. for regular dual, you don't (AFAIK)

  • From the article:

    graphics/drm-kmod isn't going to be updated for 4.3.0.

    Anybody know why not? And why no HAL support?

    • Anybody know why not?

      Because graphics/drm-kmod is sort of deprecated. It only exists for the 4.x tree, because the drm stuff is now in the kernel sources for the 5.x tree. I noticed that the kernel sources weren't updated either, so maybe an update just isn't needed.
      • The kernel sources were updated on 2003-03-09, two days before 4.3.0 hit the ports tree.

        I'm not updating drm-kmod because it's annoying to have these open-source, mit-licensed kernel modules outside of the tree. It means that as the port maintainer I have to apply patches to it every time someone changes the kernel API and all the users have to manually update it. If it's in the tree, there's no synchronization problem (except in DRI CVS).

Slashdot Top Deals

Say "twenty-three-skiddoo" to logout.

Close