ATI Rage bug#308485

Hello,
I get this EE: r128(0):No DFP Detected error setting MTRR Invalid argument 22
Reading Google I get DFP is digital flat panel? I have a CRT monitor?? Seems there is a bug in this driver or Xorg. and a fix but don't know.

back again,
Ok , here's some more info. I got a little frustrated trying things and I wanted to make sure that everything was clean so I've reinstalled. I've got X running with TWM. 3 Xterms start when it starts, I've tried ctrl+alt+backspace and it won't exit. I've found a way to kill it ctrl+alt+F2 .
I'm using X.Org X Server 1.6.1.901 (1.6.2 RC1) this is my new error : EE failed to load module "ati" (module does not exist,0)
and get the same for "fbdev". I installed xf86-video-r128 for my ATI rage r128 card. I don't have the error I had before HOWEVER in the beginner's guide it clearly states as of 1.6 you shouldn't need one? or something like that.
I'm a newb so I don't have a clear understanding over modules yet but I saw that it stated the new module init tools required the conf file to be moved is this the possible reason? I also did a lsmod and didn't see either fbdev or r128 or ati listed are they listed somewhere else as I know I installed the package and I saw the fbdev package installed also? thanks

Similar Messages

Help making an old ATI Rage XL work

I have an old-ish server (from 2006-2007 more or less) that was using solaris until some months ago but was taken out of service.
It was running X with a very basic DE.
Today, I was trying to give it a new use, but I face the problem that I cannot manage to make the video card to work
lspci reports this:
05:06.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage XL (rev 27) (prog-if 00 [VGA controller])
And I installed xorg, xorg-apps and xorg-drivers but it does not seem to work auto-magically...
I tried installing the closed source drivers without luck:
When KDE is supposed to start, I get a black screen: No mouse even and the inability of switching to a text based console....
The graphic card is integrated in the motherboard..... I hope someone can at least point me in the right direction: It's nice hardware to be used with arch and it would be a shame letting it to get forgotten in a corner forever accumulating dust.
Any ideas would help.
Thanks!

Ok, I removed the vesa driver and updated the system, now I get this:
[ 10.371]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 10.371]
X.Org X Server 1.13.2.901 (1.13.3 RC 1)
Release Date: 2013-02-15
[ 10.371] X Protocol Version 11, Revision 0
[ 10.371] Build Operating System: Linux 3.7.5-1-ARCH x86_64
[ 10.371] Current Operating System: Linux MyArch 3.7.9-2-ARCH #1 SMP PREEMPT Mon Feb 25 12:04:25 CET 2013 x86_64
[ 10.371] Kernel command line: root=/dev/sda1 ro vga=773 initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 10.372] Build Date: 18 February 2013 03:52:56PM
[ 10.372]
[ 10.372] Current version of pixman: 0.28.2
[ 10.372] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 10.372] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 10.372] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 26 08:33:30 2013
[ 10.411] (==) Using config file: "/etc/X11/xorg.conf"
[ 10.411] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 10.436] (==) No Layout section. Using the first Screen section.
[ 10.436] (==) No screen section available. Using defaults.
[ 10.436] (**) |-->Screen "Default Screen Section" (0)
[ 10.436] (**) | |-->Monitor "<default monitor>"
[ 10.436] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 10.436] (**) | |-->Device "ATI Rage XL"
[ 10.436] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 10.437] (==) Automatically adding devices
[ 10.437] (==) Automatically enabling devices
[ 10.437] (==) Automatically adding GPU devices
[ 10.486] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 10.486] Entry deleted from font path.
[ 10.486] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 10.486] Entry deleted from font path.
[ 10.487] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 10.487] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 10.487] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 10.487] (II) Loader magic: 0x7fcc20
[ 10.487] (II) Module ABI versions:
[ 10.487] X.Org ANSI C Emulation: 0.4
[ 10.487] X.Org Video Driver: 13.1
[ 10.487] X.Org XInput driver : 18.0
[ 10.487] X.Org Server Extension : 7.0
[ 10.488] (--) PCI:*(0:5:6:0) 1002:4752:1002:8008 rev 39, Mem @ 0xfd000000/16777216, 0xfeaff000/4096, I/O @ 0x0000b000/256, BIOS @ 0x????????/131072
[ 10.489] Initializing built-in extension Generic Event Extension
[ 10.489] Initializing built-in extension SHAPE
[ 10.489] Initializing built-in extension MIT-SHM
[ 10.489] Initializing built-in extension XInputExtension
[ 10.489] Initializing built-in extension XTEST
[ 10.489] Initializing built-in extension BIG-REQUESTS
[ 10.489] Initializing built-in extension SYNC
[ 10.489] Initializing built-in extension XKEYBOARD
[ 10.489] Initializing built-in extension XC-MISC
[ 10.489] Initializing built-in extension SECURITY
[ 10.489] Initializing built-in extension XINERAMA
[ 10.489] Initializing built-in extension XFIXES
[ 10.489] Initializing built-in extension RENDER
[ 10.489] Initializing built-in extension RANDR
[ 10.489] Initializing built-in extension COMPOSITE
[ 10.489] Initializing built-in extension DAMAGE
[ 10.489] Initializing built-in extension MIT-SCREEN-SAVER
[ 10.489] Initializing built-in extension DOUBLE-BUFFER
[ 10.489] Initializing built-in extension RECORD
[ 10.489] Initializing built-in extension DPMS
[ 10.489] Initializing built-in extension X-Resource
[ 10.489] Initializing built-in extension XVideo
[ 10.489] Initializing built-in extension XVideo-MotionCompensation
[ 10.489] Initializing built-in extension XFree86-VidModeExtension
[ 10.489] Initializing built-in extension XFree86-DGA
[ 10.489] Initializing built-in extension XFree86-DRI
[ 10.489] Initializing built-in extension DRI2
[ 10.489] (II) LoadModule: "glx"
[ 10.556] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 10.574] (II) Module glx: vendor="X.Org Foundation"
[ 10.574] compiled for 1.13.2.901, module version = 1.0.0
[ 10.574] ABI class: X.Org Server Extension, version 7.0
[ 10.574] (==) AIGLX enabled
[ 10.574] Loading extension GLX
[ 10.574] (II) LoadModule: "mach64"
[ 10.574] (II) Loading /usr/lib/xorg/modules/drivers/mach64_drv.so
[ 10.589] (II) Module mach64: vendor="X.Org Foundation"
[ 10.589] compiled for 1.13.1, module version = 6.9.4
[ 10.589] Module class: X.Org Video Driver
[ 10.589] ABI class: X.Org Video Driver, version 13.1
[ 10.589] (II) MACH64: Driver for ATI Mach64 chipsets
[ 10.589] (++) using VT number 7
[ 10.656] (II) MACH64(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 10.656] (==) MACH64(0): Depth 24, (--) framebuffer bpp 32
[ 10.656] (==) MACH64(0): Using EXA acceleration architecture
[ 10.656] (II) MACH64: Mach64 in slot 5:6:0 detected.
[ 10.656] (II) Loading sub module "int10"
[ 10.656] (II) LoadModule: "int10"
[ 10.656] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 10.671] (II) Module int10: vendor="X.Org Foundation"
[ 10.671] compiled for 1.13.2.901, module version = 1.0.0
[ 10.671] ABI class: X.Org Video Driver, version 13.1
[ 10.674] (II) MACH64(0): Primary V_BIOS segment is: 0xc000
[ 10.674] (II) Loading sub module "ddc"
[ 10.674] (II) LoadModule: "ddc"
[ 10.674] (II) Module "ddc" already built-in
[ 10.674] (II) Loading sub module "vbe"
[ 10.674] (II) LoadModule: "vbe"
[ 10.674] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 10.685] (II) Module vbe: vendor="X.Org Foundation"
[ 10.685] compiled for 1.13.2.901, module version = 1.1.0
[ 10.685] ABI class: X.Org Video Driver, version 13.1
[ 10.686] (II) MACH64(0): VESA BIOS detected
[ 10.686] (II) MACH64(0): VESA VBE Version 2.0
[ 10.686] (II) MACH64(0): VESA VBE Total Mem: 8128 kB
[ 10.686] (II) MACH64(0): VESA VBE OEM: ATI MACH64
[ 10.686] (II) MACH64(0): VESA VBE OEM Software Rev: 1.0
[ 10.686] (II) MACH64(0): VESA VBE OEM Vendor: ATI Technologies Inc.
[ 10.686] (II) MACH64(0): VESA VBE OEM Product: MACH64GM
[ 10.686] (II) MACH64(0): VESA VBE OEM Product Rev: 01.00
[ 10.687] (II) MACH64(0): VESA VBE DDC supported
[ 10.687] (II) MACH64(0): VESA VBE DDC Level 2
[ 10.687] (II) MACH64(0): VESA VBE DDC transfer in appr. 2 sec.
[ 10.751] (II) MACH64(0): VESA VBE DDC read successfully
[ 10.752] (II) UnloadSubModule: "vbe"
[ 10.752] (II) Unloading vbe
[ 10.752] (II) UnloadSubModule: "int10"
[ 10.752] (II) Unloading int10
[ 10.752] (II) UnloadSubModule: ""
[ 10.752] (II) Unloading
[ 10.752] (II) MACH64(0): Manufacturer: DEL Model: a023 Serial#: 860305747
[ 10.752] (II) MACH64(0): Year: 2006 Week: 49
[ 10.752] (II) MACH64(0): EDID Version: 1.3
[ 10.752] (II) MACH64(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 10.752] (II) MACH64(0): Sync: Separate
[ 10.752] (II) MACH64(0): Max Image Size [cm]: horiz.: 34 vert.: 27
[ 10.752] (II) MACH64(0): Gamma: 2.20
[ 10.752] (II) MACH64(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 10.752] (II) MACH64(0): Default color space is primary color space
[ 10.752] (II) MACH64(0): First detailed timing is preferred mode
[ 10.752] (II) MACH64(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.610
[ 10.752] (II) MACH64(0): blueX: 0.146 blueY: 0.069 whiteX: 0.312 whiteY: 0.328
[ 10.752] (II) MACH64(0): Supported established timings:
[ 10.752] (II) MACH64(0): 720x400@70Hz
[ 10.752] (II) MACH64(0): 640x480@60Hz
[ 10.752] (II) MACH64(0): 640x480@75Hz
[ 10.752] (II) MACH64(0): 800x600@60Hz
[ 10.752] (II) MACH64(0): 800x600@75Hz
[ 10.752] (II) MACH64(0): 1024x768@60Hz
[ 10.752] (II) MACH64(0): 1024x768@75Hz
[ 10.752] (II) MACH64(0): 1280x1024@75Hz
[ 10.752] (II) MACH64(0): Manufacturer's mask: 0
[ 10.752] (II) MACH64(0): Supported standard timings:
[ 10.752] (II) MACH64(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 10.752] (II) MACH64(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 10.752] (II) MACH64(0): Supported detailed timing:
[ 10.752] (II) MACH64(0): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 10.752] (II) MACH64(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 10.752] (II) MACH64(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 10.752] (II) MACH64(0): Serial No: 641806C53G9S
[ 10.752] (II) MACH64(0): Monitor name: DELL E177FP
[ 10.752] (II) MACH64(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 80 kHz, PixClock max 145 MHz
[ 10.752] (II) MACH64(0): EDID (in hex):
[ 10.752] (II) MACH64(0): 00ffffffffffff0010ac23a053394733
[ 10.752] (II) MACH64(0): 3110010368221b78eeadb0a2574a9c25
[ 10.752] (II) MACH64(0): 115054a54b00714f8180010101010101
[ 10.752] (II) MACH64(0): 010101010101302a009851002a403070
[ 10.752] (II) MACH64(0): 1300520e1100001e000000ff00363431
[ 10.752] (II) MACH64(0): 3830364335334739530a000000fc0044
[ 10.752] (II) MACH64(0): 454c4c204531373746500a20000000fd
[ 10.752] (II) MACH64(0): 00384b1f500e000a2020202020200007
[ 10.752] (II) MACH64(0): EDID vendor "DEL", prod id 40995
[ 10.752] (II) MACH64(0): Using EDID range info for horizontal sync
[ 10.752] (II) MACH64(0): Using EDID range info for vertical refresh
[ 10.752] (II) MACH64(0): Printing DDC gathered Modelines:
[ 10.752] (II) MACH64(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 10.752] (II) MACH64(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 10.752] (II) MACH64(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 10.752] (II) MACH64(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 10.752] (II) MACH64(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 10.753] (II) MACH64(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 10.753] (II) MACH64(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 10.753] (II) MACH64(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 10.753] (II) MACH64(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 10.753] (II) MACH64(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 10.753] (II) MACH64(0): BIOS Data: BIOSSize=0x8000, ROMTable=0x0114.
[ 10.753] (II) MACH64(0): BIOS Data: ClockTable=0x097C, FrequencyTable=0x0000.
[ 10.753] (II) MACH64(0): BIOS Data: LCDTable=0x0000.
[ 10.753] (II) MACH64(0): BIOS Data: VideoTable=0x0000, HardwareTable=0x015E.
[ 10.753] (II) MACH64(0): BIOS Data: I2CType=0x0F, Tuner=0x00, Decoder=0x00, Audio=0x0F.
[ 10.753] (--) MACH64(0): ATI 3D Rage XL or XC graphics controller detected.
[ 10.753] (--) MACH64(0): Chip type 4752 "GR", version 7, foundry TSMC, class 0, revision 0x00.
[ 10.753] (--) MACH64(0): PCI bus interface detected; block I/O base is 0xB000.
[ 10.753] (--) MACH64(0): ATI Mach64 adapter detected.
[ 10.753] (!!) MACH64(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
[ 10.753] (--) MACH64(0): Internal RAMDAC (subtype 1) detected.
[ 10.753] (==) MACH64(0): RGB weight 888
[ 10.753] (==) MACH64(0): Default visual is TrueColor
[ 10.753] (==) MACH64(0): Using gamma correction (1.0, 1.0, 1.0)
[ 10.753] (II) MACH64(0): Using Mach64 accelerator CRTC.
[ 10.753] (II) MACH64(0): Storing hardware cursor image at 0xFD7FFC00.
[ 10.753] (II) MACH64(0): Using 8 MB linear aperture at 0xFD000000.
[ 10.753] (!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
due to linear aperture size and/or placement of hardware cursor image area.
[ 10.753] (II) MACH64(0): Using Block 0 MMIO aperture at 0xFEAFF400.
[ 10.753] (II) MACH64(0): Using Block 1 MMIO aperture at 0xFEAFF000.
[ 10.753] (II) MACH64(0): MMIO write caching enabled.
[ 10.754] (--) MACH64(0): 8192 kB of SGRAM (2:1) 32-bit detected (using 8191 kB).
[ 10.754] (WW) MACH64(0): Cannot shadow an accelerated frame buffer.
[ 10.754] (II) MACH64(0): Engine XCLK 62.353 MHz; Refresh rate code 1.
[ 10.754] (--) MACH64(0): Internal programmable clock generator detected.
[ 10.754] (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz.
[ 10.754] (II) MACH64(0): <default monitor>: Using hsync range of 31.00-80.00 kHz
[ 10.754] (II) MACH64(0): <default monitor>: Using vrefresh range of 56.00-75.00 Hz
[ 10.754] (II) MACH64(0): <default monitor>: Using maximum pixel clock of 145.00 MHz
[ 10.754] (II) MACH64(0): Estimated virtual size for aspect ratio 1.2593 is 1280x1024
[ 10.754] (II) MACH64(0): Maximum clock: 124.00 MHz
[ 10.754] (II) MACH64(0): Not using default mode "640x350" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "320x175" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "640x400" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "320x200" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "720x400" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "360x200" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "640x480" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "320x240" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "800x600" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "400x300" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1024x768i" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "512x384i" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1024x768" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "640x480" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "640x512" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "896x672" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "928x696" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "960x720" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 10.754] (II) MACH64(0): Not using default mode "700x525" (hsync out of range)
[ 10.754] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 10.754] (II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 10.754] (II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan)
[ 10.754] (--) MACH64(0): Virtual size is 1280x1024 (pitch 1280)
[ 10.754] (**) MACH64(0): *Driver mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz ezP)
[ 10.754] (**) MACH64(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz zd)
[ 10.754] (**) MACH64(0): *Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz zd)
[ 10.754] (**) MACH64(0): *Driver mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz ez)
[ 10.754] (**) MACH64(0): *Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz zd)
[ 10.754] (**) MACH64(0): *Driver mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz ez)
[ 10.754] (**) MACH64(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 10.754] (II) MACH64(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz ez)
[ 10.755] (**) MACH64(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
[ 10.755] (II) MACH64(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
[ 10.755] (II) MACH64(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 10.755] (II) MACH64(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[ 10.755] (II) MACH64(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz zd)
[ 10.755] (**) MACH64(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz ez)
[ 10.755] (**) MACH64(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz ez)
[ 10.755] (**) MACH64(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
[ 10.755] (II) MACH64(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz zd)
[ 10.755] (**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 10.755] (II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz ez)
[ 10.755] (**) MACH64(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 10.755] (II) MACH64(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz ez)
[ 10.755] (**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 10.755] (II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
[ 10.755] (II) MACH64(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 10.755] (II) MACH64(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz zd)
[ 10.755] (**) MACH64(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
[ 10.755] (II) MACH64(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz ez)
[ 10.755] (**) MACH64(0): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz zd)
[ 10.755] (**) MACH64(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
[ 10.755] (II) MACH64(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz zd)
[ 10.755] (**) MACH64(0): Display dimensions: (340, 270) mm
[ 10.755] (**) MACH64(0): DPI set to (95, 96)
[ 10.755] (II) Loading sub module "fb"
[ 10.755] (II) LoadModule: "fb"
[ 10.763] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 10.765] (II) Module fb: vendor="X.Org Foundation"
[ 10.765] compiled for 1.13.2.901, module version = 1.0.0
[ 10.765] ABI class: X.Org ANSI C Emulation, version 0.4
[ 10.765] (EE)
[ 10.765] (EE) Backtrace:
[ 10.771] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a0c6]
[ 10.771] (EE) 1: /usr/bin/X (0x400000+0x18df19) [0x58df19]
[ 10.771] (EE) 2: /usr/lib/libpthread.so.0 (0x7f88e4d4d000+0xf1e0) [0x7f88e4d5c1e0]
[ 10.771] (EE) 3: /usr/lib/xorg/modules/libfb.so (0x7f88e17e0000+0x33a1) [0x7f88e17e33a1]
[ 10.771] (EE)
[ 10.771] (EE) Segmentation fault at address 0x0
[ 10.771]
Fatal server error:
[ 10.771] Caught signal 11 (Segmentation fault). Server aborting
[ 10.771]
[ 10.771] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 10.771] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 10.771] (EE)
[ 10.796] Server terminated with error (1). Closing log file.
I don't know if feeling more confused or relieved that the error log looks to be more specific now... xD
EDIT:
I installed hwd from AUR and ran hwd -X
Two config files were created: xorg.conf.ati and xorg.conf.vesa
The .ati one didn't work, but the .vesa one did!!!!
Now I can at least run KDE and knowing the card has 8Mb of memory, I think I cannot get anything better..... No animations, but they are not necessary at all......
Changing vesa for mach64 on the driver section didn't work either.... the module loads, then unloads, like before....
Solved perhaps or do you have any more ideas?
Thanks!!!
Last edited by Xi0N (2013-02-26 08:13:54)

Supported flat panel displays for an ATI Rage 128 Pro/G4 500

I originally was using an Apple 21" CRT display with my G4/500 until the display's picture tube failed. I am now looking to purchase a flat panel w/DVI, using my G4's DVI video port and the Rage 128 Pro card. I have found conflicting information on resolutions supported by the ATI card. I am looking at a Dell UltraSharp 2005FPW 20.1-inch Wide Aspect Flat Panel LCD, and the requirements indicate that my system must be able to support WSXGA+ resolution (1680 x 1050). A 24" version of the Dell monitor requires the support of WUXGA resolution (1920x1200). WIll either of these flat panel monitors work with my G4? If not, what specs do I need to look at to determine compatibility? Thanks.
Apple G4 500 Mac OS X (10.3.1) ATI Rage 128 Pro Graphics Card

Hi JBernstein,
Karl,
I greatly appreciate your efforts to resolve my
question.
No worries, Mate!
To address a question you posed earlier, no, my G4
did not come with a ADC port. I have both VGA and
DVI-D ports on my G4/500 (Graphite) with the Rage 128
Pro ADP card, which is 16 mb and 2x.
From that, I would infer that you computer is not ADC enabled.
It was the Genius at
the Apple Store who mentioned the Radeon 9000 card as
a replacement. but he also suggested that the current
20" Apple display would work with my G4 ... we tried
that today, and the OS would not launch and power the
display. SO, we must replace the card, or live with
small displays.
Yes, the ATY 128 Pro generally does not have enough grunt to power the larger displays.
I did find a number of Radeon 9600 Pro Mac Edition
video cards on eBay, but most had a published spec of
4X, and the response to whether it was backwards
compatible with the 2x capability in my G4/500 is
that it will not work. Is that true?
All the information I have (via the ATI website) does not specifically state that the 9600 card will support AGP 2X. Other ATI cards that do support 2X have this specifically stated in the information. Therefore, there is no garauntee that the 9600 card will support 2X. Until I receive information that someone has used this card in an AGP 2X computer with success, I cannot advise trying to use it.
I have not
confirmed the Radeon 8500 as yet, but as you might
imagine, it is frustrating to get conflicting
responses.
The ATI Radeon 8500 will work in your computer (as, partially, will the 9000 - refer to my earlier posting).
Perhaps you might address a different question ... is
there any place within Apple that I can go, even with
paying a fee for services, that would definitively
provide an absolute solution to an upgrade type
question, complete with exact part number AND
guarantee that the information is quite accurate? Why
wouldn't Apple provide some type of infomration on
replacement/upgrade path for older products (geez ---
the G4/500 Graphite isn't even on the legacy products
list yet) so that the customer can invest and upgrade
without going through a challenging process to get
the right information? The information I've turned up
is vague and not geared towards solutions like this.
Apple, for all sorts of reasons (legal and commercial), is loath to provide "official" advice on the use of any third party upgrade hardware on their products. Moreover, discussions on the morality of this is probably against the terms and conditions of this discussion forum.
I'm all ears as to how to move forward with this G4
with a replacement card, if that is possible.
The way I see it, you need either an ATI 8500/9000 if your only desired upgrade is the capacity to run larger displays, or an ATI 9800 is you wish to do gaming, graphics and be able to make full use of all the new Tiger graphics facilities.
Cheers!
Karl

PCI ATI Rage 128 Pro

I just bought an ATI Rage 128 Pro 32MB PCI video card for my early quicksilver G4 (733 MHz, 1GB RAM). The idea was to add a second monitor to my 15" Apple Studio Display connected to the AGP card (ATI Rage 128 Pro with ADC and VGA). Doesn't work though:
Card does not show up in System Profiler.app in either PCI or Graphics/Displays
Display does not show up in System Preferences.app - Displays tab
Quick search on Apple.com, ATI, OWC, and Google reveals no driver information for this card.
Thanks in advance,
-- Aubrey Granner

The reason I bought this card was how I plan to use it and what I already have.
Right now, I have an older Apple Studio Display that I like and don't want to replace. It requires a Apple Display Connector, so that means I have to keep the current AGP card:
from System Profiler
ATY,Rage128Pro:
Chipset Model: ATY,Rage128Pro
Type: Display
Bus: AGP
Slot: SLOT-1
VRAM (Total): 16 MB
Vendor: ATI
Apple Studio Display:
Display Type: LCD
Resolution: 1024 x 768
Depth: 32-bit Color
Built-In: Yes
Core Image: Not Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Not Supported
I just bought a new LCD TV and it's near the mac so I thought I'd get a VGA cable and watch videos on the new screen. I don't need the "horsepower" because I'm not doing intense graphic processing, just flat, high-resolution video (I like to watch European TV shows).
Because of these reasons I bought the cheapest PCI card I could: $20
If there's another card that will work for what I want to do without breaking the bank, please let me know.
Thanks,
-- Aubrey Granner

ATi Rage 128 PRO with DVI adaptor

I got a PowerMac G4 with Ati Rage 128 Pro which has a VGA and a DVI port on it
I would like to know if the DVI port going to work with the Apple DVI to Video adaptor?
I know the postage of the adaptor said it is only for PowerMac G5 and Mac mini but is there any differences between the DVI port on the ATi Rage 128 PRO and those on G5 and Mac Mini?
Is there any other solution that I can output the display to a TV with s-video or RGB?
Thank you so much!!
Cheers,
Lawrence

I got a PowerMac G4 with Ati Rage 128 Pro which has a
VGA and a DVI port on it
I would like to know if the DVI port going to work
with the Apple DVI to Video adaptor?
I know the postage of the adaptor said it is only for
PowerMac G5 and Mac mini but is there any differences
between the DVI port on the ATi Rage 128 PRO and
those on G5 and Mac Mini?
It's not the port, but the card that matters. The conversion to video is done by the card. The adapter just sends the output to the correct pins. I think the only cards that work are the recent ATI cards. Yours is probably too old. ATI's web-site doesn't have any information on it.
Is there any other solution that I can output the
display to a TV with s-video or RGB?
You can get a newer graphics card or use a VGA to Video converter.
<http://www.ramelectronics.net/html/PC-TVvideoadapter.html>
There are other, cheaper, ones.

Dual head setup (mach64 - ATI Rage Mobility)

hello everyone!
I want to use a new extra monitor I got recently, with my laptop, I use aweosme.
I have installed:
xf86-video-mach64 (recompiled with dri support)
mach64-dri (from community)
mach64drm (from AUR)
https://wiki.archlinux.org/index.php/Mach64
Still I can't get OpenGL to work:
ismaelvc@toybox ~ $ glxinfo | egrep "direct rendering|OpenGL renderer"
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on softpipe
I don't really know if it got something to do with this but I post it anyway in case it is.
xrandr doesnt detect the other monitor:
ismaelvc@toybox ~ $ xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 175, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 87.0* 85.0 75.0 70.0 60.0 81.0
832x624 75.0
800x600 85.0 75.0 72.0 60.0 56.0
640x480 85.0 75.0 73.0 60.0
720x400 85.0
640x400 85.0
640x350 85.0
512x384 87.0 85.0 75.0 70.0 60.0
416x312 75.0
400x300 85.0 75.0 72.0 60.0 56.0
320x240 85.0 75.0 73.0 60.0
360x200 85.0
320x200 85.0
320x175 85.0
Still it displays exactly the same that gets displayed at my laptop.
I used to had problems with the drivers, I needed both mach64 and radeon for it to detect the screen properly, until I created a "20-mach64.conf" with this:
Section "Device"
Identifier "Card0"
Driver "mach64"
Card "ATI Rage Mobility - Mach64"
Option "DMAMode" "async"
Option "ForcePCIMode" "false"
Option "AgpMode" "2"
Option "AgpSize" "32"
Option "BufferSize" "2"
Option "LocalTextures" "true"
Option "EnablePageFlip" "true"
EndSection
Section "Module"
#<Your modules>
Load "glx"
Load "dri"
EndSection
Section "DRI"
Group "video" #change to any desired group to restrict access
Mode 0660
EndSection
I have a doubt regarding the commented line that came as example in the mach64 wiki that reads <your modules>, I don't know what goes in there.
Also I red this for some mach64 related xorg info:
http://www.x.org/archive/X11R6.8.0/doc/ati5.html
http://forums.fedoraforum.org/showthread.php?t=201482
The last one is for a cursor problem I have, but it wont get fixed, neither, anyway the default xcursor looks good in awesome, I switched to cli apps form many tasks, and use uzbl now! all this plus arch is now so minimmal I love it lol!
I red in a post (not in this one) mach64 chips supported dual head, but I can't find it again, I will post it when I find it.
Thanks in advance!
EDIT: ok here it is, where it say its supported: I don't understand all the configs.
http://cgit.freedesktop.org/xorg/driver … ff432c36bf
Last edited by ismaelvc (2012-06-29 03:52:09)

Sorry to necrobump but I was seeing you get a lot of incorrect information on LinuxQuestions.
The mach64 driver does NOT support dualhead. Some chips are capable of it but this feature has yet to be added to the driver. It is also not compatible with xrandr. The man page you linked to mentioning dualhead support is for xf86-video-ati. It is only accessible from the git history of xf86-video-mach64 because those drivers used to live in the same source tree.
I can try to help with DRI if that's still not working for you.

ATI Rage PCI Card is stuck on an Unsupported Res

Hey Folks, I have a G3 B&W PowerMac with a ATI Rage PCI Graphics card that is stuck on an unsupported monitor resolution. I was playing with the settings when I accidently changed the res setting to one my monitor couldn't use. Now the resolution will not change no matter what I do. It all started when I did what I stated above so I did a reinstall after I tried to delete the pref file to fix the problem. I was able to do this from the install disk. My problem is now no matter what I do before I even see Happy Mac the monitor tells me the signal is out of range. I'm going to do a test on the monitor just to check it but I don't think that's what it is. Maybe the Card is Caput? Any ideas? I have a feeling I'm going to have to borrow a CRT to see what's going on. Any ideas or suggestions? Anyone know any other compatible cards? I right now have the 128 Rage. Thanks!

As Grant indicates, there's more than one prefs file that may be at work. The two most probable are Display Preferences and Monitors Preferences (the second is in a folder by the same name - throw away the file inside that folder).
In some cases, particularly with older CRT monitors, it is possible to reset the PRAM in the monitor, too. If your monitor has separate power and video cables, you can try resetting the PRAM in the monitor itself. To do this, power everything down, disconnect the video cable from the Mac. Then turn the monitor on, wait 15 to 20 seconds, then turn it off; wait about 10 seconds, then repeat the cycle, 3 or 4 times. Then reconnect the video cable and boot back up.

Driver for the ati rage 128 ultra graphics card

WE ARE SUPPILED SOLORIES 8 (INTEL BASED) 02/02 TO ONE OF MY CUSTOMER.WE TRY TO INSTALL ON HP XE 320 PC.GRPHICS CARD DRIVER WAS NOT SELLECTING AUTOMATICALLY.IN THAT SYSTEM ATI RAGE 128 ULTRA GRAPHICS CARD(32MB ).WE ARE TRYING DIFFERNT ATI CHIPSET BUT NOT LOADING O/S FINALLY WE SELECT 640*480 STANDARD DRIVER AND LOADING COMPLTELY.I REQUIRE DRIVER FOR ATI RAGE 128 ULTRA DRIVERS.CAN YOU PL. PROVIDE ME.

Hello,
the drivers have been supplied with patch 109401-10. Maybe there are laters revisions.
Patch-ID# 109401-10
Keywords: security X11 6.4.1_x86 video driver ati 810 matrox nvidia s3 kdmconfig
Synopsis: SunOS 5.8_x86: Updated video drivers and fixes
Date: Jul/23/2001
Solaris Release: 8_x86
SunOS Release: 5.8_x86
Best regards
Michael

8600 and ATI Rage 128

Hello all. I have an 8600/200 with a Sonnet G3 400 upgrade card running OS 9.1. I installed an ATI Rage 128 video card from a PM G3 (blue and white, I think). It works OK but when I'm surfing the web and I scroll up/down the page doesn't scroll smoothly, but is instead choppy. I know the card is not native to this 8600 model, but is there any way to smooth out the scrolling choppiness? Is there a driver download from Apple or ATI? Or, would there be another type of video card that would remedy the scrolling for this machine? I installed this card to help speed up the startup since I am using an IBM monitor and at startup it takes longer for the monitor to turn on. Before I installed the ATI card, it had a VGA adapter which worked OK but also had the same startup delay for the monitor, but the scrolling worked better. I've had the same delay with other monitors. Any suggestions will be greatly appreciated. John

I'm with Grant in assigning 40-odd MB of Ram for use by any OS 9-and-below browser, and with Jeff in using a RAM Disk (under any OS that is capable of supporting one) for the browser's cache, be that browser Netscape, Mozilla or IE. That the RAM Disk may not be persistent (ie, is lost at shutdown) is not often, if ever, a source of sorrow.
If screen redrawing (as tested by Chris's suggestion) is slow, the suspicion has to be that the video card's memory is deficient, either in quantity or activity. If that is the case, removal of the card and careful cleaning of its edge connector, followed by its reseating, and careful checking for the presence and loading of its drivers (in Extensions Manager) may be in order. The quantity oof VRAM you can do little about but by upgrading the whole card. It is not impossible that some housekeeping of your hard drive may be in order. How full is it (85% or less is desirable)? Has it been recently defragmented both as to files and file directory to provide contiguous free space and ready access to files? You may have arrived at a point where the accumulation of little hindrances has become a large hurdle.

HOW TO ATi Rage 128

Hello,
I've posted a few topics about my ATi Rage 128 card... all with minimal help. Unfortunatley there doesn't seem to be anybody out there that knows how to use the Video card... I want to know how to use the inputs on the card? Can I use them as video capture tools? Should i, instead of trying to get this to work, just upgrade to a radeon card??? Thanks in advance,

There are no current video cards (with engines newer than the ATI Rage 128 that allow video input), the newer cards only have S-Video, DVI and VGA output. Using them is simple. Plug in the desired device and boot your machine, at least thats how it should work.
As far as I know, the Rage 128s video input is the only supported under OS9 or earlier. As for output, it works just like any other graphics card, although I think it only supports one screen at a time, but I could be wrong.
http://www.ati.com/products/ragepro/xclaimvr/features.html

No kext for Xserve's ATI RAGE 128 in Leopard

Xserve running OS X Server 10.5.2
The Xserve has an ATI RAGE 128 PCI graphics card from an old G3 Blue & White. System Profiler shows no kext loaded for the graphics card. The monitor displays OK, but ScreenSharing and Timbuktu both display ragged text and graphics when connecting to the Xserve.
The Extensions for the older ATI RAGE 128 graphics cards are absent from Leopard, since it isn't spec'ed to run on the B&W.
Has anyone tried using the ATI RAGE 128 Extensions from Tiger in Leopard?
Has anything changed in the way extensions are implemented that would cause Tiger's ATI RAGE 128 Extensions to fail?
TIA,
Sam

The Rage 128 Pro has all the drivers it needs in OSX, and OS9.2x. Since ATI considers it a discontinued product, they do not supply any drivers or support for it anymore. Try a google search for a manual, you might find one. Make sure to look for the Mac Rage 128 when you look it up.
Here is the thing, because these cards were shipped OEM by Apple (not retail) they didn't come with any cables or manuals, that I am aware of. You might find one for a similar Mac ATI Rage 128 based video card.

Need ATI Rage 128 support on Solaris 8-1-01 (Intel)

Hi,
I am trying to install Solaris 8 (the new 8-1-01 release) onto an intel-based PC with an AGP-based ATI Rage 128 video driver, and there appears to be no option listed in the video driver list on the install CD, and the dirver on the hardware isn't recognized. I've tried a couple of the ATI drivers, but they seem to be PCI-based only, so of course, don't find the board, and I don't get beyond the hardware config phase. I notice there's a patch (#109401-05) specifically for ATI Rage 128 drivers, but how to apply if I can't install in the first place? Any help would be appreciated.
Thanks!
David

Have you tried installing and selecting the "Generic 640X480" support? The continue on through the rest of the install.
Once you get that all complete, add the new driver, then run kdmconfig to reconfig the video stuff.
--Brett

Compaq Armada M700 & ATI Rage Mobility

Hi. It would be greatly appreciated if anyone could help. I installed Solaris 8 on my Compaq Armada M700 notebook and have had endless trouble getting the display drivers to work.
Does anyone know of any available driver for the ATI RAGE Mobility-P AGP ? I have had to resort to using RedHat Linux which does have drivers for the time being ...

You can go to www.xig.com ,as far as i knew , solaris doesn't support
ATI Rage Mobility-P , I have a same problem like yours , but I am using ATI Rage 128 Mobility (M3) , for more information you can go to
http://soldc.sun.com/support/drivers/hcl/index.html .

How to Setup LCD Monitor and ATI Rage LT Pro ? Thanks

I have already added the 109401-01 Patch to Solaris 8 (x86) , but I got
a problem , that LCD Monitor and ATI Rage LT Pro was wrong in kdmconfig,
Someone can help me how to config them? thanks

Thanks for your response.I cannot sure which drivers should be selected , I have tried the all item of ATI,LCD monitor size and resolution in kdmconfig , but it doesn't work well ,even more , I didn't see any item which shows ATI LT Pro. The system is ok, color-mapping is right ,I can see the right color (256 colors) ,but something wrong with the right block of Login Screen that was redundant on the center of normal screen. 1152x900 resolution ,which is the default resolution in Solaris.My LCD limitation is 1024x768,I don't know that might be a problem or not,could it be a problem?
Thanks.if you can send me a mail ,I can send the picture to you.
[email protected] , thanks again.

[SOLVED] Swap on video ram ATI Rage Mobility P/M AGP 2x

I'm just following this instructions:
https://wiki.archlinux.org/index.php/Swap_on_video_ram
But, i'm not sure if its possible for this old card:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device 80f6
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e9000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at e8100000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 10100000 [disabled] [size=128K]
Capabilities: <access denied>
Also I don't understand what does this entry means:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
Subsystem: Sony Corporation Device 80f6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ INTx-
Latency: 8
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Capabilities: <access denied>
Kernel driver in use: agpgart-via
Im confused because in my bios it reads:
Total Memory: 256M
Video Memory: 8M
Here is the complete output:
http://pastebin.com/dS0EFwWv
Last edited by ismaelvc (2012-06-22 22:35:21)

lol Ingenious the guys who deviced this, personally I still dont understand completely how it actually works:
http://www.webupd8.org/2011/10/increase … -with.html
https://aur.archlinux.org/packages.php?ID=52958
Bsically right now I'm trying all of this performance optimiations (where possible)
https://wiki.archlinux.org/index.php/Ma … erformance
https://wiki.archlinux.org/index.php/Im … erformance
https://wiki.archlinux.org/index.php/Im … erformance
I'm using xfce now, it consumes around 100M at start but thats because I have all kind of gadgets turned on right now, for montioring things (without all this it consumes about the same than lxde, and a little more than openbox(crunchbang style), I really like it and when I find the other 256 ram module I will try it again (with zram too of course!), openbox is nice, I'll try maybe something even lighter, and thats why I keep trying more and more lightweight apps right now.
I LOVE qterminal, now I have a yakuake drop down style terminal that is light and featured!
Also even though using zram comes at the cost of lower-time-performance, it's still faster than swaping to disk, and I can feel the difference, if I also actiate an aditional 128M swapfile (with lower priority), I can even open more progrems, but it starts lagging if it starts to get full both ram and swaps, in those cases all I do is log out and in again, but I never let it get to those stress conditions unles I feel like testing it! lol
Also this script is useful:
https://wiki.archlinux.org/index.php/Empty_Swap
(the last one is the one I use)
here is the beast (a.k.a toybox):

ATI Rage bug#308485

Similar Messages

Maybe you are looking for