Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Radeon KMS and X with 2.6.31
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 336
Location: Stockholm, Sweden

PostPosted: Wed Sep 16, 2009 3:33 pm    Post subject: Reply with quote

I really look forward to seeing this on my ATI Radeon 4850...
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
Lori
Apprentice
Apprentice


Joined: 30 Mar 2004
Posts: 265
Location: Barcelona, Spain

PostPosted: Wed Sep 16, 2009 6:54 pm    Post subject: Reply with quote

azp wrote:
I really look forward to seeing this on my ATI Radeon 4850...


You'll have to wait for 2.6.32 (but you can start cheking out the first release candidates, after the merge window closes :P).
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2352
Location: Austria

PostPosted: Wed Sep 16, 2009 9:02 pm    Post subject: Reply with quote

Or you jump right into the merge window like I did. ^^
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 336
Location: Stockholm, Sweden

PostPosted: Wed Sep 16, 2009 11:25 pm    Post subject: Reply with quote

Haha I guess both is a good idea, but I think I'll wait at least until -rc4 or -rc5 :D
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
wdicc
n00b
n00b


Joined: 13 Mar 2008
Posts: 47

PostPosted: Fri Sep 18, 2009 1:49 pm    Post subject: Reply with quote

I've enabled KMS on my radeon X300.

$ glxinfo |grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV380 5460) 20090101 x86/MMX/SSE2 TCL DRI2

But the performance really slow. Only got 400 FPS in glxgears. I can get 1500 FPS after disable KMS. :cry: :cry:
Back to top
View user's profile Send private message
widremann
Veteran
Veteran


Joined: 14 Mar 2005
Posts: 1314

PostPosted: Fri Sep 18, 2009 2:02 pm    Post subject: Reply with quote

wdicc wrote:
I've enabled KMS on my radeon X300.

$ glxinfo |grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV380 5460) 20090101 x86/MMX/SSE2 TCL DRI2

But the performance really slow. Only got 400 FPS in glxgears. I can get 1500 FPS after disable KMS. :cry: :cry:

glxgears is not a benchmark.
Back to top
View user's profile Send private message
wdicc
n00b
n00b


Joined: 13 Mar 2008
Posts: 47

PostPosted: Fri Sep 18, 2009 11:02 pm    Post subject: Reply with quote

widremann wrote:
wdicc wrote:
I've enabled KMS on my radeon X300.

$ glxinfo |grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV380 5460) 20090101 x86/MMX/SSE2 TCL DRI2

But the performance really slow. Only got 400 FPS in glxgears. I can get 1500 FPS after disable KMS. :cry: :cry:

glxgears is not a benchmark.



But it can be a reference right ?
It's slow when switch between app like firefox and roxterm, and even switch between tabs in roxterm. 8O
Back to top
View user's profile Send private message
octoploid
n00b
n00b


Joined: 21 Oct 2006
Posts: 65

PostPosted: Tue Sep 22, 2009 6:52 am    Post subject: Reply with quote

This is great.
Everything works fine with my (build in) RS780 (Radeon HD 3300).
I use a rotated monitor normally and even this setup is supported.
Just put »vga=0xF06 fbcon=rotate:3« into your grub.cfg and you'll
get a fb-console in portrait mode.

The only thing that's missing is IRQ support, but the developers are
working on it.
_________________
Myself and mine gymnastic ever
Back to top
View user's profile Send private message
widremann
Veteran
Veteran


Joined: 14 Mar 2005
Posts: 1314

PostPosted: Tue Sep 22, 2009 2:57 pm    Post subject: Reply with quote

wdicc wrote:
widremann wrote:
wdicc wrote:
I've enabled KMS on my radeon X300.

$ glxinfo |grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV380 5460) 20090101 x86/MMX/SSE2 TCL DRI2

But the performance really slow. Only got 400 FPS in glxgears. I can get 1500 FPS after disable KMS. :cry: :cry:

glxgears is not a benchmark.



But it can be a reference right ?
It's slow when switch between app like firefox and roxterm, and even switch between tabs in roxterm. 8O

Are you using Compiz? If not, then the problem lies elsewhere. Glxgears doesn't measure drawing performance, and even if it did, it would be 3d drawing performance, not 2d, which uses a different code path (sort of).
Back to top
View user's profile Send private message
Lori
Apprentice
Apprentice


Joined: 30 Mar 2004
Posts: 265
Location: Barcelona, Spain

PostPosted: Fri Sep 25, 2009 2:18 am    Post subject: Reply with quote

Out of curiosity I made some 2D benchmarks using GTKperf comparing KMS and non-KMS based X. I disabled the xdm service, I booted my system, and as root I just ran xinit, so no window manager was running and no GTK theme was used either. I used the following command line:
Code:
gtkperf -a -c 1000


Here are the results for my KMS setup:
Code:
tkEntry - time:  0.34
GtkComboBox - time: 37.27
GtkComboBoxEntry - time: 25.47
GtkSpinButton - time:  5.24
GtkProgressBar - time:  1.29
GtkToggleButton - time: 12.02
GtkCheckButton - time: 10.64
GtkRadioButton - time: 11.91
GtkTextView - Add text - time: 30.83
GtkTextView - Scroll - time: 26.74
GtkDrawingArea - Lines - time:  8.70
GtkDrawingArea - Circles - time: 14.52
GtkDrawingArea - Text - time: 14.50
GtkDrawingArea - Pixbufs - time:  0.95
 ---
Total time: 200.43


Then I put radeon.modeset=0 on the kernel boot line, and repeated the test. I got almost double overall speed:
Code:
GtkEntry - time:  0.28
GtkComboBox - time: 16.66
GtkComboBoxEntry - time: 11.93
GtkSpinButton - time:  2.05
GtkProgressBar - time:  1.25
GtkToggleButton - time:  5.01
GtkCheckButton - time:  3.97
GtkRadioButton - time:  5.01
GtkTextView - Add text - time: 29.31
GtkTextView - Scroll - time: 12.72
GtkDrawingArea - Lines - time:  6.81
GtkDrawingArea - Circles - time:  7.76
GtkDrawingArea - Text - time: 11.08
GtkDrawingArea - Pixbufs - time:  0.84
 ---
Total time: 114.67


So, it seems that KMS performance is still lagging behind, at least with this test.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911
Back to top
View user's profile Send private message
node@are-b.org
n00b
n00b


Joined: 20 Apr 2005
Posts: 44

PostPosted: Sun Oct 04, 2009 10:56 pm    Post subject: KMS on r300 with current ebuilds Reply with quote

From what I read on http://p-static.blogspot.com/2009/08/radeon-kms-on-gentoo-almost.html the current versions of packages should be sufficient to do KMS. To summarize I have the following:

Step 1: Kernel, at least 2.6.31:
erin ~ # uname -a
Linux erin 2.6.31-gentoo-r1 #5 PREEMPT Sun Oct 4 11:45:32 CEST 2009 x86_64 AMD Athlon(tm) 64 Processor 2800+ AuthenticAMD GNU/Linux
Code:

[    6.843210] [drm] radeon default to kernel modesetting.
[    6.843216] [drm] radeon kernel modesetting enabled.
[    6.843323] radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[    6.848546] [drm] radeon: Initializing kernel modesetting.
[    6.848580] [drm] register mmio base: 0xFD400000
[    6.848584] [drm] register mmio size: 65536
[    6.904843] [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
[    6.904854] [drm] Clocks initialized !
[    6.904860] [drm] Generation 2 PCI interface, using max accessible memory
[    6.905064] [drm] Detected VRAM RAM=128M, BAR=128M
[    6.905071] [drm] RAM width 64bits DDR
[    6.905305] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[    6.905319] agpgart-amd64 0000:00:00.0: AGP 3.5 bridge
[    6.905346] agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
[    6.905424] radeon 0000:01:00.0: putting AGP V3 device into 8x mode
[    6.905433] [drm] radeon: VRAM 128M
[    6.905437] [drm] radeon: VRAM from 0x00000000 to 0x07FFFFFF
[    6.905440] [drm] radeon: GTT 64M
[    6.905444] [drm] radeon: GTT from 0xF8000000 to 0xFBFFFFFF
[    7.078260] [drm] radeon: irq initialized.
[    7.078305] [TTM] TTM available graphics memory: 501 MiB
[    7.078307] [TTM] TTM available object memory: 501 MiB
[    7.078329] [drm] radeon: 128M of VRAM memory ready
[    7.078332] [drm] radeon: 64M of GTT memory ready.
[    7.078349] [drm] radeon: cp idle (0x10000C03)
[    7.078353] [drm] Loading R300 Microcode
[    7.081001] [drm] radeon: ring at 0x00000000F8000000
[    7.081021] [drm] ring test succeeded in 1 usecs
[    7.083573] [drm] radeon: ib pool ready.
[    7.083652] [drm] ib test succeeded in 0 usecs
[    7.084377] [drm] DFP table revision: 3
[    7.084778] [drm] Radeon Display Connectors
[    7.084780] [drm] Connector 0:
[    7.084782] [drm]   VGA
[    7.084785] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[    7.084787] [drm]   Encoders:
[    7.084788] [drm]     CRT1: INTERNAL_DAC1
[    7.084790] [drm] Connector 1:
[    7.084792] [drm]   DVI-I
[    7.084794] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[    7.084796] [drm]   Encoders:
[    7.084798] [drm]     CRT2: INTERNAL_DAC2
[    7.084800] [drm]     DFP1: INTERNAL_TMDS1
[    7.086726] i2c-adapter i2c-1: unable to read EDID block.
[    7.086729] radeon 0000:01:00.0: VGA-1: no EDID data
[    7.473823] [drm] fb mappable at 0xE0040000
[    7.473827] [drm] vram apper at 0xE0000000
[    7.473830] [drm] size 3932160
[    7.473831] [drm] fb depth is 24
[    7.473833] [drm]    pitch is 5120
[    7.526123] [drm] TMDS-8: set mode 1280x768 13
[    7.585322] Console: switching to colour frame buffer device 160x48
[    7.644479] fb0: radeondrmfb frame buffer device
[    7.644482] registered panic notifier
[    7.644484] [drm] radeon: kernel modesetting successfully initialized.
[    7.644489] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0

Looks perfect to me? Check.

Step 2: libdrm, at least 2.4.12 with the configure setting:
[ebuild R ] x11-libs/libdrm-2.4.14 USE="-debug" 0 kB
which the ebuild includes, the build log reads, ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --prefix=/usr --datadir=/usr/share --enable-udev --enable-nouveau-experimental-api --enable-radeon-experimental-api, so that should be ok.

Step 3: xf86-video-ati, from git (or newer than 6.12.2):
[ebuild R ] x11-drivers/xf86-video-ati-6.12.4 USE="-debug" 0 kB
should hopefully be enough? No specifics on that part.

Step 4: Mesa, at least 7.5:
[ebuild R ] media-libs/mesa-7.5.2 USE="nptl xcb -debug -motif -pic" VIDEO_CARDS="radeon -intel -mach64 -mga -none -r128 -radeonhd -s3virge -savage -sis (-sunffb) -tdfx -trident -via" 0 kB
Also, check.


So I don't know what else i'm missing, the box seems to start nicely and everything, my X.Org X Server 1.6.4 log reads things like the following though:
Code:

(**) Option "AIGLX" "off" (did this on purpouse)
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded by default.
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.6.4, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(**) AIGLX disabled
<snip>
(**) RADEON(0): Option "EnablePageFlip" "on"
(**) RADEON(0): Option "AccelDFS" "on"
(**) RADEON(0): Option "AccelMethod" "EXA"
(**) RADEON(0): Option "TVStandard" "PAL"
<snip> A summory of my xorg config basically
(II) RADEON(0): Legacy BIOS detected
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] radeon kernel module version is 2.0.0 but version 1.17.0 or newer is needed.
[dri] Disabling DRI.
<snip> If I enable AIGLX i get about 20 of the open attempts, and a different kind of failure, but AIGLX is not important to me (yet).
(II) RADEON(0): TV standards supported by chip: NTSC PAL
(EE) RADEON(0): Invalid TV Standard: PAL
<snip> this makes me lol sorta, a bug i'm sure.


So I'm sure there's a bug somewhere, but I've always learned in school that 2 > 1 so it seems that maybe the check only checks 1.* versions? If that's the only reason DRI gets disabled, hopefully a quick fix will make it all better?
Back to top
View user's profile Send private message
jakubo
n00b
n00b


Joined: 08 Oct 2009
Posts: 2

PostPosted: Thu Oct 08, 2009 7:46 pm    Post subject: Reply with quote

hi,
i also got performance issues on radeon+KMS
im a bit new on gentoo

could it be that the driver has fallen back to software rasterizer???
for me it did
Code:

OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.5.2
OpenGL shading language version string: 1.20


but on dmesg is a certain problem that might be the answer to it, however i dont rally know how to get rid of it
Code:

[    7.624672] ------------[ cut here ]------------
[    7.624679] WARNING: at lib/dma-debug.c:787 check_unmap+0xb6/0x5d2()
[    7.624682] Hardware name: 939Dual-VSTA
[    7.624684] p54pci 0000:04:07.0: DMA-API: device driver tries to free an invalid DMA memory address
[    7.624686] Modules linked in: snd_rawmidi v4l2_common radeon(+) snd_ac97_codec videodev v4l1_compat ac97_bus v4l2_compat_ioctl32 p54pci(+) ttm drm i2c_algo_bit snd_pcm snd_page_alloc videobuf_dma_sg p54common snd_util_mem videobuf_core snd_hwdep cfbcopyarea tveeprom cfbimgblt cfbfillrect
[    7.624703] Pid: 4043, comm: modprobe Not tainted 2.6.31-gentoo-r2 #3
[    7.624705] Call Trace:
[    7.624707]  <IRQ>  [<ffffffff81268bf4>] ? check_unmap+0xb6/0x5d2
[    7.624715]  [<ffffffff81053e6a>] warn_slowpath_common+0x77/0xa4
[    7.624719]  [<ffffffff81053f0c>] warn_slowpath_fmt+0x64/0x66
[    7.624724]  [<ffffffff812dcf91>] ? put_device+0x12/0x14
[    7.624728]  [<ffffffff812fd4ea>] ? scsi_request_fn+0x335/0x3e3
[    7.624731]  [<ffffffff81268bf4>] check_unmap+0xb6/0x5d2
[    7.624735]  [<ffffffff812fcd3c>] ? scsi_run_queue+0x1f4/0x252
[    7.624738]  [<ffffffff81269287>] debug_dma_unmap_page+0x51/0x53
[    7.624745]  [<ffffffffa008c306>] pci_unmap_single+0x6d/0x76 [p54pci]
[    7.624750]  [<ffffffffa008c9e4>] p54p_check_tx_ring+0x97/0xd1 [p54pci]
[    7.624755]  [<ffffffffa008ca90>] p54p_interrupt+0x72/0xdc [p54pci]
[    7.624760]  [<ffffffff810904bc>] handle_IRQ_event+0x5b/0x12d
[    7.624764]  [<ffffffff810917e1>] handle_fasteoi_irq+0x5b/0x87
[    7.624768]  [<ffffffff8102899b>] handle_irq+0x87/0x90
[    7.624772]  [<ffffffff810283aa>] do_IRQ+0x46/0x9e
[    7.624775]  [<ffffffff81027313>] ret_from_intr+0x0/0x9
[    7.624777]  <EOI>  [<ffffffffa000319d>] ? cfb_imageblit+0x19d/0x464 [cfbimgblt]
[    7.624785]  [<ffffffff812a5340>] ? bit_putcs+0x438/0x4a0
[    7.624789]  [<ffffffff8129f89b>] ? fbcon_clear_margins+0x3b/0x3d
[    7.624793]  [<ffffffff812a04cb>] ? fbcon_putcs+0xc1/0xd0
[    7.624796]  [<ffffffff812a4f08>] ? bit_putcs+0x0/0x4a0
[    7.624800]  [<ffffffff8128c60e>] ? do_update_region+0xd4/0x114
[    7.624804]  [<ffffffff8128f00d>] ? redraw_screen+0x14f/0x1ac
[    7.624808]  [<ffffffff8128f2e5>] ? bind_con_driver+0x27b/0x2af
[    7.624812]  [<ffffffff8128f352>] ? take_over_console+0x39/0x48
[    7.624815]  [<ffffffff812a3b68>] ? fbcon_takeover+0x61/0xc5
[    7.624819]  [<ffffffff812a426c>] ? fbcon_event_notify+0x32f/0x68b
[    7.624824]  [<ffffffff812575da>] ? ida_get_new_above+0xdd/0x1af
[    7.624828]  [<ffffffff81124ad4>] ? sysfs_ilookup_test+0x0/0x14
[    7.624832]  [<ffffffff81124ce3>] ? sysfs_find_dirent+0x1c/0x31
[    7.624836]  [<ffffffff811251d4>] ? sysfs_addrm_finish+0x20/0x1db
[    7.624839]  [<ffffffff81124ebc>] ? sysfs_add_one+0x1c/0xe6
[    7.624845]  [<ffffffff814ebd62>] ? notifier_call_chain+0x33/0x5b
[    7.624849]  [<ffffffff8106a057>] ? __blocking_notifier_call_chain+0x4d/0x6a
[    7.624853]  [<ffffffff8106a083>] ? blocking_notifier_call_chain+0xf/0x11
[    7.624858]  [<ffffffff81298302>] ? fb_notifier_call_chain+0x16/0x18
[    7.624862]  [<ffffffff81299314>] ? register_framebuffer+0x307/0x326
[    7.624884]  [<ffffffffa005e038>] ? drm_mode_create+0x32/0x3a [drm]
[    7.624918]  [<ffffffffa00fc203>] ? radeonfb_probe+0x2be/0x330 [radeon]
[    7.624933]  [<ffffffffa0061f59>] ? drm_helper_initial_config+0x174/0x182 [drm]
[    7.624957]  [<ffffffffa00f9459>] ? radeon_modeset_init+0x180/0x18f [radeon]
[    7.624976]  [<ffffffffa00e80ac>] ? radeon_device_init+0x4fa/0x552 [radeon]
[    7.624995]  [<ffffffffa00e8812>] ? radeon_driver_load_kms+0xb5/0xf7 [radeon]
[    7.625002]  [<ffffffffa0059ef0>] ? drm_get_dev+0x329/0x415 [drm]
[    7.625032]  [<ffffffffa010a1a2>] ? radeon_pci_probe+0x10/0x263 [radeon]
[    7.625036]  [<ffffffff8126f36f>] ? local_pci_probe+0x12/0x16
[    7.625040]  [<ffffffff8126ffd9>] ? pci_device_probe+0x5c/0x86
[    7.625044]  [<ffffffff812e00ce>] ? driver_sysfs_add+0x4c/0x72
[    7.625048]  [<ffffffff812e0203>] ? driver_probe_device+0x96/0x13a
[    7.625052]  [<ffffffff812e02ff>] ? __driver_attach+0x58/0x7b
[    7.625055]  [<ffffffff812e02a7>] ? __driver_attach+0x0/0x7b
[    7.625059]  [<ffffffff812dfb15>] ? bus_for_each_dev+0x4e/0x84
[    7.625062]  [<ffffffff812e0080>] ? driver_attach+0x1c/0x1e
[    7.625066]  [<ffffffff812df487>] ? bus_add_driver+0xb8/0x201
[    7.625070]  [<ffffffff812e05d6>] ? driver_register+0xb3/0x121
[    7.625073]  [<ffffffff8127036d>] ? __pci_register_driver+0x47/0xb2
[    7.625091]  [<ffffffffa016e000>] ? radeon_init+0x0/0xc1 [radeon]
[    7.625104]  [<ffffffffa0055fee>] ? drm_init+0x6b/0xd1 [drm]
[    7.625122]  [<ffffffffa016e000>] ? radeon_init+0x0/0xc1 [radeon]
[    7.625138]  [<ffffffffa016e0bf>] ? radeon_init+0xbf/0xc1 [radeon]
[    7.625142]  [<ffffffff81009055>] ? do_one_initcall+0x55/0x14a
[    7.625147]  [<ffffffff810780ea>] ? sys_init_module+0xd0/0x202
[    7.625151]  [<ffffffff81026968>] ? system_call_fastpath+0x16/0x1b
[    7.625154] ---[ end trace 5cb596e10ad075a2 ]---
[    7.661902] fb0: radeondrmfb frame buffer device
[    7.661906] registered panic notifier
[    7.661908] [drm] radeon: kernel modesetting successfully initialized.
[    7.661913] [drm] Initialized radeon 2.0.0 20080528 for 0000:03:00.0 on minor 0


everything before and after seems ok..
Back to top
View user's profile Send private message
node@are-b.org
n00b
n00b


Joined: 20 Apr 2005
Posts: 44

PostPosted: Thu Oct 08, 2009 11:39 pm    Post subject: Reply with quote

That looks like a pretty bad crash :( i notice you have a -r2 kernel, i'm gonna upgrade to that one and see if I get that also.
Back to top
View user's profile Send private message
jakubo
n00b
n00b


Joined: 08 Oct 2009
Posts: 2

PostPosted: Fri Oct 09, 2009 2:29 am    Post subject: Reply with quote

its not a crash as such... i guess it has something to do with the failed dri enabling, which is described here:
Xorg.0.log
Code:

(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] radeon kernel module version is 2.0.0 but version 1.17.0 or newer is needed.
[dri] Disabling DRI.


it could be also some misconfiguration in kernel as p54pci is my wireless adapter.
so i dont know yyet if the driver isnt ready yet, or if i made a mistake
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
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