No GUI in Fedora 9: running on iMac G3, ATI Rage Pro vid
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
4 GB on the thumb drive should be more than adequate.
Yes, looks good (you actually read the man pages, I'm impressed...).
Don't forget that you'll have to actually "install" the 'git' package onto the running LiveCD in order to use the 'git' command. You won't need 'git' on the real machine (it would be useless). That list there should be all of the 'git' source code stuff that you need, too (ignore the other stuff listed on the DRI wiki page - it's already in xorg-x11-proto-devel package).
Once again, as far as packages, you need:
> The entire suite of all the ususal compilers and development tools and such (gcc, bison, ccache, gcc-c++, libgcc, gcc-gfortran, libtool, pkgconfig, libstdc++, libgfortran, libsigc++, plus automatic dependencies and maybe more).
> The kernel-devel-* packages for each kernel for which you want to build kmods, plus the kernel-headers-* package for latest kernel.
> The development packages for X11, especially: xorg-x11-proto-devel, xorg-sgml-doctools, xorg-x11-server-sdk, xorg-x11-xtrans-devel, plus in short: any package named 'libX*[-devel]', 'libx*[-devel]', and possibly more.
Here's an inventory of RPM packages that I have installed on F9. Some few may not be absolutely required, but.... This should be a fairly complete list:
DEVELOPMENT TOOLS (almost all are mandatory for sure):
autoconf
automake[14/15/16/17] (probably don't need all the old versions - i.e., 14/15/16/17 - just current)
binutils
bison
byacc
ccache
doxygen
elfutils
gcc
gcc-c++
gcc-fortran
gcc-objc
gettext
libtool
make
pkgconfig
texinfo
X SOFTWARE DEVELOPMENT (also install the base run-time packages - i.e., packages without the '-devel' suffix):
* = critical for sure
freetype-devel
freeglut-devel (will be re-built by you)
gd-devel
giflib-devel
libICE-devel*
libSM-devel
libX11-devel*
libXTrap-devel*
libXau-devel*
libXcomposite-devel*
libXcursor-devel*
libXdamage-devel*
libXdmcp-devel
libXevie-devel
libXext-devel*
libXfixes-devel
libXfont-devel
libXfontcache-devel
libXft-devel*
libXmu-devel*
libXp-devel*
libXrandr-devel*
libXrender-devel*
libXres-devel*
libXt-devel*
libXtst-devel
libXvMC-devel*
libXxf86dga-devel
libXxf86misc-devel*
libXxf86vm-devel*
libdmx-devel*
libdrm-devel (will be re-built by you)
libjpeg-devel
libmng-devel
libpng-devel
libtiff-devel
libxkbfile-devel
mesa-libGL-devel (will be re-built by you)
mesa-libGLU-devel (will be re-built by you)
mesa-libGLw-devel (will be re-built by you)
netpbm-devel
pixman-devel
xorg-x11-server-devel*
xorg-x11-bitmaps
xorg-x11-proto-devel*
xorg-x11-xtrans-devel*
OTHER DEVELOPMENT/MISC (may or may not be required ??? not entirely sure):
cairomm-devel
compat-libstdc++-296
compat-libstdc++-33
expat-devel
glib2-devel
glibmm24-devel
glibc-devel
libselinux-devel (somewhat optional)
ncurses-devel
pango-devel
zlib-devel
I'm sure I've missed a couple, but hopefully they get picked up as deps for other stuff.
Sorry I disappeared from this forum for six months and left a dangling thread. I had to move, and change jobs, among other issues.
I dunno if Hlinger will see that i've added a question to this post, but... here goes.
In the months since I last posted, fedora 10 came out, and there's allegedly a special spin for the old iMacs. I was wondering: has the issue with the lack of ATI Rage Pro drivers been resolved?
Are there any rmps out there now, to patch this problem in Fedora 9?
Also, does anyone know if this problem (the lack of drivers for the older ATI vid cards due to a "security issue") exists for Debian/Debian-based releases?
You are partly correct: I haven't checked back here in quite a while, but... hope you see this response soon.
No: there is no action at Fedora Project - in fact, it's moving backwards: the Mach64 DRI driver was dumped from the "official" 3D driver RPM. Bent me all out-of-shape, to put it mildly, since it makes it even harder - and says a bunch too about how much they intend to do on the bug/feature request.
Also, I know of no "special spin" for older MACS - but that doesn't mean that they don't exist, because I would never be interested in such a beast. And it probably won't help with this issue anyway.
HOWEVER... the good news is: I think that I've become skilled enough now to (attempt to) (re)build RPM packages for other architectures, like PPC. I'm still using the F9 RPMs on both F9 and F10 (and all is well here in 3D/DRI/OpenGL land!). If/when you respond, express interest, and what Fedora Release and architecture, we can proceed as you like: you can do the work, or I'm willing to give it a shot.
OR... so far as I know, OpenSuSE has the mach64.ko kmod included.
It turns out that my problem is different from yours (I think! not completely sure). You see, for the old-beast iMacs (as you term them) with the CRT monitors, there is a very specific horizontal sync and vertical refresh range that MUST be specified in the xorg.conf file, and if it isn't, well, you get the problem that I got (no gui, blank, darkened screen). I found out the fix for my problem when I just put up a post on a whim, asking if there were any Debian users who had successfully installed on an iMac and had a funtioning GUI (I was thinking about switching).
Within a few hours somebody had posted the solution, and, for the edification and education of fellow iMac/Fedora newbies like me (if there are any), here it is:
Code:
Section "Monitor"
Identifier "Monitor0" #or whatever the identifier is in YOUR file -- don't change it
... #don't change any of these other lines
HorizSync 59-61 #this...
VertRefresh 75-117 #...and this are what you add.
EndSection
Bingo! Problem solved. Once you've edited the xorg.conf file, and saved it, run startx from the command line, and you should have a GUI. I hope this will help SOMEBODY out there.
Once again, I believe that this solution only works for the CRT iMacs, but I don't know for sure.
P.S. To read the entire post on this subject over at forums.debian.net, go to:
I will post back soon on the subject of having you compile those other drivers for me, but I have to do some research, first. My monitor is funcioning perfectly, at this point.
Outstanding! Glad to hear that. And it's a Good Thing that you posted the solution here for posterity.
However, you realize of course that X11/Xorg is using the Mach64 2D video driver (xorg-x11-drv-mach64), right ? Because the 3D driver (component of mesa-dri-drivers) was dumped completely from the 3D driver package. So: don't try to enable any desktop effects, or you'll probably get a crash of X.
If the 2D driver is functioning and satisfactory for your normal desktop needs, I'd suggest that you stop now and just enjoy a working GUI. However, if you want/need 3D/DRI/OpenGL (and it's possible drawbacks, like reduced screen resolution), then proceed.
Yeah, what the hey, let's go forward and do a compile of the/those mach-64-3D pkgs.
If you wanna do a compile for me that'd be cool, but I'm not averse to doing my own, with a couple of caveats:
First off, I no longer have access to any Linux-running computers that have internet access, so I'd have to get those git-cloned trees some other way. Maybe you could download them for me, .zip 'em, and email 'em to me? Or maybe upload 'em to an online storage site?
Second, I will need to bother you from time to time with advice on the compiling.
Anyway, let me know which you wanna do, and we'll go from there.
I've got both FC9 and YellowDog 5 (based on RHEL 5/FC5), and I can tell you, Fedora 9 drags a little. Not in terms of how long the apps take to run or anything -- it's more subtle: windows scroll slowly, menus take a little split second before they open, the KDE menu takes a second to paint its icons initially. It's something that can be REALLY annoying after a while. My RAM is almost maxed out (for this computer) so I don't know if the problem is lack of memory, or a bloated kernel, or just having too many apps running, by default.
I wouldn't advise FC 10 on a G3, unless you've got a 500MHz+ processor -- and I don't even know if any of the G3s were that fast.
Oh, yeah, by the way, I use both Gnome and KDE, although KDE keeps giving me these errors about something -- KDE keeps switching the audio driver between ALSA and (I think it's called) phonon. Dunno what's up here, but I don't get any errors in Gnome.
Last edited by uncooldude; 03-25-2009 at 06:36 PM.
Sorry, I have not been here for a while, and I haven't looked into this issue any further. And I probably won't be back (for unrelated reasons), so if you wish to pursue this matter, please do so at fedoraforum.org.
It's been a while, but if you're still watching this thread and/or checking in occasionally, I have prepared the necessary software for F11 (x86), and this time including SRPMs for re-build on other architectures. I will be happy to make the necessary SRPMs available for download, if anyone desires, and if requested.
Would those SRPMs be compatible with FC9? I'm guessing not.
Umm... no. But it was so trivial to actually edit the "stock" spec files and re-build, now that I *really* know what I'm doing, that I was going to do that anyway "just because" (makes me wonder why - oh why? - Fedora Project won't just DO IT!).
Give me a few days to put it all together, and I'll upload them. You will of course still need all the RPM build tools, compilers, Development Tools & Libs, X Development & etc. to re-build the SRPMs (of libdrm and the Mesa suite), as well as the libdrm tarball (to build new kmods).
Ok, sounds like a plan. Once you have the SRPMs available, though, it's gonna take some doing on my part. I'll have lots of idiotic questions about all the Mesa/OpenGL stuff ... and then I'll have to actually compile all that crap...I'm sorta vascillating, now, between wanting to do this, and NOT wanting to do it. I've got FC9 up and running on my old iMac, and I've got XCFE running (and I like it!), and FC9's kinda antiquated now, anyway...I figure I might just use this thing as a server from here on out, and migrate to an Intel beast.
So, I guess my point is, don't knock yourself out getting those SRPMs set up for FC9, if I'm the only jackass who needs them.
Thanks for the info, and for answering my questions over the past, uh, ... year? Jesus! Been a year. Oh well. One of these days, I'll have to get a life.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.