public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
       [not found] <4548C6EF.7090800@akyasociados.com.ar>
@ 2006-11-01 20:57 ` Richard Fish
  2006-11-01 22:59   ` b.n.
  2006-11-02 10:53   ` Rafael Barrera Oro
  0 siblings, 2 replies; 9+ messages in thread
From: Richard Fish @ 2006-11-01 20:57 UTC (permalink / raw
  To: gentoo-user

On 11/1/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
> pandemonium, i found out that things are way, way slower than before, is
> this a known effect of modular X.org?

Not that I'm aware of.  Can you post your /var/log/Xorg.0.log
file...maybe there is some clue there.

-Richard
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-01 20:57 ` [gentoo-user] Modular X.org issue (feelings of absolute failure) Richard Fish
@ 2006-11-01 22:59   ` b.n.
  2006-11-02  7:43     ` Ow Mun Heng
  2006-11-02 10:53   ` Rafael Barrera Oro
  1 sibling, 1 reply; 9+ messages in thread
From: b.n. @ 2006-11-01 22:59 UTC (permalink / raw
  To: gentoo-user

Richard Fish ha scritto:
> On 11/1/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
>> pandemonium, i found out that things are way, way slower than before, is
>> this a known effect of modular X.org?
> 
> Not that I'm aware of.  Can you post your /var/log/Xorg.0.log
> file...maybe there is some clue there.
> 

Details about the graphic card and drivers, xorg setup etc. are welcome, 
of course.

m.
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-01 22:59   ` b.n.
@ 2006-11-02  7:43     ` Ow Mun Heng
  0 siblings, 0 replies; 9+ messages in thread
From: Ow Mun Heng @ 2006-11-02  7:43 UTC (permalink / raw
  To: gentoo-user

On Wed, 2006-11-01 at 22:59 +0000, b.n. wrote:
> Richard Fish ha scritto:
> > On 11/1/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
> >> pandemonium, i found out that things are way, way slower than before, is
> >> this a known effect of modular X.org?
> > 
> > Not that I'm aware of.  Can you post your /var/log/Xorg.0.log
> > file...maybe there is some clue there.
> > 
> 
> Details about the graphic card and drivers, xorg setup etc. are welcome, 
> of course.

I've upgraded a while ago, (leaving it to the very last minute) and it's
working fine. SO, you really need to post more details.


-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-01 20:57 ` [gentoo-user] Modular X.org issue (feelings of absolute failure) Richard Fish
  2006-11-01 22:59   ` b.n.
@ 2006-11-02 10:53   ` Rafael Barrera Oro
  2006-11-02 19:50     ` Richard Fish
  1 sibling, 1 reply; 9+ messages in thread
From: Rafael Barrera Oro @ 2006-11-02 10:53 UTC (permalink / raw
  To: gentoo-user

Richard Fish wrote:

> On 11/1/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
>
>> pandemonium, i found out that things are way, way slower than before, is
>> this a known effect of modular X.org?
>
>
> Not that I'm aware of.  Can you post your /var/log/Xorg.0.log
> file...maybe there is some clue there.
>
> -Richard

Gladly, could the problem be that i compiled with KDE with the DRI flag 
set on make.conf?, anyway here it goes:

Information about my grapchic card:    VGA compatible controller: VIA 
Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

System:    Sempron 2800 with 512 Mb of RAM

Kernel (uname -a):   Linux gentoo64 2.6.17-gentoo-r5 #1 Wed Aug 16 
12:27:04 UTC 2006 x86_64 AMD Sempron(tm) Processor 2800+ AuthenticAMD 
GNU/Linux

Xorg.o.log:

(II) VESA(0): Total Memory: 1024 64KB banks (65536kB)
(WW) VESA(0): config file hsync range 31.5-57kHz not within DDC hsync 
ranges.
(WW) VESA(0): config file vrefresh range 40-150Hz not within DDC 
vrefresh ranges.
(II) VESA(0): My Monitor: Using hsync range of 31.50-57.00 kHz
(II) VESA(0): My Monitor: Using vrefresh range of 40.00-150.00 Hz
(--) VESA(0): Virtual size is 1024x768 (pitch 1024)
(**) VESA(0): *Built-in mode "1024x768"
(**) VESA(0): *Built-in mode "800x600"
(**) VESA(0): *Built-in mode "640x480"
(--) VESA(0): Display dimensions: (280, 210) mm
(--) VESA(0): DPI set to (92, 92)
(WW) (1024x768,My Monitor) mode clock 94.5MHz exceeds DDC maximum 80MHz
(II) VESA(0): Attempting to use 70Hz refresh for mode "1024x768" (118)
(II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (115)
(II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (112)
(**) VESA(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib64/xorg/modules/libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.1.0
        ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.3
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
        [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0xfebffc00 - 0xfebffcff (0x100) MX[B]
        [5] -1  0       0xfebff800 - 0xfebff8ff (0x100) MX[B]
        [6] -1  0       0xd0000000 - 0xcfffffff (0x0) MX[B]O
        [7] -1  0       0xfeaf0000 - 0xfeafffff (0x10000) MX[B](B)
        [8] -1  0       0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
        [9] -1  0       0xf8000000 - 0xfbffffff (0x4000000) MX[B](B)
        [10] 0  0       0x000a0000 - 0x000affff (0x10000) MS[B]
        [11] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [12] 0  0       0x000b8000 - 0x000bffff (0x8000) MS[B]
        [13] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [14] -1 0       0x00000000 - 0x000000ff (0x100) IX[B]
        [15] -1 0       0x0000d400 - 0x0000d4ff (0x100) IX[B]
        [16] -1 0       0x0000d000 - 0x0000d0ff (0x100) IX[B]
        [17] -1 0       0x0000cc00 - 0x0000cc1f (0x20) IX[B]
        [18] -1 0       0x0000c800 - 0x0000c81f (0x20) IX[B]
        [19] -1 0       0x0000c400 - 0x0000c41f (0x20) IX[B]
        [20] -1 0       0x0000c000 - 0x0000c01f (0x20) IX[B]
        [21] -1 0       0x0000fc00 - 0x0000fc0f (0x10) IX[B]
        [22] -1 0       0x0000d800 - 0x0000d8ff (0x100) IX[B]
        [23] -1 0       0x0000dc00 - 0x0000dc0f (0x10) IX[B]
        [24] -1 0       0x0000e000 - 0x0000e003 (0x4) IX[B]
        [25] -1 0       0x0000e400 - 0x0000e407 (0x8) IX[B]
        [26] -1 0       0x0000e800 - 0x0000e803 (0x4) IX[B]
        [27] -1 0       0x0000ec00 - 0x0000ec07 (0x8) IX[B]
        [28] 0  0       0x000003b0 - 0x000003bb (0xc) IS[B]
        [29] 0  0       0x000003c0 - 0x000003df (0x20) IS[B]
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib64/xorg/modules/libint10.so
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 65536 kB
(II) VESA(0): VESA VBE OEM: VIA K8M800

(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor:
(II) VESA(0): VESA VBE OEM Product:
(II) VESA(0): VESA VBE OEM Product Rev:
(==) VESA(0): Write-combining range (0xf8000000,0x4000000)
(II) VESA(0): virtual address = 0x2b9561131000,
        physical address = 0xf8000000, size = 67108864
(II) VESA(0): VBESetVBEMode failed...Tried again without customized values.
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "Auto"
(**) Mouse1: Device: "/dev/psaux"
(**) Mouse1: Protocol: "Auto"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 9
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc104"
(**) Keyboard1: XkbModel: "pc104"
(**) Option "XkbLayout" "latin"
(**) Keyboard1: XkbLayout: "latin"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
    xkb_keycodes             { include "xfree86+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc104)+latin" };
    xkb_geometry             { include "pc(pc104)" };
(--) Mouse1: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/local/, removing from 
list!
FreeType: couldn't open face /usr/share/fonts/TTF/luximr.ttf: 1
FreeType: couldn't open face /usr/share/fonts/TTF/luximr.ttf: 1
    xkb_keycodes             { include "xfree86+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+es" };
    xkb_geometry             { include "pc(pc105)" };

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-02 10:53   ` Rafael Barrera Oro
@ 2006-11-02 19:50     ` Richard Fish
  2006-11-02 21:23       ` Benno Schulenberg
  0 siblings, 1 reply; 9+ messages in thread
From: Richard Fish @ 2006-11-02 19:50 UTC (permalink / raw
  To: gentoo-user

On 11/2/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
> Richard Fish wrote:
> > Not that I'm aware of.  Can you post your /var/log/Xorg.0.log
> > file...maybe there is some clue there.
> >
> > -Richard
>
> Gladly, could the problem be that i compiled with KDE with the DRI flag
> set on make.conf?, anyway here it goes:
>
> Information about my grapchic card:    VGA compatible controller: VIA
> Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

Hmm, your log looks incomplete.  The beginning of it should be some lines like:

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1

Regardless, it looks like you are using the vesa driver for your
hardware.  This is pretty much the lowest common denominator driver,
and will be *very* slow.  I'm not sure if you need the s3 or via
driver for your hardware (perhaps someone else with similar hardware
can comment).

What did you set VIDEO_CARDS to in /etc/make.conf?  This should
probably be something like:

VIDEO_CARDS="vesa s3 via"

If you have to change this setting, you need to remerge
x11-base/xorg-server.  I suggest to keep the vesa setting only to make
sure you have a recovery path if you make a mistake.

Once that is done, you should be able to change the Driver setting in
xorg.conf from "vesa" to "s3" (or "via").  The Driver setting to
change appears in the "Device" section.

-Richard
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-02 19:50     ` Richard Fish
@ 2006-11-02 21:23       ` Benno Schulenberg
  2006-11-03 12:22         ` Rafael Barrera Oro
  0 siblings, 1 reply; 9+ messages in thread
From: Benno Schulenberg @ 2006-11-02 21:23 UTC (permalink / raw
  To: gentoo-user

Richard Fish wrote:
> On 11/2/06, Rafael Barrera Oro <rafael@akyasociados.com.ar> wrote:
> > Information about my grapchic card:    VGA compatible
> > controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter
> > (rev 01)
>
> I'm not sure if you need the s3
> or via driver for your hardware

The via one.

OP, also show the output of 'lspci -vn' and 'lsmod'.

Benno
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-02 21:23       ` Benno Schulenberg
@ 2006-11-03 12:22         ` Rafael Barrera Oro
  2006-11-03 15:28           ` Rafael Barrera Oro
  2006-11-03 21:03           ` Benno Schulenberg
  0 siblings, 2 replies; 9+ messages in thread
From: Rafael Barrera Oro @ 2006-11-03 12:22 UTC (permalink / raw
  To: gentoo-user

Thanks for the advice people, here is a little more information about my 
settings:

VIDEO_CARDS="vesa vga fbdev"

after reading your suggestions, i was planning in replacing it with:

VIDEO_CARDS="vesa via s3 vga fbdev" (although i am not sure about s3)

Also, here is the output of lspci -vn:

00:00.0 0600: 1106:0204
        Subsystem: 1849:0204
        Flags: bus master, 66MHz, medium devsel, latency 8
        Memory at d0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [80] AGP version 3.0
        Capabilities: [50] Power Management version 2
        Capabilities: [60] HyperTransport: Slave or Primary Interface
        Capabilities: [58] HyperTransport: Interrupt Discovery and 
Configuration

00:00.1 0600: 1106:1204
        Subsystem: 1849:1204
        Flags: bus master, medium devsel, latency 0

00:00.2 0600: 1106:2204
        Subsystem: 1849:2204
        Flags: bus master, medium devsel, latency 0

00:00.3 0600: 1106:3204
        Subsystem: 1849:3204
        Flags: bus master, medium devsel, latency 0

00:00.4 0600: 1106:4204
        Subsystem: 1849:4204
        Flags: bus master, medium devsel, latency 0

00:00.7 0600: 1106:7204
        Subsystem: 1849:7204
        Flags: bus master, medium devsel, latency 0

00:01.0 0604: 1106:b188
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: fca00000-feafffff
        Prefetchable memory behind bridge: f4900000-fc8fffff
        Capabilities: [80] Power Management version 2

00:0f.0 0104: 1106:3149 (rev 80)
        Subsystem: 1849:3149
        Flags: bus master, medium devsel, latency 32, IRQ 17
        I/O ports at ec00 [size=8]
        I/O ports at e800 [size=4]
        I/O ports at e400 [size=8]
        I/O ports at e000 [size=4]
        I/O ports at dc00 [size=16]
        I/O ports at d800 [size=256]
        Capabilities: [c0] Power Management version 2

00:0f.1 0101: 1106:0571 (rev 06) (prog-if 8a)
        Subsystem: 1849:0571
        Flags: bus master, medium devsel, latency 32, IRQ 17
        I/O ports at fc00 [size=16]
        Capabilities: [c0] Power Management version 2

00:10.0 0c03: 1106:3038 (rev 81)
        Subsystem: 1849:3038
        Flags: bus master, medium devsel, latency 32, IRQ 16
        I/O ports at c000 [size=32]
        Capabilities: [80] Power Management version 2

00:10.1 0c03: 1106:3038 (rev 81)
        Subsystem: 1849:3038
        Flags: bus master, medium devsel, latency 32, IRQ 16
        I/O ports at c400 [size=32]
        Capabilities: [80] Power Management version 2

00:10.2 0c03: 1106:3038 (rev 81)
        Subsystem: 1849:3038
        Flags: bus master, medium devsel, latency 32, IRQ 16
        I/O ports at c800 [size=32]
        Capabilities: [80] Power Management version 2

00:10.3 0c03: 1106:3038 (rev 81)
        Subsystem: 1849:3038
        Flags: bus master, medium devsel, latency 32, IRQ 16
        I/O ports at cc00 [size=32]
        Capabilities: [80] Power Management version 2

00:10.4 0c03: 1106:3104 (rev 86) (prog-if 20)
        Subsystem: 1849:3104
        Flags: bus master, medium devsel, latency 32, IRQ 16
        Memory at febff800 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

00:11.0 0601: 1106:3227
        Subsystem: 1849:3227
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2

00:11.5 0401: 1106:3059 (rev 60)
        Subsystem: 1849:9761
        Flags: medium devsel, IRQ 18
        I/O ports at d000 [size=256]
        Capabilities: [c0] Power Management version 2

00:12.0 0200: 1106:3065 (rev 78)
        Subsystem: 1849:3065
        Flags: bus master, medium devsel, latency 32, IRQ 19
        I/O ports at d400 [size=256]
        Memory at febffc00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2

00:18.0 0600: 1022:1100
        Flags: fast devsel
        Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 0600: 1022:1101
        Flags: fast devsel

00:18.2 0600: 1022:1102
        Flags: fast devsel

00:18.3 0600: 1022:1103
        Flags: fast devsel

01:00.0 0300: 1106:3108 (rev 01)
        Subsystem: 1849:3108
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Expansion ROM at feaf0000 [disabled] [size=64K]
        Capabilities: [60] Power Management version 2
        Capabilities: [70] AGP version 3.0

Finally, the output of lsmod:

Module                  Size  Used by
snd_pcm_oss            44960  0
snd_mixer_oss          18816  2 snd_pcm_oss
snd_seq_dummy           4612  0
snd_seq_oss            34816  0
snd_seq_midi_event      8576  1 snd_seq_oss
snd_seq                55808  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
via_rhine              25348  0
mii                     6784  1 via_rhine
snd_via82xx            30504  2
gameport               16528  1 snd_via82xx
snd_ac97_codec        107608  1 snd_via82xx
snd_ac97_bus            3072  1 snd_ac97_codec
snd_pcm                94988  3 snd_pcm_oss,snd_via82xx,snd_ac97_codec
snd_timer              24968  2 snd_seq,snd_pcm
snd_page_alloc         11024  2 snd_via82xx,snd_pcm
snd_mpu401_uart         8704  1 snd_via82xx
snd_rawmidi            28064  1 snd_mpu401_uart
snd_seq_device          9744  4 
snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd                    62824  14 
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore              11424  2 snd
i2c_viapro             10264  0
via82cxxx               9732  0 [permanent]
nfs                   221744  1
lockd                  67216  2 nfs
sunrpc                168776  3 nfs,lockd
ata_piix               14212  0
sata_vsc                9732  0
sata_sis                9476  0
sata_sx4               14980  0
sata_nv                11652  0
sata_via                9988  0
sata_svw                9220  0
sata_sil               11912  0
sata_promise           13700  0
libata                 75288  9 
ata_piix,sata_vsc,sata_sis,sata_sx4,sata_nv,sata_via,sata_svw,sata_sil,sata_promise
sbp2                   25096  0
ohci1394               34504  0
ieee1394              106104  2 sbp2,ohci1394
ohci_hcd               21124  0
uhci_hcd               24088  0
usb_storage            71104  0
usbhid                 43040  0
ehci_hcd               33160  0


I am going to try reemerge xorg-server and changing the driver in 
Xorg.conf to via and see what happens, thanks for all your help, truly 
helpful

Sincerely

Rafael
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-03 12:22         ` Rafael Barrera Oro
@ 2006-11-03 15:28           ` Rafael Barrera Oro
  2006-11-03 21:03           ` Benno Schulenberg
  1 sibling, 0 replies; 9+ messages in thread
From: Rafael Barrera Oro @ 2006-11-03 15:28 UTC (permalink / raw
  To: gentoo-user

As i told i was planning to do before, i reemerged xorg-server adding 
"via" to VIDEO_CARDS and replacing "vesa" with "via" in 
/etc/X11/xorg.con, reseted my X server and things are fast again (to me 
it looks really fast, but maybe it could be i was gradually getting used 
to the slowness) and everything is working great, so far so good.

Thanks for all your help

Rafa
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [gentoo-user] Modular X.org issue (feelings of absolute failure)
  2006-11-03 12:22         ` Rafael Barrera Oro
  2006-11-03 15:28           ` Rafael Barrera Oro
@ 2006-11-03 21:03           ` Benno Schulenberg
  1 sibling, 0 replies; 9+ messages in thread
From: Benno Schulenberg @ 2006-11-03 21:03 UTC (permalink / raw
  To: gentoo-user

Rafael Barrera Oro wrote:
> VIDEO_CARDS="vesa via s3 vga fbdev" (although i am not sure about
> s3)

The s3 won't hurt, it'll just build something that won't get used, 
just like the vga and fbdev.  The vesa is nice to have as a 
fallback.

> 01:00.0 0300: 1106:3108 (rev 01)
>         Subsystem: 1849:3108

An ASRock board with a K8M800.  Too bad, 3D acceleration won't work: 
https://bugs.freedesktop.org/show_bug.cgi?id=5092

If you're content with how things are working now and don't intend 
to use 3D apps like Blender or ppracer, then you're done.  But if 
you would like to have at least the rudiments of 3D acceleration, 
then grep your kernel .config file for AGP and DRM and check that 
the following are set, and only these (to y or to m):

  CONFIG_AGP=y
  CONFIG_AGP_AMD64=y
  CONFIG_DRM=y
  CONFIG_DRM_VIA=y

You can set them under Device Drivers > Character Devices.

Store your current Xorg.0.log, then reboot with the new kernel and 
diff the old Xorg log with the new one to see what has changed.

When it works, you can try adding 'Option "EnableAGPDMA"' to 
'Section "Device"' in your /etc/X11/xorg.conf file to gain just a 
bit more responsiveness.

Benno
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2006-11-03 21:09 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <4548C6EF.7090800@akyasociados.com.ar>
2006-11-01 20:57 ` [gentoo-user] Modular X.org issue (feelings of absolute failure) Richard Fish
2006-11-01 22:59   ` b.n.
2006-11-02  7:43     ` Ow Mun Heng
2006-11-02 10:53   ` Rafael Barrera Oro
2006-11-02 19:50     ` Richard Fish
2006-11-02 21:23       ` Benno Schulenberg
2006-11-03 12:22         ` Rafael Barrera Oro
2006-11-03 15:28           ` Rafael Barrera Oro
2006-11-03 21:03           ` Benno Schulenberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox