Bug 3832 - Can't use R128 and Mach64 simultaniously.
Summary: Can't use R128 and Mach64 simultaniously.
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-21 07:28 UTC by Alan Grimes
Modified: 2013-03-15 13:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Grimes 2005-07-21 07:28:57 UTC
Causes dmesg trash too.

I *can* use *either* card alone but not BOTH. 

I think both my r128 and mach64 kernel modules are trying to use /dev/drm/card0
and that is causing confusion. 

there might be an options switch for this somewhere but it's not documented... 

The drm.ko should automaticly assign a unique ./drm/card[N] for each device. 

Secondary to this is that my test application (which I am trying to debug)
displays markedly different color blending charactoristics on the two cards! 

I need to know which behavior is correct! =P 


########################
Adding 1004052k swap on /dev/hda2.  Priority:-1 extents:1
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 19 (level, low) -> IRQ 19
[drm] Initialized drm 1.0.0 20040925
[drm] Initialized r128 2.5.0 20030725 on minor 0: ATI Technologies Inc Rage 128
RF/SG AGP
[drm] Used old pci detect: framebuffer loaded
[drm] Initialized mach64 1.0.0 20020904 on minor 1: ATI Technologies Inc 3D Rage
Pro 215GP
[drm] Used old pci detect: framebuffer loaded
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (8188 buckets, 65504 max) - 220 bytes per conntrack
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. 
http://snowman.net/projects/ipt_recent/
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
agpgart: Putting AGP V2 device at 0000:01:05.0 into 0x mode
[drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held  0
owner 00000000 f52f8240
[drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held  0
owner 00000000 f52f8240
[drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
dmesg.mach64 lines 225-297/297 (END) 
####################
Comment 1 Adam Jackson 2005-10-19 15:09:58 UTC
blaming this on the mach64 drm for now.
Comment 2 chemtech 2013-03-15 13:55:10 UTC
Alan Grimes
Do you still experience this issue with newer drivers ?
Please check the status of your issue.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.