I am running on a debian 7 with xfce. It should be exactly the same as you run now and this is on a live USB. Kernel is 3.2.0-4-686-pae.
I already see differences in the dmesg log. Some things are the same, but some are different. Okay... I mean... I only talk about the things I wrote about earlier on other systems and kernels.
Look at this part of dmesg for example:
It seems now it can read reg 1c of the Host controller and I do not see any quirks logged out for it!
That is a good sign at least and is maybe something... Also I got the values for that register so maybe
some manual hacking will be possible to provide the same data region configured somewhere?
The lspci -v is the same however:
(Maybe it is normal to write <ignored> there actually?)
There is a radeon kernel module seen in dmesg, but from dmesg I see that there is no r300 microcode and radeon fails to load because of this. There is 696 Mb of overlay available so I guess I can save data on this live USB and install things. I have no idea how to install the microcode and where to get it from for this older debian but I can only measure 3d performance if I get that. Are there still packages for this version or should I search for a later one that is easy to try out things with and install stuff?
So there are radeon modules. GART things log out the very same way and same sizes etc, and it even names the missing firmware file or microcode file or whatever.
What is new for me is the log lines for [TTM] - I have no idea what these are supposed to be, but I doubt they help because I saw them in the ubuntu 16.04 live cd too and the performance was not better.
If I search for "agp" this is the only place for it in dmesg:
To me this indicates that the AGP capability is still not listed. I have no idea if that was originally the source of my problem as it was just a big suspicion of mine and maybe I just debugged the kernel agpgart drivers for long time while actually going into a completely bad direction in why the performance was bad... I would only know for sure if I would still have the really original system...
The original system however surely had a later-than-3.2 kernel!
Full logs are available here:
PS.: Does anyone know about a way to measure VRAM memory throughput? Is there any benchmarks specifically rigged to do so?
PS.: The glxinfo and glxgears are not installed as of now, but I would only be able to test software rendering anyways so far now... Also the release is old enough to not have apt sources so I would need to compile a lot of things myself I guess.
TL;DR:
The most relevant information is that the 0x1c register sizing works here and logs a memory area: reg 1c: [mem 0xe0000000-0xffffffff 64bit] while agpgart seem to act the same ways even on this old kernel. Cannot measure 3d performance because of missing binaries.
I think it was worth a try. The system also booted fast and nice otherwise and I understand the r300 bin is missing because it is specific for a device and maybe should not be on a live cd otherwise images grow unnecessary big.
I already see differences in the dmesg log. Some things are the same, but some are different. Okay... I mean... I only talk about the things I wrote about earlier on other systems and kernels.
Look at this part of dmesg for example:
Code:
[ 0.062532] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug [ 0.062628] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.062828] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored) [ 0.062832] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored) [ 0.062837] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored) [ 0.062841] pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored) [ 0.062845] pci_root PNP0A03:00: host bridge window [mem 0x58000000-0xffffffff] (ignored) [ 0.062862] pci 0000:00:00.0: [1002:5a31] type 0 class 0x000600 [B][ 0.062886] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xffffffff 64bit][/B] [ 0.062918] pci 0000:00:01.0: [1002:5a3f] type 1 class 0x000604 [ 0.063017] pci 0000:00:13.0: [1002:4374] type 0 class 0x000c03
That is a good sign at least and is maybe something... Also I got the values for that register so maybe
some manual hacking will be possible to provide the same data region configured somewhere?
The lspci -v is the same however:
Code:
00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI Device 5a31 (rev 01) Subsystem: ASUSTeK Computer Inc. Device 13d7 Flags: bus master, 66MHz, medium devsel, latency 64 Memory at <ignored> (64-bit, non-prefetchable)
There is a radeon kernel module seen in dmesg, but from dmesg I see that there is no r300 microcode and radeon fails to load because of this. There is 696 Mb of overlay available so I guess I can save data on this live USB and install things. I have no idea how to install the microcode and where to get it from for this older debian but I can only measure 3d performance if I get that. Are there still packages for this version or should I search for a later one that is easy to try out things with and install stuff?
Code:
[ 19.861009] [drm] [B]radeon[/B] kernel modesetting enabled. [ 19.861647] [drm] initializing kernel modesetting (RS400 0x1002:0x5A62 0x1043:0x1392). [ 19.861678] [drm] register mmio base: 0xFE1F0000 [ 19.861681] [drm] register mmio size: 65536 [ 19.861867] [drm] Generation 2 PCI interface, using max accessible memory [ 19.861875] radeon 0000:01:05.0: [B]VRAM: 128M[/B] 0x0000000058000000 - 0x000000005FFFFFFF (128M used) [ 19.861880] radeon 0000:01:05.0: [B]GTT: 512M[/B] 0x0000000060000000 - 0x000000007FFFFFFF [ 19.861895] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 19.861898] [drm] Driver supports precise vblank timestamp query. [ 19.861912] [drm] radeon: irq initialized. [ 19.862380] [drm] Detected VRAM RAM=128M, BAR=256M [ 19.862384] [drm] RAM width 128bits DDR [ 19.868504] [B][TTM][/B] Zone kernel: Available graphics memory: 446938 kiB [ 19.868509] [B][TTM][/B] Zone highmem: Available graphics memory: 712062 kiB [ 19.868512] [B][TTM][/B] Initializing pool allocator [ 19.868524] [B][TTM][/B] Initializing DMA pool allocator [ 19.868566] [drm] radeon: 128M of VRAM memory ready [ 19.868569] [drm] radeon: 512M of GTT memory ready. [ 19.868602] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 19.992619] psmouse serio4: synaptics: Touchpad model: 1, fw: 6.2, id: 0x92a0b1, caps: 0xa0471b/0x200000/0x0 [ 20.009379] [drm] radeon: ib pool ready. [ 20.009472] [drm] radeon: 3 quad pipes, 1 z pipes initialized. [ 20.015730] [drm] [B]PCIE GART of 512M[/B] enabled (table at 0x0000000034880000). [ 20.019226] radeon 0000:01:05.0: WB enabled [ 20.019232] [drm] fence driver on ring 0 use gpu addr 0x60000000 and cpu addr 0xf7102000 [ 20.020302] [drm] [B]Loading R300 Microcode[/B] [ 20.058147] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input10 [ 20.093414] platform radeon_cp.0: firmware: agent aborted loading [B]radeon/R300_cp.bin (not found?)[/B] [ 20.093558] [drm:r100_cp_init] [B]*ERROR* Failed to load firmware![/B] [ 20.093612] radeon 0000:01:05.0: failed initializing CP (-2). [ 20.093662] radeon 0000:01:05.0: [B]Disabling GPU acceleration[/B]
What is new for me is the log lines for [TTM] - I have no idea what these are supposed to be, but I doubt they help because I saw them in the ubuntu 16.04 live cd too and the performance was not better.
If I search for "agp" this is the only place for it in dmesg:
Code:
[ 1.172292] Linux agpgart interface v0.103
The original system however surely had a later-than-3.2 kernel!
Full logs are available here:
PS.: Does anyone know about a way to measure VRAM memory throughput? Is there any benchmarks specifically rigged to do so?
PS.: The glxinfo and glxgears are not installed as of now, but I would only be able to test software rendering anyways so far now... Also the release is old enough to not have apt sources so I would need to compile a lot of things myself I guess.
TL;DR:
The most relevant information is that the 0x1c register sizing works here and logs a memory area: reg 1c: [mem 0xe0000000-0xffffffff 64bit] while agpgart seem to act the same ways even on this old kernel. Cannot measure 3d performance because of missing binaries.
I think it was worth a try. The system also booted fast and nice otherwise and I understand the r300 bin is missing because it is specific for a device and maybe should not be on a live cd otherwise images grow unnecessary big.
Comment