Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 24 Nov 2014, 05:39
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Puppy 2.12: 3D-Control-Center V2.00
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 6 [90 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Thu 30 Nov 2006, 10:48    Post subject:  

mach64 is a problem. Even after compiling the kernel module, the 2D mach64 drivers (ati_drv.o & atimisc_drv.o) have their DRI plugin code disabled for security reasons ... well this was the case with Xorg 6.8.1 & 6.8.2. This can be fixed, but it involves a complete recompile of Xorg7 with the configuration file modified.
Back to top
View user's profile Send private message 
MU


Joined: 24 Aug 2005
Posts: 13644
Location: Karlsruhe, Germany

PostPosted: Thu 30 Nov 2006, 21:16    Post subject:  

I tried to compile this older Kernel-module this morning.
http://dri.freedesktop.org/snapshots/mach64-20060403-linux.i386.tar.bz2

Got an error, and commented a function for tests in drm/linux-core/ati_pcigart.c

86-89
Code:
//   for (i = 0; i < ATI_PCIGART_TABLE_PAGES; i++, page++) {
//      __put_page(page);
//      ClearPageReserved(page);
//   }


Then it compiled, but a modprobe mach64 results in:
FATAL: Error inserting mach64 (/lib/modules/2.6.18.1/kernel/drivers/char/drm/mach64.ko): Unknown symbol in module, or unknown parameter (see dmesg)


No idea Crying or Very sad

Mark
Back to top
View user's profile Send private message Visit poster's website 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Thu 30 Nov 2006, 21:50    Post subject:    

Okay, the ATI driver is working for me now. Thanks Very Happy

Now I can go put it to use...

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
MU


Joined: 24 Aug 2005
Posts: 13644
Location: Karlsruhe, Germany

PostPosted: Fri 01 Dec 2006, 13:29    Post subject:  

message from tempestous:
---------
Mark,
You're right, the mach64 DRM source from http://dri.freedesktop.org/snapshots/ will not compile, but I just downloaded the latest DRM source using git, and this compiles the mach64 module OK.
So I have just uploaded the mach64 module to you.
When I ran this build command -

make DRM_MODULES="mach64"

the drm.ko module also compiled. It might be important that this version goes with the mach64 module, so I sent you both.

Regarding the 2D mach64 driver: I'm not sure what configuration options were used in Puppy's Xorg7.0, but I just downloaded the Xorg7.0 source and its default configuration (xorg.cf) has the mach64 DRI option disabled. Line 252 has this -

#define BuildDevelDRIDrivers NO

The "DevelDRIDrivers" are ffb mach64 and unichrome
So I have changed this line to "YES" and I will send you the new mach64 2D driver hopefully in a day or 2.
-----------
Kernelmodule:
http://dotpups.de/tests/mach64-DRM-k2.6.18.1.tar.gz
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Sat 02 Dec 2006, 00:03    Post subject:  

Roger, I suggest you try this new mach64 kernel module. Uncompress the package from your uppermost directory, then run "depmod". Your xorg.conf needs to contain - Load "dri"
Now restart X. Check that "lsmod" lists the mach64 module. If not, load it manually then restart X again.
If 3D still doesn't work, it means that the standard mach64 (ati) 2D Xorg7.0 driver is not DRI-aware. I am trying to compile a revised 2D driver at the moment.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Sun 03 Dec 2006, 09:19    Post subject:  

Roger, can we assume that 3D did not work with Puppy's standard 2D drivers?
Here is the revised 2D driver package - http://dotpups.de/tests/ati-mach64-Xorg7.0.tar.gz
It was compiled with the configuration option "#define BuildDevelDRIDrivers YES"
Uncompress it from your uppermost directory. It will overwrite the existing Xorg drivers in Puppy. Restart X.
Let us know if it works.
Back to top
View user's profile Send private message 
Roger

Joined: 01 Mar 2006
Posts: 15
Location: Germany

PostPosted: Sun 03 Dec 2006, 18:00    Post subject:  

Hi,

here's what dmesg

drm: no version for "struct_module" found: kernel tainted.
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C090] -> GSI 11 (level, low) -> IRQ 11
[drm] Initialized mach64 2.0.0 20060718 on minor 0:
[drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held 0 owner 00000000 c8a95820
[drm:drm_unlock] *ERROR* Process 8263 using kernel context 0


and xorg log tell me:

(II) ATI(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) ATI(0): [drm] loaded kernel module for "mach64" driver
(II) ATI(0): [drm] DRM interface version 1.3
(II) ATI(0): [drm] created "mach64" driver at busid "pci:0000:01:00.0"
(II) ATI(0): [drm] added 8192 byte SAREA at 0xd08ca000
(II) ATI(0): [drm] mapped SAREA 0xd08ca000 to 0xb701e000
(II) ATI(0): [drm] framebuffer handle = 0x40000000
(II) ATI(0): [drm] added 1 reserved context for kernel
(EE) ATI(0): [dri] ATIDRIScreenInit failed because of a version mismatch.
[dri] mach64.o kernel module version is 2.0.0, but version 1.0 or greater is needed.
[dri] Disabling DRI.
(II) ATI(0): [drm] removed 1 reserved context for kernel
(II) ATI(0): [drm] unmapping 8192 bytes of SAREA 0xd08ca000 at 0xb701e000

Something wrong with the module (drm & mach64 are loaded) or the version recognition!?!
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Mon 04 Dec 2006, 00:56    Post subject:  

Roger wrote:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)

This device should be created by the 3D DRI driver ... I can suggest a fix, but first run "lsmod" to check that all necessary kernel modules are loaded:

agpgart
intel-agp ## or whatever AGP module your motherboard requires (ali-agp / amd-k7-agp etc)
drm
mach64

All OK, but dmesg/Xorg.0.log still returns errors? Your last resort is to create that device node manually, like this -

mkdir /dev/dri
mknod /dev/dri/card0 c 226 0
Back to top
View user's profile Send private message 
MU


Joined: 24 Aug 2005
Posts: 13644
Location: Karlsruhe, Germany

PostPosted: Mon 04 Dec 2006, 01:55    Post subject:  

my ATI-radeon fglrx-driver enters hundrets of such lines in Xorg.0.log, but works, so this might be ignored.

Mark

Line 674 to 1957

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
Back to top
View user's profile Send private message Visit poster's website 
Roger

Joined: 01 Mar 2006
Posts: 15
Location: Germany

PostPosted: Mon 04 Dec 2006, 06:42    Post subject:  

Hi,

the modules
agpgart
intel-agp
drm
mach64

are loaded.

/dev/dri/card0 exists - it is created acoording to the xorg log (after 2 unsuccessful attempts before)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0

It seems to me that DRI is not recognising the module correctly
(EE) ATI(0): [dri] ATIDRIScreenInit failed because of a version mismatch.
[dri] mach64.o kernel module version is 2.0.0, but version 1.0 or greater is needed.
[dri] Disabling DRI.

DRI probably does not like version 2.0.0 ... ??
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Mon 04 Dec 2006, 11:25    Post subject:  

It's difficult to know which component is at fault; the 2D driver, 3D driver, DRM module, or libGL.
But I have a suspicion that a newer version of libGL is necessary, to be compatible with the mach64 DRM module, which is the very latest. I will investigate further.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Tue 05 Dec 2006, 00:56    Post subject:  

Attached are the latest mach64-DRI driver, and openGL(Mesa)+libdrm. The CVS source code is the same as the mach64 kernel module was compiled from, so should be compatible.
The older opengl and DRI files in Puppy will be overwritten.

EDIT: mach64-DRI.tar.gz and opengl-CVS.tar.gz removed. See later post.

Last edited by tempestuous on Tue 12 Dec 2006, 04:34; edited 1 time in total
Back to top
View user's profile Send private message 
Roger

Joined: 01 Mar 2006
Posts: 15
Location: Germany

PostPosted: Tue 05 Dec 2006, 04:28    Post subject:  

Thanks. Looks like it's getting messy again.
dmesg & Xorg.0.log show exactly the same errors as before.
I'm not sure if some of the previous modules or links or whatever should have been removed...?? Can I check somehow that the right modules/libs are used?
antinspect from MU's 3DCC package now refuses to work (it did before ... slowly)
/usr/local/3DCC/resource/antinspect: symbol lookup error: /usr/lib/libGL.so.1: undefined symbol: drmOpenOnce
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Tue 05 Dec 2006, 08:55    Post subject:  

Roger wrote:
Thanks. Looks like it's getting messy again.

Yes. It might be a good idea to delete your pup_212.sfs file and start again.
To avoid confusion, the bits you need are -

mach64-DRM-k2.6.18.1 (kernel module)
ati-mach64-Xorg7.0 (DRI-enabled 2D driver)
mach64-DRI (3D DRI driver)
opengl-CVS+libdrm

Roger wrote:
Can I check somehow that the right modules/libs are used?

There was some risk of conflicting libraries because you originally installed "OpenGL" from Mark's 3D-Control-Center, but if you start again with a fresh pup_212.sfs file, that problem is gone.
I think Mark's wizard provides the pupget verison of OpenGL ... and there are some other potentially conflicting files in it - at http://dri.freedesktop.org/wiki/DriTroubleshooting I read this "make sure you don't have any parts of the nvidia binary driver installed, particularly libglx.so*"
The pupget OpenGL package contains some nvidia-looking files in /usr/X11R7/lib/xorg/modules/extensions/

Some other troubleshooting possibilities with xorg.conf:
in Section "Screen" set DefaultDepth 16, and limit the resolution to 800x600

in Section "Module" as well as Load "dri" and Load "glx" try -
Load "drm"

in Section "Device" try -
Options "ForcePCIMode" "YES"
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5285
Location: Australia

PostPosted: Tue 12 Dec 2006, 04:36    Post subject:  

Roger, if no success, I suspect that the 3D components are not playing well with Xorg 7.0.

Xorg 6.8.1 was carried over from Puppy 1.0.9 to early Puppy 2.x versions ...
so I have packaged the mach64 3D files suitable for Puppy 2.01 and posted them here - http://www.murga-linux.com/puppy/viewtopic.php?p=83603
I also removed the earlier Puppy 1.x mach64 3D files and posted them in the same thread.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 6 [90 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0880s ][ Queries: 12 (0.0050s) ][ GZIP on ]