ok, so you DO have an xorg.conf file there. Can you paste the output of that here please ? In any case, you will need an xorg.conf file with the "nv" driver, as I pointed out in my last detailed post.

eep:
I see JD is helping you in the other thread. I wouldn't deviate from that direction. I am just posting this in case it helps JD or someone else isolate the root cause.

The Xorg.0.log you posted was using xorg.conf.new so doesn't tell us what the system is "calling" the output ports detected. (I haven't figured out a better way to find them yet.) However, it is possible that your issue is similar to my G5 in that it "sees" multiple heads and tries to assign multiple drivers to multiple cards as seen in this section from your upload:

dmesg appears to indicate your display detected properly but may be getting assigned to "Monitor1" instead of "Monitor0"

Again, I wouldn't deviate from JD's instruction in the other thread. There is no reason NV with xorg.conf and KMS disabled shouldn't work for you. (That I know of, but I don't know much. )

@str8bs: appreciate the time spent to look at the data, I certainly don't understand what I'm looking at there . . . . But, yes, it is xorg.conf.new because I added the "horz" and "vert" data as per some instruction from some debian expert . . . There has been an error: about "multiple displays detected . . . configuration failed" or something like that. I will be trying out JD's alterations tomorrow . . . but I guess I'm still not understanding that if choosing "nv" that will "disable" "xorg.conf" . . . . But, it should be that "nv" is already selected as the driver in the xorg.conf . . . which I already changed in the .new. Anyway, I'm hoping this will get a GUI going, that's mainly all I'm needing . . . a browser, email . . . and I'm good.

e.e.p.

@JD: Thanks for the follow-up . . . but pasting the output?? Is that not in the attachment that was above or in the 85% thread, the X.0.org or whatever? I could run any quick commands later, if needed . . . Looks like str8bs posted some shots from a couple of my log files that he thought might be helpful for troubleshooting--but is it the "cat /etc/X11/xorg.conf"?? if so I think it might be in the tar.gz attached.

e.e.p.

is not the same as

the first is the output of the configuration file for X and the second is the output of the log file produced by X, using that configuration file...

eep, it looks like your sources are commented out. There shouldn't be any # in front of these lines.

#deb http://ftp.us.debian.org/debian/wheezy main
#deb http://security.debian.org/wheezy/updates main

or your new linuxmint line.

totally correct....it's a mystery to me how he ended up with such a weird sources list...the saga continues...

SK: thanks kindly for your post, and comment about "uncommenting" those lines . . . I certainly don't know how that got that way . . . I guess I thought nothing of it or that it might be the "root" symbol . . .??? So, I'll be trying to run JD's suggestions in a few minutes, so it appears that there should be NO "#" in front of any lines in the sources list? Maybe there is a Linux poltergeist that is inhabiting my iMac???? and I should do a Linux system exorcism?

e.e.p.

et al:

WAAAAHHHAAAAA!!!!!!! I'm typing this in the iMac running straight Wheezy . . . and so far . . . it's still working. I'm cautiously optimistic . . . but not overly so just yet; I'm going to give it a few days before I declare it as "solved." But, wound up in straight Wheezy because I was trying str8bs's idea of using the Wheezy install with "install url=mintppc.org" but the installer would not allow that command, so after so many attempts to get the Mint11 going I just went with the Debian. But, as usual, there was a twist to this latest attempt too use JD's tips to get the "nv" driver installed . . . had no problem getting the /repository katya line added to the /apt/sources.list . . . then ran "apt-get (not apt, Debian didn't go for "apt") update" . . . and that ran so long it timed out. Since I had just "upgraded" yesterday I just went for the "apt-get install xserver-xorg-video-nv" . . . portion of JD's detailed list . . . and there was an error about "no PUBKEY" . . . but then it asked me if I wanted to continue "without authorization?" and I clicked "y" and it went ahead and downloaded nv . . . and it again asked did I want to install the "unauthorized" driver?? (words to that effect) . . . and it did . . . then the CLI was gone, the screen turned pink, and then all black, but it had the little clock-like symbol that becomes the mouse cursor . . . so I was hoping the CLI would come back so I could "echo "blacklist nouveau" . . . but it never came back after a few minutes of waiting. I had run that blacklist nouveau command yesterday from either theos911 or str8bs or JD, so I was hoping that maybe that was done already . . . I shut the computer down . . . . I think I rebooted into several kernel panics again . . . before finally booting into the basic Debian (probably GNOME2 desktop). I believe that I had already changed the xorg.conf file to have "nv" selected as the driver so I think that might be all squared away.
Oddly the system time was set for Pacific time but it was off by 11 hours, so I managed to correct the clock (might have been one reason for kernel panics?); the ethernet is obviously working, but network manager says the network is "unmanaged" . . . so that's perhaps one thing I'll have to look into in the upcoming weeks; and in the system tools Display says the display is "Unknown" . . . . But for now there is a basic GUI operational . . . using, I think, the "nv" driver. Thanks to everyone who offered thoughts, detailed instructions, hints, good wishes, and prayers for the lost soul who was trying to overcome basic technical shortcomings to acheive this goal . . . . BTW, the "#" was only in front of the two "CDROM" lines (which I'm assuming I don't need after the installation is over so I left them that way) . . . so I probably mistakenly added it when I wrote it down--in the "nano /etc/apt/sources.list" the deb and deb-src lines had no "#" . . . . Anyway, for now, I'm leaving it in whatever state it is in, and I'll check into some of these details once it seems like the GUI is here to stay for the long haul . . . .

e.e.p.

My fault, I forgot that you are in plain Debian. In Debian you can only use 'apt-get', but in a Mint system, you can use 'apt' and 'apt-get'. Just for your information.