Power Developer
https://powerdeveloper.org/forums/

KDE 4.2.2 and 3d acceleration
https://powerdeveloper.org/forums/viewtopic.php?f=7&t=1704
Page 1 of 1

Author:  Q-Master [ Fri Jun 12, 2009 1:08 pm ]
Post subject:  KDE 4.2.2 and 3d acceleration

I've updated my home debian insallation to new testing, which includes KDE 4.2.2. But seems that it lacks 3d acceleration in plasma. The CPU load is up to 100% when adding just 1 widget. Also I have a weird colors on toolbar and in menus.

Author:  Neko [ Fri Jun 12, 2009 6:09 pm ]
Post subject:  Re: KDE 4.2.2 and 3d acceleration

Quote:
I've updated my home debian insallation to new testing, which includes KDE 4.2.2. But seems that it lacks 3d acceleration in plasma. The CPU load is up to 100% when adding just 1 widget. Also I have a weird colors on toolbar and in menus.
Pegasos/Radeon?

You could take a look at the thread about radeon-rewrite elsewhere on this board and see if you can get that built, it may substantially improve performance too.

Author:  Q-Master [ Sat Jun 13, 2009 1:20 pm ]
Post subject:  Re: KDE 4.2.2 and 3d acceleration

Quote:
Pegasos/Radeon?

You could take a look at the thread about radeon-rewrite elsewhere on this board and see if you can get that built, it may substantially improve performance too.
Pegasos II / Radeon 9200

I'll take a look. Is there a problem with 3d and kde on peg?

Author:  Neko [ Sat Jun 13, 2009 3:50 pm ]
Post subject:  Re: KDE 4.2.2 and 3d acceleration

Quote:
Quote:
Pegasos/Radeon?

You could take a look at the thread about radeon-rewrite elsewhere on this board and see if you can get that built, it may substantially improve performance too.
Pegasos II / Radeon 9200

I'll take a look. Is there a problem with 3d and kde on peg?
There shouldn't be but nobody is going to update the standard original Radeon driver anymore. Finding a problem in radeon-rewrite is more likely to get fixed.

Author:  Q-Master [ Sun Jun 14, 2009 7:40 am ]
Post subject:  Re: KDE 4.2.2 and 3d acceleration

Quote:
There shouldn't be but nobody is going to update the standard original Radeon driver anymore. Finding a problem in radeon-rewrite is more likely to get fixed.
Didnt help. I've rebuild mesa from trunk (with radeon-rewrite already in trunk). AIGLX is now not working. Composites are not working yet.

Author:  Q-Master [ Mon Feb 22, 2010 4:58 am ]
Post subject: 

Ok. Now another one problem appeared. I've fixed the problem wirh wrong PCI node but now VBlank interrupt refuses to set up properly:
(II) RADEON(0): [drm] failure adding irq handler, there is a device already using that irq
[drm] falling back to irq-free operation

How to fix that I just don't know. My searches on the net gave nothing.
Can anyone help?

Author:  Q-Master [ Mon Feb 22, 2010 6:56 am ]
Post subject: 

Ok. That problem is also fixed via "dirty hack".
The hack needs apt-get source libdrm and editing xf86drm.c:
In function drmGetInterruptFromBusID you need to replace the line
Code:
p.busnum = busnum;
to
Code:
p.busnum = busnum-0x100;
In function drmGetBusid you need to add
Code:
u.unique[7] = '1';
BEFORE
Code:
return u.unique;
After that you should
Code:
dpkg-buildpackage

and then
Code:
sudo dpkg -i libdrm2_2.4.17-1_powerpc.deb libdrm-radeon1_2.4.17-1_powerpc.deb

Author:  acrux [ Mon Feb 22, 2010 9:12 am ]
Post subject: 

Quote:
Ok. That problem is also fixed via "dirty hack".
The hack needs apt-get source libdrm and editing xf86drm.c:
can you provide a patch? And maybe submit it to mesa3d-dev?

Author:  Q-Master [ Tue Feb 23, 2010 6:57 am ]
Post subject: 

Quote:
Quote:
Ok. That problem is also fixed via "dirty hack".
The hack needs apt-get source libdrm and editing xf86drm.c:
can you provide a patch? And maybe submit it to mesa3d-dev?
I'll late do this. Submitting is useless. This is a very "dirty" patch only suitable to those, who does have their videocards on PCI:0001:xx:xx.x.

Author:  acrux [ Fri Mar 12, 2010 10:29 am ]
Post subject: 

Quote:
I'll late do this. Submitting is useless. This is a very "dirty" patch only suitable to those, who does have their videocards on PCI:0001:xx:xx.x.
That's right, i only saw pegasos 1/2 and some old pseries with a videocards on PCI:0001

Well, i did a patch against libdrm-2.4.19 with your suggestions and DRI now works on this peg2. Thanks.

Author:  Neko [ Sat Mar 13, 2010 12:11 am ]
Post subject: 

Quote:
Quote:
I'll late do this. Submitting is useless. This is a very "dirty" patch only suitable to those, who does have their videocards on PCI:0001:xx:xx.x.
That's right, i only saw pegasos 1/2 and some old pseries with a videocards on PCI:0001
It should happen on any system where the PCI controller is split into several domains and the graphics card is not in the 0 domain. On Pegasos, the first PCI bus - domain 0 - is the PCI bus. The second PCI bus - domain 1 - is the "AGP" bus.

This is both a weird concept that was done on the Mai northbridge for Pegasos I and an intentional design decision for the Marvell northbridge (since it could be either on the Marvell..) as it makes using PC southbridges a little less crazy when they assume they are on the only PCI bus.

On the PC the PCI buses are usually split into discrete controllers, and domains are only common in extreme server environments where a system may have 16 or 32 PCI slots or something all with discrete configuration spaces in order to make it fit within the PCI standard (more commonly it'd be something like 4 to 8 on a desktop PC or low end server and there is usually very little problem fitting 8 PCI cards in the 2GB address space).
Quote:
Well, i did a patch against libdrm-2.4.19 with your suggestions and DRI now works on this peg2. Thanks.
What I am disappointed with here is that even with the new libpciaccess library for X.org and all the other technology in the kernel that changed how this works for the better, something somewhere STILL assumes that graphics adapters always live in Domain 0.

After all the fuss about it on Pegasos, the fact it went through every distro bugtracker (Ubuntu, SuSE, reported directly to X.org, Ian Romanick knew about it.. especially since he works at IBM and was responsible for pSeries!) it is surprising that it is still broken.

Page 1 of 1 All times are UTC-06:00
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/