mac_vanyone know if there is a bug regarding segfaults or X crashes with ntfs partitions , when viewing image or video files05:31
mac_vI'm facing crashes , with the karmic packages in ATI...05:32
hyperairsay, what libraries do i need for direct rendering to work with 32-bit programs on x64?09:53
jcristauand a dri driver09:56
hyperairjcristau: alright, i'll go break an x86 deb out for testing then.11:30
tjaaltonhyperair: ia32-libs isn't enough?11:33
hyperairtjaalton: wine's segfaulting.11:33
hyperair18:06:45 <stringfellow> the segfault is caused by http://bugs.freedesktop.org/show_bug.cgi?id=23335, but you really don't want to use indirect rendering in11:33
ubottuFreedesktop bug 23335 in Drivers/DRI/i965 "[wine] Mesa returns invalid framebuffer status" [Normal,Assigned]11:33
hyperairi submitted a patch upstream to wine to do a null pointer check11:34
hyperairbut that doesn't solve the lesser problem that is not having dri11:34
hyperairtrace:wgl:X11DRV_WineGL_InitOpenglInfo Direct rendering enabled: False11:46
hyperairit still doesn't work.11:46
* hyperair scratches head11:46
hyperairtjaalton: okay, it's not my fault, and it's not the fault of mismatched libraries either12:06
hyperairlibGL error: dlopen /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: wrong ELF class: ELFCLASS64)12:06
hyperairlibGL error: unable to load driver: i965_dri.so12:06
hyperairlibGL error: driver pointer missing12:06
* hyperair groan12:06
hyperairia32-libs is broken.12:06
mtcin karmic, I see xserver-xorg-video-radeon an ubuntu core-developers maintained package, and used by default, whereas xserver-xorg-video-radeonhd is community maintained12:22
mtcmy understanding is that the radeonhd driver will be a better the better driver for the modern AMD-ATI graphic cards (R500 / R600)12:24
mtcany insights why radeonhd was not chosen to be used by default?  seems a shame not to use a driver with the advanced features, especially as new users are immediately prompted to use the binary-only fglrx at their first login.12:29
tjaaltonmtc: -radeon supports more cnips12:33
tjaaltonolder ones too12:34
mtcsure that is true, but there are many other xorg drivers that support only a few cards12:34
tjaaltonand it's maintained by ati, and -radeonhd is mainly a suse project12:34
mtcshoot, when was the last time you saw a 3dfx Voodoo graphics card, and that is a ubuntu developer maintained xorg driver package12:37
tjaaltonwhy is that relevant?12:38
mtcyou had said the -radeonhd was more card specific than the -radeon driver12:38
tjaaltonr3xx isn't uncommon12:39
mvomtc: there is a wiki page at xorg  http://wiki.x.org/wiki/RadeonFeature that shows the support for the chips side-by-side12:39
mvo(RHD is the column for the radeonhd)12:40
mtcam pointing out that there are other drivers that are specific, which are still ubuntu developer maintained, and the voodoo are less common than the radeon R500 and R600 chipsets12:40
mvothat indicates that -ati covers the same HW as -radeonhd, sometimes even more complete12:40
tjaaltonmtc: I already explained why -ati/radeon is the chosen one12:41
mtcmvo - interesting - I had not looked at that feature chart in a while, indeed the -radeon driver appears more complete12:41
mvomtc: -ati did a big leap forward whenthe atombios docs got released IIRC 12:42
tjaaltonthere are too many drivers anyway, no point in following one that's more or less created for political reason12:42
* mvo should point out that he is not a expert in this area though12:42
mtcmy understanding is the -radeon driver would not have the R500 / R600 chipset features, but that feature chart seems to indicate otherwise12:43
tjaaltonbut it's there for people to use if they like12:43
tjaaltonlike I said12:43
tjaaltonit supports all the chips that are released12:43
tjaaltonat least in git12:43
mtcwell, nice to see the radeon drivers better supported in karmic... thanks for your thoughts on the subject of radeonhd13:16
mtclooks like there is an issue with DRI however - the Xorg log shows an error due to /usr/lib/dri/r600_dri.so file being missing13:17
tjaaltonthe newer ones don't have accelerated 3d-support yet13:19
tjaaltonmeaning r6xx ->13:19
mtctjaalton: where do those dri libraries come from?  who can I expect to see a release of r600_dri.so ?13:35
mtctjaalton: nevermind, found more information at freedesktop.org13:37
tseliotI disabled the r600 3d driver because it wasn't mature enough and it required a kernel patch which didn't make it on time. It should be ok in Lucid13:37
mtcthanks for your insights13:39
jbarneswow karmic shuts down fast21:54
jbarnesso nice21:54
bryce__jbarnes, :-)22:05
tormodyeah I am not at all impressed by boot speed (I have a "normal" HD") but the shutdown kicks ass22:52
tormodalmost like MacOS9 :)22:52
tormodalbert23, your -intel crash fix (good job!) is now in jaunty xorg-edgers22:55
albert23tormod: I thought jaunty didn't have the crash?22:56
tormodalbert23, I think I saw some jaunty reports, I was hoping it was this :)22:57
albert23tormod: it was straight 2.9.0 in jaunty before?22:58
tormodalbert23, no it was the karmic one backported, so straight + one patch22:59
tormodalbert23, I got some reports in private email on -intel crashing since a recent mesa update22:59
albert23Yeah, the mesa crash I have seen23:00
albert23tormod: I thought the crash was introduced in "uxa: Refactor create Picture for pixman format"23:01
tormodand there was someone on phoronix with a crash also23:01
tormodI told them to file bugs, I didn't look into it23:01
* albert23 still thinks that crash was not in 2.9.0 Karmic is safe :-)23:13

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!