Re: [robertpalmerjr@mac.com: Re: Suse still immature]
on 11/3/00 9:20 AM, Olaf Hering at olh@suse.de wrote:
On Fri, Nov 03, Robert G Palmer Jr wrote:
I tried the xf401 updates. I downloaded all the files into a folder on my local drive, then cd'd to that folder and executed 'rpm -Uvh *'. What I got was the following error
xpm is needed by xbanner(version..) xpm is needed by freeamp(version...) xpm is needed by xbanner(version...) xpm is needed by freeamp(version...)
I ran YAST and found xpm - it's listed as being installed. I even tried reinstalling xpm from YAST and running the rpm for the xf401 files. Same result.
the packages xbanner and freeamp need that package xpm for some reasons. freeamp doesnt work on ppc, you can remove it with "rpm -e freeamp" xbanner is also obsolete, sax needs it. But sax doesnt work very well on ppc. Just remove it as well. xpm contains some pixmaps.
This worked perfectly - had no additional problems installing the rpms
BTW, what is the xpmac stuff - just for kicks, I tried installing it and just got a X11 directory in addition to the X11R6. Is there any benefit to changing my X68config to use the X11 stuff instead of the X11R6. What are the differences. I noticed that there was also an xpmac128 specifically for the Rage128 boards. My main video board (the XClaimVR) is a RagePro. Will the standard xpm stuff support this, or should I be using the xpmac, or will the files you pointed me to (xf401) take care of the issue.
With Xpmac rev10 the r128 stuff was merged into the normal Xpmac. That obsoletes Xpmac128. But your board is a Mach64, look at /proc/fb. The /usr/X11 is a symlink to /usr/X11R6 Xpmac itself doesnt use a config file.
XFree86 4.01 should work with the "ati" driver. but the setup is a bit tricky. You can not specify a modeline to match a specific resolution. Use fbset to switch the resolution,, the ati driver will take that. It might be possible to specify something like modes "1024x768" to use the built-in modelines, but that does not work in all cases.
I don't quite understand this. I looked in the XF86config file and the modes all say default - for each of the specified bit depths. Should I be changed?
I had no time yet to write a support datebase article about the configuration issues. That will happen this weekend.
After installing the new 4.01 stuff, I saw no difference. I went into the XF86Config file and under the Devices section found that it had a parameter that was 'noaccel'. I changed this to 'accel' and restarted X. I appeared much faster, but none of the background was redrawn. Any _new_ drawing was done correctly, but what was left behind was not cleaned up. In other words, if I drug a window across the screen, it left a big ugly trail of window boundaries across the screen. These never went away. Any ----------------------------- Robert G. Palmer, Jr. Product Engineer robert.palmer@ipix.com iPIX - The Leader in Dynamic Imaging Phone: (865)-482-3000 http://www.ipix.com
On Tue, Nov 14, Robert G Palmer Jr wrote:
XFree86 4.01 should work with the "ati" driver. but the setup is a bit tricky. You can not specify a modeline to match a specific resolution. Use fbset to switch the resolution,, the ati driver will take that. It might be possible to specify something like modes "1024x768" to use the built-in modelines, but that does not work in all cases.
I don't quite understand this. I looked in the XF86config file and the modes all say default - for each of the specified bit depths. Should I be changed?
Don't use /etc/XF86config, the XFree86 4 config file is in /etc/X11
After installing the new 4.01 stuff, I saw no difference. I went into the XF86Config file and under the Devices section found that it had a parameter that was 'noaccel'. I changed this to 'accel' and restarted X. I appeared much faster, but none of the background was redrawn. Any _new_ drawing was done correctly, but what was left behind was not cleaned up. In other words, if I drug a window across the screen, it left a big ugly trail of window boundaries across the screen. These never went away.
The driver is buggy. thats the reason why we have noaccel in the options ;) Make sure the symlink /var/X11R6/bin/X points to XFree86 and not to XF86_FBDev. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
participants (2)
-
Olaf Hering
-
Robert G Palmer Jr