Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
HOW-TO: ProSavage, SuperSavage DDR and dri-drm 3d drivers
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Fri Mar 11, 2005 1:25 pm    Post subject: Reply with quote

DISCLAIMER: This is not a HOW-TO. Some users are confused about the last changes in dri cvs code, then I want to describe the steps I used to install it. This "works for me" on Acer Aspire 1200 series, you can use it by modifications but I can't guarantee what success you have and I'm not responsible if you damage your config, your data or your hardware. This method is based on this page:
http://dri.freedesktop.org/wiki/Building
and I omitted some things (libraries backup, etc.) but don't forget to use it.

Requirements: You must have masked version (~x86) of x11-base/xorg-x11 and x11-base/opengl-update and xorg must be compiled with activated dlloader use. You also must have kernel source in /usr/src. Some steps are specific for my system:

Code:

VGA compatible controller: S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02)

Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r6 i686)
=================================================================
System uname: 2.6.10-gentoo-r6 i686 Intel(R) Celeron(TM) CPU                1300MHz
Gentoo Base System version 1.4.16
ACCEPT_KEYWORDS="x86"
CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -fvisibility-inlines-hidden"
USE="x86 X X509 aalib acpi acpi4linux alsa apache2 apm arts audiofile avi berkdb bitmap-fonts cdparanoia cdr chroot crypt cups curl dga directfb distcache divx4linux dlloader dmx dvb dvd dvdread edl emacs emboss encode escreen esd etwin exif faac fam fbcon fbdev fftw flac font-server foomaticdb fortran fs ftp gdbm gif gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib imlib2 ipv6 ithreads java jpeg kde libcaca libg++ libwww live mad mailwrapper mbox mikmod mime mmx mmx2 modelock motif mozilla moznoirc moznomail mozp3p mozsvg mp3 mpeg mysql ncurses need nls nptl ntlm offensive oggvorbis opengl opens oss pam pcmcia pdflib perl php pic pie png posix python qt quicktime readline real rtc samba scanner sdl sftplogging sharedmem slang smime speedo speex spell sse sse2 ssl svg svga tcpd tetex tga tiff truetype truetype-fonts type1 type1-fonts unicode usb userlocales v4l2 vda vdesktop vhosts virus-scan wmf xanim xml xml2 xmms xosd xpm xprint xv xvid xvmc zlib linguas_it"


1- Getting the CVS trees:
get sources in the same directory; I used /root/tmp

Code:

cd /root/tmp

cvs -d:pserver:anoncvs@cvs.freedesktop.org:/cvs/xorg login
cvs -z3 -d:pserver:anoncvs@cvs.freedesktop.org:/cvs/xorg co xc

cvs -d:pserver:anonymous@cvs.freedesktop.org:/cvs/mesa login
cvs -z3 -d:pserver:anonymous@cvs.freedesktop.org:/cvs/mesa co Mesa

cvs -d:pserver:anonymous@cvs.freedesktop.org:/cvs/dri login
cvs -z3 -d:pserver:anonymous@cvs.freedesktop.org:/cvs/dri co drm


2- Preparing xorg build:

Code:

cd /root/xc/config/cf
wget http://freedesktop.org/~fxkuehl/host.def


edit /root/tmp/config/cf/host.def and change these lines:

Code:

#define XF86CardDrivers savage
#define DefaultGcc2i386Opt -O2 -gstabs+ -pipe <add other compiler options if you want>


You can choose what compiler options you want; I tested "-gstabs+ -march=pentium3 -O3 -pipe -fomit-frame-pointer" with success. DON'T USE -fPIC (for now).
Then:

Code:

cd /root/tmp/xc
wget http://freedesktop.org/~fxkuehl/buildtools.patch
patch -p0 < buildtools.patch


3- Compiling and installing xorg:

Code:

make World


and if there were no errors,

Code:

make install


4- Libraries switching:
in Gentoo systems, libraries are not in usual places. You should change some locations:

Code:

mv /usr/lib/libGL.so.1.2 /usr/lib/opengl/xorg-x11/lib
rm /usr/lib/libGL.so*
ln -s /usr/lib/opengl/xorg-x11/lib/libGL.so /usr/lib/libGL.so
cp /usr/lib/modules/extensions/libglx.so /usr/lib/opengl/xorg-x11/extensions
ldconfig


in order to use prelink, AFTER installation recompile xc with this line in host.def:

#define DefaultGcc2i386Opt -gstabs+ -pipe <other options> -fPIC

and copy ONLY libGL.so.1.2 :

Code:

cp exports/lib/libGL.so.1.2 /usr/lib/opengl/xorg-x11/lib
ldconfig


5- Building and installing Mesa drivers

Code:

cd /root/tmp/Mesa


append these line to configs/linux-dri-x86 file (or to the right file for your hardware)

Code:

DRM_SOURCE_PATH = /root/tmp/drm
    OPT_FLAGS = <compiler options, see your previous options>
    SRC_DIRS = mesa
    DRI_DIRS = dri_client savage


and then:

Code:

make linux-dri-x86


and if there were no errors:

Code:

cp lib/savage_dri.so /usr/X11R6/lib/modules/dri


6- Building and installing DRM

For 2.6 kernel series:

Code:

cd /root/tmp/drm/linux-core
make LINUXDIR=/usr/src/linux DRM_MODULES="savage"


and if there were no errors:

Code:

mkdir /lib/modules/$KERNEL/kernel/drivers/char/drm
cp savage.ko /lib/modules/$KERNEL/kernel/drivers/char/drm
cp drm.ko /lib/modules/$KERNEL/kernel/drivers/char/drm
depmod -a


7- Finishing up:

Finally, you can modify your xorg.conf to use dri. My sistem runs well with these options:

Code:

<snip>
Section "Module"
        Load  "bitmap"
        Load  "ddc"
        Load  "int10"
        Load  "dbe"
        Load  "vbe"
        Load  "extmod"
        Load  "glx"
        Load  "dri"
        Load  "record"
        Load  "xtrap"
        Load  "freetype"
        Load  "type1"
EndSection
<snip>
Section "Device"

        Option      "AGPMode"   "4"
        Option      "HWCursor"  "True"
        Option      "UseBIOS"   "False"
        Option      "ShadowStatus"  "False"
        Option      "DmaMode"   "Any"
        Option      "ForceInit" "Yes"
        Identifier  "savage"
        Driver      "savage"
        VendorName  "S3 inc."
        BoardName   "savage"
        BusId       "PCI:1:0:0"
        VideoRam    32768

EndSection
<snip>
Section "dri"
        Mode         0666
EndSection


DmaMode is a new driver option, values can be "Any", "Command", "Vertex", "None". "Any" attempts to use Command DMA as first, then Vertex DMA. I've obtained this results with glxgears: 317 (None), 318 (Vertex), 321 (Command) and 321 (Any). This option doesn't work for Savage IX/MX.
After X server restarting, if it doesn't work, play with driver options, especially ShadowStautus (with previous installations my system worked with "True" value, now only with "False" value).

Good luck!
Back to top
View user's profile Send private message
salivian
Tux's lil' helper
Tux's lil' helper


Joined: 15 Sep 2002
Posts: 91

PostPosted: Sat Mar 12, 2005 7:43 pm    Post subject: Reply with quote

Thanks, I will try and look at the new options from the dri-users lists.

I think a lot of user who found the current cvs "not working" is using a supersavage IX (it's on IBM T2x, including myself)


Thanks for the effort once again :)
Back to top
View user's profile Send private message
odocoileus
n00b
n00b


Joined: 27 Dec 2004
Posts: 45

PostPosted: Mon Mar 14, 2005 3:38 am    Post subject: Reply with quote

Thankyou for laying it out, I do appreciate it, however my journey is not over yet. Still no direct rendering here.
Code:
bash-2.05b$ glxinfo|grep render
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

Code:

bash-2.05b$ cat /var/log/Xorg.0.log|grep -w EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
        (EE) SAVAGE(0): DRI isn't enabled
        (EE) SAVAGE(0): Direct rendering disabled
       

but, earlier in the log file, it looks like dri gets loaded...
Code:

        (II) LoadModule: "dri"
        (II) Loading /usr/X11R6/lib/modules/extensions/libdri.so
        (II) Module dri: vendor="X.Org Foundation"
                compiled for 6.8.1.99, module version = 1.0.0
                 ABI class: X.Org Server Extension, version 0.2
         (II) Loading sub module "drm"
          (II) LoadModule: "drm"
          (II) Loading /usr/X11R6/lib/modules/linux/libdrm.so
          (II) Module drm: vendor="X.Org Foundation"
                   compiled for 6.8.1.99, module version = 1.0.0
                    ABI class: X.Org Server Extension, version 0.2
           (II) Loading extension XFree86-DRI
                                       


This section is sort of repeated...I thought it seemed suspicious
first here
Code:
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.so
(II) Module int10: vendor="X.Org Foundation"
        compiled for 6.8.1.99, module version = 1.0.0
        ABI class: X.Org Video Driver, version 0.7
(II) SAVAGE(0): initializing int10
(II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 32768 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Savage2000
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: Savage2000
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev C
(--) SAVAGE(0): Chip: id 9102, "Savage2000"
(--) SAVAGE(0): Engine: "Savage2000"
(--) SAVAGE(0): AGP card detected
(==) SAVAGE(0): Using AGP DMA
(**) SAVAGE(0): Will try command and vertex DMA mode
(**) SAVAGE(0): Using AGP 4x mode
(==) SAVAGE(0): Using 16 MB AGP aperture
(II) SAVAGE(0): mapping MMIO @ 0xe1000000 with size 0x80000
(==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
(**) SAVAGE(0): videoram =  32768k


and again here, but different
Code:
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.so
(II) SAVAGE(0): initializing int10
(II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 32768 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Savage2000
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: Savage2000
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev C
(--) SAVAGE(0): mapping framebuffer @ 0xe4000000 with size 0x2000000
(==) SAVAGE(0): Write-combining range (0xe4000000,0x2000000)
(II) SAVAGE(0): Splitting WC range: base: 0xd4000000, size: 0x5000000
(==) SAVAGE(0): Write-combining range (0xd8000000,0x1000000)
(==) SAVAGE(0): Write-combining range (0xd4000000,0x5000000)
(II) SAVAGE(0): map aperture:0xb08f8000
(--) SAVAGE(0): Shadow area physical e5fdffe0, linear 0xb78d7fe0
(EE) SAVAGE(0): DRI isn't enabled
(--) SAVAGE(0): Chose mode 117 at 60Hz.
(II) SAVAGE(0): Using 1280 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)

In my xorg.conf, I tried it with load "int10" and without, no chnage.
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Mon Mar 14, 2005 2:18 pm    Post subject: Reply with quote

@salivian: What's the problem, exactly?

@odocoileus: From your Xorg.0.log
Code:

(II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Savage2000


I think savage driver doesn't support your card. See http://dri.freedesktop.org/wiki/S3Savage?action=highlight&value=CategoryHardware
Back to top
View user's profile Send private message
salivian
Tux's lil' helper
Tux's lil' helper


Joined: 15 Sep 2002
Posts: 91

PostPosted: Wed Mar 16, 2005 5:32 pm    Post subject: Reply with quote

X/machine crashes on all GL apps like glxgears.
the screen starts showing defective images, mouse pointer stop functioning, then the fonts on console(not X) also got mess up.

My feeling is the driver wrote something wrong into the framebuffer.


the log was fine nothing was reported.
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Fri Mar 18, 2005 1:27 pm    Post subject: Reply with quote

salivian wrote:
the log was fine nothing was reported.


In my experience, when logs are ok, driver options are guilty. Felix Kuehl reported problems with ShadowStatus option but problem can be other. Try to change option values (one for time).

salivian wrote:
My feeling is the driver wrote something wrong into the framebuffer.


And if you start with framebuffer disabled?
Back to top
View user's profile Send private message
salivian
Tux's lil' helper
Tux's lil' helper


Joined: 15 Sep 2002
Posts: 91

PostPosted: Mon Mar 21, 2005 7:01 am    Post subject: Reply with quote

"Framebuffer"

I was refering to the framebuffer on the hardware.

anyway I will do more testing.
Back to top
View user's profile Send private message
bodymind
n00b
n00b


Joined: 25 Jan 2005
Posts: 22

PostPosted: Sun Mar 27, 2005 7:56 pm    Post subject: Reply with quote

Hi, i've done Algor How-to, my Xvinfo now works and i can see movies in full-screen! :D but i can't get DRI working.. here's some logs:

dmesg | grep drm :
Code:
[drm] Initialized drm 1.0.0 20040925
[drm] Initialized savage 2.4.1 20050313 on minor 0: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
[drm] Used old pci detect: framebuffer loaded

cat /var/log/Xorg.0.log | grep dri
Code:
        X.Org XInput driver : 0.4
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a
(II) Module dri: vendor="X.Org Foundation"
(II) Loading /usr/X11R6/lib/modules/drivers/savage_drv.o
        ABI class: X.Org XInput driver, version 0.4
        ABI class: X.Org XInput driver, version 0.4
(II) SAVAGE: driver (version 1.1.27t) for S3 Savage chipsets: Savage4,

cat /var/log/Xorg.0.log | grep error
Code:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.


Help..please.. =| i want to play!
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Mon Mar 28, 2005 12:34 pm    Post subject: Reply with quote

Hi. I'm considering joining xorg's CVS club as well, but I work with my computer, so here's my question. Has any of you felt the unstability of your CVS xorg in terms of bugs, breakages, glitches or any distressing event at all? :roll:

Responses would be greatly appreciated. :D
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Mar 29, 2005 3:48 am    Post subject: Reply with quote

OK, that's the situation:
Code:
$ cat /var/log/Xorg.1.log | grep SAVAGE
<snip>
(II)SAVAGE(0): Direct rendering enabled
Code:
$ glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
Do anyone of you have an explanation to that seemingly contradiction?:?
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Mar 29, 2005 8:01 am    Post subject: Reply with quote

OK, spent the day re-reading this thread. So it looks like the CVS stuff does not work on T20s right now huh? And I started out with the binaries, but didn't got very far... OK, back to the binaries... :?
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Mar 29, 2005 11:43 am    Post subject: Reply with quote

I promise this is the last update, but I guess it might be useful information for the ones who are thinking about trying it on a T20.

I've installed the binaries, and it's working, that is, kinda. Sometimes it does, sometimes it doesn't. Seems that after rebooting, I have to leave X and return in order to have direct rendering. Glxgears are much faster now, but crash if I move the mouse cursor while it executes, and if I test it twice, it crashes the whole system (although the apm power button keeps working). OpenGL apps all work nicely, then crash. I guess I've got the answer to my previous question now (what does unstable means). :wink:

How about the other T20s / Savage IX/MVs in this thread? Anyone was able to get it working better than I did, and how?
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Mar 29, 2005 12:35 pm    Post subject: Reply with quote

From /var/log/Xorg.1.log:
Code:
(II) SAVAGE(0): 4740 kB of Videoram needed for 3D; 8192 kB of Videoram available
To /etc/xorg.conf:
Code:
Option "VideoRam" "4740"
...And it works smoothly... :D :D :D

[edit] I take it back. It works until I use an app that uses DRI (glxgears, xscreensaver, vegastrike...). They survive longer than before, though. And X crashes on exit. :(
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Wed Mar 30, 2005 9:11 am    Post subject: Reply with quote

@bodymind:
check your cvs installation, the right version of savage driver must be 2.0.0
bodymind wrote:

Code:
 
(II) SAVAGE: driver (version 1.1.27t) for S3 Savage chipsets: Savage4,



@dmvianna:
dmvianna wrote:

Has any of you felt the unstability of your CVS xorg in terms of bugs, breakages, glitches or any distressing event at all?

My box is now very stable and all works well. Last cvs source has resolved my lockup problems with opengl screensavers (I had system freeze after about one hour of screensaver activation). If your system doesn't work with cvs version, you can ever reinstall old libraries (remember the backup of these).
dmvianna wrote:

Seems that after rebooting, I have to leave X and return in order to have direct rendering.

After rebooting check if savage and drm modules are loaded with lsmod. I have similar problem with gentoo box with udev. Try to force modules loading with modules.conf.
However, as reported by salivian, the support of savage IX/MV is still problematic.
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Wed Mar 30, 2005 9:32 am    Post subject: Reply with quote

AIgor wrote:
Quote:
Last cvs source has resolved my lockup problems with opengl screensavers (I had system freeze after about one hour of screensaver activation).

8O That's exactly the problem I had, and the reason why I've just uninstalled the binaries. Hum, maybe I'll try the CVS again later. Thanks heaps for that piece of information, AIgor! :)
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Thu Mar 31, 2005 1:43 am    Post subject: Reply with quote

:( No luck with the CVS yet. It's stable, but no direct rendering. I guess I'll have to wait until it becomes stable, who knows when. Reminds me that this thread started a year ago, and back then people thought it would become stable within months...
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Thu Mar 31, 2005 8:35 am    Post subject: Reply with quote

dmvianna wrote:
I guess I'll have to wait until it becomes stable, who knows when.

If you want DRI now, compile old source. To obtain it, use the -D option of cvs command (look previous posts). However, I think it can be helpful to check (and to take part in) the dri-users mailing list.
Back to top
View user's profile Send private message
leks
n00b
n00b


Joined: 11 Oct 2004
Posts: 40

PostPosted: Thu Mar 31, 2005 11:00 pm    Post subject: Reply with quote

Well I'm joining the club...

more or less, at least

I did everything algor said, well thats my shortened xorg log output:
Code:

(II) SAVAGE(0): 4740 kB of Videoram needed for 3D; 8192 kB of Videoram available
(II) SAVAGE(0): Sufficient Videoram available for 3D
(II) SAVAGE(0): [drm] bpp: 16 depth: 16
(II) SAVAGE(0): [drm] Sarea 2200+284: 2484
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "savage"
(II) SAVAGE(0): [drm] drmOpen failed
(EE) SAVAGE(0): [drm] DRIScreenInit failed.  Disabling DRI.
(EE) SAVAGE(0): DRI isn't enabled
(--) SAVAGE(0): Chose mode 117 at 60Hz.
(II) SAVAGE(0): Using 1280 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)
   Screen to screen bit blits
   Solid filled rectangles
   8x8 mono pattern filled rectangles
   Indirect CPU to Screen color expansion
   Solid Lines
   Image Writes
   Offscreen Pixmaps
   Setting up tile and stipple cache:
      32 128x128 slots
      12 256x256 slots
(==) SAVAGE(0): Backing store disabled
(**) Option "dpms"
(**) SAVAGE(0): DPMS enabled
(EE) SAVAGE(0): Direct rendering disabled
(WW) SAVAGE(0): Option "UseFBDev" is not used
(==) RandR enabled




Error Section:

Code:
~/tmp/drm/linux-core% cat /var/log/Xorg.0.log|grep -w EE
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load /usr/X11R6/lib/modules/extensions/libGLcore.so
(EE) Failed to load module "GLcore" (loader failed, 7)
(EE) Failed to load module "pex5" (module does not exist, 0)
(EE) Failed to load module "xie" (module does not exist, 0)
(EE) Failed to load module "speedo" (module does not exist, 0)
(EE) SAVAGE(0): [drm] DRIScreenInit failed.  Disabling DRI.
(EE) SAVAGE(0): DRI isn't enabled
(EE) SAVAGE(0): Direct rendering disabled


dmesg:
Code:


kobject_register failed for drm (-17)
 [<c025bdeb>] kobject_register+0x5b/0x60
 [<c012fba1>] mod_sysfs_setup+0x51/0xc0
 [<c0130d11>] load_module+0x7a1/0xa70
 [<c0131040>] sys_init_module+0x60/0x240
 [<c01031cf>] syscall_call+0x7/0xb
savage: Unknown symbol drm_get_resource_len
savage: Unknown symbol drm_get_dev
savage: Unknown symbol drm_get_resource_start
savage: Unknown symbol drm_cleanup_pci
savage: Unknown symbol drm_initmap
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xa00-0xaff: clean.


well the modules dont even seem to load..

now, what COULD be wrong? :?

help would be greatly appreciated..:(
_________________
FreeBSD is neat
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Fri Apr 01, 2005 9:11 am    Post subject: Reply with quote

What kernel version do you have? Has the kernel been compiled with DRM support? Try to recompile it without this support (and then the cvs drm source again).
Back to top
View user's profile Send private message
leks
n00b
n00b


Joined: 11 Oct 2004
Posts: 40

PostPosted: Fri Apr 01, 2005 11:53 am    Post subject: Reply with quote

AIgor wrote:
What kernel version do you have? Has the kernel been compiled with DRM support? Try to recompile it without this support (and then the cvs drm source again).


most recent CKsources =
Linux stella 2.6.11-ck3 #2 Tue Mar 29 22:47:46 CEST 2005 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux



nah kernel DRM is disabled :? ..
_________________
FreeBSD is neat
Back to top
View user's profile Send private message
AIgor
n00b
n00b


Joined: 27 Apr 2004
Posts: 60
Location: Perugia - Italy

PostPosted: Fri Apr 01, 2005 12:54 pm    Post subject: Reply with quote

Uhmm... According to dri-users mailing list, I think problems are depending by different kernel and cvs modules version. Be sure that you compile modules in linux-core directory and the path of kernel source is right. Both savage.ko and drm.ko must be copied, and don't forget to do depmod -a. Are kernel and cvs modules compiled with the same version of gcc?
Back to top
View user's profile Send private message
leks
n00b
n00b


Joined: 11 Oct 2004
Posts: 40

PostPosted: Fri Apr 01, 2005 8:09 pm    Post subject: Reply with quote

AIgor wrote:
Uhmm... According to dri-users mailing list, I think problems are depending by different kernel and cvs modules version. Be sure that you compile modules in linux-core directory and the path of kernel source is right. Both savage.ko and drm.ko must be copied, and don't forget to do depmod -a. Are kernel and cvs modules compiled with the same version of gcc?

jup jup jup jup
i've done everything as mentioned by you and the wiki

im not the only one with that problem, as far as i could see in the dri-user mailinglist..
:|
_________________
FreeBSD is neat
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Apr 12, 2005 10:34 am    Post subject: Reply with quote

:D The last development snapshot WORKS for me!!! :D And I didn't even had to substitute the Xorg server...
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1560
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Tue Apr 12, 2005 5:03 pm    Post subject: Reply with quote

dmvianna wrote:
:D The last development snapshot WORKS for me!!! :D And I didn't even had to substitute the Xorg server...

So you're saying that the latest dri-drm snapshot works with the plain old xorg-x11 that's emerged by portage? And if that's a yes can you post your "emerge xorg-x11 -vp" results please.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Tue Apr 12, 2005 9:55 pm    Post subject: Reply with quote

Code:

These are the packages that I would merge, in order:

Calculating dependencies    ...done!
[ebuild   R   ] x11-base/xorg-x11-6.8.2-r1  -3dfx -3dnow +bitmap-fonts -cjk -debug +dlloader -dmx -doc +font-server -hardened +insecure-drivers +ipv6 -minimal +mmx +nls +opengl +pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv 0 kB

Total size of downloads: 0 kB
12 hours running VegaStrike and xscreensaver without a glitch now :lol:
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  Next
Page 6 of 10

 
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