X.org 7.5 for FreeBSD
in [Ports]
|
Prev: xanim: Undefined symbol "__sF" on FreeBSD 8.0
Next: xf86-video-radeonhd: incorrect libpci dependency?
From: Gary Jennejohn on 20 Mar 2010 11:12 On Sat, 20 Mar 2010 08:54:28 -0400 Jerry <gesbbb(a)yahoo.com> wrote: > On Sat, 20 Mar 2010 13:26:03 +0100 > Gary Jennejohn <gary.jennejohn(a)freenet.de> articulated: > > >Of course, this is just a hack and doesn't fix the real problem and > >we're probably all getting tired of this thread :) > > Not half as tired as you will be if this port is officially released > and it breaks someone's system. If it comes down to fix it now or fix it > later, which do you think would be the more beneficial scenario? > Fix it now, of course. But right now it isn't even clear what the cause of the problem is, so a real fix isn't possible. --- Gary Jennejohn _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Jerry on 20 Mar 2010 12:06 On Sat, 20 Mar 2010 16:12:43 +0100 Gary Jennejohn <gary.jennejohn(a)freenet.de> articulated: >On Sat, 20 Mar 2010 08:54:28 -0400 >Jerry <gesbbb(a)yahoo.com> wrote: > >> On Sat, 20 Mar 2010 13:26:03 +0100 >> Gary Jennejohn <gary.jennejohn(a)freenet.de> articulated: >> >> >Of course, this is just a hack and doesn't fix the real problem and >> >we're probably all getting tired of this thread :) >> >> Not half as tired as you will be if this port is officially released >> and it breaks someone's system. If it comes down to fix it now or >> fix it later, which do you think would be the more beneficial >> scenario? >> > >Fix it now, of course. But right now it isn't even clear what the >cause of the problem is, so a real fix isn't possible. > >--- >Gary Jennejohn A real fix is possible, although it is true that the first order of business is to discover what is causing the problem. Discontinuing one threat and starting another that deals with the same problem hardly seems productive. However, it makes no discernible difference to me. By the way Gary, your "sig delimiter" is broken. -- Jerry gesbbb(a)yahoo.com Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The bland leadeth the bland and they both shall fall into the kitsch. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Torfinn Ingolfsen on 20 Mar 2010 13:47 Update On Sat, Mar 20, 2010 at 1:26 PM, Gary Jennejohn <gary.jennejohn(a)freenet.de>wrote: > > Well, I don't know whether this is really relevant, but I noticed that > xfce4-session actually depends on dbus-glib and not dbus. It might be > necessary to reinstall dbus-glib with DBUS_DISABLE_CHECKS set. > > This is easily done by modifying devel/dbus-glib/Makefile to set > --enable-checks=no at line 320. > Ok, I tried that too. Sadly, it had no effect. xfce4-session core dumps as before with this option set for dbus-glib. Yes, I restarted dbus after reinstalling this port. > Of course, this is just a hack and doesn't fix the real problem and we're > probably all getting tired of this thread :) > Possibly, but I'm willing to try a few suggestions more. It would be nice if it worked. -- Regards, Torfinn Ingolfsen _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Jeremy Messenger" on 20 Mar 2010 14:45 On Sat, 20 Mar 2010 11:47:22 -0600, Torfinn Ingolfsen <tingox(a)gmail.com> wrote: > Update > > On Sat, Mar 20, 2010 at 1:26 PM, Gary Jennejohn > <gary.jennejohn(a)freenet.de>wrote: > >> >> Well, I don't know whether this is really relevant, but I noticed that >> xfce4-session actually depends on dbus-glib and not dbus. It might be >> necessary to reinstall dbus-glib with DBUS_DISABLE_CHECKS set. >> >> This is easily done by modifying devel/dbus-glib/Makefile to set >> --enable-checks=no at line 320. >> > > Ok, I tried that too. Sadly, it had no effect. xfce4-session core dumps > as > before with this option set for dbus-glib. Yes, I restarted dbus after > reinstalling this port. > > >> Of course, this is just a hack and doesn't fix the real problem and >> we're >> probably all getting tired of this thread :) >> > > Possibly, but I'm willing to try a few suggestions more. > It would be nice if it worked. Looks like it's a known issue in the Linux world too. http://bugzilla.xfce.org/show_bug.cgi?id=5966 Try to change the theme to default. Cheers, Mezz -- mezz7(a)cox.net - mezz(a)FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome(a)FreeBSD.org _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: jhell on 21 Mar 2010 05:42
On Sun, 14 Mar 2010 23:57, Robert Noland wrote: In Message-Id: <1268625423.2608.348.camel(a)balrog.2hip.net> > On Sun, 2010-03-14 at 15:02 -0600, Warren Block wrote: >> On Sat, 13 Mar 2010, Robert Noland wrote: >> >>> Ok, now that agp seems to be working... I have created a port for the >>> 2.9.1 version of the Intel driver. You will need to uninstall the >>> existing intel driver and install this one. You still won't have drm, >>> but should be a good bit better than vesa... >>> >>> http://people.freebsd.org/~rnoland/xf86-video-intel29.tar.gz >> >> Problem: after switching away from X with ctrl-alt-f4, on switching back >> the screen is corrupted. Stuff that's drawn on top of it after that >> point is usually correct. The clear areas on this image were caused by >> GIMP redrawing them; before opening it, they were the same as the strip >> on the right edge. > > Ok, I'm not surprised... I spent a little time playing with the 2.9.1 > driver on my g45 today. Basically... It is horrid... > Damn! I rely on this driver for my main machine that has a i845G in it. This thing tends to keep getting more shitty with every release. Or I suppose I could cough it up to ancient hardware to... ;) The last Intel driver I remember working seamlessly with my i845G with no known side effects and without HAL was 2.3*. After that it somehow became very dependent on HAL and if compiled without HAL would pretty much disable you(being me) from switching from X to the console and back again resulting in a reboot after a borked screen. Now that I see the following I sort of understand whats happening with this. And eventually this hardware will have to be replaced :( > When Intel chose to remove all non-GEM support for the 2.8 series > driver, what is actually going on is that it is calling into > libdrm_intel's fake buffer manager and doing ton's of memcpy's. It > seems to be sort of ok as long as it is just basic 2d, but enable > composite in metacity and it falls on it's face... Granted all of my > machines run with WITNESS and INVARIANTS, but you can almost count the > pixels as they are drawn... > > I was thinking that Intel had actually killed the fake buffer manager as > well, but it looks like it does still exist in libdrm git. Perhaps it > was that they removed it from mesa. At any rate, they don't deny that > it is broken, nor do they test it or have any intention of fixing it... > > The only reason for using the 2.9.1 driver that I can think of is if you > have an Ironlake chipset, which isn't supported in 2.7.1. I now have to > decide whether to spend time back porting Ironlake support to 2.7.1 or > spend time on GEM. > > robert. > >> http://www.wonkity.com/~wblock/xorg7.5/grab.png >> >> -Warren Block * Rapid City, South Dakota USA >> _______________________________________________ >> freebsd-ports(a)freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" > Regards, -- jhell _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |