View previous topic :: View next topic |
Author |
Message |
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Fri Jul 21, 2006 5:39 am Post subject: SOLVED Upgrade X >7.0 Need hlp driver/conf. ATI 3D RAGE P |
|
|
I am trying to upgrade my system from the old X-Windows to the new Modular X 7.0. The system is an old Celeron box with an ONBOARD (thus not easily changed) ATI 3D Rage Pro card.
I followed the instructions in the Modular X HOWTO guide, and didn't have any major issues. However, my new installation won't work. I give the "startx" command (as a user, but I don't think that doing it as root would change anything), the screen goes blank and then comes back to the command line with a bunch of error messages...
Initially I tried using the "ati" driver as that is what my old /etc/X11/xorg.conf file had when I grepped per the Howto. That gave me an error to the effect of "no such driver"
Per lspci, I have the following:
VGA Compatible Controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c)
Searching the forums, I found this thread that said I needed the "radeon" driver, but couldn't find any further info on what I needed to setup in order to make things work. I managed to add the radeon driver, and thought I had made what changes were needed in my make.conf and /etc/X11/xorg.conf files, but no joy....
Currently, my /etc/X11/xorg.conf file in relevant part says
Code: |
Identifier "Card 0"
Driver "radeon"
VendorName "ATI"
BoardName "3D Rage Pro AGP 1X/2X"
ChipSet "ati"
ChipId "0x4742"
ChipRev "0x5c"
BusID "PCI:1:0:0"
|
This gives the errors when trying to start X:
Code: |
(WW) RADEON: Chipset "ati" in device section "Card0" is not valid for this driver
(EE) No Devices detected
|
Changing the Chipset to "radeon" doesn't do anything but change the error message above to say "radeon" instead of "ati" .
Commenting out everything but the Identifier and the Driver gives other device not found errors.
This leaves me with two main questions....
1. What driver should I be using with this (ancient) card?
2. What values do I need to set in my /etc/X11/xorg.conf file?
Any help would be much appreciated.
Gooserider
edit to change title - (I don't usually spell like that, but needed to trim it so as to get the Solved word in...) _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video
Last edited by Gooserider on Sun Aug 27, 2006 4:37 am; edited 1 time in total |
|
Back to top |
|
|
GoingDown Tux's lil' helper
Joined: 13 Jan 2004 Posts: 117 Location: Finland
|
Posted: Fri Jul 21, 2006 5:48 am Post subject: |
|
|
radeon driver should work. Try to remove following lines from your xorg.conf:
Code: |
VendorName "ATI"
BoardName "3D Rage Pro AGP 1X/2X"
ChipSet "ati"
ChipId "0x4742"
ChipRev "0x5c"
|
Also, check with lspci that your BusID is correct |
|
Back to top |
|
|
Bloop n00b
Joined: 07 Oct 2005 Posts: 26 Location: Germany
|
Posted: Fri Jul 21, 2006 6:00 am Post subject: |
|
|
Hi there
Post your make.conf. Do you have compiled Xorg with VIDEO_CARDS= ... or this setting in make.conf?
Greetz Bloop |
|
Back to top |
|
|
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Fri Jul 21, 2006 5:22 pm Post subject: |
|
|
GoingDown: The card ID seems slightly different, I had "1:0:0", LSPCI showed "01:0.0" I fixed that and commented out the lines you suggested, The result is a slightly different error message set but still no joy...
Code: |
(WW) RADEON: No matching device section for device section for instance (BusID PCI:1:0:0) found
(EE) No Devices detected
|
Note that the Bus ID shows no change, even though I'd changed it in my /etc/X11/xorg.conf file which in relevant part now says
Code: |
Identifier "Card 0"
Driver "radeon"
# VendorName "ATI"
# BoardName "3D Rage Pro AGP 1X/2X"
# ChipSet "ati"
# ChipId "0x4742"
# ChipRev "0x5c"
BusID "PCI:01:0.0"
|
BTW, IIRC, the card ID line was auto-generated back when I first installed the original system w/ monolithic X. Is there an autoconfig for the new modular X, and would there be an advantage to running it? (How?)
Bloop:
I'm not sure what you mean by "Do you have compiled Xorg with VIDEO_CARDS= ... or this setting in make.conf?" My make.conf is here:
Code: |
CFLAGS="-0s -march=pentium2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
LDFLAGS=""
MAKEOPTS="-j2"
USE="fam kde qt hal"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARD="vesa fbdev radeon"
|
I added the last two lines per the HowTo instructions,
When I initially emerged X 7.0, I had a video card line that said "vesa fbdev ati", After I found the problem with not having an ati driver, I changed the line to say radeon and repeated the emerge (which only grabbed two files the second time)
[off-topic] I'm interested in any other thoughts people might have about USE flags, etc, but that is a side issue [/off-topic] _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video |
|
Back to top |
|
|
dpryden n00b
Joined: 12 Sep 2002 Posts: 43
|
Posted: Sun Aug 27, 2006 1:21 am Post subject: |
|
|
I have an ATI Xpert 98, which is built with the ATI 3D Rage Pro XL chipset, so it seems like a close match.
For me, the trick was changing to Driver "vesa" in xorg.conf (make sure you have "vesa" in your VIDEO_CARDS line in make.conf as well). Once I switched to VESA everything worked fine. _________________ "Anything is better than IE, and you can quote me on that." -- Wil Wheaton |
|
Back to top |
|
|
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Sun Aug 27, 2006 4:33 am Post subject: |
|
|
Well I should have changed the title to say "solved" sooner. I have X working.
What I ended up with is the following in my make.conf (relevant bits only).
Code: |
INPUT_DEVICES="mouse keyboard"
VIDEO_CARDS="radeon vesa vga fbdev mach64"
# First block of a-z flags from profile defaults,
# second block added based on wiki flag use.
# added -gnome as don't run gnome, kept gtk to support those packages that need it.
USE="alsa apche2 apm arts avi cups eds emboss encode esd foomaticdb gdbm gif -gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg libwww mad mikmod motif mp3 mpeg nptl ogg opengl oss pdflib png qt qt3 qt4 quicktime sdl spell truetype udev vorbis X xml xmms xv acpi audiofile cdparanoia cdr dvd dvdr fam flac gimpprint hardened imagemagic ncurses nptlonly pic readline scanner speex ssl xml2 xvid"
|
And in relevant part of Xorg.conf
Code: |
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "xtrap"
Load "record"
Load "dbe"
Load "dri"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
# added option line
Option "XkbModel" "pc104"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
#changed from 'Option "Device" "/dev/mouse"' to:
Option "Device" "/dev/input/mouse0"
#changed from 'Option "ZAxisMapping" "4 5 6 7"' to:
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Hitachi"
ModelName "CM812"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.0 - 107.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "ati"
VendorName "ATI"
BoardName "3D Rage Pro AGP 1X/2X"
ChipSet "ati"
ChipId 0x4742
ChipRev 0x5c
BusID "PCI:1:0:0"
EndSection
Section "Screen"
<snip>
EndSection
|
I actually have seen some stuff since that says the ATI Rage 3D Pro may actually be a Mach64 based card, and should use that driver. I know that I have that driver listed in my make.conf, but I forget just why I put it in there initially.
At any rate it works, looks better than the S3Virge based card in my Ubuntu box and does 1280x1024 on my monitor just fine (It will do 1600x1280 as well, but my eyes aren't good enough to read it without straining - getting old sux ) I'll call this one solved for now.
Gooserider _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video |
|
Back to top |
|
|
nextgen Tux's lil' helper
Joined: 17 Jun 2004 Posts: 107 Location: Montreal, Quebec, Canada
|
Posted: Wed Nov 15, 2006 10:35 pm Post subject: |
|
|
I too used the "ati" driver in my xorg.conf file, but I can't manage to have direct rendering.
Code: | $ glxinfo | grep rendering
direct rendering: No |
Were you able to have direct rendering? |
|
Back to top |
|
|
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Thu Nov 16, 2006 2:54 am Post subject: |
|
|
Sorry Nextgen, I've never really looked!
Checking right now, I don't think so - This is the output I get from "glxinfo" - it isn't something I ever really cared about honestly...
As I understand it, glx is mostly useful for gaming and other high speed graphics stuff, which I'm not into, so having bleeding edge graphics never rated very high with me. Good old standard X has always seemed enough to me for browsing, office tasks, e-mail and the like. I find that I tend to try and turn down alot of the 'eye-candy' stuff even in stock KDE, and consider 3-D to be a total dud.
Perhaps I'm an old fuddy-duddy, but I have certain things I like to do on my computer, and find that stuff like eye-candy and fancy graphics tend to be more of a distraction than a help in getting them done...
The graphics I was getting kept me happy, so I never tried poking around in them to make them better. FWIW, I don't see a big difference between the graphics on the ATI box or the Nvideous Geforce2 (w/ Open Source X driver) that I have on my newer box, or the Diamond S3 Virge card I had on the P-200 box I just retired... I was happy w/ all of them so why worry.
Code: |
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture,
GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow,
GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra,
GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels,
GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_rescale_normal,
GL_EXT_secondary_color, GL_EXT_separate_specular_color,
GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, GL_EXT_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object,
GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_ATIX_texture_env_combine3, GL_IBM_texture_mirrored_repeat,
GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
GL_NV_blend_square, GL_NV_point_sprite, GL_NV_texgen_reflection,
GL_NV_texture_rectangle, GL_SGIS_generate_mipmap,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow,
GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
|
Gooserider _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video |
|
Back to top |
|
|
nextgen Tux's lil' helper
Joined: 17 Jun 2004 Posts: 107 Location: Montreal, Quebec, Canada
|
Posted: Thu Nov 16, 2006 4:16 am Post subject: |
|
|
Thanks for the reply.
I've lived (reasonably) happily without DRI for years. I'm not into gaming either. I was hoping DRI could help relieve load on my old beloved PII 350MHz processor, which I find rather slow. |
|
Back to top |
|
|
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Thu Nov 16, 2006 10:22 pm Post subject: |
|
|
I dont know that speeding up the graphics would help that much... I've never tried to measure it, but my 'seat of the pants' impression was that graphics were never that much of a bottleneck. I always found the killers to be heavy disk use, or lots of crunching in the background (like doing a major emerge) The really serious hit came when the system started doing a lot of swapping to disk.
The best cure for that is to max out your RAM. (if you haven't already done so) Since the memory for those old boxes is pretty much obsolete, you should be able to find it for little or nothing.
One of the other things I've noticed is that at least with the stuff that I've been running, the thing acts embarrassingly like that other O/S and needs to periodically either have X restarted, or even be rebooted It seems that over a few hundred hours, I see my %use on swap slowly climb until it gets to be about 80% or so, then it skyrockets to 98%+ and the system starts flogging so badly I have trouble even getting a keyboard response so I can shut things down and I have to do a power cycle to get the system back. I don't know if it's a memory leak or what.
I will say that I'm at the point where I basically won't spend any money on upgrading my old boxes, anything I put into them will be either salvage or 'dumpster dive' parts. (of which I have plenty...)
My opinion is that right now the best bargain boxes are the fast X86-32 machines, particularly AMD Athlon's. They are cheap because everyone seems to want to go for the 64 bit machines, but they are still plenty fast, and in some ways the 32-bit software trees seem to be more available, reliable and debugged than the 64 bit stuff....
Gooserider _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video |
|
Back to top |
|
|
nextgen Tux's lil' helper
Joined: 17 Jun 2004 Posts: 107 Location: Montreal, Quebec, Canada
|
Posted: Thu Nov 16, 2006 11:07 pm Post subject: |
|
|
Quote: | I dont know that speeding up the graphics would help that much... I've never tried to measure it, but my 'seat of the pants' impression was that graphics were never that much of a bottleneck. |
I was curious to see if DRI could speed up stuff like displaying the firefox, or openoffice window textures, or even my gdm welcome display (where I can really notice my screen being painted to show the login box). There's always an extra second of wait everytime I refresh a page (compared to more recent PC's).
Quote: | The best cure for that is to max out your RAM. |
I'm at 256M of RAM: my three RAM slots are filled with 64M, 64M and 128M. I have no plan to replace them. Sometimes I get swapping when I leave multiple firefox windows up for several days. Quitting firefox is usually sufficient to bring back my memory usage to a healthy level.
Anyway, I can still play powermanga occasionally, but forget about running Google Earth... |
|
Back to top |
|
|
Gooserider Apprentice
Joined: 30 Dec 2005 Posts: 165 Location: Universe, Milky Way Galaxy, Solar System, Earth, North America, USA, MA, North Billerica
|
Posted: Fri Nov 17, 2006 3:05 am Post subject: |
|
|
Quote: | I was curious to see if DRI could speed up stuff like displaying the firefox, or openoffice window textures, or even my gdm welcome display (where I can really notice my screen being painted to show the login box). There's always an extra second of wait everytime I refresh a page (compared to more recent PC's). |
I wouldn't put that up to graphics necessarily... The whole machine is alot slower, and there's lots of background stuff happening when gdm loads. When doing a browser refresh, I've noticed that there is a big difference in speed for just the data transfer that has to happen before you can get a display. My Athlon box and the Celeron box are sitting next to each other, plugged into the same hard-wired network (cat5e, going to a via a mini router / switch to a cable modem) The Athlon reliably gets at least 30-50 KB/s on a refresh, while the Celeron is lucky to break 10 KB/s. That difference in transfer speed is enough to give you the extra wait you mention. I have learned that turning off as much non-useful stuff like background textures, etc. helps in speeding things up slightly.
Quote: | I'm at 256M of RAM: my three RAM slots are filled with 64M, 64M and 128M. I have no plan to replace them. Sometimes I get swapping when I leave multiple firefox windows up for several days. Quitting firefox is usually sufficient to bring back my memory usage to a healthy level. |
That's not a bad amount, but if you can find bigger DIMM's it wouldn't hurt to bump things up, even a little bit. I was initially running 256M, and then I found a slightly bigger DIMM that let me bump up to 321M, and even that small amount made a slight but appreciable difference. I wouldn't pay much to do it though.
Gooserider _________________ Box 1: P2 Celeron 400, 320mb RAM, 80GB HD, Cirrus Logic 4614/22/24 sound card, ATI 3D RAGE PRO AGP 1X/2X (sound & video onboard)
Box 2: AMD Athlon 2500+ 512mb RAM, 80GB HD, Gigabyte K7 Triton (Nvidia) mobo, GeForce2 video |
|
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
|
|