Power Mac G5 (Early 2005) Black Screen

[str8bs]

I expect if you had a 30" Apple Cinema display, this would have worked out of the box based on the modes reported with no monitor connected.

Just to make sure I'm on the same page.
1.Boot with no params. xorg.conf Driver = nouveau = checkerboard
2. Boot with no params. xorg.conf Driver =fbdev = quarter of actual Ubuntu login screen.
The above 2 repeat regardless of physical connector attached to monitor.

Documentation is scarce, so this is a shot in the dark:

boot: Linux nouveau.duallink=0

that is assuming the default is 1. You can try that too. I'm hoping that this might "separate" the dual link and make it treat the ports independently.

[Trzone]

I tried a different monitor and cable, but to no avail.
You are correct, with nouveau, I get the checkerboard, fbdev is the small screen sometimes "low graphics drive".(no options enabled)

I tried adding this to yaboot.conf and it changed the resolution:
append="video=DVI-I-2:1280x1024@60"

Perhaps this would force the resolution? Or is the resolution not the issue?

Edit:

I have tried a few modelines in the Monitor section, while this doesnt give me any errors, I get a black screen (using nouveau)

Using the fbdev driver, I am able to get a larger screen with VirtualVirtual 1680 1050 however the screen moves around (when the cursor moves to the right or bottom of the screen) around where the 720x576 default resolution ends
It gives me an error message upon login:
Cannot apply the stored config for monitors
crtc 262: trying mode 1680x1050@0hz with output at 1280x1024@0hz

Any thoughts?

[Trzone]

I forgot to add the configuration I am using (posting rather than a edit)

Section "Device"
    Identifier    "6800"
    Driver        "fbdev"
    Option    "Monitor-DVI-I-1" "DVIport1" ##curse you!
    Option    "Monitor-DVI-I-2" "DVIport2"
    Option    "Monitor-TV-1" "TVport1"
    Option    "Monitor-TV-2" "TVport2"
EndSection

Section "Monitor"
    Identifier    "DVIport2" #The one we are trying to see.
Modeline "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync
EndSection

Section "Monitor"
    Identifier    "DVIport1"
    Option    "Ignore" "true"
EndSection

Section "Monitor"
    Identifier    "TVport1"
    Option    "Ignore" "true"
EndSection

Section "Monitor"
    Identifier    "TVport2"
    Option    "Ignore" "true"
EndSection

Section "Screen"
    Identifier    "Default Screen"
    Device        "6800"
    Monitor       "DVIport2"
        DefaultDepth    24
           SubSection        "Display"
             Depth         24
#	Modes "1600"
            Virtual 1680 1050 #Remove # left of Virtual if corrupt graphics.
           EndSubSection
EndSection

Section "ServerLayout"
    Identifier    "Default Layout"
    Screen        "Default Screen"
EndSection

[str8bs]

I'm just thinking out lout right now, I'll look at the logs again when I get a chance.

Sounds close with FBDEV but it is still thinking "multi-head" and setting up a large desktop? If you CTL+ALT+F1 from there do you see your console?

1. I probably confused things with that Virtual entry. Leave that commented out. I was thinking ahead to an unrelated acceleration bug that you may see if we get it working with nouveau. Not an issue with FBDEV.

2. I was going to suggest the modeline approach you tried. I'm confused by the mode though. What monitors are we using? I'm just wanting to look up and verify supported modes. You may have already done that.

3. Did that nouveau.duallink=0 param change anything at all? I would be curious if we removed/renamed the xorg.conf, boot with no params and no montior, and grep for connected with that switch if anything changes. I was hoping it might let us disable one without the other. I haven't found a lot of information on it. http://comments.gmane.org/gmane.comp...g.nouveau/3491

[Trzone]

I think fbdev is somehow extending the display 'virtual screen' i'm not sure how that works, but if it worked outside of the small 576x700 ish window, it would be fine.


2. I switched to a dell p2210, it was more convenient and similar to the ones we will be using. I used cvt which is the way I got modelines (and looked in xorg.0.log) though all entries were slightly different. I will look up the modes (I see 1680 1050 on the monitor).

3. With the xorg.conf moved, no monitor and only nouveau.duallink=0:

Output DVI-I-1 connected
Output TV-1 connected
Output DVI-I-2 disconnected
Output TV-2 disconnected

TV-2 has always been disconnected, while the other three were on/off.

Edit: When using fbdev, my cursor always stays within the small 720x576 resolution,
It has to do with the stretching of the screen, also 720x576 must be a default, i'll try to find the config file.

[str8bs]

Interesting. That may be a good sign. Compared to the output you got in post #12 of this thread (showed load on DVI 1 and 2 with no physical monitor) that would lead me to think that it should be able to correctly probe your monitor on one of the physical ports without combining the bogus probes.

My inclination from here would be the following:
1. With no xorg.conf, try the monitor on each physical port with that duallink=0 and see if disabling 1 still kills both. IE:

Linux nouveau.duallink=0 video=DVI-I-1:d video=TV-1:d

or

2. Revert to our xorg.conf that attempts to do the same (using either FBDEV or nouveau) and remove anything that tries to force modes and boot with only:

Linux nouveau.duallink=0 video=TV-1:d

to see if we get accurate DDC probe of your monitor on DVI-I-2 and NOT the bogus modes that are fighting us.

PS: You are a trooper!

[Trzone]

I've been using this site for more info on xorg.conf:
http://www.xfree86.org/4.1.0/XF86Config.5.html

This xorg.conf displays no devices connected / disconnected
cat /var/log/Xorg.0.log | grep -i connected

Section "Device"
    Identifier    "6800"
    Driver        "fbdev"
EndSection

Section "Screen"
	Identifier "Default Screen"
	Device "6800"
EndSection

Section "ServerLayout"
	Identifier "Default Layout"
	Screen "Default Screen"
EndSection

The (--) means that it is a 'probed' configuration, it is getting the wrong information, ignoring the config. That is the real problem, yet it may also be freaking out over the dual link capability. If I can get the resolution set, then this should work hopefully

hardware: nouveaufb (video memory: 7088kB)
FBDEV(0): checking modes against framebuffer device...
FBDEV(0): checking modes against monitor...
FBDEV(0): Virtual size is 720x576 (pitch 720)
FBDEV(0): Built-in mode "current"

[str8bs]

no, nouveau is integrated in the kernel which is what you are disabling with nouveau.modeset=0

EDIT: I should clarify that, because it can be confusing: something has to assign port/address information to whatever driver you specify. The default for nvidia built in the kernel is nouveau. You can still use FBDEV driver when booting with nouveau. Just to give an extreme example on my FX5200 with KMS(nouveau) enabled booting only with video=TV-1:d assuming I have all three open source drivers installed, this is what would happen.
1. Boots fine using nouveau. apt-get remove x....nouveau.
2. Boots fine using NV (when it was working) apt-get remove x....nv
3. Boots fine using FBDEV

Phantom ports can cause failure in a couple of ways.
1. Monitor 0 gets assigned to physical port that does not exist. The machine boots fine but sets your actual active display to off.
2. Monitor 0 gets assigned to the screen you are using, but modes are "combined" with those from phantom which can result in blank screen or poor screen depending on the modes supported by the monitor.
3. Your dual link issue seems to be forcing an explicit mode based on the phantom DVI.
The key seems to be A. Making the system ignore the phantom or B. Forcing a mode out all ports that fits your monitor.

EndEdit.

No idea how your card will react due to the dual link issue, but in addition to the routes in my previous post you could try:

edit /etc/modprobe.d/blacklist-framebuffer.conf and comment (#) nvidiafb
create a minimal xorg.conf like: (edit modes to reflect those supported by your monitor)

Section "Device"
   Identifier  "MakeItWork"
   Driver      "fbdev"
EndSection

Section "Monitor"
   Identifier   "JustWannaSeeAScreen"
EndSection
   
Section "Screen"
    Identifier "MyScreen"
    Monitor "JustWannaSeeAScreen"
    DefaultDepth 16 #If this works, try changing to 24.
    SubSection "Display"
        Depth 24
        Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubsection
    SubSection "Display"
        Depth 16
        Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

and then boot:

Linux nouveau.modeset=0 video=nvidiafb:XresYres-24@60

replace XresYres-24@60 with your monitors native display resolution and rate.

EDIT: Forgot my append in yaboot. I still have to disable phantoms.

[Trzone]

Is this the correct syntax? (in yaboot.conf)
append="nouveau.modeset=0 video=nvidiafb:1680x1050-24@75"

mode "640x480" test failed
checking modes against monitor...
Virtual size is 1680x1050 (pitch 1680)
Built-in mode "current": 100.0 MHz, 58.1 kHz, 53.3 Hz

Edit: Too much information. It tests all the modes, now I am testing other things. Only a plain config will work (I will try to test the color depth, etc) I am kind of back where I started, but at least the nouveau driver is disabled
Here is my xorg.conf, attached a screenshot of my desktop

Section "Device"
    Identifier    "6800"
    Driver        "fbdev"
EndSection

Section "Screen"
	Identifier "Default Screen"
	Device "6800"
EndSection

Section "ServerLayout"
	Identifier "Default Layout"
	Screen "Default Screen"
EndSection

Edit: Better news
This line gives me a full desktop background but it turns black every 10 seconds (refreshes)
append="nouveau.modeset=1 video=nvidiafb:1680x1050-24@60 video=DVI-I-1:d video=TV-1:d video=TV-2:d"

I'll try a lower mode, also I get
CRTC 262: trying mode 1680x1050@0hz (I think that is the dcc's config)

"Default Screen" for depth/fbbpp 24/32
Thank you for helping me get this far!

[str8bs]

I'm stumped as far as how the dual link issue might change things. I just re-tested on mine and I was wrong. (I'll strike through my previous.) Forcing nvidiafb still gets me phantom port issues so I have to video=TV-1:d. I'm stumped as to how to make yours ignore the offending load on DVI.

With KMS enabled, I can boot FBDEV at 24 bit no problem.

Did booting with nouveau.duallink=0 video=DVI-I-1:d video=TV-1:d with driver fbdev in xorg.conf and no modes reveal anything? On either physical connector?