| View previous topic :: View next topic |
| Author |
Message |
dark.elixir
n00b
Joined: 03 Jan 2005
Posts: 13
|
 Posted: Sun Apr 02, 2006 8:51 pm Post subject: DRI Kernel Modules (from Modular X) lost |
 |
|
Hi everyone. Here's the problem:
I was really excited about the new Xorg supporting my ugly and outdated SuperSavage IX video card. I just had to add the "dri" flag to my USE variable, and declare two new variables in my make.conf
| Code: | USE="... dri ..."
VIDEO_CARDS="savage s3 vesa fbdev" # I think s3 is not necessary. The other ones are for backup.
INPUT_DEVICES="keyboard mouse synaptics" |
I followed the instructions to migrate from the old Xorg, and EVERYTHING WORKED GREAT!!. I had DRI enabled, was able to run 3D applications  . But..... everything went down when I decided to recompile and reinstall my kernel (along with the modules). As I had expected the dri.ko and savage.ko kernel modules were GONE!!!, so my X server is now unable to load those kernel modules and DRI is not working anymore.
I have tried recompiling my video card's driver and the main Xorg package without any succes:
| Code: |
# emerge xf86-video-savage
# emerge xorg-server |
The modules won't appear again!!! Please!!! I need to know WHICH PACKAGE SHOULD I RECOMPILE IN ORDER TO GET THOSE MODULES AGAIN?
I'm pretty sure my Xorg is trying to load those modules (/var/log/Xorg.0.log):
| Code: |
(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 2.0
(II) SAVAGE(0): VESA VBE Total Mem: 15168 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Graphics Incorporated. Paramount video BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Graphics Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0
(--) SAVAGE(0): mapping framebuffer @ 0xdc000000 with size 0x1000000
(II) SAVAGE(0): map aperture:0xb181c000
(II) SAVAGE(0): 4740 kB of Videoram needed for 3D; 16384 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 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
[b][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[/b]
|
|
|
| Back to top |
|
 |
dmvianna
l33t
Joined: 22 Mar 2004
Posts: 742
Location: Down Underland
|
| Posted: Sun Apr 02, 2006 10:01 pm Post subject: |
|
|
Just some thoughts, with no confidence at all:
x11-libs/libdrm
x11-proto/xf86driproto
It might be also a good idea to compile
x11-drivers/xf86-video-vesa
and then
x11-drivers/xf86-video-savage
In light of my experience of the savage driver not compiling without that one being installed beforehand. Good luck! 
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Last edited by dmvianna on Sun Apr 02, 2006 10:06 pm; edited 1 time in total |
|
| Back to top |
|
|
dark.elixir
n00b
Joined: 03 Jan 2005
Posts: 13
|
| Posted: Sun Apr 02, 2006 10:03 pm Post subject: |
|
|
| Sorry. Already tried both. They compiled without any problem but the modules are still missing. |
|
| Back to top |
|
|
RoundsToZero
Guru
Joined: 17 Nov 2003
Posts: 478
Location: New York, NY
|
| Posted: Mon Apr 03, 2006 12:53 am Post subject: |
|
|
You could try equery b dri.ko and equery b savage.ko. This should show you what package those files belonged to, then you can reinstall those packages. However I see that these are modules that are included in the standard kernel, so why dont you just go back to /usr/src/linux, run make menuconfig, and check under Device Drivers->Character Devices and make sure Direct Rendering Manager and Savage Video Cards are both selected. Then quit out of that, and re-run make and make modules_install. Then you should get your modules back, in /lib/modules/...
EDIT: hm, looks like you got it working in the other thread |
|
| Back to top |
|
|
sonicbhoc
Veteran
Joined: 24 Oct 2005
Posts: 1805
Location: In front of the computer screen
|
| Posted: Mon Apr 03, 2006 1:17 am Post subject: |
|
|
emerge module-rebuild. That automatically rebuilds modules (as the name implies.  ) |
|
| Back to top |
|
|
|
Desktop Environments
