Mailinglist Archive: radeonhd (255 mails)
| < Previous | Next > |
Re: [radeonhd] 0x9480:0x103C:0x3061: ATI Technologies Inc M96 [Mobility Radeon HD 4650]
- From: Kunal Gangakhedkar <kunal.gangakhedkar@xxxxxxxxx>
- Date: Tue, 3 Nov 2009 20:49:31 +0530
- Message-id: <200911032049.31929.kunal.gangakhedkar@xxxxxxxxx>
Hi Alex,
On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
Aah, my bad, I got confused between who's reporting the memory..
Sorry for my mistake - your explanation makes sense :)
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@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
On Tuesday 03 Nov 2009 8:38:55 pm Alex Deucher wrote:
On Tue, Nov 3, 2009 at 10:00 AM, Kunal Gangakhedkar
<kunal.gangakhedkar@xxxxxxxxx> 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@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
| < Previous | Next > |