[Bug 2579] Poor FPS ( 200) on Radeon IGP 320M (HP Compaq Presario 900US)
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=2579 --- Additional Comments From [EMAIL PROTECTED] 2005-06-23 01:56 --- I've been insanely busy at work, and I'm sorry that I haven't replied sooner. I actually completely forgot about this bug. I write code all day long, and after staring at Bugzilla all day, it's no wonder my mind has completely forgotten about this other Bugzila. ;-) Anyhow... * Yes, I did verify that DRI is enabled by running glxinfo. * I don't have a drirc anywhere on this machine. * I'm currently running Xorg-6.8.2-r2 from Gentoo (various patches) * The IRQ is being shared, so this will probably be of no interest, but /proc/interrupts looks like the following: CPU0 0: 66703684 XT-PIC timer 1: 15688 XT-PIC i8042 2: 0 XT-PIC cascade 5: 17172 XT-PIC ALI 5451 7: 2 XT-PIC parport0 9: 6400 XT-PIC acpi 10: 851868 XT-PIC yenta, ath0, [EMAIL PROTECTED]::01:05.0 11: 607583 XT-PIC ohci_hcd, ohci_hcd 12: 63963 XT-PIC i8042 14: 138268 XT-PIC ide0 15: 396289 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0 MIS: 0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r300 bsd drm?
Jung-uk Kim wrote: On Wednesday 22 June 2005 06:55 pm, Adam K Kirchhoff wrote: At one point in the not-too-distant past, the r300 drm would compile on FreeBSD 5.4. After bringing a Radeon 9550 home from work to test out and being really impressed with how well the driver works (without those pesky 9800 specific lockups), I decided to give it a whirl in FreeBSD. Unfortunately, the drm module wouldn't compile: c -O -pipe -I. -I.. -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I.. -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_set_pciegart': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:1246: warning: unsigned int format, dma_addr_t arg (arg 5) /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_do_init_cp': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:1533: error: too many arguments to function `drm_ati_pcigart_init' /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_preinit': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:2087: warning: implicit declaration of function `drm_device_is_pcie' /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:2087: warning: nested extern declaration of `drm_device_is_pcie' *** Error code 1 Any ideas? Recent preliminary PCI-Express support code commit broke *BSD. I have a quick-and-dirty fix for this. If you are interested, let me know. Jung-uk Kim Definitely pass it along when you a chance :-) Thanks! Adam --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3609] New: via drm module not always works with 2.6.12 kernel
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=3609 Summary: via drm module not always works with 2.6.12 kernel Product: DRI Version: DRI CVS Platform: PC URL: http://sourceforge.net/mailarchive/message.php?msg_id=12 141672 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: DRM modules AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] In many (not all) cases module has been found not to work properly with 2.6.12 kernel, producing output: [ cut here ] kernel BUG at include/linux/dcache.h:294! invalid operand: [#1] PREEMPT Modules linked in: via drm nsc_ircc snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq parport_pc parport psmouse pcspkr snd_via82xx gameport snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd via_ircc irda acerhk amd64_agp agpgart eth1394 sata_via sata_svw libata sbp2 ohci1394 ieee1394 usb_storage usbhid CPU:0 EIP:0060:[c019d25c]Not tainted VLI EFLAGS: 00213246 (2.6.12-gentoo) EIP is at sysfs_remove_dir+0xfc/0x110 eax: ebx: db5aaf30 ecx: edx: ddf6f280 esi: db5aa800 edi: db891d14 ebp: dc5c16c0 esp: dac0de94 ds: 007b es: 007b ss: 0068 Process X (pid: 12235, threadinfo=dac0c000 task=db1835a0) Stack: dc62c9c0 dce3783a c04faea0 db5aaf30 db5aa800 dc62c940 dc5c16c0 c0300670 db5aaf30 db5aaf30 c03006a0 db5aaf30 0002 dc62cb20 df03d72d db5aaf30 dbb71380 df03e3a8 00203282 dac0c000 db5aa800 ddf64c80 Call Trace: [c0300670] kobject_del+0x10/0x20 [c03006a0] kobject_unregister+0x20/0x30 [df03d72d] drm_takedown+0x34d/0x3f0 [drm] [df03e3a8] drm_fasync+0x48/0x90 [drm] [df03e7c5] drm_release+0x3d5/0x540 [drm] [df03d950] drm_version+0x0/0xa0 [drm] [df03dbb3] drm_ioctl+0x1c3/0x23c [drm] [c0246400] udf_create+0x30/0x1b0 [df03d950] drm_version+0x0/0xa0 [drm] [c0246400] udf_create+0x30/0x1b0 [c0172cb7] do_ioctl+0x77/0xb0 [c015f58a] __fput+0x16a/0x1b0 [c015d942] filp_close+0x52/0xa0 [c015d9e8] sys_close+0x58/0xa0 [c010325b] sysenter_past_esp+0x54/0x75 Code: 89 44 24 08 8b 00 89 04 24 e8 c1 a9 fa ff 8b 54 24 08 8b 42 04 89 04 24 e8 32 35 16 00 8b 44 24 08 89 04 24 e8 a6 a9 fa ff eb 93 0f 0b 26 01 a2 94 49 c0 e9 17 ff ff ff 8d b4 26 00 00 00 00 83 In most cases where error occures X does not start, in my case on Xorg exit i get blank screen, when looking at dmesg through ssh i se the above. My configuration: Linux gentoo, Acer Aspire 1362 laptop, k8n800 chipset (using snapshot unichrome driver from http://myth.ivor.org , cvs drm module from dri cvs), kernel 2.6.12 (with 2.6.11 it worked fine, gentoo-sources), Xorg 6.8.2 (6.8.2-r2 ebuild). AMD Mobile Sempron 2800+. On request I can send my kernel configuration. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Best way to update for support of Intel 915GM
On 6/23/05, Craig Sylla [EMAIL PROTECTED] wrote: Hi - What is the best way to get all the available 3d support for the 915GM? http://dri.freedesktop.org/wiki/Building Using: FC2/2.6.5, X.org 6.8.2, with a fixed i810 driver from Alan, and the Intel driver package from January (which has the agpgart and intel-agp .ko's in it that contain the critical PCI Id's). I need to build the X driver from source because I have to use an antique version of GCC for the X server (2.96). The kernel is built using GCC 3.3.3 as are all of the kernel .ko's. Also, I would like to run in Dual-Head (two independent screens, no Xinerama) w/out a window manager (Gnome, KDE, TVM) - will that work? it should work, although dualhead on the intel hardware can be troublesome at times. Alex Thanks much - Craig --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
sysfs_remove_dir bug?
From bug 3609: I don't think this is via specific. Anybody that has a clue? kernel BUG at include/linux/dcache.h:294! invalid operand: [#1] PREEMPT Modules linked in: via drm nsc_ircc snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq parport_pc parport psmouse pcspkr snd_via82xx gameport snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd via_ircc irda acerhk amd64_agp agpgart eth1394 sata_via sata_svw libata sbp2 ohci1394 ieee1394 usb_storage usbhid CPU:0 EIP:0060:[c019d25c]Not tainted VLI EFLAGS: 00213246 (2.6.12-gentoo) EIP is at sysfs_remove_dir+0xfc/0x110 eax: ebx: db5aaf30 ecx: edx: ddf6f280 esi: db5aa800 edi: db891d14 ebp: dc5c16c0 esp: dac0de94 ds: 007b es: 007b ss: 0068 Process X (pid: 12235, threadinfo=dac0c000 task=db1835a0) Stack: dc62c9c0 dce3783a c04faea0 db5aaf30 db5aa800 dc62c940 dc5c16c0 c0300670 db5aaf30 db5aaf30 c03006a0 db5aaf30 0002 dc62cb20 df03d72d db5aaf30 dbb71380 df03e3a8 00203282 dac0c000 db5aa800 ddf64c80 Call Trace: [c0300670] kobject_del+0x10/0x20 [c03006a0] kobject_unregister+0x20/0x30 [df03d72d] drm_takedown+0x34d/0x3f0 [drm] [df03e3a8] drm_fasync+0x48/0x90 [drm] [df03e7c5] drm_release+0x3d5/0x540 [drm] [df03d950] drm_version+0x0/0xa0 [drm] [df03dbb3] drm_ioctl+0x1c3/0x23c [drm] [c0246400] udf_create+0x30/0x1b0 [df03d950] drm_version+0x0/0xa0 [drm] [c0246400] udf_create+0x30/0x1b0 [c0172cb7] do_ioctl+0x77/0xb0 [c015f58a] __fput+0x16a/0x1b0 [c015d942] filp_close+0x52/0xa0 [c015d9e8] sys_close+0x58/0xa0 [c010325b] sysenter_past_esp+0x54/0x75 Code: 89 44 24 08 8b 00 89 04 24 e8 c1 a9 fa ff 8b 54 24 08 8b 42 04 89 04 24 e8 32 35 16 00 8b 44 24 08 89 04 24 e8 a6 a9 fa ff eb 93 0f 0b 26 01 a2 94 49 c0 e9 17 ff ff ff 8d b4 26 00 00 00 00 83 /Thomas --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: sysfs_remove_dir bug?
Something in CVS is corrupting memory and causing various failures. My suspicion it is related to the power management code but I haven't been able to track it down. It is possible that this is related. On 6/23/05, Thomas Hellström [EMAIL PROTECTED] wrote: From bug 3609: I don't think this is via specific. Anybody that has a clue? kernel BUG at include/linux/dcache.h:294! invalid operand: [#1] PREEMPT Modules linked in: via drm nsc_ircc snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq parport_pc parport psmouse pcspkr snd_via82xx gameport snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd via_ircc irda acerhk amd64_agp agpgart eth1394 sata_via sata_svw libata sbp2 ohci1394 ieee1394 usb_storage usbhid CPU:0 EIP:0060:[c019d25c]Not tainted VLI EFLAGS: 00213246 (2.6.12-gentoo) EIP is at sysfs_remove_dir+0xfc/0x110 eax: ebx: db5aaf30 ecx: edx: ddf6f280 esi: db5aa800 edi: db891d14 ebp: dc5c16c0 esp: dac0de94 ds: 007b es: 007b ss: 0068 Process X (pid: 12235, threadinfo=dac0c000 task=db1835a0) Stack: dc62c9c0 dce3783a c04faea0 db5aaf30 db5aa800 dc62c940 dc5c16c0 c0300670 db5aaf30 db5aaf30 c03006a0 db5aaf30 0002 dc62cb20 df03d72d db5aaf30 dbb71380 df03e3a8 00203282 dac0c000 db5aa800 ddf64c80 Call Trace: [c0300670] kobject_del+0x10/0x20 [c03006a0] kobject_unregister+0x20/0x30 [df03d72d] drm_takedown+0x34d/0x3f0 [drm] [df03e3a8] drm_fasync+0x48/0x90 [drm] [df03e7c5] drm_release+0x3d5/0x540 [drm] [df03d950] drm_version+0x0/0xa0 [drm] [df03dbb3] drm_ioctl+0x1c3/0x23c [drm] [c0246400] udf_create+0x30/0x1b0 [df03d950] drm_version+0x0/0xa0 [drm] [c0246400] udf_create+0x30/0x1b0 [c0172cb7] do_ioctl+0x77/0xb0 [c015f58a] __fput+0x16a/0x1b0 [c015d942] filp_close+0x52/0xa0 [c015d9e8] sys_close+0x58/0xa0 [c010325b] sysenter_past_esp+0x54/0x75 Code: 89 44 24 08 8b 00 89 04 24 e8 c1 a9 fa ff 8b 54 24 08 8b 42 04 89 04 24 e8 32 35 16 00 8b 44 24 08 89 04 24 e8 a6 a9 fa ff eb 93 0f 0b 26 01 a2 94 49 c0 e9 17 ff ff ff 8d b4 26 00 00 00 00 83 /Thomas --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- Jon Smirl [EMAIL PROTECTED] --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r300 bsd drm?
On Thursday 23 June 2005 08:17 am, Adam K Kirchhoff wrote: Jung-uk Kim wrote: On Wednesday 22 June 2005 06:55 pm, Adam K Kirchhoff wrote: At one point in the not-too-distant past, the r300 drm would compile on FreeBSD 5.4. After bringing a Radeon 9550 home from work to test out and being really impressed with how well the driver works (without those pesky 9800 specific lockups), I decided to give it a whirl in FreeBSD. Unfortunately, the drm module wouldn't compile: c -O -pipe -I. -I.. -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I.. -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_set_pciegart': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:1246: warning: unsigned int format, dma_addr_t arg (arg 5) /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_do_init_cp': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:1533: error: too many arguments to function `drm_ati_pcigart_init' /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c: In function `radeon_preinit': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:2087: warning: implicit declaration of function `drm_device_is_pcie' /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_cp.c:2087: warning: nested extern declaration of `drm_device_is_pcie' *** Error code 1 Any ideas? Recent preliminary PCI-Express support code commit broke *BSD. I have a quick-and-dirty fix for this. If you are interested, let me know. Jung-uk Kim Definitely pass it along when you a chance :-) Thanks! FreeBSD build fix is committed. Cheers, Jung-uk Kim Adam --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: sysfs_remove_dir bug?
Someone has logged a bug (#3549) that might be the cause. I've just not had time to investigate this yet. If no-one beats me to it, I'll take a look early next week. Alan. On Thu, Jun 23, 2005 at 04:45:48PM -0400, Jon Smirl wrote: Something in CVS is corrupting memory and causing various failures. My suspicion it is related to the power management code but I haven't been able to track it down. It is possible that this is related. On 6/23/05, Thomas Hellström [EMAIL PROTECTED] wrote: From bug 3609: I don't think this is via specific. Anybody that has a clue? kernel BUG at include/linux/dcache.h:294! invalid operand: [#1] PREEMPT Modules linked in: via drm nsc_ircc snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq parport_pc parport psmouse pcspkr snd_via82xx gameport snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd via_ircc irda acerhk amd64_agp agpgart eth1394 sata_via sata_svw libata sbp2 ohci1394 ieee1394 usb_storage usbhid CPU:0 EIP:0060:[c019d25c]Not tainted VLI EFLAGS: 00213246 (2.6.12-gentoo) EIP is at sysfs_remove_dir+0xfc/0x110 eax: ebx: db5aaf30 ecx: edx: ddf6f280 esi: db5aa800 edi: db891d14 ebp: dc5c16c0 esp: dac0de94 ds: 007b es: 007b ss: 0068 Process X (pid: 12235, threadinfo=dac0c000 task=db1835a0) Stack: dc62c9c0 dce3783a c04faea0 db5aaf30 db5aa800 dc62c940 dc5c16c0 c0300670 db5aaf30 db5aaf30 c03006a0 db5aaf30 0002 dc62cb20 df03d72d db5aaf30 dbb71380 df03e3a8 00203282 dac0c000 db5aa800 ddf64c80 Call Trace: [c0300670] kobject_del+0x10/0x20 [c03006a0] kobject_unregister+0x20/0x30 [df03d72d] drm_takedown+0x34d/0x3f0 [drm] [df03e3a8] drm_fasync+0x48/0x90 [drm] [df03e7c5] drm_release+0x3d5/0x540 [drm] [df03d950] drm_version+0x0/0xa0 [drm] [df03dbb3] drm_ioctl+0x1c3/0x23c [drm] [c0246400] udf_create+0x30/0x1b0 [df03d950] drm_version+0x0/0xa0 [drm] [c0246400] udf_create+0x30/0x1b0 [c0172cb7] do_ioctl+0x77/0xb0 [c015f58a] __fput+0x16a/0x1b0 [c015d942] filp_close+0x52/0xa0 [c015d9e8] sys_close+0x58/0xa0 [c010325b] sysenter_past_esp+0x54/0x75 Code: 89 44 24 08 8b 00 89 04 24 e8 c1 a9 fa ff 8b 54 24 08 8b 42 04 89 04 24 e8 32 35 16 00 8b 44 24 08 89 04 24 e8 a6 a9 fa ff eb 93 0f 0b 26 01 a2 94 49 c0 e9 17 ff ff ff 8d b4 26 00 00 00 00 83 /Thomas --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- Jon Smirl [EMAIL PROTECTED] --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 2754] ATI Technologies Inc Radeon Mobility M6 LY in DRM/DRI mode locks up if CPU frequency changes on battery power
http://bugzilla.kernel.org/show_bug.cgi?id=2754 --- Additional Comments From [EMAIL PROTECTED] 2005-06-23 15:30 --- I have the exact same problem with DRI/DRM enabled, the video in AGP mode and cpufreq changing cpu clock speeds. Everything runs fine so long as the cpu frequency stays at one setting. Setup: HP Omnibook xt6200 Gentoo Linux 2005.x Kernel: 2.6.11-gentoo-r11 CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz (It has the same low clock speed of 1.2GHz when in low power mode.) --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: ioctl32 support
Bernardo Innocenti wrote:
Now libGL works, but something else fails and 32bit
clients fall back to indirect rendering:
After digging around with GDB, I can now elaborate a
bit more.
The call to drmMap() fails because it attempts to
map 0 bytes of memory. We're in r300/radeon_screen.c:radeonCreateScreen():
screen-mmio.handle = dri_priv-registerHandle;
screen-mmio.size = dri_priv-registerSize;
if (drmMap(sPriv-fd,
screen-mmio.handle, screen-mmio.size, screen-mmio.map)) {
dri_priv points to a RADEONInfoRec, which is filled
in by the server side in XF86DRIGetDeviceInfo().
The contents seem to be borked, perhaps because many
fields arn't the same size in the 64bit server side.
The full contents are:
deviceID = 16723,
width = 1400,
height = 1050,
depth = 24,
bpp = 32,
IsPCI = 0,
AGPMode = 8,
frontOffset = 0,
frontPitch = 1408,
backOffset = 23789568,
backPitch = 1408,
depthOffset = 29704192,
depthPitch = 1408,
textureOffset = 35651584,
textureSize = 98566144,
log2TexGran = 21,
registerHandle = 4225761280,
registerSize = 0,
statusHandle = 524288,
statusSize = 0,
gartTexHandle = 378144,
gartTexMapSize = 0,
log2GARTTexGran = 4096,
textureSize = 98566144,
log2TexGran = 21,
registerHandle = 4225761280,
registerSize = 0,
statusHandle = 524288,
statusSize = 0,
gartTexHandle = 378144,
gartTexMapSize = 0,
log2GARTTexGran = 4096,
gartTexOffset = 0,
sarea_priv_offset = 3224379392
Which is perhaps more readable in hex:
deviceID = 0x4153,
width = 0x578,
height = 0x41a,
depth = 0x18,
bpp = 0x20,
IsPCI = 0x0,
AGPMode = 0x8,
frontOffset = 0x0,
frontPitch = 0x580,
backOffset = 0x16b,
backPitch = 0x580,
depthOffset = 0x1c54000,
depthPitch = 0x580,
textureOffset = 0x220,
textureSize = 0x5e0,
log2TexGran = 0x15,
registerHandle = 0xfbe0,
registerSize = 0x0,
statusHandle = 0x8,
statusSize = 0x0,
gartTexHandle = 0xc0101000,
gartTexMapSize = 0x0,
log2GARTTexGran = 0x1000,
textureSize = 0x5e0,
log2TexGran = 0x15,
registerHandle = 0xfbe0,
registerSize = 0x0,
statusHandle = 0x8,
statusSize = 0x0,
gartTexHandle = 0xc0101000,
gartTexMapSize = 0x0,
log2GARTTexGran = 0x1000,
gartTexOffset = 0x0,
sarea_priv_offset = 0xc0302000
Maybe the fields of RADEONInfoRec should be reworked
to use types with a predefined size. Is that right?
--
// Bernardo Innocenti - Develer S.r.l., RD dept.
\X/ http://www.develer.com/
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
