O. Hartmann wrote: > vehemens wrote: >> On Wednesday 15 April 2009 07:24:04 am O. Hartmann wrote: >>> Gary Jennejohn wrote: >>>> On Wed, 15 Apr 2009 10:07:59 +0000 >>>> >>>> "O. Hartmann" <ohartman_at_zedat.fu-berlin.de> wrote: >>>>> Gary Jennejohn wrote: >>>>>> On Wed, 15 Apr 2009 06:55:44 +0000 >>>>>> >>>>>> "O. Hartmann" <ohartman_at_zedat.fu-berlin.de> wrote: >>>>>>> Martin wrote: >>>>>>>> Am Tue, 14 Apr 2009 18:08:54 +0200 >>>>>>>> >>>>>>>> schrieb "O. Hartmann" <ohartman_at_mail.zedat.fu-berlin.de>: >>>>>>>>> [...] >>>>>>>> Hi, >>>>>>>> >>>>>>>> if you have problems with the radeonhd driver, you should tell the >>>>>>>> guys who work at it. They are really nice and try to help >>>>>>>> everywhere. >>>>>>>> >>>>>>>> Subscribe there: >>>>>>>> http://lists.opensuse.org/radeonhd/ >>>>>>>> >>>>>>>> I am only using radeonhd, because it works for me on all cards I >>>>>>>> have. >>>>>>>> >>>>>>>> I noticed that window movement may get choppy, when you compile >>>>>>>> a new >>>>>>>> kernel (DRM) and don't recompile a fresh radeonhd driver. This >>>>>>>> happens especially when DRI is enabled for your xorg server. >>>>>>>> >>>>>>>> -- >>>>>>>> Martin >>>>>>> As far as I know, radeonhd from ports doesn't work with DRI >>>>>>> enabled on >>>>>>> FreeBSD - so it doesn't work on my box either. I guess you're >>>>>>> following the recommendations using the development brnach directly >>>>>>> from GIT. >>>>>> Works for me on amd64 8-current. >>>>>> >>>>>> garyj:ernst:~:-bash:4> grep DRI /var/log/Xorg.0.log >>>>>> (II) Loading extension XFree86-DRI >>>>>> (II) Loading extension DRI2 >>>>>> (**) RADEONHD(0): Option "DRI" >>>>>> (II) RADEONHD(0): FB: Allocated DRI Back Buffer at offset 0x024B4000 >>>>>> (size = 0x00B13000) (II) RADEONHD(0): FB: Allocated DRI Depth >>>>>> Buffer at >>>>>> offset 0x02FC7000 (size = 0x00B13000) (II) RADEONHD(0): FB: Allocated >>>>>> DRI Textures at offset 0x03ADA000 (size = 0x0C400000) (II) >>>>>> RADEONHD(0): >>>>>> [DRI] installation complete >>>>>> (II) GLX: Initialized DRISWRAST GL provider for screen 0 >>>>>> garyj:ernst:~:-bash:5> ls -d /var/db/pkg/*radeon* >>>>>> drwxr-xr-x 2 root wheel 512 Apr 14 11:32 >>>>>> /var/db/pkg/xf86-video-radeonhd-devel-1.2.5.20090412 >>>>> Tried radeonhd-devel and failed also! >>>>> >>>>> When enabling DRI in config file, I see the XDM login box and the box >>>>> crashes and freezes immediately. Without DRI radeonhd-devel is >>>>> horrible >>>>> slow when moving windows around - inacceptable. It doesn't matter >>>>> whether EXA is enabled or not and the phenomenon ist the same as with >>>>> the regular radeonhd-driver from xorg-drivers. >>>>> >>>>> I'm back with the VESA driver. >>>> Hmm. Are the drm and radeondrm in your kernel up-to-date? Your >>>> posting >>>> was chopped by the first replier and I can't remember. >>>> >>>> Can't think of anything else. >>>> >>>> I personally don't use xdm/gdm/kdm. I just use startx. >>>> >>>> --- >>>> Gary Jennejohn >>> The kernel modules 'radeon' and 'drm' are loaded via /boot/loader.conf >>> when booting and they are up to date (I do a buildworld on a regular >>> basis these days and it takes ~30 minutes for a quad core box). >>> >>> Even when not starting X via xdm, the box crashes immediately, freezes >>> and is only 'revivable' by cold resetting. This happens with driver >>> radeonhd and enabled DRI. Without DRI the radeonhd driver works, but >>> moving a window looks like on Windooze when using standard VGA driver >>> without acceleration (this is bot with EXA on or off) - scrolling and >>> moving objects is really choppy. >>> >>> 'radeon' doesn't even show up anything, freezes the box as well as >>> 'radeonhd', but no matter whether DRI enabled or not. >>> >>> At home I will test radeonhd-devel with the RV770LE chipset (here I have >>> only RV730). The RV770LE seems not to be recognized by 'radeonhd', but >>> works fine with 'radeon'. But in both cases, DRI enabled crashes the >>> box. >> >> Could you post your xorg.conf? >> >> > > Well, > next round. > > First some notices. All probem occure at the very moment on FreeBSD > 8.0-CURRENT/amd64 due to the fact I do not have any i386 box and I'm not > running any graphical 7.X-based boxes. > > So, here we go. My private box is a UP machine equipted with a RV770LE > based graphicscard (MSI R4830). Yesterday I replaced the 'radeon' driver > from xf86-video-ati with 'radeonhd' from xf86-video-radeonhd-devel (most > recent in ports). Without DRI enabled, this driver is as horrible choppy > as I mentioned before. But with all the DRI and EXA stuff enabled, it is > as fast as the 'radeon' driver, no difference. > > On my lab's box the picture is different. This box is a quadcore Q6600 > based box, P35 chipset (for PCIe-specs), SMP. > This box doesn't work with 'radeon', it crashes immediateley. Using > 'radeonhd', either from xf86-video-radeonhd or xf86-video-radeonhd-devel > leaves my desktop as choppy as unaccelerated. But enabling DRI crahes > the box immediately. > > Attached you'll find my xorg.conf (at the moment with the VESA driver > enabled) and the last Xorg.0.log when the box crashed. It surprises me > that there is no evidence of 'RADEONHD' loaded, only 'VESA'. I hope Xorg > writes a logfile before killing itself. > > A comment to the driver section of my xorg.conf: I also commented out > everything but Options DRI and EXA without success. > > Files named Xorg.log.XXX are older files and results of experiments with > the regular, non-devel-drivers and dated from the 26. March this year, I > put them also into the attachment, for your convenience. > > Regards, > Oliver > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" Please forget about the log file 'Xorg.0.log'. X-server does not write properly a suitable log, so the log is always the last successfully written log. I tried starting X via 'startx', redirecting the log, but whenever the server starts, the box crashes/reboots. Regards, OliverReceived on Thu Apr 16 2009 - 06:57:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:46 UTC