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: Torfinn Ingolfsen on 21 Mar 2010 08:34 Hi, On Sun, Mar 21, 2010 at 12:36 PM, Garrett Cooper <yanefbsd(a)gmail.com> wrote: > > XFCE4 installs files in ~/.config/xfce4 . You also may need to > clean out .gconf* . > I cleaned out tht one, ~/.gconf was clean, I cleaned ~/.gconfd, I stopped dbus and cleaned ~/.dbus/session-bus too. Nothing helped. -- 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: Gary Jennejohn on 21 Mar 2010 09:32 On Sun, 21 Mar 2010 13:27:27 +0100 Torfinn Ingolfsen <tingox(a)gmail.com> wrote: > Hi, > > On Sun, Mar 21, 2010 at 11:14 AM, Gary Jennejohn > <gary.jennejohn(a)freenet.de>wrote: > > > > > Interesting solution. > > > > Just for kicks I installed xfce4-session and ran it. It doesn't require > > the rest of xfce4 to run. > > > > Unfortunately, it worked for me without any error. It even started the > > sessions I had saved from the time when I was using xfce4. > > > > Have you tried deleteing .xfce4, Torfinn? > > > > > Yep, tried that too. For the user 'root' there wasn't a ~/.config/xfce4 > directory before I started testing. > > > > Another point which I should mention is that I did a completely clean > > install of all my ports when I updated to Xorg 7.5. This guarantees that > > there isn't any random junk left around. > > > > I did portupgrade all ports, and have checked the dates in /var/db/pkg - all > ports are updated after the installation of Xorg 7.5 > Well, I completely nuked /usr/local and /var/db/pkg before doing the installation. I may be paranoid, but I don't trust the various ports management tools to do a good job on complex updates. Just old fashioned, I guess. I'm out of ideas. -- 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: Robert Noland on 21 Mar 2010 09:47 On Sun, 2010-03-21 at 03:06 -0700, Garrett Cooper wrote: > On Sun, Mar 21, 2010 at 2:42 AM, jhell <jhell(a)dataix.net> wrote: > > > > 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. > > Intel's killing off non-GEM support slowly and surely, so we have > to port GEM or die a slow and painful death on Intel accelerated > hardware: http://www.phoronix.com/scan.php?page=news_item&px=Njc2NA , > http://software.intel.com/sites/oss/project_spotlight.htm . Kind of > sad now that anholt is no longer really a contributing member to > FreeBSD. Yes, the 2.8+ driver requires GEM for drm and the 2.10+ driver requires KMS. They keep removing code and making it that much more difficult to keep things going. The situation that I generally find myself in, is that in order to give radeon users newer/better code, I have to break Intel. Intel tends to take up an unreasonable amount of time for me to keep it functional. robert. > Thanks, > -Garrett -- Robert Noland <rnoland(a)FreeBSD.org> FreeBSD _______________________________________________ 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: Robert Noland on 21 Mar 2010 10:00 On Sat, 2010-03-20 at 18:47 +0100, Torfinn Ingolfsen 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. You said that X also crashes when this happens, correct? If so, rebuild xorg-server with -DWITH_DEBUG. ssh into the machine and "gdb startx -- :0", or If you can get X running before starting xfce4-session, just attach gdb to the running Xorg server. You must do this from a second machine or you will just lock everything up. When the server exits, your screen will freeze and you will be able to get a backtrace from gdb. Then just hit 'c' in gdb and it will finish aborting and restart or exit... robert. -- Robert Noland <rnoland(a)FreeBSD.org> FreeBSD _______________________________________________ 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 21 Mar 2010 10:47
Hi, On Sun, Mar 21, 2010 at 3:00 PM, Robert Noland <rnoland(a)freebsd.org> wrote: > > You said that X also crashes when this happens, correct? There is no indication that X crashes (no core dump, nothing in /var/log/messages, no messages on the console that it is started from) , for all I know it could just be told to quit. > If so, rebuild > xorg-server with -DWITH_DEBUG. ssh into the machine and "gdb startx > -- :0", or If you can get X running before starting xfce4-session, just > attach gdb to the running Xorg server. You must do this from a second > machine or you will just lock everything up. When the server exits, > your screen will freeze and you will be able to get a backtrace from > gdb. Then just hit 'c' in gdb and it will finish aborting and restart > or exit... > > However, you suggestion above just gave me an idea: 1) I start X with 'startx' as root 2) From a xterm I start 'xfce4-session'' xfce4-session started xfce4-panel, xfdesktop and the "tips and tricks" window. And then it crashed and core dumped. How weird. But the other xfce programs are still running. In the xterm that I started xfce4-session from, I see this text: (xfce4-settings-helper:20823): libxfcegui4-WARNING **: ICE I/O Error (xfce4-settings-helper:20823): libxfcegui4-WARNING **: Disconnected from session manager. Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property'GtkOptionMenu::indicator-size' of type 'GtkRequistion' from rc file value "0" of type 'glong' (xfce4-settings-helper:20805): libxfcegui4-WARNING **: ICE I/O Error (xfce4-settings-helper:20805): libxfcegui4-WARNING **: Disconnected from session manager. (xfce4-settings-helper:20810): libxfcegui4-WARNING **: ICE I/O Error (xfce4-settings-helper:20810): libxfcegui4-WARNING **: Disconnected from session manager. Process 20823 is xfce4-settings-helper, 20805 is xfce4-panel and 20810 is xfdesktop. In case this helps. -- 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" |