0x9480:0x103C:0x3061: ATI Technologies Inc M96 [Mobility Radeon HD 4650]
Hi, Sorry for not using word-wrap - so that the logs don't look messed up. I recently bought an HP Pavilion dv6 series laptop which comes with Mobility Radeon HD 4650 graphics chip with 1GB GDD3 VRAM. It seems to be common with the dv6 series laptops from HP. The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about: 1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used. The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM. 2. I tried to use KMS which is recently introduced - just for testing what it's all about. The kernel logs have following lines when trying to enable KMS: Nov 2 00:52:42 plutonium kernel: [ 499.645739] [drm] Module unloaded Nov 2 00:53:03 plutonium kernel: [ 519.771264] [drm] radeon kernel modesetting enabled. Nov 2 00:53:03 plutonium kernel: [ 519.771264] radeon 0000:01:00.0: setting latency timer to 64 Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm] radeon: Initializing kernel modesetting. Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL Nov 2 00:53:03 plutonium kernel: [ 519.781298] radeon: probe of 0000:01:00.0 failed with error -22 Nov 2 00:53:43 plutonium kernel: [ 560.657546] [drm] Module unloaded Is there something wrong with my setup? System details: Distribution: Kubuntu 9.10 Karmic Koala uname -a output: Linux plutonium 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux lspci -v output: 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 0 Capabilities: [c4] HyperTransport: Slave or Primary Interface Capabilities: [54] HyperTransport: UnitID Clumping Capabilities: [40] HyperTransport: Retry Mode Capabilities: [9c] HyperTransport: #1a Capabilities: [f8] HyperTransport: #1c 00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00005000-00005fff Memory behind bridge: d2300000-d23fffff Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [b0] Subsystem: Hewlett-Packard Company Device 3061 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [110] Virtual Channel <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=07, sec-latency=0 I/O behind bridge: 00003000-00004fff Memory behind bridge: d1300000-d22fffff Prefetchable memory behind bridge: 00000000d0000000-00000000d0ffffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [b0] Subsystem: Hewlett-Packard Company Device 3061 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [110] Virtual Channel <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=08, subordinate=08, sec-latency=0 Memory behind bridge: d1200000-d12fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [b0] Subsystem: Hewlett-Packard Company Device 3061 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [110] Virtual Channel <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=09, subordinate=09, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: d2500000-d25fffff Prefetchable memory behind bridge: 00000000d1000000-00000000d10fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [b0] Subsystem: Hewlett-Packard Company Device 3061 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [110] Virtual Channel <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0 Memory behind bridge: d1100000-d11fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [b0] Subsystem: Hewlett-Packard Company Device 3061 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [110] Virtual Channel <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (prog-if 01) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 22 I/O ports at 6038 [size=8] I/O ports at 604c [size=4] I/O ports at 6030 [size=8] I/O ports at 6048 [size=4] I/O ports at 6010 [size=16] Memory at d2408000 (32-bit, non-prefetchable) [size=1K] Capabilities: [60] Power Management version 2 Capabilities: [70] SATA HBA <?> Kernel driver in use: ahci 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at d2407000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller (prog-if 10) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at d2406000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17 Memory at d2408500 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at d2405000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller (prog-if 10) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at d2404000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19 Memory at d2408400 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) Subsystem: Hewlett-Packard Company Device 3061 Flags: 66MHz, medium devsel Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+ Kernel modules: i2c-piix4 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller (prog-if 8a [Master SecP PriP]) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at 6000 [size=16] Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Kernel driver in use: pata_atiixp 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, slow devsel, latency 64, IRQ 16 Memory at d2400000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, 66MHz, medium devsel, latency 0 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01) Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=80, subordinate=8f, sec-latency=64 I/O behind bridge: 00001000-00001fff 00:18.0 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] HyperTransport Configuration (rev 40) Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h [Turion X2, Athlon X2, Sempron] Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] DRAM Controller Flags: fast devsel Kernel modules: amd64_edac_mod 00:18.3 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Miscellaneous Control Flags: fast devsel Capabilities: [f0] Secure device <?> 00:18.4 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Link Control Flags: fast devsel 01:00.0 VGA compatible controller: ATI Technologies Inc M96 [Mobility Radeon HD 4650] Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at c0000000 (32-bit, prefetchable) [size=256M] I/O ports at 5000 [size=256] Memory at d2300000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at d2320000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [100] Vendor Specific Information <?> Kernel modules: radeon 01:00.1 Audio device: ATI Technologies Inc R700 Audio Device [Radeon HD 4000 Series] Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at d2310000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [100] Vendor Specific Information <?> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 08:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Hewlett-Packard Company Device 3040 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at d1200000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Virtual Channel <?> Capabilities: [160] Device Serial Number 12-14-24-ff-ff-17-15-00 Capabilities: [170] Power Budgeting <?> Kernel driver in use: ath9k Kernel modules: ath9k 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) Subsystem: Hewlett-Packard Company Device 3061 Flags: bus master, fast devsel, latency 0, IRQ 30 I/O ports at 2000 [size=256] Memory at d1004000 (64-bit, prefetchable) [size=4K] Memory at d1000000 (64-bit, prefetchable) [size=16K] Expansion ROM at d1010000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4 Capabilities: [cc] Vital Product Data <?> Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Virtual Channel <?> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Kernel driver in use: r8169 Kernel modules: r8169 PS: I'm not subscribed to the list, so, please include me in the Cc: Thanks, Kunal
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
Hi,
Sorry for not using word-wrap - so that the logs don't look messed up.
I recently bought an HP Pavilion dv6 series laptop which comes with Mobility Radeon HD 4650 graphics chip with 1GB GDD3 VRAM. It seems to be common with the dv6 series laptops from HP.
The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about:
1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used.
The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte
I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM.
256 MB is the max PCI aperture size. that's the largest amount the CPU can access. The GPU, however, can access the entire amount. Support for using the extended memory will come eventually with kms.
2. I tried to use KMS which is recently introduced - just for testing what it's all about. The kernel logs have following lines when trying to enable KMS:
Nov 2 00:52:42 plutonium kernel: [ 499.645739] [drm] Module unloaded Nov 2 00:53:03 plutonium kernel: [ 519.771264] [drm] radeon kernel modesetting enabled. Nov 2 00:53:03 plutonium kernel: [ 519.771264] radeon 0000:01:00.0: setting latency timer to 64 Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm] radeon: Initializing kernel modesetting. Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL Nov 2 00:53:03 plutonium kernel: [ 519.781298] radeon: probe of 0000:01:00.0 failed with error -22 Nov 2 00:53:43 plutonium kernel: [ 560.657546] [drm] Module unloaded
Make sure you have a new enough kernel. You need 2.6.32 or Dave's drm-next tree for r6xx/r7xx KMS support. Also, radeonhd doesn't support kms, you need to use radeon (xf86-video-ati) if you want to try kms. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Hi Alex, On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
wrote: The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about:
1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used.
The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte
I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM.
256 MB is the max PCI aperture size. that's the largest amount the CPU can access. The GPU, however, can access the entire amount. Support for using the extended memory will come eventually with kms.
Aah, my bad, I got confused between who's reporting the memory.. Sorry for my mistake - your explanation makes sense :)
2. I tried to use KMS which is recently introduced - just for testing what it's all about. The kernel logs have following lines when trying to enable KMS:
Nov 2 00:52:42 plutonium kernel: [ 499.645739] [drm] Module unloaded Nov 2 00:53:03 plutonium kernel: [ 519.771264] [drm] radeon kernel modesetting enabled. Nov 2 00:53:03 plutonium kernel: [ 519.771264] radeon 0000:01:00.0: setting latency timer to 64 Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm] radeon: Initializing kernel modesetting. Nov 2 00:53:03 plutonium kernel: [ 519.781298] [drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL Nov 2 00:53:03 plutonium kernel: [ 519.781298] radeon: probe of 0000:01:00.0 failed with error -22 Nov 2 00:53:43 plutonium kernel: [ 560.657546] [drm] Module unloaded
Make sure you have a new enough kernel. You need 2.6.32 or Dave's drm-next tree for r6xx/r7xx KMS support. Also, radeonhd doesn't support kms, you need to use radeon (xf86-video-ati) if you want to try kms.
OK, I'll try it on 2.6.32-rcX as well. However, I tried the KMS on .31 only after reading reports on the phoronix forums that said it worked on .31 as well. I admit I didn't expect the support to be fully functional - just wanted to check it out ;) Thanks, Kunal -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
wrote: Hi,
Sorry for not using word-wrap - so that the logs don't look messed up.
I recently bought an HP Pavilion dv6 series laptop which comes with Mobility Radeon HD 4650 graphics chip with 1GB GDD3 VRAM. It seems to be common with the dv6 series laptops from HP.
The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about:
1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used.
The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte
I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM.
256 MB is the max PCI aperture size. that's the largest amount the CPU can access. The GPU, however, can access the entire amount. Support for using the extended memory will come eventually with kms.
But, shouldn't the X driver (xserver-xorg-video-radeonhd) report it correctly in Xorg.0.log? Isn't that what drives the GPU (via the kernel-mode radeon drm driver)? Just curious.. I'm not a graphics guy, so, I could be wrong. :) Thanks, Kunal -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Tue, Nov 3, 2009 at 11:45 AM, Kunal Gangakhedkar
On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
wrote: Hi,
Sorry for not using word-wrap - so that the logs don't look messed up.
I recently bought an HP Pavilion dv6 series laptop which comes with Mobility Radeon HD 4650 graphics chip with 1GB GDD3 VRAM. It seems to be common with the dv6 series laptops from HP.
The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about:
1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used.
The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte
I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM.
256 MB is the max PCI aperture size. that's the largest amount the CPU can access. The GPU, however, can access the entire amount. Support for using the extended memory will come eventually with kms.
But, shouldn't the X driver (xserver-xorg-video-radeonhd) report it correctly in Xorg.0.log? Isn't that what drives the GPU (via the kernel-mode radeon drm driver)? Just curious..
It does report it: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. However, the CPU can only map 256MB, so it caps vram at 256MB. If the CPU needs to access vram, it's limited to 256MB. For VRAM beyond the 256 MB aperture, the GPU is responsible for dealing with it since only it can access the full amount. The hard part is dealing with buffers in extended memory that the CPU needs access to. The GPU has to move the buffer to some place the CPU can access it. With kms, all asic setup and modesetting moves to the kernel. The ddx at that point is only responsible for EXA/Xv acceleration and interfacing with X. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Tuesday 03 Nov 2009 10:27:28 pm you wrote:
On Tue, Nov 3, 2009 at 11:45 AM, Kunal Gangakhedkar
wrote: On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
wrote: Hi,
Sorry for not using word-wrap - so that the logs don't look messed up.
I recently bought an HP Pavilion dv6 series laptop which comes with Mobility Radeon HD 4650 graphics chip with 1GB GDD3 VRAM. It seems to be common with the dv6 series laptops from HP.
The basic radeonhd X driver with the mainline radeon GPU driver gives me pretty nice X environment. However, there are two issues that I'd like to know more about:
1. the X.org logs show that the entire VRAM is not being used - instead only 256M out of the 1G are being used.
The msg from Xorg.log is: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB. (--) RADEONHD(0): VideoRAM: 262144 kByte
I'm attaching gzipped Xorg.0.log with this mail. Even the lspci output (included below) says that the memory is 256M whereas ATi catalyst driver in pre-installed Windows Vista Home Premium shows and uses full 1GB of VRAM.
256 MB is the max PCI aperture size. that's the largest amount the CPU can access. The GPU, however, can access the entire amount. Support for using the extended memory will come eventually with kms.
But, shouldn't the X driver (xserver-xorg-video-radeonhd) report it correctly in Xorg.0.log? Isn't that what drives the GPU (via the kernel-mode radeon drm driver)? Just curious..
It does report it: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 1048576kB.
However, the CPU can only map 256MB, so it caps vram at 256MB. If the CPU needs to access vram, it's limited to 256MB. For VRAM beyond the 256 MB aperture, the GPU is responsible for dealing with it since only it can access the full amount. The hard part is dealing with buffers in extended memory that the CPU needs access to. The GPU has to move the buffer to some place the CPU can access it.
With kms, all asic setup and modesetting moves to the kernel. The ddx at that point is only responsible for EXA/Xv acceleration and interfacing with X.
Alex
Thanks a lot for the explanation - it was really helpful.. :) Thanks, Kunal -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (2)
-
Alex Deucher
-
Kunal Gangakhedkar