...which would seem to suggest it's receiving a valid input signal. It's a shame there's no on-screen menu to tell us what exactly it's receiving.
Can you post the contents of the Xorg log files when both displays are connected here? They should be
/var/log/Xorg.n.log for the root user or /home/yourusername/.local/share/xorg/Xorg.n.log for your user where n is a number starting with 0.Or just get a passive ADC-to-DVI and/or ADC-to-VGA adapter and test using any other monitor
I will research and capture what’s in the Xorg.0.log, if there is one. I have found that an xorg.conf file doesn’t exist in a form I recognize. I have in the past dealt with modifying xorg.conf files to try and force monitors to work, never with any success but it was an path I was directed and guided to pursue. So I’m familiar with that option. I was shown a command line option (Xorg -configure) which generates an xorg.conf based on the information it gathers about your computer. That particular action only generated errors. I will capture that info too and share it....which would seem to suggest it's receiving a valid input signal. It's a shame there's no on-screen menu to tell us what exactly it's receiving.
Can you post the contents of the Xorg log files when both displays are connected here? They should be/var/log/Xorg.n.logfor the root user or/home/yourusername/.local/share/xorg/Xorg.n.logfor your user wherenis a number starting with 0.
Or just get a passive ADC-to-DVI and/or ADC-to-VGA adapter and test using any other monitor
My hope is that the log(s) will reveal what signal/mode is currently being sent to the ADC display: if it's not a compatible one, that's likely to be the reason it stays black. We would then have to specify the correct signal/mode manually.
Just a quick update: found Xorg.0.log while logged in as root. Saw some great info I need to study more to understand what it’s telling me. Went down a rabbit hole looking for xorg.conf.d, it held a few files notably, 10-Radeon.conf. Further searching revealed a file xorg.conf.new on the root level of the root Home folder. It contained the Sections I’ve been looking for and also requires further review to see what I might be able to change in order to get a desktop on the ACD. Logged out as root and back in under my user account and did not see the xorg.conf.new folder in my Home folder. Not sure where that file came from.
Could you copy that file to, say, a USB stick, zip it up and attach it here?
Yes, there'll be lots of info in it. Best to attach the complete file.
It suddenly dawned on me that if this could somehow be made to work, this would open up avenues to get ppc osx to at least attempt booting on completely unsupported hardware via grub or yaboot, e.g Talos II, POWER4-9, and potentially Xbox 360/PS3/GameCube/Wii/WiiU, but very likely people already thought about this over and over and we would definitely know about it. Or... have they? Anyone ever tried to slap an osx partition on on any of those already running Linux and either tell yaboot about it in yaboot.conf or compiling xnu_kernel and xnu_mkext for ppc for grub? Or tried any ppc equivalent to osx86 chainloading via chain0 in grub? Tantalising thought even if 15 years late
I've just had a look at the log (didn't see it earlier, sorry!). It looks like you only had the Hanns.G HH193 monitor connected when this was created. Is that correct? There's nothing in the log pertaining to the Apple monitor AFAICS.
I had grub booting ubuntu, windows and osx on intel hardware, albeit hackintosh. I will check whether I can get my MP 2,1 with Focal to show el capitan and SL in grub (I normally use the boot picker to choose)
It might work on the DTK or an older Hackintosh which boot using the Darwin/x86 boot loader by chainloading the PBR.
It definitely did work in my hands under Ubuntu using chain0 under Hackintosh, I had followed the guide below:
Sorry, but just read this. been busy. So, I currently have both the Apple STUDIO display (have been calling it a cinema display and was wrong) and the DVI Monitor connected. I started up in recovery mode and signed in as root. I get a hard to read screen on the Hanns DVI Monitor but the ASD is black, blank. The system recognizes it is there as I can run the cursor off the Left DVI monitor onto the Right ASD monitor. Also when I run xrandr, it shows both the DVI-0 (primary) monitor with all of it's display options and the VGA-0 with just the native 1280x1024@60,62 Hz. The VGA-0 monitor is the Apple monitor. xrandr says it's "connected"
Hey man, why would you install a super old version of Debian?
