@str8bs:

I logged into my root account, thinking that would be "better" in terms of the logs, but I guess it doesn't matter? There is another Xorg.0.log.old file from Sunday, when I was logged in as regular user if that is needed . . . . But todays file is uploaded as well as the "mydmesg.txt" . . . thanks for that code as well.

e.e.p

eep - Thanks for the logs. I've compared them to those you posted back when ojordan was working with you on the Lubuntu live test. I see two potential problems but am still missing what I hope is the final piece of the puzzle. We will probably have to break it to fix it. (So I can see additional log info.)

Refresh my memory if the following is correct:
1. You get kernel panics after install until you disable KMS.
2. You were able to boot the Lubuntu live test using nouveau.modeset=0 (With the expected messed up colors.)

BTW: Never use Abiword, Libre, or other advanced formatting word processors when editing system files. (like *.conf) Always use a text editor like nano, gedit, or leafpad.

@str8bs: Yes, break it to fix it . . . and thanks for the thoroughness of your effort . . . . On the first point, the kernel panics--usually the kernel panics are happening when restarting from OSX to get into the Wheezy side since "wake from suspend" has never happened I keep the computer in OSX most of the time, and this is an intermittent problem that will happen as the CLI is going thru the dmesg list, and it will then say "rebooting in 180 seconds" . . . if I just let it alone it will toggle thru the choices on its own and after 2 or 3 tries it will get to the login manager. Sometimes it will just freeze and will not say, "rebooting" . . . and I have to shut the computer down with the power button. But, in this latest round of problems that hasn't happened as much--but, so far, I haven't "disabled KMS" . . . ?? which is using some yaboot parameters in the second yaboot window? No, except for needing single user mode recently I haven't put anything in the second yaboot window . . . and it might be 50% of times to a kernel panic or not.

2). Yes, I could boot the Lubuntu LiveDVD, which was I believe the only LiveDVD that could boot up in the iMac that wasn't a black or half screen . . . . I followed ojordans suggestions, I can't remember whether it was for "nouveau.modeset=0" or if it was something else . . . . But, right, the colors were so pixilated that it was pretty much impossible to read. I could see I was in my Gmail account, but couldn't read the emails, etc. Do you need me to try to boot the Lubuntu DVD again to see what works? I may have posted what I ran?

3). Yes, I know not to use Abiword to edit files, I just used Abiword on one of those files to "open" and "save as" it . . . since right-click showed that. Of course the dmesg file "could not be opened by any application" . . . so using the code you provided was used. I usually use nano . . . like if I decide to remove the "# if this doesn't work then try 24" I'll use nano . . . BTW what does the 24 do as far as the color goes? Anyway, I'm waiting to see what we are going to break before making any further adjustments . . . .

e.e.p.

eep-
You don't need to remove my comment after the "#", just change the number from 16 to 24.
That is specifying bpp or bits per pixel otherwise known as color depth. Without those subsections and specifying default depth, FBDEV defaults to 8 bpp. By the way, that is what you are seeing with the "messed up" colors when booting nouveau.modeset=0.
bpp (color depth) is what you are setting when selecting in OSX for example, 256 colors, thousands of colors, or millions of colors. On older systems, many may prefer 16 because the system doesn't have to work as hard.

Lubuntu live test - we will retest if I come up with something, but we can't get the logs I need that way. I'm still thinking about the best way to approach this.
When I say "break to fix" , don't worry. It will be easy to revert to where we are now.

I'm doubting this will tell me much the way we currently have it configured, but could you enter terminal from GUI and post the output of the following three commands?

@str8bs:



Withouth? Withouth? Mongo no understand "withouth" . . . is that from Shakespeare? : - ))))

Hey, thanks for the clarifications on the numbers, I'll run those commands either tomorrow or Sat. I know that anything we break can be fixed, so I'm not worried . . . .

e.e.p.

Sheesh, can't a guy make a type-o. (fixed)
I hate to admit it, but I remember that movie. Shakespeare it was NOT.
"Well, Mongo ain't exactly a "who". He's more of a "what."

I forget, you may need to su to root to get the output from ls /sys/class .

@str8bs: Well, if it isn't fun it isn't worth it . . . but Mongo is my alter ego/doppelganger/muse all wrapped into one; I am the Mongo of Linux . . . . Alex Carras was great as Mongo, and, hopefully having fun before he passed on to the Happy Hunting Grounds . . . . Anyway, ran the code, both using "su" at the top and then trying "sudo" . . . and that one didn't bring anything, the next two did.

e.e.p.

eep- looks like you might have missed a space
For grins, could you try again to first su and then ls /sys/class/drm ?

@str8: Do we want a space or don't want? It looks like the first line is where I ran "su" with the space, then the next with sudo and seems like no space, but then the next two had a space?

e.e.p.

Hey buddy bud, ran it with su and sudo and with space and without space and got the same results--no such file or directory . . . .

e.e.p.