Date: Wed, 18 Jun 2008 16:13:04 +0200 From: "Rene Ladan" <r.c.ladan@gmail.com> To: "Coleman Kane" <cokane@freebsd.org> Cc: x11@freebsd.org, radeonhd@opensuse.org Subject: Re: FreeBSD Port: xf86-video-radeonhd-1.2.1_1 Message-ID: <e890cae60806180713s4a421683p676eae96da197d46@mail.gmail.com> In-Reply-To: <1213646859.2184.11.camel@localhost> References: <1213634501.6012.19.camel@Desktop.kusanagi.fr> <1213641854.2184.2.camel@localhost> <4856BEB9.90303@gmail.com> <1213646859.2184.11.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/6/16 Coleman Kane <cokane@freebsd.org>: > On Mon, 2008-06-16 at 21:27 +0200, Rene Ladan wrote: >> Coleman Kane schreef: >> > On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote: >> >> hello, >> >> >> >> i would like know if a new version of radeonhd port is prevu. >> >> >> >> i read in the xorg wiki that the 3D support for my carte was bear with a >> >> latest version of radeonhd and there dependances. >> >> >> >> i am not enough any experiences in freebsd for modify him self the port. >> >> >> >> i am with freebsd-current and it isn't with the actualy version of >> >> radeonhd. >> >> >> >> i am waiting for install blender for working in my project. >> >> >> >> if not updating this port soon i must try to update him self but i am >> >> not your experience and i was need more time as you to get a fonctionnal >> >> port. >> >> >> >> thanks for your reply. >> >> best regard >> >> jean-christophe. >> > >> > Probably not until they release a new driver. However, I've just been >> > following their git tree directly and that works pretty well for me. >> > >> ( omitting ports@ ) >> >> Works here too, except that I'm now getting a "drmRadeonCmdBuffer: -22" >> message when starting something which uses dri. I have these options in >> my 7.0R box: >> >> device vga >> options VESA >> device agp >> >> and I have drm and radeon loaded as module. Maybe some code is out of sync? >> Maybe that's also the cause of the black window syndrome? >> > Oh, to be fair I've been using the "ati" driver instead of "radeonhd" > for dri lately. I've been using "radeonhd" for 2D-only X sessions (since > the ati driver sucks for 2D only). I cannot get radeonhd to actually do > DRI properly for me (RS690), I just get a black window for glxgears, > etc... > I haven't tried the ati driver (yet), but if dri works with ati but not with radeonhd, then radeonhd is to blame (and not dri/mesa)? Also, I get this in dmesg: vgapci0: <VGA-compatible display> port 0xb000-0xb0ff mem 0xc0000000-0xcfffffff,0xfdff0000-0xfdffffff irq 16 at device 0.0 on pci1 drm0: <ATI Mobility Radeon X1450> on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080528 ... vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ... info: [drm] Setting GART location based on new memory map info: [drm] GART aligned down from 0x00010000 to 0x00000000 info: [drm] Loading RS690 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] error: [drm:pid1212:r300_emit_carefully_checked_packet0] *ERROR* Register 208c failed check as flag=00 error: [drm:pid1212:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet0 failed ... info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] wait idle failed status : 0x90010140 0x00020000 info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] GART aligned down from 0x00010000 to 0x00000000 info: [drm] Loading RS690 Microcode <------ info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] Notice the line with the arrow, I actually have an M64-based card (X1450). Maybe the two error messages are causing the -22 error? The card id is 0x7186:0x1043:0x1231 (Asus A6JE) Xorg.0.log doesn't say anything noticeably wrong about dri. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e890cae60806180713s4a421683p676eae96da197d46>