View previous topic :: View next topic |
Author |
Message |
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Thu Feb 12, 2004 11:54 am Post subject: |
|
|
Hey guys! I also suffer from the Radeon IGP320M "problem". VERY new to gentoo, but not so new to linux. I read this entire thread, and I think i'm ready to tackle this. I have some questions before I start tho.
TriGun: You say that the love5 kernel has all the patches installed.
Does this mean, that I can emerge the love5 kernel, do a genkernel --config set the options that i need / want... (are there any i should stay away from).
Then, I can emerge the xfree-4.3.99.902.ebuild wait for that to compile (go out and build a pizza restaurant, then eat some pizza) Once it's compiled, reboot, and i should be able to run GLXGEARS and see something like ~450fps??
Am i reading that it's finally become this easy??
Please advise
~Jake
EDIT: I went looking through portage, and i couldnt find the love5 kernel... Is there another kernel I could use, ?? |
|
Back to top |
|
|
pakman Tux's lil' helper
Joined: 06 Jan 2004 Posts: 100
|
Posted: Thu Feb 12, 2004 7:01 pm Post subject: |
|
|
Heres the ebuild since its been removed from portage.
http://unixhead.org/docs/thinkpad/xfree-4.3.99.16.ebuild
Ya need to copy it to /usr/portage/x11-base/xfree/ then use the instructions a few pages back to get it patched. You'll need to run Code: | ebuild ./xfree-4.3.99.16.ebuild digest | before it'll let you compile/install.
I did port the patch over to the 4.3.0-r4 xfree, but it completely kills my display, even powering the backlight off, so hopefully its halfway through being integrated. Took bloody hours of compiling to get that right too!
I've not got DRM working with any xfree other than the above version with the patch from xfree.org. Am using 2.6 kernels with either the -love patch or -mm patch (since 2.6.1-mm2), both using different radeon drivers/patches but either works fine for me. |
|
Back to top |
|
|
sfb n00b
Joined: 12 Feb 2004 Posts: 6
|
Posted: Fri Feb 13, 2004 2:50 am Post subject: |
|
|
Code: |
chmod 777 /dev/dri
chmod 777 /dev/dri/card0
|
That's what I was missing!
I have dri working (at last), with an IGP340M.
Kernel 2.6.1 patched with the 2.6.1 IPG patch from consultmatt.co.uk, built with agpgart and radeon modules.
xfree-4.3.99.16 patched with the xfree patch from consultmatt.co.uk. (Thank you pakman for the link to the ebuild) |
|
Back to top |
|
|
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Fri Feb 13, 2004 10:32 pm Post subject: |
|
|
Just to recap packman, (thanks for the ebuild, BTW) but if i use the newest -mm kernel, I shouldnt have to patch a kernel??
~Jake |
|
Back to top |
|
|
pakman Tux's lil' helper
Joined: 06 Jan 2004 Posts: 100
|
Posted: Sat Feb 14, 2004 12:43 am Post subject: |
|
|
Jake: Other than applying the -mm patch you shouldn't need any others yep. I've got DRM running on 2.6.3-rc2-mm1 with a 340M.
If just the -mm patch doesn't work, check out the -love patchset which includes the http://consultmatt.co.uk igp stuff (and the -mm patch). Search the "Other things gentoo" forum for it, also has ebuilds knocking about which might make life a bit easier.
There is a kernel module included in XFree but its not installed by default, check a few pages back for instructions how to get it running. That might be useful if you don't want to change or patch kernels. Not sure how well it works though.
If you've got the wrong kernel module you'll get an error in /var/log/XFree86 just before it says "Direct Rendering Disabled" something like "mismatched fb location". Some older radeon igp modules have texture issues, the newest from consultmatt and -mm don't for me. |
|
Back to top |
|
|
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Sat Feb 14, 2004 12:58 am Post subject: |
|
|
to be honest, i'm new to patching things, i've never had to do any of that in the past... so here are some other questions that i pose to you... Looking at capnjameskirk's directions, i basically typed
Code: | emerge kernel-2.6.3-rc2-mm1 |
had a bunch of problems with the display on boot, but it booted... (wanted to make sure it booted before wasting my time recompiling X. I figure that the driver created by X that i will copy in should fix that.
Also, i found MTTR in the kernel, but was unable to locate /dev/agpgart in menuconfig... didnt think it would be too much of a problem. Also, i could not UNSELECT DRM, as it wasnt even an option in this kernel. After letting Genkernel finish, i rebooted to a garbled display, but it booted, as my previous version of X loaded correctly. then i started the XFREE Part of the HOWTO
got to the
Code: | patch --dry-run -Np0 < /home/jsylvia/radeon_igp/XFree-4.4-20031012-igp.patch |
and everything failed... Something about X out of X chunks failed, several times on the screen... I noticed that the ebuild that you posted was version xfree-4.3.99.16... and the ebuild he uses is xfree-4.3.99.14..
As i am new to this.. i dont know where to go from here... Any help... and much needed guidance.... would be appreciated.
~Jake |
|
Back to top |
|
|
pakman Tux's lil' helper
Joined: 06 Jan 2004 Posts: 100
|
Posted: Sat Feb 14, 2004 1:48 am Post subject: |
|
|
The xfree patch I'm using is from here: http://bugs.xfree.org/attachment.cgi?id=723&action=view
Check the guide by uberlord on the 3rd page of this thread for installation instructions for xfree. You did well to stop when you saw the rejected chunks, meaning the patch didn't change all the bits of code it wanted to, X compiles the radeon DRI stuff last so it wouldave taken about 2 hours before you got an error message and compile died
You need patched xfree and a radeon kernel module.
If you're going to use the kernel module supplied with X (it's not installed by default) you should be OK with any kernel. With your current kernel you can use the ati_agp and radeon modules that come with it and not worry about using xfree's kernel module, you still need to patch xfree to update its drivers though.
The kernel options are in device drivers->character devices. The ones you want are /dev/agpgart, Direct Rendering Manager, ATI Chipset support and radeon. I'd recommend doing them as modules (except DRM, won't allow you to choose it as a module) then you can replace/unload them later for testing.
Bit of extra advice, if you're using framebuffer (1024x768 console) don't use the radeon framebuffer module, use instead the vesa vga one. That might solve your garbled display. Only use support for 1 framebuffer too otherwise 2.6 cacks itself, with 2.4 you could compile them all in and it'd just use one, not any more. |
|
Back to top |
|
|
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Sat Feb 14, 2004 3:22 am Post subject: |
|
|
Thanks for the quick reply!!! I'll be looking into this as soon as i get back to my laptop tomorrow... I'll keep you... posted... hehe Thanks for all the help!! I really appreciate it.
~Jake |
|
Back to top |
|
|
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Sun Feb 15, 2004 10:12 pm Post subject: |
|
|
IT WORKS!!! Using pakman's advice above, and UberLord's directions on page 3 of this thread, 3D support is now fully operational on my Radeon IGP320M. Advice to future people... Read this thread completely before you try any of this, and dont be afraid to ask any of us for help.
Now all I have left is to get my W200 Wireless card working with my 2.6 kernel... Works perfectly in 2.4... Not quite sure why it isnt working now... Thats a problem for another post.
Thanks for all the help everyone!!
~Jake |
|
Back to top |
|
|
mizery de aria Guru
Joined: 07 Dec 2003 Posts: 309
|
Posted: Mon Feb 16, 2004 12:35 am Post subject: |
|
|
JSylvia007: What version of xfree do you have installed?
In /usr/portage/x11-base/xfree all I see are:
Code: | drwxr-xr-x 3 root root 4096 Feb 10 11:44 .
drwxr-xr-x 7 root root 4096 Feb 13 20:36 ..
-rw-r--r-- 1 root root 63634 Feb 10 11:44 ChangeLog
-rw-r--r-- 1 root root 1685 Feb 10 11:44 Manifest
drwxr-xr-x 3 root root 4096 Feb 13 19:56 files
-rw-r--r-- 1 root root 228 Jul 3 2003 metadata.xml
-rw-r--r-- 1 root root 23612 Feb 9 07:52 xfree-4.2.1-r3.ebuild
-rw-r--r-- 1 root root 34711 Feb 9 22:03 xfree-4.3.0-r4.ebuild
-rw-r--r-- 1 root root 31188 Feb 9 07:52 xfree-4.3.99.902-r1.ebuild |
I currently have 4.3.99.16 installed but I don't see it available for reinstall. How am I supposed to modify the ebuild to apply the reference to the patch? I believe I applied the patch last time I installed 4.3.99.16, so then I should be able to skip this step, right? _________________ Do not repIy to or othErwise communicate with me if you use religious, spiritual or similar terminologies or references in your typings. |
|
Back to top |
|
|
JSylvia007 Tux's lil' helper
Joined: 20 Oct 2003 Posts: 91 Location: USA East Coast
|
Posted: Mon Feb 16, 2004 1:01 am Post subject: |
|
|
Above is a link for the ebuild that you need to use.
~Jake |
|
Back to top |
|
|
Enderson Retired Dev
Joined: 12 Nov 2003 Posts: 141 Location: Arapiraca/Maceió, AL, Brazil
|
Posted: Mon Feb 16, 2004 1:00 pm Post subject: |
|
|
I read all the post and did all the tasks but I'm getting hits error at the dmesg
Code: |
# dmesg
...
radeon: no version for "struct_module" found: kernel tainted.
[drm] Initialized radeon 1.9.0 20020828 on minor 0
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda6, size 8192, journal first block 18, max tra
ns len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda6) for (hda6)
Using r5 hash to sort names
ohci1394: $Rev: 1087 $ Ben Collins <bcollins@debian.org>
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[d0007000-d00077ff] Max
Packet=[2048]
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ieee1394: Host added: ID:BUS[0-00:1023] GUID[000bcd719eec198b]
ttyS1 at I/O 0x8828 (irq = 3) is a 8250
ttyS2 at I/O 0x8840 (irq = 3) is a 8250
ttyS3 at I/O 0x8850 (irq = 3) is a 8250
ttyS4 at I/O 0x8860 (irq = 3) is a 8250
ttyS5 at I/O 0x8870 (irq = 3) is a 8250
agpgart: Detected Ati IGP320/M chipset
agpgart: Maximum main memory to use for agp memory: 379M
agpgart: AGP aperture is 64M @ 0xd4000000
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
blk: queue dbc92200, I/O limit 4095Mb (mask 0xffffffff)
mtrr: 0xe0000000,0x4000000 overlaps existing 0xe0000000,0x1000000
mtrr: 0xe0000000,0x4000000 overlaps existing 0xe0000000,0x1000000
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 4166 using kernel context 0
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
|
The part that says *ERROR*, what is that about?
The Xfree log:
Code: |
# cat /var/log/XFree86.0.log | grep -i radeon
(--) PCI:*(1:5:0) ATI Technologies Inc Radeon Mobility U1 rev 0, Mem @ 0xe0000000/28, 0xd0100000/16, I/O @ 0x9000/8
(II) LoadModule: "radeon"
(II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) Module radeon: vendor="The XFree86 Project"
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),
ATI Radeon Mobility M7 LW (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330/340/350 (A4) 4137,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP),
ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP),
ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP),
ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP),
ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600 (M10) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M11) NV (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP)
(--) Chipset ATI Radeon IGP320M (U1) 4336 found
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) RADEON(0): MMIO registers at 0xd0100000
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) RADEON(0): PCI bus 1 card 5 func 0
(**) RADEON(0): Depth 16, (--) framebuffer bpp 16
(II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Option "EnablePageFlip" "on"
(==) RADEON(0): RGB weight 565
(II) RADEON(0): Using 6 bits per RGB (8 bit DAC)
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon IGP320M (U1) 4336" (ChipID = 0x4336)
(--) RADEON(0): Linear framebuffer at 0xe0000000
(--) RADEON(0): VideoRAM: 65536 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Non-DDC laptop panel detected
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Displays Detected: Monitor1--Type 2, Monitor2--Type 0
(II) RADEON(0):
(II) RADEON(0): Primary Display == Type 2
(II) RADEON(0): Panel ID string: 1024x768
(II) RADEON(0): Panel Size from BIOS: 1024x768
(II) RADEON(0): BIOS provided dividers will be used.
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Total number of valid DDC mode(s) found: 0
(WW) RADEON(0): Mode 1024x786 800x600 is out of range.
(WW) RADEON(0): Valid modes must be between 320x200-1024x768
(II) RADEON(0): No valid mode specified, force to native mdoe
(II) RADEON(0): Total number of valid FP mode(s) found: 1
(--) RADEON(0): Virtual size is 1024x768 (pitch 1024)
(**) RADEON(0): *Mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "1024x768" 65.00 1024 1040 1176 1344 768 770 776 806
(**) RADEON(0): Default mode "640x350": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "640x350" 65.00 640 1040 1176 1344 350 770 776 806
(**) RADEON(0): Default mode "640x400": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "640x400" 65.00 640 1040 1176 1344 400 770 776 806
(**) RADEON(0): Default mode "720x400": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "720x400" 65.00 720 1040 1176 1344 400 770 776 806
(**) RADEON(0): Default mode "640x480": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "640x480" 65.00 640 1040 1176 1344 480 770 776 806
(**) RADEON(0): Default mode "800x600": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "800x600" 65.00 800 1040 1176 1344 600 770 776 806
(**) RADEON(0): Default mode "832x624": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) RADEON(0): Modeline "832x624" 65.00 832 1040 1176 1344 624 770 776 806
(==) RADEON(0): DPI set to (75, 75)
(**) RADEON(0): AGP 4x mode is configured
(II) RADEON(0): AGP Fast Write disabled by default
(II) RADEON(0): Depth moves disabled by default
(II) RADEON(0): Page flipping enabled
(!!) RADEON(0): For information on using the multimedia capabilities
(WW) RADEON(0): Failed to set up write-combining range (0xe0000000,0x4000000)
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xdda8c000
(II) RADEON(0): [drm] mapped SAREA 0xdda8c000 to 0x4426f000
(II) RADEON(0): [drm] framebuffer handle = 0xe0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xdda8c000 at 0x4426f000
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7413
(II) RADEON(0): Direct rendering disabled
|
What could be the problem, I'm using vanilla 2.6.1 with patches.
I'd like to know if it's a XFree or a kernel problem, if it's kernel, I can try the mm or love sources.
Suggestions? _________________ --
Nothing to say here! |
|
Back to top |
|
|
Enderson Retired Dev
Joined: 12 Nov 2003 Posts: 141 Location: Arapiraca/Maceió, AL, Brazil
|
Posted: Tue Feb 17, 2004 1:00 pm Post subject: |
|
|
I compiled the mm-sources 2.6.3-rc2-mm1 and the Direct Rendering worked OK for me,
I played Quake3 ithout problems. I`m getting ~500 with glxgears.
But I have the problems os synaptics drivers and acpi.
If I don`t put acpi=off the boot freezes.
And the touchpad isn`t working too.
Anyone with these problems?
I have a HP compaq nx 9005. _________________ --
Nothing to say here! |
|
Back to top |
|
|
mizery de aria Guru
Joined: 07 Dec 2003 Posts: 309
|
Posted: Tue Feb 17, 2004 4:19 pm Post subject: |
|
|
blargh, I'm using 2.6.3-rc2-mm kernel as well, but I don't have direct rendering working yet. I followed the steps in this thread several times and have been trying for 2 months, with no luck at all. _________________ Do not repIy to or othErwise communicate with me if you use religious, spiritual or similar terminologies or references in your typings. |
|
Back to top |
|
|
shard n00b
Joined: 22 May 2003 Posts: 11 Location: Sydney, Australia
|
Posted: Wed Feb 18, 2004 2:16 am Post subject: |
|
|
all of the patches to enable direct rendering on a IGP 320/340M have been checked into dri-cvs. Head over to
http://dri.sourceforge.net/cgi-bin/moin.cgi/
and check it out. I'm using a 2.6.2 kernel (vanilla/unpatched) with dri-cvs and am getting ~550fps in glxgears. _________________ somehow this should all make sense.. |
|
Back to top |
|
|
pakman Tux's lil' helper
Joined: 06 Jan 2004 Posts: 100
|
Posted: Wed Feb 18, 2004 4:45 pm Post subject: |
|
|
shard wrote: | all of the patches to enable direct rendering on a IGP 320/340M have been checked into dri-cvs. |
Which version of xfree are you using, the current one in portage (4.3.0-r5)?
That would certainly make the guide to getting IGP working easier, would now be:
1) install dri. |
|
Back to top |
|
|
mizery de aria Guru
Joined: 07 Dec 2003 Posts: 309
|
Posted: Wed Feb 18, 2004 9:21 pm Post subject: |
|
|
shard wrote: | all of the patches to enable direct rendering on a IGP 320/340M have been checked into dri-cvs. |
That means that the next stable release of dri, when installed, should increase the likelihood that my system has direct rendering capabilities. Right?
If so, I guess I'll wait until it's released. _________________ Do not repIy to or othErwise communicate with me if you use religious, spiritual or similar terminologies or references in your typings. |
|
Back to top |
|
|
tolly n00b
Joined: 03 Jan 2004 Posts: 13
|
Posted: Thu Feb 19, 2004 2:21 am Post subject: Got GL working |
|
|
I've got 3d working, however in the default window size of glxgears, I only get 200FPS. Is this ok? I am wondering why everyone else get ~450. I have an IGP320M using 64Mb of my DDR.
Is thjs normal, or can I increase it?
Tolly
If you need to see my logs, please ask.
Gentoo 1.4
2.6.3-rc2-love2
XFree86 4.3.99.16 |
|
Back to top |
|
|
Squinky86 Retired Dev
Joined: 25 Mar 2003 Posts: 309 Location: Alabama, USA
|
Posted: Thu Feb 19, 2004 2:56 am Post subject: Re: Got GL working |
|
|
tolly wrote: | I've got 3d working, however in the default window size of glxgears, I only get 200FPS. Is this ok? I am wondering why everyone else get ~450. I have an IGP320M using 64Mb of my DDR. |
Type Code: | glxinfo | grep direct | and if it says Code: | direct rendering: Yes | you probably have nothing to worry about.
That being said, I'd like to report yet another success story. After days of playing with it, I finally unmerged the ati-drivers that I forgot I still had laying around and everything worked great. IGP 340M on a Compaq Presario 2590us with ati-agp and radeon modules in /etc/modules.autoload.d/kernel-2.6. ut2003/2004-demo works great, and so does full ut2003, with a few weird color/font things that's probably on my end. _________________ Me |
|
Back to top |
|
|
tolly n00b
Joined: 03 Jan 2004 Posts: 13
|
Posted: Thu Feb 19, 2004 3:34 am Post subject: Glxgears... |
|
|
Yeah, I def. have GL working, but I was curious as to why other laptops with their integrated graphics are getting ~2.5x my glxgears. When I am compiling @ ~100% CPU, I still get ~200FPS, so I know its not getting bogged down by my processor. I know that glxgears is not a good indicator, but any ideas?
(for all those having problems, I complely removed all versions of X, including the bits that portage doesn't remove, and it worked.)
Tolly |
|
Back to top |
|
|
amigafan Tux's lil' helper
Joined: 10 Jul 2003 Posts: 134 Location: Ahrensburg, Germany
|
Posted: Thu Feb 19, 2004 7:08 pm Post subject: |
|
|
If your synaptics touchpad doesn't work as expected after a switch from xfree4.3 to 4.3.99xx simply do an "emerge synaptics". In my case the tip to click feature and the scrolling doesn't work - now it does |
|
Back to top |
|
|
Enderson Retired Dev
Joined: 12 Nov 2003 Posts: 141 Location: Arapiraca/Maceió, AL, Brazil
|
Posted: Fri Feb 20, 2004 12:23 am Post subject: |
|
|
The xfree-drm in portage doesn't support kernel 2.6.
when the IGP 320M will be avaliable in the xfree-drm with 2.6 support? _________________ --
Nothing to say here! |
|
Back to top |
|
|
_danno n00b
Joined: 08 Nov 2003 Posts: 17 Location: Michigan, USA
|
Posted: Wed Feb 25, 2004 4:11 am Post subject: |
|
|
hey guys,
i was wondering if someone who got their 340M working using a love-sources kernel could help a newbie out and put up like a condensed howto of what they did? looking through this whole thread, theres so many different things going on i don't know what to do. thanks a lot |
|
Back to top |
|
|
mattix n00b
Joined: 25 Feb 2004 Posts: 1
|
Posted: Wed Feb 25, 2004 5:50 pm Post subject: |
|
|
Just now got it working!
Used the patched xfree-4.3.99-16 ebuild. Used latest mm-sources kernel (2.6.3-mm3), with agpgart, ati agp, and radeon all compiled as modules, and I use the kernel radeon module, not the patched xfree one.
One thing that I've not seen mentioned, the agpgart and ati_agp (or whatever agp module you use) MUST be loaded BEFORE the radeon module. I just now figured that out. So in /etc/modules.autoload.d/kernel-2.6 I have agpgart first, then ati_agp, then radeon. |
|
Back to top |
|
|
Enderson Retired Dev
Joined: 12 Nov 2003 Posts: 141 Location: Arapiraca/Maceió, AL, Brazil
|
Posted: Fri Feb 27, 2004 12:18 am Post subject: |
|
|
I installed 2.6.3-mm4 and the patched xfree-4.3.99.16 and it's working, but I only get
~200fps with glxgears, I can play Quake3 but not the best performance. _________________ --
Nothing to say here! |
|
Back to top |
|
|
|
|
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
|
|